James Wilson
b6b9ac65c7
* TransactionExtensions basic support for V5 VerifySignature and renames * WIP: subxt-core v5 transaction support * Subxt to support V5 extrinsics * WIP tests failing with wsm trap error * Actually encode mortality to fix tx encode issue * fmt * rename to sign_with_account_and_signature * Add explicit methods for v4 and v5 ext construction * clippy * fix wasm example and no mut self where not needed * fix doc example * another doc fix * Add tests for tx encoding and fix v5 encode issue * add copyright and todo * refactor APIs to have clear v4/v5 split in core and slightly nicer split in subxt proper * rename Partial/SubmittableExtrinsic to *Transaction * Remove SignerT::address since it's not needed * doc fixes * fmt * doc fixes * Fix comment number * Clarify panic behaviour of inject_signature * fmt
wasm-example
This is a small WASM app using the Yew UI framework to showcase how to use Subxt's features in a WASM environment.
To run the app locally we first install Trunk, a WASM bundler:
cargo install --locked trunk
You need to have a local polkadot/substrate node with it's JSON-RPC HTTP server running at 127.0.0.1:9933 in order for the examples to be working.
If you have a polkadot binary already, running this should be sufficient:
polkadot --dev
Then, in another terminal, run the app locally with:
trunk serve --open
signing example
For the signing example, we use the @polkadot/extension-dapp NPM package to talk to wallets loaded as browser extensions. In order to sign and submit the transaction using the polkadot --dev node we spawned above, you'll need to create a dev account in your wallet of choice. Use the recovery phrase bottom drive obey lake curtain smoke basket hold race lonely fit walk and the derivation path //Alice to create a dev account that can be used.