Releases: Ether1Project/Ethoprotocol
V2.1.0 Phoenix - Update
V2.1.0 Phoenix - Update
- Major Fixes
- Removed old bootnodes, and updated with new ones.
- +++
Full Changelog: V2.0.0...V2.1.0
V2.0.0 Phoenix
New major fork update to remove old bridge contracts ( ERC-20 Bridge ). Update will also burn obsolete walletfunds to compensate and create new escrow wallet to unwrap funds of all wrapped Etho holders from the previous Ethereum Contract. Also changes nodereward to a new wallet address for new node system. New funds will go into multisig wallets controlled by team/council members. Dev fund also added for future development.
Hard-fork is planned for block 8750000
V1.6.0 New Horizon
Major fix in this fork is to adjust minimum difficulty down to stabilize block times around the 12 second mark.
Treasury addresses is now a multisig wallet controlled by team/council members.
Hard-fork is planned for block 8300000
V1.5.3 - Atlas Diff/Sync Hot Fix
Update node.go
V1.5.2 - Atlas Sync Patch
Update version.go
V1.5.1 - Atlas
Atlas v1.5.1
Block reward update/patch for planned hard-fork at block 8150000
Brings codebase current up to Go-Ethereum v1.10.8 (Hades Gamma) which patches a vulnerability in the EVM (CVE-2021-39137).
V1.5.0 - Atlas
Atlas hard-fork planned for 8000000 block.
Hard-fork to include Constantinople, Petersburg, Istanbul & Muir Glacier HFs from upstream
Required update for all nodes prior to hard-fork block.
V1.4.5 - Kepler (Update)
V1.4.5 - Kepler (Update)
- Fixes "open files" race condition.
- Efficiency upgrades for redundant data sharing
V1.4.2 - Kepler (Hot Fix)
V1.4.2 - Kepler (Hot Fix)
- Addresses non ethoFS enabled nodes syncing bug
v1.4.1 - Kepler
V1.4.1 - Kepler
1)Full merge of ethoFS and ETHO Daemon
2)Upstream go-ethereum updates (V1.9.22)
Kepler Updates (ethoFS enabled nodes)
Initializing, configuring and running an ethoFS node with the Kepler update is a three step process.
All three node types are available to initialize, config and run via the CLI utilizing the --ethofs flag to designate node type. Explore the Ether-1 Node Dashboard (https://nodes.ether1.org) for details and requirements for deploying each ethofs enabled node type.
Node Types:
Service Node (sn) Masternode (mn) Gateway Node (gn)
Node Initialization, Configuration and Run Commands:
Step 1: Run ethoFS Initialization
$ geth --ethofs=mn --ethofsInit console
Step 2: Run ethoFS Configuration
$ geth --ethofs=mn --ethofsConfig console
Step 3: Start ethoFS Enabled Node
$ geth --ethofs=mn console
All Ether-1 standard daemon functionality remains the same. Exchanges, mining pools and other nodes that do not require ethoFS to be enabled can still run the node with standard operating flags by not utilizing the new --ethofs, --ethofsInit & --ethofsConfig flags.
Directions To Connect Node To Network Stats Page:
Extract the zip file for your operating system
Open a terminal/cmd prompt into the folder where you extracted the zip file
On Linux you might need to chmod 755 geth before you can execute it
./geth --ethstats "YOUR_NODE_NAME:ether1stats@stats.ether1.org" console
If you have trouble syncing see