没有命令行钱包吗, 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.
Quote from: longdi on July 19, 2026, 07:56:31 (
https://bitcointalk.org/index.php?topic=5588797.msg66956441#msg66956441)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.
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.1Binary:
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.
Network Status Update
Hello everyone,
During the first hours after the Mainnet launch, I identified an issue that prevents the network from progressing beyond the genesis state.
The problem is related to the mining initialization path and does not affect the integrity of the genesis block, the Chain ID, or the consensus parameters that were released in v1.0.2
As a precaution, I have temporarily paused the launch while I investigate and correct the issue.
At this stage:
* The Mainnet genesis remains unchanged.
* The released source code remains available for review.
* No premine or privileged issuance has occurred.
* No blockchain history needs to be rewritten because no valid blocks have been mined beyond genesis.
I prefer to delay the public launch rather than release a network with a known consensus issue.
A corrected release will be published as soon as the root cause has been identified, tested, and independently verified.
Thank you for your patience and for everyone who has already started reviewing the code and testing the network.
— DOM Protocol Development Team
