Skip to content
Enmonetic

Security

DRAFT

The control surface, disclosed in full.

Every privileged action in the contracts, who authorizes it and whether it waits out a timelock — including the controls that can stop a withdrawal.

At a glance

Control you can verify.

Every privileged action is disclosed — including the controls that can stop a withdrawal.

  • Enmonetic is a technology provider and never holds client assets. Depositors hold vault shares in their own wallets; the vault contract holds the underlying asset and deploys it only into whitelisted markets. The Partner API cannot sign transactions or create positions.

    Your walletSHARESVault contractASSETMarket AMarket BEnmoneticSOFTWARENO CUSTODYASSETS MOVE ONLY: WALLET ⇄ VAULT ⇄ WHITELISTED MARKETS

01 · Control surface

Roles and controls

Actual role holders are defined by each deployment and listed under Contracts & deployments.

Roles and controls
ActionAuthorized byTimelockSource
Rebalance between listed providers

Both ends must be on the provider list.

ExecutorNoRebalancer.sol (impl 0x133c…de21f) · rebalance
Add a providerTimelockYesRebalancer.sol (impl 0x133c…de21f) · addProvider
Remove an empty provider

Reverts while the provider still holds vault assets.

AdminNoRebalancer.sol (impl 0x133c…de21f) · removeProvider
Force-remove a provider that holds assetsTimelockYesRebalancer.sol (impl 0x133c…de21f) · forceRemoveProvider
Set entry providerAdminNoRebalancer.sol (impl 0x133c…de21f) · setEntryProvider
Grant / revoke rolesAdminNoRoleManager.sol · grantRole, revokeRole
Set management fee (max 5%) and performance fee (max 20%)

Fees are minted as vault shares to the treasury.

CuratorNoRebalancer.sol (impl 0x133c…de21f) · setManagementFee, setPerformanceFee
Set minimum deposit and maximum vault sizeCuratorNoRebalancer.sol (impl 0x133c…de21f) · setMinAssets, setMaxTotalAssets
Set treasuryTimelockYesRebalancer.sol (impl 0x133c…de21f) · setTreasury
Replace the timelockTimelockYesRebalancer.sol (impl 0x133c…de21f) · setTimelock
Pause deposits or withdrawals (separately)

Withdrawals can be paused.

WatchdogNoRebalancer.sol (impl 0x133c…de21f) · pause
Resume deposits or withdrawalsRecoveryNoRebalancer.sol (impl 0x133c…de21f) · unpause
Emergency withdraw

Pulls all assets from the chosen providers into the vault contract itself.

Watchdog (any single key with the role)NoRebalancer.sol (impl 0x133c…de21f) · emergencyWithdraw
Re-allocate after an emergency withdraw

Only to providers on the list.

RecoveryNoRebalancer.sol (impl 0x133c…de21f) · allocate
  • Withdrawals can be paused by the Watchdog role, and resumed only by the Recovery role.
  • Deposit and withdraw pause controls are separate.
  • Emergency withdraw is executed by any single key with the Watchdog role, without a timelock. This is a deliberate trade-off in favour of reaction speed.
  • After an emergency withdraw, funds stay in the vault until the Recovery role re-allocates them. There is no automatic re-arm.

What the keys cannot do

Only statements confirmed against the verified contract code are listed here (Rebalancer.sol, RoleManager.sol).

  • No role can send vault assets to an arbitrary address. Rebalance, emergency withdraw and re-allocation move assets only between the vault and providers on its list.
  • Withdrawals and redemptions are made by the share owner or by an address the owner has approved (ERC-4626 allowance).
  • Adding a provider, force-removing a provider that holds assets, changing the treasury and replacing the timelock all go through the Timelock contract (minimum delay 30 minutes).
  • Admin can remove a provider only when it holds no vault assets.
  • Management fee is capped at 5% and performance fee at 20% in code. Fees are paid as newly minted vault shares to the treasury; there is no withdrawal fee.
  • Emergency withdraw has no destination parameter: assets can only move into the vault contract itself.
  • The role that pauses (Watchdog) cannot unpause; only Recovery can resume deposits or withdrawals.

