Code Quill

𝗪𝗵𝗲𝗻 𝗰𝗼𝗱𝗲 𝗶𝘀 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗲𝗱 𝗳𝗮𝘀𝘁𝗲𝗿 𝘁𝗵𝗮𝗻 𝗶𝘁 𝗰𝗮𝗻 𝗯𝗲 𝗿𝗲𝗺𝗲𝗺𝗯𝗲𝗿𝗲𝗱 We are entering an era where code is produced at a rate never seen before. AI systems can generate repositories, refactor large codebases, and produce entire features in minutes. The bottleneck is no longer typing — it’s understanding, coordination, and accountability. As the volume of code increases, something subtle happens: it becomes harder to answer simple questions. What exactly existed at a given moment? Who approved this release? What source state was this artifact supposed to correspond to? When did this change become authoritative? When code is generated rapidly, intent becomes easier to reconstruct after the fact. Facts do not. This is not an argument against AI. It is an argument for stronger evidence infrastructure. If software is increasingly generated, modified, and assembled at machine speed, then preserving durable, inspectable records of source states and release intent becomes more important — not less. The future may involve more automation. But automation without memory becomes noise. In an era of abundant code, what matters is not just what can be produced — but what can be preserved. Software needs memory. CodeQuill is building memory infrastructure for software.

👀

We are finally @ETHGlobal NY hackathon with our Spotlight booth! Come say hi and learn more 👀 #BOOELIEVE Special thanks to @Bookof_Eth of their incredible support 🙏📘

Can’t wait to be there 🎉

$BOOE holders have great quota boost when using CodeQuill 👀

Nine months. Eight immutable contracts. One thesis. CodeQuill is live on @base. Source code is the most reproduced asset in the world. And the least preserved. Repos vanish. Authorship gets murky. History gets rewritten. CodeQuill writes the receipts as code is built. On-chain, immutable, verifiable by anyone. Memory infrastructure for software. codequill.xyz

100% fact

🤣🤣🤣 bonus points for the UPPERCASE

Highly interesting talk!

🙏

𝗖𝗼𝗱𝗲𝗤𝘂𝗶𝗹𝗹 𝗰𝗼𝗻𝘁𝗿𝗮𝗰𝘁𝘀 𝗮𝗿𝗲 𝗻𝗼𝘄 𝗽𝘂𝗯𝗹𝗶𝗰 As we get closer to release, the core CodeQuill smart contracts are open. These contracts implement the on-chain primitives the system is built on: claims of authority, source snapshots, releases, attestations, preservation, and delegation. They are fully permissionless. Anyone can inspect them, reason about them, and build on top of them. Their job is narrow but critical: record durable facts. What source code existed. When it existed. Under whose authority. What claims were made about it. The application layer coordinates, through our CLI and Web interface, the workflows, surfaces evidence, and makes these primitives usable at scale. But the rules that govern the evidence live on-chain, in the open. If CodeQuill is meant to preserve evidence, the mechanisms that record that evidence must themselves be visible and understandable. Architecture diagrams, a permission matrix, and threat model notes are included to make the design legible, not just executable. Ethereum works best when infrastructure explains itself. Repository: github.com/codequill-claim/c… If this is interesting to you, starring the repo and following along on GitHub is the best way to stay close to where the work happens. Much more coming soon.

Supply chain attacks expose a deeper gap. We rely on dependency trees we don’t control, but we don’t preserve durable records of what source states and releases we actually depended on at a given moment. So after the incident, we reconstruct. We don’t reference. That distinction matters more as code generation accelerates.

𝗣𝗿𝗶𝗺𝗶𝘁𝗶𝘃𝗲 𝗩𝗜 - 𝗔𝘀𝘀𝗲𝗿𝘁𝗶𝗻𝗴 𝗮𝗿𝘁𝗶𝗳𝗮𝗰𝘁 𝗹𝗶𝗻𝗲𝗮𝗴𝗲 Once a release is defined, another question follows: What artifacts are claimed to originate from it? In CodeQuill, this is handled through attestations. An 𝗮𝘁𝘁𝗲𝘀𝘁𝗮𝘁𝗶𝗼𝗻 records a statement made by an authority: that a given artifact claims lineage from a specific release. It is a claim — not a proof. CodeQuill does not observe how the artifact was built. It does not guarantee build causality. Instead, it preserves the statement itself as evidence: who made the claim, what artifact was referenced, and which release it was associated with. That distinction matters. Attestations allow lineage claims to be examined later — compared against preserved source states and evaluated in context, even if build systems, logs, or registries are no longer available. They turn assumptions into explicit records. So trust can be reasoned about — not inferred.

We hope the EF will take notice of CodeQuill soon and what we are trying to achieve 🙏 we plan on releasing publicly very soon the whole smart contract architecture underneath CodeQuill and start the beta (free of use) for everyone willing to participate ❤️

𝗣𝗿𝗶𝗺𝗶𝘁𝗶𝘃𝗲 𝗩 — 𝗥𝗲𝗹𝗲𝗮𝘀𝗲 𝗜𝗻𝘁𝗲𝗻𝘁 At some point, software moves from source code to release. A specific repository state is selected and declared as the version meant to ship, govern, or be referenced. Yet this moment — the intent to release — is rarely preserved explicitly. In CodeQuill, this is where 𝗥𝗲𝗹𝗲𝗮𝘀𝗲𝘀 come in. A Release is a deterministic, human-readable record linking a repository snapshot to an explicit release intent, recorded at a point in time under a specific authority. It is: • evidence of selection • evidence of intent to release • evidence of coordination A Release declares: this source state is what we intend to release. That declaration can come directly from the repository authority or through external governance — such as DAO voting or other approval processes. This makes a release more than a technical event. It becomes a coordination point between code, governance, and infrastructure — a stable reference that other systems can rely on: governance decisions, ENS records, and downstream artifact attestations. By making release intent explicit and durable, CodeQuill turns what is usually an implicit step into a verifiable record. Releases become the point where source code and governance meet.