Suppose an Agent is participating in an auction. If it reveals its bid in advance, its competitors could adjust their offers accordingly. This is a hypothetical scenario, but it illustrates the value of @Nillion ’s core product, Covenants.
According to its official design, Covenants encrypts and seals instructions, decrypting them only after specified conditions are met. Its first version, Dusk, focuses on Ethereum L1, and its roadmap also lists an SDK for Agent applications. For developers, it’s worth exploring whether Agents can submit instructions while retaining necessary privacy, without having to handle the cryptographic details from scratch.
But this shouldn’t be taken to mean that “an Agent’s entire strategy is hidden.” Keeping instructions confidential and keeping trigger conditions confidential are capabilities at different levels.
My follow-up questions about $NIL are very specific: Will any developers turn this mechanism into a usable Agent application, and will the cost of making actual calls be acceptable? Only after a demo works does it face the test of sustained use.
@Nillion $NIL #NIL
According to its official design, Covenants encrypts and seals instructions, decrypting them only after specified conditions are met. Its first version, Dusk, focuses on Ethereum L1, and its roadmap also lists an SDK for Agent applications. For developers, it’s worth exploring whether Agents can submit instructions while retaining necessary privacy, without having to handle the cryptographic details from scratch.
But this shouldn’t be taken to mean that “an Agent’s entire strategy is hidden.” Keeping instructions confidential and keeping trigger conditions confidential are capabilities at different levels.
My follow-up questions about $NIL are very specific: Will any developers turn this mechanism into a usable Agent application, and will the cost of making actual calls be acceptable? Only after a demo works does it face the test of sustained use.
@Nillion $NIL #NIL
