Skip to content
Protocol contracts not yet configured for this build
Enter app

Introduction

Current deployment status

This page states the literal current state. Nothing here is aspirational.

Summary

Plouto contracts

Not deployed No mainnet deployment has been performed. There are no Plouto addresses to publish yet.

PLOUTO token

Not deployed Not launched. No token address, no curve address.

Registry initialization

Planned setPloutoTokenOnce has not been called, because there is nothing to register.

Pons V2 contracts

Verified The external Pons deployment is live and was verified directly against chain state.

Audit

Unaudited No external audit has been performed. See audit status.

What the interface does about it

The application reads the registry's initialized() state on every page load. It does not hardcode a token address anywhere, and it does not assume a launch has happened.

Concretely, while the registry reports uninitialized:

  • The status strip reads Protocol contracts live · PLOUTO launch pending, not "live".
  • Every staking control is disabled, not merely styled as unavailable.
  • Protocol figures render as genuine zeroes or em dashes, never as sample data.
  • The status page shows PLOUTO registered → Failing as an honest check result.

The moment setPloutoTokenOnce lands on chain, all of that flips automatically. There is no rebuild, no redeploy and no environment variable change involved, because the token address is resolved at runtime from the registry rather than baked into the bundle.

What exists today

The contracts are written, built and tested. The full suite — unit, fuzz, invariant and mainnet-fork — passes. The launch tooling exists and runs in dry-run mode against live chain state.

What has not happened is any mainnet broadcast. Every script in the repository refuses to send a transaction without an explicit --broadcast flag and a signing key supplied through the environment; the default in all cases is a simulation.

See test results for what the suite covers, and known limitations for what remains unresolved.

When this page changes

Once a deployment happens, this page and Robinhood mainnet will carry the canonical addresses, deployment blocks and verification status — taken from actual broadcast receipts, never from a prediction or a dry run.