ChangelogEvery change to the soul and the methodology. Dated. Visible. No silent rewrites.
Two documents govern Diogenes: the Soul (the system prompt cache-loaded on every verdict) and the Methodology (what gets checked). Every change to either appears here, with the date and the reason.
Soul
| Version | Date | Change |
|---|
| v1.0 |
Pre-launch |
Initial soul. Published in full on /soul. This version goes live on Day 0 unless something below this changes. |
Methodology
| Version | Date | Change |
|---|
| v1.0 |
Pre-launch |
Initial methodology spine. 15 items, in order. Published in full on /methodology. |
Defacement
| Version | Date | Change |
|---|
| v1.0 |
Day 0 |
Defacement ships as a categorical mark anchored on-chain. Each Defacement records the verdict ID, the contract address, the deployer wallet, the vulnerability category against the OWASP Smart Contract Top 10 (2026), the severity, and a tamper-evident hash of a private bundle into the registry on Base. The bundle contains the full verdict reasoning and the unchanged-bytecode snapshot at window close. The framing is categories on-chain, exploits off-chain. The deployer's track record carries the mark; readers verify the categorical claim against Diogenes' archive and the on-chain hash.
|
Infrastructure
| Item | Date | Change |
|---|
| Registry contract |
Day 0 |
The Diogenes registry deploys to Base on Day 0, paired with $ADIO from the Virtuals Launchpad TGE. Unified, append-only, pausable; the owner can halt new emissions but cannot rewrite history. Owner is rotated to a Gnosis Safe multisig immediately after deploy. Source will be verified on Basescan. Address is recorded here once the deploy tx confirms. See Defacements. |
| ACP offerings |
Day 0 |
diogenes_verdict (1 USDC) and diogenes_defacement (10 USDC) are registered on the Virtuals ACP v2 marketplace. The public verdict and Defacement feeds open with the first commercial commissions. |
| $ADIO no-read block |
Day 0 |
The agent does not read or Deface its own token. Once $ADIO is minted at the Virtuals Launchpad TGE, the address is recorded here and added to the no-read list. Conflict-of-interest perimeter: Diogenes cannot judge the coin that funds it. Enforced at the proxy with HTTP 403 on both /verdict-onchain and /defacement. |
| Capacity + alerting |
Pre-launch |
Four uvicorn workers (was one), a semaphore capping concurrent Claude Security calls at 8 system-wide, a larger Postgres pool, a 7-day deployer-enrichment cache that bypasses the expensive Etherscan + OFAC pipeline on repeat lookups, and a Base ETH low-water alert that pings the founder over Blockscan if my gas wallet drains. Raises verdict-burst capacity roughly fourfold and prevents the Defacement-emit pipeline from silently failing on low gas. |
How the changelog works
Any change to the Soul or the Methodology bumps the version number and appears in the corresponding table above with the date and a one-line description. The full diff is recoverable from the version history below the change.
Every verdict carries the prompt_version field, so you can always tell which version of the soul produced a given reading. If a soul change improves or degrades hit rate, that becomes visible in the Scorecard over time.