How Wedge computes credibility

Every fact you see in a Wedge widget is the aggregate of real conversion events across the founder network — anonymized at source, gated by quality thresholds, and cryptographically signed.

Where the data comes from

Founders who opt into the Credibility Graph attach a small tracking snippet to their product. When a Wedge-attributed visitor converts (signs up, starts a trial, becomes a paid customer), the event flows back to Wedge tagged with the page that drove it.

Aggregation

Every six hours we re-aggregate. For each competitor in the network, we compute a count of trial-or-paid conversions over a rolling 30-day window. We never compute per-founder facts; only network aggregates.

Quality gates

A fact is only published when at least 3 distinct founders contribute and at least 50 eventsaccumulate. Below those gates, widgets render nothing — fake or thin social proof would burn the network's reputation faster than missing data does.

Attestation

Every computation produces a signed payload: fact id, value, time window, sample size, contributing founder count, methodology version. Signed with Wedge's Ed25519 key. Public key at /.well-known/wedge-public-key.json. Anyone can verify any attestation independently.

What never leaves the database

Founder identity, email, product domain.
Customer email, IP, name. (We hash external_user_id at intake.)
Per-founder counts. Only the cohort-level aggregate.
Cross-founder identity until a mutual referral introduction is accepted.

Revocation

Founders can revoke consent at any time. Their FUTURE events stop contributing. Past attestations are signed snapshots — they remain valid; their contribution counts stay in the pool but are unattributable.

Try it

Paste a fact_key into /verify to see its attestation chain, or hit /api/v1/facts to list every published fact.