How ArgusPay works
ArgusPay is a fee bridge for Argus. A token is launched through us, we collect its creator share on Arc, and 80% is paid to an X account through Money. Nobody has to sign up to be paid.
Overview
ArgusPay turns a token's creator share into dollars in someone's pocket. A launcher creates a token on Argus through ArgusPay and names an X account. That account is who the fees are for.
Everything between the two is mechanical. Tax accrues to the launch's splitter as the token trades, Argus credits the creator share to our treasury, we claim it on chain, 80% is paid to the recipient through Money, and 20% buys $ARGP and burns it. Every step is recorded against the claim that produced it, and every payout is confirmed in public.
The recipient is not asked to do anything first. There is no account to make and no wallet to connect, so a payout can arrive from a token they have never heard of. Control sits where it already did: Money decides who is allowed to pay an account, and you can also ask us directly. Section 13 covers stopping payments.
- 1A token is launched through ArgusPayOur treasury calls the Argus Portal, so the treasury is the creator of record forever. See section 3.
- 2The launch names a handleThe recipient is a launch input. We write it into the description and the token's X link. See section 4.
- 3The token registers itselfOur indexer sees the launch event on chain and registers the token. There is no approval step.
- 4Fees are claimedWe claim the credited creator share on a schedule and record each claim against its transaction hash.
- 5The recipient is paid in dollarsThe recipient share is sent through Money from a pre-funded float, and a public reply confirms it.
Supported venues
Today there is one venue. Which venue a token launched on would change how fees are directed and nothing else: the split, the payout rail and the ledger are the same everywhere.
- Argus
- Arc, chain ID 5042. Live. Fees directed at creation, by launching through ArgusPay. $ARGP is issued here.
- pump.fun
- Solana. Being explored. Not supported, and may never be.
- pons.family
- Robinhood Chain. Being explored. Not supported, and may never be.
Launching through ArgusPay
On Argus, the address that receives Creator funds is the wallet that called the Portal's launch function. It is written into the launch record and the splitter at creation, there is no field to set it to someone else, and nothing can transfer it afterwards. So a token cannot be launched elsewhere and then pointed at us. It has to be launched by us.
That is what the Launch page does. You fill in the name, ticker, image and the handle to pay, your wallet pays gas in USDC and any dev buy, and our treasury submits the launch. Two rules hold on every launch, and both are enforced by the Portal rather than by a promise:
- When
- At creation. There is no second visit and no revoke step.
- Allocation
- Creator funds 100%. The whole creator share, so the payout we publish is the whole of what the token earned.
- Tax
- 3% on buys, 3% on sells. One published preset, fixed for the life of the hook.
- What we watch
- The Portal's
TokenCreatedevent, filtered on creator = treasury. - Made permanent by
- The launch itself. Argus has no owner on this line and no way to change taxes, allocation or creator.
Launching a token through ArgusPay constitutes acceptance of the Terms of Use by the launcher.
Naming the recipient
The X account that gets paid is a launch input, not something we parse later. We write this line into the token's description so anyone reading Argus can see who is paid:
Fees to @yourhandle via ArgusPay
We also set the token's X link to that handle, which lands in the launch event on chain. The description stays yours otherwise, up to Argus's 280-character limit.
The recipient does not need to agree, know in advance, or hold a wallet. That is the point of the design: a token can be launched for someone, and the first they hear of it is the money arriving and a public reply saying where it came from.
The 80/20 split
Every claim divides the same way. There is no discretion in it, no schedule to negotiate, and no tier that changes it.
- To the recipient
- 80%, paid in dollars through Money
- Protocol cut
- 20%, spent buying $ARGP and burning it
- Applied
- Per claim, at claim time
- Fees we add
- None. The 20% is the whole of it
- Before us
- Argus keeps 10% of collected tax and LP fees. That is fixed in the Portal and applies to every Argus launch, ours included.
- The one exception
- $ARGP itself does not split. All of its own fees are held as protocol treasury
How claims work
Tax does not reach us on every trade. The launch's hook collects it, Argus's keeper cranks the splitter, and the creator share is credited to our treasury rather than pushed. It sits there until it is claimed, which we do on a schedule rather than per trade. Claiming per trade would spend more in gas than it collected on a quiet token.
Each claim is written to the ledger keyed on its own transaction hash, so a claim cannot be recorded twice and every obligation can be traced back to the on-chain event that created it. The recipient share and the protocol cut are both computed at that moment, from that claim, and neither is recalculated afterwards.
A claim can fail. RPC providers go down and transactions revert. A failed claim creates no obligation and is retried; the credit stays on the splitter in the meantime and is not lost. Claiming is permissionless on Argus and always pays the treasury, so a claim someone else triggers lands in the same place and is recorded the same way.
Payout milestones
Payouts land at milestones. A recipient's share builds until it crosses $5, $10, $20, $50, $100, $250, $500, and $1,000, then every $1,000 after. Each crossing sends the full balance.
Balances below a milestone keep building; nothing expires for a resolved recipient. If the account cannot receive yet, the balance is held for 7 days. See section 9.
Getting your fees
If a token has named your handle, the money is already yours. There is nothing to claim and no form to fill in. It is sent once the balance crosses a payout milestone and your Money account can receive.
- 1A token names your handleSomebody launches a token through ArgusPay and points its creator share at your X account.
- 2Fees accrue and are claimedTrading generates tax. Argus credits the creator share and we claim it on chain on a schedule.
- 380% is paid to youSent through Money from a pre-funded float, so it does not wait on an off-ramp.
- 4A public reply confirms it@ArgusPay replies so you and your audience can see where the money came from.
You are not required to do anything, acknowledge anything, or agree to anything. Receiving a payment does not make you a customer of ArgusPay or a promoter of the token that named you.
Money you receive through ArgusPay may be taxable to you. Nothing about a payout decides how it should be treated, ArgusPay does not issue tax documents, and nothing on this site is tax advice. Where the law requires us to collect information before paying, the payout waits as a held balance until we have it.
X Money setup
Payments settle into Money, so the only requirement on your side is an Money account that is open to receiving. That is configured on X, not here, and ArgusPay cannot open one for you or change its settings.
We check whether a handle can be paid before opening a payable balance. If it cannot yet, the money is held for 7 days rather than lost.
Held balances
Any X account can be named, whether or not it has Money. Where a handle cannot yet receive, the money is not lost and it is not sent anywhere else. It is held for them.
- Who can be named
- Any X account
- Held for
- 7 days
- If they open X Money
- Paid on the next run
- If they never do
- Passes to the protocol treasury after 7 days, where it funds the buyback the same way the protocol cut does
The public confirmation
Every payout is announced. @ArgusPay replies to the recipient with the amount and the token it came from, so the recipient and their audience can both see it. Most were not asked before their handle was named, so the payment is usually the first they hear of it, and the reply is what they can check it against.
The treasury and USDC
Argus launches trade against USDC, and USDC is also Arc's gas token. The creator share is credited in USDC and claimed in USDC, so nothing on the claim path is swapped or bridged. The treasury is one address on one chain, and it is the creator of record for every token launched through ArgusPay.
Payouts do not leave the chain as USDC. The recipient share settles in dollars through Money from a pre-funded float, and the float is topped up from the treasury separately. That is the only off-ramp in the system, and it never sits between a claim and a payout.
$ARGP and the buyback
The protocol cut is spent buying $ARGP on Arc through the same Uniswap v4 router everyone else uses, at whatever the price is when it buys, and the tokens are sent to a burn address. Both halves are on chain and can be checked by anyone.
$ARGP gates nothing. Holding it does not change the split, does not change who can launch, and does not change who gets paid.
Stopping payments
Who may pay you is a setting on your Money account. Turning off incoming payments there stops ArgusPay paying you, the same as it stops anyone else.
You can also ask us directly. Send a request from your handle, or with reasonable proof you control it, to @ArgusPay on X or to admin@arguspay.pro. We honor removal within 7 days: your handle comes off the site and goes on a do-not-pay list. Because claiming on Argus is permissionless, fees for a token that names you may still reach the treasury; they are then treated as a held balance and pass to the protocol treasury after 7 days. A balance already held for you is paid if you ask for it within its hold period.
If a token is not showing
Registration is automatic, so a token that has not appeared has failed one of a short list of conditions:
- Not launched through us
- The launch record's creator is not the ArgusPay treasury. Argus tokens launched from any other wallet pay that wallet, and there is no way to redirect them.
- Not a USDC launch
- The launch trades against a quote asset other than USDC. We only launch, and only index, USDC-quoted tokens.
- Too recent
- The indexer reads Arc on a schedule. A token created moments ago has not been seen yet.
- Wrong Portal
- The token was created by an older Argus Portal. We index Portal #7 launches only.
Contracts and events
Arc mainnet, chain ID 5042. Verify the chain ID and that each address has code before you trust any of it.
- Treasury
- 0xA97Ec0De…e8F90123
- Argus Portal #7
- 0xB021Be53…9c6e97Da
- USDC
- 0x36000000…00000000
- Detection
TokenCreated(token, creator, name, symbol, poolId, imageURI, website, twitter, telegram)- Claiming
splitter.claim(treasury) → (amountUsdc6, amount18, usdcOut6)- Credit events
Accrued(to, currency, amount) · Claimed(to, currency, amount)
Argus publishes its ABI and address bundle at arguspad.io/argus-v4.json and an integration guide at argus.world/docs.
Glossary
- Creator funds
- The allocation Argus credits to a launch's creator. Set to 100% on every ArgusPay launch.
- Splitter
- The per-launch Argus contract that accounts for revenue and credits payouts.
- Hook
- The per-launch Uniswap v4 hook that applies the buy and sell tax on swaps.
- Claim
- An on-chain transaction in which ArgusPay collects the credited creator share for a registered token.
- Recipient share
- 80% of a claim, payable to the named X account.
- Protocol cut
- 20% of a claim, spent on $ARGP buybacks.
- Held balance
- A recipient share recorded but not yet payable, because the handle cannot receive. Held 7 days, then passes to the protocol treasury.
- Float
- The pre-funded X Money balance payouts are sent from, so a payment does not wait on an off-ramp.
- Treasury
- The wallet that launches every token and receives every creator share. The creator of record on Argus.