BAG Token White Paper
A detailed architecture and launch paper for the optional web-only Bag Guy crypto rewards layer on Solana. The shopper app remains usable without crypto, wallet connection, NFTs, or token participation.
Contents
1. Executive summary
Bag Guy is an AI-powered savings app for groceries, household items, and everyday essentials. Its public shopper experience focuses on scanning, deals, Bag Points, Store Credit, meal planning, shopping lists, SNAP-friendly discovery, and Shopper Share.
The BAG token system is a separate optional web layer. It is designed to support wallet-gated membership benefits, transparent treasury reporting, usage-based rewards, NFT membership credentials, and future ecosystem incentives. The token architecture is Solana-based, fixed supply, and explicitly avoids rebase, APY, yield, or profit language.
2. Problem
Grocery savings are fragmented across weekly ads, manufacturer coupons, store coupons, loyalty apps, receipts, local offers, and meal planning workflows. Shoppers often do not know which savings apply until checkout, and families have limited tools for turning savings into repeatable planning behavior.
At the same time, crypto rewards frequently fail when they lead with speculation instead of utility. Bag Guy separates the shopper product from the optional wallet layer so mainstream users can save without crypto friction while crypto users can opt into transparent membership and reward mechanics.
3. Bag Guy solution
Shopper app
One scan code, barcode scanning, receipt scan, local deals, coupons, weekly ads, Rewards, Meal Planner, Shopping List, Shopper Share, SNAP-friendly savings, and retailer map.
Backend systems
Receipt-safe reward contract, idempotent reward source IDs, product/coupon matching, provider connector architecture, recipe recommendations, and provider onboarding docs.
Wallet-gated web layer
Optional wallet connection, treasury transparency, BAG reserve status, membership badges, and crypto rewards pages outside the default mobile app flow.
Agent operations
Telegram GPT Bot Core and Bag Guy work bags help package requests, approve work, prepare Codex task files, and keep unsafe execution disabled by default.
4. BAG token design
| Field | Value |
|---|---|
| Name | Bag Guy |
| Symbol | BAG |
| Network | Solana |
| Token standard | SPL token |
| Total supply | 10,000,000,000 BAG |
| Decimals | 9 |
| Supply model | Fixed supply. No rebase logic, no automatic supply adjustment, no APY/yield model. |
| Purpose | Utility rewards token for Bag Guy shopping rewards, membership access, treasury transparency, and partner incentives. |
5. Allocation model
| Allocation | Percent | Amount | Purpose |
|---|---|---|---|
| Rewards Pool | 40% | 4,000,000,000 BAG | Usage-based rewards, shopping actions, verified engagement, campaign rewards. |
| Liquidity | 20% | 2,000,000,000 BAG | Initial and future BAG/USDC liquidity planning, subject to approval. |
| Treasury / Operations | 20% | 2,000,000,000 BAG | Operational reserves, ecosystem costs, treasury programs. |
| Team / Founder Vesting | 10% | 1,000,000,000 BAG | Locked or vested allocation. Final schedule requires legal/security approval. |
| Partnerships / Retailer Incentives | 10% | 1,000,000,000 BAG | Retailer, coupon provider, community, and growth incentives. |
All role wallets should use distinct Squads vault addresses: rewards, liquidity, operations, team vesting, partnerships, and authority. The authority wallet may also be used as the mint authority wallet where policy permits.
6. Rewards engine
Rewards are based on usage and eligible activity, not yield. The current architecture supports fixed reward pools and configurable multipliers.
Eligible activity examples
- Product scan matched to eligible offer.
- Receipt scan processed through the mobile-safe receipt endpoint.
- Deal save or coupon clip.
- Recipe shopped through Meal Planner.
- Shared list, recipe, coupon, or deal that helps another shopper save.
- Referral signup or membership event, subject to verification and anti-abuse controls.
BAG holding multiplier placeholders
| BAG balance tier | Multiplier |
|---|---|
| 0 BAG | 1x |
| Low | 1.2x |
| Medium | 1.5x |
| High | 2x |
Actual eligibility, frequency limits, provider confirmations, and jurisdiction rules must be enforced before live rewards distribution.
7. NFT membership system
NFT membership badges are planned as optional credentials for wallet-connected users. They do not replace the mobile app membership system, and they are not required for ordinary shopping savings.
| Tier | Unlock path | Benefit examples |
|---|---|---|
| Free Bag | App membership or wallet claim | Starter access, basic rewards, one scan code. |
| Small Bag | Subscription or BAG holding | More local deals, receipt boosts, expanded coupon matching. |
| Medium Bag | Subscription or BAG holding | 2x points prompts, advanced coupons, premium meal plans. |
| Large Bag | Subscription or BAG holding | Concierge picks, route optimization, best deals near user. |
Solana NFT integration is planned around Metaplex metadata and Phantom/Solflare compatibility.
8. Treasury system
The treasury layer is designed for transparency and disciplined allocation. It tracks revenue and separates rewards, liquidity, operations, vesting, and partnership reserves.
Read-only transparency
- Public treasury wallet address can be displayed for transparency.
- Private keys are never stored in the app, backend repo, or public website.
- Investor/crypto information remains wallet-gated or web-only, separate from public shopper screens.
Buyback and burn simulation
The current architecture includes placeholder simulation for BAG buyback and burn. No live transaction should occur until legal, security, liquidity, and signer approvals are complete.
9. Liquidity plan
The planned initial market structure is BAG/USDC on Solana. The current system includes placeholders for liquidity pool creation and liquidity addition, but deployment scripts must refuse live transactions while DEPLOY_LIVE=false.
- Confirm token metadata and hosted logo URI.
- Confirm authority policy and multisig vaults.
- Confirm legal/security approval.
- Confirm liquidity amount and venue.
- Seed liquidity only after final go/no-go signoff.
10. Security policy
Mint authority
Mint authority should be held only by multisig before launch. No personal wallet custody. Before public trading, Bag Guy must decide whether to revoke mint authority or permanently lock it under multisig policy.
Freeze authority
Freeze authority should be held only by multisig temporarily and never by a personal wallet. Recommended final path: revoke freeze authority after launch verification unless legal or security review requires temporary retention.
Multisig requirements
- Minimum 2-of-3 signers.
- Signers documented.
- Recovery plan documented.
- No private keys stored in app/backend/website repos.
11. Compliance posture
- No “yield,” “APY,” “profit,” or “rebase” product language.
- No guaranteed redemption or guaranteed earnings claims.
- Rewards are based on usage and eligible shopping activity.
- Provider terms, coupon terms, image rights, rate limits, and attribution rules must be respected.
- Apple/Google shopper listings should avoid crypto language and describe Bag Points, Store Credit, savings, rewards, membership, scan code, and meal planning.
12. Roadmap and launch checklist
- Complete legal review.
- Complete security review.
- Finalize signer custody plan and Squads multisig addresses.
- Finalize token logo and hosted metadata URI.
- Verify
DEPLOY_LIVE=falseuntil final approval. - Run pre-deployment validation: supply, decimals, allocations, metadata, no banned language, no live transaction functions enabled.
- Approve liquidity plan.
- Deploy SPL token only after human go/no-go.
- Verify token metadata, authority status, wallet balances, and explorer records.
- Publish final transparency notes on the web-only crypto page.