Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Devise how to update CHT automatically #320

Closed
tiabc opened this issue Sep 14, 2017 · 3 comments
Closed

Devise how to update CHT automatically #320

tiabc opened this issue Sep 14, 2017 · 3 comments
Labels

Comments

@tiabc
Copy link
Contributor

tiabc commented Sep 14, 2017

Problem Overview

CHT stands for Canonical Hash Trie - a concept of go-ethereum allowing to start synchronisation from the last trusted state which we use to avoid overheating phones, long synchronisation time and battery drain.

Currently, CHT is embedded into status-go source code and it brings a number of problems:

  1. We have to manually update CHT for every release.
  2. As we release about twice a month, CHT gets more and more outdated.
  3. Synchronisation time (and thus heating and battery drain) gets tangible for outdated versions.

Implementation

The first step is to investigate how it can be achieved and there're some options:

  1. A temporary and quick solution could be a dedicated server which will publish actual CHT values which our application will request for the most recent CHT before starting block synchronisation.
  2. Implement and register another p2p protocol in go-ethereum stack.

Acceptance Criteria

CHT is updated automatically before block synchronisation starts.

Notes

I may be wrong but, as I remember, go-ethereum were going to make automatic CHT updates for les protocol.
There's a relevant issue about growing chaindata just to keep in mind: #277

@status-open-bounty
Copy link

status-open-bounty commented Nov 2, 2017

Current balance: 0.000000 ETH
Tokens: SNT: 0.00
Contract address: 0x26332f5633a640821e42c5695dc1870df82d1708
QR Code
Network: Mainnet
To claim this bounty sign up at https://openbounty.status.im and make sure to update your Ethereum address in My Payment Details so that the bounty is correctly allocated.
To fund it, send ETH or ERC20/ERC223 tokens to the contract address.

@pacamara
Copy link

Please note: per status team request, revised PR against upstream go-ethereum now addresses this issue instead: ethereum/go-ethereum#15673

@andytudhope
Copy link

Closing here as @pacamara has been rewarded out of band and will be working with Divan and Zsolt on LES2 for the rest of what is required.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants