I am curious why so many ETN haters still love to read this ETN topic and constantly mention how shit this coin is. Please get the fuck out off here and keep this topic clean. If this coin is hated as much as XRP then I love to see where ETN finally will end up. Funny thing is that the most hated coins end up the highest in price!
I don't think ETN is a hated coin, I just think it's dead or dying fast. If we don't see any improvement from the team will always lead to zero value, I hope the team behind the project are taking time for the developments. So we shouldn't bother much about the projects as long as we see an update from the team. Will help the coin to increase it's value when the market starts recovering. Why do not you trade etn bitrex and poloniex and binance etn is scam you can see them in 1st page of this topic https://ibb.co/e3vwyG
|
|
|
|
|
and more one:
Sam Markus We're not intrigued. It's called making a blockchain centralized. EOS did that already.
|
|
|
|
|
nice comment in FB etn page, nothing to add:
Henk de Peuter Centralizing the ETN blockchain with a small amount of selected (unknown and mysterious) nodes with the purpose to prevent a 51% attack is nothing else than a 100% attack of the founders, you yourselves. It would be the same as replacing the blockchain with a centralized database, under your control, holding all the wallets of the investors, as one big spreadsheet. This is a huge throw back to 1990. But yes, it now takes you only about $1 a day for electricity.I think you missed the point here of what blockchain cryptocurrency is about. But knowing that ETN is a fork of Monero (which had to apply huge security changes over the last months), I suspect applying these same changes were way too challenging, resulting in this smart marketing solution (Proof of Responsibility, lol), satisfying the ignorant believers. I even doubt if it is legal as you changed all the fundamentals of the product to which people signed up (and paid) for in the ICO. Happy I sold my ETN a while ago. You had a great opportunity late 2017 but you missed the momentum. Good luck anyways
|
|
|
|
Richard decided to mine his own cryptocurrency himself? I want to mine etn - how can I mine it?  You can't anymore. For those interested in the technical makeup of Electroneum's PoR blockchain, the network still remains decentralised. we all know that is a huge lie - decentralized is when there is no any center and it is when everyone can mine it for now etn is like xrp - fully centralized  that's sad 
|
|
|
|
For what?
for link of course
|
|
|
|
Richard decided to mine his own cryptocurrency himself? I want to mine etn - how can I mine it? 
|
|
|
|
Easy-VPN Integration Ambassador Program Launch
thank you!
|
|
|
|
There is more activity on discord and it's more convenient to use than this forum. Finally, there are plenty linked and pinned resources about support which can greatly help.
ok, I will try last gui wallet then gui wallet works perfect! now I can see my balance 
|
|
|
|
There is more activity on discord and it's more convenient to use than this forum. Finally, there are plenty linked and pinned resources about support which can greatly help.
ok, I will try last gui wallet then
|
|
|
|
cant refresh my wallet
letheand is running and synchronized with the network:
.........\lethean-cli-win-64bit-v3.1>letheand.exe --data-dir wallet 2019-06-28 19:03:55.372 12356 INFO global src/daemon/main.cpp:279 Lethean 'Congo' (v3.1.0-7639efe) 2019-06-28 19:03:55.374 12356 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol... 2019-06-28 19:03:55.376 12356 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK 2019-06-28 19:03:55.377 12356 INFO global src/daemon/p2p.h:63 Initiali zing p2p server... 2019-06-28 19:06:55.223 12356 INFO global src/daemon/p2p.h:68 P2p serv er initialized OK 2019-06-28 19:06:55.223 12356 INFO global src/daemon/rpc.h:58 Initiali zing core rpc server... 2019-06-28 19:06:55.224 12356 INFO global contrib/epee/include/net/http_se rver_impl_base.h:70 Binding on 127.0.0.1:48782 2019-06-28 19:06:55.224 12356 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 48782 2019-06-28 19:06:55.224 12356 INFO global src/daemon/core.h:73 Initiali zing core... 2019-06-28 19:06:55.225 12356 INFO global src/cryptonote_core/cryptonote_c ore.cpp:323 Loading blockchain from folder wallet\lmdb ... 2019-06-28 19:06:55.352 12356 INFO global src/cryptonote_core/cryptonote_c ore.cpp:421 Loading checkpoints 2019-06-28 19:06:55.353 12356 INFO global src/daemon/core.h:78 Core ini tialized OK 2019-06-28 19:06:55.354 12356 INFO global src/daemon/rpc.h:68 Starting core rpc server... 2019-06-28 19:06:55.355 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok 2019-06-28 19:06:55.355 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2019-06-28 19:06:56.356 [P2P7] INFO global src/cryptonote_core/cryptonote_c ore.cpp:1262 ←[1;33m ********************************************************************** The daemon will start synchronizing with the network. This may take a long time to complete.
You can set the level of process detailization* through "set_log <level|categori es>" command*, where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the "help" command to see the list of available commands. ********************************************************************** ←[0m 2019-06-28 19:06:59.930 [P2P7] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 469144 -> 469248 [Your node is 104 blocks (0 days) behind]
SYNCHRONIZATION started 2019-06-28 19:07:02.552 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469164/46 9248←[0m 2019-06-28 19:07:05.887 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469184/46 9249←[0m 2019-06-28 19:07:08.226 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469204/46 9249←[0m 2019-06-28 19:07:11.374 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469224/46 9249←[0m 2019-06-28 19:07:13.983 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469244/46 9249←[0m 2019-06-28 19:07:14.566 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469248/46 9249←[0m 2019-06-28 19:07:14.747 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469249/46 9249←[0m 2019-06-28 19:09:21.512 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1543 ←[1;33m ********************************************************************** You are now synchronized with the network. You may now start lethean-wallet-cli.
Use the "help" command to see the list of available commands. **********************************************************************←[0m
but wallet say that daemon is not running:
...............\lethean-cli-win-64bit-v3.1>lethean-wallet-cli.exe Lethean 'Congo' (v3.1.0-7639efe) Logging to ...................\lethean-cli-win-64bit-v3.1\lethean-wall et-cli.log Specify wallet file name (e.g., MyWallet). If the wallet doesn't exist, it will be created. Wallet file name (or Ctrl-C to quit): ++++++++wallet Wallet and key files found, loading... Wallet password: *************** Opened wallet: ++++++++++++++++++++++++ ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** Starting refresh... Error: refresh failed: no connection to daemon. Please make sure daemon is runni ng.. Blocks received: 0 Background refresh thread started [wallet iz5i3F (out of sync)]:
what is wrong?
can anyone help me please? developers are do not appear here?
|
|
|
|
cant refresh my wallet
letheand is running and synchronized with the network:
.........\lethean-cli-win-64bit-v3.1>letheand.exe --data-dir wallet 2019-06-28 19:03:55.372 12356 INFO global src/daemon/main.cpp:279 Lethean 'Congo' (v3.1.0-7639efe) 2019-06-28 19:03:55.374 12356 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol... 2019-06-28 19:03:55.376 12356 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK 2019-06-28 19:03:55.377 12356 INFO global src/daemon/p2p.h:63 Initiali zing p2p server... 2019-06-28 19:06:55.223 12356 INFO global src/daemon/p2p.h:68 P2p serv er initialized OK 2019-06-28 19:06:55.223 12356 INFO global src/daemon/rpc.h:58 Initiali zing core rpc server... 2019-06-28 19:06:55.224 12356 INFO global contrib/epee/include/net/http_se rver_impl_base.h:70 Binding on 127.0.0.1:48782 2019-06-28 19:06:55.224 12356 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 48782 2019-06-28 19:06:55.224 12356 INFO global src/daemon/core.h:73 Initiali zing core... 2019-06-28 19:06:55.225 12356 INFO global src/cryptonote_core/cryptonote_c ore.cpp:323 Loading blockchain from folder wallet\lmdb ... 2019-06-28 19:06:55.352 12356 INFO global src/cryptonote_core/cryptonote_c ore.cpp:421 Loading checkpoints 2019-06-28 19:06:55.353 12356 INFO global src/daemon/core.h:78 Core ini tialized OK 2019-06-28 19:06:55.354 12356 INFO global src/daemon/rpc.h:68 Starting core rpc server... 2019-06-28 19:06:55.355 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok 2019-06-28 19:06:55.355 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2019-06-28 19:06:56.356 [P2P7] INFO global src/cryptonote_core/cryptonote_c ore.cpp:1262 ←[1;33m ********************************************************************** The daemon will start synchronizing with the network. This may take a long time to complete.
You can set the level of process detailization* through "set_log <level|categori es>" command*, where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the "help" command to see the list of available commands. ********************************************************************** ←[0m 2019-06-28 19:06:59.930 [P2P7] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 469144 -> 469248 [Your node is 104 blocks (0 days) behind]
SYNCHRONIZATION started 2019-06-28 19:07:02.552 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469164/46 9248←[0m 2019-06-28 19:07:05.887 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469184/46 9249←[0m 2019-06-28 19:07:08.226 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469204/46 9249←[0m 2019-06-28 19:07:11.374 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469224/46 9249←[0m 2019-06-28 19:07:13.983 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469244/46 9249←[0m 2019-06-28 19:07:14.566 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469248/46 9249←[0m 2019-06-28 19:07:14.747 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469249/46 9249←[0m 2019-06-28 19:09:21.512 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1543 ←[1;33m ********************************************************************** You are now synchronized with the network. You may now start lethean-wallet-cli.
Use the "help" command to see the list of available commands. **********************************************************************←[0m
but wallet say that daemon is not running:
...............\lethean-cli-win-64bit-v3.1>lethean-wallet-cli.exe Lethean 'Congo' (v3.1.0-7639efe) Logging to ...................\lethean-cli-win-64bit-v3.1\lethean-wall et-cli.log Specify wallet file name (e.g., MyWallet). If the wallet doesn't exist, it will be created. Wallet file name (or Ctrl-C to quit): ++++++++wallet Wallet and key files found, loading... Wallet password: *************** Opened wallet: ++++++++++++++++++++++++ ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** Starting refresh... Error: refresh failed: no connection to daemon. Please make sure daemon is runni ng.. Blocks received: 0 Background refresh thread started [wallet iz5i3F (out of sync)]:
what is wrong?
can anyone help me please?
|
|
|
|
|
cant refresh my wallet
letheand is running and synchronized with the network:
.........\lethean-cli-win-64bit-v3.1>letheand.exe --data-dir wallet 2019-06-28 19:03:55.372 12356 INFO global src/daemon/main.cpp:279 Lethean 'Congo' (v3.1.0-7639efe) 2019-06-28 19:03:55.374 12356 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol... 2019-06-28 19:03:55.376 12356 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK 2019-06-28 19:03:55.377 12356 INFO global src/daemon/p2p.h:63 Initiali zing p2p server... 2019-06-28 19:06:55.223 12356 INFO global src/daemon/p2p.h:68 P2p serv er initialized OK 2019-06-28 19:06:55.223 12356 INFO global src/daemon/rpc.h:58 Initiali zing core rpc server... 2019-06-28 19:06:55.224 12356 INFO global contrib/epee/include/net/http_se rver_impl_base.h:70 Binding on 127.0.0.1:48782 2019-06-28 19:06:55.224 12356 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 48782 2019-06-28 19:06:55.224 12356 INFO global src/daemon/core.h:73 Initiali zing core... 2019-06-28 19:06:55.225 12356 INFO global src/cryptonote_core/cryptonote_c ore.cpp:323 Loading blockchain from folder wallet\lmdb ... 2019-06-28 19:06:55.352 12356 INFO global src/cryptonote_core/cryptonote_c ore.cpp:421 Loading checkpoints 2019-06-28 19:06:55.353 12356 INFO global src/daemon/core.h:78 Core ini tialized OK 2019-06-28 19:06:55.354 12356 INFO global src/daemon/rpc.h:68 Starting core rpc server... 2019-06-28 19:06:55.355 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok 2019-06-28 19:06:55.355 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop... 2019-06-28 19:06:56.356 [P2P7] INFO global src/cryptonote_core/cryptonote_c ore.cpp:1262 ←[1;33m ********************************************************************** The daemon will start synchronizing with the network. This may take a long time to complete.
You can set the level of process detailization* through "set_log <level|categori es>" command*, where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the "help" command to see the list of available commands. ********************************************************************** ←[0m 2019-06-28 19:06:59.930 [P2P7] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:305 [140.82.9.90:48772 OUT] Sync data returned a new top block candidate: 469144 -> 469248 [Your node is 104 blocks (0 days) behind]
SYNCHRONIZATION started 2019-06-28 19:07:02.552 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469164/46 9248←[0m 2019-06-28 19:07:05.887 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469184/46 9249←[0m 2019-06-28 19:07:08.226 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469204/46 9249←[0m 2019-06-28 19:07:11.374 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469224/46 9249←[0m 2019-06-28 19:07:13.983 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469244/46 9249←[0m 2019-06-28 19:07:14.566 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469248/46 9249←[0m 2019-06-28 19:07:14.747 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1154 ←[1;33m[140.82.9.90:48772 OUT] Synced 469249/46 9249←[0m 2019-06-28 19:09:21.512 [P2P6] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1543 ←[1;33m ********************************************************************** You are now synchronized with the network. You may now start lethean-wallet-cli.
Use the "help" command to see the list of available commands. **********************************************************************←[0m
but wallet say that daemon is not running:
...............\lethean-cli-win-64bit-v3.1>lethean-wallet-cli.exe Lethean 'Congo' (v3.1.0-7639efe) Logging to ...................\lethean-cli-win-64bit-v3.1\lethean-wall et-cli.log Specify wallet file name (e.g., MyWallet). If the wallet doesn't exist, it will be created. Wallet file name (or Ctrl-C to quit): ++++++++wallet Wallet and key files found, loading... Wallet password: *************** Opened wallet: ++++++++++++++++++++++++ ********************************************************************** Use "help" command to see the list of available commands. ********************************************************************** Starting refresh... Error: refresh failed: no connection to daemon. Please make sure daemon is runni ng.. Blocks received: 0 Background refresh thread started [wallet iz5i3F (out of sync)]:
what is wrong?
|
|
|
|
|
electroneum-windows-v2.1.1.2>electroneumd.exe --data-dir wallet 2019-06-15 15:33:40.950 2056 INFO global src/daemon/main.cpp:280 Electron eum 'April 2019' (v2.1.1.2-release) 2019-06-15 15:33:40.996 2056 INFO global src/daemon/protocol.h:56 Initializing cryptonote protocol... 2019-06-15 15:33:41.012 2056 INFO global src/daemon/protocol.h:61 Cryptonote protocol initialized OK 2019-06-15 15:33:41.012 2056 INFO global src/daemon/p2p.h:64 Initiali zing p2p server... 2019-06-15 15:33:45.309 2056 INFO global src/daemon/p2p.h:69 P2p serv er initialized OK 2019-06-15 15:33:45.309 2056 INFO global src/daemon/rpc.h:59 Initiali zing core rpc server... 2019-06-15 15:33:45.325 2056 INFO global contrib/epee/include/net/http_se rver_impl_base.h:70 Binding on 127.0.0.1:26968 2019-06-15 15:33:45.325 2056 INFO global src/daemon/rpc.h:64 Core rpc server initialized OK on port: 26968 2019-06-15 15:33:45.325 2056 INFO global src/daemon/core.h:74 Initiali zing core... 2019-06-15 15:33:45.325 2056 INFO global src/cryptonote_core/cryptonote_c ore.cpp:324 Loading blockchain from folder wallet\lmdb ... 2019-06-15 15:33:45.496 2056 WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:1156 LMDB memory map needs to be resized, doing that now. 2019-06-15 15:33:45.496 2056 INFO global src/blockchain_db/lmdb/db_lmdb.c pp:495 LMDB Mapsize increased. Old: 44581MiB, New: 45605MiB 2019-06-15 15:33:48.700 2056 INFO global src/cryptonote_core/cryptonote_c ore.cpp:422 Loading checkpoints 2019-06-15 15:33:49.106 2056 INFO global src/blockchain_db/lmdb/db_lmdb.c pp:579 [batch] DB resize needed 2019-06-15 15:33:49.106 2056 INFO global src/blockchain_db/lmdb/db_lmdb.c pp:495 LMDB Mapsize increased. Old: 45605MiB, New: 46629MiB 2019-06-15 15:33:49.106 2056 INFO global src/blockchain_db/lmdb/db_lmdb.c pp:579 [batch] DB resize needed 2019-06-15 15:33:49.106 2056 INFO global src/blockchain_db/lmdb/db_lmdb.c pp:495 LMDB Mapsize increased. Old: 46629MiB, New: 47653MiB 2019-06-15 15:33:49.465 2056 INFO global src/daemon/core.h:79 Core ini tialized OK 2019-06-15 15:33:49.465 2056 INFO global src/daemon/rpc.h:69 Starting core rpc server... 2019-06-15 15:33:49.465 [SRV_MAIN] INFO global src/daemon/rpc.h:74 Core rpc server started ok 2019-06-15 15:33:49.481 [SRV_MAIN] INFO global src/daemon/p2p.h:79 Starting p2p net loop... 2019-06-15 15:33:50.496 [P2P7] INFO global src/cryptonote_core/cryptonote_c ore.cpp:1259 ←[1;33m ********************************************************************** The daemon will start synchronizing with the network. This may take a long time to complete.
You can set the level of process detailization* through "set_log <level|categori es>" command*, where <level> is between 0 (no details) and 4 (very verbose), or custom category based levels (eg, *:WARNING)
Use the "help" command to see the list of available commands. ********************************************************************** ←[0m 2019-06-15 15:33:50.496 [P2P7] WARN global src/cryptonote_core/cryptonote_c ore.cpp:1283 ←[1;31m********************************************************* *************←[0m 2019-06-15 15:33:50.496 [P2P7] WARN global src/cryptonote_core/cryptonote_c ore.cpp:1284 ←[1;31mLast scheduled hard fork time shows a daemon update is ne eded now.←[0m 2019-06-15 15:33:50.496 [P2P7] WARN global src/cryptonote_core/cryptonote_c ore.cpp:1285 ←[1;31m********************************************************* *************←[0m 2019-06-15 15:34:33.934 [P2P9] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:303 [188.223.205.156:26967 OUT] Sync data returned a new top block candidate: 480001 -> 573011 [Your node is 93010 blocks (129 days) behind] SYNCHRONIZATION started 2019-06-15 15:35:56.231 [P2P7] INFO global src/cryptonote_protocol/cryptono te_protocol_handler.inl:1152 ←[1;33m[188.223.205.156:26967 OUT] Synced 48186 5/573011←[0m 2019-06-15 15:35:56.481 [P2P7] WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:73 Attempt to get block size from height 481365 failed -- b lock size not in db 2019-06-15 15:36:05.746 [P2P7] WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:73 Attempt to get hash from height 481864 failed -- hash no t in db 2019-06-15 15:36:11.528 [P2P6] WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:73 Attempt to get hash from height 481864 failed -- hash no t in db 2019-06-15 15:36:11.965 [P2P6] WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:73 Attempt to get hash from height 481864 failed -- hash no t in db 2019-06-15 15:36:26.153 [P2P6] WARN blockchain.db.lmdb src/blockchain_d b/lmdb/db_lmdb.cpp:73 Attempt to get hash from height 481864 failed -- hash no t in db
synced again several times - spent a few weeks, but every time the same thing
how do I synchronize?
|
|
|
|
upd: Network Hashrate 6.29 MH/s 92.6 % unknown
|
|
|
|
the algorithm is dead, 4 MH. ASIC will sell the coin , price will collapse  It seems unrealistic that there are working asics for cryptonight now There are, at least for the original CN algo. It's not like the devs couldn't make some adjustments to get rid of any ASICs. I wouldn't worry too much.  asics are already here: Network Hashrate 2.22 MH/s 81.0 % unknown https://miningpoolstats.stream/iridium
|
|
|
|
Who the hell believes for 1 second that 25% of all the mined ETN were actually sitting on Cryptopia?
Seriously?
Use your heads.
there was more then 200 000 000 etn sell orders
|
|
|
|
|