polkadot | Polkadot Node Implementation | Blockchain library

Some how coin_name is twice as long as your other lists. Once you fix that you can do this:

You should pass {"withType": true} to the sign method too.

Wasm can be pretty hefty in its raw form. This leads to problems, for example, when upgrading from one version of the Substrate Runtime (the wasm file) to another. This is because the upgrade should fit into a block body which is capped at ≈4 MiB. A recent Polkadot wasm blob is 4.7 MiB. If you apply the zstd compression to the same file it would go down to 1.1 MiB.

That was a rationale for us to introduce compression for the wasm blobs. To distinguish between the compressed and uncompressed wasm, we introduced our own magic number. That's the magic you see there.

This logic is pretty much encapsulated in sp-maybe-compressed-blob crate.

You can decide entirely on your own how transactions are prioritized. If you are using the default ChargeTransactionPayment signed extension you will use the following formula to calculate the priority: https://github.com/paritytech/substrate/blob/fb24fda76d613305ebb2e5728c75362c94b64aa1/frame/transaction-payment/src/lib.rs#L614-L681

Sorry - you may not like the answer.

There is no option in gradle (7.2) to suppress specific deprecation. Fixing the build file is going to be cheaper and correct.

By writing out a "bridging" layer, you can do it easily.

Firstly, create a normal javascript (or typescript) application (nothing related to Flutter). You should be able to happily use the polkadot lib in your js/ts code without any problem. You may need to learn a bit about how to develop js code normally (e.g. you can depend on polkadot using npm, etc).

One small thing is that, you should "expose" some object publicly in your js/ts code. For example, your code may look like window.myFancyFunction = function() { call_some_polkadot_function(); }. Of course you can do more things like exposing other functions/objects/...

Then, you can bundle this normal js/ts application into a .js file. This is still very normal for js/ts developers and should have nothing special to deal with here, and you still do not need to touch Flutter at this stage.

Next, load this single-filed .js file when you are loading your Flutter Web application. You may simply do this by editing your Flutter Web's html file and add . Notice that, when loading this script, it simply sets window.myFancyFunction and does not do anything more. Still very trivial here, should have no problem.

Lastly, in your Flutter Web code, i.e. Dart code, call that window.myFancyFunction function. For example, Flutter Web : How to run javascript using dart js says you can do import 'dart:js' as js; js.context.callMethod('myFancyFunction', ['some arguments']);

You can use this code:

Signing a transaction on one computer and sending it from a second computer is definitely possible.

PolkadotJS Tools contains a method for building and signing a transaction offline. You can find the source here. Please note that building the transaction in the browser will still require access to a polkadot node (the endpoint in the code).

The signer sendOffline command has the exact same API, but will not broadcast the transaction. submit and sendOffline must be connected to a node to fetch the current metadata and construct a valid transaction. Their API has the format:

Therefore, you'd need to run a light client in the browser in order to have access to current block information or attach to some other node endpoint outwith the browser.

The problem here was substrate-contracts-node using an old version of the metadata.

I was able to check out the repo before the metadata merge was reverted and build locally (cargo build).

So checkout 8d91b8e to get the node to work with versions 7.7.1 and 6.6.1 of polkadot-js packages.