PSA: Get your Bitcoin off any exchange supporting "BSV" (due to insolvency risk)

[pooya87]

I mean, obviously the license is complete nonsense since the code he is trying to license was not written by him and was instead plagiarized/stolen from Satoshi and other real bitcoin devs, but that wouldn't stop him from trying I'm sure.

The scammers are good at abusing the law. Technically it is not stealing to redistribute software released under MIT license with a new license as long as you include the original license, which they do.

[1715184869]

1715184869

[1715184869]

1715184869

[1715184869]

1715184869

[davis196]

Who the hell is using BSV in 2022? Pump and dump altcoin traders?
Yes, we already know that BSV is complete garbage and Craig Wright isn't Satoshi, but who the hell would use a centralized shitcoin blockchain that would eventually steal your coins? This doesn't make any sense. Are there any people, who believe that BSV is the real Bitcoin?
I'm glad that I don't use the crypto exchanges in your list. I used HitBTC a few years ago, but my account there is dormant for years.
Yobit being on this list is no surprise to me. The ultimate shitcoin crypto scam exchange.
Any crypto exchange supporting shitcoins trading should be instant red flag for every cryptocurrency trader.
I'm sure that almost all legit crypto exchanges will delist and remove BSV sooner or later. The exchanges that keep BSV and other shitcoins would simply prove that they are crypto scams.

[worle1bm]

• Bitfinex

Are you crazy? This is a top exchange

The other exchanges like Binance are also top one in terms of volume but he's actually concerned about your funds over these exchanges due to scam coin BSV but accepted the same from you as you are already promoting it so you will find others suggestions inappropriate in this matter but you will see once it happens with you and believing in this scam coin and faketoshi.

[ABCbits]

Do you know what's funny about this? We could literally find 20 people in this forum who are willing to buy 7TB of HDD space to spin up BSV nodes and vote against Craig's 9 nodes. It would be great, just showing that it is this easy to attack a not properly decentralized blockchain.

Are you by any chance one of those people? 
It's pure waste of time and resources, but why not create such campaign, when he can spend all that time spreading toxicity and lawsuits worldwide.

I am one of those people willing to do this experiment, yes!

You have read system requirement to run BSV node[1], right? To run node which can keep up with latest block, you need 8C/16T CPU, 64GB RAM and 100Mbit internet connection. I don't know how to find cheap VPS, but on Linode[2] it costs $320/month (Linode 64 GB shared CPU) + $200/month (10 TB S3 storage, unless you use prune mode). You might as well as burn your money.

Who the hell is using BSV in 2022? Pump and dump altcoin traders?

Some time ago, certain weather app store their data on BSV blockchain[3].

[1] https://web.archive.org/web/20221009092610/https://node.bitcoinsv.io/sv-node/system-requirements
[2] https://www.linode.com/pricing/
[3] https://bitcoinist.com/96-of-bitcoin-sv-transactions-come-from-a-weather-app-report/

[BlackHatCoiner]

Do you know what's funny about this? We could literally find 20 people in this forum who are willing to buy 7TB of HDD space to spin up BSV nodes and vote against Craig's 9 nodes. It would be great, just showing that it is this easy to attack a not properly decentralized blockchain.

No reason to do the experiment. Someone else caught up with you, and accomplished a 51% attack with 100 blocks deep reorg. Absolutely nothing happened, because there's absolutely no decentralization, no immutability and no integrity behind this clown show in the first place. There was no change even in the price. BSV-ers simply don't care; it's all about what Craig tells them.

Craig's perspective is BSV's consensus mechanism.

[n0nce]

Ah you should be aware that the BSV chain is reported to contain child porn.  Not just some old non-working onion urls or whatever, but actual full on child porn due to its operators facilitating file upload and encouraging its use to bloat the chain.
[...]

Okayyy, that's really fucked up. Thanks for the heads-up! This literally changes everything. It even makes me wonder whether it's intentional; seems after all the steps they've taken to disincentivize node operators (mostly financially), it's all pretty calculated.
Even if I don't get into legal trouble and I do have access to powerful enough hardware, I will never provide infrastructure for (and store) such materials.
What started out as a funny little 'blockchain attack' idea, actually turned dark real quick here.

I am one of those people willing to do this experiment, yes!

You have read system requirement to run BSV node[1], right? To run node which can keep up with latest block, you need 8C/16T CPU, 64GB RAM and 100Mbit internet connection. I don't know how to find cheap VPS, but on Linode[2] it costs $320/month (Linode 64 GB shared CPU) + $200/month (10 TB S3 storage, unless you use prune mode). You might as well as burn your money.
[...]

