electroneum / electroneum Goto Github PK

Electroneum: The Legacy L1 Repository

License: Other

CMake 2.04% Makefile 0.70% C 10.82% C++ 83.46% Shell 0.21% Batchfile 0.02% Python 1.93% q 0.10% Dockerfile 0.17% Ruby 0.01% Assembly 0.44% Raku 0.03% Perl 0.08%

electroneum's Introduction

Electroneum is a Fast, Secure, Mobile Based Cryptocurrency

⚠️ WARNING
This project is the legacy version of Electroneum. Electroneum has since migrated over to a new smart contract enabled blockchain: https://github.com/electroneum/electroneum-sc. For details on how to migrate your ETN, please see: Smartchain-Migration

Development Resources
- Building from Source
- Running an Electroneum Node
Technical Documentation
Vulnerability Response Process
License
Copyright

Development Resources

As with many development projects, the repository on Github is considered to be the "staging" area for the latest changes. Before changes are merged into that branch on the main repository, they are tested by individual developers in their own branches, submitted as a pull request, and then subsequently tested by contributors who focus on testing and code reviews. That having been said, the repository should be carefully considered before using it in a production environment, unless there is a patch in the repository for a particular show-stopping issue you are experiencing. It is generally a better idea to use a tagged release for stability.

Anyone is welcome to contribute to Electroneum's codebase! If you have a fix or code change, feel free to submit it as a pull request directly to the "master" branch. In cases where the change is relatively small or does not affect other parts of the codebase it may be merged in immediately by any one of the collaborators. On the other hand, if the change is particularly large or complex, it is expected that it will be discussed at length either well in advance of the pull request being submitted, or even directly on the pull request.

Building from Source

See Build & Run Documentation.

Software Releases and Pre-compiled Downloads

Hard Fork upgrade height	Date	Fork version	Minimum Electroneum version	Recommended Electroneum version	Name of Release	Details
307500	2018-05-30	v6	v2.0.0.0	v2.0.0.0	Spark	Disable Mixin, Disable RingCT, Base Fee to 0.10 from 0.01, 120s Block Time, Anti-Asic Resistance
324500	2018-07-05	v7	v2.1.0.0	v2.1.0.0	Bolt	Enable ASIC
589169	2019-07-08	v8	v3.0.0.0	v3.0.0.0	Pulse	Migration to our next generation moderated blockchain with Proof of Responsbility. 300kB Blocks : Increased TPS. Improved Unlock Time (5 Blocks), Many Security Improvements, HackerOne Fixes, Reduced Block Reward By 75% (A Double Halvening)
862866	2020-07-22	v9	v3.3.0.0	v3.3.0.0	Wave	Block Reward reduction and future halving scheduling (halving every 4 years, minimum 50etn until max supply. 25etn emission per block after reaching max supply).
1175315	2021-09-30	v10	v4.0.0.1	v4.0.0.1	Aurora	Migration to a transparent blockchain with permissioned validation
1811310	2024-03-05	v11	v5.0.0.4	v5.0.0.4	Flow (Final Version)	Bridge to the Electroneum Smart chain (github.com/electroneum/electroneum-sc)

X's indicate that these details have not been determined as of commit date.

For pre-built downloads and further details of both our forks and intermediate releases, please go to our github releases page.

Running an Electroneum Node

See Build & Run Documentation.

Technical Documentation

Smartchain Migration

Please see our gitbook documentation which explains how to migrate your ETN over to the Electroneum Smartchain.

Some technical information about how the bridge address was created can be found below:

The bridge address spendkey is generated by doing Hash_to_point(v9 fork block hash).-
This ensures that the bridge address is essentially a burn address for which there is no known private key.
The same logic has been used for a coinbase burn address (hash_to_point(hash of v10 fork block: 1175315 )), 
which the remaining miners for this project will mine to. This is required for continuity in the circulating supply 
when we migrate to the smartchain. On the mainnet, emissions are burned from block 1806749 inclusive, 
essentially locking the legacy chain supply at 179,649,469,65.76 ETN.

The bridge address for the mainnet is:

etnkC4G8NfUMpnd1o1SCWeGG81DsdVNovZfQfx1W6R33PRcyWQe6gXmHR8mCAezohCPFiHKMzDPh3WD74EMJEnzw9zVUhNLMc5

The bridge address for the testnet is:

etnk6XD4xkmgsajaYyDD7SGsB93Ff6iUN2TaAaqageGkKj2yB1mtd5wJ8QgRfFWTzmJ8QgRfFWTzmJ8QgRfFWTzm4t51KXZBNg

The coinbase burn address for the mainnet and testnet is:
etnkCys4uGhSi9h48ajL9vBDJTcn2s2ttXtXq3SXWPAbiMHNhHitu5fJ8QgRfFWTzmJ8QgRfFWTzmJ8QgRfFWTzm4t51HTfCtK

Vulnerability Response Process

HackerOne is a vulnerability coordination and bug bounty platform that connects businesses with penetration testers and cybersecurity researchers. It was one of the first companies, along with Synack and Bugcrowd, to embrace and utilize crowd-sourced security and cybersecurity researchers as linchpins of its business model; it is the largest cybersecurity firm of its kind. As of July 2018, HackerOne's network consisted of approximately 200,000 researchers, had resolved 72,000 vulnerabilities across over 1,000 customer programs, and had paid $31 million in bounties.

See HackerOne Electroneum's Page.

License

See LICENSE.

Copyright

electroneum's People

Contributors

Stargazers

Watchers

Forkers

davidmikkelsen gkhorkheli kbarber adetunjiadenle szedit10 blackbinary reemardelarosa biborn ithebest786 arthaschang spacecowboylive scratchgolfer omar-hesham vandeurenglenn kinzowa xeoncrypto paysu drehsan consistime chundany tviho puzcoin karlmaster2k3 dadee85 ozgurbilgin ota1982 mahdirajabi96 futron007 dtison moeadil vatof puffeg trijetscud jakejimenez devoneonline justwee evgen66p mni456 touzi168 callidex snooza arshiay logingood calvi2b phoenixxz joeker1086 viadata andyaldridge inv-ayiba praja353 halutek zippynetworks hugoboss17 premiero davidsharpbell debughost thecryptobrains starmute stilkus hashpwr bittcoin555 tobernguyen ginosko1 syntaxserver snoweeed adultboy goofyyang c1pzo sohanlaxmicoin yassin3 mbhargava zhiyuanep songnob alekseygrud rndexspb vaibhavgupta3110 swir strelexx lycion phungmobile2 khryptorgraphics cosminfce davekoz platinumwrist bgengs juansantoscarey geekyayush krypconnect akashbeuria ramanatrav slimdevice 15963 bnyy khanhnnvn arthurleighallen mounirrquiba cideg nikola43 officiallyundead thenocturnacoders

electroneum's Issues

Electroneum windows ver is not working anymore

Today before couple of minuets I can't start anymore electroneumumd and wallet cli (Windows 7)

It just said that is not compatible with this OS ver.... since yesterday was working fine

Wrong currency name in fee

I think monero need to be replaced by electroneum.

[wallet] fee
Current fee is 0.01 monero per kB
12 block (12 minutes) backlog at priority 1
No backlog at priority 2
No backlog at priority 3
12 block (12 minutes) backlog at priority 4

electroneum wallet cli

Hi,

Have problem with etn cli. I configured everything. Check balance everything was ok. But when i sent tokens 3 times on same address with payment id and amount everything goes normal but i am not receiving any coins on exchange. Checked for address few times and that's one from exchange. But after i typed show_transfers there is 3 times some other address and payment id that i entered. How long should it take for transacation or there is some kind of virus that swapped addresses each time?

User error :)

Wallet Doesn't Sync - DB error attempting to fetch block index

2017-12-14 23:21:33.333 [P2P6] ERROR blockchain src/cryptonote_core/blockchain.cpp:3599 Exception in cleanup_handle_incoming_blocks: Failed to commit a transaction to the db: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid

Wallet was working perfectly fine until go live.

Exception: cryptonote::DB_ERROR

