status-im/specs
2
0
Fork 0
mirror of https://github.com/status-im/specs.git synced 2025-01-19 10:53:10 +00:00
Code Issues Projects Releases Wiki Activity

FAQ on RLPx subprotocols like LES and Swarm

Browse Source
This commit is contained in:
Oskar Thoren 2019-08-26 16:32:46 +02:00
parent 25068e6fda
commit 5c4a9129bf
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 15 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
status-spec.md
View File

@ -55,6 +55,21 @@ etc.
For very experimental bridge support, see the bridge between libp2p and devp2p
in [Murmur](https://github.com/status-im/murmur).
#### What about other RLPx subprotocols like LES, and Swarm?
Status is primarily optimized for resource restricted devices, and at present
time light client support for these protocols are suboptimal. This is a work in
progress.
For better Ethereum light client support, see (Re-enable LES as
option)[https://github.com/status-im/status-go/issues/1025]. For better Swarm
support, see (Swarm adaptive
nodes)[https://github.com/ethersphere/SWIPs/pull/12].
For transaction support, Status clients currently have to rely on Infura.
Status clients currently do not offer native support for file storage.
## Footnotes
1. <https://github.com/status-im/status-protocol-go/>