Loading XyloNet...
Loading XyloNet...
PayX's security practices, smart contract safety, and risk considerations.
PayX is designed with security as a top priority. Our non-custodial architecture ensures you always maintain control of your funds.
You always control your funds
Contract verified on ArcScan
Built on proven libraries
Uses OpenZeppelin's ReentrancyGuard to prevent recursive attacks
Safe token transfers using OpenZeppelin's SafeERC20 library
Solidity 0.8.24 with built-in overflow checks
Ownable pattern for administrative functions
All inputs validated with custom errors for clear feedback
Unique nonces prevent signature replay attacks on claims
The claim process uses a secure two-factor verification:
Users must authenticate via X OAuth to prove they own the handle. We only request read access to the profile.
Our backend oracle signs a message containing the handle, wallet, and nonce. The contract verifies this signature before releasing funds.
Once claimed, the wallet is linked to the handle. Subsequent claims must use the same wallet, preventing unauthorized claims.
PayX uses Circle's native USDC on Arc Network. USDC is the most trusted stablecoin, backed 1:1 by US dollars and regularly audited.
Learn more about USDC →
Arc is a stablecoin-native L1 by Circle. It provides fast finality and USDC-denominated gas fees.
Learn more about Arc →Our contracts are built on OpenZeppelin's battle-tested libraries for ERC20, ReentrancyGuard, Ownable, and cryptographic functions.
OpenZeppelin documentation →Despite security measures, smart contracts may contain undiscovered vulnerabilities. Only tip amounts you're comfortable with and consider starting small.
The claim process depends on our oracle service to sign claim authorizations. While designed for high availability, service disruptions could delay claims.
PayX is currently on Arc Testnet. Expect potential network instability and resets before mainnet launch. Testnet USDC has no real value.
If you discover a security vulnerability:
Please do not publicly disclose vulnerabilities. Contact us privately first.