Has anyone been able to compile Aeon on Arch? I cant get the darn aeond to compile on Arch or run if I compile on Ubuntu....
What error do you get?
Topic: [ANN] AEON [2019-09-27: Upgrade to version 0.13.0.0 ASAP HF@1146200 Oct 25] - page 218. (Read 625864 times)
September 09, 2015, 02:23:56 AM
What error do you get?
September 09, 2015, 02:23:45 AM
2015-Sep-09 08:49:05.440542 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
This error indicates that your blockchain.bin file is corrupt. (The alt-chain supposedly connects to a block that is higher than the length of the main chain in your blockchain.bin file.)
I don't know how this happened and if you want to upload your blockchain.bin somewhere perhaps we can analyze it. However, for the time being I suggest that you either delete blockchain.bin and resync from scratch (reasonably fast with the latest version) or download one of the bootstraps.
September 09, 2015, 02:19:18 AM
Has anyone been able to compile Aeon on Arch? I cant get the darn aeond to compile on Arch or run if I compile on Ubuntu....
September 09, 2015, 02:09:17 AM
print_block 603106
2015-Sep-09 10:05:51.583369 [P2P5][0.0.0.0:0 OUT]Connect failed to 10.1.1.1:1
Code:
block_id:
{
"major_version": 1,
"minor_version": 0,
"timestamp": 1441442773,
"prev_id": "54cfa524f540d4a413e7445f78f2790d686959dbdbd9812e7ec5f3b2d6e05241",
"nonce": 3892320750,
"miner_tx": {
"version": 1,
"unlock_time": 603166,
"vin": [ {
"gen": {
"height": 603106
}
}
],
"vout": [ {
"amount": 1172336155,
"target": {
"key": "19c5e7b5211f10dced2425c16d1598ec1db174396f012aa8a7e50e3924bb5357"
}
}, {
"amount": 80000000000,
"target": {
"key": "3c81a2e44a4b3660e87971008b68e6c3109e4de696cd2c99203d0bf5f8db39bd"
}
}, {
"amount": 300000000000,
"target": {
"key": "6f46df080bf0f95c389b0610fee778d6b53cfdf689a4f86e89be4238ecefccb9"
}
}, {
"amount": 8000000000000,
"target": {
"key": "7f4e9fd56dc78d180ad585a65012c747444e9a2fa77db45baf086d01f840ce15"
}
}, {
"amount": 30000000000000,
"target": {
"key": "861db91f8e3e50d6e2a0fc5113f6ec3fb597c44f7d3e98189522578c329441f4"
}
}
],
"extra": [ 1, 24, 230, 41, 24, 108, 42, 248, 91, 115, 172, 22, 11, 74, 230, 222, 73, 206, 180, 181, 69, 218, 62, 86, 114, 60, 218, 81, 51, 181, 167, 58, 193, 2, 8, 0, 0, 0, 0, 3, 73, 43, 125
],
"signatures": [ ]
},
"tx_hashes": [ ]
}
2015-Sep-09 10:05:51.583369 [P2P5][0.0.0.0:0 OUT]Connect failed to 10.1.1.1:1
September 09, 2015, 01:28:31 AM
Hello guru!
Some shit happend 3-4 days ago. Couldn't sync blockchain since. Block 603107 magic. Log attached. Any ideas? Tnx in advance.
Some shit happend 3-4 days ago. Couldn't sync blockchain since. Block 603107 magic. Log attached. Any ideas? Tnx in advance.
Please start your node with --add-exclusive-node 10.1.1.1:1 and then do a "print_block 603106" and post the results
September 09, 2015, 01:12:55 AM
Hello guru!
Some shit happend 3-4 days ago. Couldn't sync blockchain since. Block 603107 magic. Log attached. Any ideas? Tnx in advance.
Some shit happend 3-4 days ago. Couldn't sync blockchain since. Block 603107 magic. Log attached. Any ideas? Tnx in advance.
Code:
2015-Sep-09 08:47:17.686379 aeon v0.9.4.0()
2015-Sep-09 08:47:17.689379 Module folder: C:\BIT\AEON\aeond.exe
2015-Sep-09 08:47:17.697379 Initializing p2p server...
2015-Sep-09 08:47:17.702380 Binding on 0.0.0.0:11180
2015-Sep-09 08:47:17.736382 Net service binded on 0.0.0.0:11180
2015-Sep-09 08:47:17.742382 Attempting to add IGD port mapping.
2015-Sep-09 08:47:20.789556 UPnP device was found but not recoginzed as IGD.
2015-Sep-09 08:47:20.797557 P2p server initialized OK
2015-Sep-09 08:47:20.802557 Initializing cryptonote protocol...
2015-Sep-09 08:47:20.810557 Cryptonote protocol initialized OK
2015-Sep-09 08:47:20.819558 Initializing core rpc server...
2015-Sep-09 08:47:20.826558 Binding on 127.0.0.1:11181
2015-Sep-09 08:47:20.852560 Core rpc server initialized OK on port: 11181
2015-Sep-09 08:47:20.861560 Initializing core...
2015-Sep-09 08:47:20.866561 Loading blockchain...
2015-Sep-09 08:48:22.500086 CHECKPOINT PASSED FOR HEIGHT 1 <1440a20f078bf3264822234b347f8382606577d73d4e9d3cb7296d73889bc421>
2015-Sep-09 08:48:22.514087 CHECKPOINT PASSED FOR HEIGHT 100 <6dd13aaab16679f49ee6b2b75c7dc99b1fd09ab2282b18cb4b55b73110655742>
2015-Sep-09 08:48:22.567090 CHECKPOINT PASSED FOR HEIGHT 1000
2015-Sep-09 08:48:22.770101 CHECKPOINT PASSED FOR HEIGHT 10000 <1ac1ebd25baf0d6ec593daa3389f1aa7e860ff2cc29f3cf1be586d245b379da4>
2015-Sep-09 08:48:22.899109 CHECKPOINT PASSED FOR HEIGHT 15000 <15567af42afc1ed00538f53b5e3822d421e3ed6372ca79f4ea4e3e3bab709a87>
2015-Sep-09 08:48:27.638380 CHECKPOINT PASSED FOR HEIGHT 175500 <3f7dd748b3b863b04654d87a387f2b65a365f467188971f3192eab2368e64a35>
2015-Sep-09 08:48:33.639723 CHECKPOINT PASSED FOR HEIGHT 450000
2015-Sep-09 08:48:35.440826 CHECKPOINT PASSED FOR HEIGHT 540000 <94e19cf9d5a16ae90f67c321f8376b87da21d6d6c2cb0957b9ab558dca66c1dc>
2015-Sep-09 08:48:36.463884 CHECKPOINT PASSED FOR HEIGHT 592001
2015-Sep-09 08:48:36.471885 Blockchain initialized. last block: 603106, d3.h21.m2.s23 time ago, current difficulty: 28623881
2015-Sep-09 08:48:36.481886 Core initialized OK
2015-Sep-09 08:48:36.484886 Starting core rpc server...
2015-Sep-09 08:48:36.487886 Run net_service loop( 2 threads)...
2015-Sep-09 08:48:36.504887 [SRV_MAIN]Core rpc server started ok
2015-Sep-09 08:48:36.508887 [SRV_MAIN]Starting p2p net loop...
2015-Sep-09 08:48:36.512887 [SRV_MAIN]Run net_service loop( 10 threads)...
2015-Sep-09 08:48:37.513945 [P2P8]
**********************************************************************
The daemon will start synchronizing with the network. It may take up to several hours.
You can set the level of process detailization* through "set_log" command*, where is between 0 (no details) and 4 (very verbose).
Use "help" command to see the list of available commands.
Note: in case you need to interrupt the process, use "exit" command. Otherwise, the current progress won't be saved.
**********************************************************************
2015-Sep-09 08:48:49.303619 [P2P8][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604601 [1494 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:48:51.452742 [P2P8]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:48:51.472743 [P2P8]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:48:51.482744 [P2P8][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:01.467315 [P2P8][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604601 [1494 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:01.969343 [P2P9][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604601 [1494 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:03.592436 [P2P9][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604601 [1494 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:03.604437 [P2P8]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:03.642439 [P2P8]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:03.660440 [P2P8][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:03.840450 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:03.869452 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:03.891453 [P2P1][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:04.683499 [P2P8][99.236.119.155:11180 OUT]Sync data returned unknown top block: 603107 -> 604601 [1494 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:05.367538 [P2P1][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604601 [1494 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:05.440542 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:05.472544 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:05.502545 [P2P1][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:07.530661 [P2P8]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:07.562663 [P2P8]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:07.588665 [P2P8][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:14.999089 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:15.026090 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:15.050091 [P2P1][99.236.119.155:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:52.495233 [P2P1][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:52.971260 [P2P8][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:53.472289 [P2P8][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:54.754362 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:54.760363 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:54.768363 [P2P1][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:54.803365 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:54.814366 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:54.823366 [P2P1][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:56.222446 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:49:56.246448 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:49:56.267449 [P2P1][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:49:59.228618 [P2P5][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:49:59.729647 [P2P1][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:00.220675 [P2P1][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:00.694702 [P2P5][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:01.665758 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:01.688759 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:01.705760 [P2P5][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:01.735762 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:01.753763 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:01.768764 [P2P9][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:02.229790 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:02.236790 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:02.242791 [P2P9][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:02.497805 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:02.504806 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:02.510806 [P2P5][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:25.806139 [P2P5][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:26.298167 [P2P5][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:26.790195 [P2P9][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:27.428231 [P2P9][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:27.679246 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:27.697247 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:27.708247 [P2P9][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:28.332283 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:28.355284 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:28.373285 [P2P9][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:29.255336 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:29.277337 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:29.298338 [P2P9][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:29.553353 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:29.572354 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:29.586355 [P2P5][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:40.459977 [P2P9][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:40.958005 [P2P1][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:41.433032 [P2P7][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:41.913060 [P2P1][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:42.738107 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:42.747107 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:42.754108 [P2P9][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:42.826112 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:42.833112 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:42.839113 [P2P9][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:43.498150 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:43.509151 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:43.534152 [P2P1][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:44.089184 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:44.109185 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:44.135187 [P2P9][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:56.293882 [P2P9][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:56.775910 [P2P1][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:57.269938 [P2P9][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:57.943977 [P2P7][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:50:58.428004 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:58.456006 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:58.476007 [P2P5][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:58.748023 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:58.771024 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:58.792025 [P2P5][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:50:59.139045 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:50:59.162046 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:50:59.181047 [P2P1][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:00.288111 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:00.311112 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:00.336114 [P2P1][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:00.465121 [P2P5][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:00.957149 [P2P5][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:01.619187 [P2P1][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:02.731250 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:02.753252 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:02.774253 [P2P5][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:02.812255 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:02.835256 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:02.856258 [P2P5][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:04.119330 [P2P5][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:04.351343 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:04.367344 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:04.379345 [P2P1][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:04.594357 [P2P5][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:05.282396 [P2P5][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:05.787425 [P2P1][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:06.320456 [P2P7]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:06.335457 [P2P7]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:06.342457 [P2P7][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:06.388460 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:06.396460 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:06.406461 [P2P5][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:08.015553 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:08.022553 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:08.029554 [P2P5][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:08.299569 [P2P1][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:08.888603 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:08.910604 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:08.930605 [P2P5][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:08.956607 [P2P9][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:09.444634 [P2P9][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:09.934663 [P2P5][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:10.121673 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:10.144675 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:10.164676 [P2P9][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:11.604758 [P2P9]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:11.623759 [P2P9]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:11.634760 [P2P9][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:11.635760 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:11.660761 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:11.666762 [P2P1][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:12.086786 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:12.109787 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:12.129788 [P2P1][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:17.544098 [P2P1][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:18.026125 [P2P8][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:18.700164 [P2P8][68.67.95.71:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:19.174191 [P2P8][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:19.686220 [P2P8]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:19.710222 [P2P8]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:19.729223 [P2P8][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:20.651275 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:20.676277 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:20.697278 [P2P1][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:20.971294 [P2P1]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:20.997295 [P2P1]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:21.014296 [P2P1][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:23.414434 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:23.436435 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:23.452436 [P2P5][68.67.95.71:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:23.463436 [P2P5]Ip 68.67.95.71 blocked.
2015-Sep-09 08:51:26.800627 [P2P1][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:27.277654 [P2P1][74.91.23.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:27.751682 [P2P5][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:28.648733 [P2P7]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:28.671734 [P2P7]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:28.692735 [P2P7][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:29.363774 [P2P7]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:29.388775 [P2P7]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:29.405776 [P2P7][74.91.23.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:29.421777 [P2P7]Ip 74.91.23.186 blocked.
2015-Sep-09 08:51:29.832801 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:29.856802 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:29.877803 [P2P5][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:30.225823 [P2P5][192.187.114.114:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:30.747853 [P2P7][63.141.254.186:11180 OUT]Sync data returned unknown top block: 603107 -> 604602 [1495 blocks (4 days) behind]
SYNCHRONIZATION started
2015-Sep-09 08:51:32.018926 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:32.033927 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:32.041927 [P2P5][192.187.114.114:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:32.047927 [P2P5]Ip 192.187.114.114 blocked.
2015-Sep-09 08:51:33.053985 [P2P5]ERROR C:\Users\Arno\Documents\GitHub\aeon-0.9.4.0\src\cryptonote_core\blockchain_storage.cpp:780 main blockchain wrong height
2015-Sep-09 08:51:33.076986 [P2P5]Block recognized as orphaned and rejected, id = <6a300799d515ea87ec87c0bd17a517054ffdc2dc4683e515531170df7a0e8d90>
2015-Sep-09 08:51:33.096987 [P2P5][63.141.254.186:11180 OUT]Block received at sync phase was marked as orphaned, dropping connection
2015-Sep-09 08:51:33.115988 [P2P5]Ip 63.141.254.186 blocked.
September 08, 2015, 09:14:42 PM
Quote from GingerAle
I have zero programming ability, but would it be possible to have miners registered somehow or tagged I guess to the AEON blockchain, so that miners would have to be verified between nodes/wallets in order to mine or vote. Would that be a way to identify multiple instances as they would be seen as clones or a attempted double spend, if you will?
Kind of like using Smart Contracts along with the Byzantine General theory?
Hope that makes sense? It does to me but it's late and I'm not great at explaining things sometimes.
Quote
I mean one of the primary problems is the fact that a malicous miner could spawn multiple instances of the mining function, and assuming this miner could always just hide themselves behind layers of abstraction...... I guess its just one of those things that I assumed was too difficult to solve, and hence it hasn't been solved by now.
I have zero programming ability, but would it be possible to have miners registered somehow or tagged I guess to the AEON blockchain, so that miners would have to be verified between nodes/wallets in order to mine or vote. Would that be a way to identify multiple instances as they would be seen as clones or a attempted double spend, if you will?
Kind of like using Smart Contracts along with the Byzantine General theory?
Hope that makes sense? It does to me but it's late and I'm not great at explaining things sometimes.
September 08, 2015, 04:59:36 PM
We got another 500 AEON donation within the past day or two, plus continued --donate mining.
Thank you to all the donators!
balance: 440447.836861825727, unlocked balance: 440409.651928618917
Thank you to all the donators!
balance: 440447.836861825727, unlocked balance: 440409.651928618917
September 07, 2015, 03:55:49 PM
It sems to be that, in order to mine, you need just the latest N blocks (enough for the block template, and a few more to handle reorgs). Also the tx pool. But most of the DB, you don't need if your goal is just to mine. So making a "mining node" mode may make being a solo miner less painful.
This only works if such miners are a small hash share, but there is no way to ensure that. If they become a large share then attacking the chain with long forks, or even permanent ones, becomes possible since those miners will accept transactions that are invalid with respect to the earlier blocks. In fact those miners may never agree to reject those blocks if that chain remains longer.
Unfortunately the light node (--pruning) is the best that can be done reasonably safely and that still requires a fair bit of memory and disk (though at least the rate of growth is more contained, giving Moore's Law a chance to catch up). Of course Monero's wonderful database completely solves the memory usage part (once it is fully debugged), but currently increases the disk usage part by quite a bit.
September 07, 2015, 02:10:27 PM
One roadblock to solo mining seems like it should not be one: the memory/disk requirements of a full node. It sems to be that, in order to mine, you need just the latest N blocks (enough for the block template, and a few more to handle reorgs). Also the tx pool. But most of the DB, you don't need if your goal is just to mine. So making a "mining node" mode may make being a solo miner less painful. [...]
Exactly. Which is another reason why I'm really digging this light-node
I have effectively been solo mining on the light-node ever since the 1st test release was posted. With light-node in mind, particularly in some future iteration where one can setup bandwidth limits and is powered by some DB backend, I would probably revise my suggestion at 20% reward boost ... Maybe some 10% would be a sufficient motivator. All arbitrary numbers that I'm pulling out of my rear end btw.
Edit: Maybe worth considering a doubly-light-node, the rough equivalent of a light-node that stores an even smaller range of the network history? Or perhaps a strict barebones construct that would only store the absolutely necessary data (as you well described)... I would think that such a barebones node is still a valuable contributor towards network health (and security).
Edit2: Require some further thought as to how would we ensure that such a doubly-light-node or the barebones construct, would not include invalid transactions in blocks that it mines (double-spends, etc). Obviously, the offending node would eventually fork off, as the rest of the network would reject that block (assuming a super-majority of full nodes). Still, at minimum, this would represent a DoS attack on these nodes: that they could be "poisoned" with invalid transaction data, so that their blocks would be rejected by the network.
Edit3: Need moar edits
September 07, 2015, 01:30:47 PM
One roadblock to solo mining seems like it should not be one: the memory/disk requirements of a full node. It sems to be that, in order to mine, you need just the latest N blocks (enough for the block template, and a few more to handle reorgs). Also the tx pool. But most of the DB, you don't need if your goal is just to mine. So making a "mining node" mode may make being a solo miner less painful.
Edit: pool hash now down to 60%, and fee down to 4% (from ~80% and ~9% this morning).
Edit: pool hash now down to 60%, and fee down to 4% (from ~80% and ~9% this morning).
September 07, 2015, 11:43:04 AM
hrmm, kinda got rambly and my thought train seems to have jumped the track. damn.
Following your (criss-crossy) line of thought, here's another ramble on pools and miners:
I think that pools are a necessary evil. The smallest of miners, would be practically impeded of participating on the mining network, if there were no pools, and given sufficient nethash that their average time to find a block would be leaning towards infinity (exaggerated, yes).
On the other hand, pool concentration, and the lack of a technical necessity for running a node (for the majority of participants), present us with a very common dilemma:
nodes are too few, and they lack any substantial form of incentive.
I think this problem was indeed neatly approached by Spreadcoin, in that it attempted to prevent pool formation entirely. I think it failed at the original goal, but the fact that it resulted in a modified trust model (note the existing private pool for Spread) is quite interesting.
I'm not sure the same existed for Spread as I am not sufficiently familiar with it, but with Ziftrcoin, I know that there is an incentive to solo-mine, built on some of the same principles that Spread initiated, and by providing knowledge over the current transaction pool, solo-miners can claim a higher reward in their block finds (5% IIRC).
I think it is this latter approach that deserves some further thought. If we could work out a way to incentivize solo mining, and at the same time encourage more full nodes to exist, we'd see a much healthier network (as well as more secure, relatively speaking ofc).
I do believe that a 5% reward boost is too small of an incentive to pursue this approach sensibly, and would suggest something as high as 20%. My rationale is that: technically, solo-miners are usually at a disadvantage, because part of their mining resources are implicitly tied up with the business of running a full node (hence, some potential hashrate performance is lost). Additionally, external miners will usually perform best, seeing as they run code that is systematically being optimized for that function alone, and are less concerned with wide cross-platform support and code portability (compared to a full node).
Personally, I run a full node and I'm happy solo mining, even though I get a performance drop when compared to pool mining. Thanks to Smooth's recent updates, the performance drop is rather tiny (in the region of 5% or so), though my motivation is not so much an economical one, as it is of participating with a full node and contributing towards a healthy network.
Most miners are economically motivated, period. I think it would be nice to leverage on that motivation, and drive some of these miners towards a more meaningful contribution to the network (solo-mining, full node incentives). This ramble is just my collection of past ideas on this matter, and food for thought as much brighter minds are around
September 07, 2015, 11:04:20 AM
Done. The estimated pool share now has an extra "X/Y blocks" as an explanation.
Pool's now at 66%, going down from the earlier 80%.
Pool's now at 66%, going down from the earlier 80%.
excellent work!
So, as smooth pointed out, even if spread's countermeasure functions properly, pools can still form - there is just a level of trust involved.. So I'm working with the theory that spread can be exploited by the vectors described in the whitepaper. http://www.spreadcoin.info/downloads/SpreadCoin-WhitePaper.pdf
Unfortunately, this could spiral in the opposite direction of what is intended - a small number of very large pools. Based on the nature of trust, we could see how new pools would have a hard time forming, and miners would actually need references to join a pool, so there'd be a tighter collusion, to whatever ends. Ultimately, it introduces a large human factor into the network architecture.
However, though, an interesting aspect to explore might be why mining has evolved the way it has, especially in altcoins, and especially in intentionally asic-resistant coins like cryptonight based ones. Pooling came into existence in bitcoin to "level the playing field", if I have my history right, of those with advanced hardware. Unintentionally, this brought with it an increased ease to participate in the network (no need to run a node, or for that matter, set up asic hardware to interface with a node).
One can look back at Monero's history and see that there was specific effort in the first months to develop a pool. Ostensibly, this was done to encourage participation in the network, even though at that time it was easy to run a node (the memory requirements hadn't ballooned). So, one can surmise that in order for the general cryptocurrency community to support a coin network, pools are expected. And the way this ecosystem has evolved is that a coin network has to find a way to thrive in this community in order to potentially breakout. The skill set is here to secure the network. Hence, pools are maintained to entice community members.
Thus, pool culture might be difficult to defeat, as Wolf has pointed out, and might very well be necessary for network health during a coin's growing pains. Now, the countermeasure offered via smart-mining requires adoption, so its chicken and egg.
But ultimately, pooling, in its most simple form, isn't detrimental to the network, its the way in which the pooling is performed. I.e., forming a cooperative is functionally equivalent to independently mining - however, the conventional pool setup is not a cooperative, due to the single node to which shares are submitted.
hrmm, kinda got rambly and my thought train seems to have jumped the track. damn.
September 07, 2015, 08:31:28 AM
Done. The estimated pool share now has an extra "X/Y blocks" as an explanation.
Pool's now at 66%, going down from the earlier 80%.
Pool's now at 66%, going down from the earlier 80%.
September 07, 2015, 07:54:16 AM
Awesome, thanks Smooth & Mooo.
I'm happy either way as I'm still at it solo style, pool stats worry me not
Heck, I'll be solo'ing even if block-finds get spaced by many days for me, as the point is also to run a contributing node.
I'm happy either way as I'm still at it solo style, pool stats worry me not
Heck, I'll be solo'ing even if block-finds get spaced by many days for me, as the point is also to run a contributing node.
September 07, 2015, 07:24:32 AM
If you look right above the fee display it shows the estimate of net share that is used for the calculation. That is calculated based on the most recent 60 blocks and MoneroMooo said he's going make that more clear in the status display.
September 07, 2015, 06:38:51 AM
Mooo: I figure it would make most sense for miners on your pool, if the nethash estimate was derived from the same input data that you are using for the fee calculation. This would allow your miners to make more sense of the dynamic fee at any particular time.
In other words: switch to a nethash estimation based on the time that it took to find the last 60 blocks (as that is the sample size for the dynamic fee calculation). The only downside I'm seeing is that you'd no longer display the same estimated nethash as the other pools, though your estimation would perhaps be the more accurate one.
Cheers!
In other words: switch to a nethash estimation based on the time that it took to find the last 60 blocks (as that is the sample size for the dynamic fee calculation). The only downside I'm seeing is that you'd no longer display the same estimated nethash as the other pools, though your estimation would perhaps be the more accurate one.
Cheers!
September 07, 2015, 06:29:07 AM
The variable fee system is now in place. Current pool share is 50 of the last 60 blocks, but slow blocks mean that some large miner has recently (temporarily ?) stopped mining.
hmm... pool hashrate less that 50% of net hashrate, why Pool Fee is 8.67% ?Estimated pool share: 78.3%
This estimation uses the actual blocks found. The pool found 47 of the last 60 blocks. As a few people mentioned above, the "network hash rate" is an approximation that can lag until the difficulty algorithm overcomes its inherent inertia.
September 07, 2015, 05:27:04 AM
The variable fee system is now in place. Current pool share is 50 of the last 60 blocks, but slow blocks mean that some large miner has recently (temporarily ?) stopped mining.
hmm... pool hashrate less that 50% of net hashrate, why Pool Fee is 8.67% ? September 07, 2015, 03:25:31 AM
The variable fee system is now in place. Current pool share is 50 of the last 60 blocks, but slow blocks mean that some large miner has recently (temporarily ?) stopped mining.
Jump to: