[ANN][DOM] DOM Protocol — RandomX PoW | Mimblewimble | No Premine | Mainnet Live

[sorenplanck]

Official v1.0.0 release and source download:

https://github.com/sorenplanck/dom-protocol/releases/tag/v1.0.0



Official source repository:

https://github.com/sorenplanck/dom-protocol



Release version: v1.0.0



DOM Core commit:

Code:

6c58b0383c095384cd0150cabf074aa00fb57b17

SHA-256 checksums:



Checksums for compiled Linux and Windows binaries will be published on the official GitHub v1.0.0 release page together with the release assets.



Until those binaries are attached, the v1.0.0 Git tag and the official GitHub source archives are the authoritative distribution.






Public Mainnet Node



The initial DOM Mainnet node is online on a public VPS.

Code:

Network:        MAINNET

Status:         ONLINE

Current height: 0

Mining:         Disabled

Service:        dom-mainnet.service



DNS seed:

seed1.dom-protocol.org



Public IP:

168.100.9.70



P2P endpoint:

seed1.dom-protocol.org:33369



Direct IP fallback:

168.100.9.70:33369



P2P protocol:

TCP



RPC:

Private / not publicly exposed

Mainnet identity:

Code:

Chain ID:

f9831fadabc8a4234beab35fbb6327e84581645f33e9f75ed2ea78e8bcf1165b



Genesis hash:

182e10af28e7ec072f462e6044f580dc9dd8c866cb78dfc293bbfaee4e9325ce

The bootstrap node does not mine. Its purpose is to provide public peer discovery, block relay, transaction relay and initial synchronization.



Block height remains at zero until the first valid proof-of-work block is mined by a network participant.






Run a DOM Mainnet Node



Clone and build the exact v1.0.0 release:

Code:

git clone https://github.com/sorenplanck/dom-protocol.git

cd dom-protocol

git checkout v1.0.0

cargo build --release

Start a validating and relay-only Mainnet node:

Code:

DOM_NETWORK=mainnet \

DOM_SEED_PEERS="seed1.dom-protocol.org:33369" \

DOM_MINE=false \

DOM_DATA_DIR="$HOME/.dom-mainnet" \

DOM_P2P_LISTEN_ADDR="0.0.0.0:33369" \

DOM_LOG=info \

./target/release/dom-node

Direct-IP bootstrap alternative:

Code:

DOM_NETWORK=mainnet \

DOM_SEED_PEERS="168.100.9.70:33369" \

DOM_MINE=false \

DOM_DATA_DIR="$HOME/.dom-mainnet" \

DOM_P2P_LISTEN_ADDR="0.0.0.0:33369" \

DOM_LOG=info \

./target/release/dom-node

Operators must allow inbound TCP traffic on port:

Code:

33369/TCP

RPC and administrative interfaces should remain bound to loopback or protected private interfaces.






VPS Service Management



The initial public node runs under systemd:

Code:

sudo systemctl enable --now dom-mainnet.service

sudo systemctl status dom-mainnet.service --no-pager

Follow the Mainnet logs:

Code:

sudo journalctl -u dom-mainnet.service -f

Restart the node:

Code:

sudo systemctl restart dom-mainnet.service

Verify the public P2P listener:

Code:

sudo ss -lntp | grep 33369

Expected listener:

Code:

0.0.0.0:33369

Solo CPU Mining



DOM uses RandomX proof of work and supports integrated CPU mining.



Before mining, create and securely back up a DOM wallet. The miner wallet must be stored locally and protected with a strong password.



Example Mainnet mining command:

Code:

read -rsp "Miner wallet password: " DOM_WALLET_PASSWORD

echo

export DOM_WALLET_PASSWORD



DOM_NETWORK=mainnet \

DOM_SEED_PEERS="seed1.dom-protocol.org:33369" \

DOM_MINE=true \

DOM_MINER_THREADS="$(nproc)" \

DOM_WALLET_PATH="$HOME/.dom/miner.wallet" \

DOM_DATA_DIR="$HOME/.dom-mainnet-miner" \

DOM_P2P_LISTEN_ADDR="0.0.0.0:33369" \

DOM_LOG=info \

./target/release/dom-node



unset DOM_WALLET_PASSWORD

Direct-IP bootstrap alternative:

Code:

DOM_NETWORK=mainnet \

DOM_SEED_PEERS="168.100.9.70:33369" \

DOM_MINE=true \

DOM_MINER_THREADS="$(nproc)" \

DOM_WALLET_PATH="$HOME/.dom/miner.wallet" \

DOM_DATA_DIR="$HOME/.dom-mainnet-miner" \

