This is a sovereignty variant of RKP-1 (Full On-Chain). The anchoring mechanics are identical - the difference is the cloud infrastructure used for off-chain processing and storage.
Sovereignty Profile
When to choose this variant: Your regulatory environment requires EU cloud data residency (GDPR, national cloud policies) but does not specifically mandate that the blockchain infrastructure itself be EU-operated or under EU jurisdiction.
How It Differs from RKP-1 Standard
Anchoring Architecture
The only component outside EU legal jurisdiction is the Polygon blockchain itself - which is a permissionless, distributed network operated by no single entity and subject to no single national law.Regulatory Frameworks Addressed
Configuration
RKP-1 Enhanced EU is available as a configuration option on your ROOTKey workspace. No changes to your API integration are required - the anchoring API endpoints and request format are identical to RKP-1 Standard. Contact our team to configure your workspace for OVH-backed processing. → Request EU cloud configurationWhen to Use RKP-1 Sovereign EU Instead
If your regulatory environment requires that the blockchain record itself be under EU legal jurisdiction - not only the cloud infrastructure - use RKP-1 Sovereign EU (EBSI + OVH) instead. RKP-1 Sovereign EU is appropriate for:- National critical infrastructure operators with sovereignty requirements on the anchoring layer
- Organisations subject to classification requirements that prohibit reliance on non-EU networks for integrity proofs
- Public sector organisations or those processing data at EU-classified levels