ProofForge RFCs

RFCs define durable architecture decisions for ProofForge. They describe

RFCs define durable architecture decisions for ProofForge. They describe intended capabilities before implementation, and separate current behavior from research or future backend targets.

Process: proposals start as Draft, move to Accepted when recorded in decisions.md and cross-linked docs are aligned.

Index

RFC	Status	Summary
0001	Accepted	Lean-first multi-chain contract platform architecture
0002	Accepted	Target profiles, build pipelines, and backend implementation design
0003	Draft	Portable IR, capability lowering, runtime profiles
0004	Draft	EVM semantic plan and Yul AST boundary
0005	Accepted	Solana sBPF assembly backend — direct codegen route bypassing the Zig runtime
0006	Draft	Multi-chain Token SDK: ERC-20 on EVM, SPL Token / Token-2022 plans on Solana
0007	Draft	Unified Rust test framework: declarative scenarios over revm/Mollusk/wasmtime harnesses
0008	Draft	Chain-decoupled allocator abstraction across EVM, Solana, and NEAR
0009	Accepted	CLI product surface: `build	emit	check —target <id> —fixture <id>`; M1 landed, M3/M4 transition open
0010	Draft	Resource budgets as testkit gates (gas / CU / near-gas)
0011	Draft	Portable runtime error model + unified client generation
0012	Draft	Versioning and compatibility policy (IR, artifact schema, capability ids, SDK)
0013	Draft	Deployment lifecycle, upgrades, and signing boundary

Related

• Documentation index
• Design decisions
• Implementation backlog
• Target notes
• 中文文档