-
Notifications
You must be signed in to change notification settings - Fork 72
adds clean copy of dual-vm-stack.md page and updated LLMs files #1145
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates the documentation for Polkadot's smart contract virtual machine architecture by replacing the previous "PolkaVM Design" page with a new "Dual Virtual Machine Stack" page. The changes reflect Polkadot's dual-VM approach, introducing REVM (Rust Ethereum Virtual Machine) for EVM compatibility alongside the existing PolkaVM content.
- Restructured content to emphasize both REVM and PolkaVM options
- Updated page title, description, and section headings
- Removed compilation process details and mermaid diagrams showing VM architecture comparison
- Added migration guidance for choosing between REVM and PolkaVM
Reviewed Changes
Copilot reviewed 13 out of 13 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
smart-contracts/for-eth-devs/dual-vm-stack.md |
Complete rewrite introducing dual-VM architecture with REVM and PolkaVM |
llms.txt |
Updated page title and description references |
llms-full.jsonl |
Updated metadata, content, and structure for the new page |
.ai/site-index.json |
Updated last modified timestamps across multiple entries |
.ai/pages/smart-contracts-for-eth-devs-dual-vm-stack.md |
AI-generated page version with same content updates |
.ai/categories/*.md |
Updated category files with new page content |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
@dawnkelly09 merge conflicts 🙃 |
📝 Description
Provide a clear and concise description of your changes.
I made a mess out of attempting to clear merge conflicts for #1028 and accidentally merged in changes from master rather than staging. This PR adds the new documentation page Nico added in his PR and updates the LLMs files with the added content. This PR should be merged INSTEAD of #1028, which can then be closed.