Runes2.0 | Programmable Runes

[Runes2.0 | Programmable Runes @Runes_2]

Runes2.0 is coming - Bitcoin #Runes tokens are going to be programmable!

✅ Unlocking stablecoins, BTCfi, & more on Runes.
✅ No bridges, no L2s, no multisigs.
✅ No gas token, pure Bitcoin.

[Casey @rodarmor]

If I was redesigning inscriptions from scratch, I would seriously consider requiring all inscriptions to have at least one parent, linking them all into a huge, convoluted family tree.

[Leonidas 🧡 $DOG @LeonidasNFT]

Runes trading is going to get 1000x faster and cheaper

The things I have heard on calls over the past week are insane

Many of the solutions will work with your existing Xverse wallet

Runes devs are cracked

$DOG is going to be so easy to buy that it will make your head spin

[DANY #freedogofbitcoin🫶🏻🚀 @Danytoken]

Runes trading is going to get 1000x faster and cheaper

The things I have heard on calls over the past week are insane

Many of the solutions will work with your existing Xverse wallet

Runes devs are cracked

$DOG is going to be so easy to buy that it will make your head spin🚀🚀🚀

[Casey @rodarmor]

ord 0.22.0 is out!

This is a nice release, with a bunch of new features. Let's dive in. 🧵

https://t.co/dUXxIlwzbh

[Casey @rodarmor]

This isn't actually correct: you cannot front-run a runes etching.

Runes uses a commit/reveal scheme, where in a valid etching transaction must also spend an input which includes, in its witness, a commitment to the rune's name, and that commitment output must have at least six confirmations as of the etching transaction.

So, even if you see an etching in the mempool, you would have to broadcast a new commitment, get that mined, wait five blocks, and then get your etching mined, all before the original etching transaction is mined.

[Casey @rodarmor]

Rune protocol messages fit easily in OP_RETVRNs because runes relies entirely on bitcoin core for authorization and authentication, so only the semantics of the transaction have to be encoded, i.e., what the transaction is doing, not whether it's allowed to do it.

[Leonidas 🧡 $DOG @LeonidasNFT]

OFFICIAL STATEMENT FROM @RODARMOR: "Casey will only hardcode the one first Rune and it's already in the codebase and it's UNCOMMON•GOODS no ten Runes... take that to the bank and smoke it"

[Bankless @Bankless]

LIVE NOW - Runes: The Frontier of Bitcoin

w/ Casey @rodarmor

Casey is the creator of the Ordinals Protocol, a harmless protocol that simply allowed for arbitrary data to be inscribed into individual Bitcoin UTXOs, creating Bitcoin NFTs

He is now also the creators of Runes, a new protocol, working to bring fungible tokens to Bitcoin and which stands to fundamentally change the Bitcoin ecosystem

0:00 Intro
5:00 The Guy Who Changed Bitcoin
10:21 Why Casey’s Building
16:45 Ordinals Cultural Shift
22:43 Runes
31:40 The Ord Standard
45:27 Bitcoin Blocks & Blockspace Limit
57:47 Bitcoin Innovation Implications
1:02:41 Rune Parameters
1:11:20 The First Runes (Uncommon Goods)
1:14:34 Timeline on Runes & Trading Ecosystem
1:17:12 The Future of Runes/Ordinals
1:19:48 The Bitcoin Renaissance
1:21:34 Winning Over Bitcoin Maximalists
1:23:45 Casey’s Podcast
1:24:58 Runes Team
1:26:37 Closing & Disclaimers

[Casey @rodarmor]

if the runes ecosystem marketcap doesn't hit one billion dollars within one month of launch i will commit seppuku

[Casey @rodarmor]

This was a pretty big release, and I'm very happy to finally have runes out the door!

[Casey @rodarmor]

Runes were built for degens and memecoins, but the protocol is simple, efficient, and secure. It is a legitimate competitor to Taproot Assets and RGB.

The protocol is self contained and has no dependencies on ordinals or inscriptions, making it extremely simple.

Balances are stored in UTXOs, which can be locked in HTLCs, so runes can be lifted on the lightning network.

Rune names are optional, and if an etching does not specify a name, a reserved name is allocated. Etchings of reserved names are unconditionally valid, and, if they don't have a supply-capped mint, are very light client friendly.

The ordinals library provides everything needed to encode and decode runestones, so integration should be straight forward.

I'm highly skeptical of "serious" tokens, but runes is without a doubt a "serious" token protocol.

https://t.co/bTKzQmnycW

[Casey @rodarmor]

I started work on an implementation of runes named Runestone.

Runestone will not recognize runes below a future block height, decided in well in advance and publicized widely.

I don't think there's any reason to rush an implementation, and there are subtle details of the protocol that deserve attention and consideration.

Obviously, everyone else is free to do whatever they want.

GLHF

https://t.co/HUfVIZ06Dz