hahaha don't tell them it's an AltCoin - Luke still claims that "core forked off" and that he is maintaining the "real Bitcoin"

I am sure we will have some memes soon of Luke stating how the forums have now attacked Bitcoin by closing the thread and "incorrectly" calling the "real" Bitcoin an altcoin. Will claim it is an attack on their value.

At the time of writing, not yet, but they may block 1-of-15 multisig, used by bitfiles, when they will merge this change: https://github.com/bitcoinknots/bitcoin/pull/422

Note that you don't have to trust them in any way, when it comes to your private keys. You upload files first, then download JSON recovery files, and then you can do with them whatever you want, for example upload it manually, without using this website at all.

For example, let's assume, that I would want to upload some text file. I can try to upload it first, and download this JSON:
And then, I can do anything I want. First, I can make sure, that my file is not too big, and it is encoded properly. Then, I can make sure, that I can control the address, where I would want to send some dust. And also, I can skip this website completely, grab that data, and push it by myself, entirely outside bitfiles, and then, it will be indexed, and displayed later. Another thing is if you know the encoding, then you can also replace their keys with your own ones, then it is fully trustless, and can be done, without "sending" coins to another place: you can simply point at any existing address under your control, and modify that data accordingly.

Which also means, that pushing data can be outsourced. You can prepare everything upfront, browse your transactions offline, and only push them, when you are sure, that you know, what are you doing. Another thing is you can run Knots node offline, point it at regtest, and see, if it is still valid in their current consensus, before actually sending anything.

It is already there, because they keep hosting the first 961,639 blocks for absolutely no reason: https://mempool.guide/tx/0bfd399a28127e569985a52bd1bcc2f82951582e26db18753d52638041b4d2f0

Also, their chain has some older images, compatible with bitfiles, long before that website was even coded, but they are just not displayed by default: https://bitfiles.io/btcb2/bae7f2ef77b2083b6aff095583cc7562cdda9f12cc9d1381953352af75d60812

In general, if they changed block headers through hard-fork, and they consider SHA-256 to be "captured", then they have no reason to keep old block headers anyway. If they would be serious about it, then they would for example introduce OP_BLAKE inside Script, and deprecate OP_SHA256, OP_HASH256, OP_HASH160, and so on, because it contains SHA-256. They wouldn't use SHA-256 in merkle trees, signatures, checksums, and anywhere else.

They are wrong here, because the only reason, why they keep the first 961,639 blocks, is because they are lazy. Reorging beyond that point would make their whole chain obsolete. And if they need old data for any reason, then they should re-hash it with Blake, just as Satoshi described.

Where is it? Where can I see Blake hashes for historical blocks?

No

I don't forsee anyone wasting their time with trying to both me about it, they can spend about 2 minutes researching how that's going to go.

We run a BUFU exchange.


We almost named it BJr (Bcash Jr).  Really, an exchange can name anything they want and then it's a battle of customer support tickets if you stray too far.  If you have more pull than the other service, then they start getting support tickets.

It's really just a war of support tickets, but thus far... no confusion or complaints.

I know. But re-publishing same NSFW/disturbing content on newer TX after BIP 110 is activated may annoy them, especially if you add provocative text/message to it. But i won't do it myself since it's waste of time and i don't want to see that NSFW/disturbing content ever again.


Good for you, they probably have wasted enough energy and time harassing neoxa.

Ok, so somebody here is either playing innocent while crapping on blake chain or there is somebody lurking around reading the topic and deciding to do the stuff we discuss


So this was early morning on 26th....
The same file was broadcast and added to a block on Blake 2026-09-26 15:02:17:
https://mempool.guide/tx/7690b398fe92a6aacfe65b639f14f274733df205d61e06f9424e7744c313a6e5
1-hour difference between forum time and mempool, 1 hour between broadcast and confirmation, so 2-3 hours after the message was posted...
Common, this is no coincidence!

