PROJECT SHAREFundingManagercompleted-cycle project allocation
→
ON-CHAIN ROUTERAllocationManagerReading active policy…
Loading policy destinations…
PROJECT / ALLOCATION
Follow the project share.
Every destination stays visible.
FundingManager routes the project share into AllocationManager. A versioned on-chain policy separates investor distribution from fixed project recipients, while startup and operational funding remain bounded by explicit contract rules.
VERSIONED policy by cycle
FIXED recipient addresses
BOUNDED operational funding
CURRENT FLOW
One project inflow. Explicit on-chain destinations.
The visualization below is derived from the active policy. It does not estimate or invent percentages; every share comes from AllocationManager.
VERSION HISTORY
Policy changes are tied to cycle boundaries.
The active policy applies according to its effective cycle. Scheduled and historical policies stay visible so allocation rules can be reconstructed later.
Loading policy versions…
Cycle settlement is permissionless and sequential. Calling sync cannot alter recipient addresses, percentages, or the policy selected for a historical cycle.
FIXED DESTINATIONS
Claimable project funds can only go where policy says.
Anyone may invoke a configured payout. AllocationManager sends the full claimable amount directly to the recipient encoded in policy; the caller cannot redirect it.
Loading recipient balances…
FUJI / FIVE CATEGORY VAULTS
Budget authority. By vault.
View each deployed budget separately. Requests, approvals, limits and balances are enforced by that vault’s on-chain policy and credentials. Unconfigured categories remain read-only; Treasury Safe is not the Treasury Budget Vault.
Reading the five budget vaults…
Checking this vault’s current policy routing…
Checking connected wallet…
Loading Fuji budget vaults…
Development vault available—
AllocationManager credit claimable—
Total funded (vault)—
Total spent (vault)—
AVAX ledger reconciliation—
Spending policy—
30-day spending period—
Development spending request
Wallet roles not loaded
Only a credentialed Requester for the selected category can submit. Limits are enforced on-chain; this form never sends funds directly. The destination must be reviewed before approval.
Request review packet
Share this packet with both approvers. The contract stores the purpose hash, not the readable purpose. Approvers must verify the exact text before signing.
Claim Development allocation into vault
Permissionless: calls the vault’s pullAllocation(). The money can only enter the vault; it cannot be redirected to your wallet.
On-chain expenditure requests
Newest first · approval counts verified on-chainReading requests…
LAUNCH CAPITAL
Startup reserve is isolated from ordinary allocation balances.
Voluntary startup deposits feed a dedicated reserve. Bootstrap can only fund enabled operational roles according to their configured launch targets and period limits.
Reserve coverage—
Available—
Expected bootstrap—
Required reserve—
Shortfall—
PERMISSIONLESS ACTIONS
Fund or invoke the reserve rules.
Deposits are explicit voluntary AVAX transfers to AllocationManager. Bootstrap only succeeds when the on-chain reserve requirement is satisfied.
OPERATIONAL GAS
Role funding is bounded before anyone invokes it.
Each operational role has a fixed wallet, minimum, target, per-period cap, and enabled state. An invoker pays gas but cannot choose a different destination.
Loading operational roles…