I know; it's CSW's way of financially disincentivizing (obviously altruistic) node operators and making the blockchain more centralized. Personally, access to such hardware would be no problem for me, since I don't need to rent it. But as mentioned above, I now declare this idea as 'discarded'. Maybe we can demonstrate on another, 'centralized' blockchain what the consequences of having few nodes can be. But that's a different topic.

Do you know what's funny about this? We could literally find 20 people in this forum who are willing to buy 7TB of HDD space to spin up BSV nodes and vote against Craig's 9 nodes. It would be great, just showing that it is this easy to attack a not properly decentralized blockchain.

No reason to do the experiment. Someone else caught up with you, and accomplished a 51% attack with 100 blocks deep reorg. Absolutely nothing happened, because there's absolutely no decentralization, no immutability and no integrity behind this clown show in the first place. There was no change even in the price. BSV-ers simply don't care; it's all about what Craig tells them.

Craig's perspective is BSV's consensus mechanism.

That's amazing! I think I missed that. It's hilarious though, how the 'BSV Association' then tried to replace PoW with 'Proof of Authority' by asking node operators to reject the longest chain. I hope the attackers succeeded and got away with a good amount of BSV which they immediately market-dumped.

However, what I hoped to be able to achieve is not only show such attacks are easy when you have 9 nodes, but also to stop CSW in his endeavors of introducing massive changes into the BSV blockchain, granting him however many coins and such. Not for protecting BSV holders or anything, just to make him a little bit upset.
That would require setting up a bunch of nodes and just leaving them running without updating them with any such code changes.

But again, idea scrapped.

[o_e_l_e_o]

Who the hell is using BSV in 2022? Pump and dump altcoin traders?

