what do you think, would it be possible to implement some kind of paper-wallet-generator into the Mooncoin-wallet? Maybe a more than useful feature.
I was just reading about that before, same bitcoin wiki page:
Tips for making paper wallets
- 1. Disconnecting from the Internet guarantees that that the paper wallet generator is truly self-contained and isn't transmitting your keys online.
- 2. Verifying the integrity of the code (and the trustworthiness of the author) is important to make sure a hacker hasn't modified the HTML so that it generates predictable addresses instead of truly random keys.
- 3. Using a very basic printer is advisable since high-end office printers may have WiFi or internal storage that keeps a cache of printed documents.
Practicalities restrict us to simply recommending that Mooncoin holders follow 1. and 3. there isn't much more we can do.
However, it's possible that we could improve the Ux by actually tackling 2 instead of making totally unrealistic demands of users. Apart from the woeful laxity of undefined terms such as "predictable" and "truly random", it blithely ignores the fact that users are not generally in a position to verify the integrity of program code (nor are currency exchange operators, apparently).
But anyway, the codebase has moved on and there are now strong imprecations
against creating paper wallets, e.g.
this one from Pieter Wuille:
“As of the 0.8.x series, the reference client does not support paper wallets. You can export individual keys, and print them to paper, but you are very likely to shoot yourself in the foot unless you're familiar with the implementation details.
In particular, change (the difference in value between coins used to create your transaction, and the amount being sent) is sent to a fresh address in order to increase privacy of the system. When you're using a paper wallet, you will likely miss these, as well as key pool entries.
There is support planned for deterministic wallets (BIP32), which means a single backup of a wallet seed will be enough to create the wallet. This may or may not end up in 0.9, though.
The reason why no "Export wallet to PDF" exists, is exactly because in the current model, this would result in many misconceptions and lost coins. Without deterministic key generation, no immutable dump of the wallet can survive (a series of) spends.”
Mooncoin could follow Dogecoin's example and plot a course to migrate to the Bitcoin Core 0.9.x codebase. Then, if/when BIP32 is implemented in the 0.9 series, Mooncoin would be in an excellent position to adopt the tech.
Cheers,
Graham
P.S. Some altcoin devs are offering extended "user-facing" wallet functionality by including additional tabs. For example,
Silkcoin has a block explorer built in to the wallet, as does AllAgescoin, although with 8 tabs, I think Mike may have got a bit carried away. I hear he's planning to include a TV guide
.
We could take a sober look at what's available to adapt.
Bellacoin has an expanded set of wallet tabs. Most of them are quite simple, using Qt's webhandler to render http-retrieved content a la browser. However, this is also verging on creeping centralism; control of the remote domain means control over the rendered content of the wallet tab - so it's only really suitable for a trusted, actively-defended remote source such as a well-run Foundation or a currently- favoured exchange.
P.P.S. Bellacoin's website is an excellent example of high-quality altcoin user support, many props.
