diff --git a/01_host/04_networking/10_light-client.adoc b/01_host/04_networking/10_light-client.adoc deleted file mode 100644 index 52d44ea6c..000000000 --- a/01_host/04_networking/10_light-client.adoc +++ /dev/null @@ -1,188 +0,0 @@ -[#sect-light-msg] -= Light Client Messages - -Light clients are applications that fetch the required data that they need from -a Polkadot node with an associated proof to validate the data. This makes it -possible to interact with the Polkadot network without requiring to run a full -node or having to trust the remote peers. The light client messages make this -functionality possible. - -All light client messages are protobuf encoded and are sent over the -`/91b171bb158e2d3848fa23a9f1c25182fb8e20313b2c1eb49219da7a70ce90c3/light/2` substream. - -== Request - -A message with all possible request messages. All message are sent as part of -this message. - -[cols="2,1,5"] -|=== -|Type |Id |Description - -|`oneof` (`request`) -| -|The request type -|=== - -Where the `request` can be one of the following fields: - -[cols="2,1,5"] -|=== -|Type |Id |Description - -|`RemoteCallRequest` -|1 -|A remote call request (<>) - -|`RemoteReadRequest` -|2 -|A remote read request (<>) - -|`RemoteReadChildRequest` -|4 -|A remote read child request (<>) -|=== - -== Response - -A message with all possible response messages. All message are sent as part of -this message. - -[cols="2,1,5"] -|=== -|Type |Id |Description - -|`oneof` (`response`) -| -|The response type -|=== - -Where the `response` can be one of the following fields: - -[cols="2,1,5"] -|=== -|Type |Id |Description - -|`RemoteCallResponse` -|1 -|A remote call response (<>) - -|`RemoteReadResponse` -|2 -|A remote read response (<>) -|=== - -== Remote Call Messages - -Execute a call to a contract at the given block. - -[#sect-light-remote-call-request] -.<> -==== -Remote call request. - -[cols="1,1,5"] -|=== -|Type |Id |Description - -|`bytes` -|2 -|Hash of the header of the block at which to perform call - -|`string` -|3 -|Method name - -|`bytes` -|4 -|Call data, corresponding to `A` in the algorithm of -<> -|=== -==== - -[#sect-light-remote-call-response] -.<> -==== -Remote call response. - -[cols="1,1,5"] -|=== -|Type |Id |Description - -|`bytes` -|2 -|Merkle proof of the storage items accessed by the call, as defined in -<>. The field is missing if the request can't be answered -because the call failed or the block is inaccessible. -|=== -==== - -== Remote Read Messages - -Read a storage value at the given block. - -[#sect-light-remote-read-request] -.<> -==== -Remote read request. - -[cols="1,1,5"] -|=== -|Type |Id |Description - -|`bytes` -|2 -|Hash of the header of the block at which to read the storage - -|`repeated bytes` -|3 -|List of storage keys to query -|=== -==== - -[#sect-light-remote-read-response] -.<> -==== -Remote read response. - -[cols="1,1,5"] -|=== -|Type |Id |Description - -|`bytes` -|2 -|Merkle proof of the requested storage items, as defined in -<>. The field is missing if the request can't be answered -because the block is inaccessible. -|=== -==== - -== Remote Read Child Messages - -Read a child storage value at the given block. - -[#sect-light-remote-read-child-request] -.<> -==== -Remote read child request. - -[cols="1,1,5"] -|=== -|Type |Id |Description - -|`bytes` -|2 -|Hash of the header of the block at which to read the storage - -|`bytes` -|3 -|Child storage key, this is relative to the child type storage location - -|`repeated bytes` -|6 -|List of storage keys to query -|=== -==== - -The response is the same as for the _Remote Read Request_ message, respectively -<>.