How FIRM works

What is FIRM?

FIRM brings together AI project creation, token launches on Solana through pump.fun, and trader referrals through HR OFFICE.

• BUILD: turn an idea into a website, artwork and post drafts, then prepare a token launch.
• HR OFFICE: choose a launched project, share your referral link and earn a share of creator fees generated by referred wallets.
• DOCS: instructions, requirements and operating limits.

A project draft is not a token. A token exists only after its creation transaction is signed and confirmed.

From one idea to a complete project

1. Click BUILD MY FIRM in the office.
2. Describe your idea, or leave the field blank to let FIRM invent a concept, name and ticker.
3. Set an initial purchase, a total launch limit in SOL and a Community allocation. The total limit must exceed the purchase amount to leave room for transaction costs.
4. On the public site, connect your wallet and sign in before starting paid generation. Signing in does not transfer SOL.
5. Submit the form. Your team creates the concept and briefs, then the logo, website and post drafts.
6. Follow IDEA → LOGO → WEBSITE → POSTS → REVIEW. You can close the panel: work continues on the server and results are saved.
7. If a provider fails, select RESUME FROM SAVED RESULTS. Completed stages are not repeated. After a server restart, unfinished work also requires an explicit resume.
8. Review the logo, website and posts. Completed materials are filled into the launch form automatically. Select REVIEW LAUNCH SETTINGS to continue.
9. Connect any missing services. FIRM simulates the prepared launch and compares its estimated cost, including fees, against your SOL limit.
10. Review and sign the transaction in your wallet. The limit is checked again before submission. If the estimate is unavailable or exceeds the limit, submission is blocked.

AI generation uses the server's Requesty balance and shared daily AI budget, which defaults to $1. This is separate from the SOL launch limit. Generating materials does not transfer SOL. Use the manual BRIEF THE AGENTS form when you want to supply your own name, image and detailed direction.

Your six agents

Character movement does not mean AI is running continuously. There is no unattended continuous posting, replying or buying back tokens.

Connect a wallet and launch

1. Select CONNECT WALLET and connect a compatible Solana wallet. The sign-in message proves ownership of your address; it does not authorize a transfer.
2. Open REVIEW LAUNCH. Check the name, ticker, image, purchase settings and Community allocation, from 0% to 50%.
3. FIRM stores the logo and JSON metadata on its server and uses public HTTPS URLs during launch. A public site URL must be configured. Pinata is an optional IPFS alternative.
4. Your browser creates a new mint keypair. PumpPortal prepares the creation transaction for Solana mainnet.
5. Review the transaction in your wallet and sign it. Your wallet needs SOL for network fees, token creation and any initial purchase you selected.
6. The server verifies the prepared message and signatures, simulates the transaction, checks the cost limit and submits it.
7. Wait for confirmation. If submission succeeded but the result is uncertain, FIRM checks the existing transaction instead of launching a second token.

Community allocation applies to creator fees. It does not change network, PumpPortal or protocol fees, and it does not allocate token supply.

After launch

1. Your project becomes live, with a mint address and public project page.
2. Analytics can fetch real market data. Missing data immediately after launch does not mean zero volume.
3. To publish to X, connect your API credentials, review the exact text and explicitly publish it. Replies also require a separate action.
4. Project tools let you prepare creator fee collection and token buybacks. Each operation requires review and a wallet signature.
5. A launched project with a Community allocation above zero can participate in HR OFFICE.

Share the public project page and your individual HR OFFICE referral links.

HR OFFICE: from referral to verified trade

1. Open HR OFFICE, connect your wallet and choose a launched project with a nonzero Community Pool allocation.
2. Create and share your personal referral link. It contains a unique referral code.
3. A visit is recorded as a click. Clicks are counted by browser and link; they are not a guaranteed count of unique people.
4. The referred trader must connect their wallet and sign in on the site. Clicking a link alone is not enough to attribute future trades.
5. The first referrer is retained for 30 days for each project and wallet. Self-referrals and a builder's referrals to their own project do not earn rewards.
6. After a trade, the server checks the finalized transaction, mint, trader wallet, attribution time and actual creator fee in a Pump or PumpSwap event.
7. Verified trades update attributed volume, fees and earnings. The same trade event cannot be credited twice.

