Top block doesn't match SDK-TESTNET Explorer

PoW Mining AE
1

Hi Just wondering if this is normal, or I am looking at the wrong match up.

I run:

curl http://localhost:3013/v2/blocks/top
{“key_block”:{“beneficiary”:“ak_2TPTDkrfr7sh5BDVrWJVvHqeRHXQtvQPonV6AiRoi1QWmn9s7j”,“hash”:“kh_pL3zFyKVg1LxDTksbNSXS2b4C7zEumXMKxt12FaKv3u8LbDd3”,“height”:6651,“miner”:“ak_2F5kMJETn819SvxKS82eQtj4FfhgYzEV9rtF3DoSX2b6VTkYFq”,“nonce”:18280143364420247425,“pow”:[123,660,843,1403,1753,2158,2948,3918,4348,5850,6382,7167,7512,8464,8813,11722,11955,14222,14671,15470,16098,16953,17329,17439,17589,17799,19519,21068,21267,22074,22793,24074,24159,24369,25894,27786,28051,28554,29515,29662,30093,32489],“prev_hash”:“kh_Ruhg9RnRMG4Jpe6PWw1Yh7Zh5QHzBjha9UERJ2tCZNNzw7XVK”,“prev_key_hash”:“kh_Ruhg9RnRMG4Jpe6PWw1Yh7Zh5QHzBjha9UERJ2tCZNNzw7XVK”,“state_hash”:“bs_BQKvXF1EdHPCUdwn8bbAhSdHX4AShsLYvDARLgLBYc6Df8N75”,“target”:536986490,“time”:1543319880950,“version”:28}}

the height eventually seems to be a few numbers ahead of æternity Explorer

I dont have any peers set in my config. I assumed it defaults to SDK-TESTNET ?

thanks for any info !

2

Hey @ryanprice,

Our dev team is currently looking into that.
We’ll keep you updated.

Best,
Albena

3

@ryanprice Epoch node joins UAT not SDK-testnet by default.

2 Likes
4

ahh ok that explains it. So adding

peers:

  • aenode://pp_HdcpgTX2C1aZ5sjGGysFEuup67K9XiFsWqSPJs4RahEcSyF7X@sync.sdk-testnet.aepps.com:3015

to my config will get me on the same network as the explorer… ok looks like its working… the height matches now lol.

Does this network reward blocks with tokens ? I see the wallets have zero balances.

2 Likes
5

Yes it does. But that network has faucets running that you may use to top up.

2 Likes
6

For the ROMA release. I grabbed the new 1.0.0 epoch. Do I need to set any peers in the config to sync to the ROMA Mainnet ? right now with no peers entry, it does not look like it’s syncing to the correct network

7

Hey @ryanprice,
Your question has been answered in this thread.

Best,
Albena

1 Like
8

Just make sure you don’t have an old DB around, and that your epoch.yaml points to the correct network_id - ae_mainnet (and not ae_uat if you have previously been connected to the testnet).

1 Like