Orchestration

A private wallet that supports multiple chains is not one transaction. It is a sequence: receive on the right network, prepare funds for private use, route a swap, shield the result, maybe enter a yield vault, keep activity legible in the app.

That sequence is the orchestration layer.

What orchestration absorbs

Without an orchestration layer, users assemble the flow themselves:

• pick a chain and asset
• manage gas and bridging concerns
• talk to a privacy system
• find a swap route
• remember to re-shield
• deposit into a yield venue
• track which receipt belongs to which step

Fiber collapses those steps into product actions — deposit, send, swap, earn — while keeping the privacy and authorization properties described elsewhere in these docs.

Examples in the product

Deposits. A successful chain transfer can appear in activity immediately, then continue through privacy activation before the balance is fully usable. See Supported chains.

Swaps. Buy gold or silver by unshielding through a one-time address, swapping, and shielding the output. See Privacy.

Yield. Move stablecoins into a supported Morpho vault path and shield the vault shares back to the private wallet. See Built-in yield.

Design constraints

Orchestration is allowed to be opinionated. It is not allowed to become custody.

That means:

• multi-step flows can be automated in the UX
• signatures and authorization still belong to the user
• failures should surface as transaction states, not silent invention of balances
• chain and asset differences may change timing without changing the ownership model

The trade

The benefit is obvious: people can use private onchain finance without running a personal trading desk.

The cost is also obvious: when something is slow or stuck, the stuckness may be inside a multi-step pipeline rather than a single public transfer. Activity history, pending states, and these docs exist so that pipeline is inspectable instead of mystical.