{"action":"opened","issue":{"url":"https://api.github.com/repos/trust-net/go-trust-net/issues/3","repository_url":"https://api.github.com/repos/trust-net/go-trust-net","labels_url":"https://api.github.com/repos/trust-net/go-trust-net/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/trust-net/go-trust-net/issues/3/comments","events_url":"https://api.github.com/repos/trust-net/go-trust-net/issues/3/events","html_url":"https://github.com/trust-net/go-trust-net/issues/3","id":299608247,"number":3,"title":"POC - Iteration 2 - Persist Blockchain Across Node Shutdown/Restart","user":{"login":"gnulib","id":7948960,"avatar_url":"https://avatars1.githubusercontent.com/u/7948960?v=4","gravatar_id":"","url":"https://api.github.com/users/gnulib","html_url":"https://github.com/gnulib","followers_url":"https://api.github.com/users/gnulib/followers","following_url":"https://api.github.com/users/gnulib/following{/other_user}","gists_url":"https://api.github.com/users/gnulib/gists{/gist_id}","starred_url":"https://api.github.com/users/gnulib/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gnulib/subscriptions","organizations_url":"https://api.github.com/users/gnulib/orgs","repos_url":"https://api.github.com/users/gnulib/repos","events_url":"https://api.github.com/users/gnulib/events{/privacy}","received_events_url":"https://api.github.com/users/gnulib/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-02-23T06:04:07Z","updated_at":"2018-02-23T06:04:07Z","closed_at":null,"author_association":"COLLABORATOR","body":"### Requirements\r\nAs an administrator for a full node of the global network counter blockchain implemented in #2,\r\n\r\nI want to be able to shutdown/restart my blockchain node, and the node should be able to sync correctly from its pre-shutdown state without requiring full sync,\r\n\r\nSo that I can continue to participate in the real world blockchain network that is continuously updating the network counter, without needing to maintain an always-on node.\r\n### Acceptance Criteria\r\nImplementation must accomplish following:\r\n* a mechanism is provided to define and initialize node from configuration data\r\n* the node should be able to persist blockchain data across shutdown/restart\r\n* the node should be able to sync with multiple peers concurrently\r\n* sync protocol should be able to handle reset/rewind if a fork is detected for the syncing node\r\n* a [GHOST-like](https://github.com/ethereum/wiki/wiki/Design-Rationale#uncle-incentivization) total weight/difficulty algorithm is implemented to negotiate correct sync and fork resolution\r\n\r\nThe implementation does not cover the following:\r\n* mining challenge and reward are not required\r\n* all nodes are assumed to be honest, and hence every new block message is trusted\r\n"}}
{"actor":{"display_login":"gnulib"}}