Everstrat Docs home
Changelog

Changelog

New features, improvements, and fixes across Everstrat.

All 59 dated updates across five components, from March 6, 2026 to October 19, 2026. Dates are UTC.

UniCL v2 migration executed

Governance 019 registered four v2 strategies on the existing pools. All four 020 operations then moved the v1 strategies' funds into Controller and removed the old instances. At the October 19 snapshot, only the four v2 strategies were registered and held the Converter caller role; the retired v1 instances reported zero NAV.

Registration alone does not establish that the v2 instances are funded or continuously executing.

Execution evidence

019 executed at block 26,226,427 in this transaction. The four 020 operations followed at blocks 26,226,428–26,226,432. The deployment snapshot records all five operation IDs and execution transactions, checked at block 26,226,476, 11:59:35 UTC. It also lists the registered v2 and retired v1 addresses.

View in Strategies

See protocol earnings in Metrics

Metrics now shows the protocol’s available fee earnings in ETH and USD.

  • Protocol Earnings joins NAV and deployed capital in Protocol overview.
  • Pending Redemptions moves to Market & liquidity.
  • Snapshot sharing moves to Admin Insights; existing shared links still work.
Everstrat Metrics showing Protocol Earnings and Pending Redemptions, with numbered highlights.

1. Protocol Earnings now appears in Protocol overview. 2. Pending Redemptions moves to Market & liquidity.

Development capture for this release. Figures are a historical snapshot.

Admin Insights campaign link builder with Copy snapshot link highlighted in its new location.

1. Copy snapshot link now lives in the Campaign link builder in authenticated Admin Insights.

Development capture for the October 14 release; analytics figures are historical.

Details & sources

Protocol Earnings and Admin snapshot sharing

Production deployment. Metrics gained Protocol Earnings in ETH with a USD equivalent. Pending Redemptions moved to Market & liquidity, and the Instant Liquidity headline card was removed. Copy snapshot link moved to the Campaign link builder in authenticated Admin Insights. Existing public snapshot URLs and image routes remain available.

Source: app #15, production commit 47c0756. Deployment 7062176549 reported success at 09:52:32 UTC. Earnings combine pending strategy fees and attributable harvested EVE; see Metrics.

View in App

Share a snapshot that stays the same

Shared protocol snapshots now keep the figures from the finalized block captured when you copied the link.

  • Snapshot links get a matching social preview.
  • Ordinary app links use the Everstrat brand image.
  • The sharing control later moved from Metrics to Admin Insights on October 14.
October 12 Metrics interface with the Copy snapshot link control highlighted; the control later moved to Admin.

1. Copy snapshot link in the October 12 interface. This control moved to Admin Insights on October 14.

Historical screen; figures are not current.

Public protocol snapshot page with the fixed timestamp and historical NAV and holder count highlighted.

1. Fixed timestamp. 2. NAV and holder count from that snapshot. The public link keeps this captured state, with a separate link to live Metrics.

Historical page captured on October 12; figures are not current.

Details & sources

Social previews and fixed-block snapshots

Production deployments. Added Open Graph/X images and metadata, followed by fixed-block protocol snapshot links. A snapshot URL retains its finalized-block image; ordinary app links use the brand preview. Invalid or unavailable snapshot requests fall back to the brand preview. The copy control was initially in Metrics and moved to Admin on October 14.

Sources: app #9 and app #10. Production deployments 7016719221 and 7021465978 reported success for merge commits 446a76e and e42e58b, respectively. Production sharing-client and artwork acceptance remained tracked separately in app #3.

View in App

Governance can now pull funds from one strategy into Controller

Controller 1.1.0 is active on mainnet, letting the admin timelock move a specific strategy's funds back into Controller for strategy migrations.

  • Funds always return to Controller; governance cannot send them to any other address.
  • The Controller proxy address stays the same.
  • Keeper access remains available; SECURITY gains no new permission.
Details & sources

Controller 1.1.0 activated

Executed on mainnet. Upgraded the Controller proxy to 1.1.0. The admin timelock can now call withdrawFromStrategy alongside the keeper, providing a governed path to move a specific strategy's funds back into Controller for migration. The function has no recipient parameter: StrategyManager always withdraws to the Controller, so governance cannot transfer strategy funds to any other address. SECURITY does not gain that permission. The proxy address remains unchanged.

Evidence: contracts #52, governance 018 payload, and execution receipt, block 26,176,319, 12:13:23 UTC. The receipt contains the implementation upgrade and timelock execution events. The proposal's older Scheduled wording predates this execution.

