A List of Seed Nodes for the Roma Release!

vlad.chain · November 28, 2018, 12:49am

Hello everyone!

We hoped you noticed the new Roma release It includes a list of seed nodes that you can use in order to join the æternity network. Here it is. You can chose a random one.

-“aenode://pp_5mmzrsoPh9owYMfKhZSkUihufDTB6TuayD173Ng464ukVm9xU@35.178.61.73:3015”
- “aenode://pp_2KWhoNRdythXAmgCbM6QxFo95WM4XXGq2pjcbKitXFpUHnPQc3@35.177.192.219:3015”
- “aenode://pp_2L8A5vSjnkLtfFNpJNgP9HbmGLD7ZAGFxoof47N8L4yyLAyyMi@18.136.37.63:3015”
- “aenode://pp_2gPZjuPnJnTVEbrB9Qgv7f4MdhM4Jh6PD22mB2iBA1g7FRvHTk@52.220.198.72:3015”
- “aenode://pp_frAKABjDnM3QZCUygbkaFvbd8yhv6xdufazDFLgJRc4fnGy3s@52.56.252.75:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_2mwr9ikcyUDUWTeTQqdu8WJeQs845nYPPqjafjcGcRWUx4p85P@3.17.30.101:3015”
- “aenode://pp_FLpSUrKwgBAu5uVRnB2iWKtwGAHZckxvtCbjVPeeCA3j33t3J@52.56.66.124:3015”
- “aenode://pp_2CAJwwmM2ZVBHYFB6na1M17roQNuRi98k6WPFcoBMfUXvsezVU@13.58.177.66:3015”
- “aenode://pp_vxK2ikV9djG8MXmDnYYs338ETEsaUPweZrc2S54L3scxBfncU@13.250.190.66:3015”
- “aenode://pp_28si4QQ4YkjpZdo5cER7nxQodT2cMv7uNLBzUmaTkfU7EVHFH9@34.218.57.207:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_H4ooofyixJE6weqsgzKMKTdjZwEWb2BMSWqdFqbwZjssvtUEZ@18.217.69.24:3015”
- “aenode://pp_2qPAV7cYcHBK8MDo7neB2p1ow5Bmu1o56EUtnVv19ytuZ3pTtX@3.0.217.255:3015”
- “aenode://pp_2mWh671xYJRdzXFmJGy4M1Vhsy8y4ECadmoAcTYMw6pEGW5VCz@3.8.105.183:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_2eu9njAqnd2s9nfSHNCHMbw96dajSATz1rgT6PokH2Lsa531Sp@3.17.15.122:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_21DNLkjdBuoN7EajkK3ePfRMHbyMkhcuW5rJYBQsXNPDtu3v9n@35.166.231.86:3015”
- “aenode://pp_RKVZjm7UKPLGvyKWqVZN1pXN6CTCxfmYz2HkNL2xiAhLVd2ho@52.11.110.179:3015”
- “aenode://pp_AnPnGst52qzh7ii8KUzHHFwFGiXxyF2TALhds9LPguAxJJqKd@54.214.159.45:3015”
- “aenode://pp_2u68ui39npbsjDVAy7Q1vBYFxfgaV3AWbXL8UB38TuKsgehHF1@52.88.74.110:3015”
- “aenode://pp_BPYCajukjRmJkPQ3nY4TyjPZ969aCMDqWZkZ3EDXkxJbvN2cH@35.177.165.232:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_2GBVGpHdZzmxA5k92RiY39RpjVNgECQRNfeFQ6z7ruJ5PPn5hH@35.177.212.38:3015”
- “aenode://pp_Xv6KMd1612pLWznW37s2fx79QMHGbLZuXTyFvuXRrHSNb8s5o@18.218.172.119:3015”
- “aenode://pp_XpZVMtsbg39Rm69aBP3m2Q245ght8MNUGN1omBr7xJmd4goxR@52.40.117.141:3015”
- “aenode://pp_21fv4vH2GbmL35gb6tWhwFQjMnprftuGQ4Xx97VehSM8eQdB7U@34.211.251.83:3015”
- “aenode://pp_sGegC48UrvDA7cvvUU3GPTze9wNUnnK1P4q46mL5jAFddNrbD@13.250.144.60:3015”
- “aenode://pp_io8yyDuTfCUmLkLShXvvkZEJFnfC6oVMnrS2tUygLkbbnnJxd@35.176.217.240:3015”
- “aenode://pp_4cHNMu9xgXE1DvDrqdaUypr1yzmwhHSUrTyT8o9u8954bYCau@18.130.106.60:3015”
- “aenode://pp_cVrCJWsg2vyWnRerEpLyB6ut6A8AA1MchQWAheRFNWpRWHXHJ@35.163.118.175:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_2aAEHdDFNbqH23HdZqu6HMtQmaE6rvLQuDZqEEWndkNbWunyuY@18.216.167.138:3015”
- “aenode://pp_2R7a7JHzfZQU5Ta7DJnFiqRr7ayCcAVakqYzJ2mvZj5k4ms5mV@3.17.15.239:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_8nn6ypcwkaXxJfPGq7DCpBpf9FNfmkXPvGCjJFnLzvwjhCMEH@52.26.157.37:3015”
- “aenode://[email protected]:3015”
- “aenode://pp_QkNjQbJL3Ab1TVG5GesKuZTixBdXEutUtxG677mVu9D4mMNRr@13.228.202.140:3015”
- “aenode://pp_2jtDgarjfr7S5NBZpBBx3fgn3wdtLb24UmiYGtVCGzF6x7Bytb@52.77.168.79:3015”

sammy007 · November 28, 2018, 2:28am

