1. All Agents must be built using Warden Agent Kit highlighting the use of Warden native capabilities like Keychain, Spaces, and Rules. (Please see warden documentation for further reading.) 2. On-chain activities must be demonstrated by deploying contracts over the Warden chain. 3. Agents must have a sense of purpose. Brownie points for something that is fun or has the potential to become viral, however only ‘fun’ will not be considered. 4. All code must be open-sourced and clear to read with relevant comments. 5. The project should be added to the Warden Agent example repo. (https://github.com/warden-protocol/agent-kit-examples) 6. Participants are expected to attend mandatory check-in with the Warden team on 4th February and 11th February. No exceptions!
1. All Agents must be built using Warden Agent Kit highlighting the use of Warden native capabilities like Keychain, Spaces, and Rules. (Please see warden documentation for further reading.) 2. On-chain activities must be demonstrated by deploying contracts over the Warden chain. 3. Agents must have a sense of purpose. Brownie points for something that is fun or has the potential to become viral, however only ‘fun’ will not be considered. 4. All code must be open-sourced and clear to read with relevant comments. 5. The project should be added to the Warden Agent example repo. (https://github.com/warden-protocol/agent-kit-examples) 6. Participants are expected to attend mandatory check-in with the Warden team on 4th February and 11th February. No exceptions!
1. All Agents must be built using Warden Agent Kit highlighting the use of Warden native capabilities like Keychain, Spaces, and Rules. (Please see warden documentation for further reading.) 2. On-chain activities must be demonstrated by deploying contracts over the Warden chain. 3. Agents must have a sense of purpose. Brownie points for something that is fun or has the potential to become viral, however only ‘fun’ will not be considered. 4. All code must be open-sourced and clear to read with relevant comments. 5. The project should be added to the Warden Agent example repo. (https://github.com/warden-protocol/agent-kit-examples) 6. Participants are expected to attend mandatory check-in with the Warden team on 4th February and 11th February. No exceptions!