View in Contracts

Your Portfolio, separate from protocol Metrics

Follow your own position in Portfolio and the whole protocol in Metrics.

  • Switch your position chart between Return and Value, in USD or ETH.
  • View EVE market history with clearer loading and data-freshness feedback.
  • Mint-form scrolling and long error messages display correctly.
Portfolio position-history preview with Return/Value and USD/ETH controls highlighted. Example data.

1. Return / Value and USD / ETH controls. 2. Position history. Preview captured during chart development, using example data.

Details & sources

Portfolio and Metrics analytics

Production deployment. Separated personal Portfolio from protocol Metrics, preserving redirects from the former dashboard/stats routes. Added connected-wallet position history with Return/Value and USD/ETH controls, EVE market history, and clearer loading, stale-data, and error states. Queued exits remain in the position until processing changes the holding.

The development toolchain also moved to Node.js 24 and Bun 1.4.3, with read-only checks separated from autofixes. Source: tooling commit 3f5bb71.

Source: app #2, production commit d4cf1f5, deployment 6978600729 (success). The data work is described in Data & Integrations. Real connected-wallet reconciliation and visual acceptance remained tracked in app #12; deployment success alone does not resolve it.

Mint-form and branding fixes

Production deployment. Fixed mint-form scrolling and long error-message wrapping, and standardized Everstrat branding across headers.

Source: app #7, production commit 860fec9, deployment 6986524734 (success).

View in App

Position history follows your actual EVE holdings

Portfolio reconstructs positions from indexed mints, burns, transfers, and redemption-price snapshots.

  • Queued exits stay in the position until processing changes the holding.
  • Valuation uses lifetime prices, and usable history survives refresh failures.
Details & sources

Connected-wallet position reconstruction

Merged. Reconstructs EVE holdings from indexed mints, burns, transfers, and redemption-price snapshots. Queued and slippage-closed exits remain part of the position until processing changes the holding. Position history uses lifetime prices for valuation and preserves usable history through refresh failures. The user-facing rollout is recorded in App updates.

Source: app #2, including e3d29f7. Synthetic checks and deployment success do not establish the outstanding real-wallet acceptance tracked in app #12.

View in Data & integrations

Wallet connections can recover

imToken no longer waits indefinitely for a permissions response.

  • Other injected wallets show a retryable timeout after 60 seconds.
  • WalletConnect keeps its QR connection flow.
Wallet chooser captured during development of wallet connection recovery, with WalletConnect highlighted.

1. WalletConnect remains available in the wallet chooser alongside detected injected wallets.

Captured during development of this recovery fix on October 6. This image shows the connection interface; the timeout and retry behavior is described above.

Details & sources

Wallet connection recovery

Production deployment. imToken requests accounts directly instead of waiting indefinitely for wallet_requestPermissions. Other injected wallets receive a retryable 60-second timeout; WalletConnect retains its QR flow. Real imToken Android validation remained an explicit follow-up.

Source: app #1, production commit 669ab83, deployment 6930028485 (success). This supersedes the original monorepo PR after extraction.

View in App

UniCL v2 makes better use of inventory

The new implementation sizes swaps for the position’s actual token ratio and uses leftover inventory in an alternate position.

  • Deposits can add liquidity without rebuilding the whole position.
  • Withdrawals use idle inventory first, then remove the liquidity needed.
  • Existing static strategies still require deployment and migration.

Subsequent mainnet activation: the v2 registration and v1 removal operations executed on October 19, 2026. Migration execution and evidence.

Details & sources

UniCLStrat 2.0.0 implementation

Merged. Added ratio-aware inventory swaps, an alternate position built from actual leftovers, and incremental liquidity additions. Withdrawals use idle inventory before partially burning positions, size swaps against the actual route, and fully unwind near-full withdrawals. Partial collection rebases the LP-fee snapshot so returned principal does not become performance-fee income. Shared logic moved into the linked UniCLStratLib.

Source: contracts #53, merge 157129b. Mainnet activation followed through new deployments and the October 19 migration.

View in Strategies

Missing data stays missing

Insights stops treating incomplete collection as complete results.

  • Funnels preserve missing values and respect the selected period.
  • Revised reports replace earlier versions atomically.
  • Partial Telegram collection is shown separately.
Details & sources

Insights completeness and attribution corrections

Committed. Incomplete protocol index coverage is rejected instead of treated as complete. Conversion funnels preserve missing data and respect the selected period; weekly metrics retain unknown values. Revised analytics reports replace prior versions atomically, and partial Telegram collection is distinguished from complete collection.

