Traction

Public usage evidence and product proof, not growth hype.

Investor diligence gets easier when the site shows what is actually moving. These numbers come from the public settlement snapshot and the spendability catalog, not from anonymous claims.

Return Home Trust evidence Pricing Demo Customer stories
Snapshot2026-06-01 public data
Payments fulfilled346
Bridge-backed reserve155.010315 ETH
Open liability9454.337 ETH

Snapshot metrics

What the public snapshot shows right now.

Total supply

9,999,999,999,899,760

Liquid supply

2,499,999,999,974,940

Locked supply

7,499,999,999,924,820

Fulfilled payments

346

Merchant count

4

Utility items

11

Entitlement groups

9

Layer6 reserve inventory

56,926.66 ETH

What traction means here

The product is credible when the user path and the proof path are both visible.

Problem solved

AI launches usually hide pricing, owner responsibility, and proof. This stack exposes them.

Who it is for

Founders, operators, and buyers who need trust, route control, and a public evidence trail.

Why it is different

Evidence-first pages, public status labels, and explicit disclosure states replace vague claims.

How it works

Open the demo, review the trust hub, then move into the CAPPS-gated product lanes.

Case evidence

Use cases are public; named customer stories are not yet published.

Route-heavy operator flow

Public users can see how wallet connect, CAPPS registration, and Capsule review gate access to protected actions.

Pricing transparency flow

Clear pricing pages show what the product costs instead of hiding the number behind a sales call.

Evidence-first launch flow

Security, trust, and launch-readiness pages are explicit about what is verified and what is still pending.

If a named customer case study is published later, it should include the problem, workflow, measurable result, and approval date on the public page. Until then, this page should not pretend the customer evidence exists.