Sumbissions
Trovebook is your private, onchain registry of zero-knowledge proofs, used to verify past actions, credentials, and assets without ever revealing the underlying data.
Every TRIS ID has its own Trovebook.
It enables users to anchor zk-hashed claims to their identity and build trust over time while maintaining full control over what gets revealed, when, and to whom.
How Submissions Work
Each entry in a Trovebook is:
ZK-hashed locally ensuring that no raw data is submitted to Tythe
Linked to a TRIS-bound wallet or smart agent identity
Tagged by DISC metric (e.g., Financial, Creative, etc.)
Typed by submission class (e.g., asset, credential, contribution)
Time-stamped
Scored only if approved
Wallet-Level Structure
Trovebook entries are organized by wallet address for provenance and accuracy:
Onchain proofs (e.g., DAO votes, LP positions, lending behavior) are recorded under the wallet that performed the action
Offchain claims (e.g., certificates, research papers, public records) are submitted under the wallet used to activate your TRIS
This structure ensures:
No cross-wallet score inflation
No recycled proofs across identities
Strong provenance per submission
Submission Categories
Each entry is double-tagged:
Metric Category:
Financial, Educational, Creative, Behavioral, Social, Security, Compliance
Submission Type:
Asset, Verifiable Credential (VC), Contribution, Achievement, Attestation
These tags define how a submission affects DISC Score (if validated) and how it appears in DISC Reports.
Wallet Address
Source address linked to TRIS (Individual or Agent)
Submission Type
Asset, VC, Contribution, etc.
Metric Category
One of seven DISC trust categories
Status
Approved / Pending / Rejected
Timestamp
Submission time (used for traceability)
Status Labels
Approved – Verified by a trusted third-party validator (affects DISC Score)
Pending – Under review, not yet counted toward DISC
Rejected – Failed validation; cannot be reused or resubmitted
Once submitted, Trovebook entries are immutable, deduplicated, and bound to a single TRIS ID; no identity can claim the same proof twice.
Privacy Control
Your Trovebook is private by default.
You control who sees what, when, and for what purpose
ZK-verification happens locally; Tythe only sees the hash
Even platforms requesting DISC Reports cannot see underlying data unless explicitly authorized
This architecture gives you granular trust disclosure, enough to qualify, never enough to expose.
Use Cases
Anchor proof of pre-launch contributions (for Pre-Protocol scoring)
Submit educational credentials, DAO activity, or certifications
Establish compliance records without identity exposure
Enable trust-based access to gated capital, governance, or reputation systems
Maintain a selectively disclosable credibility trail across multiple platforms
Read more about Trovebook as a Memory Repository →
“Let your yes be yes and your no be no, so that you may not fall under condemnation.”
— James 5:12
Last updated