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. docs.rs/ordinals/0.0.5…
@rodarmor > if an etching does not specify a name, a reserved name is allocated does it mean they will be given a random name?
@rodarmor Any more thought on the orderbook issues with PSBTs? Would be ideal to have that ability somehow but might require some thinking on how to do that.
@rodarmor docs are looking majestic. code is looking beautiful
@rodarmor Are there readings on the difference between those protocols?
@rodarmor Excited for niggolas cages redemption on runes
@rodarmor I'm so fucking bullish right now on @AI_Rune and @LeonidasNFT Thank you @rodarmor for the hard work and innovative protocols!
@rodarmor I was already bullish 🚀 Now im straight melting 🫠 Send runes 🫶