-
Notifications
You must be signed in to change notification settings - Fork 120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[sync with universe] unable to sync universe: proof for key is invalid #320
Comments
Interesting, it looks like you're trying to download a proof from the server that your |
Dug into this a bit, and it looks like the proof returned by the server fails before the actual tap level validation. instead the SMT inclusion proof doesn't match the universe root we fetch. |
Confirmed the same RPC error on my testnet setup, same minting outpoint. ScriptKey shows different x & y values. |
Can you elaborate on that? As in another leaf for that asset group or something else? |
Some inserted debug logs:
So it is the case that the roots mismatch. I think then this would mean the issuance proof isn't being serialized properly for the request/response of |
Encountered the similar issue while syncing universe. I was testing a workflow to transfer one asset from one tapd instance to address generated on another tapd instance. The CLI command I hit was : tapcli universe sync --universe_host testnet.universe.lightning.finance And the output I received was |
Will be the team's P0 priority as this issue will be encountered by many users. |
Solve by cleaning up DB state |
Hi, I am trying to mint my own taproot assets and I followed the steps:
bitcoind
, where thebitcoin.conf
looks like:lnd
, withlnd.conf
:Launched
tapd
, withtapd --network=testnet --debuglevel=debug --lnd.host=localhost:10009 --lnd.macaroonpath=~/.lnd/data/chain/bitcoin/testnet/admin.macaroon --lnd.tlspath=~/.lnd/tls.cert
Unlock lnd, create wallet address, and receive some testnet bitcoin:
after that, mint asset:
And then, when I want to sync with universe, I got this error:
The text was updated successfully, but these errors were encountered: