mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-27 15:07:59 +00:00
Aaro Altonen
e71c484d5b
This commit introduces a new concept called `NotificationService` which allows Polkadot protocols to communicate with the underlying notification protocol implementation directly, without routing events through `NetworkWorker`. This implies that each protocol has its own service which it uses to communicate with remote peers and that each `NotificationService` is unique with respect to the underlying notification protocol, meaning `NotificationService` for the transaction protocol can only be used to send and receive transaction-related notifications. The `NotificationService` concept introduces two additional benefits: * allow protocols to start using custom handshakes * allow protocols to accept/reject inbound peers Previously the validation of inbound connections was solely the responsibility of `ProtocolController`. This caused issues with light peers and `SyncingEngine` as `ProtocolController` would accept more peers than `SyncingEngine` could accept which caused peers to have differing views of their own states. `SyncingEngine` would reject excess peers but these rejections were not properly communicated to those peers causing them to assume that they were accepted. With `NotificationService`, the local handshake is not sent to remote peer if peer is rejected which allows it to detect that it was rejected. This commit also deprecates the use of `NetworkEventStream` for all notification-related events and going forward only DHT events are provided through `NetworkEventStream`. If protocols wish to follow each other's events, they must introduce additional abtractions, as is done for GRANDPA and transactions protocols by following the syncing protocol through `SyncEventStream`. Fixes https://github.com/paritytech/polkadot-sdk/issues/512 Fixes https://github.com/paritytech/polkadot-sdk/issues/514 Fixes https://github.com/paritytech/polkadot-sdk/issues/515 Fixes https://github.com/paritytech/polkadot-sdk/issues/554 Fixes https://github.com/paritytech/polkadot-sdk/issues/556 --- These changes are transferred from https://github.com/paritytech/substrate/pull/14197 but there are no functional changes compared to that PR --------- Co-authored-by: Dmitry Markin <dmitry@markin.tech> Co-authored-by: Alexandru Vasile <60601340+lexnv@users.noreply.github.com>
84 lines
3.1 KiB
WebAssembly Text Format
84 lines
3.1 KiB
WebAssembly Text Format
(module
|
|
(import "seal0" "seal_input" (func $seal_input (param i32 i32)))
|
|
(import "seal0" "seal_return" (func $seal_return (param i32 i32 i32)))
|
|
|
|
(import "seal0" "seal_hash_sha2_256" (func $seal_hash_sha2_256 (param i32 i32 i32)))
|
|
(import "seal0" "seal_hash_keccak_256" (func $seal_hash_keccak_256 (param i32 i32 i32)))
|
|
(import "seal0" "seal_hash_blake2_256" (func $seal_hash_blake2_256 (param i32 i32 i32)))
|
|
(import "seal0" "seal_hash_blake2_128" (func $seal_hash_blake2_128 (param i32 i32 i32)))
|
|
|
|
(import "env" "memory" (memory 1 1))
|
|
|
|
(type $hash_fn_sig (func (param i32 i32 i32)))
|
|
(table 8 funcref)
|
|
(elem (i32.const 1)
|
|
$seal_hash_sha2_256
|
|
$seal_hash_keccak_256
|
|
$seal_hash_blake2_256
|
|
$seal_hash_blake2_128
|
|
)
|
|
(data (i32.const 1) "20202010201008") ;; Output sizes of the hashes in order in hex.
|
|
|
|
;; Not in use by the tests besides instantiating the contract.
|
|
(func (export "deploy"))
|
|
|
|
;; Called by the tests.
|
|
;;
|
|
;; The `call` function expects data in a certain format in the input buffer.
|
|
;;
|
|
;; 1. The first byte encodes an identifier for the crypto hash function
|
|
;; under test. (*)
|
|
;; 2. The rest encodes the input data that is directly fed into the
|
|
;; crypto hash function chosen in 1.
|
|
;;
|
|
;; The `deploy` function then computes the chosen crypto hash function
|
|
;; given the input and puts the result into the output buffer.
|
|
;; After contract execution the test driver then asserts that the returned
|
|
;; values are equal to the expected bytes for the input and chosen hash
|
|
;; function.
|
|
;;
|
|
;; (*) The possible value for the crypto hash identifiers can be found below:
|
|
;;
|
|
;; | value | Algorithm | Bit Width |
|
|
;; |-------|-----------|-----------|
|
|
;; | 0 | SHA2 | 256 |
|
|
;; | 1 | KECCAK | 256 |
|
|
;; | 2 | BLAKE2 | 256 |
|
|
;; | 3 | BLAKE2 | 128 |
|
|
;; ---------------------------------
|
|
(func (export "call")
|
|
(local $chosen_hash_fn i32)
|
|
(local $input_len_ptr i32)
|
|
(local $input_ptr i32)
|
|
(local $input_len i32)
|
|
(local $output_ptr i32)
|
|
(local $output_len i32)
|
|
(local.set $input_len_ptr (i32.const 256))
|
|
(local.set $input_ptr (i32.const 10))
|
|
(i32.store (local.get $input_len_ptr) (i32.const 246))
|
|
(call $seal_input (local.get $input_ptr) (local.get $input_len_ptr))
|
|
(local.set $chosen_hash_fn (i32.load8_u (local.get $input_ptr)))
|
|
(if (i32.gt_u (local.get $chosen_hash_fn) (i32.const 7))
|
|
(then
|
|
;; We check that the chosen hash fn identifier is within bounds: [0,7]
|
|
(unreachable)
|
|
)
|
|
)
|
|
(local.set $input_ptr (i32.add (local.get $input_ptr) (i32.const 1)))
|
|
(local.set $input_len (i32.sub (i32.load (local.get $input_len_ptr)) (i32.const 1)))
|
|
(local.set $output_len (i32.load8_u (local.get $chosen_hash_fn)))
|
|
(call_indirect (type $hash_fn_sig)
|
|
(local.get $input_ptr)
|
|
(local.get $input_len)
|
|
(local.get $input_ptr)
|
|
(local.get $chosen_hash_fn) ;; Which crypto hash function to execute.
|
|
)
|
|
(call $seal_return
|
|
(i32.const 0)
|
|
(local.get $input_ptr) ;; Linear memory location of the output buffer.
|
|
(local.get $output_len) ;; Number of output buffer bytes.
|
|
)
|
|
(unreachable)
|
|
)
|
|
)
|