For platforms
I run a venue, a copy rail, a prop firm or a marketplace. Why require this?
Because disputes narrow to the committed data. Require a PROBATUM credential for premium listings, show the badge your users filter on, and settle contingent payments on the token.
IWhat to do
Three steps. No human at MIZAN in the loop.
Set a policy
POST /api/venues/policy: record days, trades, forward-only, fill provenance grade. Unknown ids refuse.
Gate listings
One script tag or one call per listing. Proven listings first; refusals are already public.
Subscribe
Revocations push to your webhook within a minute. Founding seats get fixed-fee pricing and first listing in the register.
IIWhere it lives
The live surfaces.
Live surface
Founding seats and the badge
Live surface
Policies on the check
Live surface
What is already proven
IIIHonest status
What is live, what is declared, what is a draft.
Venue policies, badges, embeds and revocation webhooks are live. The venue of our own comes later, by a separate entity.
Every profile carries its chip wherever it is named: LIVE DECLARED DRAFT ROADMAP