Shadow Mainnet Testing. Public deposits not yet open.See roadmap →

Why Multyr

Allocating capital across DeFi shouldn't require a second job

If you manage capital across multiple DeFi protocols, you already know the operational overhead. You monitor yields, watch integrations, and rebalance when conditions shift. This works up to a point. Then it doesn't.

The problem with manual allocation

You can't enforce limits on yourself

When you manage capital manually, exposure caps, loss caps, and rebalancing discipline are policy, not code. Policy breaks under stress. Code does not.

You can't monitor 24/7

DeFi conditions shift in minutes. A manual allocator either misses moves or trades huge amounts of attention to keep up. Neither scales cleanly.

Rebalancing costs compound

Every manual reallocation pays gas and slippage. Without explicit cost-benefit gating, operational friction eats into returns over time.

No audit trail by default

Manual allocation leaves decisions scattered across wallet history, dashboards, and notes. Reporting becomes reconstruction instead of recordkeeping.

Why not a generic yield aggregator?

Yield aggregators optimize for one thing: highest yield available. They do not typically enforce per-strategy exposure caps, per-protocol exposure caps, cost-benefit gating on rebalances, or on-chain governance with timelock.

Multyr is different by design: the objective function is rule-based allocation within encoded constraints, not yield maximization.

What Multyr does differently

  • allocates capital across Strategy Vaults according to encoded rules
  • enforces hard exposure and loss caps at allocation time
  • rebalances only when expected benefit exceeds execution cost
  • provides on-chain observable execution trail
  • governs parameter changes through multisig plus 48h timelock

Fit and non-fit

Suitable if you:

  • manage size and want systematic exposure
  • require enforceable constraints, not policy
  • prefer deterministic execution over discretionary override
  • accept that rule-based allocation won't capture every tactical opportunity

Not a fit if you:

  • prefer discretionary, opportunistic allocation
  • optimize for short-term tactical yield
  • need override authority on allocation decisions
  • cannot tolerate periods where the protocol holds liquid buffers instead of deploying