Verified source

Verification lets anyone confirm the contract running on chain is compiled from the source published here. Without it, every claim in this documentation is unfalsifiable.

Build settings

Verification only reproduces if the compiler settings match exactly:

solc_version   = "0.8.24"optimizer      = trueoptimizer_runs = 1000via_ir         = falseevm_version    = "cancun"bytecode_hash  = "none"

bytecode_hash = "none" strips the metadata hash, so builds are reproducible across machines.

Verifying at deploy time

forge script script/Deploy.s.sol:Deploy \  --rpc-url $ROBINHOOD_RPC_URL \  --account plouto-deployer \  --broadcast \  --verify

Verifying afterwards

forge verify-contract <address> src/PloutoRegistry.sol:PloutoRegistry \  --chain 4663 \  --verifier blockscout \  --verifier-url https://robinhoodchain.blockscout.com/api

Repeat per contract. Constructor arguments must be supplied with --constructor-args where they are not recoverable from the creation transaction.

Checking as a user

1. Open the address on Blockscout.
2. Look for the Contract tab and a verified badge.
3. Read the source. It should match this repository at the tagged commit.
4. Check the constructor arguments — particularly ponsFactory, ponsFeeEscrow and expectedLauncher on the registry.

Current status

Not deployed Nothing is deployed, so nothing is verified. The status page will show live verification state once addresses exist.

The Pons side

Because the curve and token are unverified, their ABIs were recovered from deployed bytecode by selector extraction and cross-checked against the public 4-byte database. See contract ABIs.