AEGIS — Grant Application
> - Contact email: olaoyesalemgreat@gmail.com
> - GitHub/owner handle: olaoyesalem
> - Wallet address: 0xD3DfB1f144F548dE4e32166B9E5214691343D4F1
> - Proposed grant amount: USD 75,000
1. Applicant & Project Overview
Project Name
AEGIS — Adaptive Immune Firewall
Team / Individual Names
- Olaoye Salem (primary developer / maintainer)
(Repository owner: `olaoyesalem`)
- Morakinyo Damilare
Links
- X account: https://x.com/aegis_protocol2
100 Word Summary
AEGIS is an Adaptive Immune Firewall for decentralized finance: a set of Solidity smart contracts, Off-chain agents, and an SDK that detect, score, and mitigate on‑chain threats using stakeholder challenges, automated agents, and a registry of trusted actors. Built with Hardhat, the system includes developer tooling, frontend components, and a knowledge-graph style registry for risk signals and attestations. AEGIS enables protocols to surface suspicious activity, allow community challenge/verification, and apply configurable mitigations to reduce risk while preserving decentralization.
Project Category
Security / Risk mitigation / Developer tooling (Smart contracts + SDK + Frontend)
Agent / Registry
Includes an on‑chain registry for agents and triples (used to represent threats, attestations, and signals). Agent processes (antibody-agents) are provided as part of the SDK.
InfoFi / Knowledge Graph
AEGIS models facts and risk signals as triples/atoms suitable for integration into an InfoFi/knowledge-graph layer; those triples are used to record attestations, threat links, and resolution status.
Developer Tooling
- Hardhat-based contracts and tests (TypeScript scripts under `scripts/`).
- SDK (TypeScript) in `AEGIS/sdk` with examples.
- Frontend components for integration (in `frontend/`).
- CI/testable contract artifacts and Typechain types provided.
Identity / DID / Reputation
AEGIS provides an agent/registry pattern for on‑chain identities and reputations (attestation/triple records), enabling reputation weighted challenge mechanics.
AI Context / MCP
AEGIS can be extended with AI risk scorers and MCP-style agents that consume the knowledge graph (triples/signals) to surface, score and recommend actions for threats.
Consumer App
A frontend exposing threat registration, monitoring, and challenge workflows for protocol operators and stakeholders.
Others
Includes scripts for deployment, monitoring, and demo flows (e.g., `scripts/` contains registration, challenge, and agent helpers).
Elevator pitch
AEGIS is a composable on chain firewall that detects and mitigates DeFi threats by combining token weighted challenges, attestations, and automated agent responses , enabling protocols to respond to suspicious activity quickly while preserving decentralization.
Origin story
Developed to address recurring on-chain exploitation patterns, AEGIS combines research into decentralized governance and automated monitoring to give protocols a structured, auditable way to flag and remediate risk.
Notable traction or achievements
- Contains comprehensive Hardhat tests and a working SDK and frontend.
- Developer tooling and examples included for integration and testing.
Current users or early testers
- Internal tests and local deployments. Seeking protocol pilots for on chain trials.
2. What You’re Building
Problem Statement
DeFi protocols lack standardized, composable mechanisms to detect, score, and coordinate mitigation of on‑chain threats in an auditable and trust minimized way. Current responses are ad-hoc and often centralized.
Proposed Solution
AEGIS provides:
- Smart contracts to register threats, record attestations (triples), and manage challenge windows.
- A registry of agents and triples that function as the system knowledge graph.
- Off-chain agents (antibody-agents) and an SDK to automate monitoring, risk scoring, and challenge actions.
- Frontend tooling to allow stakeholders to view and act on threats.
Together these components enable community-challenges, reputation-weighted attestations, and automated mitigations.
Stage of Development
MVP — contracts, SDK, tests, and a frontend are present. Ready for pilot integrations and security review.
Technical architecture overview
- On-chain: Solidity contracts (AdaptiveImmuneFirewall and support contracts) deployed via Hardhat.
- Off-chain: TypeScript SDK + agent processes that interact with the chain and knowledge graph.
- Frontend: React/Next app components that interact with the SDK.
- Data model: Triples/atoms represent facts (threats, attestations, resolutions). Signals and registry entries store metadata and reputations.
Integrations or dependencies
- Hardhat, TypeChain, OpenZeppelin contracts.
- Potential integration targets: MCP/InfoFi graph for knowledge storage and query, DID/agent registry primitives, and token-based reputation staking interfaces.
Security considerations
- On-chain challenge windows and dispute mechanics to avoid false positives.
- Role-based and reputation-weighted actions minimize single-point-of-failure remediation.
- Recommend third-party audits and staged mainnet rollouts.
- Time-locked mitigations and multisig/admin fallbacks for emergency response.
3. Team & Execution Ability
Team backgrounds
- Olaoye Salem — core developer and maintainer. Experience building Solidity contracts, TypeScript SDKs, and web frontends (project structure demonstrates Hardhat + SDK + frontend).
-Morakinyo Damilare — Co founder
Execution proof
- Repository contains smart contracts, tests (`test/ImmuneFirewall.test.ts`), deployment and management scripts, and an SDK with example usage (e.g., `AEGIS/sdk/examples`), showing shipped developer tooling and runnable code.
Commitment level
- Core maintainer: full-time on project development (adjustable — please confirm exact availability).
Team structure and roles
- Lead developer / architect — contract and SDK design.
- Frontend engineer — UI and UX flows.
- Security reviewer / auditor — external (to be contracted).
- Ops/DevRel — integrations and sample deployments.
Advisors / collaborators
- To be announced; will seek security and protocol governance advisors as part of grant funding.
Expected future hiring
- Full-time security engineer; part-time frontend dev; community manager for integrations.
Prior crypto / AI experience
- Project demonstrates Solidity, Hardhat, and agent patterns; integrates with AI risk-scorer components in the SDK for extensibility.
4. Grant Request & Milestones
> Proposed (adjustable) total request: USD 75,000
Budget breakdown by milestone
1. Milestone 1 — Security audit & hardening (USD 25,000)
-
Contract audit (external firm)
-
Fixes, gas optimizations, and formal verification where feasible
2. Milestone 2 — Pilot integrations & developer UX (USD 20,000)
-
Integrate with 1–2 partner protocols for pilot
-
UX improvements to frontend and SDK based on pilot feedback
3. Milestone 3 — MCP/InfoFi integration & knowledge-graph export (USD 15,000)
-
Build connectors to Intuition graph, triple/atom mapping, and attestations export
-
Implement MCP agent scaffolding for automated context consumption
4. Milestone 4 — Production readiness & ops (USD 10,000)
- Monitoring, observer agents, documentation, example deployments, and community onboarding
5. Buffer / Misc (USD 5,000)
- Contingency, minor bounties, and developer tooling
Expected timeline & deliverables
- Month 0–1: Audit engagement signed, test fixes prioritized.
- Month 1–3: Audit fixes, optimization, and internal QA (Milestone 1 complete).
- Month 3–5: Pilot integrations with 1–2 protocols (Milestone 2 complete).
- Month 5–7: MCP/InfoFi integration and agent scaffolding (Milestone 3 complete).
- Month 7–9: Production readiness, docs, monitoring, and final handoffs (Milestone 4 complete).
Success criteria for each milestone
- M1: Third-party audit completed; no critical-severity issues; all high-severity mitigations merged and tested.
- M2: Pilot protocols integrated; threat detection & challenge workflows exercised in staging; measurable reduction in manual response time.
- M3: Bi-directional flow of triples/signals to Intuition graph demonstrated; MCP agents can consume signals and create attestations.
- M4: Public docs, example deployments, live monitoring, and at least one protocol running AEGIS in staging or production.
Stretch goals
- Cross-protocol attestation marketplace for remedial services
- Automated slashing or insurance hooks
Key dependencies
- Audit firm availability
- Pilot protocol partners for integrations
- Intuition primitives/APIs for graph integration
How this work compounds value for the network
- Adds reusable security primitives, increases on-chain signal density, and encourages cross-protocol shared attestations that improve network-wide threat intelligence.
5. Intuition Ecosystem Alignment
Why Intuition
AEGIS benefits from Intuition’s knowledge-graph primitives (triples/atoms, registry, and MCP) to persist, query, and share trustable attestations and signals about threats.