Identity
Exact network and identifier. The underlying reference stays separate from each representation.
VERIFICATION INFRASTRUCTURE FOR TOKENIZED ASSETS
Verify a tokenized asset before your application lists, routes, accepts or monitors it
JUJING connects exact onchain identifiers with instrument identity, documented rights, token controls, lifecycle changes and reproducible evidence.
Corporate Action Guard
Know when a tokenized asset changes
JUJING connects issuer lifecycle events to the exact onchain representation, then produces integration-ready data with provenance and deterministic evidence receipts.
For wallets, exchanges, DeFi protocols, market operators and tokenized-asset integration teams reviewing how material asset changes affect their systems.
- Exact contract or mint binding
- Normalized corporate-action and lifecycle events
- Issuer claim and onchain observation separation
- Operational guidance for affected integrations
- Evidence provenance and deterministic receipts
- Explicit stale, incomplete and NOT_ESTABLISHED states
Explore the historical working demonstration and live read-only APIs. Continuous production monitoring, active webhook delivery and an SLA are not currently provided.
Pilot inquiries: contact@jujingwhale.xyz
01 / Identity before equivalence
A ticker is not an identity
Same company.
Different instrument.
Two tokens can reference the same company while having different issuers, legal structures, holder rights, controls and eligibility. A symbol alone cannot tell your application what it is accepting.
See the comparison dimensions →02 / The evidence model
One record, four evidence layers
Evidence
Documented claims, retained observations, provenance and content digests.
Lifecycle
Attributed events and required actions, with time precision and unresolved relationships.
Exposure
Scoped observations and availability. Production exposure remains NOT_ESTABLISHED.
03 / Application decisions
Built for integration decisions
Wallets
Explain which representation a user holds, and which controls apply.
Distribution platforms
Check identity and evidence boundaries before including an asset.
Venues and aggregators
Keep exact instruments separate when evaluating routing and acceptance.
Risk and monitoring systems
Use retained lifecycle and exposure evidence as explicit inputs.
04 / Explicit result semantics
What JUJING returns
Evidence with its limits attached
An established identity can coexist with incomplete rights evidence. A matching receipt can be stale. Missing exposure is not zero exposure.
Read result semantics →PRESENT- Present in retained reviewed registry records; no safety or eligibility conclusion.
INCOMPLETE- Some required evidence remains unresolved, including OURA’s overall evidence.
NOT_ESTABLISHED- A fact or conclusion is not established; it is never replaced with an assumed value.
STALE / STALE_EVIDENCE- Freshness is separate from record integrity and completeness.
UNKNOWN_REPRESENTATION- No exact admitted identifier match. A shared ticker is not a fallback.
IDENTITY_MISMATCH- The API fails closed when exposure identity does not match the requested representation.
05 / Public working examples
Working evidence
Working evidence
NVDA wrapper comparison
One underlying reference, distinct representations.
Working evidence
PreStocks directory
Publisher identity and retained evidence, with scope.
Working evidence
SpaceX Passport
A documented transition and required-action deadline.
Working evidence
OURA Passport
Identity-only admission, contextual lifecycle evidence.
06 / A deliberate boundary
Designed to fail closed
Unknown stays unknown.
Missing evidence is not proof of absence. Shared tickers do not establish identity, equivalent rights or interchangeable instruments. Publisher statements remain attributed statements.
JUJING is independent verification infrastructure for tokenized assets. It supports application decisions; it does not make a legal, reserve, eligibility, safety or investment approval.
Evidence before action
Use JUJING as a verification input
Inspect exact identifiers. Preserve provenance. Handle unresolved states explicitly.
Explore the developer API →