lol and where to put this list?

xiahui135 · November 28, 2018, 2:50am

yes. so what is this for? How can check the explorer?

vlad.chain · November 28, 2018, 3:05am

This list is part of the release. It is pasted here for convenience. The explorer needs to be ported to the Roma release.

Best,
Vlad

sammy007 · November 28, 2018, 4:29am

Could you configure https://explorer.aepps.com to show mainnet?

Kryztoval · November 28, 2018, 11:01am

I don’t think they can right now, as it is not working with release just yet.

But the team is working hard, I am currently trying out the develop branch and it is coming out nice.

dimitar.chain · November 28, 2018, 2:45pm

Update for the explorer is comming but it will take a few days probably

ryanprice · November 28, 2018, 3:48pm

If you run 1.0.0 epoch as a node. To sync, do we need to define anything for peers in the config ? if left bank should the node sync to the Roma mainnet ?

thanks

hanssv.chain · November 28, 2018, 4:27pm

No, that is correct. The default seed nodes for 1.0.0 corresponds to the list in this post!

ryanprice · November 28, 2018, 5:49pm

awesome. ok I am running the sync. but when I:

curl http://localhost:3013/v2/blocks/top
{“key_block”:{“beneficiary”:“ak_11111111111111111111111111111111273Yts”,“hash”:“kh_pbtwgLrNu23k9PA6XCZnUbtsvEFeQGgavY4FS2do3QP8kcp2z”,“height”:0,“miner”:“ak_11111111111111111111111111111111273Yts”,“prev_hash”:“kh_2CipHmrBcC5LrmnggBrAGuxAf2fPDrAt79asKnadME4nyPRzBL”,“prev_key_hash”:“kh_11111111111111111111111111111111273Yts”,“state_hash”:“bs_QDcwEF8e2DeetViw6ET65Nj1HfPrQh1uRkxtAsaGLntRGXpg7”,“target”:522133279,“time”:0,“version”:1}}

this looks incorrect to me ? shouldnt that match the top block from a seed like http://35.178.61.73:3013/v2/blocks/top returns. height is like 295 when I posted this

hanssv.chain · November 28, 2018, 5:53pm

It looks like you have not managed to connect to the network, that is the genesis block. I’d suggest looking in the log-files, especially the log/epoch_sync.log

ryanprice · November 28, 2018, 6:00pm

the log shows stuff like:

<<243,90,61,15,…,207,83,85,117>>}"
2018-11-28 12:57:55.292 [debug] <0.1275.0>@aec_sync:get_next_work_item:339 Get block at height 65
2018-11-28 12:57:55.292 [debug] <0.3274.0>@aec_sync:do_fetch_generation_ext:797 we don’t have the block -fetching ("<<243,90,61,15,…,207,83,85,117>>")
2018-11-28 12:57:55.330 [debug] <0.3274.0>@aec_sync:do_fetch_generation_ext:802 block fetched from “pp_SFA9D5w…ZAbSkDt” ("<<243,90,61,15,…,207,83,85,117>>"); “#block{height=65, root_hash=<<4,29,244,27,…,41,192,204,113>>, prev_hash=<<131,184,198,83,…,250,196,162,69>>}”
2018-11-28 12:57:55.331 [debug] <0.1275.0>@aec_sync:get_next_work_item:339 Get block at height 22

which looks correct ? but the top block curl request should be always showing the height, right ?
so… what is going wrong here… hmmm

hanssv.chain · November 28, 2018, 6:06pm

That part looks good, you are getting blocks from the network. Any errors further down? You should be trying to add them to your chain.

Yes, asking localhost:3013/v2/blocks/top should be the top block of your view of the chain.

ryanprice · November 28, 2018, 6:17pm

No errors in sync… it just keeps going and going… but the top block curl doesn’t change

in epoch.log I have

2018-11-28 13:14:59.347 [debug] <0.2446.4>@aec_tx_pool:do_update_sync_top:482 do_update_sync_top(304,304,<0.1264.0>), LocalTop = 0
2018-11-28 13:14:59.347 [debug] <0.1264.0>@aec_tx_pool:handle_info:309 [15] Msg = {<0.2446.4>,new_gc_height,304}

the folder data/aecore/ only has .genesis in it. Should it have more folders created by now ?

hanssv.chain · November 28, 2018, 6:22pm

Hmm, strange…

Check in log/epoch_sync.log that you really manage to get block 1… Then also check log/epoch_mining.log and look for problems there, it should try to synced_block: ... and possibly indicate if there are issues?

Apart for the DB-folder it should not create any folders.

ryanprice · November 28, 2018, 6:53pm

ok this must be a symptom of the culprit , when I set mining to true I get

2018-11-28 13:51:11.737 [error] <0.12280.10>@aec_conductor:handle_mining_reply:718 Failed to mine block, runtime error; retrying with different nonce (was 7839255539520788826). Error: {execution_failed,{status,127}}

When it is set to false. which is how it was set with all the above messages, i get this in the mining log

2018-11-28 14:17:33.521 [info] <0.13584.26>@aec_conductor:add_synced_block:150 Header failed validation: incorrect_pow

my config is

autostart: false
cuckoo:
miner:
executable: lean30
extra_args: “”
edge_bits: 30

Kryztoval · November 28, 2018, 7:22pm

are you sure you are using the proper configuration, minimum ram requirements, or the proper bits, mean/lean etc?

This almost sounds like a misconfiguration of your base yaml

ryanprice · November 28, 2018, 7:25pm

sure was
changed to

autostart: false
cuckoo:
miner:
executable: lean29-generic
extra_args: “”
edge_bits: 29

and its working.

now to get CUDA going

thanks for your help