Quote from: kobik on February 14, 2018, 08:49:09 AM

Quote from: droark on February 13, 2018, 07:04:45 PM

Or, maybe nobody thought to add such functionality. Tongue

Ugh my bad, it's lockboxes you can create remotely, not wallets.

Quote

As I already said, I'm quite sure I know what I'm doing and the risks involved

The issue with creating wallets dynamically is 2 fold: your servers will be carrying the private seed, and how do you back that up? It's not that it can't be done, but the opsec are poop. What you'd want instead is a wallet model where you have one master seed, and any amount of child wallets derived on the fly from that seed. That's for 0.97, which is a couple months away at the earliest.

Quote

I love the fact that Armory is using bitcoind as a full node, but the downside of bitcoind is the lack of dynamic wallets management.

What I can offer you in the short term is a method to import wallets from their seed (either public or private). You'd have to create the wallets in the GUI, deal with the backups and what not, then you can register that wallet with armoryd through the 72 character seed.

Quote

I find Armory to be very well designed, but I need the GUI functionality of managing wallets to be done via RPC including adding fresh new wallet for an employee instead of doing that manually via GUI.
So I think this feature will be great for us and others! Smiley

What do you want this for? I think you're confused about Armory's stack. This is how it works:

- The GUI, which deals will all things UX and wallets/crypto. The GUI connects to the DB over a socket. The DB can be remote but right now there is no encryption layer over that socket. That's for 0.97 too.

- The DB, that deals with all things blockchain. A GUI registers the addresses in its loaded wallets with the DB. The DB tracks these addresses and passes on balances and historical data back to clients. The DB requires a full node that's fully compatible with Core's P2P, RPC and on disk blockdata serialization. The DB needs disk access to the blockdata. There can be many clients per DB.

- armoryd uses the same socketing interface as the GUI, i.e. it can connect to a DB remotely. armoryd DOES NOT interface with GUIs, or other armoryd instances. It only presents a JSON-RPC interface to users. Registering a wallet through armoryd will NOT affect other GUIs nor armoryd instances. It's just another isolated client.

From your description, it feels like you are expecting things out of armoryd that it was never designed to do. You should lay out your logistics at least, so we can tell if your requirements can be met.