[ANN] CivicNet (CIVIC) - CivicLight PoW | Mainnet is LIVE! | CPU-Only

[Sergick2023]

How start mine SOLO? On http://103.180.165.99:8080 pool?

[CivicLight]

Wallet not sync on Windows(

Thanks for reporting this - you're right, and it's on us for not making this clearer.

CivicNet doesn't have DNS seed nodes set up yet (the infrastructure that lets a wallet auto-discover peers on the network). Without that, a fresh wallet install has no way to find anyone to connect to unless you point it at a known node manually.

Fix - add our node manually:

1. Open File Explorer, type this in the address bar: %APPDATA%\CivicNet
2. Create a file there called civicnet.conf (if it doesn't already exist)
3. Open it in Notepad and add this line:

Code:

addnode=103.180.165.99

4. Save, close, and restart civicnet-qt.exe

That points your wallet directly at our node, and it should sync from there.

We're planning to bake a default seed node into the software itself so this becomes automatic for everyone in a future release - for now this manual step is needed. Sorry for the friction, and thanks for flagging it.

[CivicLight]

How start mine SOLO? On http://103.180.165.99:8080 pool?

Great question! Solo mining through our pool is supported - you use the same stratum connection, but with a special password flag to indicate solo mode.

Command:

Code:

cpuminer -a civiclight -o stratum+tcp://103.180.165.99:3032 -u YOUR_CIVC_ADDRESS -p solo

Replace YOUR_CIVC_ADDRESS with your own CivicNet wallet address (starts with civc1q...).

Key points about solo mining through the pool:
- You compete against the whole network, not shared rounds with other pool miners
- If YOU find a block, you get the full reward (minus a small 0.5% solo fee) - it's not split with other miners
- Since you're going solo, you need to find a full block yourself (not just pool-difficulty shares), so it can take much longer between rewards depending on your hashrate vs current network difficulty
- Stats for solo miners show up separately on the pool website

If you'd rather run your own node instead of connecting through our pool at all, that's also possible - see the civicnet-node release on GitHub and connect your miner directly to your own node's RPC instead.

Let us know if you run into any issues getting it connected.

[yunta]

Hello, I followed the tutorial and have successfully deployed the miner. The backend shows that everything is running normally, but I don’t know where I can check my earnings. I also cannot find any information on http://103.180.165.99:3001/search.

Additionally, my Windows wallet cannot synchronize, and I have already added the .conf configuration file as you mentioned above, but the issue still remains.

windows wallet cannot syn,

-07-12 14:02:32] 3965 Accepted 3965 S0 R0 B1, 2.910 sec (234ms)
[2026-07-12 14:02:35] New Work: Block 807, Tx 0, Netdiff 4.8469, Job 118
                      Diff: Net 4.8469, Stratum 0.1, Target 0.1
                      TTF @ 66.41 Mh/s: Block 5m13s, Share 6s
                      Net hash rate (est) 149.77 Mh/s
[2026-07-12 14:02:44] 3966 Submitted Diff 0.1459, Block 807, Job 118
[2026-07-12 14:02:44] 3966 Accepted 3966 S0 R0 B1, 11.905 sec (231ms)
[2026-07-12 14:02:53] 3967 Submitted Diff 0.17625, Block 807, Job 118
[2026-07-12 14:02:54] 3967 Accepted 3967 S0 R0 B1, 9.466 sec (234ms)
[2026-07-12 14:02:54] 3968 Submitted Diff 0.19893, Block 807, Job 118
[2026-07-12 14:02:55] 3968 Accepted 3968 S0 R0 B1, 0.948 sec (233ms)
[2026-07-12 14:02:58] 3969 Submitted Diff 0.26788, Block 807, Job 118
[2026-07-12 14:02:58] 3970 Submitted Diff 1.8199, Block 807, Job 118
[2026-07-12 14:02:58] 3969 Accepted 3969 S0 R0 B1, 3.588 sec (234ms)
[2026-07-12 14:02:58] 3970 Accepted 3970 S0 R0 B1, 0.036 sec (430ms)
[2026-07-12 14:03:01] 3971 Submitted Diff 0.10339, Block 807, Job 118
[2026-07-12 14:03:01] 3971 Accepted 3971 S0 R0 B1, 3.053 sec (238ms)
[2026-07-12 14:03:20] 3972 Submitted Diff 0.13441, Block 807, Job 118
[2026-07-12 14:03:20] 3972 Accepted 3972 S0 R0 B1, 18.592 sec (234ms)
[2026-07-12 14:03:25] 3973 Submitted Diff 0.89923, Block 807, Job 118
[2026-07-12 14:03:26] 3973 Accepted 3973 S0 R0 B1, 5.745 sec (230ms)
[2026-07-12 14:03:30] New Work: Block 807, Tx 0, Netdiff 4.8469, Job 119
                      Diff: Net 4.8469, Stratum 0.1, Target 0.1
                      TTF @ 66.39 Mh/s: Block 5m13s, Share 6s
                      Net hash rate (est) 124.66 Mh/s

[CivicLight]

Hello, I followed the tutorial and have successfully deployed the miner. The backend shows that everything is running normally, but I don’t know where I can check my earnings. I also cannot find any information on http://103.180.165.99:3001/search.

Additionally, my Windows wallet cannot synchronize, and I have already added the .conf configuration file as you mentioned above, but the issue still remains.

windows wallet cannot syn,

-07-12 14:02:32] 3965 Accepted 3965 S0 R0 B1, 2.910 sec (234ms)
[2026-07-12 14:02:35] New Work: Block 807, Tx 0, Netdiff 4.8469, Job 118
                      Diff: Net 4.8469, Stratum 0.1, Target 0.1
                      TTF @ 66.41 Mh/s: Block 5m13s, Share 6s
                      Net hash rate (est) 149.77 Mh/s
