Casey Rodarmor

This is unfortunately something I can't change in a PR, I think it can only be changed by a repository owner. It's this space:

We could consider using a prefix varint, where the number of leading 1s in the initial and subsequent bytes, until a 0 is reached, determines how many additional bytes follow....

I notice that there's no maximum varint size mentioned. Would it be a good idea to restrict varints to being no greater than one of `{u32, u64, u128}::MAX`? (Which one...

@arik-so means that if you etch a reserved rune, you can still include a spacers field, which will put spacers into the reserved rune's name. Reserved rune names are automatically...

> An RFC isn't the best tool to jumpstart progress but instead engaging with the issue is. If there is enough to move forward, i then recommend using Internals wxth...

> From what I can tell, the behavior didn't change in 1.37. From the [linked issue](https://github.com/rust-lang/cargo/issues/7169): I believe the change in behavior was to `cargo install `, i.e., installing from...

> At the moment, we could only do 130x4 declining mints immediately after deployment. Problem is: the total supply would immediately exist from a regulatory / legal / tax PoV,...

Also, what is the specific issuance schedule want to implement? I'm curious if it's deterministic or discretionary.

There are actually already rarity colors. Check out the /sat pages for different rarity sats. They're based on classic Diablo/WoW loot colors.

Thank you Luke, I appreciate it. Users have already begun financially relying on the details of ordinals, so I think at least for clarity it should be a BIP. A...