Capital flow
Creator fees from pons are claimed on a schedule, converted to dollars through Kraken, and sent to the creator's Money account. 20% of every claim buys and burns $PAID.
- pons→
- Fees claimed→
- Bridged and off-ramped through Kraken→
- Sent to X Money balance→
- Sent to X user→
- $PAID bought back and burnt
Off-ramp
Treasury ETH bridged from Robinhood Chain and sold for dollars at Kraken. Conversions run in batches.
On-ramp
Dollars from Kraken landing in the X Money balance every payout is made from
A token on pons points its fees at us
At launch, the token sets our treasury as its creator fee recipient and pons locks in that destination: only the current recipient can hand it on. pons pays creator fees in the quote asset, ETH. We read the X handle from the token's description and claim the fees from the pons fee escrow on a schedule. Every claim splits: 80% to the creator and 20% to buy and burn $PAID.
Kraken converts it to dollars
Every claim's recipient share reaches this step as ETH on Robinhood Chain. It crosses the Robinhood Chain bridge, lands at Kraken, and converts to US Dollars at the same Kraken account. Conversions run in batches rather than one per payout, and Kraken's fee is about 0.22%.
$PAID is bought back and burnt
The 20% buys $PAID on pons, in ETH, and burns it through the token's own ERC20Burnable burn function, which removes it from supply rather than parking it at an address. Supply is fixed, and the buys and burns are on chain if you want to check them.
USD arrives in our X Money balance
The dollars Kraken settles land in the Money balance on the @paidfamily account, the treasury every payout is made from. It holds what is owed to X users between a claim and its payout, and we keep it ahead of what is owed.
The X user receives the distribution through X Money
The payout leaves our balance and arrives in the X user's Money account, the one matched to their handle. X asks for verification and the enrolled security key answers it, so nobody taps a prompt. @paidfamily then replies with X's own receipt attached.
X Money operations
X Money allows an account to confirm payments with a security key. @paidfamily has one enrolled and held by our payout worker. When X requests verification, the worker uses the key to sign the challenge, allowing the payment to proceed through the X Money interface. This is what makes the sends automatic.
- Verification
- An X security key, held by our payout worker
- Send limit
- No hard cap on peer-to-peer sends
- Fee
- $0 per send
- Minimum
- $1 per send
X's settings as of September 2026.