Elastos Node for Ubuntu v1.1 is now live.
This is the safety release for the node runner used by Council members, BPoS operators, and ELA node operators on Elastos.
The script is the main Ubuntu tool used to install, run, restart, monitor, and maintain Elastos nodes. It decides which chains start, how services bind to the network, how operators see status, and how node processes are managed.
For anyone who has ever set up a Council node, BPoS node, or full node on ELA, this is the same runner used to start and manage the node.
v1.1 keeps the existing node layout, keystores, chain data, and familiar commands intact. It can be adopted on a live Council or BPoS node without moving the keystore or changing the chain data.
What is new in v1.1
Elastos Node for Ubuntu v1.1 is focused on making node operation safer, clearer, and easier to manage.
- EVM sidechains are no longer exposed by default: Sidechain RPC and WebSocket services now listen locally unless the operator chooses otherwise. If public RPC access is needed, it must be turned on clearly with a valid address.
- Mining no longer needs an unlocked hot account: The local geth account is no longer kept unlocked while mining chains are running. Council and BPoS nodes can still produce blocks because block signing uses the PBFT keystore. This fixes an exploitable issue that caused some Council members to lose mining rewards.
- Sensitive RPC features are removed from reach: Functions tied to personal accounts, database access, admin actions, and miner controls are no longer exposed through the reachable RPC surface.
- Rewards are easier to control: Mining rewards can still go to the local hot account for compatibility, but v1.1 now warns the operator when mining starts. Operators can set a dedicated reward address once, have it checked, and apply it across the relevant chains in one step.
- Firewall and hardening are built in: The firewall setup opens only the ports needed for the selected node type and checks the SSH port first, so operators do not lock themselves out of a remote server. The hardening tool blocks exposed EVM RPC, WebSocket, and oracle ports at the firewall level, then tells the operator which services should be restarted when they are ready.
- Node status is easier to read: A new summary view shows each chain, its state, height, peers, and health in one table. Health checks now return proper success or failure results for alerts and monitoring. Logs are easier to follow, and status data can be shown as JSON for dashboards.
- Restarts are safer: A normal restart will not restart ELA unless the operator clearly forces it. This helps avoid accidentally taking a Council or BPoS node out of consensus during routine maintenance.
- Reliability fixes are included: Reward checks now wait until ELA is fully synced. Dead sidechain RPC values show as unavailable instead of zero. Failed starts show the latest logs. The known missing-sponsors-file issue around block 1.8 million is handled at start, and stop commands now have a time limit so a stuck daemon does not hang forever.
- Installation and migration are safer: The installer checks the downloaded script against its checksum and runs a syntax check before installing. Existing nodes can be adopted without changing keystores, chain data, or binaries. Migration creates a rollback snapshot, blocks public RPC ports first, and gives the operator a one-by-one restart plan for sidechains. ELA is never restarted by the migration flow.
- ECO cleanup is now available: Since ECO is decommissioned, it has been removed from profiles and bulk commands. If old ECO data is still present, the purge flow backs up the ECO keystore first and requires typed confirmation before removing anything.
- Read-only monitoring is included: Operators can let their node report health to a dashboard once a minute over HTTPS. It does not open an inbound port and does not share an RPC password. The node proves its role using its on-chain consensus public key, which can be checked against public Council and BPoS data.
v1.1 keeps the same directory layout, keystores, chain data, binaries, and existing commands. It is meant to be adopted on live Council, BPoS, and full nodes with minimal disruption, while making the runner safer and easier to understand.
How to upgrade
Elastos Node for Ubuntu v1.1 can be adopted on existing Council, BPoS, and full nodes without changing keystores, chain data, or binaries.
- For an existing node, update first:
./node/node.sh update_script
- Migrate from older version to the latest, no interruption:
./node/node.sh migrate –apply
- After upgrading, check the node:
./node/node.sh summary
./node/node.sh health
Full command reference: https://github.com/elastos/Elastos.Node/blob/master/docs/commands.md
