RuneData

ord 0.18.1 is out! This is the last (lol it's probably not) release before the halving. github.com/ordinals/ord/rele… This release has crucial fixes and improvements, so absolutely upgrade: 1. github.com/ordinals/ord/comm… The first is a fix for a cheek-clappingly bad bug in the runes index, found by alexha123123 on GitHub. To etch a rune, you must first mine a transaction which commits to the rune being etched, followed by an etching transaction which spends the commit transaction output which commits to the rune. The commit transaction must have at least six confirmations as of the block in which the etching is mined. We were getting the number of confirmations from Bitcoin Core, but, if Bitcoin Core is ahead of ord, Bitcoin Core will report the number of confirmations the commit transaction has as of Bitcoin Core's block height, which will be larger than the number confirmations it actually had as of the etching transaction block. 2. github.com/ordinals/ord/comm… The second is the addition of the turbo flag, which is set, or not, when a rune is etched. Why set this flag? There are features we'd like to add to runes in the future which must be opt-in on an individual rune basis. This might be because they preclude other desirable things, for example, increasing light client validation costs, or simply because they are too degenerate, for example, an ongoing biweekly global lottery. If you set the turbo flag you are opting in to whatever preposterous ideas we cook up. UNCOMMON•GOODS is turbo, natch. 3. github.com/ordinals/ord/comm… We fixed an off-by-one error in the wallet which would cause ord to wait one more block than necessary for a rune commitment to mature. You might notice that these commits all have comments, all because @t4t5 cornered me at a party in New York and made me promise to write commit comments.