Sources: ebcef8f, e10f1a0, 599ab54, and 85030fc.

View in Data & integrations

Controller 1.1.0 is ready for upgrade

The implementation letting ADMIN move a single strategy's funds into Controller merged. Its mainnet proxy upgrade followed on October 12.

Details & sources

Controller 1.1.0 implementation merged

Merged. Added ADMIN authorization to the single-strategy withdrawal function, which returns funds to Controller only, and changed version() from 1.0.0 to 1.1.0. This source milestone preceded the October 12 proxy upgrade; it did not itself activate the permission on mainnet.

Source: contracts #52.

View in Contracts

Clearer strategy names and Admin Insights

Strategies are labeled by their pool pair and fee tier. Admin Insights brings channel and protocol activity into one view.

  • Inspect each Telegram chat separately.
  • Run a collection on demand from Admin.
Details & sources

Admin Insights and clearer strategy labels

Committed. Added an authenticated Insights tab combining analytics, social-channel, and protocol data, with per-chat Telegram views and an on-demand collection control. Strategy labels and history resolve pool pairs and fee tiers, and strategy details identify the paired token and pool.

Sources: 8aecb4a, 7168b67, a0ab7b5, and 09797e7. Subsequent completeness corrections are recorded in Data & Integrations.

View in App

The 15% performance fee is enabled

The protocol now charges 15% of eligible accrued Uniswap V3 LP trading fees.

  • The fee is settled by minting EVE to the DAO treasury.
  • Deposits and general NAV growth are not the fee basis.
Details & sources

Performance fee enabled

Executed on mainnet. Changed StrategyManager.performanceFeeBps from 0 to 1500 (15%). The fee applies to eligible accrued Uniswap V3 LP fees and is settled by minting EVE to the DAO treasury. It is not a fee on deposits or all NAV growth.

Evidence: governance 014, execution receipt, block 26,061,384, 11:39:47 UTC. See Performance fee.

View in Contracts

UNI/WETH joins the strategy basket

The re-deployed UNI/WETH 0.30% strategy is registered, bringing the basket to four strategies at execution.

Details & sources

UNI/WETH 0.30% strategy registered

Executed on mainnet. Registered the re-deployed UNI/WETH strategy with deposit/withdrawal weights 10 / 10, bringing the registered basket to four strategies at that execution. This is governance record 017. The earlier record 015 was withdrawn before timelock scheduling and did not activate its proposed strategy.

Evidence: governance 017, execution receipt, block 26,061,446, 11:52:11 UTC.

View in Strategies

Smaller withdrawals and a settlement reserve

The strategy keeper can withdraw as little as 0.0001 ETH, and targets a 0.05 ETH reserve in Controller for settlement.

Details & sources

Smaller withdrawal threshold and Controller reserve

Executed on mainnet. Changed minWithdrawETH from 0.01 to 0.0001 ETH and controllerReserveETH from 0 to 0.05 ETH. These settings allow smaller strategy withdrawals and retain a Controller reserve for queue settlement.

Evidence: governance 016. The threshold call executed at block 26,061,390, 11:40:59 UTC; the reserve call at block 26,061,396, 11:42:11 UTC.

View in Automation

A clearer view of period return

The dashboard shows EVE redemption-price return for the measured period, without converting it into an annual rate.

Details & sources

Redemption-price return shown without annualization

Committed. Removed annualized EVE redemption-price return from the dashboard calculation and copy. Period return is not a forecast of future annual yield.

Source: 54582c4.

View in App

Gas budgets depend on the job

W2’s new fee policy gives each action its own budget and increases urgency as priced exits approach expiry.

  • Withdrawals and rebalances use deadline-aware ceilings.
  • Deposits, harvests, and liquidity top-ups use amount-based budgets.
  • Operators must redeploy the function and recreate its trigger.
Details & sources

Per-action W2 gas-fee policy

Merged. Replaced one flat fee policy with action-specific ceilings. Withdrawal shortfalls use a deadline ramp, rebalances can inherit that urgency, sync uses a lower ceiling, and deposit, harvest, and exit-liquidity actions use an amount-based budget. The function continues to forward the on-chain checker's payload bytes. Invalid fee inputs produce configuration-error logs.

Source: keepers #30. Operator action: deploy the new function and recreate the trigger with its updated inputs. The merge date does not establish when that trigger became active.

View in Automation

Better feedback when a transaction is interrupted

Wallet submission and recovery now explain what happened and help you resume an interrupted flow.

Details & sources

Transaction submission and recovery

