[deployer] Per-organization grid wallets per network so each organization funds its own deployments #294
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lhumina_code/home#294
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of the Launcher settings work in #291. Each organization should be able to use its own TFGrid wallet for mainnet and for qanet, falling back to the admin instance default when left blank, so one organization's deployments are funded from its own wallet rather than the shared one. This is more than a settings panel: today a wallet is bound to a compute daemon (one mnemonic per network, read once at startup and used for every deployment on that daemon), so the deploy path always funds from the shared daemon wallet regardless of organization. Making per-organization wallets real needs either a separate daemon per organization and network, or a way to pass a per-deployment wallet into the compute deploy call, which is a compute and deploy-path change rather than admin UI. Filing this so the wallet piece gets a proper design rather than a settings field that looks active but quietly funds from the shared wallet. The other per-organization settings (email sender, Resend key, assistant keys) land separately as UI plus a small install-time fallback.