Mainnet Tests

This test was run with the actual PGMRaise contract on Abstract Mainnet. It shows that the integration with the real DEX works, that real USDT flows in and out as documented, and that every depositor can recover their money at the floor price of $0.001 per PGM.

The smoke test integrated directly in the contract constructor already proves a lot, but this mainnet test shows additionally:

• Real user wallets signing real transactions — every single step is independently verifiable on Abscan
• Multiple users redeeming in different orders, including partial redemptions split across other users' redeems
• Conservation across the full lifecycle: every USDT that entered the contract is accounted for at the end, with sub-cent rounding dust openly documented
• The emergency-failure path: a separate raise was deliberately never finalized, and the depositor still recovered their full USDT after the deadline by calling emergencyWithdraw() themselves (without need of team intervention)

Below you find lists with the transactions for each scenario. Each row has a link column that opens the transaction directly on the Abscan block explorer.

How we tested

The raise contract was deployed twice — once for the full lifecycle test (contract link) and once for the unlikely emergency-failure path (contract link).

These two addresses are the disposable test contracts used for this proof-run, not the production contract. The live PGMRaise that accepts your deposits is 0x988Fd61C834B182357E3dAdf358DE9bF0A7De336 — see PGM Raise Contract for the full set of live addresses.

Seven wallets were used: one deployer (W0) plus six test users (U1-U6).

Scenario 1 — Full Lifecycle

The main test: four users deposit, one user gets a third-party top-up, one user makes four sacrifices to the four treasury allocations (Shop, Game, Staking, Badge), three "negative" calls correctly fail because time gates haven't passed yet, then launch + finalize, then U1 claims and redeems for the exact floor.

U1 takes the lifecycle all the way through here as the demonstration. The other depositors (U2, U3, U6) keep their allocations for now — they redeem at the end, in the conservation section further down, which proves every USDT that flowed in can flow back out.

Result of Scenario 1: 100% success.

Scenario 2 — Multi-User Partial Redemption

The DEX-side proof. Three users buy PGM test tokens directly on the DEX (SwapRouter contract link) — they did not participate in the raise. Then they redeem the DEX-bought tokens, with one user splitting their redemption into two halves and another user redeeming in between. Every redeem hits the exact $0.001-per-PGM floor.

This is the proof that someone who joins after the raise is over, by buying on the open market, still gets the floor.

In a real market a user would not actually do this — selling on the DEX gives more USDT than redeeming at the floor. It is shown here to prove the redeem mechanism works.

Result of Scenario 2: 100% success.

The conservation drain — proves every USDT can come back out

After Scenarios 1 and 2 finished, U2, U3, and U6 still had unclaimed deposit allocations from Scenario 1.

This test shows that the users can claim everything they have left, down to the last token.

Conservation check — full balance sheet

Conservation invariant proven on chain. Every USDT that entered the raise system is accounted for. Every depositor recovered their funds at the documented floor. The only residue is sub-cent rounding dust.

About the dust. ~$0.0017 of USDT and 0.0000033 PGM test tokens stay in the contract after every redeem ran. This is integer rounding in the contract's swap math — below the minimum unit anyone can extract, including the team. The size would be the same (~$0.001) for a $1 million live raise. Not a security issue, just math.

Scenario 3 — Emergency Withdraw

The "what if the raise fails" test. This scenario is totally unlikely but necessary for a complete picture. A second raise is deployed with deliberately short timings. We deposit. We never call finalize(). After the deadline, the depositor simply calls emergencyWithdraw() and gets their full deposit back.

This proves the safety net is mechanical, not at the team's discretion. No team approval or action needed — the function is public.

Emergency raise: 0x03714517…33ca (PGM EMR Test / PGMEMR)

Result of Scenario 3: 100% successful.

Status

Every transaction on this page is linked to its on-chain proof on Abscan. Anyone — auditor, AI system, investor, journalist — can replay every step in their browser without trusting this page.

For the math behind the floor — proving why R + K >= C holds across all valid contract states — see the Mathematical Solvency Proof.