Skip to main content
ROOTKey processes and anchors data through a set of formally defined protocols. Each protocol defines how data is anchored (on-chain vs. off-chain vs. hybrid) and where it is processed (sovereignty tier). These two dimensions together determine the auditability, throughput, cost, and regulatory fit of an integration.

​
Protocol Naming - RKP

All ROOTKey protocols follow a standardised naming convention:
RKP-N - base protocol · RKP-N Enhanced EU - EU cloud sovereignty · RKP-N Sovereign EU - full EU sovereignty
ProtocolArchitectureSovereignty
RKP-1Full On-ChainStandard (Azure/AWS + Polygon)
RKP-1 Enhanced EUFull On-ChainPartial EU (OVH + Polygon)
RKP-1 Sovereign EUFull On-ChainFull EU (OVH + EBSI)
RKP-2Off-ChainStandard (Azure/AWS)
RKP-2 Enhanced EUOff-ChainFull EU cloud (OVH)
RKP-2 Sovereign EUOff-ChainFull EU - on-premise / air-gap
RKP-3HybridStandard (Azure/AWS + Polygon)
RKP-3 Enhanced EUHybridPartial EU (OVH + Polygon)
RKP-3 Sovereign EUHybridFull EU (OVH + EBSI)

​
Architecture Comparison

CapabilityRKP-1RKP-2RKP-3
On-chain recordFullNoneSelective
Blockchain usedPolygon / EBSINonePolygon / EBSI
Third-party verifiabilityIndependent (Polygonscan / EBSI)Hash-basedDual-path
ThroughputLowerHighestBalanced
Cost per operationHigherLowestModerate
GDPR erasure compatibilityYes (off-chain data only)YesYes
Best forLegal / regulatory critical recordsIoT / high-frequencyEnterprise mixed workloads

​
Sovereignty Comparison

Sovereignty levelCloudBlockchainProtocols
None (Standard)Azure / AWSPolygonRKP-1, RKP-2, RKP-3
Partial EUOVHPolygonRKP-1 Enhanced EU, RKP-3 Enhanced EU
Full EU (cloud)OVHNoneRKP-2 Enhanced EU
Full EUOVHEBSIRKP-1 Sovereign EU, RKP-3 Sovereign EU
Full EU - air-gapOn-premiseEBSI (optional)RKP-2 Sovereign EU
→ See Data Sovereignty for infrastructure details and regulatory context.

​
Decision Guide

Your requirementRecommended protocol
Maximum on-chain auditability, no sovereignty requirementRKP-1
Maximum on-chain auditability, EU cloud requiredRKP-1 Enhanced EU
Full EU sovereignty on every layerRKP-1 Sovereign EU or RKP-3 Sovereign EU
High-volume IoT / sensor data, no sovereignty requirementRKP-2
High-volume IoT / sensor data, EU cloud requiredRKP-2 Enhanced EU
High-volume data, on-premise / air-gappedRKP-2 Sovereign EU
Mixed workloads (bulk + critical events), no sovereignty requirementRKP-3
Mixed workloads, EU cloud requiredRKP-3 Enhanced EU
Mixed workloads, full EU sovereigntyRKP-3 Sovereign EU
GDPR data requiring potential erasureAny RKP-2 or RKP-3 variant
EUDIW / EU Digital Identity WalletAny Sovereign EU variant

Not sure which protocol fits your architecture?

Our engineering team is available for technical briefings. We’ll assess your data classification, throughput requirements, sovereignty obligations, and regulatory framework - and recommend the right protocol configuration.