DOM_P2P_LISTEN_ADDR="0.0.0.0:33369" \

DOM_LOG=info \

./target/release/dom-node

The miner must have access to a valid local wallet file:

Code:

$HOME/.dom/miner.wallet

Never publish the wallet password or recovery phrase.



Never include the wallet password in public scripts, screenshots, configuration files or shell history.






Official DOM Wallet



Official DOM Wallet V3



Official Linux and Windows wallet releases are published in the dedicated DOM Wallet V3 repository:



https://github.com/sorenplanck/dom-wallet-v3/releases



Official wallet repository:



https://github.com/sorenplanck/dom-wallet-v3



Download DOM Wallet V3 only from the official GitHub Releases page.



Before installing:

• Verify the release version and attached checksums.
• Back up the recovery phrase offline.
• Never share the wallet password or recovery phrase.
• Never download installers from unofficial mirrors.

The public Mainnet explorer is being prepared.



The official explorer URL will be posted in this announcement thread and on the official project website after deployment.



The explorer is informational only. Consensus is determined independently by validating DOM nodes.






Official Website



https://dom-protocol.org






Technical Documentation



Mainnet documentation:



https://github.com/sorenplanck/dom-protocol/tree/release/mainnet/docs



Mainnet source branch:



https://github.com/sorenplanck/dom-protocol/tree/release/mainnet



Mainnet v1.0.0 release:



https://github.com/sorenplanck/dom-protocol/releases/tag/v1.0.0






Official Community and Support



This Bitcointalk announcement thread is the initial official public discussion channel.



Technical issues and reproducible bug reports:



https://github.com/sorenplanck/dom-protocol/issues



Additional official channels will be announced only through:

• This Bitcointalk announcement thread
• The official GitHub repository
• The official project website

Any Telegram, Discord, X/Twitter or social-media account that is not linked from those official sources must be treated as unofficial.

DOM Mainnet is online.



Public seed: seed1.dom-protocol.org:33369



No premine. No ICO. No founder allocation.



Not a store of value. A means of exchange.

[yunta]

没有命令行钱包吗, solo必须本地钱包这个好难搞，服务器一般不支持GUI。或者有矿池没。

[longdi]

Subject: One seed node for an entire mainnet — and it's down. Seriously?

