Skip to content
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

Lightweight resolver deployment roadmap: Spec and deploy SPV36 wire command #217

Open
hlandau opened this issue Jan 19, 2015 · 0 comments
Open

Comments

@hlandau
Copy link
Member

hlandau commented Jan 19, 2015

Issue created at the request of Indolering.

Probably the first step which should be taken in the deployment of Namecoin lightweight resolvers is to spec and, with the release of Namecore, deploy, a new wire command which allows lightweight clients to query for name transactions by name, i.e. something like:

getname(key) ->
  (name transaction, merkle branch proving inclusion in block, block header, block height)
| does-not-exist

The block header could be replaced with a hash and the block height omitted but I think it's better to include these things as they consume negligible bandwidth and maximize the flexibility of implementation of lightweight clients.

It should be noted that UTXO CB changes this protocol only mildly:

getname(key, depth) ->
  (name transaction, merkle branch proving inclusion in block, block header, block height,
   branch proving inclusion in UTXO set, coinbase transaction containing attestation value,
   merkle branch proving inclusion of coinbase transaction in block of $depth, block header, block height)
| does-not-exist.

Changes for NX CB change the does-not-exist response in a similar way.

If depth is fixed at 12 then this simplifies the above protocol accordingly.

@hlandau hlandau changed the title Lihtweight resolver deployment roadmap: Spec and deploy SPV36 wire command Lightweight resolver deployment roadmap: Spec and deploy SPV36 wire command Jan 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant