Casey Rodarmor
Casey Rodarmor
Take advantage of the commit/reveal structure to avoid sniping. If the index sees: - Commit A with name X - Commit B with name X - Reveal B with name...
> Thoughts on this proposed [Bitcoin Ordinals DID Method Specification](https://github.com/ordinalsreserve/btco/blob/main/spec.md#bitcoin-ordinals-did-method-specification-v0051)? Unfortunately I'm pretty bandwidth constrained just thinking about and trying to get back working on the core inscription protocol, so...
@tyjvazum These are all good points. I think the ideal solution would be to allow names of any length, with the restriction that names less than the more recently mined...
I think I'm inclined not to do this, for a number of reasons: - Miners can take desirable new symbols, even if users bid a high fee for them. -...
> is there a specific way to upgrade the db or should we just index it again from block 1? Yup, just delete the db and re-run ord.
@rot13maxi Yah, that's right. One complication is that the envelope header expects only single data pushes for field values, and a single data push is limited by taproot to 520...
@batcavekid The filename might be something random or weird, and people might not realize that they're including it in an inscription. The title might also contain spaces, slashes, or other...
I think this is covered by metadata.
@haribosan The main issue with multiple inscriptions in a single UTXO is that the wallet can only currently deal with one inscription per UTXO. It's a simplifying assumption that makes...