Bitcoin Forum
December 11, 2018, 06:52:43 PM *
News: Latest Bitcoin Core release: 0.17.0 [Torrent].
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ... 547 »
501  Bitcoin / Development & Technical Discussion / Re: How to compile bitcoin-qt 0.8 for Windows on Ubuntu? on: February 11, 2018, 10:27:41 PM
I agree. Maybe later I will. I'm really a beginner Smiley and Bitcoin Core 0.8 was the simplest version of all.
Older versions are not "simpler". They may actually be harder to understand as not everything is named logically or commented well. With newer versions of the code, most things are well commented and named appropriately. Things that aren't are typically shared with older versions so using an older version really won't help.

Also newer versions have documentation that makes it easier to build and do other common things with the software.
502  Bitcoin / Development & Technical Discussion / Re: My backup strategy for the Ledger Nano on: February 11, 2018, 08:46:16 PM
80 bits of security is not considered secure. It is within the realm of practical. In cryptography terms, taking 2500 years to brute force something is weak. There's a reason you don't see anything with less than 128 bits of security actually in use for applications that need serious security.
503  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.15 multiwallet limit on: February 11, 2018, 05:54:29 PM
Lock table is out of available locker entries
This error is because each wallet.dat file is opened in the same BDB environment. The entire environment has a limited number of database locks, and it seems like 333 wallets hits that number of database locks. Of course, if you are actually receiving transactions, I think you will run into more problems even with 332 wallets since database locks are required in order to write data to the wallets.

Any way to workaround this?  Huh
In the Bitcoin Core data directory, create a file named DB_CONFIG. Put the following lines in that file:
set_lk_max_locks 400000
set_lk_max_objects 400000
That will increase the number of available locks by tenfold (was 40000, no 400000) which will let you open 10 times more wallets (assuming you have enough memory), in theory. Once you run out of locks again, just keep increasing those two numbers.
504  Bitcoin / Bitcoin Technical Support / Re: help please with Bitcoin Core download on: February 11, 2018, 05:47:06 PM
But really?  Should this programme take so long, 5 days already plus another 8 days just to download it??
Yes. That is normal.

Bitcoin Core requires the entire blockchain, which currently takes up ~170 GB of disk space. The entire blockchain must be downloaded and validated. This means that you need to have a fast internet connection and a fast processor in order to be able to download the blockchain and process blocks quickly. Furthermore, while validating blocks, Bitcoin Core will need to read many things from the hard drive, and write many things to the hard drive. So a slow hard drive is going to make the sync take even longer.

There are likely 3 things that are causing you to have a slow sync time. Firstly, your laptop has a mechanical hard drive (that's what HDD means). A mechanical hard rive has moving parts and because it has moving parts, it is slow. Thus this is a bottleneck that will slow down your sync time because it takes longer to read and write data to and from the mechanical hard drive.

Secondly, you are using a laptop, which means that you are likely using a WiFi connection. WiFi can be slow. It depends a lot on any interference, the materials between your laptop and the router, and the router that you are using. It's likely that your WiFi connection is not all that fast and thus syncing will take a longer time. Also, WiFi means that there can be more data loss and corruption, so it will take longer for the networking protocols to either resend the data or recover it.

Lastly, you are using a laptop, which means that you are likely using a slow processor. Generally Intel Core i5's are decent, but it depends on what kind of processor you have. Many laptop processors, even if they are Core i5 or Core i7, are very low powered because laptops need to have lower powered components in order to have a better battery life. This means that your laptop could be running a low powered processor which is slowing down the sync as it cannot process blocks quickly.

Does it take everyone this long to get started?
It does for everyone using Bitcoin Core. It really depends on the computer that you are using. For some people, they can be synced in 6 hours. For others, it takes weeks. But for everyone who uses Bitcoin Core, there is always a period of waiting for it to sync when you first get started.

This is also recommended to be installed to a flashdrive or hard drive away from your PC in the event of a malfunction.
No, don't do that. It absolutely is not recommended to do that. The USB protocol and the USB connection is not very fast and not very good for transferring large amounts of data without some corruption. Storing the Bitcoin Core data on an external drive is a good way to have it corrupted. There have been many more cases of people's Bitcoin Core data directories being corrupted routinely when using an external drive than when using an internal drive.

2. There is a number of web wallets that can accomplish what the Core does in an acceptable way. BlockChain for instance is the number one website and the original web wallet i'd say. It offers a wallet ID that you could save or print, and you can extract your private address or access on any other application or website that allows a private key upload. You can find a number more by googling "Bitcoin Web Wallet" and ensuring you do your research on each website that pops up.
Don't use web wallets. If you want to use a wallet that does not have to do this kind of syncing, use a wallet like Electrum. Don't use web wallets.
505  Bitcoin / Development & Technical Discussion / Re: How to compile bitcoin-qt 0.8 for Windows on Ubuntu? on: February 11, 2018, 05:31:35 PM
Why did you use BItcoin Core 0.8? Everything that is in 0.8 is available in the most recent release of Bitcoin Core (and the master branch). You should use those instead. Those also include things such as better cross compilation, increased performance, and many security and bug fixes.
506  Bitcoin / Bitcoin Technical Support / Re: wallet.dat backwards incompatibility in 0.15.1 version on: February 10, 2018, 07:36:52 PM
I was not here for long time. I hope is not just another scam site is Bitcoin Core's official site. W're moving away from using for Bitcoin Core. You can check that SHA256SUMS.asc is signed with Wladimir's release key which can be found here, here, and here (it's the same key in 3 difference places). Also is stated as the new Bitcoin Core website on's Bitcoin Core page.