2017-12-14 10:52:00.306 [P2P3] INFO stacktrace src/common/stack_trace.cpp:120 Exception: cryptonote::DB_ERROR
2017-12-14 10:52:00.306 [P2P3] INFO stacktrace src/common/stack_trace.cpp:121 Unwound call stack:
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [1] /usr/bin/electroneumd:__cxa_throw+0x106 [0x7df796]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [2] /usr/bin/electroneumd() [0x718174]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [3] /usr/bin/electroneumd:cryptonote::BlockchainLMDB::get_txpool_tx_meta(crypto::hash const&) const+0x35b [0x720fcb]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [4] /usr/bin/electroneumd:cryptonote::Blockchain::get_txpool_tx_meta(crypto::hash const&) const+0x24 [0x748254]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [5] /usr/bin/electroneumd:cryptonote::tx_memory_pool::set_relayed(std::__cxx11::list<std::pair<crypto::hash, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > >, std::allocator<std::pair<crypto::hash, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > > const&)+0xcc [0x78ea2c]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [6] /usr/bin/electroneumd:cryptonote::core::on_transaction_relayed(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+0x444 [0x77e984]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [7] /usr/bin/electroneumd:cryptonote::t_cryptonote_protocol_handler<cryptonote::core>::relay_transactions(cryptonote::NOTIFY_NEW_TRANSACTIONS::request&, cryptonote::cryptonote_connection_context&)+0x47 [0x619167]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [8] /usr/bin/electroneumd:cryptonote::t_cryptonote_protocol_handler<cryptonote::core>::handle_notify_new_transactions(int, cryptonote::NOTIFY_NEW_TRANSACTIONS::request&, cryptonote::cryptonote_connection_context&)+0x208 [0x5c3478]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [9] /usr/bin/electroneumd:int epee::net_utils::buff_to_t_adapter<cryptonote::t_cryptonote_protocol_handler<cryptonote::core>, cryptonote::NOTIFY_NEW_TRANSACTIONS::request, cryptonote::cryptonote_connection_context, boost::_bi::bind_t<int, boost::_mfi::mf3<int, cryptonote::t_cryptonote_protocol_handler<cryptonote::core>, int, cryptonote::NOTIFY_NEW_TRANSACTIONS::request&, cryptonote::cryptonote_connection_context&>, boost::_bi::list4<boost::_bi::value<cryptonote::t_cryptonote_protocol_handler<cryptonote::core>*>, boost::arg<1>, boost::arg<2>, boost::arg<3> > > >(cryptonote::t_cryptonote_protocol_handler<cryptonote::core>*, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, boost::_bi::bind_t<int, boost::_mfi::mf3<int, cryptonote::t_cryptonote_protocol_handler<cryptonote::core>, int, cryptonote::NOTIFY_NEW_TRANSACTIONS::request&, cryptonote::cryptonote_connection_context&>, boost::_bi::list4<boost::_bi::value<cryptonote::t_cryptonote_protocol_handler<cryptonote::core>*>, boost::arg<1>, boost::arg<2>, boost::arg<3> > >, cryptonote::cryptonote_connection_context&)+0x1f2 [0x655c22]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [10] /usr/bin/electroneumd:int cryptonote::t_cryptonote_protocol_handler<cryptonote::core>::handle_invoke_map<cryptonote::cryptonote_connection_context>(bool, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, cryptonote::cryptonote_connection_context&, bool&)+0x1e3 [0x65c6a3]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [11] /usr/bin/electroneumd:int nodetool::node_server<cryptonote::t_cryptonote_protocol_handler<cryptonote::core> >::handle_invoke_map<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> >(bool, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >&, nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context>&, bool&)+0xbe [0x66ff2e]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [12] /usr/bin/electroneumd:nodetool::node_server<cryptonote::t_cryptonote_protocol_handler<cryptonote::core> >::notify(int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context>&)+0x4f [0x67034f]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [13] /usr/bin/electroneumd:epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> >::handle_recv(void const*, unsigned long)+0x470 [0x670820]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [14] /usr/bin/electroneumd:epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >::handle_read(boost::system::error_code const&, unsigned long)+0x1ba [0x6764ea]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [15] /usr/bin/electroneumd:void boost::asio::detail::strand_service::dispatch<boost::asio::detail::binder2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> >, boost::system::error_code, unsigned long> >(boost::asio::detail::strand_service::strand_impl*&, boost::asio::detail::binder2<boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> >, boost::system::error_code, unsigned long>&)+0x6e [0x61ebee]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [16] /usr/bin/electroneumd:boost::asio::detail::completion_handler<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> >, boost::asio::detail::is_continuation_if_running>, boost::system::error_code, unsigned long>, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> > > >::do_complete(boost::asio::detail::task_io_service*, boost::asio::detail::task_io_service_operation*, boost::system::error_code const&, unsigned long)+0x171 [0x61ef41]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [17] /usr/bin/electroneumd:void boost::asio::detail::strand_service::dispatch<boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> >, boost::asio::detail::is_continuation_if_running>, boost::system::error_code, unsigned long>, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> > > >(boost::asio::detail::strand_service::strand_impl*&, boost::asio::detail::rewrapped_handler<boost::asio::detail::binder2<boost::asio::detail::wrapped_handler<boost::asio::io_service::strand, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> >, boost::asio::detail::is_continuation_if_running>, boost::system::error_code, unsigned long>, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> > >&)+0x279 [0x61f2b9]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [18] /usr/bin/electroneumd:boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::asio::detail::wrapped_handler<boost::asio::io_service::strand, boost::_bi::bind_t<void, boost::_mfi::mf2<void, epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >, boost::system::error_code const&, unsigned long>, boost::_bi::list3<boost::_bi::value<boost::shared_ptr<epee::net_utils::connection<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > > > >, boost::arg<1> (*)(), boost::arg<2> (*)()> >, boost::asio::detail::is_continuation_if_running> >::do_complete(boost::asio::detail::task_io_service*, boost::asio::detail::task_io_service_operation*, boost::system::error_code const&, unsigned long)+0x235 [0x61f585]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [19] /usr/bin/electroneumd:epee::net_utils::boosted_tcp_server<epee::levin::async_protocol_handler<nodetool::p2p_connection_context_t<cryptonote::cryptonote_connection_context> > >::worker_thread()+0x817 [0x5b88e7]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [20] /usr/local/lib/libboost_thread.so.1.65.1+0x1437d [0x7fb8a25e037d]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [21] /lib/x86_64-linux-gnu/libpthread.so.0+0x76ba [0x7fb8a17716ba]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	    [22] /lib/x86_64-linux-gnu/libc.so.6:clone+0x6d [0x7fb8a14a73dd]
2017-12-14 10:52:00.312	[P2P3]	INFO 	stacktrace	src/common/stack_trace.cpp:159	
2017-12-14 10:52:00.313	[P2P3]	ERROR	txpool	src/cryptonote_core/tx_pool.cpp:516	Failed to update txpool transaction metadata: Error finding txpool tx meta: MDB_NOTFOUND: No matching key/data pair found

How to solve this problem?

Can't build electroneum repo

hi there,
Im having trouble building the repo im using ubuntu 16.04, ive installed all dependencies.
here's my output when I try build:

-- Building without build tag
-- Could not find DEVELOPER_LOCAL_TOOLS in env (not required)
-- BOOST_IGNORE_SYSTEM_PATHS defaults to OFF
-- Could not find DEVELOPER_LIBUNBOUND_OLD in env (not required)
-- Building for a 64-bit system
-- Building internal libraries as static
-- Could not find DATABASE in env (not required unless you want to change database type from default: lmdb)
-- Using LMDB as default DB type
-- Stack trace on exception enabled
-- Found miniupnpc API version 10
-- Using shared miniupnpc found at /usr/include/miniupnpc
-- Looking for libunbound
-- Found libunbound include (unbound.h) in /usr/include
-- Found libunbound shared library
-- Using 64-bit LMDB from source tree
-- Building on x86_64 for native
-- AES support enabled
-- Found Boost Version: 105800
-- Could NOT find Readline (missing: Readline_INCLUDE_DIR Readline_LIBRARY)
-- Could not find GNU readline library so building without readline support
-- Found Git: /usr/bin/git
-- Configuring done
-- Generating done
-- Build files have been written to: /root/electroneum

If anyone could shed some light on what my problem is building Electroneum.

Thanks.

GLIBC_2.16' not found (required by ./electroneumd)

HI,

Tried the Linux direct miner on a VPS (CentOS 6). Any idea?

`# ./electroneumd

./electroneumd: /lib64/libc.so.6: version GLIBC_2.16' not found (required by ./electroneumd) ./electroneumd: /lib64/libc.so.6: version GLIBC_2.15' not found (required by ./electroneumd)
./electroneumd: /lib64/libc.so.6: version GLIBC_2.17' not found (required by ./electroneumd) ./electroneumd: /lib64/libc.so.6: version GLIBC_2.14' not found (required by ./electroneumd)`

Orphan block when syncing from blockchain.raw

Trying to sync blockchain under ubuntu 16.04 vps. Built from source. Error in console reads

block 5140 / 430432017-12-12 07:49:40.703 b7594940 ERROR bcutil src/blockchain_utilities/blockchain_import.cpp:199 Block verification failed, id = c2ee1058f801020108a2e53d4ccc36d921c3a465186dbcf163276df5bba57c49 2017-12-12 07:49:49.580 b7594940 ERROR bcutil src/blockchain_utilities/blockchain_import.cpp:205 Block received at sync phase was marked as orphaned

I have synced from blockchain.raw in past from release binary under mac and linux on another vps.

Snap remains inactive after start

Running on Ubuntu 17.10, not sure if I'm missing something, but snap start electroneum seems to work, and there is no error in the logs:

$ systemctl status -l snap.electroneum.electroneumd.service 
● snap.electroneum.electroneumd.service - Service for snap application electrone
   Loaded: loaded (/etc/systemd/system/snap.electroneum.electroneumd.service; en
   Active: inactive (dead) since Fri 2017-12-08 18:05:59 EST; 59s ago
  Process: 68451 ExecStart=/usr/bin/snap run electroneum.electroneumd (code=exit
 Main PID: 68464 (code=exited, status=0/SUCCESS)

Dec 08 18:05:59 monolith systemd[1]: Starting Service for snap application elect
Dec 08 18:05:59 monolith electroneum.electroneumd[68451]: 2017-12-08 23:05:59.93
Dec 08 18:05:59 monolith electroneum.electroneumd[68451]: Forking to background.
Dec 08 18:05:59 monolith systemd[1]: Started Service for snap application electr

It seems to fork and die. The cli also reports it can't connect, so I think the service is truly stopping (i.e., it doesn't look like an issue with reporting from snap / systemd).

Happy to poke around if you want to point me in some direction!

Error: Mining did not start -- BUSY

Can anyone help with this?
I am using an iMac and I am getting this error when I enter in start_mining (wallet) 2 or 4.
I want to start mining ETN but this is really discouraging me from doing so.

Any help is appreciated.

electroneum-wallet-cli crashing

Hello,
First i run electroneumd.exe and wait for it to sync.
Then i run electroneum-wallet-cli.exe but it fails when it reaches 700 - 800 refresh.

It worked fine a day ago.

This is the electroneum-wallet-cli.log log:
2017-12-11 17:22:09.413 5936 INFO logging contrib/epee/src/mlog.cpp:148 New log categories: *:WARNING,net:FATAL,net.p2p:FATAL,net.cn:FATAL,global:INFO,verify:FATAL,stacktrace:INFO,logging:INFO,msgwriter:INFO
2017-12-11 17:22:09.415 5936 INFO msgwriter src/common/scoped_message_writer.h:102 Monero 'Helium Hydra' (v0.11.0.0-53f8b3fa)
2017-12-11 17:22:09.420 5936 INFO msgwriter src/common/scoped_message_writer.h:102 Logging to C:\mining\ETN Electroneum\win-x64-0.11.0.0\electroneum-wallet-cli.log
2017-12-11 17:22:14.993 5936 INFO msgwriter src/common/scoped_message_writer.h:102 Wallet and key files found, loading...
2017-12-11 17:22:19.559 5936 WARN wallet.wallet2 src/wallet/wallet2.cpp:2497 Loaded wallet keys file, with public address: etnk123 (Fake wallet)
2017-12-11 17:22:19.714 5936 INFO msgwriter src/common/scoped_message_writer.h:102 Opened wallet: etnk123 (Fake wallet)
2017-12-11 17:22:19.715 5936 INFO msgwriter src/common/scoped_message_writer.h:102 **********************************************************************
Use "help" command to see the list of available commands.

2017-12-11 17:22:19.743 5936 INFO msgwriter src/common/scoped_message_writer.h:102 Starting refresh...

Wallet still not found

Hello,

So I got an Offline wallet back on Nov 1, 2017, at the first launch and it when I would search my wallet on the "Stats & Payment History" it kept saying "Not Found."

Then it went offline and I would periodically check just to see if it was found but no luck. Well now that Electroneum is up and running again I tried to find my wallet again, and it still i keep getting "Not Found".

Any ideas? I made two new offline wallets, but those are also not found.

Build error Ubuntu 16.04

Recent github snapshot can not be built on my machine running 16.04 with all the dependencies installed in the README.
This is my error after issuing "make":

[ 57%] Building CXX object tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp: In function ‘bool {anonymous}::lift_up_difficulty(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&, std::vector<long unsigned int>&, std::vector<long unsigned int>&, test_generator&, size_t, cryptonote::block, const cryptonote::account_base&)’: /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp:48:85: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope difficulty_type diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARGET_V1); ^ /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_invalid_nonce::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const’: /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp:178:81: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope difficulty_type diffic = next_difficulty(timestamps, commulative_difficulties,DIFFICULTY_TARGET_V1); ^ In file included from /home/holger/Documents/electroneum-master/src/cryptonote_basic/cryptonote_basic.h:47:0, from /home/holger/Documents/electroneum-master/src/cryptonote_basic/account.h:33, from /home/holger/Documents/electroneum-master/src/cryptonote_basic/account_boost_serialization.h:33, from /home/holger/Documents/electroneum-master/tests/core_tests/chaingen.h:47, from /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp:31: /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_unlock_time_is_timestamp_in_future::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const’: /home/holger/Documents/electroneum-master/src/cryptonote_config.h:85:57: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope #define DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN DIFFICULTY_TARGET_V1 //just alias; used by tests ^ /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp:267:87: note: in expansion of macro ‘DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN’ miner_tx.unlock_time = blk_0.timestamp + 3 * CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW * DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN; ^ /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_invalid_binary_format::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const’: /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp:575:67: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARGET_V1); ^ /home/holger/Documents/electroneum-master/tests/core_tests/block_validation.cpp:590:65: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARGET_V1); ^ tests/core_tests/CMakeFiles/coretests.dir/build.make:86: recipe for target 'tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o' failed make[3]: *** [tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o] Error 1 make[3]: Leaving directory '/home/holger/Documents/electroneum-master/build/release' CMakeFiles/Makefile2:2157: recipe for target 'tests/core_tests/CMakeFiles/coretests.dir/all' failed make[2]: *** [tests/core_tests/CMakeFiles/coretests.dir/all] Error 2 make[2]: Leaving directory '/home/holger/Documents/electroneum-master/build/release' Makefile:138: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/home/holger/Documents/electroneum-master/build/release' Makefile:62: recipe for target 'release-all' failed make: *** [release-all] Error 2

electroneumd won't sync

I'm trying to sync the blockchain with electroneumd but i'm stuck at height 1 (print_height always show 1)

electroneum.log https://pastebin.com/7zHKM8nj

mining starts automaticly

when you get it with snap on ubuntu, electroneumd deamon CPU mining auto starts until you stop with wallet-cli stop-mining command. monero deamon dont do that... 👎

and also, monero label every where... thats unbelievable

i found triggers in miner.cpp :
m_do_mining(false),
m_current_hash_rate(0),
m_is_background_mining_enabled(false),
but no usefull, because it is disabled like monero. ???

electroneumd.exe Fails to start https://imgur.com/K0qIz9Z

2017-12-13 11:49:26.715 7028 INFO global src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-53f8b3fa)
2017-12-13 11:49:26.716 7028 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol...
2017-12-13 11:49:26.716 7028 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2017-12-13 11:49:26.716 7028 INFO global src/daemon/p2p.h:63 Initializing p2p server...
2017-12-13 11:49:30.029 7028 INFO global src/daemon/p2p.h:68 P2p server initialized OK
2017-12-13 11:49:30.030 7028 INFO global src/daemon/rpc.h:58 Initializing core rpc server...
2017-12-13 11:49:30.030 7028 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:26968
2017-12-13 11:49:30.031 7028 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 26968
2017-12-13 11:49:30.031 7028 INFO global src/daemon/core.h:73 Initializing core...
2017-12-13 11:49:30.032 7028 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder C:\ProgramData\electroneum\lmdb ...
2017-12-13 11:49:30.034 7028 WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:72 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-13 11:49:30.034 7028 ERROR cn src/cryptonote_core/cryptonote_core.cpp:399 Error opening database: Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-13 11:49:30.035 7028 INFO global src/daemon/rpc.h:90 Deinitializing rpc server...
2017-12-13 11:49:30.035 7028 INFO global src/daemon/p2p.h:90 Deinitializing p2p...
2017-12-13 11:49:30.047 7028 INFO global src/daemon/core.h:89 Deinitializing core...
2017-12-13 11:49:30.048 7028 ERROR daemon src/daemon/core.h:94 Failed to deinitialize core...
2017-12-13 11:49:30.049 7028 INFO global src/daemon/protocol.h:77 Stopping cryptonote protocol...
2017-12-13 11:49:30.051 7028 INFO global src/daemon/protocol.h:81 Cryptonote protocol stopped successfully

^^^^This is what I get trying to launch electroneumd.exe

Build issue ‘DIFFICULTY_TARGET_V1’ was not declared in this scope

CentOS 7
Boost 1.65

[ 74%] Building CXX object tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o
/root/electroneum/tests/core_tests/block_validation.cpp: In function ‘bool {anonymous}::lift_up_difficulty(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&, std::vector<long unsigned int>&, std::vector<long unsigned int>&, test_generator&, size_t, cryptonote::block, const cryptonote::account_base&)’:
/root/electroneum/tests/core_tests/block_validation.cpp:48:85: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
	   difficulty_type diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARGET_V1);
																					 ^
/root/electroneum/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_invalid_nonce::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const’:
/root/electroneum/tests/core_tests/block_validation.cpp:178:81: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
   difficulty_type diffic = next_difficulty(timestamps, commulative_difficulties,DIFFICULTY_TARGET_V1);
																				 ^
In file included from /root/electroneum/src/cryptonote_basic/cryptonote_basic.h:47:0,
				 from /root/electroneum/src/cryptonote_basic/account.h:33,
				 from /root/electroneum/src/cryptonote_basic/account_boost_serialization.h:33,
				 from /root/electroneum/tests/core_tests/chaingen.h:47,
				 from /root/electroneum/tests/core_tests/block_validation.cpp:31:
/root/electroneum/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_unlock_time_is_timestamp_in_future::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const’:
/root/electroneum/src/cryptonote_config.h:85:57: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
 #define DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN             DIFFICULTY_TARGET_V1 //just alias; used by tests
														 ^
/root/electroneum/tests/core_tests/block_validation.cpp:267:87: note: in expansion of macro ‘DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN’
   miner_tx.unlock_time = blk_0.timestamp + 3 * CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW * DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN;
																					   ^
/root/electroneum/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_invalid_binary_format::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const’:
/root/electroneum/tests/core_tests/block_validation.cpp:575:67: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
	 diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARGET_V1);
																   ^
/root/electroneum/tests/core_tests/block_validation.cpp:590:65: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
   diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARGET_V1);

Cant Get wallet.cli.exe to work properly

Hi I am trying to get wallet.cli.exe to work in dos through command prompt, but after I follow all steps correctly (at least i think I am) it asks me to specify a starting date or block number which I do and then just returns back to the directory. I am mining Electroneum on my desktop buti can't see my mined balance. For all I know I am just wasting precious time & energy without any ETN to show for it. Any help in solving my mystery is absolutely 100% appreciated.
Cheers in advance
Alien rob

net.dns warning

Hello when I run electroneumd on my mac there is warning pop up : 2017-11-26 21:44:52.669 [P2P1] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
I've give them some time to synchronize but nothing happen.
do you have any solve for this ??

electroneum daemon

Hi Guys,
I am currently trying to setup a text electroneum pool at home before i move it onto a commercial server. When i launch the electroneum daemon i get the following message

2017-12-03 12:29:34.255 7faaf1c6d740 INFO global src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-release)
2017-12-03 12:29:34.256 7faaf1c6d740 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol...
2017-12-03 12:29:34.256 7faaf1c6d740 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2017-12-03 12:29:34.257 7faaf1c6d740 INFO global src/daemon/p2p.h:63 Initializing p2p server...
sendto: Operation not permitted
2017-12-03 12:29:34.445 7faaf1c6d740 INFO global src/daemon/p2p.h:68 P2p server initialized OK
2017-12-03 12:29:34.445 7faaf1c6d740 INFO global src/daemon/rpc.h:58 Initializing core rpc server...
2017-12-03 12:29:34.445 7faaf1c6d740 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:26968
2017-12-03 12:29:34.445 7faaf1c6d740 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 26968
2017-12-03 12:29:34.445 7faaf1c6d740 INFO global src/daemon/core.h:73 Initializing core...
2017-12-03 12:29:34.445 7faaf1c6d740 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder /home/mark/.electroneum/lmdb ...
2017-12-03 12:29:34.464 7faaf1c6d740 INFO global src/cryptonote_core/cryptonote_core.cpp:421 Loading checkpoints
2017-12-03 12:29:34.472 7faaf1c6d740 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2017-12-03 12:29:34.473 7faaf1c6d740 INFO global src/daemon/core.h:78 Core initialized OK
2017-12-03 12:29:34.473 7faaf1c6d740 INFO global src/daemon/rpc.h:68 Starting core rpc server...
2017-12-03 12:29:34.473 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok
2017-12-03 12:29:34.473 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop...
2017-12-03 12:29:35.474 [P2P3] INFO global src/cryptonote_core/cryptonote_core.cpp:1247

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|categories>" command*,
where 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.

2017-12-03 12:29:35.569 [P2P3] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received

I am using Ubuntu server Ubuntu Linux 16.04.3

Thanks

Rockyuk

electroneumd: command not found

what dose it mean ?
ubonto 16

Repo location cannot be changed

Hello, Please allow me to change the location of the repo. When launching the daemon it automatically starts downloading to the C drive.]

electroneumd not syncing with network

Takes a few seconds to this point and then stays there forever.
I also tried it at another pc and left it open 12 hours.

2017-11-25 14:09:29.734 2300 INFO global src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-53f8b3fa)
2017-11-25 14:09:29.734 2300 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol...
2017-11-25 14:09:29.734 2300 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2017-11-25 14:09:29.734 2300 INFO global src/daemon/p2p.h:63 Initializing p2p server...
2017-11-25 14:09:52.145 2300 INFO global src/daemon/p2p.h:68 P2p server initialized OK
2017-11-25 14:09:52.145 2300 INFO global src/daemon/rpc.h:58 Initializing core rpc server...
2017-11-25 14:09:52.146 2300 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:26968
2017-11-25 14:09:52.146 2300 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 26968
2017-11-25 14:09:52.146 2300 INFO global src/daemon/core.h:73 Initializing core...
2017-11-25 14:09:52.147 2300 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder C:\ProgramData\electroneum\lmdb ...
2017-11-25 14:09:52.165 2300 INFO global src/cryptonote_core/cryptonote_core.cpp:421 Loading checkpoints
2017-11-25 14:10:04.219 2300 WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2017-11-25 14:10:04.219 2300 INFO global src/daemon/core.h:78 Core initialized OK
2017-11-25 14:10:04.220 2300 INFO global src/daemon/rpc.h:68 Starting core rpc server...
2017-11-25 14:10:04.220 [SRV_MAIN] INFO global src/daemon/rpc.h:73 Core rpc server started ok
2017-11-25 14:10:04.221 [SRV_MAIN] INFO global src/daemon/p2p.h:78 Starting p2p net loop...
2017-11-25 14:10:05.224 [P2P7] INFO global src/cryptonote_core/cryptonote_core.cpp:1247 �[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|categories>" command*,
where 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
2017-11-25 14:10:05.648 [P2P7] WARN net.dns src/common/dns_utils.cpp:487 WARNING: no two valid ElectroneumPulse DNS checkpoint records were received

snap install electroneum --beta

error: snap "electroneum" not found (at least in channel "beta")
Is it removed from snap ?

Im Using Ubunto 16

Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 0

(https://user-images.githubusercontent.com/30440412/33385192-4ad4c9ee-d528-11e7-9f6c-cf7f5d28ff07.png)

Unfortunatly wallet won't sync

No mining information for direct mining even in verbose mode

I started electroneumd in a term and I'm fully synced
I launched electroneum-wallet-cli in another term
I log in my wallet
I started to mine with start_mining 6 and can see the RPC message on the daemon confirming that I started mining and I see 6 of my threads running at 100%
On electroneum-wallet-cli I set log to max level set_log 4

But I don't see my mining hashrate, if I found good hash, if I'm earning ETN, etc.. the verbose mode doesn't seems very verbose and I don't have any information about my mining status.

So I don't know if it's me (question) not able to configure it correctly or if the CLI/RPC daemon need to add this information (feature request).

Error: wallet failed to connect to daemon

I have setup a wallet and got everything working on my Windows PC. after that I installed a docker (https://hub.docker.com/r/tperalta82/electroneum/) and synced the blockchain.
Now I want to connect the electroneum-wallet-cli.exe on my windows machine to the docker:
electroneum-wallet-cli.exe --daemon-address 192.168.2.2:26967

This results in a error:

Error: wallet failed to connect to daemon: 192.168.2.2:26967. Daemon either is not started or wrong port was passed. Please make sure daemon is running or restart the wallet with the correct daemon address.
Error: wallet failed to connect to daemon: 192.168.2.2:26967. Daemon either is not started or wrong port was passed. Please make sure daemon is running or restart the wallet with the correct daemon address.

Just to rule network issues out, I started the blockhain daemon on my Windows machine and start the wallet-cli without any arguments, works as expected.
Exit the wallet and start with electroneum-wallet-cli.exe --daemon-address 192.168.2.190:26967 where 192.168.2.190 is the ip address of the local windows machine I'm working on. It gives me the same error (failed to connect to daemon).

Also : when the docker is running, I can connect to port 26967 on the target machine, when the docker is stopped the port is closed.

Any help on how to connect over the network to the blockchain daemon ?

update: I learned I was using the wrong port, the correct port is 26968. When I run the daemon on local windows machine I can only connect to localhost, not to the local IP.
The docker file is setup to bind RPC to ip 0.0.0.0 , it won't start when I change it to 127.0.0.1

Daemon error: Failed to update txpool transaction metadata: Error finding txpool tx meta: MDB_NOTFOUND: No matching key/data pair found

Hello,

I hope you can help us out. We're running a pool at https://etnpool.net and are, as of last friday morning (8th of December), experiencing the error in the attached file concerning:

2017-12-14 08:26:29.870 [P2P4] ERROR txpool src/cryptonote_core/tx_pool.cpp:516 Failed to update txpool transaction metadata: Error finding txpool tx meta: MDB_NOTFOUND: No matching key/data pair found

We've tried everything to resolve this, and with everything I mean:

Rebuilding the blockchain from scratch (miners were still connected during this process).
Rebuilding the block externally, uploading it to the server while miners were not connected.
Updating the wallet to the latest version & rebuilding the blockchain, again, externally.
Completely reinstalling the server by reinstalling the OS and start off new. We've also changed the ports to mine on to make sure no miner is submitting corrupt shares from before the crash. The blockchain has also been rebuild on this system from scratch.

As you might understand we're quite lost here and would like to know what might cause this issue and, of course, how to solve it. We're under the assumption that due to this error our pool is not possible to correctly talk with the blockchain and thus is not able to submit blocks to the chain (not finding blocks). This issue has currently caused our pool to run dry so this is our last resort.

Additional details:

We're running our Redis server separately from our main pool server to maintain stats, I am under the assumption that this should not be a problem as the daemon doesn't talk with Redis.

I thank everybody very much in advance for looking into this and helping us out as we really want to start mining again and be of service to our miners.

Best regards,
Stefan

20171214-MDB_NOTFOUND_no_matching_key_data_pair.txt

Linux Direct Miner Balance Shows Zero Balance Only

Hi,

I'm giving the Linux direct miner a shot. I first ran the daemon towards the end it printed this:

2017-12-09 17:51:20.172	[P2P2]	INFO 	global	src/cryptonote_core/blockchain.cpp:893	REORGANIZE SUCCESS! on height: 60304, new blockchain size: 60306
2017-12-09 17:51:23.080	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:1518	SYNCHRONIZED OK
2017-12-09 18:10:08.222	[P2P1]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:302	[73.47.228.92:55706 INC] Sync data returned a new top block candidate: 60329 -> 60330 [Your node is 1 blocks (0 days) behind] 
SYNCHRONIZATION started
2017-12-09 18:10:10.599	[P2P6]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:1518	SYNCHRONIZED OK
2017-12-09 18:10:56.492	[P2P5]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:302	[105.246.9.158:59277 INC] Sync data returned a new top block candidate: 60330 -> 60331 [Your node is 1 blocks (0 days) behind] 
SYNCHRONIZATION started
2017-12-09 18:11:23.927	[P2P7]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:1518	SYNCHRONIZED OK
2017-12-09 18:11:55.408	[P2P0]	INFO 	global	src/cryptonote_protocol/cryptonote_protocol_handler.inl:1518	SYNCHRONIZED OK

So that should be all good. I then created a wallet by running ./electroneum-wallet-cli and folllowed the promts and finally once that was complete I exectued the start_mining 7 command to start mining with 7 threads.

The daemon starts logging output like this so it looks as if it's mining:

2017-12-09 19:57:54.303	[RPC0]	WARN 	miner	src/cryptonote_basic/miner.cpp:305	Mining has started with 7 threads, good luck!
2017-12-09 19:57:54.303	[miner 1]	INFO 	global	src/cryptonote_basic/miner.cpp:416	Miner thread was started [1]
2017-12-09 19:57:54.303	[miner 2]	INFO 	global	src/cryptonote_basic/miner.cpp:416	Miner thread was started [2]
2017-12-09 19:57:54.303	[miner 4]	INFO 	global	src/cryptonote_basic/miner.cpp:416	Miner thread was started [4]
2017-12-09 19:57:54.303	[miner 3]	INFO 	global	src/cryptonote_basic/miner.cpp:416	Miner thread was started [3]
2017-12-09 19:57:54.303	[miner 5]	INFO 	global	src/cryptonote_basic/miner.cpp:416	Miner thread was started [5]
2017-12-09 19:57:54.303	[miner 6]	INFO 	global	src/cryptonote_basic/miner.cpp:416	Miner thread was started [6]

But when checking the wallet balance with refresh, I only seeBalance: 0.00, unlocked balance: 0.00

[wallet etnk76 (out of sync)]: start_mining 7
Mining started in daemon
[wallet etnk76 (out of sync)]: refresh
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 0                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refersh
unknown command: refersh
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 0                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 0                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 0                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76 (out of sync)]: refresh
Starting refresh...
Refresh done, blocks received: 0                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 3                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 2                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]: refresh     
Starting refresh...
Refresh done, blocks received: 1                                
Balance: 0.00, unlocked balance: 0.00
[wallet etnk76]:

So obviously something is going on because it says the there are blocks received - but what are these blocks actually translating into? Also with the linux direct minre we just type start_mining <threads> in the wallet, so we don't really know what pool we are going to?? I've seen some youtube explanatory videos where we go to the pool site (ASIA, US, etc) and type in our wallet ID. So how would we do this with the Linux Direct Miner? Thoughts?

Balance showing as 0

I have been using this wallet since day one. And have synced it fully today 2/12/2017 and my balance is showing as 0 after quite a fair bit of mining. Weeks and weeks worth, I'm certain the pools have paid out the figures as they are quite high.

I have noticed this is a major problem as there are a lot of people having the issue on forums/youtube videos.

Has all this mining been wasted?

wallet-rpc returns "not found" when trying to lookup a wallet-address

I have issues getting stats for wallet addresses.
The redis-server is running on port 6379 and the wallet-rpc also on port 8082.
Nevertheless I can't get the stats working on our pool ? It always returns not found?
I have tried to debug the code lib/api.js

if (urlParts.query.longpoll === 'true'){ redisClient.exists(config.coin + ':workers:' + address, function(error, result){ if (!result){ response.end(JSON.stringify({error: 'not found'})); return; } addressConnections[address] = response; response.on('finish', function(){ delete addressConnections[address]; }) }); }
Somehow the redisClient doesn't find the worker with linked address ? I have started the wallet-rpc with following command succesfully

./electroneum-wallet-rpc --wallet-file WalletName --password mypwd --rpc-bind-port 8082 --daemon-address 127.0.0.1:26968

Would be glad if someone could help me out with this

Electroneum windows service name

The service under Windows (electroneumd --install-service) overwrite the Monero daemon service since they both have the same name.

That would be a good idea to rename the service "Electroneum Daemon" instead of "Monero Daemon"

The money that is not collected in the pool

After the synchronization is completed, the coin that can't get out of the pool has been 0

Did not receive the sms

Hello
I didn't received my sms for confirmation of mobile
the entered number is my own and the correct one
Bad Gate 502 all the time during the relaunch!
Raise your qouta in the AWS services

Deamon up to date but balance not correct

Seem like somethings wrong with the blockchain on local machine. The deamon showed up to date, but the balance is missing 1 or 2 transactions.

Where is the blockchain download location on Windows 10?

wallet-rpc randomly detaches from the daemon

Hey,

does anybody know why the wallet-rpc would randomly detach from the daemon?
After those detaches the wallet-rpc is out of sync and wont sync again untill its restarted.

(and sorry if this is the wrong section/repo)

make release-test reply this

[ 60%] Building CXX object tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o
/home/privacy/electroneum/tests/core_tests/block_validation.cpp: In function ‘bool {anonymous}::lift_up_difficulty(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_objectcryptonote::block, serialized_objectcryptonote::transaction, event_visitor_settings> >&, std::vector&, std::vector&, test_generator&, size_t, cryptonote::block, const cryptonote::account_base&)’:
/home/privacy/electroneum/tests/core_tests/block_validation.cpp:48:85: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
type diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY ^
/home/privacy/electroneum/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_invalid_nonce::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_objectcryptonote::block, serialized_objectcryptonote::transaction, event_visitor_settings> >&) const’:
/home/privacy/electroneum/tests/core_tests/block_validation.cpp:178:81: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
type diffic = next_difficulty(timestamps, commulative_difficulties,DIFFICULTY ^
In file included from /home/privacy/electroneum/src/cryptonote_basic/cryptonote_basic.h:47:0,
from /home/privacy/electroneum/src/cryptonote_basic/account.h:33,
from /home/privacy/electroneum/src/cryptonote_basic/account_boost_serialization.h:33,
from /home/privacy/electroneum/tests/core_tests/chaingen.h:47,
from /home/privacy/electroneum/tests/core_tests/block_validation.cpp:31:
/home/privacy/electroneum/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_unlock_time_is_timestamp_in_future::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_objectcryptonote::block, serialized_objectcryptonote::transaction, event_visitor_settings> >&) const’:
/home/privacy/electroneum/src/cryptonote_config.h:85:57: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
#define DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN DIFFICULTY_TARGET_V1 // ^
/home/privacy/electroneum/tests/core_tests/block_validation.cpp:267:87: note: in expansion of macro ‘DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN’
time = blk_0.timestamp + 3 * CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW * DIFFICULTY_ ^
/home/privacy/electroneum/tests/core_tests/block_validation.cpp: In member function ‘bool gen_block_invalid_binary_format::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_objectcryptonote::block, serialized_objectcryptonote::transaction, event_visitor_settings> >&) const’:
/home/privacy/electroneum/tests/core_tests/block_validation.cpp:575:67: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TA ^
/home/privacy/electroneum/tests/core_tests/block_validation.cpp:590:65: error: ‘DIFFICULTY_TARGET_V1’ was not declared in this scope
diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARG ^
tests/core_tests/CMakeFiles/coretests.dir/build.make:86: recipe for target 'tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o' failed
make[3]: *** [tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o] Error 1
make[3]: Leaving directory '/home/privacy/electroneum/build/release'
CMakeFiles/Makefile2:2232: recipe for target 'tests/core_tests/CMakeFiles/coretests.dir/all' failed
make[2]: *** [tests/core_tests/CMakeFiles/coretests.dir/all] Error 2
make[2]: Leaving directory '/home/privacy/electroneum/build/release'
Makefile:138: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/privacy/electroneum/build/release'
Makefile:58: recipe for target 'release-test' failed
make: *** [release-test] Error 2
privacy@dallas-tx-datacenter:~/electroneum$

