You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BRC20 is not anonymous since it is possible to trace the lineage of the ordinal transfer inscriptions. There is no way to anonymize ordinal ownership (unlike with BTC) but since BRC20 is a meta-protocol on top we can obfuscate transfers by routing through a single taproot address.
Users inscribe and transfer to mixer (provides list of addresses off-chain)
Mixer inscribes and transfers to each (uniform amount)
The problem with this is we have to trust the mixer to actually send the BRC20. To eliminate the intermediary we can do the following:
Users join off-chain pool (possibly on BOB)
Create P2TR multisig address
Users send BRC20 to taproot address
Users sign multisig to distribute tokens
This approach assumes the parties actually complete the process since otherwise the BRC20 tokens are locked forever. Additionally, to distribute the tokens we either need multiple rounds of signing or we can create a "cursed" inscription which contains multiple BRC20 transfers. The open question here is whether that is supported by the BRC20 protocol, I think ord already indexes these inscriptions but they are certainly not "native".
Some other thoughts
If we were able to introspect the witness data in the P2TR reveal script we could make sure it is only spent with a specific inscription but I don't think that is possible. It is also unclear if the multiple inscriptions discussed here mean that the they can be rolled within one envelope or multiple.
The text was updated successfully, but these errors were encountered:
BRC20 is not anonymous since it is possible to trace the lineage of the ordinal transfer inscriptions. There is no way to anonymize ordinal ownership (unlike with BTC) but since BRC20 is a meta-protocol on top we can obfuscate transfers by routing through a single taproot address.
The problem with this is we have to trust the mixer to actually send the BRC20. To eliminate the intermediary we can do the following:
This approach assumes the parties actually complete the process since otherwise the BRC20 tokens are locked forever. Additionally, to distribute the tokens we either need multiple rounds of signing or we can create a "cursed" inscription which contains multiple BRC20 transfers. The open question here is whether that is supported by the BRC20 protocol, I think ord already indexes these inscriptions but they are certainly not "native".
Some other thoughts
If we were able to introspect the witness data in the P2TR reveal script we could make sure it is only spent with a specific inscription but I don't think that is possible. It is also unclear if the multiple inscriptions discussed here mean that the they can be rolled within one envelope or multiple.
The text was updated successfully, but these errors were encountered: