feat: Add Wasm sandbox proposal document #93
Conversation
This change introduces a new document, info.wasm.sandbox.md, which proposes replacing the existing smart contract sandbox with a more secure and performant Wasm-based solution. The document outlines the limitations of the current system, the benefits of Wasm, a proposed architecture, a migration path, and a future roadmap.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This change significantly enhances the Wasm sandbox proposal document by incorporating detailed technical learnings and best practices from other major blockchain platforms that use Wasm. The document now includes: - A new section on "Learnings from Other Blockchains" (NEAR, Polkadot, CosmWasm, EOS). - A completely revised "Proposed Architecture" section with specific recommendations on runtime choice (Wasmtime), determinism, gas metering, memory management, and API design. - A new "Further Reading" section with links to valuable resources.
This change introduces a new document, info.wasm.sandbox.md, which proposes replacing the existing smart contract sandbox with a more secure and performant Wasm-based solution. The document outlines the limitations of the current system, the benefits of Wasm, a proposed architecture, a migration path, and a future roadmap.
PR created automatically by Jules for task 6122992729921204512 started by @attogram