Repository navigation
Synchronization Troubleshooting
Alex edited this page Sep 29, 2026
·
2 revisions
Verified against: Core
v2.0.2, Qwertycoin mainnet, 2026-09-29.
Diagnose before changing data:
- Check
qwertycoind --versionand the configured network. - Compare local height with multiple healthy peers/explorer observations.
- Check incoming/outgoing peer counts and the system clock.
- Check disk, filesystem errors, memory pressure and OOM events.
- Check firewall/NAT reachability for P2P
8196. - Read logs around the first error, not only later retries.
Common causes are a legacy data directory, blocked seed/peer connectivity, insufficient disk, an uncleanly copied LMDB, wrong permissions or a clock far from network time.
Do not delete wallet files, seeds or EPoSe keystores. Do not import historical CSV checkpoints to suppress a symptom. A normal full resynchronization replaces only blockchain data. EPoSe additionally requires endpoint, identity and lifecycle checks.
Qwertycoin documentation · Verified against pinned revisions · Report a documentation issue
Start
Project
Wallets
Nodes and builds
- Run a Full Node
- Configuration and Ports
- Docker
- Linux Service Operation
- Upgrade and Recovery
- Synchronization Troubleshooting
- Build Overview
EPoSE
- Overview
- Service Node Quickstart
- Configuration and Identity
- Admission and Lifecycle
- Epochs and Qualification
- Rewards
- Monitoring and Diagnostics
- FAQ and Troubleshooting
APIs
- API Overview
- Daemon JSON-RPC
- Daemon HTTP and Binary RPC
- Wallet RPC Setup
- Wallet RPC Reference
- EPoSE RPC Reference
- Errors and Compatibility
- Integration Examples
- Complete Route Inventory
Mining and ecosystem
- RandomX Mining
- Solo Mining
- Pool Mining
- Pool Operator Integration
- Explorer and Web Wallet Hosting
- Exchanges and Compatibility
Contributing