Joined January 2019
BIP-39 maps 11 bits per word. A 12-word seed encodes 128 bits of entropy. A 24-word seed encodes 256 bits. The extra 128 bits do not reach the private key in any meaningful way, because Bitcoin private keys have a security level of 128 bits regardless of seed length. The ECDSA curve order is 256 bits, but brute-forcing a Bitcoin address via RIPEMD-160 collapses that to 160-bit preimage space, and the actual attack surface against a secp256k1 key sits at roughly 128 bits of effective security.
14
12
6
152
60,382
xpub retweeted
Only 10,000 people on planet Earth can own 100 Bitmaps.
1
1
70
xpub retweeted
📙 you can now build a full bitmap index on-chain with the LiveOCI dashboard 📚 [Local Indexing] tab: pulls inscription IDs, u can also enable images, blocktributes, sats etc 🔎 use [Compare] tab to diff check an outside index (.csv or json) 🔗ordinals.com/content/0c1d5fb…
11
34
6
90
4,303
xpub retweeted
🟧 bitmap LiveOCI (live on-chain indexer) 🧪alpha > get any bitmap inscription ID or sat, up to the latest block import from js module: 🔗ordinals.com/content/0c18b83… const id = await getBitmapInscriptionId(blockheight) or const sat = await getBitmapSat(blockheight) more info 👇
13
26
8
70
5,688
Ultra high resolution image files embedded contiguously in BIP110-valid txs? No problem. -No Inscriptions-style decoding -Doesn't use Taproot -Knots policy standard -Cheaper than Inscriptions (fee/quality) -4x cheaper than OP_RETURN Introducing JXL-n-hide.
74
52
70
339
150,501
BIP110 taketh away OP_IF, but giveth OP_PLENTY. Introducing a novel way to encode arbitrary data in *contiguous* bytes. Up to 2MB fully BIP110 compliant. OP_PLENTY encodes each 4 bit nibble of the raw data into a tapscript opcode. Decoding is trivial: take the opcode mod 22.
41
48
51
286
150,122
Replying to @ScarcityMan
The issue is that all of that data still winds up in Bitcoin. Op return isn’t even the cheapest place to put it, it’s just historically the least harmful place to put it (that’s why it exists). All of this fork discussion is basically a debate about which bucket to put spam into, since there isn’t a proposal on the table to materially reduce spam or materially increase the cost of the cheapest method to spam. That’s why I didn’t bother to talk about it over the past year. And I’d see tweets regularly tagging me asking why I’m not talking about it, people claiming it’s the biggest thing and I’m not talking about it (it’s not the biggest thing. I had little reason to talk about a fork with low consensus that doesn’t materially reduce spam.) I have people emailing asking me if Bitcoin is going to die if a fork that just mildly re-arranges where spam goes doesn’t pass (because they somehow think it stops spam, and its leading proponents have called spam an emergency in need of a rapid fix). Then I’m asked about it on a podcast. So I explained that it’s not an emergency, the fork doesn’t materially stop spam, it comes with some trade-offs, bitcoin is fine, it’s always worth exploring ways to optimize bitcoin for the future, etc. Then I get dozens of replies from fork proponents asking if I’m compromised, why do I like spam, why don’t I want to stop spam, etc. Most of them (not all) have playground-grade ad hominems attached as well. It’s mostly not their fault though; they’ve been whipped into a frenzy by people saying if they don’t pass this fork then bitcoin dies. I support people trying to fork if they want to. Bitcoin needs market tests once in a while. But if people ask me my opinion about this fork’s technical merits, the marketing around it, or its probability of becoming consensus, I’ll give my opinion.
95
101
29
1,239
115,117
Trading is now live on ◉RD ord.net For now, we only have listing and buying. But this is just the beginning. There's more to come. Stay tuned 🧙‍♂️
161
308
50
1,009
88,194
xpub retweeted
A straightforward proposal to inscribe BIP47 payment codes onto Bitcoin using Ordinals, creating a decentralised, censorship-resistant directory that anyone can write to and verify. ~$300 for the entire known database. No servers to seize. bip47db.github.io/
28
50
12
184
45,080
Quantum-Safe Bitcoin Transactions Without Softforks github.com/avihu28/Quantum-S…
244
666
289
3,413
2,020,966
New drop on bitmap.trade 🟧 Wallet Connect is now live on bitmap.trade 🟧 🔗 Connect via Xverse or Unisat 👤 Your own Profile Page 📊 Full portfolio view — every bitmap you own 💼 Link multiple wallets to one portfolio ✏️ Name your wallets 🔗 Share your portfolio with anyone Every Bitcoin block is a bitmap. Now you can prove which ones are yours 🟧🟧🟧 Go connect 👉 bitmap.trade/profile
Public Launch Announcement 📢 🟧 bitmap.trade explorer is now live for public You can now browse, search, and filter every bitmap on-chain on bitmap.trade Explore by block number, collection, rarity, or type. View full metadata — tx count, block size, traits, owner, child inscriptions all pulled directly from the chain. Visualize ANY bitmap in its original form — now with native 3D rendering 💖 and much more 🟧🟧🟧 Trading 🔜
8
36
2
92
5,371
xpub retweeted
Replying to @adam3us
I usually don't bother saying this, but spam is something sent from A to B that B doesn't want to receive. Spam is not something sent from A to B, where A wants to send it, B wants to receive it, and C doesn't want it to exist.
86
197
17
918
35,716
Binohash: Transaction Introspection Without Softforks A first transaction has been mined demonstrating a limited form of covenants using only existing Bitcoin script functions. This development potentially eliminates the need for a Bitcoin light client in BitVM bridges, simplifying the construction and improving security. We hope this development furthers research on the possibility of creating introspection and covenants-style functionality on Bitcoin without the need for softforks, and advances discussions on the usability of covenants in Bitcoin and the use-cases they enable. Many thanks to everyone at @idealgroup, as well as @PortlandHODL and the Slipstream team at @MARA for patching their nodes to mine these wacky transactions. Full paper in the comments 👇
45
76
43
341
75,053
xpub retweeted
BREAKING: Future Natcats supply will now be automatically distributed directly to Natcats holders. Excited to announce P2P Perpetual Distribution. This update ensures full decentralization and fair distribution of the @dmtnatcats collection over the years to come.
As of Bitcoin block 919296, all future Natcats supply will be automatically issued to Natcats holders through an on-chain decentralized distribution system. Natcats will enable P2P Perpetual Distribution, a Bitcoin-native mechanism developed by @evonbit. 🧵👇
22
40
8
167
12,023
As of Bitcoin block 919296, all future Natcats supply will be automatically issued to Natcats holders through an on-chain decentralized distribution system. Natcats will enable P2P Perpetual Distribution, a Bitcoin-native mechanism developed by @evonbit. 🧵👇
59
85
26
262
41,637
team still here?
25
12
1
105
2,428
9btc.mp3
35
52
10
157
8,166
Bitcoin's cats 🟧
9
38
3
177
5,678
welcome to the daily weird
26
38
6
158
6,603
Stack cats 🟩
14
20
2
146
2,995