Key Syncing
Key Syncing enables automated synchronization of encryption keys between CRYMBO Oracle and partner platforms — ensuring that as wallets are created or updated on the partner side, the Oracle network stays current.
How Key Syncing Works
- Partner registers with CRYMBO Oracle as an integration partner
- Webhook configured — Partner's system sends key updates to CRYMBO via secure webhook
- Automatic publication — New or rotated keys are published to the Oracle network in real-time
- Validation — Oracle verifies key integrity and associates it with the correct institution
Sync Events
| Event | Trigger |
|---|---|
key.created | New encryption key generated by partner |
key.rotated | Existing key replaced with new key |
key.revoked | Key marked as revoked (compromised or expired) |
wallet.created | New wallet registered — requires key association |
Security Requirements
- All key sync communications must use TLS 1.3
- Webhook endpoints must be authenticated via HMAC signatures
- Private keys are never transmitted — only public keys are synced
- Key revocation is immediate and irreversible