Remember to duck, beware of the tail rotor even if it's a Fenestron, and don't climb too high prior to reaching ETL!
With the /r/inscription and /r/tx recursive endpoints, you could theoretically enforce a commission by disabling the inscription unless the latest tx has an output paying a minimum fee. You could even trace the entire transaction chain all the way to the revelation.
Dev Aloft retweeted
Chisel New Feature Highlights
1. Customizability
Besides adding metadata, you can now set the title and traits for each inscription, immediately burn it, or unbind it from the mortal sphere of ordinals altogether (it will not be bound to any satoshi, essentially a public good.)
In the @chiselxyz server logs, every once in a while I would notice a request for several thousand inscriptions, typically 5-10,000, that would take a very long time to process. I rewrote the opportunistic batching algorithm, and it should now be on the order of 1-300 ms.
I found your message! It was hidden in the Chisel Twitter account's message requests, even though I had disabled the filter and set it to auto-accept requests from everyone. I have a bunch of very old support requests to go through now, thank you so much for letting me know!
That's very kind, but I can definitely see a message getting drowned out across the various channels, especially with how spammy email is, and that should never happen. Perhaps I should streamline support to just Discord.
Where did you reach out to support? I'll try to find it on Discord and the email inbox. Again, apologies for missing your message earlier!
Thanks! If you're trying to inscribe rare sats in bulk that are already in your possession, it will require a little bit of special prep, but it's easily done and won't take long.
Yes, provenance is a concept entirely orthogonal to satoshi binding, so you can easily have unbound children. However, you cannot have children of unbound inscriptions because they're non-transferable.
Custody here only being necessary so the address remains constant. The relinking could be done by anybody, enabling that flexibility.
While still subject to too-long-mempool-chain, if the platform custodies the parent, it would allow the parent input utxo to be relinked automatically depending on confirmation order or in case of an RBF.