[2026-07-12 14:02:44] 3966 Submitted Diff 0.1459, Block 807, Job 118
[2026-07-12 14:02:44] 3966 Accepted 3966 S0 R0 B1, 11.905 sec (231ms)
[2026-07-12 14:02:53] 3967 Submitted Diff 0.17625, Block 807, Job 118
[2026-07-12 14:02:54] 3967 Accepted 3967 S0 R0 B1, 9.466 sec (234ms)
[2026-07-12 14:02:54] 3968 Submitted Diff 0.19893, Block 807, Job 118
[2026-07-12 14:02:55] 3968 Accepted 3968 S0 R0 B1, 0.948 sec (233ms)
[2026-07-12 14:02:58] 3969 Submitted Diff 0.26788, Block 807, Job 118
[2026-07-12 14:02:58] 3970 Submitted Diff 1.8199, Block 807, Job 118
[2026-07-12 14:02:58] 3969 Accepted 3969 S0 R0 B1, 3.588 sec (234ms)
[2026-07-12 14:02:58] 3970 Accepted 3970 S0 R0 B1, 0.036 sec (430ms)
[2026-07-12 14:03:01] 3971 Submitted Diff 0.10339, Block 807, Job 118
[2026-07-12 14:03:01] 3971 Accepted 3971 S0 R0 B1, 3.053 sec (238ms)
[2026-07-12 14:03:20] 3972 Submitted Diff 0.13441, Block 807, Job 118
[2026-07-12 14:03:20] 3972 Accepted 3972 S0 R0 B1, 18.592 sec (234ms)
[2026-07-12 14:03:25] 3973 Submitted Diff 0.89923, Block 807, Job 118
[2026-07-12 14:03:26] 3973 Accepted 3973 S0 R0 B1, 5.745 sec (230ms)
[2026-07-12 14:03:30] New Work: Block 807, Tx 0, Netdiff 4.8469, Job 119
                      Diff: Net 4.8469, Stratum 0.1, Target 0.1
                      TTF @ 66.39 Mh/s: Block 5m13s, Share 6s
                      Net hash rate (est) 124.66 Mh/s

Thanks for the detailed report! Let's go through each point:

1. Where to check your mining earnings:
Go to: http://103.180.165.99:8080/workers/YOUR_CIVC_ADDRESS
(replace YOUR_CIVC_ADDRESS with your actual payout address)

