Skip to content
This repository was archived by the owner on Mar 26, 2025. It is now read-only.

Updating the registrar after Orphaned BNS-TX #64

Open
sleepiJoe opened this issue Jan 18, 2022 · 0 comments
Open

Updating the registrar after Orphaned BNS-TX #64

sleepiJoe opened this issue Jan 18, 2022 · 0 comments

Comments

@sleepiJoe
Copy link

example https://registrar.stacks.co/v1/names/alexandernacho.id.stx shows the linked address,
{"blockchain":"stacks","status":"submitted_subdomain","last_txid":"32ad1787fcaa6a8aaf6f29ff440fab63d098374af1549b08dff6d14db59d39cf","zonefile":"$ORIGIN alexandernacho.id.stx\n$TTL 3600\n_http._tcp\tIN\tURI\t10\t1\t\"https://gaia.blockstack.org/hub/1G6DVN2rCw4cWKpTE6yVaJQHMMpJXXfMfD/profile.json\"\n\n","address":"SP2JRCS2HC0WC5D29NC683RPXDVK9F41Y7W4EQS9V","zonefile_hash":"41c8cf0cea57becec455a6449e39f33059a9aa94"}
but calling its
stacks name or name history
can not confirm its state in the chain.

Could that come from orphaned TXs? How many orphaned BNS names are there?
And the wallet is able to get a second BNS name.
image

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant