Everstrat Docs home
Operations

Current deployments

Ethereum mainnet settings, exit liquidity, role holders, and governance state at block 26,226,476.

Verification boundary

This read-only snapshot is pinned to Ethereum mainnet block 26,226,476 (October 19, 2026, 11:59:35 UTC), hash 0x8c8b9f242d4b1513b6bd8d6b8502db03ce3581a590508239980d63c28b138029. It does not refresh automatically. The app uses chain ID 1.

The tables above the historical October 15 recheck all use the October 19 snapshot. The recheck preserves the earlier migration state.

Entry remains invite-gated: Whitelist.disabled() returned false. A deployed address or a merged PR is not an announcement of unrestricted access.

Registered contracts

At this block, the 10 registered addresses returned by Registry.getContractsAndKeys() matched the canonical contract-address reference. That reference also lists Registry itself and the timelock holding ADMIN_ROLE, for 12 addresses in total. Upgradeable components are listed at their proxy addresses, which integrations should call.

Live settings

GetterResult at the snapshot blockMeaning
AMM.connectorWeight()0.9 × 10^18Entry price is base price divided by 0.9
AMM.minBatchExitETH()0.001 ETHMinimum size of a queued exit; it does not apply to mints
StrategyManager.performanceFeeBps()150015% of eligible accrued Uniswap V3 LP fees; it is not charged on deposits
StrategyManager.daoTreasury()0x1780C78eB50cD28dC349CEA8452eD1F7206D8fF9Recipient of fee EVE
Timelock.getMinDelay()172800 seconds48-hour scheduling delay
Controller.version()1.1.0018 executed; ADMIN or KEEPER may move a single strategy's funds into Controller
Both keeper executors' version()2.1.0-mimicMimic executor contracts
QueueKeeperExecutor.minBatchAge()86400 secondsA batch can be priced automatically once it is 24 hours old
StrategyKeeperExecutor.controllerReserveETH()0.05 ETHController reserve target
StrategyKeeperExecutor.minWithdrawETH()0.0001 ETHStrategy withdrawal threshold
StrategyKeeperExecutor.exitLiquidityTargetETH()0Automatic AMM float top-up disabled
Whitelist.disabled()falseInvite checks remain active

The three-day queue processing window starts after pricing and is separate from the keeper's minimum batch age. Expiry and cancellation rules are in The redemption queue.

Exit liquidity at this block

ReadResult (wei)
AMM ETH balance0
AMM.lockedForClaims()0
AMM.freeBalance()0

AMM held no ETH and had no free balance. Every new successful positive-size exit at this block would therefore queue, subject to the queued minimum and other checks. Deposits are forwarded to Controller, and exitLiquidityTargetETH = 0 disables routine AMM float top-up. The contracts still settle an exit immediately when free balance covers it, and authorized liquidity transfers can raise free balance. Recheck it before assuming an immediate exit is available. This snapshot does not establish historical exit counts.

Registered strategies

StrategyManager.strategies() returned these four v2 strategy addresses, registered by 019. The v1 strategies were drained and removed by 020; see Strategy migration. Registration does not guarantee that a strategy is healthy, funded, or executing at every moment.

PoolFee tierRegistered strategy
USDC/WETH0.30%0xfbcC73fA67F50D38FB318991C6CAbD5A6f64014A
USDC/WETH0.01%0x63B68CC99991429CA8a808125e446990Ae7fe669
WETH/USDT0.30%0xE80bfd65A55855ead8Cb5f7040031426CB718Cc5
UNI/WETH0.30%0xFC888a499c4172e393A258FbC6cAd1475a7e4129

Role holders

Registry roleHolders
ADMIN_ROLETimelock
SECURITY_ROLE0x7c128C1CF39822B4133F8E067F4bF14999c49846
KEEPER_ROLEQueueKeeperExecutor and StrategyKeeperExecutor
MINTER_ROLEAMM and StrategyManager
CONVERTER_CALLER_ROLEFour registered v2 strategies listed above
CONVERTER_CALLER_MANAGER_ROLEConverter
DEFAULT_ADMIN_ROLENo holders

The two Converter role assignments were read through Registry's getRoleMemberCount() and getRoleMember() at the snapshot block: four caller holders and one manager holder.

Both executors allow the Mimic caller 0x41153f0c36f8Fb5c38396573dDB487AC95a98256. This is an executor caller allowlist. The account itself holds no KEEPER_ROLE. Allowlisting alone does not prove uninterrupted off-chain task execution.

Strategy migration

Governance recordChain state at the snapshotEffect
018: Controller 1.1.0Done, executedAdded ADMIN access to the single-strategy withdrawal function (funds return to Controller only)
019: register v2 strategiesDone, executedRegistered the four v2 strategies
020: drain and remove v1All four operations Done, executedMoved the four v1 strategies' funds into Controller and removed them

Record 018 executed at block 26,176,319 (October 12, 12:13:23 UTC), in this transaction. The Controller proxy's implementation slot points to 0xd4f4152a887253CFdD23d0289951176Ec13cd55D.

019 and 020 executed on October 19, 2026, between blocks 26,226,427 and 26,226,432. 020's operations name 019 as their timelock predecessor, so 019 executed first.

OperationRecordBlockExecution transaction
0xf558cda6b3831a4fb393278e368ff3b319c04696e37ebb034d31c463fc9ed6a601926,226,4270xffad87e1…5fa9
0xfa9e716cf5547d760c68e8758a4900a0644df7490af3fbee8a9ccf56ed7493d502026,226,4280x4eaa06d6…680f
0xe9438cb7438f47c22b1e74477c013d86870cb08f7080080844d3532dacef75c802026,226,4290x469b60d0…d56c
0xe680e96963678090ac5854516999bf7c770284e622e66c014e04c689b9265bd902026,226,4300x13b895e8…6959
0x93ee86d5f12f2b739647a886d51e7dce3baeb77c02809d4c0d10fcf3b81f4cd202026,226,4320x0bb24561…b44f

The linked proposal files describe intended payloads; their older status prose is not the authority for this pinned chain state.

Retired v1 strategies

At the snapshot block the retired v1 strategies were absent from StrategyManager.strategies(), held no CONVERTER_CALLER_ROLE, and reported navInETH() = 0:

PoolRetired v1 address
USDC/WETH 0.30%0x5E12FFD5e0F69d37B581D06b68ad6c53609cac38
USDC/WETH 0.01%0x59C476c1817b23791d96F35b9f468E6d9A242252
WETH/USDT 0.30%0x3Fb6B9174427CA4FF38728398F4F4CB526F66501
UNI/WETH 0.30%0x956fE55DB50527E75c1fcA679adE509AD89cAFDd

Migration recheck: October 15, 2026

A read-only recheck of Controller version, timelock states, and the registered strategy list was pinned to Ethereum mainnet block 26,199,960, October 15, 2026, 19:18:11 UTC, hash 0x47bf3b2566e613ed44e5109dfcef849681ff828f06643dfae3a5f7440bbd0a08. This historical check covered only the three reads named above. The current balances, settings, and role holders use the October 19 snapshot at the top of this page.

ReadResult at block 26,199,960
Controller.version()1.1.0
018 operation 0x8cc3710fc1e770419105d3974350f2de05eb8a575e8057bf602fd28830b7c98a3 — Done
019 operation 0xf558cda6b3831a4fb393278e368ff3b319c04696e37ebb034d31c463fc9ed6a62 — Ready
020 USDC/WETH 0.30% operation 0xfa9e716cf5547d760c68e8758a4900a0644df7490af3fbee8a9ccf56ed7493d52 — Ready
020 USDC/WETH 0.01% operation 0xe9438cb7438f47c22b1e74477c013d86870cb08f7080080844d3532dacef75c82 — Ready
020 WETH/USDT 0.30% operation 0xe680e96963678090ac5854516999bf7c770284e622e66c014e04c689b9265bd92 — Ready
020 UNI/WETH 0.30% operation 0x93ee86d5f12f2b739647a886d51e7dce3baeb77c02809d4c0d10fcf3b81f4cd22 — Ready
StrategyManager.strategies()The four addresses now listed under Retired v1 strategies

019 and 020 had not executed at this block. The passing of their ready-at times did not activate the migration. They subsequently executed on October 19, as recorded under Strategy migration. The strategy changelog links the execution to the implementation and proposal history; contract updates record the separately executed Controller upgrade.

Data and source references

Current app configuration uses the Goldsky mainnet subgraph.

Addresses and deployment configuration are maintained in everstrat-xyz/app, at src/config/index.ts and subgraph/config/deployments/mainnet.json. Proposals and execution receipts live in everstrat-xyz/governance.

For current authorization and settings, read the contracts at a pinned block. For intended changes, read the proposal. Neither repository main nor this dated page automatically proves a transaction has executed.

Last updated on

On this page