Is core.blockstack.org not synced?

Support
#1

I recently registered petrsnm.id

After waiting several hours I tried:

$ curl https://core.blockstack.org/v1/names/petrsnm.id
{
“status”: “available”
}

Docs say that: “Power users are encouraged to run local Blockstack Core nodes on their laptops or home/office networks in order to have reliable access to the Blockstack network. Your local node maintains the same state as the rest of the Blockstack Core nodes, so it will keep serving names, public keys, and storage routes even if upstream nodes are unreachable or go offline.”

So I install my own full node which returns what I expected:

$ curl http://localhost:6270/v1/names/petrsnm.id
{
“status”: “registered”,
“zonefile”: "$ORIGIN petrsnm.id\n$TTL 3600\n_http._tcp\tIN\tURI\t10\t1\t"https://gaia.blockstack.org/hub/1CYgYkkm67knmiL9u4qg9kALr1anVPnVZq/profile.json"\n\n",
“expire_block”: 620939,
“blockchain”: “bitcoin”,
“last_txid”: “93fb5205ce196d2c4b7041350e4a67828d9bbdbcdf464c55c6bcc062291b735e”,
“address”: “1CYgYkkm67knmiL9u4qg9kALr1anVPnVZq”,
“zonefile_hash”: “6ea37b5738439c985bb1332011c6c541f7510ee2”
}

… So is there something wrong with core.blockstack.org?

Purchased blockstack ID from wndows - profile erased
#2

Seems like explorer.blockstack.org has a problem loading namespaces

#3

core.blockstack.org caches requests for 12 hours, including negative responses. Your name loads for me on core.blockstack.org. Does it work for you now as well?

EDIT: see @aaron’s reply below.

#4

Seems like explorer.blockstack.org has a problem loading namespaces

Heh, the real issue is that explorer.blockstack.org needs an overhaul :wink: You can still query information about namespaces through core.blockstack.org, though.

1 Like
#5

@jude Yes, working now. I also notice that my name now appears as being registered in blockstack-browser. Yesterday it appeared with a clock icon and a tooltip that told me it was still in the process of being registered.

Conclusion: Clearly was registered on the blockchain, but due to core.blockstack.org caching, didn’t appear for 12 hours. Perhaps this should be mentioned to users when they register a name from the browser – “It may take 12 hours for name registration to complete”.

#6

There was some server down time for core.blockstack.org last night which probably caused that behavior. The /v1/names/ endpoint caches for a much shorter period of time than 12 hours.

1 Like