01
Published math
The formula is public. Same events in, same score out. A collector, seller, or regulator can replay it without asking us for hidden weights.
PUBLIC REPUTATION LAYER
Trust you can verify, not just admire.
VaultStore trust is a certifiable score, not a private badge. Every signal ceiling, tier cutoff, and event type is published. Every profile links back to a replayable ledger.
The claim
Any client can re-run the score and land on the same number.
That is the whole product promise. Trust is derived from an append-only ledger of platform events, then materialized into a public score with no editorial thumb on the scale. If a badge says Gold, the evidence is right behind it.
Signals
8
KYC, age, volume, shipping, refunds, lock hygiene, ratings
Tiers
4
Warn-only tiers visible before every deal, trade, and listing
Ledger model
Append-only
No deletes, no silent rewrites, no hidden overrides
Business rule
No pay-to-win
Plans never buy trust. Only verified platform behavior changes the score.
02
Append-only ledger
Scores are derived from immutable events: KYC, completed transactions, shipping scans, refunds, disputes, trades, and peer ratings.
03
No editorial overrides
There is no concierge path to a better badge. We do not hand-wave users into higher tiers or quietly suppress bad events.
04
Gameable inputs are capped
Peer ratings now carry a full twenty points of the score, but only after enough counterparties rate you and the rest of the system still dampens spam-heavy behavior.
Signal map
The eight score inputs.
Identity verified
+20
Positive ceiling
Binary verification through Stripe Connect identity completion.
Account maturity
+10
Positive ceiling
Square-root dampened until one full year on VaultStore.
Completed transactions
+20
Positive ceiling
Log-dampened until roughly fifty completed transactions.
Transaction volume
+20
Positive ceiling
Log-dampened until roughly $25k lifetime gross volume.
On-time shipping
+15
Positive ceiling
Linear reward tied to first carrier scan timing.
Dispute / refund rate
-25
Penalty ceiling
Penalty based on dispute and refund share of completed transactions.
Trade lock hygiene
-5
Penalty ceiling
Penalty for post-lock trade edits after the counterparty believed the basket was frozen.
Peer ratings
+20
Positive ceiling
Counterparty-only ratings can contribute up to twenty points, but only after enough ratings exist to count and only alongside the rest of the ledger-based signals.
Tier ladder
What each tier actually means.
96Top Rated Seller
Top Rated Seller
Gold
Top Rated Seller. Vault-native operators with deep history, near-perfect shipping, and almost no negative trust signal.
Usually means KYC is complete, shipping stays on-time at scale, transaction count and volume are mature, and penalties are near-zero.
84Highly Rated Seller
Highly Rated Seller
Silver
Highly Rated Seller. Healthy transaction volume, stable shipping behavior, and enough verified history to transact confidently.
Usually means the seller has real volume, enough carrier scans to score shipping, and very few negative trust events dragging the total down.
58Trusted Seller
Trusted Seller
Bronze
Trusted Seller. KYC complete and a real track record — still building toward Silver, but already well past the warning line.
Usually means KYC is done and the account has crossed the first meaningful history threshold, but volume or shipping maturity is still building.
18Unverified
Unverified
Unverified
No completed identity verification or not enough history yet. Visible warning tier, not a silent block.
Usually means identity is still incomplete, history is thin, or the account has not yet produced enough events for the positive ceilings to matter.
Audit path
Verify any score yourself.
1. Pull the score
Read /api/trust/<userId> to get the current score, tier, and signal contribution map.
2. Pull the ledger
Read /api/trust/<userId>/events to fetch the append-only event history that fed the score.
3. Replay the math
Run computeTrustScore(userId, events) with the public event list and compare the returned score to the API.
Positive ceilings+105
Penalty ceilings-30
Published clamp0–100
score = clamp(round(sum(signal.earned)), 0, 100)computeTrustScore(userId, events)Live examples
See how real profiles resolve.