| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |/
|
|
|
|
| |
This skips the vast majority of "dust" output amounts with just
one instance on the chain. Clocks in at 0.15% of the original
time on testnet.
|
| | |
|
| |
|
|
|
|
| |
This function isn't used in the codebase.
Signed-off-by: Jean Pierre Dudey <jeandudey@hotmail.com>
|
| | |
|
| |\
| |
| |
| | |
42f86624 rpc: expose recent median block size in getinfo (moneromooo-monero)
|
| | | |
|
| |/ |
|
| |\
| |
| |
| | |
ae860230 Fix exceptions not finding txpool txes when relaying (moneromooo-monero)
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This patch allows to filter out sensitive information for queries that rely on the pool state, when running in restricted mode.
This filtering is only applied to data sent back to RPC queries. Results of inline commands typed locally in the daemon are not affected.
In practice, when running with `--restricted-rpc`:
* get_transaction_pool will list relayed transactions with the fields "last relayed time" and "received time" set to zero.
* get_transaction_pool will not list transaction that have do_not_relay set to true, and will not list key images that are used only for such transactions
* get_transaction_pool_hashes.bin will not list such transaction
* get_transaction_pool_stats will not count such transactions in any of the aggregated values that are computed
The implementation does not make filtering the default, so developers should be mindful of this if they add new RPC functionality.
Fixes #2590.
|
| |\
| |
| |
| | |
69ce33f2 core: fix failure to sync when a tx is already in the pool (moneromooo-monero)
|
| | | |
|
| |\ \
| |/
|/|
| | |
7adceee6 precomputed block hashes are now in blocks of N (currently 256) (moneromooo-monero)
|
| | |
| |
| |
| | |
This shaves a lot of space off binaries
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit refactors some of the rpc-related functions in the
Blockchain class to be more composable. This change was made
in order to make implementing the new zmq rpc easier without
trampling on the old rpc.
New functions:
Blockchain::get_num_mature_outputs
Blockchain::get_random_outputs
Blockchain::get_output_key
Blockchain::get_output_key_mask_unlocked
Blockchain::find_blockchain_supplement (overload)
functions which previously had this functionality inline now call these
functions as necessary.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
If monerod is started with default sync mode, set it to SAFE after
synchronization completes. Set it back to FAST if synchronization
restarts (e.g. because another peer has a longer blockchain).
If monerod is started with an explicit sync mode, none of this
automation takes effect.
|
| |
|
|
| |
Not used yet.
|
| |\
| |
| |
| | |
d732c73e blockchain: remove a few unused variables (moneromooo-monero)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
We won't even talk to a peer which claims a wrong version
for its top block. This will avoid syncing to known bad
peers in the first place.
Also add IP fails when failing to verify a block.
|
| |\ \
| | |
| | |
| | | |
5d91b26c blockchain: skip checking tx semantics in embedded block hash range (moneromooo-monero)
|
| | |/
| |
| |
| |
| | |
If the txes are bad, this'll be picked up by the block hash mismatch
since the tx merkle root is part of the block hash.
|
| |/
|
|
|
|
|
|
|
| |
If the number of blocks to check was not a multiple of the
number of preparation threads, the last few blocks would
not be included in the threaded long hash calculation.
Those would still get calculated when the block gets added
to the chain, however, so this was only a tiny performance
hit, rather than a security bug.
|
| |
|
|
| |
set_user_options()
|
| |
|
|
| |
Avoids exception spam for the "nope, not found" case
|
| |
|
|
|
| |
Changed Blockchain::for_all_blocks() to for_blocks_range()
Operate on blockchain in-place instead of building a copy first.
|
| |\
| |
| |
| | |
b52abd13 Move txpool to the database (moneromooo-monero)
|
| | |
| |
| |
| |
| |
| |
| | |
Integration could go further (ie, return_tx_to_pool calls should
not be needed anymore, possibly other things).
poolstate.bin is now obsolete.
|
| |/
|
|
| |
Only works from V5 fork onward - returns 0 before that block.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Minimum mixin 4 and enforced ringct is moved from v5 to v6.
v5 is now used for an increased minimum block size (from 60000
to 300000) to cater for larger typical/minimum transaction size.
The fee algorithm is also changed to decrease the base per kB
fee, and add a cheap tier for those transactions which we do
not care if they get delayed (or even included in a block).
|
| |
|
|
| |
BlockchainDB functions virtual again to avoid missing symbols error
|
| |
|
|
|
| |
should fix a cross dependency betewen cryptonote_basic and
blockchain_db
|
| | |
|
| |
|
|
| |
This speeds up operations such as serving blocks to syncing peers
|
| | |
|
| | |
|
| |
|
|
| |
It was always set to false, even for orphan blocks
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fee will vary based on the base reward and the current
block size limit:
fee = (R/R0) * (M0/M) * F0
R: base reward
R0: reference base reward (10 monero)
M: block size limit
M0: minimum block size limit (60000)
F0: 0.002 monero
Starts applying at v4
|
| |
|
|
|
|
|
| |
25% of the outputs are selected from the last 5 days (if possible),
in order to avoid the common case of sending recently received
outputs again. 25% and 5 days are subject to review later, since
it's just a wallet level change.
|
| |
|
|
|
|
|
|
|
|
| |
The whole rct data apart from the MLSAGs is now included in
the signed message, to avoid malleability issues.
Instead of passing the data that's not serialized as extra
parameters to the verification API, the transaction is modified
to fill all that information. This means the transaction can
not be const anymore, but it cleaner in other ways.
|