{"id":"usepaid","hidden":false,"ipfs":"QmRtw5pxdKehasvfskvLVkSKjuzVjtsy2xy2iaSw1F4Q36","language":"en","transactionHash":"0x6cb913042adb905fd3f8907ad8f1f4c938e550661a06ad768af1af7e14a36b45","created":"2026-09-21T15:02:57.119Z","updated":"2026-09-21T15:02:57.119Z","title":"UsePaid","summary":"UsePaid is a cryptocurrency fee bridge that routes eligible token creator fees to named X accounts via X Money, paying 80% in dollars to recipients and using 20% to buy and burn the $PAID token.","content":"**UsePaid** is a [cryptocurrency](https://iq.wiki/wiki/cryptocurrency) fee bridge that routes the creator fees generated by tokens on supported launchpads such as [Pump.fun](https://iq.wiki/wiki/pumpfun) and [Pons](https://iq.wiki/wiki/pons) to designated X (formerly Twitter) accounts, paying the recipients in dollars through X Money.[[1]](#cite-id-cbkzktqevj) The protocol works by having a token point its creator fees at the UsePaid treasury; UsePaid then claims those fees on chain, converts 80% into dollars and pays them to the X account named in the token's description, and spends the remaining 20% buying and burning its own token, PAID.[[1]](#cite-id-cbkzktqevj) \n\n## Overview\n\nUsePaid positions itself as a bridge that turns a token's creator fees into dollars in a recipient's pocket.[[1]](#cite-id-cbkzktqevj) \"Creator fees\" are the fees a launchpad pays to a token's creator [wallet](https://iq.wiki/wiki/cryptocurrency-wallet) in respect of trading in that token; UsePaid's model redirects those fees from the deployer to a chosen X user.[[1]](#cite-id-cbkzktqevj) The project's marketing summarizes the concept as pairing \"any pump fun token to a handle to start sending them fiat,\" and its interface displays a running stream of named payouts to figures such as [Elon Musk](https://iq.wiki/wiki/elon-musk), [Vlad Tenev](https://iq.wiki/wiki/vlad-tenev), [Sam Altman](https://iq.wiki/wiki/sam-altman), Naval, Garry Tan, and [Ansem](https://iq.wiki/wiki/zion-thomas-ansem).[[2]](#cite-id-z8kmv8rbcl)​[[4]](#cite-id-pj0zmcchd8)​\n\nThe system is designed so that a deployer, rather than the recipient, initiates the arrangement. A deployer launches a token on a supported venue, points its creator fees at the UsePaid treasury, and names an X account in the token's description as the party the fees are for.[[1]](#cite-id-cbkzktqevj) The named recipient does not need to agree, know in advance, or hold a wallet; control over who may ultimately be paid rests with X Money, and UsePaid does not add a second layer of approval.[[1]](#cite-id-cbkzktqevj) The independent crypto exchange [Bitrue](https://iq.wiki/wiki/bitrue) described UsePaid in a September 16, 2026 article as a fee bridge that routes eligible token creator fees to designated X accounts through X Money.[[3]](#cite-id-1xhahj0k5t)​\n\n## Technology and Architecture\n\nUsePaid’s mechanics are described as a sequence of on-chain and off-chain steps that start with a token directing 100% of its creator fees to the UsePaid treasury, continue through scheduled fee claims and conversions on supported chains, and end with payouts in dollars through X Money alongside protocol buybacks of PAID.[[1]](#cite-id-cbkzktqevj)​[[7]](#cite-id-mezly0uufr) These steps use launchpad-specific fee-routing rules, an indexer that detects eligible tokens and claims, a ledger of fee events and pending buybacks, and integrations with [Kraken](https://iq.wiki/wiki/kraken), [deBridge](https://iq.wiki/wiki/debridge), and X Money.\n\n### How It Works\n\nUsePaid describes a five-step mechanical flow from token launch to payout. First, a deployer points 100% of a token's creator fees at the UsePaid treasury permanently. Second, the token's description names a handle. Third, the token registers itself automatically when UsePaid's indexer detects the fee direction on chain — there is no approval step and no queue. Fourth, UsePaid claims the accrued creator fees on a schedule and records each claim against its transaction signature. Fifth, the recipient's share is sent through X Money from a pre-funded float, and a public reply confirms the payment.[[1]](#cite-id-cbkzktqevj)​\n\nA token qualifies only if it meets two rules: the whole fee must be directed to UsePaid (100%, not a partial share), and the direction must be permanent.[[1]](#cite-id-cbkzktqevj)​\n\n### Supported Venues\n\nUsePaid supports two live launch venues and describes a third as under exploration:\n\n* [**Pump.fun**](https://iq.wiki/wiki/pumpfun) ([Solana](https://iq.wiki/wiki/solana)), live. Fees are directed after a token is created, using pump.fun's fee-sharing feature. This is also where the PAID token itself is issued.[[1]](#cite-id-cbkzktqevj)\n* [**Pons**](https://iq.wiki/wiki/pons) ([Robinhood Chain](https://iq.wiki/wiki/robinhood-chain)), live. Fees are directed at creation, by setting UsePaid as the token's fee wallet.[[1]](#cite-id-cbkzktqevj)\n* [**Four.meme**](https://iq.wiki/wiki/fourmeme) ([BNB Chain](https://iq.wiki/wiki/binance-smart-chain)), being explored; the project states it is not supported and may never be.[[1]](#cite-id-cbkzktqevj)\n\nOn both live venues, the arrangement ends with UsePaid as the token's permanent fee recipient, and it cannot be moved afterward.[[1]](#cite-id-cbkzktqevj) On [Pump.fun](https://iq.wiki/wiki/pumpfun), fees are directed after the coin is created through pump.fun's fee-sharing screen, which lets a creator split fees across up to ten wallets; adding the UsePaid treasury at 100% makes the token appear in its sharing configuration as a shareholder. That configuration stays editable until its authority is revoked, so a token is detected but not payable until the revoke flag is set — revoking the authority makes the direction permanent.[[1]](#cite-id-cbkzktqevj) On [Pons](https://iq.wiki/wiki/pons), the fee wallet is set at launch, and because the contract lets only the current recipient hand the fee wallet on, assigning it to the UsePaid treasury is self-locking: once it is UsePaid's treasury, the deployer cannot take it back.[[1]](#cite-id-cbkzktqevj)​\n\n### Naming a Recipient\n\nThe X account that gets paid is read from the token's description. UsePaid requires an exact line of the form \"Fees to via UsePaid,\" used anywhere in the description, with the handle bracketed by \"Fees to\" and \"via UsePaid\" so that only one reading is possible.[[1]](#cite-id-cbkzktqevj) If that specific line is missing, UsePaid falls back first to the first handle appearing in the description and then to the X account the token is linked to, both of which the project describes as less reliable.[[1]](#cite-id-cbkzktqevj) Description length differs by venue: [Pons](https://iq.wiki/wiki/pons) allows 256 characters, while [Pump.fun](https://iq.wiki/wiki/pumpfun) allows considerably more.[[1]](#cite-id-cbkzktqevj) Several token addresses associated with the system carry a trailing \"paid\" suffix as a vanity marker.[[4]](#cite-id-pj0zmcchd8)​\n\nThe documentation lists common reasons a token fails to register, in rough order of likelihood: the sharing configuration gives UsePaid only a partial share rather than the whole fee; on [pump.fun](https://iq.wiki/wiki/pumpfun) the configuration's authority has not yet been revoked; fees are directed to an address that is not the UsePaid treasury; nothing in the description names a recipient and the token is not linked to an X account; or the token is too recent for the scheduled indexer to have seen it.[[1]](#cite-id-cbkzktqevj)​\n\n### Fee Claiming and Payouts\n\nCreator fees accrue to the UsePaid treasury as a token trades and are claimed on a schedule rather than per individual trade. Each claim is written to the ledger keyed on its own transaction signature so that a claim cannot be recorded twice, and the recipient's share and protocol cut are computed at claim time and not recalculated afterward. A failed claim creates no obligation and is retried, with the fees remaining accrued in the meantime.[[1]](#cite-id-cbkzktqevj)​[[3]](#cite-id-1xhahj0k5t) For tokens launched on pons.family, the project states that fees still accrue in the fee escrow but that claiming and bridging them are paused while pons is not operational.[[7]](#cite-id-mezly0uufr)​\n\nEvery claim is divided under a fixed 80/20 split applied per claim at claim time, with no additional fees, discretion, or tiers. Eighty percent — the \"recipient share\" — is paid to the named X account in dollars through X Money, while the 20% \"protocol cut\" is spent buying PAID and burning it.[[1]](#cite-id-cbkzktqevj) The sole exception is PAID itself, whose own fees do not split and are held entirely as protocol treasury.[[1]](#cite-id-cbkzktqevj)​\n\nPayouts are triggered by a series of milestones. A recipient's share builds until it crosses $5, then $10, $20, $50, $100, $250, $500, $1,000, and every $1,000 thereafter; each crossing sends the full balance. Balances below a milestone continue to accumulate, and nothing expires for a resolved recipient.[[1]](#cite-id-cbkzktqevj)​[[3]](#cite-id-1xhahj0k5t) Because of this structure, small amounts of creator fees do not necessarily result in an immediate payment.[[3]](#cite-id-1xhahj0k5t) When a payout is sent, it draws on a pre-funded X Money balance called the \"float,\" so a payment does not have to wait on an off-ramp, and UsePaid publicly replies from its account to confirm each payout with the amount and the token it came from.[[1]](#cite-id-cbkzktqevj)​\n\n### X Money and Held Balances\n\nPayments settle into X Money, and the only requirement to receive them is an X Money account that is open to receiving. X Money is configured on X and is available to X Premium members; UsePaid cannot open or change a user's X Money account, and it checks whether a handle can be paid before opening a payable balance.[[1]](#cite-id-cbkzktqevj) As of September 2026, X stated that X Money was rolling out to select users in the United States, meaning access could not be assumed for every X user globally.[[3]](#cite-id-1xhahj0k5t)​\n\nBecause any X account can be named regardless of whether it can yet receive, UsePaid holds money for recipients who cannot be paid. A held balance stays held for seven days: if the recipient opens an X Money account within that window, the balance becomes payable and is sent on the next run. If seven days pass and the account still cannot receive, the held balance is recycled into the PAID buyback, which UsePaid states is the only thing that ever happens to an unclaimed balance.[[1]](#cite-id-cbkzktqevj) To stop receiving payments, a user turns off incoming payments in their own X Money settings, since UsePaid provides no opt-out on its own site; removal of a handle from the site can be requested by asking on X.[[1]](#cite-id-cbkzktqevj)​\n\n### Cross-Chain Treasury\n\nBecause a token earns fees on whatever chain it launched on but PAID has a single market and a single burn instruction, both on [Solana](https://iq.wiki/wiki/solana), protocol cuts earned on other chains must reach [Solana](https://iq.wiki/wiki/solana) before they can be spent. UsePaid gives the example of fees earned on [Robinhood Chain](https://iq.wiki/wiki/robinhood-chain) through pons, which would cross to [Solana](https://iq.wiki/wiki/solana) at the treasury once, over the [deBridge](https://iq.wiki/wiki/debridge) cross-chain protocol, and the project states this is the only bridge anywhere in its path; however, it also notes that pons is not operational and that pons fees therefore sit accruing in the fee escrow rather than being claimed or bridged.[[5]](#cite-id-ygmvbydlr0)​[[7]](#cite-id-mezly0uufr) Recipient payouts never touch that bridge — the recipient's share settles in dollars through X Money from the pre-funded float regardless of which chain the fee came from.[[1]](#cite-id-cbkzktqevj)​\n\n### Off-Ramp Operations\n\nUsePaid's site exposes the mechanics by which claimed [Solana](https://iq.wiki/wiki/solana) fees are converted to dollars and moved into X Money, using the exchange [Kraken](https://iq.wiki/wiki/kraken) as an intermediary. In representative activity dated 15 September 2026, SOL was sent to a [Kraken](https://iq.wiki/wiki/kraken) deposit address, swapped on [Kraken](https://iq.wiki/wiki/kraken)'s SOL/USD market as a market order, and the resulting dollars were transferred to an X Money checking account by ACH through a Plaid transfer.[[4]](#cite-id-pj0zmcchd8) One recorded sequence swapped 25 SOL at an average price of $96.73 per SOL for a gross of $2,418.25, from which [Kraken](https://iq.wiki/wiki/kraken) took a fee of $8.46 (0.35%), leaving $2,409.79 that was then sent to X Money via ACH. A parallel sequence swapped 25 SOL at an average of $96.43 per SOL for a gross of $2,410.75, a fee of $8.44, and $2,402.31 transferred onward.[[4]](#cite-id-pj0zmcchd8) The interface also logs on-ramp deposits, including $309.32 and $232.05 received from Kraken via ACH on 15 September 2026, and $11.02 received on 14 September 2026.[[4]](#cite-id-pj0zmcchd8)​\n\n## The PAID Token\n\nPAID is the token that anchors UsePaid's value-accrual mechanism. It lives on [Solana](https://iq.wiki/wiki/solana) and was issued via [pump.fun](https://iq.wiki/wiki/pumpfun); after launch it began trading on [Solana](https://iq.wiki/wiki/solana) markets and on exchanges such as [Bitrue](https://iq.wiki/wiki/bitrue).[[6]](#cite-id-h0moskx1gj)​[[2]](#cite-id-z8kmv8rbcl) The project describes PAID strictly as its value-accrual mechanism and explicitly not as a [governance token](https://iq.wiki/wiki/governance-tokens) or a fee token. Holding PAID does not change the 80/20 split, does not change who can launch a token, and does not change who gets paid; nothing about the bridge is gated behind it, and holders receive no entitlement to fees, governance, or protocol features.[[5]](#cite-id-ygmvbydlr0)​[[3]](#cite-id-1xhahj0k5t)​\n\nThe 20% protocol cut funds a buy-and-burn process. UsePaid buys PAID on the open market from the same market as everyone else, at whatever the price is when it buys, with \"no special route and no discount,\" and sends the purchased tokens to a burn address. Both the buy and the burn occur on chain so the entire path can be checked by anyone, with the stated effect that supply only ever goes down.[[5]](#cite-id-ygmvbydlr0) The accounting works by recording each claimed fee as a fee event keyed on the claim's transaction signature, then writing 20% of that event to the ledger as a pending buyback tied to the originating fee event for later reconciliation. Recycled held balances are recorded separately from protocol-cut buybacks so the two sources can be distinguished rather than blended.[[5]](#cite-id-ygmvbydlr0)​\n\nWhen the project's PAID documentation was first published, PAID had not yet been issued and the protocol cut accrued in the ledger as pending buybacks rather than being spent; the page continues to describe this pre-launch state and emphasizes that the first burn would simply spend a balance that already existed by the time it happened.[[5]](#cite-id-ygmvbydlr0) Its disclosures state that the buyback depends on fees actually being claimed and should not be interpreted as a guaranteed price-support mechanism.[[5]](#cite-id-ygmvbydlr0)​[[3]](#cite-id-1xhahj0k5t)​\n\n### Tokenomics\n\nPAID launched on [Solana](https://iq.wiki/wiki/solana) via pump.fun with a total supply of approximately 986,520,430 tokens, a figure that decreases over time as the protocol’s buyback-and-burn mechanism removes tokens from circulation.[[6]](#cite-id-h0moskx1gj) After launch, PAID began trading on [Solana](https://iq.wiki/wiki/solana) and on centralized exchanges such as [Bitrue](https://iq.wiki/wiki/bitrue).[[6]](#cite-id-h0moskx1gj) Every eligible fee UsePaid processes is split 80/20, with 80% paid to the designated X account in dollars through X Money and the remaining 20% used to buy PAID on the open market and burn it, aligning the token’s value-accrual role with the fee-bridge flow described above.[[1]](#cite-id-cbkzktqevj)​[[5]](#cite-id-ygmvbydlr0)​[[6]](#cite-id-h0moskx1gj) Public sources describing PAID do not disclose any further breakdown of allocations between parties or detailed vesting schedules beyond this overall supply and mechanism, and the project’s own disclosures stress that buybacks depend on actual fee claims and do not guarantee any particular price outcome.[[5]](#cite-id-ygmvbydlr0)​\n\n## Use Cases\nDeployers typically interact with UsePaid by launching tokens on supported venues such as pump.fun or pons.family, directing 100% of the resulting creator fees to the UsePaid treasury, and including an X handle in the token description so that those fees are routed to that account through X Money.[[1]](#cite-id-cbkzktqevj) The protocol describes a model in which the deployer, rather than the recipient, initiates this arrangement, allowing tokens to pay X users who do not need to hold a wallet or sign up with UsePaid.[[1]](#cite-id-cbkzktqevj) [Bitrue](https://iq.wiki/wiki/bitrue)’s explainer frames this pattern as a way for token creators to share trading activity with X users while simultaneously funding PAID buybacks through the protocol cut.[[3]](#cite-id-1xhahj0k5t) An additional use case introduced after launch is creator rewards for deployers, under which deployers of tokens launched through Paid can receive up to 10% of the fees those tokens generate, with payouts made via X Money alongside recipient payments.[[2]](#cite-id-z8kmv8rbcl)​\n\n## Ecosystem and Interface\nUsePaid’s ecosystem centers on launchpads and chains whose creator-fee systems can direct 100% of fees to the protocol’s treasury, with specific supported venues and cross-chain mechanics described in the Technology and Architecture section.[[1]](#cite-id-cbkzktqevj)​\n\nThe main UsePaid web interface exposes a live stream of recent payments, showing for each transfer the recipient’s X handle, token address, timestamp, amount, and transaction identifiers.[[4]](#cite-id-pj0zmcchd8) It also logs off-ramp operations such as swaps of SOL to USD on [Kraken](https://iq.wiki/wiki/kraken) and subsequent ACH transfers into X Money, alongside on-ramp deposits from [Kraken](https://iq.wiki/wiki/kraken) into the linked checking account.[[4]](#cite-id-pj0zmcchd8) A separate capital-flow view describes how fees from pump.fun are claimed on a schedule, converted to dollars through [Kraken](https://iq.wiki/wiki/kraken), and split between X Money payouts and PAID buybacks, and explains that pons fees remain in the fee escrow while pons is not operational and that claiming and bridging those fees are paused.[[7]](#cite-id-mezly0uufr)​\n\n## Team and Governance\n\nUsePaid describes itself as an independent product and states that PAID is a value-accrual token only, not a [governance token](https://iq.wiki/wiki/governance-tokens) and not a fee token.[[8]](#cite-id-03kojwpjmr)​[[5]](#cite-id-ygmvbydlr0) Holding PAID does not change the fee split, does not control who can launch tokens or who gets paid, and does not grant any entitlement to protocol fees or on-chain governance rights.[[5]](#cite-id-ygmvbydlr0) The protocol does not present any on-chain governance mechanism, and decisions about how it operates are not described as being subject to token-holder votes or other PAID-based control structures.[[5]](#cite-id-ygmvbydlr0)​\n\n## Developments\n\nUsePaid's presence on X was established in August 2026, and its pinned announcement declared the project \"officially live,\" inviting users to pair a pump.fun token to any X handle so that creator fees would be paid to that account in dollars through X Money.[[2]](#cite-id-z8kmv8rbcl) Shortly after launch, the account reported that more than $8,000 had been paid to X Money users and more than $80,000 was queued to be sent as ACH payments came through, describing the period as \"Day 1, [Block](https://iq.wiki/wiki/block) Chain 1.\"[[2]](#cite-id-z8kmv8rbcl) The account also stated that $34,825 of PAID had been \"bought back and burnt\" in a single day and praised X Money, noting that its ACH settlement occurred \"in under a few hours.\"[[2]](#cite-id-z8kmv8rbcl) These figures are the account's own statements. On 16 September 2026, [Bitrue](https://iq.wiki/wiki/bitrue) published an explainer on the project, advising that because PAID is newly launched and volatile, traders should verify its contract address and current market data before trading.[[3]](#cite-id-1xhahj0k5t) In a later update, the UsePaid X account announced \"creator rewards\" for deployers, stating that deployers can earn up to 10% of the fees for tokens launched through Paid, with those rewards paid out through X Money.[[2]](#cite-id-z8kmv8rbcl)​","recentActivity":null,"operator":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"categories":[{"id":"projects-and-protocols","title":"Projects & Protocols"}],"tags":[{"id":"Payments"},{"id":"Solana"},{"id":"BNB Chain"},{"id":"Bridge"},{"id":"Polkadot"}],"images":[{"id":"QmQLmuLwyjDfuk4Pn8hD3j8N2xXjm9CLhrUed26Kgpu9AC","type":"image/jpeg, image/png"}],"media":[{"name":"Cópia de Design sem nome (10).png","id":"Qmcf4NSFS9FqFjAjkT4FEAN1KPJB3uBed8g5UAd9woHuLn","size":null,"type":null,"source":"IPFS_IMG"}],"linkedWikis":{"founders":[],"blockchains":["solana","binance-smart-chain","robinhood-chain"],"speakers":[]},"events":[{"title":"Bitrue publishes explainer article about UsePaid and PAID","date":"2026-09-01","type":"DEFAULT","description":"Bitrue publishes an explainer article describing UsePaid and the PAID token's 80/20 fee mechanism and risks.","link":"https://www.bitrue.com/blog/what-is-usepaid","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"53dd799b-9c28-436b-a5ea-10eb3f1b88d0"},{"title":"First on‑chain claims, payouts, and off‑ramp operations logged","date":"2026-09-01","type":"DEFAULT","description":"UsePaid's site logs its first visible on‑chain claims, payouts to X Money, and off‑ramp operations via Kraken and ACH.","link":"https://usepaid.app/","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"bf5e243f-791e-4335-9bbb-0b367c5b1752"},{"title":"First PAID pool appears on Solana via pump.fun","date":"2026-09-01","type":"DEFAULT","description":"The first trading pool for the PAID token appears on Solana after its issuance via pump.fun.","link":"https://www.bitrue.com/blog/where-to-buy-usepaid-paid-token","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"7200bc04-6cf6-4180-8081-16905257656a"},{"title":"UsePaid launchpad announced with creator rewards","date":"2026-09-01","type":"DEFAULT","description":"UsePaid announces its launchpad platform integrating token fee sharing for X accounts and introduces creator rewards for deployers.","link":"https://x.com/UsePaid","country":"","continent":"","multiDateStart":null,"multiDateEnd":null,"id":"c83f4c07-eb49-4320-86b6-ed641e211689"},{"id":"c182864c-08ab-428b-8e5b-9f4c255ed244","type":"CREATED","date":"2026-09-15","multiDateStart":null,"multiDateEnd":null,"country":"United States","continent":"North America","title":"UsePaid officially launches via X announcement","description":"UsePaid announces it is officially live on X, inviting users to pair pump.fun tokens to X handles so creator fees are paid out in dollars through X Money.","link":"https://x.com/UsePaid/status/2100017768116658199"}],"founderWikis":[],"blockchainWikis":[{"id":"solana","title":"Solana"},{"id":"binance-smart-chain","title":"BNB Chain"},{"id":"robinhood-chain","title":"Robinhood Chain"}],"metadata":[{"id":"twitter_profile","value":"https://x.com/UsePaid"},{"id":"website","value":"https://usepaid.app/"},{"id":"references","value":"[{\"id\":\"cbkzktqevj\",\"url\":\"https://usepaid.app/docs\",\"description\":\"UsePaid documentation describing the fee bridge\",\"timestamp\":1790002196121},{\"id\":\"z8kmv8rbcl\",\"url\":\"https://x.com/UsePaid\",\"description\":\"Pinned post on the UsePaid X account\",\"timestamp\":1790002196121},{\"id\":\"1xhahj0k5t\",\"url\":\"https://www.bitrue.com/blog/what-is-usepaid\",\"description\":\"Bitrue report on the PAID token launch timing\",\"timestamp\":1790002196121},{\"id\":\"pj0zmcchd8\",\"url\":\"https://usepaid.app/\",\"description\":\"UsePaid site showing named payout stream\",\"timestamp\":1790002196121},{\"id\":\"ygmvbydlr0\",\"url\":\"https://usepaid.app/paid\",\"description\":\"UsePaid page describing PAID as value accrual only\",\"timestamp\":1790002196122},{\"id\":\"h0moskx1gj\",\"url\":\"https://www.bitrue.com/blog/where-to-buy-usepaid-paid-token\",\"description\":\"Bitrue explainer with PAID token metrics\",\"timestamp\":1790002805026},{\"id\":\"mezly0uufr\",\"url\":\"https://usepaid.app/capital-flow\",\"description\":\"UsePaid capital-flow description\",\"timestamp\":1790435195010},{\"id\":\"03kojwpjmr\",\"url\":\"https://usepaid.app/legal/disclosures\",\"description\":\"UsePaid disclosures\",\"timestamp\":1790435195010}]"},{"id":"previous_cid","value":"QmRtw5pxdKehasvfskvLVkSKjuzVjtsy2xy2iaSw1F4Q36"},{"id":"commit-message","value":"Expand UsePaid wiki: add 532 words, timeline, and tags"},{"id":"previous_cid","value":"QmRtw5pxdKehasvfskvLVkSKjuzVjtsy2xy2iaSw1F4Q36"}],"user":{"id":"0x8af7a19a26d8fbc48defb35aefb15ec8c407f889"},"author":{"id":"0x1E23b34d3106F0C1c74D17f2Cd0F65cdb039b138"},"views":121}