Production foundation
The API, wallet auth, waitlist, X and Telegram intake, durable workers, and all 26 database migrations are deployed. The public production web still shows the launch waitlist.
Bagwork field manual / reconciled July 10, 2026
Build the claim case. Open the books. Pay the work.
Bagwork is the back office for surviving meme coin communities. It turns activity into evidence, creator fees into a public operating budget, and completed work into receipts anyone can check.
truth ledgerpreview
- production web
- launch waitlist
- product surfaces
- this preview
- money authority
- named wallets
- bot custody
- none
The bot never touches your money. The API builds. The browser checks. A named wallet signs. Finalized chain state becomes the receipt.
availability
Read the status before the feature.
“Built” describes code. “Production” describes deployed behavior. This page keeps those claims separate.
This preview build
The claim-case, treasury, work-network, token-charter, and expanded Pump.fun surfaces are visible here. Their newest data routes require the matching branch API before they can show live records.
Separate signing gates
The Bounty path builds and verifies wallet transactions, but real settlement waits on the Bagwork program deployment. Pump.fun builders are separate, include simulation, and do not depend on that program; their newest routes are still preview-only.
Explicitly deferred
The DEX Screener Fundraiser, general multi-contributor campaigns, campaign refunds, and generic public Solana action creation are not V1 features.
00 / the operating loop
From group chat chaos to a public operating record.
- 01
Build the claim case
Collect activity, proposals, proof, and receipts that show a community is still operating.
- 02
Submit outside Bagwork
Use the evidence in a pump.fun CTO application. Pump.fun alone decides whether to approve it.
- 03
Verify the handoff
After approval, inspect canonical on-chain state and confirm the authority or fee route changed.
- 04
Open the books
Publish named treasury wallets, fee inflows, proposals, signer actions, and receipts.
- 05
Pay useful work
Fund clear Bounties, review proof, sign payouts, and turn completed work into public receipts.
01 / claim case
Two claims. Two different authorities.
A Bagwork community claim and a pump.fun CTO application are separate decisions. Neither one becomes official from a form submission alone.
Bagwork community claim
A signed-in wallet creates a durable request. The board stays limited until an allowlisted human reviewer approves it. Production intake works; reviewer decisions currently fail closed because the reviewer allowlist is empty.
pump.fun CTO application
Bagwork organizes activity, proposals, proof, and receipts into a stronger case. Pump.fun reviews the application at its discretion. CTO Radar never reports pump.fun application status.
Approved authority handoff
If pump.fun approves a change, Bagwork can inspect canonical chain state and verify the resulting creator, sharing config, pool, and fee-route state.
Bagwork strengthens the case and verifies the result. It never guarantees approval.
02 / public treasury
A treasury page that answers the group chat.
The treasury is a public reconciliation layer around named wallets. Proposals record intent, named signers execute, and verified receipts show what actually happened.
Balances and fee sources
Reconcile named treasury wallets, native SOL balances, bonding-curve claimables, PumpSwap claimables, and the current fee route. Claimable fees may use a non-native quote asset.
Ledger and receipts
Separate inflows from signer-approved spends. A transaction is marked verified only after trusted RPC evidence matches the expected instruction and destination.
Evidence export
Export a JSON evidence pack with community milestones, observed activity, receipt evidence, and confidence labels. Activity remains a heuristic, not ownership proof.
Honest bounds
Treasury history is a projection over the latest 250 proposals. It is never presented as an unbounded lifetime total.
Preview status: the interface and API are built locally. This Vercel preview needs the matching branch API to populate the newest treasury data.
03 / bounties
A brief, locked funds, reviewed proof, one receipt.
V1 Bounties are single-funder and SOL-denominated. Social bots can point people to the website, but funding, proof review, payout, and refund stay behind wallet signatures.
Post and approve
Create a clear deliverable, reward, deadline, payout authority, and acceptance test. Funded work requires a claimed community before moderator approval.
Lock funds until proof
The funder wallet signs the on-chain funding transaction. Bagwork reconstructs the exact wallet return and records a finalized RPC-verified receipt.
Review and settle
A reviewer accepts or rejects submitted proof. The payout authority signs a winner payment, or the authorized wallet signs a refund under the published rules.
No automatic payout
Winner payments are intentionally signer-controlled. Automatic payout and USDC settlement remain future work.
Production gate: the transaction path is built, but the configured Bagwork program is absent from devnet and mainnet. No real Bounty settlement is available yet.
04 / raids and pulse
Ping humans. Record what happened.
Raid and Pulse are watch-only coordination surfaces. They create a public board and record useful context, but never automate engagement, promise rewards, or instruct a wallet to trade.
Raid board
Open a target and public coordination page from the website or Telegram. Humans choose whether to participate on their own accounts.
Token Pulse
Post a public community update or status message on the board. It is observation, not endorsement, safety certification, or financial advice.
Observed Activity
Verified proposal events, chat, and eligible X mentions can feed a decayed activity score. Duplicate events and repeated actors are bounded by stable keys and scoring windows.
Evidence, not engagement pay
Raid and Pulse history can strengthen the community operating record. No token or financial reward attaches to likes, replies, reposts, or engagement counts.
Production intake: website and Telegram can create Raid and Pulse records. X webhook intake is live, while background X replies and Telegram mirrors remain dry-run.
05 / pump.fun verification
The form records intent. The wallet signs. Chain state decides.
Pump.fun fee proposals use canonical state inspection, unsigned transaction building, browser-wallet approval, and finalized receipt verification. Bagwork never invents a recipient or hides a signing step.
Inspect first
Resolve the bonding curve, sharing config, creator vault, canonical PumpSwap pool, signer, fee authority, and known eligibility limits before offering an action.
Fail closed
Unknown historical eligibility, Cashback Coins, noncanonical pools, unsupported sharing versions, and revoked admins produce explicit limits instead of optimistic actions.
Build and simulate
The API builds an unsigned route, collection, AMM sweep, or distribution transaction. The browser validates it before the connected wallet can sign and send.
Verify the receipt
The API checks the finalized transaction, expected signer, exact instruction, canonical recipient, and before-and-after state diff before recording success.
Bagwork's own planned launch uses 70% of creator fees for the creator wallet and 30% for a separate Bounty treasury. That is not total trading volume and not a default split for other communities.
06 / work network
Verified work becomes the distribution loop.
Creator fees fund useful work. Contributors ship. Verified receipts become public proof that the community can operate after the original developer leaves.
Receipts feed
Publish only trusted server and RPC-verified funding, payout, refund, and Pump.fun receipts from the latest 100-proposal sample.
CTO Radar
Show observed Bagwork board and claim state for active, dormant, claimed, pending, or disputed communities. Radar is not pump.fun status or endorsement.
Genesis Season
Group useful Bounties around launch QA, onboarding, treasury education, integrations, and security. Never reward engagement counts or trading.
Contributor privacy
V1 publishes only an aggregate distinct-winner count. Portable profiles and proof history will be opt-in rather than automatic wallet dossiers.
Future work: Birdeye market signals, opt-in contributor passports, and USDC Bounty settlement.
08 / token charter
The token gets utility. It never gets the keys.
The Bagwork token is live on pump.fun at Ey7h7iJ95AYttb5P2MzBPxwYVj4XogCKdmXqaM2Apump. Planned utility covers credits, operating limits, premium exports, perks, and clearly labeled visibility boosts.
01
No custody or control over treasury funds
02
No replacement for wallet signatures
03
No yield, guaranteed rewards, or revenue share
04
No buybacks, burns, or holder distributions
05
No paid activity score or reputation
06
No gate on raids, claims, voting, or Bounty creation
Post-launch work still requires a published security review, verified creator and Bounty wallets, controlled X and Telegram delivery tests, and public treasury and payout receipts.
Read the charter09 / status and gates
What still has to happen.
01
No community-claim reviewer allowlist in production
02
No Birdeye token feed, so watcher token ingestion stays dry-run
03
No active Helius provider subscription until targets and credit budget are approved
04
No deployed Bagwork program on devnet or mainnet
05
X replies and Telegram background mirrors remain dry-run
06
No token ticker, security report, launch wallets, or real launch receipts yet
on hold
Deferred from V1
DEX Screener Fundraiser, general multi-contributor campaigns, per-contributor campaign refunds, and generic public Solana action creation.
future
Later, but not on hold
Automatic Bounty payout, USDC settlement, opt-in contributor passports, and Birdeye market signals for CTO Radar.
route index
Go to the operating surface.
Community boardssearch, claim setup, chat, and observed activityProposal boardPulse, Raid, Bounty, Pump.fun, proof, and receiptsWork networkverified receipt sample, CTO Radar, and Genesis SeasonToken charterplanned utility, launch gates, and the permanent never-listPrivate run logwallet-owned agent actions and finalized execution records
07 / social intake
Bots open the board. Humans do the work.
Telegram command intake and signed X webhook intake are deployed. Commands create watch-only proposals or safe notices. They never approve, fund, sign, or move money.
/start /helpShow the safe command list and website links.production/pulse $TOKENCreate an open community pulse.production/raid $TOKEN target:urlCreate an open raid board. Humans choose whether to act.production/status prop_123Return the public proposal page.production/wallet CODE /linkwallet CODETelegram DM only. Link the sender to a website-issued wallet code without exposing it in a group.production@bagworktech wallet CODEX only. Consume a website-issued code that is bound to the intended handle.production/link CODETelegram group only. Link a board after both the caller and bot pass admin checks.production/diagnoseTelegram group only. Refresh board, admin, pin, and topic setup state.production/bounty /pumpfees /dexReturn on-hold guidance. They never fund or sign from chat.on holdProduction note: X background replies and Telegram proposal mirrors are deployed in dry-run mode. The bot pings people; it never automates likes, reposts, comments, or wallet actions.