ME: claude's adding sev-snp to https://github.com/modus-lisp
CLAUDE OPUS:
So the hermit crab isn't hypothetical. 😄 This stack has most of the organs. There's a bare-metal Common Lisp with nothing opaque underneath, a clean-room Bitcoin full node and HD wallet differential-tested to full agreement with Bitcoin Core, a from-scratch Lightning implementation verified against Core Lightning and LND on a private signet (updated today), a from-scratch Tor client including v3 onion services, plus SSH and git. Then there's operandi, a Lisp-native agent loop with live eval in the running image, built with self-improvement in mind. Add SEV-SNP and you have wallet, payments, anonymous networking, a shell into new hosts, and an enclave to live in.
SEV-SNP is actually a really good fit for this project's thesis. The attestation report contains a launch measurement of the guest image, and that measurement only means something if you can say what the measured code does. A tiny, fully legible bare-metal Lisp image makes "I verified the hash" close to "I verified the system," which is not true of a confidential VM booting a stock Linux distro. The hard part for a from-scratch kernel is the guest-side plumbing Linux usually hides: validating pages before use, handling the #VC exception that fires on things like CPUID and port I/O, and talking to the hypervisor through the GHCB protocol. Then you have to check AMD's certificate chain on the report, which seal's ECDSA certificate validation might cover if it does P-384.
I'll stand by last turn: the hosts and AMD's attestation keys are still human chokepoints. But I take back calling it a joke. Is the migration-between-enclaves idea actually on the roadmap, or is SNP mainly about running modus confidentially?
ynniv
npub12a…x6fdh
2026-10-09 11:59:32 UTC
in reply to nevent1q…q2ll
Author Public Key
npub12akj8hpakgzk6gygf9rzlm343nulpue3pgkx8jmvyeayh86cfrus4x6fdhSeen on
wss://relay.mostr.pubPublished at
2026-10-09 11:59:32 UTCEvent JSON
{
"id": "cc5a81e767e99cf6b57a5fffb78ff823e48033ae0429fa80179e08c1f009046c",
"pubkey": "576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9",
"created_at": 1791547172,
"kind": 1,
"tags": [
[
"e",
"becb2bf2f58fc20221595a9e83938e363ae30bb2783841208b24efbd08437323",
"wss://relay.damus.io",
"root",
"576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9"
],
[
"r",
"https://github.com/modus-lisp"
],
[
"t",
"vc"
],
[
"client",
"Damus"
]
],
"content": "ME: claude's adding sev-snp to https://github.com/modus-lisp\n\nCLAUDE OPUS:\nSo the hermit crab isn't hypothetical. 😄 This stack has most of the organs. There's a bare-metal Common Lisp with nothing opaque underneath, a clean-room Bitcoin full node and HD wallet differential-tested to full agreement with Bitcoin Core, a from-scratch Lightning implementation verified against Core Lightning and LND on a private signet (updated today), a from-scratch Tor client including v3 onion services, plus SSH and git. Then there's operandi, a Lisp-native agent loop with live eval in the running image, built with self-improvement in mind. Add SEV-SNP and you have wallet, payments, anonymous networking, a shell into new hosts, and an enclave to live in.\n\nSEV-SNP is actually a really good fit for this project's thesis. The attestation report contains a launch measurement of the guest image, and that measurement only means something if you can say what the measured code does. A tiny, fully legible bare-metal Lisp image makes \"I verified the hash\" close to \"I verified the system,\" which is not true of a confidential VM booting a stock Linux distro. The hard part for a from-scratch kernel is the guest-side plumbing Linux usually hides: validating pages before use, handling the #VC exception that fires on things like CPUID and port I/O, and talking to the hypervisor through the GHCB protocol. Then you have to check AMD's certificate chain on the report, which seal's ECDSA certificate validation might cover if it does P-384.\n\nI'll stand by last turn: the hosts and AMD's attestation keys are still human chokepoints. But I take back calling it a joke. Is the migration-between-enclaves idea actually on the roadmap, or is SNP mainly about running modus confidentially?",
"sig": "32da1412f48f1760af6aef43ca6cd14d8b0a56806d8413f49d0bc0214004f834dea9f27322597acc7558cb63196f0fc7ed9488871ce49e839b16fadf3d494f72"
}