The only xOneRS release is v0.1.0, published on 2026-11-12. Since then hundreds of pull requests have merged on main, most of them on 2026-11-14 and 2026-11-15. No new release has been cut, so moving a node to main means a build from source. This page lists what an operator notices after such a move: defaults that changed, flags that are new but off, and data formats that change on disk. Each line links to the post with the details. For the move itself, see upgrade and rollback.
Which defaults changed?
| Area | v0.1.0 | main after 2026-11-15 |
Details |
|---|---|---|---|
/readyz head age |
60 s, fixed | 180 s, --metrics.readyz.maxheadage |
health checks |
eth_getLogs limits |
5,000 blocks and 10,000 logs, fixed | same defaults, now --rpc.rangelimit and --rpc.logs.maxresults |
eth_getLogs limits |
| Account recreation in one block | block refused, node stops | imported, old storage wiped | ADR-011 |
| Peer arrival log | none | Block received lines with --debug.logslowblock |
receive and slow-block fields |
Which new features stay off until I turn them on?
- History windows and backfill:
--history.*(history retention). - Native TLS and per-key method lists:
--http.tls.*,--rpc.jwtsecret,--rpc.acl(TLS and ACLs). - One port for HTTP and WebSocket: equal addresses and ports (one port).
- Node allowlist:
--permissions.nodes(allowlist). - DNS discovery:
--discovery.dns(DNS discovery). - OTLP traces:
--tracing.otlp(OTLP). - Kafka export:
--kafka.brokers(chain events). - New namespaces:
trace,ots,perm, and manydebug_methods, served only when listed (debug, explorers).
What changes on disk?
- Receipts. New receipts are written in a compact form without blooms; old receipts still read, and RPC answers are byte-identical (smaller datadirs).
- History segments. Files also rotate at
--snapshot.chunk-bytes(2 GB). Closed chunks are compressed only when you runxone db compact-history. - State window.
--history.stateis written into the datadir on first use and reused when the flag is omitted. - A datadir written by
mainmay not be readable by v0.1.0. Keep a backup of the v0.1.0 datadir if you might roll back.
What is new for day-to-day work?
xone dbgained inspection, check and repair commands (the xone db toolkit).xone setupplans a first follower, in English, Hindi or Marathi (xone setup); answer its network prompt yourself until issue #1164 is fixed.measure-node.shrecords before-and-after numbers (measure-node).
Frequently asked questions
Is there a newer xOneRS release than v0.1.0?
Not when we checked on 2026-11-15. Everything newer is on main and needs a build from source.
Will my v0.1.0 config still work on main?
New features are off until you set them, but we did not check every v0.1.0 flag against main. Run xone checkconfig with your config before you restart; it validates the config without starting the node.
Can I go back to v0.1.0 after running main?
Plan for no. New on-disk formats, such as the compact receipts, may not be readable by v0.1.0. Keep a backup of the datadir from before the upgrade.
Sources
- xOneRS releases (v0.1.0, 2026-11-12) and the posts linked above, each with its own pull requests.
This article describes the source and evidence at its review date. Check the linked repository for current implementation and qualification status.
Explore the engineering evidenceEdit this page on GitHub opens the Markdown source (content/blog/xone-v010-to-main-changes/index.md). GitHub may ask you to sign in. Report a correction opens a prefilled GitHub issue for this page.