That page shows your hashrate, shares, and balance/payout history specifically for your address.

Also worth flagging directly: we've found and are actively fixing some deeper bugs in the automatic payout system today. Your shares are being tracked correctly, but the actual automated payment step has had a few issues we're working through right now. Nothing is lost - if there's any delay, we'll make sure it gets resolved, including manual payouts if needed while we finish stabilizing the automatic system.

2. /search not working:
That's expected - /search only works through the search box on the block explorer's homepage (http://103.180.165.99:3001), not as a direct URL. It's a form submission (POST), not a bookmarkable link. Just go to the homepage and type your address/txid into the search box there.

3. Windows wallet not syncing:
From your miner log, your connection to our pool is clearly working fine (shares accepted, blocks visible), so this seems specific to the Qt wallet's P2P connection, not a general network/firewall problem on your end. A few things to check:
- Confirm the config file is at exactly: %APPDATA%\CivicNet\civicnet.conf (not civicnet.conf.txt - Windows sometimes hides the real extension)
- Confirm you fully closed and reopened civicnet-qt.exe after saving the file (not just minimized)
- Try adding this line as well:

Code:

connect=103.180.165.99

(forces a direct connection attempt, more aggressive than addnode)
- Check if Windows Firewall or antivirus is specifically blocking civicnet-qt.exe's outbound connections

If it still doesn't work after that, let us know: what does the wallet's Debug Window > Peers tab show (any peers listed at all)?

Appreciate your patience as we iron out these early-stage issues - and thanks for actually mining and testing things, that's exactly the kind of feedback that helps.

[yunta]

还是不行，下面是日志：

2026-07-12T07:10:33Z CivicNet Core version v0.21.5.5-8e2655e56-dirty (release build)
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -connect set -> setting -dnsseed=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -connect set -> setting -listen=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -upnp=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -discover=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
2026-07-12T07:10:33Z Qt 5.9.8 (static), plugin=windows (static)
2026-07-12T07:10:33Z System: Windows 10 (10.0), x86_64-little_endian-llp64
2026-07-12T07:10:33Z Screen: \\.\DISPLAY1 1920x1080, pixel ratio=1.0
2026-07-12T07:10:33Z Validating signatures for all blocks.
2026-07-12T07:10:33Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000000000000000000000000
2026-07-12T07:10:33Z Using the 'shani(1way,2way)' SHA256 implementation
2026-07-12T07:10:33Z Using RdSeed as additional entropy source
2026-07-12T07:10:33Z Using RdRand as an additional entropy source
2026-07-12T07:10:33Z GUI: "registerShutdownBlockReason: Successfully registered: CivicNet Core 尚未安全退出..."
2026-07-12T07:10:33Z Default data directory C:\Users\hpp\AppData\Roaming\CivicNet
2026-07-12T07:10:33Z Using data directory C:\Users\hpp\AppData\Roaming\CivicNet
2026-07-12T07:10:33Z Config file: C:\Users\hpp\AppData\Roaming\CivicNet\civicnet.conf
2026-07-12T07:10:33Z Config file arg: connect="103.180.165.99"
2026-07-12T07:10:33Z Setting file arg: wallet = ["yunta"]
2026-07-12T07:10:33Z Using at most 125 automatic connections (2048 file descriptors available)
2026-07-12T07:10:33Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2026-07-12T07:10:33Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2026-07-12T07:10:33Z Script verification uses 7 additional threads
2026-07-12T07:10:33Z scheduler thread start
2026-07-12T07:10:33Z Using wallet directory C:\Users\hpp\AppData\Roaming\CivicNet\wallets
2026-07-12T07:10:33Z init message: 正在检测钱包的完整性...
2026-07-12T07:10:33Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2026-07-12T07:10:33Z Using wallet C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\wallet.dat
2026-07-12T07:10:33Z BerkeleyEnvironment::Open: LogDir=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\database ErrorFile=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\db.log
2026-07-12T07:10:33Z init message: 正在加载黑名单...
2026-07-12T07:10:33Z SetNetworkActive: true
2026-07-12T07:10:33Z Using /16 prefix for IP bucketing
2026-07-12T07:10:33Z Cache configuration:
2026-07-12T07:10:33Z * Using 2.0 MiB for block index database
2026-07-12T07:10:33Z * Using 56.0 MiB for basic block filter index database
2026-07-12T07:10:33Z * Using 8.0 MiB for chain state database
2026-07-12T07:10:33Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2026-07-12T07:10:33Z init message: 正在加载区块索引...
2026-07-12T07:10:33Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2026-07-12T07:10:33Z Opening LevelDB in C:\Users\hpp\AppData\Roaming\CivicNet\blocks\index
2026-07-12T07:10:33Z Opened LevelDB successfully
2026-07-12T07:10:33Z Using obfuscation key for C:\Users\hpp\AppData\Roaming\CivicNet\blocks\index: 0000000000000000
2026-07-12T07:10:33Z LoadBlockIndexDB: last block file = 0
2026-07-12T07:10:33Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=299, heights=0...0, time=2026-07-07...2026-07-07)
2026-07-12T07:10:33Z Checking all blk files are present...
2026-07-12T07:10:33Z Opening LevelDB in C:\Users\hpp\AppData\Roaming\CivicNet\chainstate
2026-07-12T07:10:33Z Opened LevelDB successfully
2026-07-12T07:10:33Z Using obfuscation key for C:\Users\hpp\AppData\Roaming\CivicNet\chainstate: 9ea89a69de4f0a5c
2026-07-12T07:10:33Z Loaded best chain: hashBestChain=d241c02c655f2c8192df11147f51f9d5027807ff0aea0255b3dc149b68bd4c13 height=0 date=2026-07-07T17:00:00Z progress=1.000000
2026-07-12T07:10:33Z init message: 回退区块...
2026-07-12T07:10:33Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2026-07-12T07:10:33Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2026-07-12T07:10:33Z init message: 正在验证区块...
2026-07-12T07:10:33Z  block index              23ms
2026-07-12T07:10:33Z Opening LevelDB in C:\Users\hpp\AppData\Roaming\CivicNet\indexes\blockfilter\basic\db
2026-07-12T07:10:33Z Opened LevelDB successfully
2026-07-12T07:10:33Z Using obfuscation key for C:\Users\hpp\AppData\Roaming\CivicNet\indexes\blockfilter\basic\db: 0000000000000000
2026-07-12T07:10:33Z basic block filter index thread start
2026-07-12T07:10:33Z basic block filter index is enabled at height 0
2026-07-12T07:10:33Z basic block filter index thread exit
2026-07-12T07:10:33Z init message: 正在加载钱包...
2026-07-12T07:10:33Z BerkeleyEnvironment::Open: LogDir=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\database ErrorFile=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\db.log
2026-07-12T07:10:33Z [yunta] Wallet File Version = 210000
2026-07-12T07:10:33Z [yunta] Keys: 3004 plaintext, 0 encrypted, 3004 w/ metadata, 3004 total. Unknown wallet records: 0
2026-07-12T07:10:33Z [yunta] Wallet completed loading in              28ms
2026-07-12T07:10:33Z [yunta] setKeyPool.size() = 2000
2026-07-12T07:10:33Z [yunta] mapWallet.size() = 0
2026-07-12T07:10:33Z [yunta] m_address_book.size() = 1
2026-07-12T07:10:33Z block tree size = 1
2026-07-12T07:10:33Z nBestHeight = 0
2026-07-12T07:10:33Z init message: 正在加载P2P地址...
2026-07-12T07:10:33Z loadblk thread start
2026-07-12T07:10:33Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2026-07-12T07:10:33Z Loaded 81 addresses from peers.dat  0ms
2026-07-12T07:10:33Z init message: 正在启动网络线程...
2026-07-12T07:10:33Z loadblk thread exit
2026-07-12T07:10:33Z DNS seeding disabled
2026-07-12T07:10:33Z net thread start
2026-07-12T07:10:33Z addcon thread start
2026-07-12T07:10:33Z init message: 加载完成
2026-07-12T07:10:33Z opencon thread start
2026-07-12T07:10:33Z msghand thread start
2026-07-12T07:10:33Z GUI: Platform customization: "windows"

