“Who can change what?” — if you claim decentralization, you must be honest here. This item reads where ownership sits across every live V1 contract. The bottom line, up front: every changeable contract (the Ownable ones) is held directly by a single deployer key. This is the expected pre-mainnet stage, and the exact thing the source itself declares it will resolve via multisig handoff or renounce. We don’t boast about closed locks; we count the doors that are open, accurately.

1. Claim (what is verified)

To actually read who owns (owner) each contract across all of live V1, and to record honestly which contracts the deployer EOA can change directly and which are ownerless by design.

2. Method

3. Verdict

Ownership split cleanly in two.

From there, we split the single key’s “can / cannot” honestly.

• residual A single key holds all Ownable contracts. It can call each contract’s owner-gated functions (e.g. rotating the delegate). This is the expected pre-mainnet posture, not a hidden owner.
• cannot Re-pointing a peer is impossible even for the owner (B-1, OnlyOnce). Swapping logic is impossible too (A-3, not a proxy). The wiring setters are one-shot and already used.
• by design Seven contracts are ownerless. Marketplace fixes its payment-token set at construction (no post-deploy add/remove); ClientManager is just identity/fees/registry; BuyAndBurn has all params immutable; FontDataA/B are pure data. None expose an admin surface.

Honestly summarized: it is a fact that a single raw key still holds every Ownable contract. At the same time, what that key cannot do (re-point peers, swap logic) is clear, and there is no hidden owner and no proxy backdoor. Not “decentralization complete,” but a single pre-mainnet key with visible boundaries — that is the observed state.

4. Receipt (public proof)

The deployer EOA and the ownership reads. All 12 Ownable contracts return the same EOA.

Ownerless (L1, no owner function): ClientManager 0xA5C515…24C7a, Minter 0x8D65D1…290D9, Quoter 0x3100B1…8e79, Marketplace 0x6404d1…67C3, BuyAndBurn 0x5860d1…7F486, FontDataA 0xB7ec88…43B8cf, FontDataB 0x1D084C…98fBf3.

To reproduce, just read owner() on each address. Every Ownable returns the deployer EOA; the ownerless group has no owner() function.

Reproduction commands — the same ethers v6 (node) / curl you would run on your node — are provided copy-safe under “CLI” in the tool below (every Ownable returns 0xF713…4a95).

5. Why a single key for now (the pre-mainnet stage)

Before branding the single key as “proof of centralization,” read what the key cannot do and what the source itself declares. We write this without fudging.

So “single key = confirmed centralization” does not hold. The key’s power does not reach peers or logic, and the handoff is spelled out in source — a matter of stage, not of missing capability. That said, “decentralization complete” does not hold either. Until the multisig handoff or renounce is executed, we keep counting this honestly as an open door.

6. Notes & limits

What this item (A-2) covers is where ownership/admin sits. Code identity is A-1, the ownership-transfer history (txhash) is A-4, and proxy structure is A-3. The ownership state is point-in-time; we will update this page if a multisig handoff / renounce is executed.