Extending the Namecoin Wallet App to include Naming features
Posted: Sat Jan 10, 2015 8:19 am
I would like to explore the idea of adding Namecoin specific functions to an existing SPV client for Namecoin (the Namecoin Wallet for Android: https://play.google.com/store/apps/deta ... oin.wallet - forked by Hash Engineering). This particular SPV client does not store the blockchain, but rather downloads the headers only. It is able to get relevant transactions other peers for coin transactions.
Since the naming service functions are also in transactions (with a different transaction version to mark them off), I am wondering if it is possible to add the name_new, name_firstupdate and name_update transaction functionality to the Namecoin Wallet (which is forked from the Bitcoin Wallet for android).
Theoretically, we could design a UI for creating a domain name. The app would send out the first transaction (new_name), then wait the 12 blocks before sending out the name_firstupdate transaction. The app would know when these transactions are confirmed in the blockchain, in the same way it knows about simple coin transactions (send or receive).
The desktop client generates a Name Index database from parsing the blockchain, block by block, which it first queries to see if a name already exists. Can this functionality be left out? That file is 97 MB currently.
What foreseeable problems would there be with doing an SPV namecoin client? Does it really need to see the entire blockchain to create and update names?
Is there any other functionality that would also be good to add to the Namecoin Wallet for android?
Since the naming service functions are also in transactions (with a different transaction version to mark them off), I am wondering if it is possible to add the name_new, name_firstupdate and name_update transaction functionality to the Namecoin Wallet (which is forked from the Bitcoin Wallet for android).
Theoretically, we could design a UI for creating a domain name. The app would send out the first transaction (new_name), then wait the 12 blocks before sending out the name_firstupdate transaction. The app would know when these transactions are confirmed in the blockchain, in the same way it knows about simple coin transactions (send or receive).
The desktop client generates a Name Index database from parsing the blockchain, block by block, which it first queries to see if a name already exists. Can this functionality be left out? That file is 97 MB currently.
What foreseeable problems would there be with doing an SPV namecoin client? Does it really need to see the entire blockchain to create and update names?
Is there any other functionality that would also be good to add to the Namecoin Wallet for android?