[CivicLight]

还是不行，下面是日志：

2026-07-12T07:10:33Z CivicNet Core version v0.21.5.5-8e2655e56-dirty (release build)
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -connect set -> setting -dnsseed=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -connect set -> setting -listen=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -upnp=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -discover=0
2026-07-12T07:10:33Z InitParameterInteraction: parameter interaction: -listen=0 -> setting -listenonion=0
2026-07-12T07:10:33Z Qt 5.9.8 (static), plugin=windows (static)
2026-07-12T07:10:33Z System: Windows 10 (10.0), x86_64-little_endian-llp64
2026-07-12T07:10:33Z Screen: \\.\DISPLAY1 1920x1080, pixel ratio=1.0
2026-07-12T07:10:33Z Validating signatures for all blocks.
2026-07-12T07:10:33Z Setting nMinimumChainWork=0000000000000000000000000000000000000000000000000000000000000000
2026-07-12T07:10:33Z Using the 'shani(1way,2way)' SHA256 implementation
2026-07-12T07:10:33Z Using RdSeed as additional entropy source
2026-07-12T07:10:33Z Using RdRand as an additional entropy source
2026-07-12T07:10:33Z GUI: "registerShutdownBlockReason: Successfully registered: CivicNet Core 尚未安全退出..."
2026-07-12T07:10:33Z Default data directory C:\Users\hpp\AppData\Roaming\CivicNet
2026-07-12T07:10:33Z Using data directory C:\Users\hpp\AppData\Roaming\CivicNet
2026-07-12T07:10:33Z Config file: C:\Users\hpp\AppData\Roaming\CivicNet\civicnet.conf
2026-07-12T07:10:33Z Config file arg: connect="103.180.165.99"
2026-07-12T07:10:33Z Setting file arg: wallet = ["yunta"]
2026-07-12T07:10:33Z Using at most 125 automatic connections (2048 file descriptors available)
2026-07-12T07:10:33Z Using 16 MiB out of 32/2 requested for signature cache, able to store 524288 elements
2026-07-12T07:10:33Z Using 16 MiB out of 32/2 requested for script execution cache, able to store 524288 elements
2026-07-12T07:10:33Z Script verification uses 7 additional threads
2026-07-12T07:10:33Z scheduler thread start
2026-07-12T07:10:33Z Using wallet directory C:\Users\hpp\AppData\Roaming\CivicNet\wallets
2026-07-12T07:10:33Z init message: 正在检测钱包的完整性...
2026-07-12T07:10:33Z Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2026-07-12T07:10:33Z Using wallet C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\wallet.dat
2026-07-12T07:10:33Z BerkeleyEnvironment::Open: LogDir=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\database ErrorFile=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\db.log
2026-07-12T07:10:33Z init message: 正在加载黑名单...
2026-07-12T07:10:33Z SetNetworkActive: true
2026-07-12T07:10:33Z Using /16 prefix for IP bucketing
2026-07-12T07:10:33Z Cache configuration:
2026-07-12T07:10:33Z * Using 2.0 MiB for block index database
2026-07-12T07:10:33Z * Using 56.0 MiB for basic block filter index database
2026-07-12T07:10:33Z * Using 8.0 MiB for chain state database
2026-07-12T07:10:33Z * Using 384.0 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
2026-07-12T07:10:33Z init message: 正在加载区块索引...
2026-07-12T07:10:33Z Switching active chainstate to Chainstate [ibd] @ height -1 (null)
2026-07-12T07:10:33Z Opening LevelDB in C:\Users\hpp\AppData\Roaming\CivicNet\blocks\index
2026-07-12T07:10:33Z Opened LevelDB successfully
2026-07-12T07:10:33Z Using obfuscation key for C:\Users\hpp\AppData\Roaming\CivicNet\blocks\index: 0000000000000000
2026-07-12T07:10:33Z LoadBlockIndexDB: last block file = 0
2026-07-12T07:10:33Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=299, heights=0...0, time=2026-07-07...2026-07-07)
2026-07-12T07:10:33Z Checking all blk files are present...
2026-07-12T07:10:33Z Opening LevelDB in C:\Users\hpp\AppData\Roaming\CivicNet\chainstate
2026-07-12T07:10:33Z Opened LevelDB successfully
2026-07-12T07:10:33Z Using obfuscation key for C:\Users\hpp\AppData\Roaming\CivicNet\chainstate: 9ea89a69de4f0a5c
2026-07-12T07:10:33Z Loaded best chain: hashBestChain=d241c02c655f2c8192df11147f51f9d5027807ff0aea0255b3dc149b68bd4c13 height=0 date=2026-07-07T17:00:00Z progress=1.000000
2026-07-12T07:10:33Z init message: 回退区块...
2026-07-12T07:10:33Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) started
2026-07-12T07:10:33Z FlushStateToDisk: write coins cache to disk (0 coins, 0kB) completed (0.00s)
2026-07-12T07:10:33Z init message: 正在验证区块...
2026-07-12T07:10:33Z  block index              23ms
2026-07-12T07:10:33Z Opening LevelDB in C:\Users\hpp\AppData\Roaming\CivicNet\indexes\blockfilter\basic\db
2026-07-12T07:10:33Z Opened LevelDB successfully
2026-07-12T07:10:33Z Using obfuscation key for C:\Users\hpp\AppData\Roaming\CivicNet\indexes\blockfilter\basic\db: 0000000000000000
2026-07-12T07:10:33Z basic block filter index thread start
2026-07-12T07:10:33Z basic block filter index is enabled at height 0
2026-07-12T07:10:33Z basic block filter index thread exit
2026-07-12T07:10:33Z init message: 正在加载钱包...
2026-07-12T07:10:33Z BerkeleyEnvironment::Open: LogDir=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\database ErrorFile=C:\Users\hpp\AppData\Roaming\CivicNet\wallets\yunta\db.log
2026-07-12T07:10:33Z [yunta] Wallet File Version = 210000
2026-07-12T07:10:33Z [yunta] Keys: 3004 plaintext, 0 encrypted, 3004 w/ metadata, 3004 total. Unknown wallet records: 0
2026-07-12T07:10:33Z [yunta] Wallet completed loading in              28ms
2026-07-12T07:10:33Z [yunta] setKeyPool.size() = 2000
2026-07-12T07:10:33Z [yunta] mapWallet.size() = 0
2026-07-12T07:10:33Z [yunta] m_address_book.size() = 1
2026-07-12T07:10:33Z block tree size = 1
2026-07-12T07:10:33Z nBestHeight = 0
2026-07-12T07:10:33Z init message: 正在加载P2P地址...
2026-07-12T07:10:33Z loadblk thread start
2026-07-12T07:10:33Z Imported mempool transactions from disk: 0 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
2026-07-12T07:10:33Z Loaded 81 addresses from peers.dat  0ms
2026-07-12T07:10:33Z init message: 正在启动网络线程...
2026-07-12T07:10:33Z loadblk thread exit
2026-07-12T07:10:33Z DNS seeding disabled
2026-07-12T07:10:33Z net thread start
2026-07-12T07:10:33Z addcon thread start
2026-07-12T07:10:33Z init message: 加载完成
2026-07-12T07:10:33Z opencon thread start
2026-07-12T07:10:33Z msghand thread start
2026-07-12T07:10:33Z GUI: Platform customization: "windows"

Thanks for sharing the log - here's what I can see:

Your wallet loaded correctly (wallet "yunta", 3004 keys, no errors there), and it's using the connect= method which is the more aggressive/direct connection option - good choice.

However, your blockchain height is still at 0 (nBestHeight = 0), meaning no blocks have synced yet. The log you shared cuts off right as it's starting network threads, so it doesn't show whether the connection to our node actually succeeded or failed.

Can you let it run for another minute or two, then check:
1. In the wallet: Window > Peers - do you see any peer listed at all (even 0/1 connections)?
2. If zero peers after a few minutes, this points to a network/firewall issue blocking the outbound connection specifically.

One thing worth checking: you have 81 addresses loaded from peers.dat, which seems unusually high for such a new network - if that peers.dat file was inherited from another coin/previous install, it might be worth deleting it (close the wallet first, then delete peers.dat in your data folder) so it starts fresh and only tries your configured connect= node.

Let us know what the Peers tab shows after a couple minutes.

[yunta]

日志还是一样，日志到这里就不动了：

2026-07-12T07:29:36Z init message: 加载完成
2026-07-12T07:29:36Z opencon thread start
2026-07-12T07:29:36Z msghand thread start
2026-07-12T07:29:36Z GUI: Platform customization: "windows"

界面看不到peer节点

[CivicLight]

日志还是一样，日志到这里就不动了：

2026-07-12T07:29:36Z init message: 加载完成
2026-07-12T07:29:36Z opencon thread start
2026-07-12T07:29:36Z msghand thread start
2026-07-12T07:29:36Z GUI: Platform customization: "windows"

界面看不到peer节点

Thanks for confirming - zero peers means the connect= attempt isn't successfully reaching our node at all (not just slow, genuinely failing).

Let's isolate whether this is a network-level block. Can you try this from Windows PowerShell:

Code:

Test-NetConnection -ComputerName 103.180.165.99 -Port 9333

If it says "TcpTestSucceeded: False" - that confirms something on your network path (local firewall, router, ISP, or regional network restrictions) is blocking the connection before it even reaches us, which is outside what the wallet config can fix on its own.

If it says "TcpTestSucceeded: True" but the wallet still shows 0 peers, then the issue is likely wallet-specific and we'd dig further there.

A few other things to try in the meantime:
- Temporarily disable Windows Defender Firewall (just to test) and see if peers appear
- Try connecting from a different network if possible (mobile hotspot, VPN, etc.) to rule out local/regional restrictions
- Double check there's no typo or extra space in the connect= line in civicnet.conf

Let us know what the Test-NetConnection result shows - that'll tell us where to focus next.

