Bastian Köcher d489bd70b5 Do not call initialize_block before any runtime api (#8953) ...

* Do not call `initialize_block` before any runtime api

Before this change we always called `initialize_block` before calling
into the runtime. There was already support with `skip_initialize` to skip
the initialization. Almost no runtime_api requires that
`initialize_block` is called before. Actually this only leads to higher
execution times most of the time, because all runtime modules are
initialized and this is especially expensive when the block contained a
runtime upgrade.

TLDR: Do not call `initialize_block` before calling a runtime api.

* Change `validate_transaction` interface

* Fix rpc test

* Fixes and comments

* Some docs

2021-07-01 15:50:42 +00:00

..

client

Introduce code_substitute (#8898)

2021-05-25 14:07:36 +00:00

src

Do not call initialize_block before any runtime api (#8953)

2021-07-01 15:50:42 +00:00

transaction-pool

Transaction pool: Ensure that we prune transactions properly (#8963)

2021-06-03 16:04:29 +02:00

build.rs

Init RuntimeLogger automatically for each runtime api call (#8128)

2021-03-01 15:29:17 +01:00

Cargo.toml

Make BlockImport and Verifier async (#8472)

2021-03-30 09:19:49 +00:00