Topic: Generate armory wallet addresses with Bit-Wasp / bitcoin-php (Read 151 times)
armoryd talks to ArmoryDB, not bitcoind. ArmoryDB needs a local bitcoind. Clients such as ArmoryQt and armoryd connect to ArmoryDB only, through a socket. That socket is however not encrypted, so it's on you to secure that stuff.
Thx for your input guys. I'll experiment with the different avenues.
If I want to deal with armoryd, that would mean I need to run a full bitcoind node on the server right? If so I would rather avoid it.
If I want to deal with armoryd, that would mean I need to run a full bitcoind node on the server right? If so I would rather avoid it.
AFAIK, Armory doesn't generate private keys in the same way as BIP32 type wallets etc... It is using a proprietary system. So, I don't think you'll be able to export a "Master Public Key" from Armory, and have other wallet apps/libraries reproduce the same keys/addresses as your Armory wallet.
You options would then be to generate keys/addresses externally to Armory, and then import them to Armory... or you would need to use a different wallet that supported the BIP32 standard that I believe bitwasp is using.... that way, you would be able to export a "Master Public Key" from your wallet... and Bitwasp should be able to derive the same public keys/addresses without needing to expose the underlying seed/private keys.
You options would then be to generate keys/addresses externally to Armory, and then import them to Armory... or you would need to use a different wallet that supported the BIP32 standard that I believe bitwasp is using.... that way, you would be able to export a "Master Public Key" from your wallet... and Bitwasp should be able to derive the same public keys/addresses without needing to expose the underlying seed/private keys.
You can export Armory public roots. You'd have to implement the address chain derivation code in php most likely. Your best bet is to setup your stack to talk to an instance of armoryd, which will handle the wallet stuff, spit out new addresses, and monitor the blockchain for you. It works over JSON-RPC.
https://github.com/goatpig/armoryd
AFAIK, Armory doesn't generate private keys in the same way as BIP32 type wallets etc... It is using a proprietary system. So, I don't think you'll be able to export a "Master Public Key" from Armory, and have other wallet apps/libraries reproduce the same keys/addresses as your Armory wallet.
You options would then be to generate keys/addresses externally to Armory, and then import them to Armory... or you would need to use a different wallet that supported the BIP32 standard that I believe bitwasp is using.... that way, you would be able to export a "Master Public Key" from your wallet... and Bitwasp should be able to derive the same public keys/addresses without needing to expose the underlying seed/private keys.
You options would then be to generate keys/addresses externally to Armory, and then import them to Armory... or you would need to use a different wallet that supported the BIP32 standard that I believe bitwasp is using.... that way, you would be able to export a "Master Public Key" from your wallet... and Bitwasp should be able to derive the same public keys/addresses without needing to expose the underlying seed/private keys.
Hello,
I would like to implement some payment system, where I would generate a unique address for each transaction/user. My website runs on php 7.3.
I found some examples using bitwasp library. But am unsure what would be the best approach to implement this.
- Should I provide a wallet private key to bitwasp to generate my addresses? This example seems to take a private key fromWif ? (i dont know what this is)
https://github.com/Bit-Wasp/bitcoin-php/blob/9e535f04665ba22ba2b8b63f371ec50d2e7eabb8/examples/addresstypes.script.php#L16-18
Then I guess the generated addresses would show up in Armory
- Is it possible to provide bitwasp with only my wallet public key to generate new addresses ? I would rather not leave my private key in some php file or in my database (even if it is secured).
- Should I generate a unique private key with bitwasp, use it to generate my addresses and then import it in Armory ?
- Should I generate a new private key and address for each new transaction and then import it in Armory ?
Some help on this would be appreciated.
Thx
Eric
I would like to implement some payment system, where I would generate a unique address for each transaction/user. My website runs on php 7.3.
I found some examples using bitwasp library. But am unsure what would be the best approach to implement this.
- Should I provide a wallet private key to bitwasp to generate my addresses? This example seems to take a private key fromWif ? (i dont know what this is)
https://github.com/Bit-Wasp/bitcoin-php/blob/9e535f04665ba22ba2b8b63f371ec50d2e7eabb8/examples/addresstypes.script.php#L16-18
Then I guess the generated addresses would show up in Armory
- Is it possible to provide bitwasp with only my wallet public key to generate new addresses ? I would rather not leave my private key in some php file or in my database (even if it is secured).
- Should I generate a unique private key with bitwasp, use it to generate my addresses and then import it in Armory ?
- Should I generate a new private key and address for each new transaction and then import it in Armory ?
Some help on this would be appreciated.
Thx
Eric
Jump to: