Repository navigation
Add shared wallet planning and protocol policies for v0.2.0 - #1
Merged
Merged
Conversation
This file contains hidden or 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
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.
Wallet clients need the shared core's lock, metadata, fee, and allocation rules to produce the same transactions across runtimes. This implements those rules natively against
tx-typesat02d194605c475013745cc65b26f1413cd098932eand the official Hoon fixtures at9bcc26c6c57019dfde7f83aad9a9dd4ed5cd7902, and sets the SDK version to 0.2.0.The shared corpus checks all 31 tagged lock leaves, Hoon metadata and fee results, seven Rust planner scenarios, and four migration scenarios with exact unsigned and signed bytes. Documentation describes the APIs, height/fee context, and validation boundaries. This does not publish a package or tag.
The native Go APIs and typed WebAssembly adapter expose the same planner. The adapter accepts complete note JAM, returns selected records and fee breakdowns, and carries migration/fund context through inspection and signing. The repository also contains the reproducible cross-SDK fixture exporter.
Validation:
go vet ./...,go test -race ./..., andgofmtchecks pass.js/wasmintegration tests pass, including planner and signed migration goldens; TypeScript declarations check successfully.--check --protocol-corpus testdata/reference.jsonand all copied Hoon SHA-256 checksums pass.Related core work: SWPSCO/tx-types#25