[yunta]

PS C:\WINDOWS\system32> Test-NetConnection -ComputerName 103.180.165.99 -Port 9333


ComputerName     : 103.180.165.99
RemoteAddress    : 103.180.165.99
RemotePort       : 9333
InterfaceAlias   : WLAN
SourceAddress    : 192.168.3.3
TcpTestSucceeded : True

[sdnz]

How can we see no peers on the explorer?
There must be some problems in the core ported from Lightcoin. quick check shows pchMessageStart setting is missing in github code.
Is there anyone on the main network?
You can prove the chain is running correctly by running another node or tell us another peer node.

[Sergick2023]

Not working - NOTHING... 26 hours mine - 0 payout Wallet not sync, mine without block etc Stop mining!
 

[CivicLight]

How can we see no peers on the explorer?
There must be some problems in the core ported from Lightcoin. quick check shows pchMessageStart setting is missing in github code.
Is there anyone on the main network?
You can prove the chain is running correctly by running another node or tell us another peer node.

Good catch, and you're right - after checking, pchMessageStart is indeed never explicitly assigned a value in chainparams.cpp's CMainParams constructor. This is a genuine gap.

Important context: this isn't a quick one-line patch. pchMessageStart is embedded in every P2P network message - changing it would make old and new node binaries unable to talk to each other, effectively requiring a coordinated network-wide upgrade (every node, not just ours). We're not going to rush that given we have active miners on the network right now - it needs a proper announced upgrade window, not a silent patch.

To answer your "is anyone actually running this" question directly - here's a live peer you can add right now to verify:

Code:

addnode=103.180.165.99

We'll plan a proper coordinated fix + upgrade announcement for this. Appreciate the technical scrutiny.

[sdnz]

Important context: this isn't a quick one-line patch. pchMessageStart is embedded in every P2P network message - changing it would make old and new node binaries unable to talk to each other,

You pointed it exactly.
Do you see any peer on your side? Because the pchMessageStart is not set I guess it's random value when the node starts, so if you run another node it cannot join with the same binary. That's what happens to everyone trying to join your node, 103.180.165.99.
So I asked did you have another node on the network.

Also note that miners are talking to your mining pool not to your p2p node I believe.
So logically 103.180.165.99 is a sole node on the chain and no one else can join.

Worth to republish the core sooner otherwise will see the sad end.