Back to corpus
architecturetechnical paper candidatescore 22
EPOCH Appchain: Stacks Fork + Native Rust Services
Instead of 5 external services talking to the chain via HTTP, they become native chain modules. Graph Kernel queries happen at chain speed, not network speed. N'Ko inscriptions render inside the block validator. RAG++ vector search is part of consensus.
Full HTML reader
Read the full artifact
Extracted abstract or opening context
Instead of 5 external services talking to the chain via HTTP, they become native chain modules. Graph Kernel queries happen at chain speed, not network speed. N'Ko inscriptions render inside the block validator. RAG++ vector search is part of consensus.
| Crate | Lines | Appchain Role | |-------|-------|--------------| | cc-rag-plus-plus | 33,274 | Native vector similarity precompile | | cc-inscription | 22,881 | Native inscription validator (the killer feature) | | cc-graph-kernel | 14,953 | Native context slicing with admissibility tokens | | cc-protocol | 7,429 | Smart contract type definitions | | cc-kernel | 4,357 | Ledger/storage layer | | cc-semantic-language | 4,000 | N'Ko text processing primitives |
**Appchain spec**: 764 lines at `docs/appchain-mining-spec.md` covering mining rules, bridge contracts, economic model, security analysis.
**Fork base**: Stacks `feat/app-chain-mvp` branch. Alpha quality, predates Nakamoto upgrade. Needs rebase against v3.[ip].
These run inside the block validator at Rust speed, not Clarity interpreter speed.
Promotion decision
What has to happen next
Promote into a technical note or architecture paper with implementation anchors.
Why this is not always a full paper yet
Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.