DocsClaiming

Claiming

Verify your X account and claim your balance to any wallet on Arc.

How claiming works

Payments stay in escrow until you prove you own the handle. Each supported asset has its own PayX contract, so the creator hub shows one balance and one Claim button per asset (one transaction each). The claim combines:

X OAuth (PKCE)

Oracle EIP-712 signature

Our server authorizes handle to wallet; the contract verifies it.

Claim process

Visit the creator hub
Go to /pay/creator.
Sign in first; your pending balance is read from the contract for the verified handle.
Sign in with X
Click "Sign in with X" and approve read-only access to your profile.
We never request posting permissions. Your verified username is kept in an encrypted, HttpOnly cookie.
See your pending balances
Pending, lifetime received and claimed totals per asset, straight from each instance’s getHandleInfo().
Amounts are already net of the 1% platform fee.
Connect a wallet on Arc and claim
Connect the wallet you want paid; if it is on another network we ask it to switch to Arc (chain 5042). Click Claim on the asset you want and confirm.
The whole pending balance of that asset is paid out in one transaction. Each asset is claimed separately.

Wallet linking

Your first successful claim links that wallet to your handle onchain (WalletLinked). Linking is per contract: each asset's instance remembers its own linked wallet, so use the same wallet across assets if you want a single payout address. After that:

Every later claim must use the same wallet

A claim for a different wallet reverts with WalletMismatch, even with a valid oracle signature.

Recovery through governance

If you lose the wallet, contact @Xylonet_. After verification the Admin Safe (2-of-3) calls adminRelinkWallet, which redirects future claims and emits WalletRelinked. It never moves existing funds by itself.

Choose your first claim wallet carefully. It should be one you control long-term.

Technical details

Claim transaction

function claimTips(
    string calldata handle,    // your X handle (normalized onchain)
    address wallet,            // destination wallet
    bytes32 nonce,             // random, single-use
    bytes calldata signature   // oracle EIP-712 signature
) external nonReentrant whenNotPaused

Signature verification (EIP-712)

The contract rebuilds the typed-data digest and checks the recovered signer against oracleSigner():

// domain: EIP712("PayX", "2") + chainId 5042 + address(this)
bytes32 CLAIM_TYPEHASH = keccak256("Claim(string handle,address wallet,bytes32 nonce)");

bytes32 structHash = keccak256(
    abi.encode(CLAIM_TYPEHASH, keccak256(bytes(normalizedHandle)), wallet, nonce)
);
bytes32 digest = _hashTypedDataV4(structHash);
if (ECDSA.recover(digest, signature) != oracleSigner) revert InvalidSignature();
if (usedNonces[nonce]) revert NonceAlreadyUsed();

Because the domain includes the chain id and the contract address, a signature is useless on any other chain or deployment.

Onchain events

Successful claims emit TipsClaimed (and WalletLinked on the first claim):

event TipsClaimed(
    string indexed handleHash,
    string handle,
    address indexed wallet,
    uint256 amount,             // total claimed (token units of that instance)
    uint256 timestamp
);

Common questions

How long do payments stay in escrow?

Indefinitely. There is no expiry and no admin function that can remove them.

Can I claim partial amounts?

No. Each claim withdraws your entire pending balance of that asset at once. Each asset is claimed separately.

What if I change my X handle?

Payments are indexed by the handle text, not your X user ID. Payments sent to your old handle stay under that handle and can be claimed by whoever can sign in as it. Announce a new handle before renaming.

Can someone else claim my balance?

Only someone who can sign in to X as your handle. The oracle signs only for the handle in a verified session, and the contract accepts only oracle signatures.

What does "PayX is paused" mean?

The guardian or owner halted payments and claims temporarily (for example during an incident). Escrow is untouched; claims resume when the owner unpauses.

How claiming works

X OAuth (PKCE)

Oracle EIP-712 signature

Our server authorizes handle to wallet; the contract verifies it.

Claim process

Visit the creator hub

Go to /pay/creator.

Click "Sign in with X" and approve read-only access to your profile.

We never request posting permissions. Your verified username is kept in an encrypted, HttpOnly cookie.

See your pending balances

Pending, lifetime received and claimed totals per asset, straight from each instance’s getHandleInfo().

Amounts are already net of the 1% platform fee.

Connect a wallet on Arc and claim

Connect the wallet you want paid; if it is on another network we ask it to switch to Arc (chain 5042). Click Claim on the asset you want and confirm.

The whole pending balance of that asset is paid out in one transaction. Each asset is claimed separately.

Wallet linking

Every later claim must use the same wallet

A claim for a different wallet reverts with WalletMismatch, even with a valid oracle signature.

Recovery through governance

Choose your first claim wallet carefully. It should be one you control long-term.

Technical details

Claim transaction

function claimTips( string calldata handle, // your X handle (normalized onchain) address wallet, // destination wallet bytes32 nonce, // random, single-use bytes calldata signature // oracle EIP-712 signature ) external nonReentrant whenNotPaused

Signature verification (EIP-712)

The contract rebuilds the typed-data digest and checks the recovered signer against oracleSigner():

// domain: EIP712("PayX", "2") + chainId 5042 + address(this) bytes32 CLAIM_TYPEHASH = keccak256("Claim(string handle,address wallet,bytes32 nonce)"); bytes32 structHash = keccak256( abi.encode(CLAIM_TYPEHASH, keccak256(bytes(normalizedHandle)), wallet, nonce) ); bytes32 digest = _hashTypedDataV4(structHash); if (ECDSA.recover(digest, signature) != oracleSigner) revert InvalidSignature(); if (usedNonces[nonce]) revert NonceAlreadyUsed();

Because the domain includes the chain id and the contract address, a signature is useless on any other chain or deployment.

event TipsClaimed( string indexed handleHash, string handle, address indexed wallet, uint256 amount, // total claimed (token units of that instance) uint256 timestamp );

Common questions

How long do payments stay in escrow?

Indefinitely. There is no expiry and no admin function that can remove them.

Can I claim partial amounts?

No. Each claim withdraws your entire pending balance of that asset at once. Each asset is claimed separately.

What if I change my X handle?

Can someone else claim my balance?

Only someone who can sign in to X as your handle. The oracle signs only for the handle in a verified session, and the contract accepts only oracle signatures.

What does "PayX is paused" mean?

The guardian or owner halted payments and claims temporarily (for example during an incident). Escrow is untouched; claims resume when the owner unpauses.