2015-01-05 19:30:17 +00:00
|
|
|
/// @file
|
|
|
|
/// @author rfree (current maintainer/user in monero.cc project - most of code is from CryptoNote)
|
2018-01-19 07:54:14 +00:00
|
|
|
/// @brief This is the original cryptonote protocol network-events handler, modified by us
|
2015-01-05 19:30:17 +00:00
|
|
|
|
2019-03-05 21:05:34 +00:00
|
|
|
// Copyright (c) 2014-2019, The Monero Project
|
2014-07-23 13:03:52 +00:00
|
|
|
//
|
|
|
|
// All rights reserved.
|
|
|
|
//
|
|
|
|
// Redistribution and use in source and binary forms, with or without modification, are
|
|
|
|
// permitted provided that the following conditions are met:
|
|
|
|
//
|
|
|
|
// 1. Redistributions of source code must retain the above copyright notice, this list of
|
|
|
|
// conditions and the following disclaimer.
|
|
|
|
//
|
|
|
|
// 2. Redistributions in binary form must reproduce the above copyright notice, this list
|
|
|
|
// of conditions and the following disclaimer in the documentation and/or other
|
|
|
|
// materials provided with the distribution.
|
|
|
|
//
|
|
|
|
// 3. Neither the name of the copyright holder nor the names of its contributors may be
|
|
|
|
// used to endorse or promote products derived from this software without specific
|
|
|
|
// prior written permission.
|
|
|
|
//
|
|
|
|
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
|
|
|
|
// EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
|
|
|
|
// MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
|
|
|
|
// THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
|
|
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
|
|
|
|
// PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
|
|
// INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
|
|
|
|
// STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
|
|
|
|
// THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
//
|
|
|
|
// Parts of this file are originally copyright (c) 2012-2013 The Cryptonote developers
|
2014-03-03 22:07:58 +00:00
|
|
|
|
|
|
|
#pragma once
|
|
|
|
|
|
|
|
#include <boost/program_options/variables_map.hpp>
|
2014-07-18 23:33:03 +00:00
|
|
|
#include <string>
|
2014-03-03 22:07:58 +00:00
|
|
|
|
2017-08-16 18:27:16 +00:00
|
|
|
#include "math_helper.h"
|
2014-03-03 22:07:58 +00:00
|
|
|
#include "storages/levin_abstract_invoke2.h"
|
|
|
|
#include "warnings.h"
|
|
|
|
#include "cryptonote_protocol_defs.h"
|
|
|
|
#include "cryptonote_protocol_handler_common.h"
|
2017-07-02 21:41:15 +00:00
|
|
|
#include "block_queue.h"
|
Pruning
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
2018-04-29 22:30:51 +00:00
|
|
|
#include "common/perf_timer.h"
|
2017-01-26 15:07:23 +00:00
|
|
|
#include "cryptonote_basic/connection_context.h"
|
|
|
|
#include "cryptonote_basic/cryptonote_stat_info.h"
|
2015-02-12 19:59:39 +00:00
|
|
|
#include <boost/circular_buffer.hpp>
|
2014-03-03 22:07:58 +00:00
|
|
|
|
|
|
|
PUSH_WARNINGS
|
|
|
|
DISABLE_VS_WARNINGS(4355)
|
|
|
|
|
2015-02-20 21:28:03 +00:00
|
|
|
#define LOCALHOST_INT 2130706433
|
|
|
|
|
2014-03-03 22:07:58 +00:00
|
|
|
namespace cryptonote
|
|
|
|
{
|
|
|
|
|
2015-01-05 19:30:17 +00:00
|
|
|
class cryptonote_protocol_handler_base_pimpl;
|
|
|
|
class cryptonote_protocol_handler_base {
|
|
|
|
private:
|
|
|
|
std::unique_ptr<cryptonote_protocol_handler_base_pimpl> mI;
|
|
|
|
|
|
|
|
public:
|
|
|
|
cryptonote_protocol_handler_base();
|
|
|
|
virtual ~cryptonote_protocol_handler_base();
|
|
|
|
void handler_request_blocks_history(std::list<crypto::hash>& ids); // before asking for list of objects, we can change the list still
|
|
|
|
void handler_response_blocks_now(size_t packet_size);
|
|
|
|
|
2015-02-12 19:59:39 +00:00
|
|
|
virtual double get_avg_block_size() = 0;
|
2015-01-05 19:30:17 +00:00
|
|
|
virtual double estimate_one_block_size() noexcept; // for estimating size of blocks to download
|
|
|
|
};
|
|
|
|
|
2014-03-03 22:07:58 +00:00
|
|
|
template<class t_core>
|
2015-01-05 19:30:17 +00:00
|
|
|
class t_cryptonote_protocol_handler: public i_cryptonote_protocol, cryptonote_protocol_handler_base
|
2014-03-20 11:46:11 +00:00
|
|
|
{
|
2014-03-03 22:07:58 +00:00
|
|
|
public:
|
|
|
|
typedef cryptonote_connection_context connection_context;
|
|
|
|
typedef core_stat_info stat_info;
|
|
|
|
typedef t_cryptonote_protocol_handler<t_core> cryptonote_protocol_handler;
|
|
|
|
typedef CORE_SYNC_DATA payload_type;
|
|
|
|
|
2018-01-25 13:35:17 +00:00
|
|
|
t_cryptonote_protocol_handler(t_core& rcore, nodetool::i_p2p_endpoint<connection_context>* p_net_layout, bool offline = false);
|
2014-03-03 22:07:58 +00:00
|
|
|
|
|
|
|
BEGIN_INVOKE_MAP2(cryptonote_protocol_handler)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_NEW_BLOCK, &cryptonote_protocol_handler::handle_notify_new_block)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_NEW_TRANSACTIONS, &cryptonote_protocol_handler::handle_notify_new_transactions)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_REQUEST_GET_OBJECTS, &cryptonote_protocol_handler::handle_request_get_objects)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_RESPONSE_GET_OBJECTS, &cryptonote_protocol_handler::handle_response_get_objects)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_REQUEST_CHAIN, &cryptonote_protocol_handler::handle_request_chain)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_RESPONSE_CHAIN_ENTRY, &cryptonote_protocol_handler::handle_response_chain_entry)
|
2016-10-26 19:00:08 +00:00
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_NEW_FLUFFY_BLOCK, &cryptonote_protocol_handler::handle_notify_new_fluffy_block)
|
|
|
|
HANDLE_NOTIFY_T2(NOTIFY_REQUEST_FLUFFY_MISSING_TX, &cryptonote_protocol_handler::handle_request_fluffy_missing_tx)
|
2014-03-03 22:07:58 +00:00
|
|
|
END_INVOKE_MAP2()
|
|
|
|
|
|
|
|
bool on_idle();
|
|
|
|
bool init(const boost::program_options::variables_map& vm);
|
|
|
|
bool deinit();
|
|
|
|
void set_p2p_endpoint(nodetool::i_p2p_endpoint<connection_context>* p2p);
|
|
|
|
//bool process_handshake_data(const blobdata& data, cryptonote_connection_context& context);
|
|
|
|
bool process_payload_sync_data(const CORE_SYNC_DATA& hshd, cryptonote_connection_context& context, bool is_inital);
|
|
|
|
bool get_payload_sync_data(blobdata& data);
|
|
|
|
bool get_payload_sync_data(CORE_SYNC_DATA& hshd);
|
|
|
|
bool get_stat_info(core_stat_info& stat_inf);
|
|
|
|
bool on_callback(cryptonote_connection_context& context);
|
|
|
|
t_core& get_core(){return m_core;}
|
2014-03-20 11:46:11 +00:00
|
|
|
bool is_synchronized(){return m_synchronized;}
|
|
|
|
void log_connections();
|
2014-07-18 23:33:03 +00:00
|
|
|
std::list<connection_info> get_connections();
|
2017-07-02 21:41:15 +00:00
|
|
|
const block_queue &get_block_queue() const { return m_block_queue; }
|
2016-12-04 12:27:45 +00:00
|
|
|
void stop();
|
2017-08-18 19:14:23 +00:00
|
|
|
void on_connection_close(cryptonote_connection_context &context);
|
Pruning
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
2018-04-29 22:30:51 +00:00
|
|
|
void set_max_out_peers(unsigned int max) { m_max_out_peers = max; }
|
|
|
|
std::string get_peers_overview() const;
|
|
|
|
std::pair<uint32_t, uint32_t> get_next_needed_pruning_stripe() const;
|
|
|
|
bool needs_new_sync_connections() const;
|
2014-03-03 22:07:58 +00:00
|
|
|
private:
|
|
|
|
//----------------- commands handlers ----------------------------------------------
|
|
|
|
int handle_notify_new_block(int command, NOTIFY_NEW_BLOCK::request& arg, cryptonote_connection_context& context);
|
|
|
|
int handle_notify_new_transactions(int command, NOTIFY_NEW_TRANSACTIONS::request& arg, cryptonote_connection_context& context);
|
|
|
|
int handle_request_get_objects(int command, NOTIFY_REQUEST_GET_OBJECTS::request& arg, cryptonote_connection_context& context);
|
|
|
|
int handle_response_get_objects(int command, NOTIFY_RESPONSE_GET_OBJECTS::request& arg, cryptonote_connection_context& context);
|
|
|
|
int handle_request_chain(int command, NOTIFY_REQUEST_CHAIN::request& arg, cryptonote_connection_context& context);
|
|
|
|
int handle_response_chain_entry(int command, NOTIFY_RESPONSE_CHAIN_ENTRY::request& arg, cryptonote_connection_context& context);
|
2016-10-26 19:00:08 +00:00
|
|
|
int handle_notify_new_fluffy_block(int command, NOTIFY_NEW_FLUFFY_BLOCK::request& arg, cryptonote_connection_context& context);
|
|
|
|
int handle_request_fluffy_missing_tx(int command, NOTIFY_REQUEST_FLUFFY_MISSING_TX::request& arg, cryptonote_connection_context& context);
|
|
|
|
|
2014-03-03 22:07:58 +00:00
|
|
|
//----------------- i_bc_protocol_layout ---------------------------------------
|
|
|
|
virtual bool relay_block(NOTIFY_NEW_BLOCK::request& arg, cryptonote_connection_context& exclude_context);
|
|
|
|
virtual bool relay_transactions(NOTIFY_NEW_TRANSACTIONS::request& arg, cryptonote_connection_context& exclude_context);
|
|
|
|
//----------------------------------------------------------------------------------
|
|
|
|
//bool get_payload_sync_data(HANDSHAKE_DATA::request& hshd, cryptonote_connection_context& context);
|
Pruning
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
2018-04-29 22:30:51 +00:00
|
|
|
bool should_drop_connection(cryptonote_connection_context& context, uint32_t next_stripe);
|
2017-07-02 21:41:15 +00:00
|
|
|
bool request_missing_objects(cryptonote_connection_context& context, bool check_having_blocks, bool force_next_span = false);
|
2014-03-03 22:07:58 +00:00
|
|
|
size_t get_synchronizing_connections_count();
|
|
|
|
bool on_connection_synchronized();
|
Pruning
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
2018-04-29 22:30:51 +00:00
|
|
|
bool should_download_next_span(cryptonote_connection_context& context, bool standby);
|
2017-08-09 19:49:24 +00:00
|
|
|
void drop_connection(cryptonote_connection_context &context, bool add_fail, bool flush_all_spans);
|
2017-08-16 18:27:16 +00:00
|
|
|
bool kick_idle_peers();
|
2018-12-07 12:32:50 +00:00
|
|
|
bool check_standby_peers();
|
2017-08-18 19:14:23 +00:00
|
|
|
int try_add_next_blocks(cryptonote_connection_context &context);
|
Pruning
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
2018-04-29 22:30:51 +00:00
|
|
|
void notify_new_stripe(cryptonote_connection_context &context, uint32_t stripe);
|
|
|
|
void skip_unneeded_hashes(cryptonote_connection_context& context, bool check_block_queue) const;
|
2017-08-09 19:49:24 +00:00
|
|
|
|
2014-03-03 22:07:58 +00:00
|
|
|
t_core& m_core;
|
|
|
|
|
|
|
|
nodetool::p2p_endpoint_stub<connection_context> m_p2p_stub;
|
|
|
|
nodetool::i_p2p_endpoint<connection_context>* m_p2p;
|
|
|
|
std::atomic<uint32_t> m_syncronized_connections_count;
|
2014-03-20 11:46:11 +00:00
|
|
|
std::atomic<bool> m_synchronized;
|
2016-12-04 12:27:45 +00:00
|
|
|
std::atomic<bool> m_stopping;
|
2017-07-02 21:41:15 +00:00
|
|
|
boost::mutex m_sync_lock;
|
|
|
|
block_queue m_block_queue;
|
2017-08-16 18:27:16 +00:00
|
|
|
epee::math_helper::once_a_time_seconds<30> m_idle_peer_kicker;
|
2018-12-07 12:32:50 +00:00
|
|
|
epee::math_helper::once_a_time_milliseconds<100> m_standby_checker;
|
Pruning
The blockchain prunes seven eighths of prunable tx data.
This saves about two thirds of the blockchain size, while
keeping the node useful as a sync source for an eighth
of the blockchain.
No other data is currently pruned.
There are three ways to prune a blockchain:
- run monerod with --prune-blockchain
- run "prune_blockchain" in the monerod console
- run the monero-blockchain-prune utility
The first two will prune in place. Due to how LMDB works, this
will not reduce the blockchain size on disk. Instead, it will
mark parts of the file as free, so that future data will use
that free space, causing the file to not grow until free space
grows scarce.
The third way will create a second database, a pruned copy of
the original one. Since this is a new file, this one will be
smaller than the original one.
Once the database is pruned, it will stay pruned as it syncs.
That is, there is no need to use --prune-blockchain again, etc.
2018-04-29 22:30:51 +00:00
|
|
|
std::atomic<unsigned int> m_max_out_peers;
|
|
|
|
tools::PerformanceTimer m_sync_timer, m_add_timer;
|
|
|
|
uint64_t m_last_add_end_time;
|
|
|
|
uint64_t m_sync_spans_downloaded, m_sync_old_spans_downloaded, m_sync_bad_spans_downloaded;
|
|
|
|
uint64_t m_sync_download_chain_size, m_sync_download_objects_size;
|
|
|
|
size_t m_block_download_max_size;
|
2014-03-03 22:07:58 +00:00
|
|
|
|
2016-03-11 12:25:28 +00:00
|
|
|
boost::mutex m_buffer_mutex;
|
2015-02-12 19:59:39 +00:00
|
|
|
double get_avg_block_size();
|
|
|
|
boost::circular_buffer<size_t> m_avg_buffer = boost::circular_buffer<size_t>(10);
|
2015-01-05 19:30:17 +00:00
|
|
|
|
2016-12-04 13:13:54 +00:00
|
|
|
template<class t_parameter>
|
|
|
|
bool post_notify(typename t_parameter::request& arg, cryptonote_connection_context& context)
|
2014-03-03 22:07:58 +00:00
|
|
|
{
|
2016-12-04 13:13:54 +00:00
|
|
|
LOG_PRINT_L2("[" << epee::net_utils::print_connection_context_short(context) << "] post " << typeid(t_parameter).name() << " -->");
|
2014-03-03 22:07:58 +00:00
|
|
|
std::string blob;
|
|
|
|
epee::serialization::store_t_to_binary(arg, blob);
|
2015-01-05 19:30:17 +00:00
|
|
|
//handler_response_blocks_now(blob.size()); // XXX
|
2018-12-06 18:04:33 +00:00
|
|
|
return m_p2p->invoke_notify_to_peer(t_parameter::ID, epee::strspan<uint8_t>(blob), context);
|
2014-03-03 22:07:58 +00:00
|
|
|
}
|
|
|
|
};
|
2015-01-05 19:30:17 +00:00
|
|
|
|
|
|
|
} // namespace
|
2014-03-03 22:07:58 +00:00
|
|
|
|
|
|
|
POP_WARNINGS
|