DJZS Protocol
DJZS Protocol's Team
Problem Statement
Autonomous agents move money, make trades, and sign commitments on behalf of humans, but there is no verification layer between the agent reasoning and execution. Trust is the default. During this hackathon, agents were prompt-injected through public channels, credentials were compromised, and identities were hijacked. A single hallucinated data point, a FOMO-driven allocation, or a fabricated risk assessment can drain a treasury before anyone reviews the logic. The infrastructure underneath the agent determines whether humans can trust how it operates.
DJZS Protocol is an adversarial audit oracle that intercepts agent reasoning before execution. It applies an 11-code failure taxonomy (the DJZS Logic Firewall), writes trust scores on-chain via DJZSLogicTrustScore on Base Mainnet, mints immutable Proof-of-Logic certificates to Irys Datachain, and gates capital deployment through DJZSEscrowLock. If the agent fails audit, capital stays locked. If it passes, escrow releases. The human can verify every step on-chain. Two integration channels serve different threat models: the Dark Channel (XMTP MLS encrypted) for proprietary strategies with zero public trace, and the Light Channel (x402 REST API) for DAO treasury audits with permanent Irys provenance. Both enforce the same Audit-Before-Act kill switch. Four verified smart contracts on Base Mainnet: DJZSLogicTrustScore (0xB3324D07A8713b354435FF0e2A982A504e81b137), DJZSStaking (0xA362947D23D52C05a431E378F30C8A962De91e8A), DJZSEscrowLock (0xB041760147a60F63Ca701da9e431412bCc25Cfb7), DJZSAgentRegistry (0xe40d5669Ce8e06A91188B82Ce7292175E2013E41). Trust is not the default. Proof is.
Build Timeline
Team
DJZS Protocol
admin
MandateIncrease your chances to win
- ›Most agents in the hackathon are exposed to prompt injection
- ›This might cause overspending and loss of funds
- ›Security is a crucial part of the hackathon
Share on X
Tell the world about this project
Tracks
Intention
Plans to continue
DJZS Protocol existed before this hackathon and will continue development after. The hackathon provided the context to deploy on-chain contracts, wire the end-to-end integration pipeline, and demonstrate the protocol against real competition themes. Full disclosure of pre-existing vs hackathon work available in DISCLOSURE.md.