electroneumd.exe closes/fail

Hi there,

I'm new in this, and when i tried to sync to etn blockchain, console gimme this:

"2017-12-17 22:10:09.756 11692 INFO global src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-53f8b3fa)
2017-12-17 22:10:09.756 11692 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol...
2017-12-17 22:10:09.756 11692 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2017-12-17 22:10:09.756 11692 INFO global src/daemon/p2p.h:63 Initializing p2p server...
2017-12-17 22:10:14.129 11692 INFO global src/daemon/p2p.h:68 P2p server initialized OK
2017-12-17 22:10:14.129 11692 INFO global src/daemon/rpc.h:58 Initializing core rpc server...
2017-12-17 22:10:14.129 11692 INFO global contrib/epee/include/net/http_server_impl_base.h:70 Binding on 127.0.0.1:26968
2017-12-17 22:10:14.129 11692 INFO global src/daemon/rpc.h:63 Core rpc server initialized OK on port: 26968
2017-12-17 22:10:14.129 11692 INFO global src/daemon/core.h:73 Initializing core...
2017-12-17 22:10:14.129 11692 INFO global src/cryptonote_core/cryptonote_core.cpp:323 Loading blockchain from folder C:\ProgramData\electroneum\lmdb ...
2017-12-17 22:10:14.129 11692 WARN blockchain.db.lmdb src/blockchain_db/lmdb/db_lmdb.cpp:72 Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-17 22:10:14.129 11692 ERROR cn src/cryptonote_core/cryptonote_core.cpp:399 Error opening database: Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-17 22:10:14.129 11692 INFO global src/daemon/rpc.h:90 Deinitializing rpc server...
2017-12-17 22:10:14.129 11692 INFO global src/daemon/p2p.h:90 Deinitializing p2p...
2017-12-17 22:10:14.160 11692 INFO global src/daemon/core.h:89 Deinitializing core...
2017-12-17 22:10:14.160 11692 ERROR daemon src/daemon/core.h:94 Failed to deinitialize core...
2017-12-17 22:10:14.160 11692 INFO global src/daemon/protocol.h:77 Stopping cryptonote protocol...
2017-12-17 22:10:14.160 11692 INFO global src/daemon/protocol.h:81 Cryptonote protocol stopped successfully"

Anyone can help me?

Thanks in advance,
Marcos

electroneumd.exe crashing

I was running electroneumd.exe to sync with the network, when my pc froze and had to do a hard restart. Since than, I cannot run electroneumd.exe, it crashes right away. I was able to capture this screen with a slomo video. Any help would be greatly appreciated.

https://imgur.com/x0AvyMa

Thanks

Unable to see transferred ETN from online wallet to paper wallet.

I was able to withdraw coins I bought from Cryptopia into my paper wallet much earlier on with no hassle and each time I type balance that amount reflects with no issues. Unfortunately I've been trying to transfer my ETN coins from my online wallet to that same paper wallet since Wednesday. In my online wallet it shows there has been a debit with a transaction hash, which I entered into the Electroneum blockchain explorer to confirm if that the transfer had been carried out.
Correct me if I'm wrong but I run the electroneumd file (Mac OS), waited for it to sync and run the electroneum-wallet-cli file (via terminal) after sync was complete. Is this the right procedure? Also after doing this I received two error messages, both times I refreshed the wallet:

Error: refresh failed: no connection to daemon. Please make sure daemon is running.. Blocks received: 0
Error: wallet failed to connect to daemon: http://localhost:26968. Daemon either is not started or wrong port was passed. Please make sure daemon is running or restart the wallet with the correct daemon address.

For the first error my wallet was "out of sync" and for the second one, "no daemon".
And to make matters worse the transferred coins from my online wallet are still not showing in my paper wallet.

Linux Wallet Slow Synchronize

The Linux RPC and CLI wallets synchronize extremely slow.
It sync 999-1000 blocks and pause for 4-5 minutes, before synchronizing 1000 more.

Environment: Docker, Rancher.