Will try Bitcoin Core 0.16.0 Research Chemical 3
RC stands for Release Candidate  Tongue
507  Bitcoin / Development & Technical Discussion / Re: Difference between SegWit addresses on: February 10, 2018, 07:03:15 PM
Can I send bitcoins from a standard wallet (starting with 1, i.e: 1dr4Jindendl....) to a SegWith address starting with bc1?

If yes, can I do it on electrum?
508  Bitcoin / Bitcoin Technical Support / Re: wallet.dat backwards incompatibility in 0.15.1 version on: February 10, 2018, 05:53:04 PM
Your wallet is corrupted, kind of. I have seen this behavior before in other wallets and, if the problem is what I think it is, it has been fixed in Bitcoin Core 0.16.0.

Try using Bitcoin Core 0.16.0rc3 available from here:

If this does not work, make a backup of your wallet and try starting Bitcoin Core with the -salvagewallet option.
509  Bitcoin / Bitcoin Technical Support / Re: help needed: Import priv key from electrum bech32 address into core on: February 10, 2018, 05:50:47 PM
If I understand correctly, I didn't even need to mess with the sbtc core wallet. I should just be able to convert into legacy priv keys and do the job with those.
No, "legacy" private keys will correspond to non-segwit addresses. You will need to convert the non-segwit address into a segwit address. You can use the sbtc core wallet and use the addwitnessaddress command once you import the WIF private key.
510  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.15 multiwallet limit on: February 10, 2018, 05:43:21 PM
@achow101 Thanks, How are wallets actually loaded into memory? if the wallet.dat file is ~1.5M will the entire file be loaded into process memory (will that take ~1.5M in memory)?
All of the wallet data is read off disk and loaded into memory at start. So if your wallet is ~1.5 MB, then it should consume ~1.5 MB of memory.

Also, do you know if the new 0.16.0 allow creating new wallets on the fly?
It won't.
511  Bitcoin / Development & Technical Discussion / Re: Using the same block files for multiple coins on: February 10, 2018, 05:40:09 PM
Is there anyway to use the same blocks or block files for other every coin that has a QT wallet?
There is a way using symbolic links, but I wouldn't recommend it as it will likely just corrupt your block files. So in practice, there isn't. All you an do is copy and paste the data directory. When you do that, you have to make sure that the data directory you copy does not have blocks that would be invalid to the forked coin, i.e. there are no blocks after the forking point.
512  Bitcoin / Bitcoin Technical Support / MOVED: Smart arbitration contact will realize transaction between the legal tender and on: February 10, 2018, 05:34:20 PM
This topic has been moved to Trashcan.

513  Bitcoin / Development & Technical Discussion / Re: Atomic Multi-Path? on: February 09, 2018, 03:58:53 PM
I would like to disagree with you but I found in the past that the "Ban" button comes in to play so best not to say anything
that might upset the moderator.
Feel free to disagree. I'm fine with having a discussion. But its not okay when the discussion turns from actually talking about a topic constructively to trolling, mudslinging, and flaming.
514  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.15 multiwallet limit on: February 09, 2018, 03:54:59 PM
There's technically no limit, but of course you do have memory limits, so at some point you will run out of memory if you load too many wallets.
515  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core does not connect to the network on: February 09, 2018, 03:54:11 PM
Please post the full debug.log file.
516  Bitcoin / Development & Technical Discussion / Re: Latest bitcoin core? on: February 09, 2018, 02:02:11 AM
The biggest differences are related to syncing performance, which is going to be significantly worse for you with address indexing enabled. There were also some database changes but that's not really a problem for you.
517  Bitcoin / Development & Technical Discussion / Re: Newbie clightning on Mainnet questions on: February 08, 2018, 04:55:09 PM
So, if I manually establish connections to other nodes, a properly working configuration should remember those prior-connected nodes, and reconnect on restart ?

Even if the connects are unfunded ?
It should.
518  Bitcoin / Bitcoin Technical Support / Re: Bitcoin Core 0.15.1: RPC call to re-read config file? on: February 08, 2018, 04:21:42 PM
I know. but unfortunately I was looking for an immediate solution, since the new wallet features are not yet implemented.
No such immediate solution exists.

Finally, do you by chance know of any other full node server alternatives other than Bitcoin Core that supports full node and multi-wallets with RPC? (I was hoping for a similar full node like ethereum geth where I can create separate independent (encrypted)  accounts/wallets)
You can try btcd. I don't know if they support the functionality that you want, but it is a full node.

Was this idea abandoned back in 2012 and now re-implemented (maybe?)
Most of the functions in that PR are being reimplemented or have been reimplemented.
519  Bitcoin / Development & Technical Discussion / Re: Estimating Segwit transaction fees on: February 08, 2018, 04:17:02 PM
I think it would be best, if wallets like Electrum calculate 2 fees by default. One for sending the money as fast as possible and another to send the money within 24 hours.

Not all people needs to send their money right away, so the option is needed. And if more people use this option transaction fees would fall. If the average transaction fee lowers, fees for fast transactions will also fall as a result.
Fee estimators do that. Most of them (including Electrum and Bitcoin Core) have some option to let you select different speeds.
520  Alternate cryptocurrencies / Altcoin Discussion / Re: How to clone newest Bitcoin/Litecoin source? on: February 08, 2018, 04:14:22 PM
Those files were split into validation.{cpp, h} and net_processing.{cpp, h}.

For lines that you have to change, many of them still exist just in different places. So you can use grep to search for them.
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 [26] 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 ... 547 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!