How it works / the loop

One swarm.
Multiple routes.

A simple flow. A powerful engine. Five moves take NEAR from your wallet into strategies and back, and each one is a single contract call.

  1. 01Deposit

    Put your capital
    to work.

    Deposit supported assets into a Near_Beetle vault or strategy.

  2. 02Deploy

    The beetles move.

    Capital is routed according to the selected strategy and its parameters.

  3. 03Harvest

    Yield comes back
    to the nest.

    Generated rewards can be harvested according to the strategy.

  4. 04Compound

    Yield becomes
    more capital.

    Where supported, rewards can be redeployed to compound the position.

  5. 05Rebalance

    The swarm adapts.

    Strategy allocations can be adjusted according to predefined rules and protocol parameters.

Call by call

What each
move does.

Straight from the vault contract:
who calls it, what changes, what it can’t do.

  1. 01

    Deposit

    deposit() · you

    Attach NEAR to the call. The vault mints shares at the current share price and adds your NEAR to idle liquidity.

    Your first deposit also pays once for your own storage entry, about 0.001 NEAR, taken from the attached amount. What remains must be at least 0.01 NEAR.

  2. 02

    Deploy

    deploy(strategy_id, amount) · keeper

    The keeper moves idle NEAR into a whitelisted, enabled strategy.

    The call fails if it would take that strategy above its target share of total assets.

  3. 03

    Harvest

    harvest(strategy_id, reward_amount) · keeper

    Yield is reported per strategy and added to that strategy’s balance, which raises the share price for every depositor.

    The performance fee is minted as shares to the fee recipient, sized so those shares are worth exactly the fee.

  4. 04

    Compound

    no extra call

    Harvested yield stays in the strategy balance, so it is working capital from the moment it is reported.

    You don’t receive new shares. The ones you hold are worth more NEAR.

  5. 05

    Rebalance

    rebalance() · keeper

    First, anything above target is recalled to idle; a disabled strategy has a target of zero. Then idle NEAR is deployed to strategies below target, while it lasts.

    Whatever the targets leave unallocated stays idle as the withdrawal buffer.

Getting out

Back to
your wallet.

Burn shares, receive NEAR. Withdrawals are always allowed, including while the vault is paused.

They are paid from idle liquidity only. If idle is too low, the call fails cleanly with Insufficient idle liquidity and nothing is burned; the keeper has to recall capital first.

If the payout transfer itself fails, the shares you burned are restored.

// what would I get?
preview_withdraw(shares)   // → yoctoNEAR
idle_assets()              // → liquidity available now

// burn shares, receive NEAR
withdraw(shares)

// keeper, if idle runs short
recall(strategy_id, amount)

Straight answers

Before you ask.

Can I deposit today?

No. The vault contract is an unaudited prototype and goes to testnet first. The app opens with the vault.

Where does the yield come from right now?

In the current prototype, strategy integrations are simulated with internal accounting: no NEAR leaves the vault when capital is deployed, and yield is whatever the keeper reports, backed by NEAR the keeper attaches to the call. Real cross-contract integrations are the next step.

What does it cost?

A performance fee on harvested yield, capped at 20% by the contract. The contract has no deposit or withdrawal fee. Your first deposit pays a one-time storage cost of about 0.001 NEAR, and share conversions round down in favour of the vault.

Can the keeper take my funds?

The keeper can only move capital between idle liquidity and strategies the owner has whitelisted, within each strategy’s cap. It cannot withdraw to an arbitrary account or change the whitelist. The owner controls that whitelist, so the owner is the party you are trusting.

Can withdrawals be paused?

No. Pausing blocks deposit, deploy and rebalance. A withdrawal can still fail if idle liquidity is too low, until the keeper recalls capital.

Next / strategies

Where the capital goes.

Continue ↗