How Squads works

Pons pays creator fees to a single address, the creator wallet, set when a token is created. Squads lets that address be a small contract owned by several people instead of one. Every fee the token earns lands in the contract, and anyone can trigger a split that pays each member their percentage directly. Nothing is held for you: the contract never custodies your tokens, and it cannot spend fees on anything except paying members and the platform fee.

1. 1
   Create a team
   Pick a picture and a name, list wallets and their shares. One transaction deploys your team wallet.
2. 2
   Launch on Pons with it
   Paste the team address as the creator wallet on Pons, or launch from the Launch page here. You stay the on-chain creator; only the fee recipient is the team.
3. 3
   Harvest
   When fees have accrued, anyone presses Harvest. The team pulls its fees from the Pons escrow and pays every member in the same transaction.

On Pons v2, a token starts on a bonding curve and graduates into a permanently locked Uniswap v4 pool. Every trade pays a fee that is split between the protocol, the creator, and optional buybacks, plus any creator tax the creator set at launch. Fees are paid in the token's quote asset: ETH, USDG, cbBTC, or a tokenized stock, whatever the launch was paired against.

Creator fees are not pushed to the creator. They accumulate in the Pons fee escrow under the creator wallet's address until that wallet claims them. A Squads team is such a wallet, so its fees sit in the escrow under the team's address until someone harvests.

Pons also gives the creator wallet two controls after launch: it can hand the creator role to another address, and it can switch creator-funded buybacks on or off. Everything else about a launch is immutable. Read the Pons v2 docs for the full mechanics.

A team is a contract deployed by the Squads factory. It stores a name, a picture, up to 32 members, and each member's share in basis points. Shares must total exactly 100%. Every member must have a share above zero and no wallet can appear twice.

Creating

The person who creates the team does not get special rights. Membership is the only role.

Address

The team address is what you give Pons. It never changes, and it can receive any ERC-20 or ETH at any time; direct transfers are split like fees.

Registering launches

Anyone can register a Pons token with a team, if that token's creator wallet is the team. Registered tokens appear on the team page and on the Tokens page.

Harvest asks the Pons escrow to pay out what the team is owed for one asset. Distribute splits whatever the team contract holds of that asset. The dashboard button does both in one transaction. Anyone can call either, so a member, a bot, or a stranger can move fees along; funds only ever go to members and the platform fee, never to the caller.

Per asset

A team that launched an ETH token and a USDG token has two separate balances, harvested and split separately. Rounding dust stays in the contract for the next round.

Deferred payouts

If a member's wallet cannot receive a payment, for example a contract that rejects ETH or a blocklisted stock-token holder, their share is parked as a deferred balance they withdraw later. Nobody else's payout waits for it.

Platform fee

Before members are paid, a small fee goes to the buyback vault. See section 7.

Shares are locked. Adding a member or re-weighting shares is a proposal, and a proposal executes only when every current member has approved it. The proposer's approval counts immediately, so a two-person team needs one more click and a one-person team executes at once.

Old fees, old split

The moment a team change executes, everything the contract holds in tracked assets is distributed under the old shares first. Money earned under one agreement is never redistributed under another.

Stale and expired

Any team change makes older open proposals stale. Proposals also expire after 30 days. The proposer can cancel their own proposal while it is open.

Removal

The contract accepts any new member table, so a member can be removed, but only with that member's own approval like everyone else's. The app focuses on adding and re-weighting.

Pons attaches two controls to the creator wallet, and since the team is that wallet, the team holds them. Both go through the same unanimous proposal flow so no single member can act alone.

Transfer the creator role

Hand a token's creator role to another address, for instance a community Safe or a new team. After the team approves, Pons enforces a 3-day timelock before the change can be completed from the team page.

Buybacks

Enable or disable Pons' creator-funded buybacks for a token. On Pons, bought tokens vest over five years.

Every distribution sends a platform fee to the Squads buyback vault before members are paid. It is 1% today and capped at 5% in the contract; only the factory owner can change it, and teams read it live so a change never requires touching a team.

The vault can only buy $SQUADS

It has no withdraw function. The only way value leaves is a swap into $SQUADS through a swapper adapter set by the owner.

Buybacks are permissionless

Anyone can trigger one. The vault takes the adapter's own quote and rejects any fill worse than 3%, so a caller cannot loosen the slippage. Bought tokens are burned.

Until $SQUADS exists

The vault simply accumulates fees in every quote asset it receives.

The Launch page calls the Pons factory from your own wallet, with your team as the creator fee recipient. Pons records you as the deployer, so attribution on Pons stays with you, and records the team as the creator wallet, so fees flow to it.

Immutable metadata

Name, symbol, image, description, socials, pair asset, creator tax, and supply cannot be edited after launch. The form uploads your image and stores its URL on chain.

Launch fee

Pons charges a small fee in ETH, shown on the button. Squads adds nothing.

Or launch on Pons directly

Paste the team address into the creator wallet field there and register the token with the team afterwards.

You can create a team without opening the site. Post on X, tag @squadsrh, attach a picture, and write the command in the same post:

@squadsrh create Cat Team @alice 50 @bob 30 @carol 20

The name

Everything between “create” and the first tagged account. Up to 64 characters.

The members

Each tagged account becomes a member. Numbers after a handle are that member's share in percent; they must add up to 100. Leave them out for an even split.

The picture

Attach a photo to the post. It becomes the team image, copied to our storage so it stays up even if the post is deleted. A post without a photo gets a reply asking for one.

The wallets

Every member gets an embedded wallet tied to their X account, created through Privy if they have never logged in. Log in with X on the site and the team is already yours to manage.

The reply

@squadsrh replies with the team link within a minute. The team is created by our relay wallet, which keeps no rights over it; only members can propose changes.

Limits keep it sane: two to 32 members, one team per account per hour, and a daily cap on the relay. If a post cannot be parsed the reply says what to fix.

Images

Team pictures and token images are uploaded through the site, resized to 512px, and stored with it. Only the URL goes on chain. A team image is required.

X handles

Any member can set the team's X handle and website, and each member can set their own. They are self-reported labels; nothing verifies them on chain.

Login

Wallet connection runs through Privy: an external wallet, email, or X. Users who arrive without a wallet get an embedded one. The app never holds keys.

Everything runs on Robinhood Chain, chain id 4663. Sources are verified on Sourcify and mirrored by Blockscout.

Each team is a minimal-proxy clone of the implementation, so creating one costs a fraction of a full deployment. The factory keeps registries of teams and registered launches, which is what the Teams and Tokens pages read.

Unaudited code

Pons v2 states its own contracts are unaudited while reviews are in progress, and Squads has unit tests but no audit. Do not route more than you can afford to lose.

Immutable choices

Shares can change by unanimous vote, but a token's pair asset, tax, and metadata never can.

Members are trust boundaries

A member who refuses to approve blocks every team change. Choose members you can reach.

Stock-token quote assets

They follow market hours and can drift from their reference price when markets are closed. Fees in those assets carry that risk.

Ready? Create a team.