Blockstream / Blockstream/asset_registry
Possible bug on Testnet [Mainnet to be checked]
- Dominant language
- HTML
- Stars
- 5
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
I created [an asset](https://blockstream.info/liquidtestnet/asset/a9d52b02348a097d4f780644064c437e364a41d6299290fef1c49e7d1fbbf665) and registered it using liquidjs-lib
Follow the steps of [this example to reproduce](https://github.com/baset-btc/liquid-test/blob/main/test.js)
Unfortunately, it looks like the asset hash is not recognized properly by the registry
We already checked with the Blockstream's support and they've been able to get the same hash for the asset with the contract of the example
Any help would be appreciated
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with test.js from the linked reproduction example and follow how the asset is created and registered on Liquid Testnet. Compare the generated asset hash with the registry result and check whether the behavior also occurs on Mainnet; done means the cause is identified and the registry recognizes the asset hash correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100