pull down to refresh
0 sats \ 4 replies \ @conduition OP 18 Dec 2023 freebie \ parent \ on: Inviscriptions - How to bypass Luke's filtering and mint useless NFTs anyway bitcoin
The ciphertext transaction is invisible. The translator transaction isn't, and that's intentional. Part of the use case of inscriptions is on-chain discoverability. If my wallet software mints an NFT, software running on other nodes should be able to detect that new NFT without an external communication channel or database. This implies the inscription must be distinguishable on-chain, eventually.
If I perform inscribing first in secret, and reveal the inscription occurred only after it has already been mined, this nullifies any incentive to censor/filter in the first place (beyond spite), because 99.9% of the damage (block space usage) has already been done.
Take street art as an analogy. Inscriptions are like graffiti, except permanent. Currently, vandals are painting buildings in broad daylight: Their progress is easy to observe, and thus easy to interrupt if we wanted to.
However if we start to interrupt them too much, then the little punks will just wait until dark, and paint in the shadows while we're asleep. We wake up and find their works were completed in secret, and by then, nobody can remove them. The damage is already done.
I discussed all of this in this section with more detail
If I perform inscribing first in secret, and reveal the inscription occurred only after it has already been mined, this nullifies any incentive to censor/filter in the first place (beyond spite)
It seems to me there is a second reason, beyond spite: to disincentive inscriptions. If, due to translation censorship, you lost money irrecoverably whenever you did an invisible inscription, perhaps inscribers would stop doing it
reply
Money spent on fees would never be truly lost, as long as the inscriber still knows their translator secret, and as long as they have some hope of being able to publish it on-chain in the future. Again, I covered all of this in the article.
Furthermore, even if one translator transaction can be identified and effectively excluded from the blockchain, the ciphertext is already on-chain, so censoring nodes would need to ensure that no other translator transactions for that inviscription ever make it onto the chain in perpetuity, which is no small feat.And even then, the inscribing user can still publish theirtranslatoroff-chain to reveal the inscription data, and prove they inscribed bitcoins with said data. It just won't be detectable by on-chain scanning alone.
reply
The latter option -- "do it off chain" -- is rather encouraging
Maybe you could do inscriptions even more invisibly by doing more parts of the process off chain
reply
You can do the whole process off-chain using OpenTimestamps and taproot commitments if you wanted to.
The people using inscriptions don't care about efficiency though :( They want it all on-chain, for reasons beyond my understanding.