use wazero #582
Draft
use wazero #582
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
faddat
changed the title
faddat
changed the title
- Updated `MockEnv` to use `types.Uint64` for time representation. - Introduced helper functions for memory operations: `readMemory` and `writeMemory`. - Replaced direct memory read/write calls in `hostGet` and other functions with the new helpers. - Removed the `MemoryAllocator` struct and related functions, simplifying memory management. - Cleaned up unused code and deleted obsolete files in the `libwasmvm` directory. - Adjusted function signatures and error handling for better clarity and consistency. This commit enhances the overall structure and readability of the codebase while ensuring proper memory handling.
run tests
- Deleted unused `prettyJSON` helper function from `internal/api/api_test.go` - Simplified test file by removing unnecessary JSON formatting utility - Kept `prettyPrint` function for struct formatting
This commit introduces several key changes: - Moved host functions to a separate package - Simplified host function registration - Updated memory management and region handling - Added String() method to Checksum type for hex encoding - Improved error handling and logging in host functions - Restructured runtime interfaces for better modularity
Modify the Secp256k1RecoverPubkey method call to match the updated function signature, which now returns an additional value. This change ensures compatibility with the latest API implementation.
This commit extends the cryptographic capabilities of the library by: - Adding BLS12-381 cryptographic function signatures to the GoAPI type - Updating host crypto functions to use new runtime and memory management - Implementing gas charging for BLS12-381 operations - Refactoring import paths and function signatures for crypto-related methods
|
Yesterday I broke this Branch but it was intentional. There really wasn't any way for me to break changes up into pieces and I wanted to break this into multiple packages |
This commit introduces comprehensive gas management modules for the WasmVM runtime: - Created gas package with core GasState implementation - Added gas configuration modules for different CosmWasm versions (v1.x and v2.x) - Implemented default gas configuration methods - Structured gas tracking and consumption logic - Prepared foundation for flexible gas metering across runtime versions
…anagement This commit introduces a new WasmRuntime interface that defines a comprehensive set of methods for managing WebAssembly smart contract lifecycles, including: - Code storage and management operations - Contract instantiation, execution, and migration methods - IBC (Inter-Blockchain Communication) entry points - Caching and resource management - Metrics retrieval The interface provides a flexible and extensible approach to handling WASM contract interactions across different runtime environments.
This commit introduces several improvements to the internal API library: - Simplified runtime initialization and cache management - Enhanced error handling with more descriptive error messages - Removed unused methods and simplified function signatures - Updated import paths to reflect new package structure - Added more descriptive comments for public functions - Streamlined code storage and contract lifecycle methods The changes improve code readability, error reporting, and overall maintainability of the WASM runtime library.
…tions This commit introduces significant improvements to the crypto and runtime modules: - Added new cryptoapi interfaces for crypto operations - Implemented comprehensive BLS12-381 cryptographic functions - Created new gas management and runtime type definitions - Updated host functions to use new crypto and runtime interfaces - Improved gas metering and configuration handling - Enhanced memory and context management for contract execution The changes provide a more modular, flexible, and extensible approach to cryptographic operations and runtime management in the WasmVM library.
This commit enhances the WasmVM library's cryptographic capabilities by: - Implementing host functions for secp256k1, ed25519, and BLS12-381 cryptographic operations - Adding a new RegisterHostFunctions method to export crypto functions to WebAssembly modules - Introducing a ReadUint32 utility method in the memory manager for reading 32-bit integers - Implementing gas charging for various cryptographic verification operations - Improving memory management for batch verification and key recovery functions The changes provide a more comprehensive and flexible approach to handling cryptographic operations in the WebAssembly runtime.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
status
problems
what?
To ensure that contracts can run reliably without stopping chains, we shall endeavor to swap out wasmer for wazero. Wasmer is a great wasm vm written in rust, a great programming language. Wazero is a great web assembly virtual machine written in go, a great programming language (with horrible c interop). Both languages get spicy around interop, so it is best to code an entire blockchain application in just one programming language. Additionally, Go memory management breaks when using cgo to import C.
why?
Because cgo doesn't work all that well, and messes up some basic features of Go. Also, similar ABI issues and c interop issues on the rust side, so it is probably not a good idea to use cgo / unsafe in go / unsafe in rust on >40 production networks, even if we are just accounting for the extreme increase in random explosions cause by cgo. But in fact we will be able to reduce explosions in many other ways too.
Probably right now this is a proof of concept.
How?
When the lint PR's are merged to main, they can be merged here also.
clarify structure
Create an interface for runtimes so that the runtime interface is clear
implement wazero in the runtime folder
implement the
whats the trick?
The trick is that cosmwasm's vm package is imported by libwasmvm and provides a lot of functions. We will need to recreate that for wazero and use the
host functionsfeature.there's a pretty clear migration path to wazero insrtead of wasmer in wasmvm.
When I began to work on cosmwasgo, I made a design mistake and made things less modular.
Today, I began to go through all of the code file by file, and I was able to get to a pretty good place. I still need to reconcile your last commit though.
Although I have hardcoded the runtime, I think you can see how using the
runtimefolder and theruntimeinterface allows for a pretty singificant simplification of wasmvm.There are still remaining questions around gas metering, and a few other things.
cheers!
-Jacob
Note: even if you do not reveiw or merge this, I would appreciate not closing it. Among other things I am using the PR to compare.
Random notes that I will add to as I go: