I spent some time going through Nillion’s documentation today, and one detail changed how I was thinking about Covenants.

At first, I assumed the main challenge was simply keeping an instruction private. Then I started wondering about execution itself. If nobody can read the instruction while it waits, why does Covenant not need a keeper, bot, or third party to watch the condition and execute it? That security model is what I want to understand better.

Dusk being live on Ethereum mainnet also makes this more concrete. Moving to production raises questions around reliability, incentives, and what happens when users depend on these encrypted instructions.

I’m also curious about Neon and private conditions. If the trigger itself can eventually remain confidential, could that protect more than the strategy being executed?

And if Dusk is only era one, I’m trying not to judge the whole system by what exists today. A future with richer conditions, multichain settlement, private conditions, and lower costs could look very different.

My interpretation may still be incomplete, especially around the exact execution and governance model.

For builders here, what technical problem do you think Nillion needs to solve next? And what would convince you that Covenants can become a genuinely decentralized privacy primitive?

#nil $NIL @Nillion