search

lightninglabs / taproot-assets

A layer 1 daemon, for the Taproot Assets Protocol specification, written in Go (golang)
MIT License
457 stars 110 forks source link

[bug]:The lnd node receiving the asset cannot synchronize the universe #706

Open Wmengti opened 9 months ago

Wmengti commented 9 months ago

Background

I ran two lnds and two taproot on the same server, assuming they were called tapd and tapd1. First, I used tapd to publish an asset, and then synchronized it to the test public universe node. Then I used tapd1 to synchronize the asset ID and found that it could not be synchronized.

Your environment

tapcli --profile=tapd1 universe sync --universe_host testnet.universe.lightning.finance:10029 --asset_id 7f5ded073780fa499269ae7e137dff9fb5bef03b50e7b09086909a9a88884dc1
tapcli --profile=tapd universe sync --universe_host testnet.universe.lightning.finance:10029 --asset_id 7f5ded073780fa499269ae7e137dff9fb5bef03b50e7b09086909a9a88884dc1
tapcli --profile=tapd addrs new --asset_id 7f5ded073780fa499269ae7e137dff9fb5bef03b50e7b09086909a9a88884dc1 --amt 21

Expected behavior

tapd shoud sync universe successfully and generate an address to receive assets

Actual behavior

image
Roasbeef commented 9 months ago

Which version of tapd are all the nodes running? You'll need to be on at least v0.3.1 for that universe.

Wmengti commented 9 months ago

Which version of tapd are all the nodes running? You'll need to be on at least v0.3.1 for that universe.

how to update the tapd version, I used 0.3.0-alpha

guggero commented 9 months ago

how to update the tapd version, I used 0.3.0-alpha

How did you install it? From source code, from the release binary, within Litd or within Polar?