CSW, his immediate family, Calvin Ayre, the people they employ at CoinGeek (although I'm sure there will be at least a few who dump any BSV they receive immediately for bitcoin), scammers, and idiots. Remember that there are people willingly using Bitconnect 2.0 and Terra Luna 2.0. There are no shortages of idiots to whom to sell a shitcoin.

Yes, we already know that BSV is complete garbage and Craig Wright isn't Satoshi, but who the hell would use a centralized shitcoin blockchain that would eventually steal your coins? This doesn't make any sense.

Most stablecoins are centralized and can arbitrary steal/freeze your coins, and yet have volumes of tens of billions of dollars.

It's hilarious though, how the 'BSV Association' then tried to replace PoW with 'Proof of Authority' by asking node operators to reject the longest chain.

Oh, and don't forget that Ayre reported the actual longest chain to the police: https://nitter.it/CalvinAyre/status/1422655123147399172

[DooMAD]

Okayyy, that's really fucked up. Thanks for the heads-up! This literally changes everything. It even makes me wonder whether it's intentional; seems after all the steps they've taken to disincentivize node operators (mostly financially), it's all pretty calculated.
Even if I don't get into legal trouble and I do have access to powerful enough hardware, I will never provide infrastructure for (and store) such materials.
What started out as a funny little 'blockchain attack' idea, actually turned dark real quick here.

Yeah.  To say that puts a bit of a downer on festivities would be an understatement, heh.  I've heard of security-through-obscurity, but never security-through-abhorrence.  Messing with SV has definitely fallen into the category of "if you lower yourself to that level, there's no coming back".  Where's the puke emoji when you need it? 

[pooya87]

No reason to do the experiment. Someone else caught up with you, and accomplished a 51% attack with 100 blocks deep reorg. Absolutely nothing happened, because there's absolutely no decentralization, no immutability and no integrity behind this clown show in the first place. There was no change even in the price. BSV-ers simply don't care; it's all about what Craig tells them.

Craig's perspective is BSV's consensus mechanism.

They should have done it to exchanges in order to force them to delist this scam coin.
Send a large amount of BSV to the exchange.
Sell it and withdraw the money.
51% attack and reverse the transaction.
Send a message to the exchange telling them you'd send the money back after they remove it

[o_e_l_e_o]

https://bitcoinsv.com/bitcoin-association-releases-mining-software-to-freeze-lost-or-stolen-bitcoin/

Here we go. The next step in the complete centralization of BSV.

‘Bitcoin Association and the broader BSV ecosystem do not believe that “code is law”. All the laws in the classical sense still apply to blockchain technology and therefore BSV. If someone has a valid right to digital assets but doesn’t have the technical means to access them, there should be a way to recover access to those assets,’ he said.

We know, of course, that this is completely consistent with what Satoshi said in the past: "Lost coins only make everyone else's coins worth slightly more.  Think of it as a donation to everyone, until the owner goes through the necessary legal system to force a centralized solution on miners to freeze these lost coins and then later return them to a different address, all without needing a private key or any other cryptographic proof.  After all, if there is one thing I've always loved, it is third parties having complete control over the entire blockchain."  

Can't wait for BSV miners (read: CSW and Ayre) to start freezing coins in various exchange wallets, and to see just how quickly an exchange will delist this trash when they find their assets being frozen against their will. Will be funny to see exchanges being on the receiving end of having their coins locked against their will for a change.

[gmaxwell]

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.

Take the following with a grain of salt because I don't read Chinese and haven't talked to a Chinese speaker yet.  It is apparently a Chinese mining pool that appears to have recently become BSV only.  According to its webpages it is approved by (or run by??) the Cyberspace Administration of China and claims that it's the only mining pool that can legally operate in china.

[gmaxwell]

Sorry for the double post but:


Wright's conspirators and employees will be holding a live-stream to explain Wright's plans to enable centralized coin theft on BSV, BCH, and Bitcoin by introducing a cryptographic backdoor will start and open for your questions at 2PM Eastern today (as in about 2 hours from now!).

https://www.youtube.com/watch?v=VKXOdTgPvfs

[o_e_l_e_o]

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?

On another note, lets hope this is the first of many exchanges to start seeing BSV for the scam that it is:

It appears that @WhiteBit Exchange quietly delisted BSV yesterday. For 24 hours there's no trading volume being reported anymore, the link to the public trading page is now re-routed to, oh irony, the BTC page and the Search page returns a "No results".

[n0nce]

Sorry for the double post but:


Wright's conspirators and employees will be holding a live-stream to explain Wright's plans to enable centralized coin theft on BSV, BCH, and Bitcoin by introducing a cryptographic backdoor will start and open for your questions at 2PM Eastern today (as in about 2 hours from now!).

https://www.youtube.com/watch?v=VKXOdTgPvfs

Basically, they repeated over and over that:
(1) You don't need keys; you just prove ownership in front of any court and get the coins.
(2) If a court rules that your coins actually belong to someone else, they will be forcibly transferred by BSV nodes and they actively work on that.

Completely invalidating 'Not your keys, not your Bitcoin' and questioning the whole existence of decentralized blockchains in the first place. Also obviously the completely opposite than what we read in the Bitcoin whitepaper.

[DaveF]

The question is how long until we see posts like this about BSV:

...
Dear STEX Trader,

The developers changed the code (fork) of the SUM project. According to the new SUM coin code, all transactions do not exist in the block explorer. The STEX does not support the transition to the new code leading to the loss of blocks. Therefore, in case the SUM coin developers team provide us with the old node that supports all lost blocks then withdrawals on STEX will be enabled. Currently, the communication between us and SUM coin developers team does not bring a positive outcome.

Please note that these actions characterize SUM as an exit scam project. In order to protect our users, we’ve decided to start the delisting procedure and stop any support of SUM coin on STEX.

Project info: www.sumcoin.org

Medium: medium.com/@sumcoinindex

STEX Team

I can see exchanges keeping it on so long as there is trade volume and they are making money. I have said it before and will say it again, that is what exchanges try to do, make money.  As soon as they see a coin as a real threat to that it is tossed.

Even if it was known to be a scam at the beginning they will still list something if they think they can make money on the trading fees.

But, there is a tipping point, if they think they can be really hurt by it, it's tossed like yesterdays trash. After all, once you list a coin the hard work is done, you just have to sit there and take the fees, shutting it off is just about no work at all.

-Dave

[NotFuzzyWarm]

...
Yeah.  To say that puts a bit of a downer on festivities would be an understatement, heh.  I've heard of security-through-obscurity, but never security-through-abhorrence.  Messing with SV has definitely fallen into the category of "if you lower yourself to that level, there's no coming back".  Where's the puke emoji when you need it?  

Ya mean like these?
I really hope there is a special spot in Hell for CSW and his cronies...

[NotATether]

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?

[n0nce]

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?

Same here; I always assumed the block format that is explained on https://learnmeabitcoin.com/technical/blkdat to be used without exception.
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).

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>

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:

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

[...]

[ABCbits]

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.

[n0nce]

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):

Code:

b12dcefd8f872536

An obfuscated value from the database will look something like this:

Code:

71a9e87d62de25953e189f706bcf59263f15de1bf6c893bda9b045

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:

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