docs: peripheral-contract ownership update (9 Oct 2026) + annex [do not merge]

astro.config.mjs

@@ -254,6 +254,10 @@ export default defineConfig({
               slug: "reference/contracts",
               items: [
                 { label: "EVM (V3)", slug: "reference/contracts/evm-v3" },
+                {
+                  label: "Peripheral ownership",
+                  slug: "reference/contracts/peripheral-ownership",
+                },
                 { label: "Starknet", slug: "reference/contracts/starknet" },
                 {
                   label: "Starknet Sepolia",

src/content/docs/products/governance.md

@@ -49,11 +49,23 @@ For the practical steps, see [Participate in governance](/user-guides/governance
 
 - **Starknet contracts** — Core, Positions, and the extensions are upgradeable in place. The extensions are owned directly by the Governor; Core and Positions are held by the RevenueBuybacks contracts, which the Governor owns and can reclaim from by proposal
 - **The treasury** — assets held by the DAO, disbursed by proposal (including streamed payments)
-- **Cross-chain deployments** — owner proxies on Ethereum, Arbitrum, Optimism, Base, and Robinhood Chain let a Starknet proposal control contracts on other chains
-- **Periphery ownership** — the owner role on Positions and other periphery contracts, which withdraws accumulated protocol fees to the DAO. The fee _rate_ itself is not a governance parameter: it is immutable on EVM and a compile-time constant on Starknet, so changing it requires a new deployment
+- **Cross-chain deployments** — owner proxies on Ethereum, Base, Optimism, Arbitrum One, Robinhood Chain, Unichain, World Chain, Ink, MegaETH, Gnosis, and Polygon are configured so that a Starknet proposal can control contracts on other chains. See the [peripheral-contract ownership update](#peripheral-contract-ownership-update-9-october-2026) below for which contracts they own and for the status of production cross-chain message delivery
+- **Periphery ownership** — the owner role on Positions and other periphery contracts, which can withdraw accumulated protocol fees to a recipient the owner chooses. It is not held by the DAO on every chain: on BNB Smart Chain and Monad, Ekubo, Inc. still owns the Positions and Orders contracts (see the [update](#peripheral-contract-ownership-update-9-october-2026) below). The fee _rate_ itself is not a governance parameter: it is immutable on EVM and a compile-time constant on Starknet, so changing it requires a new deployment
 
 Notably _not_ controlled: the EVM V3 Core contract, which has no owner at all.
 
+## Peripheral-contract ownership update (9 October 2026)
+
+**Peripheral-contract ownership update — 9 October 2026.** Ekubo, Inc. has completed 33 direct ownership transfers of Positions, Orders and Auctions peripheral contracts to designated DAO owner proxies across 11 EVM chains: Ethereum, Base, Optimism, Arbitrum One, Robinhood Chain, Unichain, World Chain, Ink, MegaETH, Gnosis and Polygon. Six new owner proxies were deployed as part of this migration. The transfers were company-signed, board-approved `transferOwnership` transactions, not transactions executed under a DAO vote. No Governor proposal was created for the prepared P1, R1 or R2 drafts. P1 was withdrawn before proposal; R1 was superseded before proposal; the board stood down R2 on 9 October 2026. No ownership handover request or completion step remains pending.
+
+**Six company-controlled contracts remain.** The Ekubo, Inc. company key `0x00000c771f6176268d5a9846e0956c3ef58597a1` still owns Positions and Orders v3.2.0 on BNB Smart Chain (two contracts), and Positions and Orders v3.1.1 and v3.2.0 on Monad (four contracts). Their DAO-control route remains subject to a separate board decision. Positions ownership permits withdrawal of accrued protocol fees to an owner-selected recipient and metadata/ownership administration; Orders ownership permits metadata/ownership administration, not funds withdrawal. These six contracts are not DAO-controlled.
+
+**Production cross-chain delivery remains unproven.** Ownership and proxy configuration have been independently verified by Ekubo's security reviewer, and messaging paths have been tested on live-chain forks. However, no production DAO message has yet been delivered through any of the ten L2/sidechain owner proxies. The board accepted this residual and decided not to create the R2 reachability-proof proposal. Configured DAO ownership is not a demonstration or guarantee of production cross-chain message delivery. If a messaging route fails to deliver, affected owner-only functions, including fee withdrawal and metadata administration where applicable, could be unreachable until the route is restored. Such a delivery failure does not itself transfer or give access to user positions or funds, or change the immutable, ownerless EVM Core contracts.
+
+The ownership migration did not withdraw fees, transfer user tokens or position NFTs, change protocol fee rates or fee recipients, create automatic fee remittances or buybacks, or change STONX economic rights. The accompanying chain-, version- and address-specific control matrix and transaction record identify the migrated contracts, new proxies and remaining company-controlled contracts. This is a dated ownership snapshot, not a claim that all deployments are DAO-controlled or that every cross-chain route has been exercised in production.
+
+The per-contract transaction record, the owner proxies and the six contracts that remain company-owned are listed, with snapshot blocks, in [Peripheral-contract ownership](/reference/contracts/peripheral-ownership/).
+
 ## Revenue buybacks
 
 Protocol fees are collected at the periphery — a share of the swap fees liquidity providers collect — and flow back to the DAO through the RevenueBuybacks contract.

src/content/docs/reference/contracts/evm-v3.md

@@ -121,6 +121,16 @@ ERC-721 manager for [DCA orders](/user-guides/dollar-cost-average-orders/). A fe
 also carry earlier manager deployments that are not canonical and should not be used for
 new transactions.
 
+Each manager has an `owner` role: on Positions it can withdraw accrued protocol fees to a
+recipient the owner chooses and administer metadata and ownership; on Orders it
+administers metadata and ownership only. Who holds
+that role differs by chain. It is not held by the DAO on every chain: on BNB Smart Chain
+and Monad, Ekubo, Inc. still owns the managers. See
+[Peripheral-contract ownership](/reference/contracts/peripheral-ownership/) for the
+dated, per-chain record and the
+[ownership update](/products/governance/#peripheral-contract-ownership-update-9-october-2026)
+for what it does and does not establish.
+
 ### Deployment-specific contracts
 
 Contracts added or reworked in `v3.2.0` are configuration-specific and have no universal address — their addresses are per deployment:

src/content/docs/reference/contracts/index.md

@@ -6,6 +6,7 @@ title: "Contract addresses"
 Deployed contract addresses by deployment:
 
 - [EVM (V3)](/reference/contracts/evm-v3/) — the current EVM deployment: same deterministic addresses on every supported chain
+- [Peripheral ownership](/reference/contracts/peripheral-ownership/) — dated per-chain record of who owns the EVM Positions, Orders and Auctions contracts
 - [Starknet](/reference/contracts/starknet/) — the original Ekubo deployment on Starknet
 - [Starknet Sepolia](/reference/contracts/starknet-sepolia/) — the Starknet testnet deployment
 - [Governance](/reference/contracts/governance/) — the EKUBO token, Staker, and Governor contracts on Ethereum and Starknet mainnet