Olaoluwa Osuntokun
Olaoluwa Osuntokun
So each address you create can only receive a set asset + amt of that asset. They're similar to LN invoice in that regard, as they're intended to be use...
Keeping this one open, as the syncer hasn't been updated to use the new methods yet.
I think this is possible, but fwiw that way the addresses were designed was that they're intended to be more or less single use, and also bind the amount into...
@jayneel007 yes, we'll address this while creating group key addresses: https://github.com/lightninglabs/taproot-assets/issues/291.
Sounds like you want that add that a unique challenge is bound to the prove/verify calls? So we'd add that hash/challenge value to the `prove` call, it's embedded to the...
Given the above, here's a rough implementation plan: * Add a random challenge hash to the `prove` RPC call * When we go to generate the ownership proof, if the...
@straumat so on the gRPC interface the outpoint field is also available. We require that if a user has multiple UTXOs as distinct outpoints for the same `asset_id`. Overall though,...
@GeorgeTsagk latest code link (the other one broke): https://github.com/lightninglabs/taproot-assets/blob/109d86f5763cfa412d4c05b98a02bf9eb4cef6c4/tappsbt/create.go#L140-L166
Duplicate of https://github.com/lightninglabs/taproot-assets/issues/478?
I think let's target this at using the batched postgers queries for things like reading the SMT levels. I think we can modify the recursive call to fetch all the...