Who did it!?!?!? 

I also haven't seen anything about it on any other places (other forums or social media), that's one of the reason I mentioned the echo chamber. ^.^

There are of course other issues too, I'd say the two major ones are:
- Lack of an easy-to-use tool to claim the "airdrop". In comparison to BCash, there is no lightweight wallet that users an use. BCash guys quickly created a fork of Electrum which is a very easy to use tool. So how does one claim BLuke? Download and run Knots which is a full node? That ain't gonna happen with 99.99% of people.

- Lack of exchanges to trade it. Someone who is KYC'd on for example Binance is not going to sign up on some new exchange (usually with no volume) just to sell an airdrop to a thin orderbook that would crash if he did.

Of course this user: https://bitcointalk.org/index.php?action=profile;u=3751337

It is not that hard to see deleted posts, indexed by bitcointalk crawlers: https://bitlist.co/post/67182178

Yeah, he complained about bitfiles being buggy, but at that time, his transaction was already hanging as unconfirmed. Which means maybe he got errors like "too-long-mempool-chain", but somehow the transaction was pushed anyway. And maybe he thought, that it failed, so did it again, but this time with a lower quality. Anyway, it seems bitfiles indexed all of his attempts.

By making BIP-110-incompatible transaction, in any way: https://bt.irlbtc.com/view/5590674.msg67025339#msg67025339

Of course, using P2PK is not the only option, there are many others. And some people did it faster, than me: https://mempool.space/tx/fd1a2b41fbae10adfcc44b0e3e6d6a4ff8679ac86f1da1386a0ff2263522143e

I did everything from Bitcoin Core, without having full access to the chain. My node is still downloading new blocks, and is still somewhere at 80%. Maybe after a few more weeks, I will finally have the whole chain, I am syncing since June 2026 or so.

One of the funny things I can see, is some connections from Knots, hanging at block number 961,639.

Not only that. There are some exchanges, which support it now, but didn't support it then. Which means it was possible to sell some BIP-110 coins back then, withdraw some BTCs, and get yet another airdrop of BIP-110 coins, out of that exchange, and repeat the same cycle multiple times, as long as that exchange had enough unsplitted coins, to be worth it.

But usually, it was not a big difference, at least for me, because BIP-110 price was too low, and deposit/withdraw fees were too high, to make any profits out of repeating that cycle.

Also, people could mine more coins, than they could get from "having BTCs", which is yet another reason, why that coin failed, and now the community is trying to "fix" it somehow, by preventing miners from spending some of their coins. But there are workarounds, and for example CTRLpool deployed "Stratum 2 Datum converter" to unlock their coins, and just slightly changed the format of their blocks, to still be compatible with stratum v1: https://x.com/CTRLpool/status/2103242037378142467

Huh? I wouldn't know about bitfiles at all, if I wouldn't read it on X. So, it was mentioned there earlier: https://x.com/devinsellerz/status/2099834649379831960

I never thought that there would be deleted posts when I check the topic, and...why was that deleted anyhow?


I guess anyone there from the guys that know are afraid to mention it since it will indeed break their own bubble.
And if it's somebody from the outside, it was probably banned instantly, speaking of:


Much freedom, such punishment, wow what a madness!

Looking at their blocks, I realized something funny, so Luke is against spam, against useless transactions, such as SatoshiDice, but their whole method of decentralized payments for coinbase rewards they are trying to make mandatory is just creating spam. That lonely block in the corner is their coinbase reward:


Since every miner gets paid in every block, of course at the end of the day a miner from a bigger pool will have 30-40 outputs, which he will consolidate, multiply this by 100 miners, and you get 3-4k of tx space wasted every day!

Browsing around:
https://mempool.guide/tx/ab8cee20c45a193fb028b5a7ad302282164427dc663cb5da0a186624cffe4de1
Block: ‎97.99 kB. That tx alone: 6.07 kb