Skip to content
Enmonetic

Solutions · Licensed operators

DRAFT

Your managed product, on Enmonetic rails.

Brokers and asset managers build permissioned vaults on Enmonetic infrastructure. You set the provider whitelist and serve your clients under your own licence; Enmonetic supplies the technology.

Enmonetic Protocol

One engine under every product.

Particle swarm optimisation splits liquidity across vetted lending markets; the Collateral Risk Analyzer vetoes unsafe ones first. It runs Lemonaire® today and the liquid part of Earn and Yield-as-a-Service.

01 · Problem

The problem

  • Clients ask for stablecoin allocation products.
  • Building vaults, allocation logic and risk monitoring is outside the operator's core stack.
  • Regulators expect clear accountability and a documented control surface.

02 · How it runs

How it works for an operator

  1. 01Configure a permissioned vault: asset, provider whitelist, fees, depositor whitelist.
  2. 02The engine allocates only within your whitelist and CRA limits.
  3. 03Role holders (multisig, timelock) are defined per deployment and disclosed.
  4. 04Report to clients and your regulator from Partner API data and on-chain records.
Who is responsible for what
Client relationship, suitability, onboardingOperator
Regulatory licence and obligationsOperator
Provider whitelistOperator
Vault contracts, engine, Partner APIEnmonetic (technology provider)
SettlementOn-chain

03 · Scope

What you don't have to build

Partners share the performance fee on yield actually generated. Economics

  • A risk teamCRA scores the collateral behind each market and vetoes unsafe ones before every allocation.
  • Rebalancing operationsThe engine re-splits liquidity as rates and utilisation move.
  • Vault contractsStandard ERC-4626 shares your app reads with convertToAssets.
  • ReportingAllocations, rebalances and history through the Partner API and CSV.
  • A user interfaceUse the public app, or embed Earn in your own screens.
  • Monitoring and alertsRisk events, pauses and pending timelock changes arrive as Partner API webhooks.

04 · Model

Model the economics.

Enter your own figures. The example uses an illustrative 8.5% APY; real rates are variable.

Float yield

ILLUSTRATIVE MODEL

APY (fixed for this example)8.5%

Enmonetic performance fee15% of yield

What your company earns a year by putting part of its idle stablecoin float into Earn.

Money in Earn
$5,000,000
Yield earned / year at 8.5%
$425,000
Enmonetic performance fee (15% of yield)
− $63,750
You keep / year
$361,250
  1. 1 Average idle float — The money that usually sits idle on your balance sheet — pre-funded payouts, settlement buffers, client balances awaiting transfer. The figure is an example; enter your own.
  2. 2 Share put into Earn — How much of that float you put into Earn. The rest stays with you as an instant-liquidity buffer.
  3. 3 Hours a day in Earn — How many hours a day the money stays in Earn. 24 = around the clock; lower it if you pull funds back every day for settlements.

Illustrative model. Not a rate quote, projection of returns or payout record.

Discuss these assumptions with the team

05 · Integration

Integration model

  • Permissioned ERC-4626 vaults with a depositor whitelist.
  • MPC custody integration (e.g. Fireblocks) for operator wallets.
  • Partner API for reporting and reconciliation.

06 · Risk

Risk controls

  • CRA gates and score ladder apply inside the operator's whitelist.
  • Timelocked provider changes; separate deposit and withdraw pause controls.
  • Emergency withdraw returns liquidity to the vault contract only — it has no destination parameter.
  • Withdrawals depend on market liquidity and can be paused.

Control

What we can't do with the funds.

For the vault contracts of the protocol. Each statement is checked against the contract code.

Full security page
  1. 01

    No key can send vault funds to an arbitrary address

    Rebalances, emergency withdraws and re-allocations move assets only between the vault and providers on its list. Withdrawals are made by the share owner or with their approval.

  2. 02

    New markets wait behind a timelock

    Adding a provider, force-removing one that holds funds or changing the treasury is queued first and executes only after a public delay.

  3. 03

    Fees are capped in code

    Management fee at most 5%, performance fee at most 20% of yield, paid as vault shares to the treasury. No withdrawal fee.

  4. 04

    The key that pauses cannot unpause

    Watchdog pauses deposits or withdrawals separately; only the Recovery role can resume them. The app shows when either is paused.

FAQ

Questions from licensed operators & asset managers.

Who is responsible to our clients and regulator?
You are. Enmonetic supplies the technology; the operator serves clients under its own licence and remains responsible for suitability, disclosures and reporting.
Can we restrict which markets the vault uses?
Yes. You set the provider whitelist for your vault. The engine allocates only within it and within CRA limits, and whitelist changes go through the timelock.
Can we restrict who deposits?
Permissioned vaults support a depositor whitelist, configured per deployment.
Who holds the privileged roles?
Role holders — multisigs and the timelock — are defined per deployment and disclosed on the Security page.

Find your way in.

Walk through the engine, the controls and a sandbox integration for licensed operators & asset managers.

Talk to the team