Today's #Bitcoin# Cartoon: Chain Splits. "Blake 2b...or not Blake 2b. That is the question." - @miketwenty1 I want to thank @w_s_bitcoin, @coinjoined, @bitcoin_bugle and @MrHodl for the memes and X spaces that inspired this cartoon! #bip110#

EntropyLab had a pile of updates in the last 24 hours. Here are couple I'm most excited about PSBT editor now draws the spend like mempool does.. one box per input, one box per output. Amount. Address. Signed or not. Tap a box, edit that field. rust bitcoin checks the file before it hands it back. Global sync is in too. One checkbox, off by default. Turn it on and the lab keeps dice, cards, number bases, seed words, and keys talking to each other as you type. Enough bits land, the next character appears. Hashed inputs can fill the rest. Edits in the other direction never overwrite a hashed source. This one is my favorite.. Vanity grinding should merge later today. Same offline HTML file. You pick a prefix. The lab walks the keyspace on CPU, or GPU if the browser has WebGPU. Regular addresses and Silent Payments. Default is a calculator: hash a salt, add a counter, same salt always replays the same key. No RNG for the private key. Nothing leaves the page. Don't ever use it for real Bitcoin. Educational purpose only!

One week old today. What EntropyLab already did: • Dice, coins, cards, hex, or binary → seed • Dice methods: hash the rolls, BitBox-style, Ian Coleman / Keystone, D++ D8/D16 • Live die-fairness check while you enter rolls • Seed phrase, xprv/xpub, WIF, hex key, Casascius minikey • Optional passphrase • All five BIP39 lengths: 12, 15, 18, 21, 24 • BIP39 seed, xpubs, fingerprints, descriptors, Bitcoin Core wallet.dat export • LifeHash next to each fingerprint so two keys are not easy to mix up • Legacy, nested SegWit, native SegWit, Taproot • Mainnet and testnet • Watch-only multisig from xpubs. No private keys required • Recovery sheet you can save or print • PSBT inspect: where it sends, amounts, fee, signed or not • Same inspector accepts a fully signed raw transaction • Labels outputs as change, receive, or not in this wallet when a session key is loaded • Finds inscription envelopes in tap-leaf scripts and witnesses (`OP_FALSE OP_IF "ord"`). Reports content-type, size, and a text preview. It does not number sats, fetch the chain, create inscriptions, or render images. • ECDSA nonce reuse check • Optional RFC 6979 check with a key that stays in RAM for that session only • Jade anti-exfil transcript check without a key What we added in the last two days: • BIP-85 child entropy from the parent you supply. Same parent, application, and index always reproduce the same child. Matches COLDCARD. Calculator, not a generator. • Silent Payments (BIP-352): reusable `sp1q` / `tsp1q` addresses, labeled codes, BIP-392 `spscan` / `spspend` descriptors, sender taproot outputs from pasted vin JSON, receiver check of pasted x-only outputs. It does not connect to a node or scan the chain. • Decodes OP_RETURN size and a text/hex preview. It does not create OP_RETURN outputs. • All Bitcoin math now runs on rust-bitcoin in WASM. Same library family Bitcoin Core uses. The HTML no longer ships a JS crypto stack. It still does not generate entropy. • Real PSBT editor. Open a PSBT, see every field, change a field, export only if rust-bitcoin accepts the file. It does not sign. It does not go online. • Pick the derivation scheme instead of hoping the tool guessed BIP84. BIP44 / 49 / 84 / 86 / 48, or type the path yourself. • PSBT inspect now reads Taproot script-path spends, UR crypto-psbt payloads, BitBox anti-klepto transcripts (not Jade), and reused Schnorr nonces. Reused nonce is the alarm. RFC 6979 mismatch is not. • Taproot multisig starts on BIP87, the co-signer account standard — not BIP86. A pasted BIP87 xpub no longer silently flips you to legacy P2SH. • After it is done with a seed or key, it wipes those buffers. Strings in the page are still strings. Download the file. Verify it. Open it on a machine that never goes online. This tool is for a Bitcoin power user which was only possible because of token maxen. #OogaBooga#

Who’d be interested in a limited-edition “Seed Round” of EntropyLab merch to help fund our clankers for the next few weeks/months? I’m thinking a small run of a few different items...just 21 of each, individually numbered and tastefully branded with the EntropyLab logo. Each piece would be marked: Seed Round · x/21

I have many thoughts on this. As a lead maintainer of a project that has many contributors receiving grants, I take this responsibility extremely seriously. Every grant is a huge amount of trust that these organizations put on our project and I see my primary role as the mediator of that trust. I have seen many contributors come and go. Some have managed to get grants without producing anything worthwhile after years of larping on a side project that has almost zero impact. Others have produced immense value, without any grant at all. This has multiple risks and negative consequences: - Trust: We as a project risk losing the trust of organizations that want to support us. I regard every grantee as a potential liability. If you mess up, we as a project suffer more from it than you do. We might be better off without your minimal contributions. - Internal conflicts: People in the team know exactly who produces value and who pretends to be busy with pet projects. Seeing someone get a big grant for a worthless hobby project, or just producing a fraction of the output than someone else, hurts internal harmony. We have a high bar for excellence. Either you give your best, or you have to go somewhere else. - Stasis: Grants can feel like "easy money". Some people just kick back and enjoy, work 2 days a week for a full time salary someone else would kill for. This is deeply unfair and hurts the project, since there might be other folks that could've done a much better job if they received your grant. Open source work on the internet is a global market. There could be way more talented, more ambitious, more motivated people out there who would do a better job. If you work for in the industry, that company will have to constantly evaluate whether its worth keeping you whether it'd be better to replace you with a more productive developer. In most of the grant ecosystem, there is hardly any feedback between the grant renewal periods. This is why I take my job extremely seriously. I value the trust of the organizations who support Cashu more than anything else. My promise to them that my highest objective is to make sure their resources and their trust are used in the best possible way. This is good for us as a project, and good for the funding organizations as well. It is also good for the grantees, even if it sometimes feels harsh. If you get used to being a lazy dev with easy grant money, your career will be over as soon as you lose that privilege. There is no place for slackers in our team. We have no time for lazy people working on pet rock projects. If you don't show up every day, work at least as much as someone with a comparable salary in the industry, I will go back to the org that funds you and let them know about it. My team knows this. Our funders know this. Work hard or go find a different job.

I wasn’t in the right state of mind when I posted this morning. I’m feeling better now and not nearly as paranoid...that being said, I’ll still be migrating away from Coldcard and putting their products in a Faraday box out in my shed. I’m just not in some panicked fervor to move everything into a different wallet ASAP anymore. I’m going to take my time and be extremely safe and methodical so I don’t lose any bitcoin in the process.

BIP-110 doesn’t end the cat and mouse game. It rewards it. Restrict one type of spam and it just makes it more “rare” while spammers find an easy workaround using techniques that aren’t temporarily blocked. As retarded as it sounds, they love knowing they baited y’all into attempting a consensus change…especially one that either doesn’t stop them (e.g. runes) or that they’ve already bypassed. 💀 You’re not beating them at that game. You’re volunteering to play it and with no chance of winning.