So let me get this straight: the entire DOM mainnet hangs off exactly one seed node (seed1.dom-protocol.org = 168.100.9.70), and that node has been dead for hours. TCP still connects (that's just your DDoS proxy answering), then... nothing. Noise handshake times out after 10 seconds, every single time, from every machine we've tried. We were synced to height 195 earlier — then the network just vanished.

A whole "mainnet" that stops existing when one box goes down. Impressive engineering.

And it gets better: your anti-DDoS layer silently drops all datacenter/cloud IPs. We tested from clean VPSes in New York and Singapore — not even a TCP SYN-ACK on :33369 or :443. So even when your one seed comes back from its nap, nobody can actually run infrastructure on this network: no pools, no explorers, no public nodes. You firewalled out the exact people who could stop your single point of failure from being a single point of failure. Grin shipped with multiple redundant seeds back in 2019 — it's 2026 and DOM launched with one, hidden behind a hostile firewall.

The README says "Not a store of value. A means of exchange." Right now it's neither — it's a whitepaper with a disconnected phone number.

Since I'd actually like this network to live:

1. Is seed1 down, or did you change the filtering? Any ETA?
2. Spin up 2–3 more seeds on different providers/ASNs. This is table stakes for a mainnet.
3. Give clean datacenter IPs a way in — whitelist or a documented policy. We have a public node + mining pool built from your canonical v1.0.0 tag (6c58b038…) sitting ready to deploy, which would give your network exactly the extra peers it desperately needs. We can be part of the fix the moment we can handshake.

Your move.

[sorenplanck]

没有命令行钱包吗, solo必须本地钱包这个好难搞，服务器一般不支持GUI。或者有矿池没。

没有命令行钱包吗, solo必须本地钱包这个好难搞，服务器一般不支持GUI。或者有矿池没。

Thanks for the comment.

Yes, DOM currently runs through the command line. Solo mining is done through the node binary, and headless server deployment is expected. A GUI wallet can exist separately, but the protocol itself is designed to run without requiring a desktop environment.

We will publish clearer miner and node setup instructions so operators can bootstrap more easily on VPS and server environments.

[sorenplanck]

Subject: One seed node for an entire mainnet — and it's down. Seriously?

So let me get this straight: the entire DOM mainnet hangs off exactly one seed node (seed1.dom-protocol.org = 168.100.9.70), and that node has been dead for hours. TCP still connects (that's just your DDoS proxy answering), then... nothing. Noise handshake times out after 10 seconds, every single time, from every machine we've tried. We were synced to height 195 earlier — then the network just vanished.

A whole "mainnet" that stops existing when one box goes down. Impressive engineering.

And it gets better: your anti-DDoS layer silently drops all datacenter/cloud IPs. We tested from clean VPSes in New York and Singapore — not even a TCP SYN-ACK on :33369 or :443. So even when your one seed comes back from its nap, nobody can actually run infrastructure on this network: no pools, no explorers, no public nodes. You firewalled out the exact people who could stop your single point of failure from being a single point of failure. Grin shipped with multiple redundant seeds back in 2019 — it's 2026 and DOM launched with one, hidden behind a hostile firewall.

The README says "Not a store of value. A means of exchange." Right now it's neither — it's a whitepaper with a disconnected phone number.

Since I'd actually like this network to live:

1. Is seed1 down, or did you change the filtering? Any ETA?
2. Spin up 2–3 more seeds on different providers/ASNs. This is table stakes for a mainnet.
3. Give clean datacenter IPs a way in — whitelist or a documented policy. We have a public node + mining pool built from your canonical v1.0.0 tag (6c58b038…) sitting ready to deploy, which would give your network exactly the extra peers it desperately needs. We can be part of the fix the moment we can handshake.

Your move.

Thank you for taking the time to test the network, document your observations, and report the issues in detail.

Your feedback was useful.

After investigating the behavior, we confirmed that the main issue was not a consensus failure, inflation bug, or chain-identity problem. It was an operational defect in the miner: under prolonged mining conditions, the miner could remain stuck hashing an outdated block template with an obsolete timestamp and target instead of refreshing the candidate properly over time.

That defect has now been fixed.

To be explicit, the fix did not change:

- genesis
- Chain ID
- ASERT formula or parameters
- reward schedule
- validation rules
- consensus rules
- economic policy

So this was not a hard fork or a consensus rewrite. It was a miner-side template refresh correction.

Your point about bootstrap resiliency was also fair. Seed redundancy and broader public entry-point availability are important for a live network, and improving that operational layer is a valid priority. A mainnet should be easier for independent operators, public nodes, miners, and infrastructure providers to reach reliably.

The network is advancing again, and the correction was deployed without changing consensus.

Thank you again for the scrutiny and for raising the issue constructively. External technical review, even when critical, is valuable — especially at this stage.

[sorenplanck]

Thank you for taking the time to test the network, document your observations, and report the issue in detail.

Your feedback was useful.

After investigation, we confirmed that the problem was not a consensus failure, not an inflation issue, and not a Chain ID, genesis, or ASERT rule problem. The root cause was an operational defect in the miner: under prolonged mining conditions, the miner could continue hashing an outdated block template with an obsolete timestamp and target instead of refreshing the candidate over time.

That issue has now been fixed.

To be explicit, this correction did not change:

- genesis
- Chain ID
- ASERT formula or parameters
- target block spacing
- block rewards
- transaction rules
- validation rules
- economic policy
- historical block validity

So this was not a hard fork and not a consensus change. It was a miner-side template refresh fix.

The network is advancing again, and the correction was deployed without altering consensus.

Additional bootstrap resilience is also being prioritized. Seed redundancy and broader public entry-point availability are valid operational concerns for a live network, and that layer will continue to be improved.

--------------------------------------------------
MINER UPDATE
--------------------------------------------------

All miners should update and restart their node process.

Older miner binaries may still become stuck on an outdated block template and should be considered obsolete for mining purposes.

Release:
https://github.com/sorenplanck/dom-protocol/releases/tag/v0.1.1

Binary:
dom-node-linux-x86_64

Platform:
Linux x86_64

SHA-256:
223b23270bf6a0305f1d37505c8bfd730dd50d99f4d51f2e41726cdf792cee60

Verify before installing:

sha256sum dom-node-linux-x86_64

The result must exactly match:

223b23270bf6a0305f1d37505c8bfd730dd50d99f4d51f2e41726cdf792cee60

--------------------------------------------------
INSTALLATION
--------------------------------------------------

1. Download the new Linux x86_64 binary from the release page.
2. Verify the SHA-256 checksum.
3. Stop the currently running DOM miner/node process.
4. Back up the existing binary.
5. Replace it with the new binary.
6. Restart the node with the same configuration/environment previously used.
7. Do not delete wallet data or blockchain data.

This update is required for miners.

Existing non-mining validating nodes remain compatible and can continue accepting new blocks.

Thank you again for the scrutiny and for raising the issue constructively. External technical review, especially at this stage, is useful and appreciated.