I assumed the chain itself decides when a sealed instruction opens

@Nillion Covenants don't work that way. An instruction is sealed to a committee of nodes and published on Ethereum together with its release condition.
Nillion's developer docs say the nodes evaluate that condition off chain, against their own price feed, and once enough of them judge it met, the instruction opens

That changed how I read Dusk, the first release of Covenants on Ethereum. The design is built so no keeper has to act and no single party decides whether the instruction opens

What it gives up, per the docs, is the chain adjudicating the condition itself. Nillion presents that as a deliberate trade-off: for most application shapes, it says, that part was never the interesting one

I don't see that as a flaw. It's a clear choice about where trust sits. It just means the sealing protects who can read the instruction and when, while the condition itself is evaluated by the nodes

If nodes evaluate the condition, what should someone sealing an instruction check first: the cryptography that keeps it sealed, or the independence of the nodes that decide when it opens?

#nil $NIL @Nillion