Committed. Hardened wallet submission and transaction recovery, including feedback when a flow must resume after interruption. Updated transaction status presentation and its orb states.

Sources: 6f0ced0 and 2657ae0. See Transaction modal and status UX.

View in App

UNI valuation and accounting support

The UNI/USD price feed and supported-token registration are active, preparing the protocol for the UNI/WETH strategy.

Details & sources

UNI oracle and supported-token registration

Executed on mainnet. Added the UNI/USD feed with a 4200-second staleness bound and added UNI to StrategyManager's supported ERC-20 set. These calls prepared token valuation and accounting; the UNI/WETH strategy was registered on September 26.

Evidence: governance 013. The feed call executed at block 26,036,243, 23:15:47 UTC, and the supported-token call at block 26,036,248, 23:16:47 UTC.

View in Contracts

Rebalance only when there is work to do

The strategy health check no longer requests a rebalance while a pool is non-calm. Existing instances need migration to receive this implementation change.

Details & sources

Rebalance health predicate corrected

Merged. isHealthy() reports no actionable rebalance for paused or non-calm pools. The rebalance trigger now requires a calm, unpaused, drifted strategy. Deposit capacity still independently falls to zero when paused or non-calm. This change applies to newly deployed builds; existing static instances require migration. The interim off-chain mitigation is recorded in Automation.

Source: contracts #51.

View in Strategies

Position history and clearer exit feedback

Dashboard charts show historical activity, and mint/burn feedback includes the pending exit batch.

  • Transaction status gains visual feedback.
  • Navigation keeps the app shell and mint-price marquee mounted.
Details & sources

History charts and queued-exit feedback

Committed. Added dashboard history analytics and charts, a transaction-status orb, and mint/burn feedback that includes the pending batch ID. The application shell and mint-price marquee remain mounted across route changes.

Sources: f4b9884, 42abc74, and 63bd499.

View in App

Invitation links open the access flow, and invite-code labels are easier to follow.

  • Admin views gain wallet-state and activity history.
  • Account history is separated from the actions you can take now.
Details & sources

Committed. Added invitation links and the access flow, refined invite-code labels, and expanded admin wallet-state and activity views. Account history is distinct from currently available actions.

Sources: 3064b38, d62d800, and 43dcdfb.

View in App

Skip rebalance batches that can only revert

W2 skips a rebalance when every selected strategy is non-calm, avoiding guaranteed no-op work.

  • Read failures are logged separately and emit no intent.
  • Other actions keep the on-chain checker’s exact payload.
Details & sources

Suppress guaranteed no-op rebalance batches

Merged. W2 suppresses a Rebalance intent when every selected strategy is non-calm and the batch would therefore only revert. Read failures emit no intent and are logged separately. Other actions retain the checker's exact payload, and ambiguous payloads retain the prior relay behavior. This is an off-chain mitigation for static strategies with the older health predicate.

Source: keepers #28. Operator action: redeploy the function and recreate its trigger against the new CID. The subsequent strategy health-predicate fix is a separate implementation change.

View in Automation

Know the minimum before you queue an exit

The exit form shows how much EVE is needed to meet the queued-exit minimum.

  • The displayed minimum rounds upward.
  • A small quote buffer helps with NAV movement before submission.
Details & sources

Queued-exit minimum and NAV-movement buffer

Committed. The exit form shows the minimum EVE needed to queue an exit and rounds the displayed minimum upward. Requested ETH is buffered to reduce failures from small NAV movements between the quote and submission. These changes do not guarantee an immediate exit.

Sources: a3c3350, 35afae5, and 4dbcc6f.

View in App

Mimic is authorized to call both executors

The Mimic smart account is added to the queue and strategy executor allowlists.

  • This authorizes executor calls without granting the account a Registry keeper role.
  • Authorization alone does not establish continuous off-chain task execution.
Details & sources

Mimic caller authorized on both executors

Executed on mainnet. Added the Mimic smart account to the QueueKeeperExecutor and StrategyKeeperExecutor caller allowlists. The smart account can call executor perform(); it does not itself acquire Registry's KEEPER role. This authorization does not prove ongoing task availability or a particular function CID.

Evidence: governance 012. The queue executor call executed at block 25,997,085, 12:02:59 UTC; the strategy executor call at block 25,997,092, 12:04:23 UTC.

View in Automation

More margin around the USDT feed heartbeat

The USDT price-feed freshness window increases from 24 hours to 24 hours 30 minutes.

Details & sources

USDT feed staleness margin

