Loading price
FourteenControllerPublic earn snapshot

A growth route built for real buyer capture, visible reward flow, and a cabinet that can scale with the network.

The wallet route begins with ambassador identity and grows into a cabinet with tracked buyers, verified purchases, reward progression, and controlled withdrawals. The website keeps that story public without pretending to be the cabinet itself.

Total Ambassadors

6

6 active on-chain right now.

Rewards Claimed

1.28

TRX already withdrawn by ambassadors.

Verified Purchases

11

Purchases already processed into the earn flow.

Bound Buyers

4

Buyer identities currently tied to ambassadors.

System Counts

Who is already inside the ambassador footprint

Total Ambassadors6
Active Ambassadors6
Bound Buyers4
Profiles On Chain6
Profiles Marked Active6
Ambassadors With Purchases3

This combines public controller totals with cabinet-side profile and purchase footprint from the wallet backend. That keeps the website useful without pretending to be the working cabinet.

Reward Ledger

What the controller shows about reward motion

Tracked Volume258 TRX
Rewards Accrued1.81 TRX
Rewards Claimed1.28 TRX
Reserved Rewards0.53 TRX
Owner Available16.25 TRX
Unallocated Purchase Funds8.96 TRX

Why this matters: claimed rewards show what ambassadors have already withdrawn, reserved rewards show what is still ring-fenced for them, and tracked volume shows how much verified purchase flow has already passed through the controller.

Purchase Footprint

What the growth pipeline has already processed

Recorded Purchases

12

Purchases tied to ambassadors across processed and pending rows.

Pending Replay

1

Rows still waiting for controller-side processing or operator readiness.

Withdrawal Events

2

Confirmed reward withdrawal rows already written by the backend.

Last Purchase Seen

Apr 3, 2026, 12:50:06 PM UTC

Latest ambassador-attributed purchase timestamp.

Purchases and withdrawals are counted from the same backend ledger the wallet cabinet already uses. That gives the website a clean public proof layer without needing wallet connection.

Runtime Readiness

Can the operator side process reward rows now

Operator WalletTN95o1...LH6TCT
Ready NowNeeds top-up
Energy Available0
Bandwidth Available883
Need per Allocation120000 energy / 500 bandwidth
Safe Floor After Run100 energy / 10 bandwidth

This is the public version of the same idea the wallet uses: if resources are not safe, reward rows queue instead of pretending everything completed.

Level Ladder

Buyer growth changes the reward share

0-9 buyers

Bronze

10% reward share on qualified flow.

10-99 buyers

Silver

25% reward share on qualified flow.

100-999 buyers

Gold

50% reward share on qualified flow.

1000+ buyers

Platinum

75% reward share on qualified flow.

Earn Flow

How the product moves from identity to withdrawal

Register

Identity first

The wallet route begins with ambassador registration, slug ownership, and cabinet identity. The public website does not fake this step as a generic referral form.

Bind

Buyer attribution

Purchases are not counted from loose traffic guesses. A buyer is bound, the purchase is verified, and only then the controller tracks reward state.

Accrue

Reward reservation

The controller separates accrued rewards, claimed rewards, owner balance, and reserved rewards, so the cabinet can explain what belongs to ambassadors and what is still waiting.

Withdraw

Claimable cabinet

The same route later becomes the cabinet: purchases, level progress, pending replay, and withdrawable reward balance live in one place.