Wallet Start Command:
/daemon/electroneum-wallet-rpc --daemon-address=http://daemon.address:19734 --wallet-file=/daemon/data/electroneum.wallet --rpc-bind-ip=0.0.0.0 --rpc-bind-port=19735 --confirm-external-bind --trusted-daemon --disable-rpc-login --password '<removed>' --log-level=2

	src/wallet/wallet2.cpp:1131	Processed block: <09fbc3beb4e8ddebb8ad0c45af92d1f8b1a3165e487ab519fff81624036d068a>, height 986, 2(2/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.369	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <485a18d322835ecbb43dc74539b11993364ba08010a7d09fcaddc82cd49d46ea>, height 987, 1(1/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.388	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <1e5cbac9ca7dbe844d84adbea313e4a1ec7e98684410ca28e3152c1826480e5d>, height 988, 1(1/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.390	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <f258f0ec17cf95aa26787a873ba2ecd589b484a57d17f026dcebc7b63f2ba04b>, height 989, 1(1/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.450	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <b800d1ea60bfe5ebe7209cb40dabb7b739a4d9cdadda333e16778fea4b4274fa>, height 990, 58(3/55)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.454	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <17ad4222bffc62bb7b643c63122775ce95c6b4c4003408b3d70e84e946c6e39e>, height 991, 3(3/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.480	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <51172721c659811fb0774583f01ebeb800c95da0007abb99716ba847fef93bd8>, height 992, 2(2/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.481	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <84d119184e2209b4ffb1438b7b1aee8d3e47513f5e0c81f8af9fe55b877831d8>, height 993, 1(1/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.485	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <40f25ad0ecc532da95f4f8b58cb434e58cf21ccff0d9b76c75f9bef51bebf308>, height 994, 3(3/0)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.893	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <b24944f44364ee198313d0585bf0753e5b8cca1e098e5b8a63544e81c0ea2eb0>, height 995, 408(3/405)ms
12/6/2017 5:06:08 PM2017-12-06 16:06:08.993	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <a07ba111680f74312f9c0084adda34f94646d823c45b9ec16f8840f99377f6ca>, height 996, 100(5/95)ms
12/6/2017 5:06:09 PM2017-12-06 16:06:09.503	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <9bd669524aaa3c366e363e15b50d50c570b53cb5a847fbb4cc1289afbbfb2478>, height 997, 509(5/504)ms
12/6/2017 5:06:09 PM2017-12-06 16:06:09.760	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <df49f9e0021f37b0d9d156c9476b29b1a1dc409292a2433ed1023b43d2173be9>, height 998, 257(1/256)ms
12/6/2017 5:06:09 PM2017-12-06 16:06:09.761	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <9aa1e7165b7ffa29838f6fd4384c15cf9cf8a3a6707bba848ad8ce84aa83bcb9>, height 999, 2(2/0)ms
12/6/2017 5:10:51 PM2017-12-06 16:10:51.895	    7f0ad714b700	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1202	Daemon is recent enough, asking for pruned blocks
12/6/2017 5:10:51 PM2017-12-06 16:10:51.901	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1311	Block is already in blockchain: 9bd669524aaa3c366e363e15b50d50c570b53cb5a847fbb4cc1289afbbfb2478
12/6/2017 5:10:51 PM2017-12-06 16:10:51.902	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1311	Block is already in blockchain: df49f9e0021f37b0d9d156c9476b29b1a1dc409292a2433ed1023b43d2173be9
12/6/2017 5:10:51 PM2017-12-06 16:10:51.902	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1311	Block is already in blockchain: 9aa1e7165b7ffa29838f6fd4384c15cf9cf8a3a6707bba848ad8ce84aa83bcb9
12/6/2017 5:10:52 PM2017-12-06 16:10:52.164	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <d7ec8a6329948fee02cdc95b13f286bd69fe9540863a80dfff7fe14940756293>, height 1000, 262(1/261)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.285	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <b4ca0af136d679322e2082288508f299c955dd2f376a16e9a13c863f438a6caa>, height 1001, 115(1/114)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.525	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <234cd76b6366518376786b67469d319ec6a65b5d388a3828de8c0819f6a6aafe>, height 1002, 240(5/235)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.526	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <96be1100cb21ee06e82d3e03344050482d334c3afb4f918797dd52bde8bb58e3>, height 1003, 1(1/0)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.571	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <a434e5a43b62b33ad3610fc83f5328ade5df7d9d9599d83213736e85f30c55c7>, height 1004, 45(3/42)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.592	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <54bd641000c3a9be567c46b2512dd1664241e815248be5fb086a4eaabd25ffb7>, height 1005, 13(1/12)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.607	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <bc09ed6d05297562d4b8fae4c8a7beaf85f34353a5451955bb3bd308084ad708>, height 1006, 15(1/14)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.609	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <510d7d116e6877eda39b574e39823adf04ab7b8f47f5f7994318f543cff975a4>, height 1007, 2(2/0)ms
12/6/2017 5:10:52 PM2017-12-06 16:10:52.840	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <dba40166420d007cdbdaf2bec8d7b74d186815123229343688cc5a53b15da5d4>, height 1008, 230(1/229)ms
12/6/2017 5:10:53 PM2017-12-06 16:10:53.100	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <a072eaf2b0e977c7eb8b7119ee7fcb971434411c2932b4dffaa3407ee3d8c271>, height 1009, 260(1/259)ms
12/6/2017 5:10:53 PM2017-12-06 16:10:53.402	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <be03786da099dd109a969c933a99e20f797e49ba4a1e5cf6de80df27e3403ef9>, height 1010, 301(1/300)ms
12/6/2017 5:10:53 PM2017-12-06 16:10:53.603	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <200386d378fc2e5090e6cb43450852a418a912e021e0be73b619cb2ed38cea6e>, height 1011, 201(2/199)ms
12/6/2017 5:10:53 PM2017-12-06 16:10:53.639	    7f0ad88a3740	DEBUG	wallet.wallet2	src/wallet/wallet2.cpp:1131	Processed block: <cdba8f92ecca24ea7fe718e659755880f0510

Electroneumd.exe not syncing : serviced_tcp_initiate: failed to send tcp query

Hello,

When I start electroneumd.exe this is what I get:

2017-12-12 23:50:13.344 1876 INFO global src/daemon/main.cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-unknown)
2017-12-12 23:50:13.344 1876 INFO global src/daemon/protocol.h:55 Initializing cryptonote protocol...
2017-12-12 23:50:13.344 1876 INFO global src/daemon/protocol.h:60 Cryptonote protocol initialized OK
2017-12-12 23:50:13.345 1876 INFO global src/daemon/p2p.h:63 Initializing p2p server...
[1513122614] libunbound[10404:0] error: serviced_tcp_initiate: failed to send tcp query
[1513122614] libunbound[10404:0] error: serviced_tcp_initiate: failed to send tcp query
[1513122614] libunbound[10404:0] error: serviced_tcp_initiate: failed to send tcp query

Any idea what may cause this?

Thank you

electroneumd destroys BC once a week

having electroneumd running in an UBU 16.04 LXC it hangs once a week (roughly) hogs 100% CPU and on restart shows the following error.
the only way out ist to delete the BC, restore from backup and let it sync from that point again.
electroneumd --db-salvage doesn't fix it.

17-12-09 10:15:36.330     7f2dbb857ec0        INFO    global  src/daemon/protocol.h:60        Cryptonote protocol initialized OK                                                                                                          
2017-12-09 10:15:36.331     7f2dbb857ec0        INFO    global  src/daemon/p2p.h:63     Initializing p2p server...                                                                                                                          
2017-12-09 10:15:40.407     7f2dbb857ec0        INFO    global  src/daemon/p2p.h:68     P2p server initialized OK                                                                                                                           
2017-12-09 10:15:40.407     7f2dbb857ec0        INFO    global  src/daemon/rpc.h:58     Initializing core rpc server...                                                                                                                     
2017-12-09 10:15:40.407     7f2dbb857ec0        INFO    global  contrib/epee/include/net/http_server_impl_base.h:70     Binding on 127.0.0.1:26968                                                                                          
2017-12-09 10:15:40.407     7f2dbb857ec0        INFO    global  src/daemon/rpc.h:63     Core rpc server initialized OK on port: 26968                                                                                                       
2017-12-09 10:15:40.407     7f2dbb857ec0        INFO    global  src/daemon/core.h:73    Initializing core...                                                                                                                                
2017-12-09 10:15:40.407     7f2dbb857ec0        INFO    global  src/cryptonote_core/cryptonote_core.cpp:323     Loading blockchain from folder /home/electroneum/.electroneum/lmdb ...                                                      
2017-12-09 10:16:11.485     7f2dbb857ec0        INFO    global  src/cryptonote_core/cryptonote_core.cpp:421     Loading checkpoints                                                                                                         
2017-12-09 10:16:11.791     7f2dbb857ec0        WARN    net.dns src/common/dns_utils.cpp:487    WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2017-12-09 10:16:11.791     7f2dbb857ec0        INFO    global  src/daemon/core.h:78    Core initialized OK
2017-12-09 10:16:11.791     7f2dbb857ec0        INFO    global  src/daemon/rpc.h:68     Starting core rpc server...                                                                                                                         
2017-12-09 10:16:11.792 [SRV_MAIN]      INFO    global  src/daemon/rpc.h:73     Core rpc server started ok                                                                                                                                  
2017-12-09 10:16:11.792 [SRV_MAIN]      INFO    global  src/daemon/p2p.h:78     Starting p2p net loop...                                                                                                                                    
2017-12-09 10:16:12.792 [P2P2]  INFO    global  src/cryptonote_core/cryptonote_core.cpp:1247                                                                                                                                                
**********************************************************************
…
**********************************************************************

2017-12-09 10:16:12.838 [P2P2]  WARN    net.dns src/common/dns_utils.cpp:487    WARNING: no two valid ElectroneumPulse DNS checkpoint records were received
2017-12-09 10:16:13.371 [P2P4]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [159.224.199.37:26967 OUT] Sync data returned a new top block candidate: 58759 -> 59887 [Your node is 1128 blocks (0 days) behind]                                                                                                                                                                                                                                      
SYNCHRONIZATION started                                                                                                                                                                                                                     
2017-12-09 10:22:53.833 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [82.25.30.124:26967 OUT] Sync data returned a new top block candidate: 58759 -> 59892 [Your node is 1133 blocks (0 days) behind]                                                                                                                                                                                                                                        
SYNCHRONIZATION started                                                                                                                                                                                                                     
2017-12-09 10:22:54.882 [P2P1]  WARN    blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:72   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-09 10:22:54.892 [P2P1]  WARN    blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:72   Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid                                           
2017-12-09 10:22:54.899 [P2P1]  ERROR   cn      src/cryptonote_core/cryptonote_core.cpp:1127    Exception at [core::handle_incoming_block()], what=Failed to query m_blocks: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-09 10:22:54.900 [P2P1]  WARN    blockchain.db.lmdb      src/blockchain_db/lmdb/db_lmdb.cpp:72   Failed to commit a transaction to the db: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid
2017-12-09 10:22:54.905 [P2P1]  ERROR   blockchain      src/cryptonote_core/blockchain.cpp:3599 Exception in cleanup_handle_incoming_blocks: Failed to commit a transaction to the db: MDB_BAD_TXN: Transaction must abort, has a child, or is invalid                                                                                                                                                                                                                                  
2017-12-09 10:22:58.491 [P2P8]  ERROR   txpool  src/cryptonote_core/tx_pool.cpp:316     internal error: try to insert duplicate iterator in key_image set                                                                                   
2017-12-09 10:22:58.524 [P2P8]  ERROR   txpool  src/cryptonote_core/tx_pool.cpp:316     internal error: try to insert duplicate iterator in key_image set                                                                                   
2017-12-09 10:24:28.205 [P2P8]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [24.61.241.59:26967 OUT] Sync data returned a new top block candidate: 58759 -> 59893 [Your node is 1134 blocks (0 days) behind]                                                                                                                                                                                                                                        
SYNCHRONIZATION started                                                                                                                                                                                                                     
2017-12-09 10:24:45.577 [P2P5]  INFO    global  src/cryptonote_protocol/cryptonote_protocol_handler.inl:302     [41.216.194.25:26967 OUT] Sync data returned a new top block candidate: 58759 -> 59894 [Your node is 1135 blocks (0 days) behind]                                                                                                                                                                                                                                       
SYNCHRONIZATION started 
stays there forever…

Virus detected via Webroot program

After downloading "win-x64-0.11.0.0.zip" then extracting the files, Webroot found potential virus in all of the extracted .exe files and deleted them. This denies my transfer of Public Wallet to Cryptopia coin exchange. I cannot proceed until this issue is corrected.

Electroneum node list, please, add in comment

29/11/2017

91.107.97.108:4904
175.142.65.149:51704
129.21.89.185:26967
70.76.17.198:26967
178.251.110.84:26967
70.76.17.198:26967

'DIFFICULTY_TARGET_V1' was not declared in this scope

Hi, I'm using Ubuntu 16.04. When I'm trying build repo i get these errors:


[ 56%] Building CXX object tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o
/root/electroneum/tests/core_tests/block_validation.cpp: In function 'bool {anonymous}::lift_up_difficulty(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&, std::vector<long unsigned int>&, std::vector<long unsigned int>&, test_generator&, size_t, cryptonote::block, const cryptonote::account_base&)':
/root/electroneum/tests/core_tests/block_validation.cpp:48:85: error: 'DIFFICULTY_TARGET_V1' was not declared in this scope
 _type diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_
                                                                     ^
/root/electroneum/tests/core_tests/block_validation.cpp: In member function 'bool gen_block_invalid_nonce::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const':
/root/electroneum/tests/core_tests/block_validation.cpp:178:81: error: 'DIFFICULTY_TARGET_V1' was not declared in this scope
 _type diffic = next_difficulty(timestamps, commulative_difficulties,DIFFICULTY_
                                                                     ^
In file included from /root/electroneum/src/cryptonote_basic/cryptonote_basic.h:47:0,
                 from /root/electroneum/src/cryptonote_basic/account.h:33,
                 from /root/electroneum/src/cryptonote_basic/account_boost_serialization.h:33,
                 from /root/electroneum/tests/core_tests/chaingen.h:47,
                 from /root/electroneum/tests/core_tests/block_validation.cpp:3 :
/root/electroneum/tests/core_tests/block_validation.cpp: In member function 'bool gen_block_unlock_time_is_timestamp_in_future::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const':
/root/electroneum/src/cryptonote_config.h:85:57: error: 'DIFFICULTY_TARGET_V1' was not declared in this scope
 #define DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN             DIFFICULTY_TARGET_V1 //
                                                         ^
/root/electroneum/tests/core_tests/block_validation.cpp:267:87: note: in expansion of macro 'DIFFICULTY_BLOCKS_ESTIMATE_TIMESPAN'
 time = blk_0.timestamp + 3 * CRYPTONOTE_MINED_MONEY_UNLOCK_WINDOW * DIFFICULTY_
                                                                     ^
/root/electroneum/tests/core_tests/block_validation.cpp: In member function 'bool gen_block_invalid_binary_format::generate(std::vector<boost::variant<cryptonote::block, cryptonote::transaction, cryptonote::account_base, callback_entry, serialized_object<cryptonote::block>, serialized_object<cryptonote::transaction>, event_visitor_settings> >&) const':
/root/electroneum/tests/core_tests/block_validation.cpp:575:67: error: 'DIFFICULTY_TARGET_V1' was not declared in this scope
     diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TA
                                                                   ^
/root/electroneum/tests/core_tests/block_validation.cpp:590:65: error: 'DIFFICULTY_TARGET_V1' was not declared in this scope
   diffic = next_difficulty(timestamps, cummulative_difficulties,DIFFICULTY_TARG
                                                                 ^
tests/core_tests/CMakeFiles/coretests.dir/build.make:86: recipe for target 'tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o' failed
make[3]: *** [tests/core_tests/CMakeFiles/coretests.dir/block_validation.cpp.o] Error 1
make[3]: Leaving directory '/root/electroneum/build/release'
CMakeFiles/Makefile2:2157: recipe for target 'tests/core_tests/CMakeFiles/coretests.dir/all' failed
make[2]: *** [tests/core_tests/CMakeFiles/coretests.dir/all] Error 2
make[2]: Leaving directory '/root/electroneum/build/release'
Makefile:138: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/root/electroneum/build/release'
Makefile:62: recipe for target 'release-all' failed
make: *** [release-all] Error 2

I tried to use "make" and "make release-static", what can I do with this issue?

electroneumd uses monero file-names, cannot run on same node

electroneumd uses the same file like monerod which hinders them, running side by side on the same node

electroneumd --detach

# in the log:
2017-11-23 16:09:12.237     7f6aaeef9ec0        INFO    stacktrace      src/common/stack_trace.cpp:159
2017-11-23 16:09:12.237     7f6aaeef9ec0        ERROR   daemon  src/daemon/main.cpp:287 Exception in main! Unable to open output file: /tmp/bitmonero.daemon.stdout.stderr

compiling : boost dependency on Centos 7

Centos 7 shipped boost lib is 1.53.

To install boost-devel 1.59 in CentOS7‏, id did the following:
$ sudo wget http://repo.enetres.net/enetres.repo -O /etc/yum.repos.d/enetres.repo
$ wget fr2.rpmfind.net/linux/Mandriva/official/2010.0/x86_64/media/main/release/lib64icu42-4.2.1-1mdv2010.0.x86_64.rpm
$ sudo rpm -ivh lib64icu42-4.2.1-1mdv2010.0.x86_64.rpm
$ sudo yum install boost-devel

no two valid ElectroneumPulse DNS checkpoint records were received

Hi, I have problem with sync electroneum, here is output:

:~/electroneum/build/release/bin# ./electroneumd
2017-11-26 19:49:44.114     7fb3905b9740        INFO    global  src/daemon/main.      cpp:279 Electroneum 'Helium Hydra' (v0.11.0.0-5425662)
2017-11-26 19:49:44.114     7fb3905b9740        INFO    global  src/daemon/proto      col.h:55        Initializing cryptonote protocol...
2017-11-26 19:49:44.114     7fb3905b9740        INFO    global  src/daemon/proto      col.h:60        Cryptonote protocol initialized OK
2017-11-26 19:49:44.114     7fb3905b9740        INFO    global  src/daemon/p2p.h      :63     Initializing p2p server...
2017-11-26 19:49:49.536     7fb3905b9740        INFO    global  src/daemon/p2p.h      :68     P2p server initialized OK
2017-11-26 19:49:49.536     7fb3905b9740        INFO    global  src/daemon/rpc.h      :58     Initializing core rpc server...
2017-11-26 19:49:49.536     7fb3905b9740        INFO    global  contrib/epee/inc      lude/net/http_server_impl_base.h:70     Binding on 127.0.0.1:26968
2017-11-26 19:49:49.536     7fb3905b9740        INFO    global  src/daemon/rpc.h      :63     Core rpc server initialized OK on port: 26968
2017-11-26 19:49:49.536     7fb3905b9740        INFO    global  src/daemon/core.      h:73    Initializing core...
2017-11-26 19:49:49.536     7fb3905b9740        INFO    global  src/cryptonote_c      ore/cryptonote_core.cpp:323     Loading blockchain from folder /root/.electroneu      m/lmdb ...
2017-11-26 19:49:49.537     7fb3905b9740        WARN    blockchain.db.lmdb     s      rc/blockchain_db/lmdb/db_lmdb.cpp:72    Error attempting to retrieve a hard fork       version at height 0 from the db: MDB_NOTFOUND: No matching key/data pair found
2017-11-26 19:49:49.592     7fb3905b9740        INFO    global  src/cryptonote_c      ore/cryptonote_core.cpp:421     Loading checkpoints
2017-11-26 19:49:49.618     7fb3905b9740        WARN    net.dns src/common/dns_u      tils.cpp:487    WARNING: no two valid ElectroneumPulse DNS checkpoint records we      re received
2017-11-26 19:49:49.618     7fb3905b9740        INFO    global  src/daemon/core.      h:78    Core initialized OK
2017-11-26 19:49:49.618     7fb3905b9740        INFO    global  src/daemon/rpc.h      :68     Starting core rpc server...
2017-11-26 19:49:49.618 [SRV_MAIN]      INFO    global  src/daemon/rpc.h:73    C      ore rpc server started ok
2017-11-26 19:49:49.618 [SRV_MAIN]      INFO    global  src/daemon/p2p.h:78    S      tarting p2p net loop...
2017-11-26 19:49:50.619 [P2P1]  INFO    global  src/cryptonote_core/cryptonote_c      ore.cpp:1247
**********************************************************************
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.
**********************************************************************

2017-11-26 19:49:50.645 [P2P1]  WARN    net.dns src/common/dns_utils.cpp:487   W      ARNING: no two valid ElectroneumPulse DNS checkpoint records were received

electroneum / electroneum Goto Github PK

electroneum's Introduction

Electroneum is a Fast, Secure, Mobile Based Cryptocurrency

Table of Contents

Development Resources

Building from Source

Software Releases and Pre-compiled Downloads

Running an Electroneum Node

Technical Documentation

Smartchain Migration

Vulnerability Response Process

License

Copyright

electroneum's People

Contributors

Stargazers

Watchers

Forkers

electroneum's Issues

Recommend Projects

Recommend Topics

Recommend Org