Executed on mainnet. Increased the USDT/USD staleness interval from 86400 to 88200 seconds to allow heartbeat jitter while preserving a finite freshness bound.

Evidence: governance 010, execution receipt, block 25,989,820, 11:44:47 UTC.

View in Contracts

WETH/USDT joins the strategy basket

The WETH/USDT 0.30% strategy is registered with deposit and withdrawal weights of 45 / 45.

Details & sources

WETH/USDT 0.30% strategy registered

Executed on mainnet. Added the WETH/USDT strategy with deposit/withdrawal weights 45 / 45. Registration also authorized the strategy as a Converter caller.

Evidence: governance 011, execution receipt, block 25,989,831, 11:46:59 UTC.

View in Strategies

ETH and USDC feed freshness windows adjusted

Oracle freshness bounds gain a margin for normal feed-update timing: 70 minutes for ETH/WETH and 23 hours 30 minutes for USDC.

Details & sources

ETH and USDC feed staleness margins

Executed on mainnet. Increased the WETH and native-ETH feed staleness bounds from 3600 to 4200 seconds, and USDC from 82800 to 84600 seconds.

Evidence: governance 008. Execution receipts: WETH at block 25,983,142, 13:24:11 UTC; native ETH at block 25,983,200, 13:35:59 UTC; and USDC at block 25,983,206, 13:37:11 UTC.

View in Contracts

The first two USDC/WETH strategies are registered

USDC/WETH strategies join the basket for the 0.30% and 0.01% pools, with weights of 40 / 40 and 15 / 15.

Details & sources

First two USDC/WETH strategies registered

Executed on mainnet. Added USDC/WETH strategies for the 0.30% and 0.01% pools with deposit/withdrawal weights 40 / 40 and 15 / 15, respectively. Each registration granted Converter caller permission.

Evidence: governance 009. The 0.30% registration executed at block 25,983,233, 13:42:35 UTC; the 0.01% registration at block 25,983,238, 13:43:47 UTC.

View in Strategies

Risk acknowledgment before your first mint

The first-mint flow asks you to acknowledge the risks of the experimental mainnet protocol.

Details & sources

First-mint risk acknowledgment

Committed. Added explicit risk acknowledgment before the first mint and updated mainnet, testing-phase, privacy, and risk wording. Entry remains subject to the invite gate.

Sources: 2f4deb7 and e72f952.

View in App

USDT valuation and accounting are enabled

USDT gets a USD price feed and joins the protocol’s supported-token set.

Details & sources

USDT valuation and accounting support

Executed on mainnet. Registered the USDT/USD feed with an initial 86400-second staleness bound, then added USDT to StrategyManager's supported-token set.

Evidence: governance 006 and 007. The feed registration executed at block 25,968,966, 13:59:11 UTC; the supported-token registration at block 25,970,736, 19:53:47 UTC.

View in Contracts

USDT behavior tested on a mainnet fork

New fork tests exercise UniCLStrat with real USDT behavior before strategy registration.

Details & sources

Real-USDT fork coverage

Merged. Added mainnet-fork coverage for UniCLStrat against real USDT behavior. This is validation of the implementation, not the strategy's registration date.

Source: contracts #50.

View in Strategies

Bootstrap settings checked against mainnet

Fork tests validate UniCLStrat’s mainnet bootstrap parameters before registration.

Details & sources

Bootstrap configuration fork checks

Merged. Added fork validation of UniCLStrat mainnet bootstrap parameters before registration.

Source: contracts #48.

View in Strategies

USDC accounting and Uniswap conversion are enabled

USDC joins the supported-token set, and the Uniswap V3 Converter adapter is authorized.

Details & sources

USDC accounting and Uniswap adapter enabled

Executed on mainnet. Added USDC to StrategyManager's supported ERC-20 set and allowed the Uniswap V3 Converter adapter. Adapter authorization is separate from registering a strategy.

Evidence: governance 004 and 005. The USDC call executed at block 25,933,686, 15:57:47 UTC; the adapter call at block 25,934,444, 18:30:11 UTC.

View in Contracts

USD price feeds for USDC and WETH

The first USDC/USD and WETH/USD feeds are registered on mainnet.

Details & sources

USDC and WETH USD feeds registered

Executed on mainnet. Configured the USDC/USD and WETH/USD reference feeds with initial staleness bounds of 82800 and 3600 seconds. Later bounds are recorded above.

Evidence: governance 003, execution receipt, block 25,925,347, 12:02:11 UTC.

View in Contracts

Each timelock batch call has its own history

Indexed governance records now distinguish individual calls by operation ID and call index.

