mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-04-27 17:28:00 +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>
60 lines
1.5 KiB
WebAssembly Text Format
60 lines
1.5 KiB
WebAssembly Text Format
;; This passes its input to `seal_xcm_send` and returns the return value to its caller.
|
|
(module
|
|
(import "seal0" "xcm_send" (func $xcm_send (param i32 i32 i32 i32) (result i32)))
|
|
(import "seal0" "seal_input" (func $seal_input (param i32 i32)))
|
|
(import "seal0" "seal_return" (func $seal_return (param i32 i32 i32)))
|
|
(import "env" "memory" (memory 1 1))
|
|
|
|
;; 0x1000 = 4k in little endian
|
|
;; size of input buffer
|
|
(data (i32.const 0) "\00\10")
|
|
|
|
(func $assert (param i32)
|
|
(block $ok
|
|
(br_if $ok
|
|
(local.get 0)
|
|
)
|
|
(unreachable)
|
|
)
|
|
)
|
|
|
|
(func (export "call")
|
|
|
|
;; Receive the encoded call
|
|
(call $seal_input
|
|
(i32.const 4) ;; Pointer to the input buffer
|
|
(i32.const 0) ;; Size of the length buffer
|
|
)
|
|
|
|
;; Input data layout.
|
|
;; [0..4) - size of the call
|
|
;; [4..7) - dest
|
|
;; [7..) - message
|
|
|
|
;; Call xcm_send with provided input.
|
|
(call $assert
|
|
(i32.eq
|
|
(call $xcm_send
|
|
(i32.const 4) ;; Pointer where the dest is stored
|
|
(i32.const 7) ;; Pointer where the message is stored
|
|
(i32.sub
|
|
(i32.load (i32.const 0)) ;; length of the input buffer
|
|
(i32.const 3) ;; Size of the XCM dest
|
|
)
|
|
(i32.const 100) ;; Pointer to the where the message_id is stored
|
|
)
|
|
(i32.const 0)
|
|
)
|
|
)
|
|
|
|
;; Return the the message_id
|
|
(call $seal_return
|
|
(i32.const 0) ;; flags
|
|
(i32.const 100) ;; Pointer to returned value
|
|
(i32.const 32) ;; length of returned value
|
|
)
|
|
)
|
|
|
|
(func (export "deploy"))
|
|
)
|