lifofifo ◉
@lifofifo
Followers
29K
Following
59K
Media
1K
Statuses
13K
Founder @TheWizardsOfOrd
Mempool
Joined November 2019
We just created the largest OP_RETURN in Bitcoin history 🧙♂️ Introducing the first-ever 1 megger, Block 896696, which includes every single @TheWizardsOfOrd in OP_RETURN data. ➔ https://t.co/p5BEbKMRPB All 3,333 of them. Inscription #96032542, created in the same TX, shows
215
189
915
If you enjoy Ordinals, best thing you can do is own as much Bitcoin as you humanly can.
25
22
297
Yesterday, it was Bera and Blast. Today, it's Monad and Mega. Tomorrow, a fresh batch of VC-backed EVM horseshit. Through it all, Bitcoin remains Bitcoin. Grifters chase trends. If you're a serious builder, there's only one place to be. Bitcoin.
Yesterday, it was Sui, Aptos, Base, Blast. Today, it's Abstract, Bera, Monad. Tomorrow, a fresh batch of VC-backed L2 horseshit. Through it all, Bitcoin remains Bitcoin. Grifters chase trends. If you're a serious builder, there's only one place to be. Bitcoin.
52
63
348
@udiWertheimer Shout out to @Miami_flys for rescuing this wizard earlier!
1
0
6
Bitcoin File Sharing Network also supports RAID-4 storage for max protection. 📁Inscription 📁ANNEX 📁Control Block 📁OP_RETURN https://t.co/bINtiuoA2F Every Knots node will store 4 full copies of the file for no extra cost 🆓 Credits to @udiWertheimer for the RAID-4 idea!
58
37
267
If you're inscribing, don't be a bozo and least set the title attribute.
13
30
143
As Bitcoin is now a file sharing network, it's about time we have better tooling to upload files via OP_RETURN. ➔ https://t.co/sh9EQX4Smg Sub 1 sat/vB supported as well 🧙♂️
50
58
320
Inscription and gallery attributes support is now live on @TheWizardsOfOrd Inscriber 🧙♂️ ➔ https://t.co/iDiEPrNCEL You can also populate gallery attributes using the marketplace JSON file. Consider this experimental. Since galleries can get large, try inscribing sub-1 sat/vB.
I am most pleased to announce the release of ord 0.24.2*! https://t.co/CFQEi3CnNn This release expands structured metadata, which we hope can be used to finally move off-chain collections on-chain. More below! 🧵 *Please do not ask about 0.24.0 or 0.24.1.
22
23
164
I am most pleased to announce the release of ord 0.24.2*! https://t.co/CFQEi3CnNn This release expands structured metadata, which we hope can be used to finally move off-chain collections on-chain. More below! 🧵 *Please do not ask about 0.24.0 or 0.24.1.
github.com
👁🗨 Rare and exotic sats. Contribute to ordinals/ord development by creating an account on GitHub.
93
147
607
Surprisingly, there are only 11 TXs so far with annex data. Possibly because signing annex can be trickier. Here's some reference code for generating a TX with a JPEG in the annex. https://t.co/IRQJUwAlaN ✅ Witness Discount ✅ Contiguous ✅ Single TX ✅ Libre Relay AFAIK,
github.com
Contribute to lifofifoX/annex development by creating an account on GitHub.
Rule #4: "Witness stacks with a Taproot annex are invalid." So far, 11 transactions have attached an annex to taproot spends, mostly for jpegs. https://t.co/q9IcstecN9
4
8
40
Note: these on-chain BIP-Knotz futures are _not_ binary futures! They actually have _three_ possible outcomes. 1) Win 2) Lose 3) Chain Split In the third option, a hash power minority mines enough blocks that Knots splits off into a separate currency. In that circumstance,
We now have an on-chain BIP-444 futures contract! https://t.co/gSuFb7CSpD
@tclowdotsats, for some odd reason, decided to put his faith in BIP-444 activating, while I'm putting my sats on it being a dud. Setup includes sending funds to a 2-of-2 and two pre-signed (mutually
15
6
45
We now have an on-chain BIP-444 futures contract! https://t.co/gSuFb7CSpD
@tclowdotsats, for some odd reason, decided to put his faith in BIP-444 activating, while I'm putting my sats on it being a dud. Setup includes sending funds to a 2-of-2 and two pre-signed (mutually
Here's a different approach to BIP-444 futures using pre-signed transactions and larger OP_RETURN (300 bytes) for settlement, the most contentious aspect of this debate. https://t.co/vB6t00hq0z This should work well with https://t.co/wy8oxpaoeW + Xverse/Unisat. Shoutout to
14
37
127
Here's a different approach to BIP-444 futures using pre-signed transactions and larger OP_RETURN (300 bytes) for settlement, the most contentious aspect of this debate. https://t.co/vB6t00hq0z This should work well with https://t.co/wy8oxpaoeW + Xverse/Unisat. Shoutout to
github.com
Contribute to lifofifoX/bip444-contract development by creating an account on GitHub.
I have now fully open sourced the code which creates this on-chain BIP-444 futures contract! The contract starts with an atomic deposit into the contract address of 1 BTC each (to make sure both parties put in the same amount into the contract address). Context: BIP-444 makes
8
8
80
2
1
23
Rest are at height 1470069 If someone wants to make this more approachable, check out
10
11
77
Hal Finney invented the first Bitcoin metaprotocol 🤯 OP_NOP1 ➔ OP_PUSHDATA ➔ OP_DROP is conceptually very similar to how inscription envelopes work. "Overlay aware code" is basically describing the ord indexer. GM ☀️
62
100
459