The Sealed Registry

A national phone-number database on a real chain — that cannot leak.

Starting up…
The participants each may learn exactly what its role entitles it to — nothing more
First — what is this encryption? try it on two numbers

Normally, to compare two encrypted numbers you must decrypt them first. This encryption lets you do the maths while they stay encrypted. Pick two numbers and watch.

In this sandbox the oracle opens the whole answer so you can check the maths. In the registry below, it only ever opens what a role is allowed to ask.

Pick an operator to file a sealed record, or the regulator to ask a question. What you do — and what the chain lets you learn — appears here.
The chain + coprocessor everything they can see is on this side

They have

  • ✓ every sealed record, in real transactions
  • ✓ a 342 MB compute-only key

They do not have

  • ✗ any key that opens a record
  • ✗ any way to seal one either
The registry — public, anyone may read it

Every block is one sealed record in a real MERDEKA transaction. Click one to inspect it.

Access log — who asked what, forever
No access requested yet. The oracle has opened nothing.
Nothing received yet 
waiting for a sealed record…