etclabscore / multi-geth-fork

GNU Lesser General Public License v3.0
3 stars 8 forks source link

Feat/mordor bootnodes #110

Closed meowsbits closed 4 years ago

meowsbits commented 4 years ago

There have been reported in chats some issues with connectivity for ETC Mordor chain bootnodes.

This includes all bootnodes listed here https://github.com/eth-classic/mordor/blob/master/static-nodes.json as well as the consistent peers my mining client keeps.

Maybe we'll want to rebase and merge this set to master rather than have it on top of all this development; has no dependencies and could go straight to master w/o conflict.

Note still however that this list still seems functionally sparse, with only two nodes responding to ping:

$ cat params/bootnodes_mordor.go |grep -E 'enode' | grep -v Mordor | sed 's-"--g' | sed 's-\t--g'| sed 's/,.*//g' | while read -r line; do echo "$line"; ./build/bin/devp2p discv4 ping "$line" 2>/dev/null;done
enode://03b133f731049e3f7be827339c3759be92778c05e54a1847d178c0fdb56fa168aa1e7e61fc77791a7afdd0328a00318f73c01212eb3f3bbe919f5ce8f5b4a314@192.227.105.4:32000
enode://06fdbeb591d26f53b2e7250025fe955ca013431ded930920cf1e3cd1f0c920e9a5e727949d209bc25a07288327b525279b11c5551315c50ff0db483e69fc159b@34.218.225.178:32000
enode://1813e90a0afdd7c1e4892c5376960e3577a9e6c5a4f86fa405a405c7421a4a1608248d77cc90333842f13d8954d82113dec480cfb76b4fef8cb475157cf4d5f2@10.28.224.3:30000
enode://2b69a3926f36a7748c9021c34050be5e0b64346225e477fe7377070f6289bd363b2be73a06010fd516e6ea3ee90778dd0399bc007bb1281923a79374f842675a@51.15.116.226:30303
enode://621e28e529146fd501709194885f50540c494f1a2985d1fb4ec8769226b5cb0b0d1a11545926077821474c2767cdd87888ead8a2509a2c9069dd5584e4b1c3b8@10.28.223.8:30000
enode://a59e33ccd2b3e52d578f1fbd70c6f9babda2650f0760d6ff3b37742fdcdfdb3defba5d56d315b40c46b70198c7621e63ffa3f987389c7118634b0fefbbdfa7fd@51.15.116.226:30303
enode://f840b007500f50c98ea6f9c9e56dabf4690bbbbb7036d43682c531204341aff8315013547e5bee54117eb22bd3603585ae6bf713d9fa710659533fcab65d5b84@35.238.101.58:30303
enode://5a1399e6ba3268721dd7656530cd81230dbeb950570c6e3ec2a45effc50c032f66633c5eaaa1a49c51ba1849db37a7bef6e402779ad12dc9943f117e058d7760@34.69.121.227:30303
enode://2592745efd35b4be443b8ee25fd2099de132e037951f9f6d3e8805e0a78f213537f71264b973f1a83a57372f57bbe6acac8d6ae678f39393221c045ccbe3b18c@51.15.116.226:30304
enode://111bd28d5b2c1378d748383fd83ff59572967c317c3063a9f475a26ad3f1517642a164338fb5268d4e32ea1cc48e663bd627dec572f1d201c7198518e5a506b1@88.99.216.30:45834
enode://c0afb552bfe932c72598caa245aef82d55c23555622c5ab946d4e49bb0ab694e46086dcff6793a606527f323ef94d0eb499d01ceb26aefb6fa3f8977105d7dd8@157.230.152.87:52138
enode://07fa944c83597d5e935a2abe6194ed40fc7239e86111c971a43537a33d0184d1cd1b3f1291b8dd3bcfaebfbb802de77c843465a00065b39120c338fdd877ca4a@35.238.126.60:51240
enode://023a31a6e1c601e727c681ea6195c83d97dd11a02e2fd4d640453d60eeecb0ceb6f909bd67bc5d16e0d809735479c2eca35c7a4ee60b86b3f882ab52b3fba3e5@84.160.87.178:30504
enode://f50f52b5fe18fd281748905bf5dad5439471f32cc02d99fecf960a983c1f4eba701ffca96afd2f2a68dcf6f97c5d02b566bafce1f361b51717e1a03c1dd9a836@157.230.42.102:30303
node responded to ping (RTT 357.404042ms).
enode://1f378945c9b2eeb292d910f461911fd99520a23beda1bc5c8aea12be09e249f8d92615aa3d4d75c938004db5281dabad4a9cf7a0f07ec7c1fc8e7721addc7c85@34.205.41.164:40218
enode://e2ea472bcbf28c3a5784e34f6ca05cca9c87779885af013eaf3ecc4d0f213e19a20f4170b83945631507b84187368df51dcb15011da4f2c125e9a1e58f258934@84.160.87.178:57584
enode://617a2009783a09085ed0d5d5e7250e2e3c142f73448bf28200284bf4825c5926a80f3e9fb481edf38b89ade2aa0ad5a2f14cc935f3150e36e648eddda674fd70@35.225.5.185:51320
enode://cdd6a68697f46dc000c4b3478a46c03948ea44f7b1dc3b7aad19fccc56e82de0e88816535baac9cc230a72a2f45eff936dae73f1f4bde214d2e84b82d895f43e@84.160.87.178:48848
enode://5a1399e6ba3268721dd7656530cd81230dbeb950570c6e3ec2a45effc50c032f66633c5eaaa1a49c51ba1849db37a7bef6e402779ad12dc9943f117e058d7760@35.225.124.17:39306
enode://f840b007500f50c98ea6f9c9e56dabf4690bbbbb7036d43682c531204341aff8315013547e5bee54117eb22bd3603585ae6bf713d9fa710659533fcab65d5b84@34.69.50.155:42078
enode://0d70715514674189792de4ad294b658c96d0ec40fe517fbe9cb7949d3792f25f82357ec77d1bd8bed6ec719ca0c1d608bb34cc702bf3d4bb4507f7280f835452@154.5.137.161:61410
enode://0fade975875f77237de433cba75893a09264e370d7c4d81a0a269d94ad01d9ebf6056f4d690e82f4fa636f02fee94b0393f6994919bb4cb275b26de352d40517@84.160.87.178:60648
enode://642cf9650dd8869d42525dbf6858012e3b4d64f475e733847ab6f7742341a4397414865d953874e8f5ed91b0e4e1c533dee14ad1d6bb276a5459b2471460ff0d@157.230.152.87:30303
node responded to ping (RTT 379.204995ms).
meowsbits commented 4 years ago

Just FYI this is now a dupe of #112 -- will become obsolete once etclabscore-develop branch receives it's PR-storm merges and can be rebased on master.

meowsbits commented 4 years ago

Closing since #112 has been merged into etclabscore-develop at #82, and etclabscore-develop has merged master.