Zxo on PulseChain Deployment Report

All six were deployed on 3 October 2026 by 0x98C3eEc2b28D82b05edfA3D40F8A468a58BD1e24, an externally owned account that is also the current owner of Zxo. The order on-chain was ZxoTreasury, ZxoOracle, ZxoVerify, ZxoV3Deployer, ZxoVerify again, then Zxo at 16:46 UTC, followed by ZxoV3Deployer.setZxoContract(Zxo) at block 27704538. That is the order the audit requires. Both ZxoVerify deployments succeeded, and ZxoVerify reverts unless its checks pass.

The nine reward tokens are ZxoToken instances created by Zxo.createPool from the same token source. No reward token address was submitted for separate verification, so they are covered through the Zxo build, which contains the token code.

This confirms the H-02 fix on a live PancakeSwap-style pool. PancakeSwap itself on BNB Chain has not been run, but it uses the same pool design and the same Zxo code path, so the remaining risk there is low. The health gate count is the 16 stake and 6 harvest transactions. The mint count is the 18 successful pool initializations and the 16 stakes.

Transactions and events for Zxo and ZxoV3Deployer were read through the PulseChain explorer API, from deployment on 3 October 2026, 16:46 UTC to 5 October 2026, 22:39 UTC: 100 Zxo transactions with 119 ZxoEvent logs, and all 38 ZxoV3Deployer transactions with their 39 logs.

Functions exercised on mainnet

Numbers recomputed from the audited formulas

The first row reproduces a live claim to the last wei from the reward formula in the audit. The second shows that the single-sided core stake counts toward the value used for emissions (finding M-01): the on-chain figure comes from the first emission rate, and the formula figure from the core-stake liquidity and its tick range.

• Target APR. Pools 5 and 6 target 360% and 510%. Both were created with the 320% cap, which doubles to 640% in the first year. Each pool's emissions are also limited by its 30-day cap, fixed at creation.
• Referral rate. It ranges from the 3% default to the 30% maximum (pool 6). The referral share comes out of each claim, so a staker on pool 6 keeps 70% of rewards unless they are their own referrer.
• Core stake and your APR. The core stake counts toward a pool's reward weight but never claims (finding M-03, accepted). What that costs stakers depends on its size beside theirs. The core stakes are small, so the cost fades quickly as a pool fills; the table below gives the sizes.
• Seeding. Every pool was seeded through three position managers: 0xCC05bf158202b4F461Ede8843d76dcd7Bbad07f2, 0x18A532b36A9F6B10b3FEC5BF225C00A0Ec89B79E and 0xC36442b4a4522E871399CD717aBDD847Ab11FE88. The third is the Uniswap V3 position manager address. This review did not identify the DEX behind the first two; the team should publish their names so users can check them.
• Token-only calls. 23 of the 32 createPool calls used withoutPool = true. These deploy a token with no pool and no supply and have no effect on the pools.

These settings are within the limits the contract enforces and are the owner's to choose. They are listed so that users can see them; they are not findings.

Core stake size and what it costs stakers

• Size. The nine core stakes are worth about $330 to $1,030 each and about $4,900 together, at DEX prices of the pair tokens on 5 October 2026. The team reports $1,078.57 for pool 0 and about $200 to $600 for the others. This review's figures agree, except pool 3, which comes out near $790 at the INC price used here.
• Fixed at creation. Each amount is set in the createPool call, stored as an immutable value in the reward token, and minted once. It cannot be increased later. The amounts above are decoded from those calls and match each pool's first emission rate exactly.
• Effect on APR. A core stake carries about 2.2 times the reward weight of a user stake of the same value. When user stakes equal the core stake, stakers earn about 62% of the target APR. At ten times the core stake they earn about 90%, and at one hundred times about 99%. For pool 0 that is roughly $10,000 and $100,000 of user stakes; for a $400 core stake, $4,000 and $40,000.
• Where the pools stood. Pools 6 and 8 held real user stakes, and stakers there were earning about 90% and 99.9% of target. The other pools held test-size stakes far smaller than the core stake, or none. That is the only case where stakers earn about half of target.

• It covers the six addresses in section 02 on PulseChain mainnet only. Other chains need their own report.
• Source and bytecode status come from Sourcify. Transactions and events come from the PulseChain explorer API, up to 5 October 2026, 22:39 UTC. Later activity is not covered.
• No contract state was read directly from a node. The current owner, the deployer link, pool history sizes and treasury settings are inferred from events, not read from storage.
• Dollar values of the core stakes use DEX prices of each pair token read from DexScreener on 5 October 2026. They are approximate and move with the market. Pool 5's pair token has thin liquidity, so its figure is the least reliable.
• 11 of the 119 event records came through the reader with damaged data and were only partly decoded. None of the checks in section 06 relies on them.
• The files compiled only into Zxo were matched line by line, not by hash (section 03).
• The LibertySwap pool and position manager contracts themselves were not audited. Their type was inferred from the verified factory interface.
• No fuzzing, static analysis or fork testing was run by this review. This AI-assisted report does not replace an independent human audit.