ITEERegistry holds five things for every TEE node: the attestation document, a signing key. A TLS certificate, a payment address. And endpoint.
A node submits those five fields, and from that point any validator on OpenGradient's network can pull them and check them independently.
Nobody has to ask permission to verify. Nobody can quietly slip a node into the registry. Without the submission sitting there for everyone to see at once.
No admin in the loop. No approval queue.
Just five fields, public the moment they land.
I counted those five fields twice before I trusted the count. Mostly because the gap looked too clean to be an accident.
They cover everything a node submits to get listed on OpenGradient. None of them cover what happens after.
A registry that records what a node claims isn't the same thing as a registry that confirms what a node does. Not once it's in. That's the actual point where the privacy-policy comparison stops working. The claiming part exists on OpenGradient.
The confirming part doesn't — not here, not anywhere running this kind of setup.
There's still a check happening on OpenGradient's end, just a much smaller one than the comparison makes it sound.
It runs once — the moment a node hands over those five fields, nothing after. The key can sit untouched for years.
The enclave code under it can get patched a dozen times, with no link back to that first entry.
Whether the registry still means anything by then isn't something its design was built to answer.
$OPG #OPG @OpenGradient
A node submits those five fields, and from that point any validator on OpenGradient's network can pull them and check them independently.
Nobody has to ask permission to verify. Nobody can quietly slip a node into the registry. Without the submission sitting there for everyone to see at once.
No admin in the loop. No approval queue.
Just five fields, public the moment they land.
I counted those five fields twice before I trusted the count. Mostly because the gap looked too clean to be an accident.
They cover everything a node submits to get listed on OpenGradient. None of them cover what happens after.
A registry that records what a node claims isn't the same thing as a registry that confirms what a node does. Not once it's in. That's the actual point where the privacy-policy comparison stops working. The claiming part exists on OpenGradient.
The confirming part doesn't — not here, not anywhere running this kind of setup.
There's still a check happening on OpenGradient's end, just a much smaller one than the comparison makes it sound.
It runs once — the moment a node hands over those five fields, nothing after. The key can sit untouched for years.
The enclave code under it can get patched a dozen times, with no link back to that first entry.
Whether the registry still means anything by then isn't something its design was built to answer.
$OPG #OPG @OpenGradient