Hub-and-Spoke Model

Makina strategies are cross-chain by design. A single strategy can hold capital and run positions on many chains at once, while presenting users with one machine token, one share price, and one place to deposit and redeem. The architecture that makes this possible is hub-and-spoke.

The topology

• The Hub Chain is the single home of the Machine. It is where users deposit and redeem, where shares are minted, and where the strategy's total AUM and share price are computed. It also hosts the strategy's Hub Caliber.
• Each Spoke Chain hosts a Caliber plus a Caliber Mailbox. The Caliber executes the strategy locally, and the Mailbox is its connection back to the Machine.

Any supported chain can serve as a hub. A hub together with its spoke chains forms a Makina instance, with its own core factory, registries and beacons, and several instances can run side by side. See the Deployments page for the live instances and the chains they span.

Why a Mailbox on each spoke

A Spoke Caliber works exactly like the Hub Caliber, except it can't talk to the Machine directly, because the Machine is on another chain. The Caliber Mailbox stands in as the Machine's local endpoint: from the Spoke Caliber's point of view, the Mailbox is the Machine. It handles the bridging and reporting that connect the Spoke back to the Hub, so the Caliber's logic is identical everywhere. See Caliber Mailbox.

Two cross-chain problems to solve

Spanning chains creates two distinct challenges, each with its own mechanism:

1. Moving value across chains. Capital must travel between the Hub and the Spokes, and value must never appear lost while it's in transit. This is handled by Liquidity Bridging, a deliberate, multi-step process over approved bridge adapters, with in-flight transfers explicitly tracked in AUM.
2. Knowing value across chains. The Machine must learn what each Spoke Caliber is worth in order to compute total AUM, without trusting a single reporter. This is handled by Cross-Chain Accounting, which relies on Chainlink CRE to relay each Spoke's accounting snapshot to the Hub.

The next pages cover each in turn.

Shared cross-chain infrastructure

Reasoning about "the same token on another chain" requires a shared map, deployed once per chain: the Token Registry maps a local token to its equivalent address on each foreign chain. It is what lets bridging and accounting refer unambiguously to assets across the whole deployment.