Bitcoin Forum
November 17, 2018, 07:53:38 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 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 ... 547 »
921  Bitcoin / Development & Technical Discussion / Re: Confused about 2x and the 1:1 coin ownership after fork on: November 26, 2017, 05:24:27 AM
when is btc2x fork taking place? i see BCD is already gaining lot of attention although supply volume is massive than BTC core.

thank you all...
2x was canceled. Bitcoin Gold, Bitcoin Diamond, Bitcoin Cash, etc. are completely different things.
922  Bitcoin / Bitcoin Technical Support / Re: How to detect (with bitcoin-cli) if the blockchain download has been completed on: November 26, 2017, 12:47:01 AM
Thanks for your reply. I'm not sure. I mean, there must be a way to check if the blockchain loading is complete without checking how many blocks do currently exist first and then compare this number with the number of loaded block.

I have something in minde like "bitcoin-cli -proof-completeness" and getting "yes" or "no" as a result. I just want to know when the system is ready to spend any funds.
This is not possible. Bitcoind does not and cannot know when the blockchain is actually fully synced until it is fully synced (and even then it technically doesn't know it is synced). The best you can do is check the blockchain height.

There is a variable called IsInitialBlockDownload and in the next major release of Bitcoin Core, that variable will be included in the getblockchaininfo output. That is what tells the GUI to show whether it is in syncing mode or not, but IBD can be set to false before it is actually fully synced.
923  Bitcoin / Development & Technical Discussion / Re: Knots on bitcoin.org on: November 26, 2017, 12:38:25 AM
What happened was that Cobra, one of the Bitcoin.org domain co-owners, pushed a blog post to Bitcoin.org without a Pull Request. This means that he did it without consulting the contributors to the project and there was no review of the post itself. This action itself was controversial. The commit was reverted later because it had been done unilaterally without anyone else's consent.

The other problem isn't so much that Knots would be hosted there but rather that Bitcoin.org would be promoting Knots instead of Core. Knots, while based on Core, has experimental things merged and does not have as much review. There are also a few other controversial changes such as address blacklists that luke-jr implemented in it himself.
924  Bitcoin / Development & Technical Discussion / Re: Bitcoin Core tarball differences on: November 25, 2017, 05:15:02 PM
Thanks a lot. However, I want to compile it myself for my PC and 2 nodes which are running on Devuan distro.

I was actually wondering myself because there is actually no source tarball on http://bitcoin.org/en/download. There is a link there that brings me to the github repo. So I guess the only source tarball in on github.
All of the released stuff (source tarballs, binaries, etc.) can be found here: http://bitcoincore.org/bin/ and http://bitcoin.org/bin/. You should use the source tarballs that are distributed from those places as those are the ones that are deterministically built and PGP signed by the release maintainer.
925  Bitcoin / Development & Technical Discussion / Re: Blockchain Capabilities on: November 23, 2017, 06:42:02 PM
First of all, transactions are not lines or strings. They are just data in a specific format.

You can store any sequence of bytes (aka any data) that you want in the blockchain. However just because you can does not mean that you should. Storing your data means that thousands of nodes must also store your data, and that is a lot of disk space and computer power that needs to go towards storing your data for eternity. Storing arbitrary data on the blockchain is rude to node operators and everyone else that uses Bitcoin as you are taking up block space that could otherwise be used for actual transactions. So yes, you can store data, but you really shouldn't.
926  Bitcoin / Bitcoin Technical Support / Re: What is Coin Burning on: November 23, 2017, 06:24:59 PM
I don't really see why people would use this in bitcoin
There are some coins that do a "Proof of Burn" where you must burn Bitcoin in order to mine (or something like that) on the altcoin.
927  Bitcoin / Armory / Re: Armory stuck in Offline mode/can't see my transactions on: November 23, 2017, 06:10:58 PM
Try using Armory 0.96.4 RC1: http://github.com/goatpig/BitcoinArmory/releases/tag/v0.96.3.99
928  Bitcoin / Bitcoin Technical Support / Re: Sync bitcoin-core on deported fullnode ? on: November 23, 2017, 06:09:14 PM
No, you can't do that. The best you can do is have your wallet only connect to your raspberry pi and only sync off of it. But this won't help with the time required to catch up.

Alternatively you could use Electrum and setup your own Electrum server (full node with some additional things; requires bitcoind) on your raspberry pi. This would let you use your own full node but not have to wait a long time every time you want to use your wallet. However I don't know whether a raspberry pi is capable of running an Electrum server.
929  Bitcoin / Bitcoin Technical Support / Re: Lost wallet password, no recovery file on: November 21, 2017, 04:29:56 PM
If you don't have any wallet files or your password, then there is nothing that you can do.
930  Bitcoin / Bitcoin Technical Support / MOVED: Bitcoin Cash is gone.... Sent to Ledger Nano S by using QR code. on: November 20, 2017, 08:18:09 PM
This topic has been moved to Trashcan.

Duplicate
931  Bitcoin / Development & Technical Discussion / Re: why every blk00000.dat is different in every wallet? on: November 20, 2017, 07:58:00 PM
Wouldn't it make sense to normalize the block storage format?
That would make it practical to do various operations between computers, like fill missing data or compare/verify.

The block storage and file formats are normalized. What you can't do is ensure that every single node has exactly the same data in exactly the same order. This is because during normal operation, orphan blocks will cause nodes to receive different blocks in different orders. Some nodes might see a block which another node does not see at all. Or they might see two different blocks and write them in the same position. Because of orphans, it is not possible to make all nodes have exactly the same data in exactly the same order.

During initial sync, having to write the blocks to disk in blockchain order rather than order received will result in a slower sync.

Why XOR the chainstate data or (index?) database files?
To prevent antivitus software from messing with the database files because sometimes they contain virus signatures because virus signatures are embedded into the blockchain. Having the database files corrupted will require the entire database to be rebuilt which will take a long time.
932  Bitcoin / Development & Technical Discussion / Re: why every blk00000.dat is different in every wallet? on: November 20, 2017, 06:42:17 PM
Content is XORed with random key, so that antivirus software does not trigger.
The block files themselves are not XORed with the random key; the databases are.
933  Bitcoin / Bitcoin Technical Support / Re: URGENT Help Required on: November 20, 2017, 06:38:35 PM
achow please help - I did what you said to push the transaction through. Funds are showing in the address here - http://blockchain.info/address/1LAMWagYdsGKUDqUT2GxJFb1aKANywr4Ur

The transaction hasn’t come up on my computer though (bitcoin core wallet).

http://pasteboard.co/GUydvhi.jpg

It’s picked up the 0.01 bitcoin transaction but not the 10 bitcoin’s in my wallet.

Why?
Ahhhh did what achow said on both computers. Seems to have worked now. Just awaiting confirmations, will probably take a while because I sent low fees. Such a dick head  Cry
Your transaction may not necessarily reach all nodes. Both of your wallets will see the transaction once it has confirmed. But since you have broadcast it a second time through your second wallet, it should be fine.
934  Bitcoin / Bitcoin Technical Support / Re: Bitcoin ABC stuck at block 478558 and not syncing on: November 20, 2017, 06:36:04 PM
Hi, I have the same problem as the OP, I invalidated that block, and the sync will not resume anyway. How is deleting the portion of the block chain as you suggest done? Now bitcoin abc is stuck at 478557. Thank you
Stop Bitcoin Core. Go to the Bitcoin Core datadir and then the blocks folder within that. Delete the highest numbered blk*.dat and rev*.dat files. Then start Bitcoin Core. It will say it needs to reindex, let it reindex.
935  Bitcoin / Bitcoin Technical Support / Re: URGENT Help Required on: November 20, 2017, 04:44:59 PM
Please do not make duplicate threads.



Go to the transactions tab in Bitcoin Core. Right click your transaction and choose the "Copy raw transaction" option. Open the debug console and type
Code:
sendrawtransaction <copied raw transaction>
where <copied raw transaction> is where you paste what you copied. Hit enter and the transaction will be sent.
936  Bitcoin / Development & Technical Discussion / MOVED: URGENT Help Required on: November 20, 2017, 04:39:41 PM
This topic has been moved to Trashcan.

Duplicate
937  Bitcoin / Development & Technical Discussion / Re: Why Segwit adoption is so slow? on: November 20, 2017, 04:30:15 PM
^Segwit transfers are faster and cheaper? So wallets’ users would benefit?
Yes, and services which cover fees for their customers and want customers to be happy would want to have transactions that have lower transaction fees.
938  Bitcoin / Bitcoin Technical Support / Re: synchronization stuck at 494782 on: November 20, 2017, 03:19:13 PM
btc1 node currently gets stuck at block height 494782.
btc1 is literally incapable of going past block 494782 because that is when they forked (they also forked a block too early) and no one is even mining their blockchain and producing valid blocks to go past that height. You are synced as far as btc1 is able to go.

Switching to core node didn't help synchronization. Does anyone know how I can resolve this stuck issue without having to download the entire block chain again?
Install Core and do
Code:
reconsiderblock 000000000000000000386cd4605d5f2481dc5ff02f95b1a4a18749fe51ff90b7
939  Bitcoin / Development & Technical Discussion / Re: why every blk00000.dat is different in every wallet? on: November 20, 2017, 03:15:05 PM
Bitcoin Core downloads and stores in blocks in the order that they are received, not the order that they are in the blockchain. Bitcoin Core downloads multiple blocks simultaneously, so it is likely that blocks will be received and written to disk in a different order from the actual blockchain and in a different order from node to node.
940  Bitcoin / Development & Technical Discussion / Re: Why Segwit adoption is so slow? on: November 20, 2017, 03:11:33 PM
Why Segwit adoption is so slow?
It's likely because large services like Coinbase, Bitpay, and Blockchain.info have not yet implemented segwit.

Is it because of lack of wallet support?
Yes.

Are there incentives for wallet developers to implement Segwit?
For services, yes. It will cost them and their users less in fees. For other wallet software developers, the incentive is to avoid technical debt and have the latest and greatest.
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 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 ... 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!