What is PulseX?
PulseX is an automated market maker built from the Uniswap v2 design. Its contracts carry the same names with a PulseX prefix — PulseXERC20 (the LP token), PulseXPair, PulseXFactory (PulseXFactory.sol:131, :288, :505) — and are compiled with the same Solidity versions as Uniswap v2 (0.5.16 for the core, 0.6.6 for the router). Pairs are created deterministically with create2 (:523-538), and the first 1,000 LP units of every pool are locked forever (:292, :397-398).
The swap fee is 0.29 %. The pair enforces it in its invariant check balance × 10000 − amountIn × 29 (:456-459); the router quotes trades with amountIn × 9971 / 10000 (PulseXRouter02.sol:251). Where that fee ends up is explained in Fees.
New to pools? Watch one work, step by step, in How an AMM works.
Which contracts make up PulseX?
The addresses match those hard-coded in the official front-end build. A deployment date is when the contract went on-chain, not necessarily when the public app opened.
Same address, different chain: on Ethereum, 0x1715a3E4…A10D is not a PulseX factory but the PulseChain bridge’s mediator, and 0x2fa878Ab…C95d is not INC but the bridge’s validator contract. Always check the chain together with the address.
What is the difference between v1 and v2?
The two generations run side by side. On 2026-10-19 (block 27,837,219) the v1 factory had 65,440 pairs and the v2 factory 191,227 pairs. Their pair code differs in one place only: the share of the fee that goes to the protocol inside _mintFee. In v2 liquidity providers keep 0.22 % of every trade; in v1 the protocol takes the whole fee growth. The details, with the on-chain check, are on the Fees page.
Who controls PulseX?
The factory has exactly Uniswap’s privileged role: feeToSetter may change feeTo — the address that receives the protocol fee — and hand its own role to someone else (PulseXFactory.sol:540-548). It cannot touch pools, prices or LP balances.
These are mutable settings, valid for the date shown. The buy-and-burn contracts have their own owner with wider powers — see Fees.
How well are the contracts verified?
PulseScan marks PLSX, INC, WPLS, the MasterChef and both factories and routers as partially verified through Sourcify (2026-10-17). A partial match means the compiled code matches the deployed bytecode, but the embedded metadata hash — which also covers comments, file names and settings — does not. The executable logic is the published source. HEX, by comparison, is fully verified.
Have the PulseX contracts been audited?
No public audit report of the PulseX factories, routers, PLSX, INC, the MasterChef or the buy-and-burn contracts has been found (re-checked 2026-10-17). The pair and router logic is derived from Uniswap v2 and the farm contract from SushiSwap’s MasterChef (with the migrator removed), but no audit of the PulseX deployment itself is known. The official repositories contain front-end builds, not Solidity projects with tests; the contract sources come from the verified code on the explorer.
Can I use PulseX without the official website?
Yes. The official app is app.pulsex.com (also mirrored on IPFS), and its front-end is published as a self-hostable build in the pulsex-server repository, so the exchange can be used from a local copy against the same contracts. Bookmark official addresses — copies of exchange sites are a common scam (Security).