Skip to main content

Proof-of-Validation Mechanism

The Proof-of-Validation (PoV) system is CRYMBO Oracle’s trust framework. It ensures that all validation decisions—whether for transaction requests or KYC payloads—are cryptographically signed and consensus-driven.

Purpose​

  • Enforce trust-minimized validation
  • Provide cryptographic evidence of compliance
  • Enable decentralized validator quorums
  • Establish an audit trail for regulatory review

Core Components​

1. Validator Signature​

Each validator submits a signed proof payload:

{
	"validator": "0xValidatorAddress",
	"txHash": "0x...",
	"status": "approved",
	"timestamp": 1713600000,
	"signature": "0xSignature"
}

2. Quorum Threshold​

Validation decisions require a minimum number of unique, eligible validators:

  • Default quorum: 3 of N
  • Weighted by validator reputation
  • Dynamic quorum sizes based on network scale

3. Aggregation Engine​

CRYMBO Oracle collects and verifies all proofs:

  • Confirms signatures and validator eligibility
  • Applies quorum logic
  • Emits final result to the chain or off-chain relay

4. Finalization​

Once quorum is reached:

  • Validation is logged as successful or failed
  • Validator scores are updated
  • Trigger for next identity flow step (e.g. delivery or rejection)

Security Model​

  • ECDSA or BLS signatures for validator proof
  • Nonce + timestamp included to prevent replay
  • Validators penalized for conflicting or missing responses

📌 Next Step: Learn how validators are Rewarded & Scored