fabius-catenalisted

fabius's on-chain layer — build trustless systems on a blockchain and prove provenance with one. Two jobs under one concern: (1) write and review on-chain code — EVM (Solidity / Foundry / EIP-712) and Solana (Anchor / Pinocchio) programs, wallets, transactions, on-chain reads — account-validation first, money-safe by default; (2) cryptographically SEAL artifacts with independently checkable provenance — a content-bound hash, a signature, and a timestamp whose pending or confirmed status and trust assumptions are reported. Use when the task touches a smart contract, a program, a wallet, a transaction, a token/mint, an on-chain read, or when the user says "seal this", "sign this file", "prove provenance", "anchor it", or "verify authenticity". Boring-cryptography only; defensive — it hardens and proves, never weaponizes: no exploit tooling, no wallet-draining, no rug mechanics, no market-manipulation code — hardening and verification only.
shear559/fabius · ★ 2 · AI & Automation · score 64

Install: claude install-skill shear559/fabius

# Fabius Catena — build on the chain, prove with the chain *Catena* — the chain. One concern with two faces: write code that runs **on** a chain, and use a chain to **prove** something existed and was signed. Both rest on the same discipline — assume the adversary controls every input, and trust math over operators. ## 1. The two jobs, and the line between them - **Build on-chain.** Contracts, programs, wallet and transaction flows, on-chain reads. The risk is money and irreversibility, so the bar is higher than ordinary code. - **Prove with the chain.** Seal an artifact (a file, a release, a dataset) so its existence bound and release-key attribution are independently checkable under stated trust assumptions. This is `fabius`'s own provenance mechanism (see [PROVENANCE.md](../../PROVENANCE.md)) made reusable. `fabius-praesidium` owns *application* defensive security; `fabius-catena` owns the *on-chain* surface (account validation, transaction safety) and *cryptographic provenance*. Both stand on `fabius-parcus`'s never-trim floor and never drop below it. ## 2. On-chain is account-validation-first Assume the attacker controls **every account, every argument, the transaction ordering, and the call graph.** Validation is the work; the business logic is the easy part. The vulnerabilities to check on every program, named so yo