scriptnetwork / node-network-guide

This repository is deprecated and is no longer maintained.

Please go to:

https://github.com/scriptnetwork/script-4

node-network-guide's Issues

Upstream disconnection

The way the fork was performed back in 2021 present one major problem. Since the technique used was basically copy and paste into a brand new separate repository:

The commit log is lost, losing analysis capacity
The source commit hash in the source repository was not documented in the first commit, losing the possibility of manually jump to the theta repo and explore the changeset history
The first commit does not match any upstream commit because instead of committing a verbatim copy of the code, the first commit includes unaccounted changes made 'offline' before the code is back again in control. This adds difficulty to the task of finding the original hash.
Most critical: The inability to frequently re-sync the upstream repository keeping our fork up to date with patches. Hence our L1 software is frozen since 2021 and Theta is +3 years ahead. 

The task consist on recreating the fork using the following procedure:

*Fork https://github.com/thetatoken/theta-protocol-ledger into https://github.com/scriptnetwork/script-protocol-ledger
*Investigate and determine the commit hash our repo is based on in the upstream theta rep (basehash)
*checkout basehash and create a new branch 'script' departing from upstream:basehash
*first commit with changes made offline (diff upstream:basehash first commit of Node-Network-guide:master:#1)
*cherry pick rest of commits
*at this point TAG a the branch "script_2021"
*SYNC Theta from master branch. Rebase branch script with master:HEAD, resolve possible conflicts

The New Script blockchain will be allocated in the repository: https://github.com/scriptnetwork/script-protocol-ledger

branches:

*master ← upstream theta codebase
*script <- our codebase