Details & sources

Timelock calls indexed individually

Committed. Timelock call records are identified by operation ID and call index, preserving individual calls within a batch rather than treating the operation as a single call.

Source: 82f9179.

View in Data & integrations

The app moves to Ethereum mainnet

Network checks, contract configuration, and explorer links now target Ethereum mainnet. Access remains invite-gated.

Details & sources

Ethereum mainnet configuration

Committed. Moved the frontend and subgraph configuration to Ethereum mainnet, including contract addresses, explorer links, network checks, and analytics configuration. This source change is not an announcement of unrestricted access.

Source: 98688bc. Indexer details are in Data & Integrations.

View in App

The Everstrat EVE token is registered

The Registry points to the new token named Everstrat, with the symbol EVE. The unused bootstrap token is replaced.

Details & sources

Everstrat EVE token registered

Executed on mainnet. Repointed Registry's EVE key to the re-deployed token named Everstrat, symbol EVE. The original bootstrap token had no supply. Canonical token and proxy addresses are maintained in Contract addresses.

Evidence: governance 002, execution receipt, block 25,897,546, 15:01:59 UTC.

View in Contracts

Mainnet data, access, and governance indexing

The app and subgraph share mainnet deployment configuration. The indexer adds Whitelist records and scheduled, executed, and cancelled governance operations.

Details & sources

Mainnet source configuration and access/governance indexing

Committed. Added Ethereum mainnet deployment configuration shared by the app and subgraph. Extended indexing to Whitelist and Timelock state, including access records and scheduled, executed, and cancelled governance operations. Indexed history supports the UI; pinned chain reads remain the authority for current permissions and operation readiness.

Sources: 98688bc and 737cff7. The app network change and subgraph deployment are separate milestones.

View in Data & integrations

Enter with an invite code

Invite-code redemption replaces the team-password access flow. Rate limits for invite requests and voucher refresh followed on August 28.

Historical invitation interface with request and existing invite-code entry paths highlighted. Captured October 6, after the August introduction.

1. Request an invite code. 2. Enter with an existing code. These are the two invitation paths.

Later development capture from October 6, showing the access flow introduced in August. The email validation message comes from that capture.

Details & sources

Invite-code redemption

Committed. Replaced the team-password access path with invite-code redemption. Rate limiting for invites and voucher refresh followed on August 28.

Sources: 2dc82a5 and 42f4121 (August 28).

View in App

Everstrat branding and wallet-based Admin access

The app takes the Everstrat name. Administrators can sign in with Ethereum, and the whitelist feature is added.

Details & sources

Admin authentication and Everstrat branding

Committed. Added Sign-In with Ethereum admin authentication and an admin dashboard, introduced the whitelist feature, and renamed the application to Everstrat.

Sources: ad31792, 5f8c5e4, and 0f7bbda.

View in App

Keeper executors are rebuilt around a caller allowlist

Vendor-neutral keeper executors replace the CRE receivers. Any allowlisted automation address, such as a Mimic smart account, can call them.

Details & sources

CRE receivers replaced by caller-allowlist executors

Merged. Removed the CRE/Keystone receivers merged on August 14 (CREReceiverBase, CREQueueExecutor, CREStrategyExecutor) and replaced them with KeeperExecutorBase, QueueKeeperExecutor, and StrategyKeeperExecutor. Instead of forwarder and workflow-identity checks, the new executors admit calls from an ADMIN-managed caller allowlist (allowExecutorCaller), so any per-operator automation address can drive them. Executor version is 2.1.0-mimic. The PR passed through an intermediate Gelato-based version before the final Mimic-oriented naming; only the final state reached main. Off-chain migration and on-chain caller authorization have separate dates in Automation.

Source: contracts #46.

View in Contracts

Queue and strategy keepers move to Mimic

W1 and W2 are rebuilt as Mimic functions. W1 handles queue decisions; W2 relays the contract checker’s instructions.

  • Timestamp conversion, missing-map reads, and payload guards are fixed.
  • The old W4 watcher and Go plane are removed from the final merge.
Details & sources

Mimic W1/W2 functions

Merged. Replaced the earlier CRE/Gelato implementations with Mimic functions compiled from AssemblyScript to WASM. W1 retains queue decisions and cross-checks; W2 relays the contract checker's payload. Fixed millisecond/second conversion, missing-map access, AMM pause checks, and payload-length enforcement. Removed the old W4 freeze-watch and Go plane from the final merge.

Sources: keepers #24, W4 removal 24534c3, and W1 guards 7c58f2f. The final merged tree supersedes the PR description's earlier statement that W4 remained. The on-chain executors were replaced in contracts #46; caller authorization followed on September 17.

View in Automation

Queue scans spend their read budget on useful work

Historical CRE keepers skip unusable queue candidates, avoid pricing after a truncated scan, and split large user-list reads into chunks.

Details & sources

CRE-era queue selection and read-budget fixes

Merged. W1 skips expired candidates and continues to later processable batches instead of spending the read budget on an unusable head. A truncated request scan blocks new pricing. W2 excludes unpriced/expired batches from its needs scan and chunks large user-list reads. These entries describe the historical CRE implementation before the Mimic migration.

Sources: keepers #21 and #22.

View in Automation

The first keeper implementation reaches main

W1 queue decisions, W2 strategy decisions, and the historical W4 watcher are merged from staging. This CRE-era implementation is later replaced by Mimic.

Details & sources

Initial keeper implementation merged to main

Merged. Brought the staging keeper implementation into main, including W1 queue decisions, W2 strategy decisions, shared report encoding, and the historical read-only W4 watcher. It included alignment with priced-liability and deposit-weight semantics from the contracts. This CRE-era implementation was superseded on August 26.

Source: keepers #18, with implementation commits 1e919d2, 3dd571e, and e98cf81.

View in Automation

Keeper receipts report what actually moved

Controller methods return achieved amounts so keeper receipts reflect execution results.

  • Unpriced, cancellable exits no longer drive strategy-withdrawal liabilities.
  • Empty whole-batch processing becomes a no-op.
  • Deposit eligibility checks the strategy’s deposit weight.
Details & sources

Keeper liabilities and achieved amounts

Merged. Excluded unpriced, cancellable exits from strategy-keeper withdrawal liabilities. Controller deposit, withdrawal, and harvest methods return achieved amounts, which the strategy executor uses in receipts instead of requested estimates. Empty whole-batch processing becomes a no-op, and deposit eligibility also checks nonzero deposit weight.

Source: contracts #43. The returned amounts change the Controller ABI; clients should use the matching interfaces.

View in Contracts

Share pricing accounts for priced exits

Live pricing and fee minting now account for in-window priced redemption liabilities and escrowed EVE.

  • Minting happens before ETH is forwarded to Controller.
  • Deployment checks enforce the timelock floor, proposer, and whitelist setup.
Details & sources

Priced-queue share accounting and deployment checks

Merged. Live pricing and fee minting deduct in-window priced redemption liabilities and their escrowed EVE. Unpriced requests remain equity; expired unprocessed requests stop contributing to those offsets and recover through cancellation/closure. Added a 25-live-priced-batch bound. The ExitQueue storage-layout change requires migration planning for an initialized proxy.

Also reordered minting before the ETH transfer to Controller, and hardened deployment checks for the 48-hour timelock floor, a nonzero proposer, and Whitelist registration before finalization.

Sources: contracts #39, #16, and #41. Strategy circuit-breaker changes are recorded in Strategy updates.

View in Contracts

Stronger strategy recovery and pool checks

Strategy pause and ETH recovery can proceed when a paired token fails.

  • Pool configuration must match the trusted factory.
  • TWAP history is checked at construction and when settings change.
  • Pause is still best-effort recovery, not proof that all assets were recovered.
Details & sources

Circuit-breaker and pool-validation hardening

Merged. Isolated best-effort paired-token allowance revocation and token recovery so a degraded paired token does not roll back the pause or ETH sweep. Added factory provenance checks for pools, and construction/configuration checks for TWAP availability and observation cardinality. Pause remains best-effort recovery; it does not prove that all pool liquidity was recovered.

Source: contracts #42.

View in Strategies

Emergency Converter pause and new keeper receivers

SECURITY can pause Converter immediately; unpausing remains an admin action. Historical CRE receivers replace the earlier automation contracts.

Details & sources

Converter emergency pause and CRE executor implementation

Merged. SECURITY gained permission to pause Converter; unpause remained ADMIN-only. Replaced the legacy Chainlink Automation executors with CRE/Keystone receivers, including forwarder/workflow authentication and replay guards. This historical CRE integration was subsequently superseded by the Mimic-compatible executor plane.

Sources: contracts #17 and #5.

View in Contracts

Strategy activation goes through the timelock

Deploying a strategy and activating it are now separate steps. Adapter authorization and strategy registration use the admin timelock.

Details & sources

Timelocked strategy go-live

Merged. Unified deployment flows so adapter allowlisting and strategy registration go through the admin timelock. Core deployment, adapter deployment, strategy deployment, and authorization are distinct steps. Deployment configuration became explicit for performance fees and keeper roles.

Source: contracts #1.

View in Contracts

A native wallet chooser

The app’s wagmi-based wallet connection flow replaces RainbowKit.

Details & sources

Native wallet chooser

Committed. Replaced RainbowKit with the application's native wagmi wallet-connection flow.

Source: e6cb587.

View in App

Dashboard metrics use protocol data

The dashboard gains indexed analytics, historical snapshots, a market chart, and clearer data-freshness feedback.

Details & sources

Data-backed dashboard

Committed. Added subgraph-driven dashboard analytics, protocol snapshots, data-freshness indicators, caching, and a GeckoTerminal chart integration after replacing mocked dashboard metrics.

Sources: b4889b8 and 8c37fcf. See the analytics data changes.

View in App

Historical analytics and EVE transfer tracking

Subgraph 0.2.0 adds dashboard aggregates and EVE transfer tracking. A snapshot worker provides persisted protocol history.

Details & sources

Dashboard aggregates and protocol snapshots

Committed. Subgraph source version 0.2.0 added dashboard aggregates and EVE transfer tracking. Added a protocol analytics worker and persisted snapshots for performance history, followed by freshness metadata, caching, and validation. A source version does not establish a historical production-tag activation date.

Sources: da916e0, b98606a, and 8c37fcf.

View in Data & integrations

The indexer moves to Ethereum Sepolia

Testnet configuration and frontend ABIs move from Arbitrum Sepolia to Ethereum Sepolia. Mainnet follows in September.

Details & sources

Ethereum Sepolia configuration

Committed. Moved the subgraph configuration from Arbitrum Sepolia to Ethereum Sepolia and aligned frontend network configuration and protocol ABIs. This was a testnet milestone; mainnet configuration followed in September.

Sources: f470c4e, 0e41347, and ae15707.

View in Data & integrations

Join the launch waitlist

The launch waitlist now saves registrations to the database.

Details & sources

Launch waitlist

Committed. Added the launch waitlist with database persistence and migration tooling.

Source: 3d20a58.

View in App

Slippage controls and clearer transaction feedback

Mint and burn gain slippage controls, with more detailed confirmation and account-activity feedback.

Details & sources

Slippage controls and transaction feedback

Committed. Added slippage controls to mint/burn, expanded transaction confirmation and action feedback, and refined account activity presentation.

Sources: 64b78a3 and 6a7c240.

View in App

Account history and redemption actions

Account details gains a profile, activity history, refresh controls, and redemption cancellation.

Details & sources

Account details and redemption actions

Committed. Added account profile and activity views, refresh/error/empty states, and redemption cancellation support.

Sources: 93885ca and 4850546.

View in App

More complete account activity

The indexer gains expanded event handling and user-activity tracking for account history.

Details & sources

Account activity indexing expanded

Committed. Expanded subgraph event handling and user-activity tracking after the initial indexer scaffold, providing the historical data used by account activity views.

Source: 50345b3.

View in Data & integrations

The first protocol subgraph

The initial Arbitrum Sepolia indexer tracks AMM, EVE, and ExitQueue events.

Details & sources

Initial protocol subgraph

Committed. Added the initial protocol subgraph for Arbitrum Sepolia with AMM, EVE, and ExitQueue event handlers, schema, configuration, and query documentation. Later network and schema entries supersede this historical configuration.

Source: 8f9fd46.

View in Data & integrations

The first web3 app

The first application iteration brings together wallet connection, mint/burn forms, market data, and transaction handling.

Details & sources

First web3 application iteration

Committed. Introduced the web3 application with wallet connection, mint/burn forms, market-data reads, transaction handling, and protocol ABIs. This belongs to the preserved monorepo history and predates the current mainnet configuration.

Source: 7538e2b.

View in App

About this history & verification

This feed contains every dated entry from the five category histories, including pre-extraction app commits from March 2026. Entries are maintained in their category pages and combined automatically here.

Released entries have a successful app Production deployment; On-chain entries have an execution receipt. Code merged and Source update entries record implementation work, not a verified production activation date.

Baseline history reviewed on October 15, 2026: app through 47c0756, contracts through 157129b, keepers through ec1ab3f, and governance through 047f8e3. Later entries record their own verification evidence. Some source links require organization access.

For dated protocol state, use Current deployments. Addresses live in Contract addresses. Research experiments in backtests do not establish a live strategy. See the release notes policy for maintenance rules.

Last updated on