4
1
In my case a store owner has different POS terminals. On none of the terminals should be a private key stored! The owner has one wallet, where he wants to get all transactions aggregated, done on the POS terminals.
According to my reasearch I came up with 2 possibilities:
- Stealth addresses (BIP 63), which to my knowledge is not implemented anywhere in a library, so that I could use it easily.
- Master Public Key: E.g. the electrum wallet gives you an MPK by which one could derive addresses (through HD Derivation).
Now to my questions:
- Is there any other approach one could generate addresses without a private key available?
- Are there any problems one could face with the MPK derivation approach?
- Which wallets expose the MPK and furthermore which wallets get a notice of transactions done to addresses derived outside of their knowledge (however from the seed they know)?
Of course, there is always the naive approach where you generate one single address (or one per terminal) and use that address for all incoming transactions. I assume that for improved anonymity (both for your store owner and the customers), you wish to avoid this? – Nate Eldredge – 2015-08-01T18:14:30.707
@NateEldredge Or improved auditability. – Nick ODell – 2015-08-01T18:17:14.587
@NateEldredge absolutely, reusing the same address should be avoided! – Stefan – 2015-08-01T18:21:43.997
@NickODell Auditing is not an issue in my case, as the orders are stored in a POS system, only the payments should go via bitcoin. – Stefan – 2015-08-01T18:23:38.267
Just checking, if you are still looking you can try https://medium.com/@blockonomics_co/payment-companion-for-your-wallet-dc3766b14e7a#.sh1h017gy. Can generate address/invoice using ur MPK
– dark knight – 2016-07-29T04:27:51.563