Skip to main content

Validator Roles Overview

CRYMBO Oracle relies on decentralized validators to secure, verify, and score compliance actions on-chain. Validators are the execution and enforcement layer of the Oracle — they ensure that identity exchange requests are legitimate, data integrity is maintained, and compliance standards are upheld.

Validators are professional infrastructure operators, not anonymous yield farmers. They are economically incentivized for uptime and correctness; malicious or unreliable behavior is penalized.

There are two main types of validators:

  • Transaction Validators — Validate the on-chain request and execution integrity
  • KYC Validators — Confirm the authenticity and regulatory alignment of identity data

Why Validators Matter​

Validators are core to CRYMBO's decentralized trust model. They:

  • Prevent malicious or unverified data exchanges
  • Provide redundancy and decentralization to the compliance process
  • Ensure compliance outcomes are deterministic and economically enforced
  • Enable the Oracle to operate without centralized trust assumptions

Validator Incentives​

Each successful validation results in:

  • A reward payout in $RMBO tokens (base reward per epoch + variable reward per validated transaction)
  • An update to the validator's reputation score
  • Optional quality multiplier based on uptime, latency, and dispute score

Reputation scores impact future eligibility, weight in quorum voting, and long-term credibility in the network.

Validator Eligibility (Phase 1)​

In Phase 1, validators may include:

  • Banks and financial institutions
  • Infrastructure providers
  • Regulated entities with compliance expertise

Banks can become validators — this anchors Oracle trust in the same institutions that require its services.

Participation Requirements​

To participate as a validator, entities must:

  • Complete a Validator KYB process (verified institutional identity)
  • Stake $RMBO tokens (minimum stake amount, maintained continuously while active)
  • Host validation infrastructure (off-chain worker node + wallet access)
  • Meet protocol-defined uptime and performance thresholds

Lifecycle of a Validation​

  1. Oracle emits a validation event (transaction requires compliance check)
  2. Eligible validators are notified based on stake weight and availability
  3. Validators fetch and verify the encrypted compliance payload
  4. Validations are cryptographically signed and returned
  5. Oracle aggregates results, reaches consensus, and publishes attestation
  6. Fees distributed to participating validators; slashing applied for misbehavior

📌 Next: Transaction Validation →