Manager Signing Wallet & Fund Holding Wallet
See Core Concepts for the full custody and signing model this page assumes. In short: Tahoe provisions and custodies both wallets described here; fund managers direct them, authorizing each action via 2FA.
There are two distinct wallets on the fund-manager side of a fund, not one:
| Wallet | Scope | Purpose |
|---|---|---|
| Manager Signing Wallet | One per person whose role has permission for these actions | Authorizes fund-owned operations via 2FA — accepting investments, issuing shares, and similar actions |
| Fund Holding Wallet | One per fund, shared across all managers on that fund | Holds fund assets before they move into the Fund Treasury Vault. No one operates it directly — it only moves when directed by an authorized signing action. |
Wallet Ownership
Tahoe provisions and custodies both wallets. No one — not even the fund manager — has direct operating access to the Fund Holding Wallet; it can only be directed to act through an authorized Manager Signing Wallet action. This is not a self-custody arrangement for either wallet, and no fund manager holds keys to either one.
A future version may offer true self-custody as a separate option for fund managers who want to hold their own keys. That is not the default today, and should not be described as already available.
Planned: multi-signature support
Multi-signature authorization for the Manager Signing Wallet is approved future scope: the fund manager will define an approval threshold and designate which people can check or sign a given action, so no single person can unilaterally authorize a fund-owned operation. Implementation approach is undecided and may change before this is built — not yet built.
What Each Wallet Does
Check with Vlad: the exact split of which operations are called directly by the Manager Signing Wallet versus routed through the Fund Holding Wallet is not yet confirmed. The table below lists the responsibilities; the wallet column is intentionally left open pending that confirmation.
| Responsibility | Operation | Which wallet? |
|---|---|---|
| Hold subscription assets | Receives staged subscription USDC; manager acceptance is recorded separately. | Fund Holding Wallet |
| Authorize an exact asset pull | USDC.approve(vaultAddress, exactAssets). This changes allowance only. | Check with Vlad |
| Send subscription assets | TreasuryWallet.requestDeposit(assets, investor, holdingWallet). The Fund Treasury Vault pulls the approved USDC. | Check with Vlad |
| Fulfill a deposit | TreasuryWallet.fulfillDeposit(assets, shares, investor) after pricing and protocol checks are ready. | Check with Vlad |
| Fulfill a redemption | TreasuryWallet.fulfillRedeem(shares, assets, investor) after manager price acceptance and liquidity checks. | Check with Vlad |
| Exchange strategy liquidity | Receives approved drawdowns from the Fund Treasury Vault and returns approved assets through the protocol's strategy operations. | Check with Vlad |
Relationship To The Fund Treasury Vault
The Manager Signing Wallet and Fund Holding Wallet together are where fund-owned authorization and pre-deposit custody happen. The Fund Treasury Vault controls subscription and redemption accounting, claimability, share issuance, and asset payouts. Vault Operations monitors all wallet identities and their current state.
Return to Investment Management or Core Concepts.