Manual Contents

This is the “how it actually works” page. Home stays tight. This page stays complete.

1) What 7TRB Is

7TRB isn’t “get rich.” It’s a circulation system. The goal is to keep value moving inside a network of people and businesses: members → merchants → builders → community projects → back to members.

What makes 7TRB different?

Most tokens chase price. 7TRB chases utility + proof: a public treasury, receipts, merchant acceptance, and funded work you can verify.

What must be true for 7TRB to grow?
  • Many holders (wide distribution).
  • Real use (merchant network + projects).
  • Transparent treasury (reports + receipts).
  • Rules (so people trust the system).

2) Wallets (Personal + Tribe)

Personal wallet (member)

Your personal wallet is where you hold and spend your 7TRB. Treat it like a debit card + vault. Seed phrase = master key. Never screenshot it. Never share it.

Tribe Treasury wallet (community funds)

The tribe treasury is not “one person’s wallet.” It is a shared asset governed by rules. Best practice is multi-sig (requires multiple approvals) or a treasury contract once ready.

  • Small tribes: multi-sig + monthly reporting.
  • Growing tribes: treasury contract + on-chain proposals/votes.
Safety rules
  • No one “from support” will ever need your seed phrase.
  • Test small transfers first.
  • Only use contract/explorer links from your official site.

3) Start a Tribe (Step-by-Step)

A tribe is a small economic unit with rules. Without rules, it becomes drama. This is the minimum viable structure.

Step 1 — Gather the core (5–20 people)

Start with disciplined people, not hype people. You want folks who show up, vote, and contribute. Create a group chat (WhatsApp/Telegram) and set a weekly or bi-weekly meeting rhythm.

Step 2 — Choose a mission + territory

Pick one sentence that explains why this tribe exists (example: “Build a local merchant loop in Detroit”). Territory can be a neighborhood, city, church network, or online community.

Step 3 — Assign roles (non-negotiable)
  • Coordinator: runs meetings + communication.
  • Treasurer: manages treasury process (not “owns” it).
  • Recorder: logs votes, decisions, and publishes updates.
Step 4 — Write the rules (simple, enforceable)
  • Membership dues (amount + due date + late policy).
  • Voting method (simple majority, quorum required, etc.).
  • What counts as a tribe project.
  • Conflict policy (warnings → suspension → removal).
  • Exit policy (how members leave, what happens to dues).

4) Treasury (Trust is Built Here)

The treasury is the engine. If treasury is sloppy, the whole project looks like a hustle. This is how you run it clean.

Treasury basics
  • Purpose-bound: treasury money has categories (operations, merchant support, builder grants, emergency).
  • Reporting cadence: weekly mini-update + monthly full report.
  • Receipts: no receipt = no reimbursement.
How spending gets approved

Use a simple pipeline: Proposal → Discussion → Vote → Fund → Deliver → Report. Start small. Force proof. Grow trust.

USD vs 7TRB in the treasury

Early on, tribes usually keep a mix: some stable value (USD/stable) for predictable expenses, and 7TRB for internal incentives, rewards, and merchant circulation.

5) Builders (Work → Proof → Payment)

Builders are how the ecosystem becomes real. No builders = no products, no tools, no growth.

How a builder gets funded
  1. Submit a proposal (scope + budget + timeline).
  2. Tribe discusses (what’s the ROI to the community?).
  3. Vote approval (and set deliverables).
  4. Fund in milestones (not all at once).
  5. Deliver + report. Receipt culture only.
Pay structure (practical)

Use milestone payments: 30% start, 40% mid, 30% completion — or whatever fits. The rule is: payment follows verified progress.

6) Merchants (Where Circulation Becomes Real)

Merchant onboarding (simple)
  1. Create a merchant wallet (separate from personal wallet).
  2. Agree to acceptance rules (partial payments allowed, refund policy, redemption policy).
  3. Get listed in the merchant directory (name, city, category, contact).
  4. Display “7TRB Accepted” signage (online + in-store).
How payments work (cash + card + 7TRB)

Keep it realistic: customers can pay in cash/card like normal, and use 7TRB as a partial payment or loyalty layer. The goal is not to force 100% crypto transactions — the goal is to create repeat circulation.

  • Option A: “Up to 20% of bill in 7TRB.”
  • Option B: “Pay full in USD, earn 7TRB rewards.”
  • Option C: “Tribe discount if you pay a portion in 7TRB.”

7) Merchant Redemption (Cash-Out Rules)

Merchants need a clear exit, or they won’t accept it. Redemption must be rule-based so it doesn’t drain the system.

Three sane redemption models
  • Model 1 (Best early): Partial redemption with limits (weekly cap).
  • Model 2: Discounted redemption (merchant gets 90% USD value) to protect treasury.
  • Model 3: Swap + liquidity route (DEX) when liquidity is strong.
Why limits matter

If merchants can instantly dump unlimited 7TRB for USD, you create a bank-run machine. Limits protect the treasury and push merchants to also recirculate (pay suppliers, buy services, sponsor builders).

8) Dashboard Metrics (What to Track)

The KPIs that actually matter
  • Holders: distribution strength.
  • Active wallets (30d): real movement.
  • Treasury balance: runway + stability.
  • Spent % (30d): circulation speed.
  • Project pipeline: proposed → approved → funded → delivered.
  • Merchant volume: adoption strength.
Rule of thumb

Price is loud. Usage is real. Build usage first and the value has something to stand on.

Want the basics page? Go to Learn (Crypto 101).