Role holders, the timelock delay and the treasury are set per deployment and listed under Contracts & deployments.

Emergency withdraw

  1. 1A Watchdog key calls emergency withdraw for one or more providers; all vault assets at those providers move into the vault contract.
  2. 2The provider is taken out of the active set — removed by Admin once empty, or force-removed through the Timelock.
  3. 3Normal allocation resumes only when the Recovery role re-allocates the idle assets. There is no automatic re-arm.

Three levels of reaction to risk

  1. Level 1 · Planned rebalance

    A pool's score drops below its current allocation limit — the position is reduced in the next rebalancing cycle.

  2. Level 2 · Circuit breaker

    A hard gate fails in an open position, utilization exceeds 90% or a sentinel alert fires — liquidity moves to the idle buffer and new allocations stop until conditions normalise.

  3. Level 3 · Emergency withdraw

    A critical behavioural signal — a Watchdog key pulls liquidity from providers back into the vault contract.

02 · Contracts & deployments

Contracts and deployments

TBD

No production deployment yet. Addresses, versions, role holders and timelock delays will be listed here at launch.

03 · Audits

Independent reviews

Each deployment is compared with the commits each audit covers. A review of one revision does not cover a different one.

Independent security reviews will be published here.

04 · Bug bounty

Bug bounty

TBD

Program details will be published here.

05 · Risk & resilience

Exposures and how they are handled

ExposureWhat can happenSignalResponse
Smart contracts & adaptersA bug in the vault, rebalancer or a provider adapter leads to loss or locked funds.Audit findings, bug bounty reports, anomalous contract state.Pause deposits and/or withdrawals; emergency withdraw into the vault contract; fix and redeploy through the timelock.
Underlying markets — credit channelBad debt in a market lending our asset: collateral cannot be liquidated at a price that covers borrowed funds.CRA structural and positional contours: concentration, collateral quality, HF buckets, stress scenarios, liquidation feasibility.Hard gate sets allocation to zero; score ladder reduces limits; circuit breaker or emergency withdraw.
Underlying markets — liquidity channelA run on withdrawals pushes utilization to 100%, or governance freezes reserves; assets cannot be withdrawn from the market for a period.Utilization above 90%, frozen / paused market flag, exit-time stress versus the vault's exit SLA.Circuit breaker to idle buffer; stop new allocations; withdrawals from that market wait for liquidity.
Stablecoin & networkThe vault asset loses its peg, is frozen by its issuer, or the network is congested or halted.Peg deviation, issuer actions, network status.Pause controls; disclosure. Stablecoin issuer risk cannot be diversified inside a single-asset vault.
Privileged configurationA role key is compromised or misused.Unexpected admin transactions, scheduled timelock changes.Provider changes wait out the timelock and are published as pending; multisig role holders; emergency withdraw destination is hard-coded.
Indexing & APIIndexer or API outage shows stale or missing data.Uptime monitoring; data age.Stale data is labelled as delayed, never shown as current. On-chain state remains the source of truth. A stale risk score blocks allocation.
Integration credentialsA partner's API credentials leak.Unusual API activity.Credential rotation. The Partner API cannot sign customer transactions or create on-chain positions.
Customer actionsWrong network, unlimited approvals, phishing front-ends.—Exact-amount approvals by default; confirmation screen shows chain, token, receiver, amounts in asset and shares, and fees; contract addresses only from the published deployments list.

Exit behavior

  • Redeeming burns shares and returns the asset from the vault's idle balance and, if needed, from underlying markets.
  • Execution depends on underlying market liquidity, contract state (including pause) and network conditions. No exit time is promised.
  • maxWithdraw and maxRedeem report what can be exited at a given moment.

06 · Incident disclosure

Incident disclosure policy

Security incidents affecting user funds or contract state are disclosed on this page and in the risk events feed, with a timeline, affected vaults and actions taken. Report vulnerabilities to the security contact below.

security@enmonetic.com