bitcoinops/bitcoinops.github.io

Topic review: Taproot Assets not use Client Side Validation

22388o opened this issue · 2 comments

I was reading the CSV topic and I'm missing information, according to Taproot Assets documentation and the code itself , in which CSV is not mentioned, but Sparse Merkle Tree or Merkle Tree

If I'm wrong, please fix me.

Taproot assets require the users to keep track of the full history of the exchanged token and to provide it alongside any transactions. This historical data is not stored on chain. It can optionally be provided via Universes, but is required to prove the presence of taproot assets and only validated client-side.

Check out for example “How do I find out what assets have been issued?” in the Taproot Assets FAQ.

Now is clear for me