Topic: Namecoin Support? (Read 671 times)

Thanks goatpig, that's good info to have.

Depends how hard Namecoin has forked from the core Bitcoin source. Armory grabs its data from the raw binary block files created by the core client. As such it trusts the core client with block verification. This makes porting Armory rather easy.

Assuming Namecoin uses the same transaction signing scheme and EC as Bitcoin, you're left with node port, magic words, fee calculation and dust sweeping/ignoring rules to change. And everything else I possibly overlooked =P

There is some interest in the Namecoin community in using Armory's cold storage for protecting critical Namecoin names.  I noticed that there are a few references to Namecoin in the Armory source code (I guess Alan wrote parts of Armory with non-Bitcoin chains in mind), so I'm curious how much work would be involved in adding Namecoin support to Armory.  The three stages I can think of would be: (1) send and receive non-name transactions on the Namecoin network, including with offline wallets; (2) handle name operations, including with offline wallets; and (3) generate multiple renew operations for the same name from an offline wallet (maybe with a LOCKTIME), so that e.g. a name could be renewed for 10 years and have the signed transactions stored on an online wallet for queued release to the network.

For each of those 3 stages, is it possible to roughly estimate how much work would be involved in adding this?  I'm aware that the Armory devs have much higher priorities, so I wouldn't expect them to work on this themselves, but if (hypothetically) someone else volunteered to attempt it, would an Armory dev be willing to assist logistically and/or answer questions when necessary?  Would the code be merged by the Armory devs if it were written and tested?

Thanks.