Only supported SOL-denominated Pump / PumpSwap trades count. Other exchanges, unconnected wallets, trades before attribution, and unsupported or incomplete events are excluded.

Background verification processes one active campaign per minute and checks the latest 250 transactions for each referred wallet. Use VERIFY TRADES for a manual check. A trader can submit an older trade signature through the verification form.

How rewards are calculated

A referrer earns 20% of the Community Pool share attributable to creator fees generated by their referred wallets.

Example: a trade generates 0.01 SOL in creator fees and the allocation is 30%. The pool share is 0.003 SOL. The referrer earns 0.0006 SOL, or 6% of that creator fee.

The remaining 80% of the pool share is not automatically credited to that referrer. Rewards are not a percentage of trade volume, total trading fees or token supply. Calculations use whole lamports and round down.

• Clicks: recorded visits through your link.
• Wallets referred: wallets with confirmed attribution.
• Volume generated: verified attributed trading volume in SOL, not total market volume.
• Fees generated: creator fees from those trades.
• Earned: rewards accrued.
• Paid / Pending: completed payments and amounts reserved for unresolved payouts.
• Claimable: the amount available to request, limited by pool funding.

Fund the pool and claim SOL

1. The builder collects available creator fees into their own wallet.
2. In project tools, the builder separately prepares a Community Pool deposit and signs the SOL transfer.
3. The server verifies the finalized transfer and its project reference, then credits the deposit once.
4. The referrer selects CLAIM. The available amount is limited by both unpaid earnings and verified pool funding.
5. The server reserves the payout and sends SOL from the configured treasury only to the authenticated recipient's wallet.
6. Once finalized, the amount is marked paid. An uncertain transaction keeps its reservation until reconciled, preventing duplicate payment.

Claims are unavailable without a configured treasury key and sufficient SOL, even if rewards have accrued. An Earned balance does not guarantee an immediate payout.

The office and laboratory

• OFFICE: six workstations and characters. Select an agent card or workstation to open its details.
• LAB: a laboratory with equipment and a workstation for the same project.
• − / 100% / +: change the scene scale. The pause button stops decorative animation.
• Office characters navigate around furniture, take breaks and return to their computers. Agents with active tasks remain at their workstations.
• Screen animations, printers and character movement do not make AI requests or spend your Requesty balance.

Required connections

Provider keys are configured on the server, never in public JavaScript. Server connection settings can only be changed by the administrator. X access is connected through project tools. Connection availability is shown in the control room.

Status and troubleshooting

• Draft / Not launched: the project exists, but its token has not been created.
• Queued / Working: a task is waiting or running. Do not restart it just to trigger animation.
• Done: that task's result is saved. This does not mean the token is live.
• Paused: the agent is waiting for an action or a required condition.
• Submitted: the transaction was sent and confirmation is being checked. Check the existing transaction before retrying.
• Live: the launch is confirmed.
• Requesty error: check the provider balance, model availability and task message. Retrying generation can incur another charge.
• Missing rewards: check that wallet attribution preceded the trade, the 30-day window is valid, the market is supported and the trade is finalized. Then run Verify trades.
• Earned balance but no Claim: check pool funding, treasury configuration and pending payouts.

Data and access

Projects, tasks, events, referral records and accounting are saved in SQLite on the server. Wallet ownership is verified with a single-use, expiring sign-in challenge. The server checks operation permissions and protects state-changing requests against cross-site submission.

The Requesty key stays in the server environment. Stored X credentials are encrypted. The standard wallet flow does not request a user's private key: users sign transactions in their own wallets. The Community treasury has a separate server-held key, so the server operator controls its funds.

Keep the database and encryption key backed up, serve the app over HTTPS and protect the host. Never place secrets in referral links or public files.

Launch checklist

1. Create a brief and review the website, artwork and copy.
2. Connect your wallet and verify the token settings and spending limit.
3. Sign the launch and wait for network confirmation.
4. Open the project page and verify the mint and public links.
5. If HR OFFICE is enabled, fund the Community Pool and invite participants.
6. Track verified trades, earnings and the remaining pool balance.