mirror of https://github.com/status-im/swarms.git
* Rename #95 and more precise priorizing * Add ULC goal regarding battery and network consumption * Fix status
This commit is contained in:
parent
af823d024a
commit
21c49373f3
|
@ -1,23 +1,36 @@
|
|||
---
|
||||
id: 095-les-improvement
|
||||
title: Improvement of LES
|
||||
status: Active
|
||||
created: 2018-03-20
|
||||
contributors:
|
||||
- themue
|
||||
- jeka
|
||||
- b00ris
|
||||
- zsfelfoldi (external)
|
||||
---
|
||||
|
||||
## Preamble
|
||||
|
||||
Idea: #095-les-service-model
|
||||
Title: Introduce LES Service Model
|
||||
Status: Draft
|
||||
Idea: #095-les-improvement
|
||||
Title: Improvement of LES
|
||||
Status: In progress
|
||||
Created: 2018-03-20
|
||||
|
||||
## Summary
|
||||
|
||||
Introduce the LES Service Model where LES clients can subscribe to higher quality services. Different
|
||||
payment models will be available, negotiation between client and full node is done via auctions based
|
||||
on demands and capacity.
|
||||
Current LES is not yet optimized for ultra-light devices like mobile phones. So in the first step introduce
|
||||
the ULC addressing this kind of clients.
|
||||
|
||||
This way full node service provide are able to monetize the services they provide. LES will make the
|
||||
Later add the LES Service Model where clients can subscribe to higher quality services. Different payment
|
||||
models will be available, negotiation between client and full node is done via auctions based on demands and
|
||||
capacity. This way full node service provide are able to monetize the services they provide. LES will make the
|
||||
beginning, Whisper and Swarm may follow.
|
||||
|
||||
## Swarm Participants
|
||||
|
||||
- Lead Contributor: @themue
|
||||
- Testing & Evaluation:
|
||||
- Testing & Evaluation: TBD
|
||||
- Contributor: @jeka
|
||||
- Contributor: @b00ris
|
||||
- PM: @zsfelfoldi (external)
|
||||
|
@ -25,8 +38,14 @@ beginning, Whisper and Swarm may follow.
|
|||
|
||||
## Product Overview
|
||||
|
||||
Today all light clients are treated equal by the full nodes they connect. A future service model will introduce
|
||||
the separation between free and payed services. As outlined by Felföldi Zsolt:
|
||||
Current LES is not optimized for usage on mobile phones. So Status is using Infura with all its assets and
|
||||
drawbacks. ULC is addressing ultra-light clients and distribution without dependency to central providers.
|
||||
Instead a network of trusted LES nodes acts as counterpart for the protocol.
|
||||
|
||||
So Status is supporting the development and testing of ULC to accelerate integration into *geth*.
|
||||
|
||||
Als right now all light clients are treated equal by the full nodes they connect. A future service model will
|
||||
introduce the separation between free and payed services. As outlined by Felföldi Zsolt:
|
||||
|
||||
- LES will be available either as free or paid service,
|
||||
- paid service can guarantee availability and short response times,
|
||||
|
@ -35,11 +54,8 @@ the separation between free and payed services. As outlined by Felföldi Zsolt:
|
|||
- free service is a good indicator of high bandwidth capacity and therefore the capability to provide good service, and
|
||||
- paying clients will prefer servers which already gave them free service so free service can act as an advertisement.
|
||||
|
||||
Once the service model is introduced changes to Status app are needed:
|
||||
|
||||
- Migration from Infura to ULC
|
||||
- Choice between free and paid LES service
|
||||
- In case of paid LES service definition of demands for auction
|
||||
Here Status also supports the development and testing to make the service model become a part of *geth* and be
|
||||
integrated into Status.
|
||||
|
||||
### Remark
|
||||
|
||||
|
@ -48,8 +64,9 @@ for own clients. This business case should be evaluated in an own swarm.
|
|||
|
||||
### Product Description
|
||||
|
||||
Parts of the introduction of the LES Service Model are:
|
||||
Parts of ULC and the LES Service Model introduction are:
|
||||
|
||||
- research, definition, and implementation of ULC,
|
||||
- research, definition, and implementation of connection management system of paying clients for full nodes,
|
||||
- research, definition, and implementation of auctioning,
|
||||
- research, definition, and implementation of payment methods and models,
|
||||
|
@ -61,9 +78,10 @@ Goal Date: TBD (before end of Q2/2018)
|
|||
|
||||
Description:
|
||||
|
||||
- [ ] New Ultra Light Client Mode is added to LES
|
||||
- [ ] Integrate ULC with status-go,
|
||||
- [ ] Collect metrics (CPU, mem, disk, network I/O) when starting with a branch new install and after 1h of inactivity.
|
||||
- [ ] New Ultra Light Client mode is added to LES
|
||||
- [ ] Integrate ULC with `status-go`
|
||||
- [ ] Collect metrics (CPU, mem, disk, network I/O) when starting with a branch new install and after 1h of inactivity
|
||||
- [ ] Keep battery and network consumption at least as low as today with Infura
|
||||
|
||||
### Iteration 1
|
||||
|
||||
|
@ -72,7 +90,7 @@ Goal Date: TBD
|
|||
Description:
|
||||
|
||||
- [ ] Auctioning protocol between client and full node is defined
|
||||
- [ ] Payment methods or interfaces are defined
|
||||
- [ ] Payment methods and interfaces are defined
|
||||
- [ ] Initial implementation validates auctioning and micropayment in automated tests
|
||||
|
||||
## Artifacts
|
||||
|
@ -83,7 +101,7 @@ Description:
|
|||
|
||||
## Success Metrics
|
||||
|
||||
LES of `go-ethereum` is extended to provide micropayed services with a higher quality
|
||||
LES of `go-ethereum` is extended to use ULC and provide micropayed services with a higher quality
|
||||
level as well as free services depending on capacity and configuration.
|
||||
|
||||
## Copyright
|
|
@ -1,5 +1,12 @@
|
|||
## Logfile
|
||||
|
||||
### 2018-04-26
|
||||
|
||||
- ULC has higher priority to become independend of Infura asap
|
||||
- Swarm has been renamed to #095-les-improvement
|
||||
- MVP is now ULC integration
|
||||
- Iteration 1 is initial development of LES service model
|
||||
|
||||
### 2018-04-12
|
||||
|
||||
- Exchange about observer chain/chain filters and sharding
|
Loading…
Reference in New Issue