Probably not going to matter much but as @gmaxwell mentioned in another thread hodlonaut won his case https://twitter.com/hodlonaut/status/1583086284792205312
So it might not make a difference OR faketoshi might start a scorched earth campaign and attack everyone he can. In the end it probably does not matter anyway. There will always be people who believe him and it's probably not worth anyone's time to change their opinion on that. We can just make sure that the number of people who do believe him is as small as possible.
-Dave
Topic: PSA: Get your Bitcoin off any exchange supporting "BSV" (due to insolvency risk) - page 2. (Read 1514 times)
October 20, 2022, 08:10:02 PM
October 19, 2022, 08:40:00 AM
I'm running a search for the word 'Chancellor' now, just out of curiosity. 
Off-topic, but for anyone interested: It finished after a while, with the following results. 'Chancellor' appears 8 more times on the blockchain.Code:
bitcoin@localhost:~/.bitcoin/blocks> grep -aPo '\x43\x68\x61\x6e\x63\x65\x6c\x6c\x6f\x72' *.dat
blk00000.dat:Chancellor
blk00000.dat:Chancellor
Code:
bitcoin@localhost:~/.bitcoin/blocks> grep -aPo '\x43\x68\x61\x6e\x63\x65\x6c\x6c\x6f\x72' *.dat
blk00000.dat:Chancellor
blk00280.dat:Chancellor
blk00281.dat:Chancellor
blk00315.dat:Chancellor
blk01005.dat:Chancellor
blk01241.dat:Chancellor
blk01679.dat:Chancellor
blk02741.dat:Chancellor
blk03078.dat:Chancellor
blk00000.dat:Chancellor
blk00280.dat:Chancellor
blk00281.dat:Chancellor
blk00315.dat:Chancellor
blk01005.dat:Chancellor
blk01241.dat:Chancellor
blk01679.dat:Chancellor
blk02741.dat:Chancellor
blk03078.dat:Chancellor
For example, in blk00280.dat, we have a copy of part of the actual message from the genesis block:
Code:
bitcoin@localhost:~/.bitcoin/blocks> hexdump -C blk00280.dat | grep -C 10 Chancellor
067af060 70 49 ea 5a 2f 12 8e 3e b8 0f 1c 40 1b 25 30 00 |pI.Z/..>...@.%0.|
067af070 00 00 00 6a 47 30 44 02 20 61 9f 56 b8 3c f4 47 |...jG0D. a.V.<.G|
067af080 6d a7 51 ff 1b 02 1c 46 75 59 64 ee 60 72 de 50 |m.Q....FuYd.`r.P|
067af090 0e cd b5 6c 7d 81 62 58 05 02 20 70 69 1e 15 29 |...l}.bX.. pi..)|
067af0a0 e8 9c 1a 32 d5 91 f9 80 d9 ce df 96 ca 6d d0 54 |...2.........m.T|
067af0b0 30 53 25 d6 b8 e8 6e 7a 88 de 26 01 21 03 07 94 |0S%...nz..&.!...|
067af0c0 ea 0d e0 18 68 85 21 57 89 70 87 6f 3a 14 b7 db |....h.!W.p.o:...|
067af0d0 e1 c5 5e 5a fd 01 71 9e d8 e2 13 2e e4 ce ff ff |..^Z..q.........|
067af0e0 ff ff 02 01 00 00 00 00 00 00 00 28 6a 26 54 68 |...........(j&Th|
067af0f0 65 20 54 69 6d 65 73 20 30 33 2f 4a 61 6e 2f 32 |e Times 03/Jan/2|
067af100 30 30 39 20 43 68 61 6e 63 65 6c 6c 6f 72 20 6f |009 Chancellor o|
067af110 6e 2e 2e 2e 24 82 1e 00 00 00 00 00 19 76 a9 14 |n...$........v..|
067af120 89 44 a5 66 b5 b6 fe 71 ae fb 22 89 e5 af cf 7b |.D.f...q.."....{|
067af130 40 17 c4 55 88 ac 00 00 00 00 01 00 00 00 02 3d |@..U...........=|
067af140 52 a6 8b 79 89 e8 0a 98 f7 32 d2 42 3a 55 12 98 |R..y.....2.B:U..|
067af150 0c 0f 90 97 3f bb db c0 9e 3e 9a ac bd a2 9e 01 |....?....>......|
067af160 00 00 00 da 00 48 30 45 02 21 00 b7 32 8c 22 4b |.....H0E.!..2."K|
067af170 50 4d 26 b8 15 a4 cb d6 38 33 7d 7c 4b a0 c9 5b |PM&.....83}|K..[|
067af180 b4 e6 c3 60 92 8b b4 63 c7 6c d8 02 20 76 c1 0c |...`...c.l.. v..|
067af190 55 8f fe 63 a1 01 63 76 16 05 b4 79 c9 36 b1 8d |U..c..cv...y.6..|
067af1a0 52 0f 5b 2d 0e 3e 18 aa 53 b5 fa 09 dd 01 47 30 |R.[-.>..S.....G0|
067af060 70 49 ea 5a 2f 12 8e 3e b8 0f 1c 40 1b 25 30 00 |pI.Z/..>...@.%0.|
067af070 00 00 00 6a 47 30 44 02 20 61 9f 56 b8 3c f4 47 |...jG0D. a.V.<.G|
067af080 6d a7 51 ff 1b 02 1c 46 75 59 64 ee 60 72 de 50 |m.Q....FuYd.`r.P|
067af090 0e cd b5 6c 7d 81 62 58 05 02 20 70 69 1e 15 29 |...l}.bX.. pi..)|
067af0a0 e8 9c 1a 32 d5 91 f9 80 d9 ce df 96 ca 6d d0 54 |...2.........m.T|
067af0b0 30 53 25 d6 b8 e8 6e 7a 88 de 26 01 21 03 07 94 |0S%...nz..&.!...|
067af0c0 ea 0d e0 18 68 85 21 57 89 70 87 6f 3a 14 b7 db |....h.!W.p.o:...|
067af0d0 e1 c5 5e 5a fd 01 71 9e d8 e2 13 2e e4 ce ff ff |..^Z..q.........|
067af0e0 ff ff 02 01 00 00 00 00 00 00 00 28 6a 26 54 68 |...........(j&Th|
067af0f0 65 20 54 69 6d 65 73 20 30 33 2f 4a 61 6e 2f 32 |e Times 03/Jan/2|
067af100 30 30 39 20 43 68 61 6e 63 65 6c 6c 6f 72 20 6f |009 Chancellor o|
067af110 6e 2e 2e 2e 24 82 1e 00 00 00 00 00 19 76 a9 14 |n...$........v..|
067af120 89 44 a5 66 b5 b6 fe 71 ae fb 22 89 e5 af cf 7b |.D.f...q.."....{|
067af130 40 17 c4 55 88 ac 00 00 00 00 01 00 00 00 02 3d |@..U...........=|
067af140 52 a6 8b 79 89 e8 0a 98 f7 32 d2 42 3a 55 12 98 |R..y.....2.B:U..|
067af150 0c 0f 90 97 3f bb db c0 9e 3e 9a ac bd a2 9e 01 |....?....>......|
067af160 00 00 00 da 00 48 30 45 02 21 00 b7 32 8c 22 4b |.....H0E.!..2."K|
067af170 50 4d 26 b8 15 a4 cb d6 38 33 7d 7c 4b a0 c9 5b |PM&.....83}|K..[|
067af180 b4 e6 c3 60 92 8b b4 63 c7 6c d8 02 20 76 c1 0c |...`...c.l.. v..|
067af190 55 8f fe 63 a1 01 63 76 16 05 b4 79 c9 36 b1 8d |U..c..cv...y.6..|
067af1a0 52 0f 5b 2d 0e 3e 18 aa 53 b5 fa 09 dd 01 47 30 |R.[-.>..S.....G0|
Similar in blk00281.dat:
Code:
04438c70 13 e7 d8 5d 06 ff ff ff ff 02 58 02 00 00 00 00 |...]......X.....|
04438c80 00 00 29 6a 54 68 65 20 54 69 6d 65 73 20 30 33 |..)jThe Times 03|
04438c90 2f 4a 61 6e 2f 32 30 30 39 20 43 68 61 6e 63 65 |/Jan/2009 Chance|
04438ca0 6c 6c 6f 72 20 6f 6e 20 62 2e 2e 2e 31 02 70 00 |llor on b...1.p.|
04438cb0 00 00 00 00 19 76 a9 14 77 bf 6e 7f f6 2b da d5 |.....v..w.n..+..|
04438cc0 23 7e c8 a1 da 91 f5 2b 16 28 18 63 88 ac 00 00 |#~.....+.(.c....|
04438c80 00 00 29 6a 54 68 65 20 54 69 6d 65 73 20 30 33 |..)jThe Times 03|
04438c90 2f 4a 61 6e 2f 32 30 30 39 20 43 68 61 6e 63 65 |/Jan/2009 Chance|
04438ca0 6c 6c 6f 72 20 6f 6e 20 62 2e 2e 2e 31 02 70 00 |llor on b...1.p.|
04438cb0 00 00 00 00 19 76 a9 14 77 bf 6e 7f f6 2b da d5 |.....v..w.n..+..|
04438cc0 23 7e c8 a1 da 91 f5 2b 16 28 18 63 88 ac 00 00 |#~.....+.(.c....|
Does anyone know or have a suspicion why people used / still do copy these bytes into blocks every now and then?
Maybe some miners that don't know what to put in scriptSig?
October 18, 2022, 07:23:07 AM
Since it's still trading at close to $50 a coin I took a look at CoinEx which is the only exchange I have an account in that trades it they have a 10 block confirm for trading and 30 blocks to withdraw. Either they know something we don't or have a lot more confidence that there will not be a massive reorg. Does anyone else with an account at an exchange that still trades see anything different?
I don't see the point in taking the risk at the moment, but I guess you can say that about any coin that has low to mid hashrate with an abundance of ASICs out there.
-Dave
I don't see the point in taking the risk at the moment, but I guess you can say that about any coin that has low to mid hashrate with an abundance of ASICs out there.
-Dave
October 18, 2022, 06:45:20 AM
Five explorers, five different block heights. Lol.
Looking again at the two I quoted before (which are the two which seem closest to the chain tip), they are again showing different blocks. Taking block 761,998, viawallet has an almost empty block from the unknown miner with a hash of 00000000000000000988466f0965faa0ad16c5208a6053ba4868c8ef17b3cde4, while whatsonchain has a qdlnk 4GB block with a hash of 000000000000000007765478946ed0cfeda56343ab956699bb39d1b9b44696d3.
This seems to be the case every time I check. Just endless conflicting blocks and stale chains. Reorgs within reorgs.
Looking again at the two I quoted before (which are the two which seem closest to the chain tip), they are again showing different blocks. Taking block 761,998, viawallet has an almost empty block from the unknown miner with a hash of 00000000000000000988466f0965faa0ad16c5208a6053ba4868c8ef17b3cde4, while whatsonchain has a qdlnk 4GB block with a hash of 000000000000000007765478946ed0cfeda56343ab956699bb39d1b9b44696d3.
This seems to be the case every time I check. Just endless conflicting blocks and stale chains. Reorgs within reorgs.
Sounds like the beginning of the end for BSV. Now all that's left to happen is a black swan event to cause the mass delisting & exodus to other chains and possibly even a hardfork (by someone other than nChain bros).
October 18, 2022, 06:24:24 AM
Five explorers, five different block heights. Lol.
Looking again at the two I quoted before (which are the two which seem closest to the chain tip), they are again showing different blocks. Taking block 761,998, viawallet has an almost empty block from the unknown miner with a hash of 00000000000000000988466f0965faa0ad16c5208a6053ba4868c8ef17b3cde4, while whatsonchain has a qdlnk 4GB block with a hash of 000000000000000007765478946ed0cfeda56343ab956699bb39d1b9b44696d3.
This seems to be the case every time I check. Just endless conflicting blocks and stale chains. Reorgs within reorgs.
Looking again at the two I quoted before (which are the two which seem closest to the chain tip), they are again showing different blocks. Taking block 761,998, viawallet has an almost empty block from the unknown miner with a hash of 00000000000000000988466f0965faa0ad16c5208a6053ba4868c8ef17b3cde4, while whatsonchain has a qdlnk 4GB block with a hash of 000000000000000007765478946ed0cfeda56343ab956699bb39d1b9b44696d3.
This seems to be the case every time I check. Just endless conflicting blocks and stale chains. Reorgs within reorgs.
October 18, 2022, 04:23:45 AM
The entire BSV network has collapsed. Blockchair shows no blocks for a day. https://explorer.viawallet.com/bsv and https://whatsonchain.com/blocks both show recent blocks, but different recent blocks. If you look through the past 24 hours worth of blocks, this unknown miner is mining between 70-80% of them, completely empty. At any point, this miner could decide to just ignore all blocks other than their own, completely halting all transactions and activity on BSV.
Difference on each block explorer made me curious, so i did quick research about top block height on each BSV block explorer. Here's the result,
| Link | Top block height |
| https://bchsvexplorer.com/ | 761976 |
| https://explorer.viawallet.com/bsv | 761988 |
| https://blockchair.com/bitcoin-sv | 761833 |
| https://whatsonchain.com/blocks | 761991 |
| https://www.blockchain.com/explorer/assets/bsv | 761834 |
I skipped block explorer/website which no longer update their data (indicated by last block was mined on few weeks/years ago), but none of them show same number.
And it's still on going (according to Blockchair). Honestly i don't know benefit of doing this other than proving they have full control over the network or reducing cost of running node.
Definitely some weird stuff going on. Blockchair and some other explorers are showing no blocks for ~5 hours, while other explorers are showing 50 blocks beyond that, but with dozens more empty blocks. Seems to me that CSW and co are trying to re-org out all these empty blocks?I spend a minute on r/bsv and found post showing OP_RETURN on transaction (included on empty block) which say "Pay enough fee. Not 0.05 sat/B spam. Money has value.".
https://www.reddit.com/r/bsv/comments/y71d5l/empty_block_miner_showing_his_cards_pay_enough_fee/
October 17, 2022, 06:41:08 PM
Better get your popcorn popping: https://www.reddit.com/r/bsv/comments/y62pth/bitcoin_association_freezing_funds_miner_without/
First nail in the coffin, waiting for Blockchain association to hammer the rest of the nails into BSV. Good work driving their user base away.
Actually I wouldn't be surprised if some crank forks BSV in a situation similar to Bitcoin Cash ABC vs SV.
October 17, 2022, 02:22:27 PM
I'm of the opinion that the general incompetence of Bitcoin Association to run a public blockchain, and CSW running around calling himself Satoshi, are not connected events or at least not cause-and-effect. CSW's too busy fighting legal lawsuits to get his hands dirty with most of the decisions they make 
Devil's advocate: The scammyness of Craig and Calvin scares off everyone competent.They do directly operate as his command, e.g. they said nothing about these empty blocks until Wright started railing about them. They take down any post he complains about (e.g. when they referred to BSV as a cryptocurrency), etc.
October 17, 2022, 12:47:38 PM
I'm really sad that BSV is such a top-to-bottom scam. I think they're demonstrating the *inevitable* consequences of their lack of resource constraints: Essentially zero fee income, users insecure against seizure due to the possibility of arbitrary rule changes, massive centralization in *all* parts of the ecosystem, amplifications of hashpower centralization (anyone making big blocks causes the largest miners to get more than their fair share). But someone could argue that these are really just the effects of a blockchain created and run by con-men, and not their technical and economic decisions.
I'm of the opinion that the general incompetence of Bitcoin Association to run a public blockchain, and CSW running around calling himself Satoshi, are not connected events or at least not cause-and-effect. CSW's too busy fighting legal lawsuits to get his hands dirty with most of the decisions they make
October 17, 2022, 12:42:00 PM
Better get your popcorn popping: https://www.reddit.com/r/bsv/comments/y62pth/bitcoin_association_freezing_funds_miner_without/
Wait, what? Did they miss the part where this miner has the majority hashrate on the chain and is finding ~80% of all blocks? The only way the could "freeze" their block rewards is to convince literally every person and every service which still uses BSV to not accept these coins.Quote
I'm also laughing at the fact that when Taal does manage to find a block, since it is 4 GB, in the time it takes to propagate across the network to the unknown miner, the unknown miner has often just found their own block in the meantime and orphans the 4 GB block. But tell me again about how big blocks don't cause any problems. 
I'm really sad that BSV is such a top-to-bottom scam. I think they're demonstrating the *inevitable* consequences of their lack of resource constraints: Essentially zero fee income, users insecure against seizure due to the possibility of arbitrary rule changes, massive centralization in *all* parts of the ecosystem, amplifications of hashpower centralization (anyone making big blocks causes the largest miners to get more than their fair share). But someone could argue that these are really just the effects of a blockchain created and run by con-men, and not their technical and economic decisions.
October 17, 2022, 10:32:54 AM
Better get your popcorn popping: https://www.reddit.com/r/bsv/comments/y62pth/bitcoin_association_freezing_funds_miner_without/
Wait, what? Did they miss the part where this miner has the majority hashrate on the chain and is finding ~80% of all blocks? The only way the could "freeze" their block rewards is to convince literally every person and every service which still uses BSV to not accept these coins. They can't actually prevent the miner from moving their coins since they can just mine their own transactions with their majority hashrate. Or maybe they are planning to fork to a new algorithm which only accepts blocks from Taal? BSV is so centralized already then such a fork would literally make no difference, lol. Just fork to an Excel spreadsheet on CSW's personal laptop at this point.I'm also laughing at the fact that when Taal does manage to find a block, since it is 4 GB, in the time it takes to propagate across the network to the unknown miner, the unknown miner has often just found their own block in the meantime and orphans the 4 GB block. But tell me again about how big blocks don't cause any problems.
October 17, 2022, 08:21:59 AM
Better get your popcorn popping: https://www.reddit.com/r/bsv/comments/y62pth/bitcoin_association_freezing_funds_miner_without/
First nail in the coffin, waiting for Blockchain association to hammer the rest of the nails into BSV. Good work driving their user base away.
Actually I wouldn't be surprised if some crank forks BSV in a situation similar to Bitcoin Cash ABC vs SV.
October 17, 2022, 03:21:43 AM
Better get your popcorn popping: https://www.reddit.com/r/bsv/comments/y62pth/bitcoin_association_freezing_funds_miner_without/
October 16, 2022, 09:55:27 AM
Or it could be someone trying to force a re-org
They are using the cutting edge Proof of Tweet algorithm: https://nitter.it/Arthur_van_Pelt/status/1581464913591291904#mThe entire BSV network has collapsed. Blockchair shows no blocks for a day. https://explorer.viawallet.com/bsv and https://whatsonchain.com/blocks both show recent blocks, but different recent blocks. If you look through the past 24 hours worth of blocks, this unknown miner is mining between 70-80% of them, completely empty. At any point, this miner could decide to just ignore all blocks other than their own, completely halting all transactions and activity on BSV.
The amount of copium on Twitter is hilarious. Everything from "There is no attack" to "This is good because it means fees will be pushed higher than the subsidy" to "This is just someone trying to load up their bags with block rewards before we moon" (seriously). People are unable to make transactions, and there are frequent reorgs dozens of blocks deep.
Any word on exchanges starting to implement freezes on BSV withdrawals/deposits? Even if someone does manage to get a deposit confirmed on the network, I can't imagine the exchange will be too happy when a reorg makes that deposit disappear 100 blocks later. Given I can only imagine the majority of BSV bagholders will be keen to dump their bags for real bitcoin as soon as possible, any exchange which continues to accept BSV deposits is at a huge risk of loss, even without CSW's new software allowing him to arbitrarily seize any coins he likes. So back to the original point of this thread: Get your bitcoin in to your own wallets as soon as possible.
October 16, 2022, 08:25:04 AM
And now they are showing no blocks for 16 hours, last one as of this post was Oct 15, 2022, 8:26 PM UTC.
Since it was mentioned earlier in the thread that only 9 nodes at the tip, it could be that a bunch of places were all puling data from the same place that shit the bed.
Or it could be someone trying to force a re-org and others fighting it and due to the massive chain bloat severs are just spinning themselves into oblivion, or it could be bad coding caused an issue. Fun to speculate but until the people running the public block explorers tell us, it's just conjecture.
Either way, it's interesting to watch.
-Dave
Since it was mentioned earlier in the thread that only 9 nodes at the tip, it could be that a bunch of places were all puling data from the same place that shit the bed.
Or it could be someone trying to force a re-org and others fighting it and due to the massive chain bloat severs are just spinning themselves into oblivion, or it could be bad coding caused an issue. Fun to speculate but until the people running the public block explorers tell us, it's just conjecture.
Either way, it's interesting to watch.
-Dave
October 15, 2022, 11:37:30 AM
And it's still on going (according to Blockchair). Honestly i don't know benefit of doing this other than proving they have full control over the network or reducing cost of running node.
Definitely some weird stuff going on. Blockchair and some other explorers are showing no blocks for ~5 hours, while other explorers are showing 50 blocks beyond that, but with dozens more empty blocks. Seems to me that CSW and co are trying to re-org out all these empty blocks?Whoever this unknown miner is, they control a majority of the hashrate and are finding somewhere between 70-80% of BSV blocks. We always knew BSV was a centralized scam coin, but currently instead of it being centralized under CSW's control it is centralized under the control of this unknown miner.
Wonder if they'll start using the new protocol to simply assign every BSV in existence to themselves?
October 15, 2022, 10:53:00 AM
It's just XOR operation with random key and IIRC it's used on chainstate rather blocks directory.
Oh, that's true! The LevelDB UTXO database does have scrambled values.First of all, every value in the database has been obfuscated, so you will need the get the obfuscate_key (the first entry in the database):
An obfuscated value from the database will look something like this:
To deobfuscate it, you just need to extend the obfuscate_key to the same length as the value, and then XOR the value with that extended obfuscate_key:
Code:
b12dcefd8f872536
Code:
71a9e87d62de25953e189f706bcf59263f15de1bf6c893bda9b045
Code:
71a9e87d62de25953e189f706bcf59263f15de1bf6c893bda9b045 <- value
b12dcefd8f872536b12dcefd8f872536b12dcefd8f872536b12dce <- extended obfuscate_key
c0842680ed5900a38f35518de4487c108e3810e6794fb68b189d8b <- deobfuscated value (XOR)
So I guess if people store obscene data or malware pieces in (unspendable or not) UTXOs, the bytes might not be matched by government agencies and antiviruses. If it's in a blk*.dat file, it's different, though.
For example, we can find the byte representation of 'Chancellor on brink of second bailout for banks' easily in our bitcoin folder.
Looking for strings like this;
Code:
bitcoin@localhost:~/.bitcoin/blocks> strings *.dat | grep 'Chancellor on brink of second bailout for banks'
EThe Times 03/Jan/2009 Chancellor on brink of second bailout for banks
But we can also search for 'magic bytes' easily, as follows:
Code:
bitcoin@localhost:~/.bitcoin/blocks> grep -aPo '\x54\x68\x65\x20\x54\x69\x6D\x65\x73\x20\x30\x33\x2F\x4A\x61\x6E\x2F\x32\x30\x30\x39\x20\x43\x68\x61\x6E\x63\x65\x6C\x6C\x6F\x72\x20\x6F\x6E\x20\x62\x72\x69\x6E\x6B\x20\x6F\x66\x20\x73\x65\x63\x6F\x6E\x64\x20\x62\x61\x69\x6C\x6F\x75\x74\x20\x66\x6F\x72\x20\x62\x61\x6E\x6B\x73' *.dat
blk00000.dat:The Times 03/Jan/2009 Chancellor on brink of second bailout for banks
I'm running a search for the word 'Chancellor' now, just out of curiosity.
Code:
bitcoin@localhost:~/.bitcoin/blocks> grep -aPo '\x43\x68\x61\x6e\x63\x65\x6c\x6c\x6f\x72' *.dat
blk00000.dat:Chancellor
October 15, 2022, 07:01:52 AM
So recently 50% of BSV's hashpower comes from something called "mempool.com". Most explorers have been claiming this hashpower as "unknown" but the blocks are identified.
Any idea why they are mining empty blocks? Are CSW and Taal going to simply re-org all these blocks away because they don't like them?And it's still on going (according to Blockchair). Honestly i don't know benefit of doing this other than proving they have full control over the network or reducing cost of running node.
AFAIK they haven't broken the scrambling support in the code they copied from Bitcoin Core so their block files should be scrambled with some weak encryption that will prevent dumb scanning tools from finding things in them (we added that in bitcoin to prevent idiot anti-virus software from corrupting peoples blockchains when someone inserted some twentysome byte virus pattern in the chain).
I didn't know the blocks were scrambled in the (BTC) database. Can you post a link to the PR that added this?
It's just XOR operation with random key and IIRC it's used on chainstate rather blocks directory.
October 14, 2022, 06:07:28 PM
AFAIK they haven't broken the scrambling support in the code they copied from Bitcoin Core so their block files should be scrambled with some weak encryption that will prevent dumb scanning tools from finding things in them (we added that in bitcoin to prevent idiot anti-virus software from corrupting peoples blockchains when someone inserted some twentysome byte virus pattern in the chain).
I didn't know the blocks were scrambled in the (BTC) database. Can you post a link to the PR that added this?I also tried on a few blocks and nothing seems scrambled; whole block is stored on disk, piece by piece.
You are referring to the structure of a blk*.dat file?
It is explained here: https://learnmeabitcoin.com/technical/blkdat
You can even hover over part of the genesis block to get annotations on what bytes are what, as shown below.
I also queried a few selected blocks for you (first 0x90 bytes each).
As we can see, they are just a concatenation of blocks. Blocks start with the mainnet's magic bytes f9beb4d9, followed by 4 bytes of size of the following block and then the header and body.
Bitcoin Wiki actually defines the whole structure quite well.
More details about the header here: https://en.bitcoin.it/wiki/Block_hashing_algorithm
You can quickly find all the block starts in blk00000.dat like this:
You can also see where the next block starts by using the 0x125 'offset' from the above command's output and hexdump the block file until that point (plus 8 bytes of the next block just to confirm it really is the next block):
[...]
It is explained here: https://learnmeabitcoin.com/technical/blkdat
You can even hover over part of the genesis block to get annotations on what bytes are what, as shown below.
I also queried a few selected blocks for you (first 0x90 bytes each).
Code:
bitcoin@localhost:~/.bitcoin/blocks> hexdump -C blk00000.dat | head
00000000 f9 be b4 d9 1d 01 00 00 01 00 00 00 00 00 00 00 |................|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 3b a3 ed fd |............;...|
00000030 7a 7b 12 b2 7a c7 2c 3e 67 76 8f 61 7f c8 1b c3 |z{..z.,>gv.a....|
00000040 88 8a 51 32 3a 9f b8 aa 4b 1e 5e 4a 29 ab 5f 49 |..Q2:...K.^J)._I|
00000050 ff ff 00 1d 1d ac 2b 7c 01 01 00 00 00 01 00 00 |......+|........|
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff |................|
00000080 ff ff 4d 04 ff ff 00 1d 01 04 45 54 68 65 20 54 |..M.......EThe T|
00000090 69 6d 65 73 20 30 33 2f 4a 61 6e 2f 32 30 30 39 |imes 03/Jan/2009|
bitcoin@localhost:~/.bitcoin/blocks> hexdump -C blk01337.dat | head
00000000 f9 be b4 d9 e8 e3 11 00 00 00 00 20 ea 58 90 18 |........... .X..|
00000010 60 a5 72 4d 96 f4 86 48 cb 7c c4 1d 35 6f 15 4a |`.rM...H.|..5o.J|
00000020 fa 9e 26 00 00 00 00 00 00 00 00 00 8a 12 56 61 |..&...........Va|
00000030 81 67 04 09 5e b6 b9 ca e6 6b 55 11 e8 15 b3 03 |.g..^....kU.....|
00000040 44 d9 ec f2 28 09 37 aa 6a e3 b6 86 8d ff 68 5b |D...(.7.j.....h[|
00000050 7b 4f 2f 17 36 4f 8f 4c fd 7e 05 01 00 00 00 00 |{O/.6O.L.~......|
00000060 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000080 00 00 ff ff ff ff 55 03 0d 2c 08 41 d6 da 3f e1 |......U..,.A..?.|
00000090 c8 72 c2 41 d6 da 3f e1 58 d3 4b 2f 42 54 43 2e |.r.A..?.X.K/BTC.|
bitcoin@localhost:~/.bitcoin/blocks> hexdump -C blk03203.dat | head
00000000 f9 be b4 d9 88 e5 16 00 00 a0 1a 21 d2 aa ee 3a |...........!...:|
00000010 0b 36 2d 02 14 34 b7 e2 f8 28 ac 90 04 15 be ce |.6-..4...(......|
00000020 2d 25 01 00 00 00 00 00 00 00 00 00 77 ee 79 dd |-%..........w.y.|
00000030 57 09 1c d6 b3 48 03 c2 c6 84 46 5a f4 c9 cc 2a |W....H....FZ...*|
00000040 e6 bf 80 db 97 3d bf bf fb 80 c7 0c d4 b1 29 63 |.....=........)c|
00000050 94 c8 08 17 30 cf 27 9d fd 9b 0b 01 00 00 00 00 |....0.'.........|
00000060 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000080 00 00 ff ff ff ff 4c 03 fc 84 0b 13 62 69 6e 61 |......L.....bina|
00000090 6e 63 65 2f 37 38 39 48 00 0b 03 7e f9 3b fc fa |nce/789H...~.;..|
bitcoin@localhost:~/.bitcoin/blocks>
Bitcoin Wiki actually defines the whole structure quite well.
More details about the header here: https://en.bitcoin.it/wiki/Block_hashing_algorithm
You can quickly find all the block starts in blk00000.dat like this:
Code:
bitcoin@localhost:~/.bitcoin/blocks> hexdump -C blk00000.dat | grep "f9 be b4" | head
00000000 f9 be b4 d9 1d 01 00 00 01 00 00 00 00 00 00 00 |................|
00000120 ac 00 00 00 00 f9 be b4 d9 d7 00 00 00 01 00 00 |................|
00000200 00 00 00 00 f9 be b4 d9 d7 00 00 00 01 00 00 00 |................|
000002e0 00 00 00 f9 be b4 d9 d7 00 00 00 01 00 00 00 bd |................|
000003c0 00 00 f9 be b4 d9 d7 00 00 00 01 00 00 00 49 44 |..............ID|
000004a0 00 f9 be b4 d9 d7 00 00 00 01 00 00 00 85 14 4a |...............J|
00000580 f9 be b4 d9 d7 00 00 00 01 00 00 00 fc 33 f5 96 |.............3..|
00000810 1f f7 05 29 d6 2e 0b a1 ac 00 00 00 00 f9 be b4 |...)............|
000008f0 86 43 f6 56 b4 12 a3 ac 00 00 00 00 f9 be b4 d9 |.C.V............|
000009d0 b3 86 81 64 25 dd ac 00 00 00 00 f9 be b4 d9 d7 |...d%...........|
You can also see where the next block starts by using the 0x125 'offset' from the above command's output and hexdump the block file until that point (plus 8 bytes of the next block just to confirm it really is the next block):
Code:
bitcoin@localhost:~/.bitcoin/blocks> head -c $(python3 -c 'print(0x125+8)') blk00000.dat | hexdump -C
00000000 f9 be b4 d9 1d 01 00 00 01 00 00 00 00 00 00 00 |................|
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000020 00 00 00 00 00 00 00 00 00 00 00 00 3b a3 ed fd |............;...|
00000030 7a 7b 12 b2 7a c7 2c 3e 67 76 8f 61 7f c8 1b c3 |z{..z.,>gv.a....|
00000040 88 8a 51 32 3a 9f b8 aa 4b 1e 5e 4a 29 ab 5f 49 |..Q2:...K.^J)._I|
00000050 ff ff 00 1d 1d ac 2b 7c 01 01 00 00 00 01 00 00 |......+|........|
00000060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ff ff |................|
00000080 ff ff 4d 04 ff ff 00 1d 01 04 45 54 68 65 20 54 |..M.......EThe T|
00000090 69 6d 65 73 20 30 33 2f 4a 61 6e 2f 32 30 30 39 |imes 03/Jan/2009|
000000a0 20 43 68 61 6e 63 65 6c 6c 6f 72 20 6f 6e 20 62 | Chancellor on b|
000000b0 72 69 6e 6b 20 6f 66 20 73 65 63 6f 6e 64 20 62 |rink of second b|
000000c0 61 69 6c 6f 75 74 20 66 6f 72 20 62 61 6e 6b 73 |ailout for banks|
000000d0 ff ff ff ff 01 00 f2 05 2a 01 00 00 00 43 41 04 |........*....CA.|
000000e0 67 8a fd b0 fe 55 48 27 19 67 f1 a6 71 30 b7 10 |g....UH'.g..q0..|
000000f0 5c d6 a8 28 e0 39 09 a6 79 62 e0 ea 1f 61 de b6 |\..(.9..yb...a..|
00000100 49 f6 bc 3f 4c ef 38 c4 f3 55 04 e5 1e c1 12 de |I..?L.8..U......|
00000110 5c 38 4d f7 ba 0b 8d 57 8a 4c 70 2b 6b f1 1d 5f |\8M....W.Lp+k.._|
00000120 ac 00 00 00 00 f9 be b4 d9 d7 00 00 00 |.............|
0000012d
October 14, 2022, 08:39:03 AM
AFAIK they haven't broken the scrambling support in the code they copied from Bitcoin Core so their block files should be scrambled with some weak encryption that will prevent dumb scanning tools from finding things in them (we added that in bitcoin to prevent idiot anti-virus software from corrupting peoples blockchains when someone inserted some twentysome byte virus pattern in the chain).
I didn't know the blocks were scrambled in the (BTC) database. Can you post a link to the PR that added this?
Jump to: