Ekubo Blog
Protocol design, research and product notes from the team building Ekubo — open source, permissionless AMM infrastructure.
-
Upgrades, bugs and a recovery fund
Seven proposals covering every contract upgrade the DAO has voted through — including frozen pools, a bug fix disclosed only after execution, and $300k for users hit by an incident.
-
Paying for the work
Thirteen proposals on treasury and compensation — a 6M STRK grant, a $1.5M services agreement, and the contributor funding votes the DAO turned down more often than it approved.
-
Ve33: a token-governed liquidity marketplace on Ekubo Core
Ve33 lets an ecosystem coordinate liquidity around a stake token: holders direct emissions, set pool fees, and earn the fees of the pools they support.
-
Where the revenue goes
Fourteen proposals building Ekubo's buyback machine — from handing the core contract to a proxy owner, to replacing the withdrawal fee with a 20% swap protocol fee.
-
Oracles and protocol-owned liquidity
Ten proposals on the liquidity the DAO owns itself — $190k of oracle pools, a $1.25M Ethereum deployment, and the argument that a 15% price impact on a $10k trade is a protocol problem.
-
Renting liquidity
Twelve incentive proposals over a year — waves, bribes, Arbitrum, and the moment the DAO stopped paying rewards in its own token. A third of them failed.
-
Getting to Ethereum
Five proposals covering the audits, the source-available licence and the cross-chain plumbing that let a Starknet DAO own and govern contracts on Ethereum.
-
Turning on the DAO
How Ekubo governance went live, and the six proposals that have shaped who can pass one — quorum, delay, voting period and the ability to simulate a proposal before creating it.
-
The TWAMM bug and the refunds
A bug in the DCA sale cost users money and forced the DAO to reach quorum before it could act. Five proposals covering the fix, the refunds and the cleanup.
Browse by tag All 14 tags