pull down to refresh

0 sats \ 2 replies \ @conduition OP 19 Dec 2023 \ parent \ on: Inviscriptions - How to bypass Luke's filtering and mint useless NFTs anyway bitcoin
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 their translator off-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.
write
preview
0 sats \ 1 reply \ @supertestnet 19 Dec 2023
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
0 sats \ 0 replies \ @conduition OP 22 Dec 2023 freebie
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.