aboutsummaryrefslogtreecommitdiff
path: root/src/rpc (unfollow)
AgeCommit message (Collapse)AuthorFilesLines
2023-07-09Enforce restricted # pool txs served via RPC + optimize chunked reqs ↵j-berman2-37/+34
[release-v0.18] - `/getblocks.bin` respects the `RESTRICTED_TX_COUNT` (=100) when returning pool txs via a restricted RPC daemon. - A restricted RPC daemon includes a max of `RESTRICTED_TX_COUNT` txs in the `added_pool_txs` field, and returns any remaining pool hashes in the `remaining_added_pool_txids` field. The client then requests the remaining txs via `/gettransactions` in chunks. - `/gettransactions` no longer does expensive no-ops for ALL pool txs if the client requests a subset of pool txs. Instead it searches for the txs the client explicitly requests. - Reset `m_pool_info_query_time` when a user: (1) rescans the chain (so the wallet re-requests the whole pool) (2) changes the daemon their wallets points to (a new daemon would have a different view of the pool) - `/getblocks.bin` respects the `req.prune` field when returning pool txs. - Pool extension fields in response to `/getblocks.bin` are optional with default 0'd values.
2023-07-09wallet2, RPC: Optimize RPC calls for periodic refresh from 3 down to 1 call ↵rbrunner72-60/+173
[release-v0.18]
2023-06-30core_rpc_server: return ID of submitted blockjeffro2562-2/+7
2023-03-18Add a size limit for tx_extra in tx pooltevador2-1/+5
2022-12-14Refactored rx-slow-hash.cSChernykh1-3/+1
- Straight-forward call interface: `void rx_slow_hash(const char *seedhash, const void *data, size_t length, char *result_hash)` - Consensus chain seed hash is now updated by calling `rx_set_main_seedhash` whenever a block is added/removed or a reorg happens - `rx_slow_hash` will compute correct hash no matter if `rx_set_main_seedhash` was called or not (the only difference is performance) - New environment variable `MONERO_RANDOMX_FULL_MEM` to force use the full dataset for PoW verification (faster block verification) - When dataset is used for PoW verification, dataset updates don't stall other threads (verification is done in light mode then) - When mining is running, PoW checks now also use dataset for faster verification
2022-09-12wallet2: check wallet compatibility with daemon's hard fork versionj-berman2-1/+24
2022-09-06rpc: skip bootstrap nodes that are lower than last checkpointselsta1-0/+6
2022-06-13Revert "Merge pull request #7937"j-berman1-36/+14
This reverts commit 50410d1f7d04bf60053f2263410c39e81d3ddad1, reversing changes made to d054def63f9b8950fe20b2d8e841f5a9ae09418f.
2022-05-05Give better error messages when missing SSL filesJeffrey Ryan1-5/+16
While copying my data dir to another drive, I missed copying the rpc_ssl.key file b/c of the file permissions. This change will give a much more clear, descriptive error in that scenario.
2022-04-21add a sanity check to RPC input data sizemoneromooo-monero1-0/+2
reported by m31007
2022-04-18Add Include statementsJeffrey1-0/+1
2022-04-10Fee changes from ArticMinemoneromooo-monero2-1/+13
https://github.com/ArticMine/Monero-Documents/blob/master/MoneroScaling2021-02.pdf with a change to use 1.7 instead of 2.0 for the max long term increase rate
2022-04-05Make RPC server functions that read db thread safej-berman1-14/+36
- grab an lmdb db_rtxn_guard to ensure consistent data from the db - fixed on_getblockhash error resp when requested height >= blockchain height - left functions that read shared memory untouched for now
2022-03-04Copyright: Update to 2022mj-xmr31-31/+35
2022-02-19Fixes: Don't require --rpc-login with --rpc-access-control-origins #8168Jeffrey1-6/+0
This PR removes the requirement for --rpc-login to be specified if --rpc-access-control-origins is. This will allow public nodes to serve cross-origin requests. You can still use --rpc-login with --rpc-access-control-origins, but it is no longer mandatory. Original Issue: #8168
2022-02-07rpc: add explicit restricted flag to /get_infotobtoht2-1/+4
2021-11-20Add calcpow RPCHoward Chu3-1/+62
Calculate PoW hash for a block candidate
2021-10-24rpc: fix DoS vector in get_output_distributionmoneromooo-monero1-0/+15
This will prevent people spending old pre-rct outputs using a stranger's node, which may be a good thing
2021-09-20rpc: Fix get_transactions failing when not foundNathan Dorfman1-2/+14
2021-09-15rpc: don't set error code as status stringselsta1-2/+2
2021-09-11RPC and ZeroMQ APIs to support p2poolSChernykh5-15/+189
Adds the following: - "get_miner_data" to RPC API - "json-miner-data" to ZeroMQ subscriber contexts Both provide the necessary data to create a custom block template. They are used by p2pool. Data provided: - major fork version - current height - previous block id - RandomX seed hash - network difficulty - median block weight - coins mined by the network so far - mineable mempool transactions
2021-08-20daemon: allow proxy configurationanon2-3/+7
Co-authored-by: selsta <selsta@sent.at> Co-authored-by: tobtoht <thotbot@protonmail.com>
2021-07-15rpc: source file extensions must be explicit (cmake warning)selsta1-1/+1
2021-04-15rpc: send confirmations in get_transactions resultmoneromooo-monero2-1/+5
if the wallet does it, it would get a wrong result (possibly even negative) if its local chain is not synced up to the daemon's yet
2021-03-28Reduce compilation time of epee/portable_storage_template_helper.hmj-xmr2-0/+2
2021-02-15rpc: fix some error return codes/statusmoneromooo-monero2-23/+33
Some RPC return an error string in status, and the code must return true on error (with a status string).
2021-02-13Store RPC SSL key/cert for consistent authentication between runsLee Clagett1-2/+23
2021-02-09New add_aux_pow RPC to support merge miningmoneromooo-monero3-1/+169
2021-02-09Remove unused variables in monero codebaseKevin Barbour1-2/+0
There are quite a few variables in the code that are no longer (or perhaps never were) in use. These were discovered by enabling compiler warnings for unused variables and cleaning them up. In most cases where the unused variables were the result of a function call the call was left but the variable assignment removed, unless it was obvious that it was a simple getter with no side effects.
2021-01-28Fix monerod --rpc-ssl disabledLee Clagett1-1/+1
2021-01-23Improve cryptonote (block and tx) binary read performanceLee Clagett1-1/+4
2021-01-21bootstrap_daemon: proxy configuration supportxiphon5-19/+64
2020-12-29rpc: limit the number of txes for get_blocks.binmoneromooo-monero2-5/+5
2020-12-22restrict public node checks a littlemoneromooo-monero2-2/+13
do not include blocked hosts in peer lists or public node lists by default, warn about no https on clearnet and about untrusted peers likely being spies
2020-12-17rpc: add a busy_syncing field to get_infomoneromooo-monero2-1/+4
true if and pretty much only if new blocks are being added
2020-12-10protocol: drop origin IP if a block fails to verify in sync modemoneromooo-monero1-5/+1
It would otherwise be possible for a peer to send bad blocks, then disconnect and reconnect again, escaping bans
2020-12-10rpc: report target height as 0 when syncedmoneromooo-monero1-2/+2
since it only makes sense when syncing, and it confuses people
2020-11-19rpc: get_info - add 'synchronized' fieldxiphon2-1/+4
2020-11-17rpc: skip non-synced bootstrap daemons in --no-sync mode tooxiphon3-17/+21
2020-11-15rpc: on_send_raw_tx (bootstrap) - send to bootstrap daemon and P2Pxiphon1-0/+9
2020-11-11Silence stupid warningsHoward Chu1-2/+2
2020-10-29Fix CLI and unrestricted RPC relay_tx with stempoolLee Clagett1-2/+8
2020-10-29Add rpc-restricted-bind-ip optionHoward Chu3-3/+53
Fixes #6369
2020-10-13fix next_seed_height regression in getblocktemplate rpcAlexis Enston1-0/+7
2020-10-13core_rpc_server: on_get_blocks - forward bootstrap daemon errorxiphon1-3/+11
2020-10-12core_rpc_server: on_send_raw_tx - fix bootstrap daemon mode checkxiphon1-1/+1
2020-09-27rpc_private_headers declaration fixMichal m@lbit Malicki1-1/+1
2020-09-15wallet2: adapt to deterministic unlock timeTheCharlatan4-1/+7
2020-09-07rpc: assume randomx from v13 onwardsmoneromooo-monero1-2/+2
2020-08-27core: fix mining from a block that's not the current topmoneromooo-monero1-15/+11
2020-08-27Integrate CLSAGs into moneromoneromooo-monero1-1/+1
They are allowed from v12, and MLSAGs are rejected from v13.
2020-08-19Fix ZMQ pruned bulletproof transactionsLee Clagett1-1/+5
2020-08-17replace most boost serialization with existing monero serializationmoneromooo-monero2-15/+71
This reduces the attack surface for data that can come from malicious sources (exported output and key images, multisig transactions...) since the monero serialization is already exposed to the outside, and the boost lib we were using had a few known crashers. For interoperability, a new load-deprecated-formats wallet setting is added (off by default). This allows loading boost format data if there is no alternative. It will likely go at some point, along with the ability to load those. Notably, the peer lists file still uses the boost serialization code, as the data it stores is define in epee, while the new serialization code is in monero, and migrating it was fairly hairy. Since this file is local and not obtained from anyone else, the marginal risk is minimal, but it could be migrated later if needed. Some tests and tools also do, this will stay as is for now.
2020-08-16rpc: always send raw txes through P2P (don't use bootstrap daemon)xiphon1-43/+56
It turns out that some remote (bootstrap) nodes silently drop / don't broadcast client's transactions.
2020-08-14Change ZMQ-JSON txextra to hex and remove unnecessary base fieldsLee Clagett2-5/+1
2020-08-14Switch to insitu parsing for ZMQ-JSON; GetBlocksFast reads 13%+ fasterLee Clagett6-11/+15
2020-08-14Fix pruned tx for ZMQ's GetBlocksFastLee Clagett1-0/+1
2020-07-30rpc: reject wrong sized txidmoneromooo-monero1-6/+4
Reporter requested credit to be given to Decred
2020-07-25rpc: return empty txid get_outs rather than 00..00 when not requestedmoneromooo-monero1-1/+2
It's more obvious there's no txid, and it saves space
2020-06-05rpc: fix loading rpc payment data from filemoneromooo-monero1-1/+1
Got broken after making one of those micro optimizations requested on review..
2020-05-31Fix boost <1.60 compilation and fix boost 1.73+ warningsLee Clagett1-2/+2
2020-05-31rpc: fix comparison of seconds vs microsecondsmoneromooo-monero1-1/+1
2020-05-28rpc: fix relay_tx error return mixupmoneromooo-monero1-1/+1
2020-05-23rpc: don't display invalid json errors on default log levelmoneromooo-monero1-5/+5
It's not something the user needs to know, and will display attacker controlled data
2020-05-20rpc: add a sanity limit to a few RPC in restricted modemoneromooo-monero2-6/+46
2020-05-19rpc: lock access to the rpc payment objectmoneromooo-monero2-0/+12
2020-05-06Update copyright year to 2020SomaticFanatic25-25/+25
Update copyright year to 2020
2020-05-04Adding ZMQ/Pub support for txpool_add and chain_main eventsLee Clagett6-53/+788
2020-04-29Fixes for ZMQ JSON-RPC endpoint names for raw txLee Clagett1-1/+2
2020-04-27rpc: fix 'use_bootstrap_daemon_if_necessary' return valuexiphon1-1/+1
2020-04-15bootstrap_daemon: fix missing virtual destructor and lambda capture (clang ↵xiphon2-1/+3
warning)
2020-04-11Add byte_stream for zero-copy serialization, and add support in ZMQ-JSON.Lee Clagett5-67/+66
2020-04-03Use byte_slice for sending zmq messages - removes data copy within zmqLee Clagett6-22/+33
2020-04-01Hash domain separationSarang Noether1-3/+1
2020-03-31cryptonote_basic: drop unused verification_context::m_not_rct fieldxiphon3-9/+0
2020-03-30Allow unrestricted rpc calls to get full txpool infoLee Clagett1-7/+12
2020-03-26Adding Dandelion++ support to public networks:Lee Clagett3-11/+11
- New flag in NOTIFY_NEW_TRANSACTION to indicate stem mode - Stem loops detected in tx_pool.cpp - Embargo timeout for a blackhole attack during stem phase
2020-03-12rpc: add --rpc-payment-allow-free-loopbackmoneromooo-monero2-1/+12
This allows RPC coming from the loopback interface to not have to pay for service. This makes it possible to run an externally accessible RPC server for payment while also having a local RPC server that can be run unrestricted and payment free.
2020-03-09Move hex->bin conversion to monero copyright files and with less includesLee Clagett1-2/+2
2020-03-05Various improvements to the ZMQ JSON-RPC handling:Lee Clagett6-650/+353
- Finding handling function in ZMQ JSON-RPC now uses binary search - Temporary `std::vector`s in JSON output now use `epee::span` to prevent allocations. - Binary -> hex in JSON output no longer allocates temporary buffer - C++ structs -> JSON skips intermediate DOM creation, and instead write directly to an output stream.
2020-02-28daemon: auto public nodes - cache and prioritize most stable nodesxiphon7-43/+304
2020-02-17rpc: Add check for too old timestamps in payment signatures.Guillaume Le Vaillant1-0/+5
2020-02-08rpc: fix print_pool_sh not finding local txesmoneromooo-monero1-1/+4
2020-01-14wallet: reroll fake outs selection on local tx_sanity_check failurexiphon1-1/+1
2019-12-20rpc: fill miner_tx_hash againmoneromooo-monero1-0/+1
It was removed to save duplicated generation time, but it can be copied from another instance instead
2019-12-16rpc: drop the obsolete and wrong "unpruned size" logmoneromooo-monero1-6/+4
Since we now get pruned data in the first place, the "unpruned" data size will in fact be the pruned data size, leading to confusion
2019-12-12print_coinbase_tx_sum now supports 128 bits sumsmoneromooo-monero2-6/+19
The tail emission will bring the total above 64 bits
2019-12-04--disable-ban-rpc option to prevent RPC users from banningnaughtyfox4-1/+9
2019-12-02rpc: add bad-blocks to flush_cache RPCmoneromooo-monero2-1/+5
Flushes m_invalid_blocks in Blockchain.
2019-11-29daemon: run with -rpc-payment-address and --rpc-restricted-bind-portmoneromooo-monero2-2/+4
2019-11-27rpc: error out from get_info if the proxied call errors outmoneromooo-monero1-2/+1
Coverity 205410
2019-11-27rpc: init a few missing client_info membersmoneromooo-monero1-0/+4
Coverity 205414
2019-11-27rpc: do not propagate exceptions out of a dtormoneromooo-monero1-4/+8
Coverity 205415
2019-11-27rpc: always set the update field in update on sucessmoneromooo-monero1-0/+1
Coverity 205416
2019-11-25rpc: fix bootstrap RPC payment RPC being made in raw JSON, not JSON RPCmoneromooo-monero1-5/+5
2019-11-22rpc: don't auto fail RPC needing payment in bootstrap modemoneromooo-monero1-1/+5
2019-11-22rpc: add received_timestamp for pool txes in gettransactionsmoneromooo-monero2-1/+6
2019-11-18Fixed bug in ZMQ JSON-RPC method fieldLee Clagett1-3/+12
2019-11-14Actually concatenate error strings.Bert Peters1-8/+8
2019-11-12rpc: Only show version string if it matches expected patternNathan Dorfman3-0/+100
2019-11-02Adding support for hidden (anonymity) txpoolLee Clagett2-12/+10
2019-10-31cryptonote: untangle dependency from miner to blockchainmoneromooo-monero1-1/+3
It causes link errors at least on mac
2019-10-31cryptonote: untangle dependency from miner to blockchainmoneromooo-monero1-1/+3
It causes link errors at least on mac
2019-10-30daemon: always use bootstrap daemon (if set) in '--no-sync' modexiphon1-3/+5
2019-10-28daemon: always use bootstrap daemon (if set) in '--no-sync' modexiphon1-3/+5
2019-10-27rpc: base flush_cache request/response on the new base structsmoneromooo-monero1-5/+4
2019-10-26rpc: fix PRIx64 build error on some systemsmoneromooo-monero1-1/+1
2019-10-25rpc: add a flush_cache RPCmoneromooo-monero3-1/+34
This allows flushing internal caches (for now, the bad tx cache, which will allow debugging a stuck monerod after it has failed to verify a transaction in a block, since it would otherwise not try again, making subsequent log changes pointless)
2019-10-25simplewallet: add public_nodes commandmoneromooo-monero3-3/+6
Lists nodes exposing their RPC port for public use
2019-10-25daemon, wallet: new pay for RPC use systemmoneromooo-monero11-431/+1929
Daemons intended for public use can be set up to require payment in the form of hashes in exchange for RPC service. This enables public daemons to receive payment for their work over a large number of calls. This system behaves similarly to a pool, so payment takes the form of valid blocks every so often, yielding a large one off payment, rather than constant micropayments. This system can also be used by third parties as a "paywall" layer, where users of a service can pay for use by mining Monero to the service provider's address. An example of this for web site access is Primo, a Monero mining based website "paywall": https://github.com/selene-kovri/primo This has some advantages: - incentive to run a node providing RPC services, thereby promoting the availability of third party nodes for those who can't run their own - incentive to run your own node instead of using a third party's, thereby promoting decentralization - decentralized: payment is done between a client and server, with no third party needed - private: since the system is "pay as you go", you don't need to identify yourself to claim a long lived balance - no payment occurs on the blockchain, so there is no extra transactional load - one may mine with a beefy server, and use those credits from a phone, by reusing the client ID (at the cost of some privacy) - no barrier to entry: anyone may run a RPC node, and your expected revenue depends on how much work you do - Sybil resistant: if you run 1000 idle RPC nodes, you don't magically get more revenue - no large credit balance maintained on servers, so they have no incentive to exit scam - you can use any/many node(s), since there's little cost in switching servers - market based prices: competition between servers to lower costs - incentive for a distributed third party node system: if some public nodes are overused/slow, traffic can move to others - increases network security - helps counteract mining pools' share of the network hash rate - zero incentive for a payer to "double spend" since a reorg does not give any money back to the miner And some disadvantages: - low power clients will have difficulty mining (but one can optionally mine in advance and/or with a faster machine) - payment is "random", so a server might go a long time without a block before getting one - a public node's overall expected payment may be small Public nodes are expected to compete to find a suitable level for cost of service. The daemon can be set up this way to require payment for RPC services: monerod --rpc-payment-address 4xxxxxx \ --rpc-payment-credits 250 --rpc-payment-difficulty 1000 These values are an example only. The --rpc-payment-difficulty switch selects how hard each "share" should be, similar to a mining pool. The higher the difficulty, the fewer shares a client will find. The --rpc-payment-credits switch selects how many credits are awarded for each share a client finds. Considering both options, clients will be awarded credits/difficulty credits for every hash they calculate. For example, in the command line above, 0.25 credits per hash. A client mining at 100 H/s will therefore get an average of 25 credits per second. For reference, in the current implementation, a credit is enough to sync 20 blocks, so a 100 H/s client that's just starting to use Monero and uses this daemon will be able to sync 500 blocks per second. The wallet can be set to automatically mine if connected to a daemon which requires payment for RPC usage. It will try to keep a balance of 50000 credits, stopping mining when it's at this level, and starting again as credits are spent. With the example above, a new client will mine this much credits in about half an hour, and this target is enough to sync 500000 blocks (currently about a third of the monero blockchain). There are three new settings in the wallet: - credits-target: this is the amount of credits a wallet will try to reach before stopping mining. The default of 0 means 50000 credits. - auto-mine-for-rpc-payment-threshold: this controls the minimum credit rate which the wallet considers worth mining for. If the daemon credits less than this ratio, the wallet will consider mining to be not worth it. In the example above, the rate is 0.25 - persistent-rpc-client-id: if set, this allows the wallet to reuse a client id across runs. This means a public node can tell a wallet that's connecting is the same as one that connected previously, but allows a wallet to keep their credit balance from one run to the other. Since the wallet only mines to keep a small credit balance, this is not normally worth doing. However, someone may want to mine on a fast server, and use that credit balance on a low power device such as a phone. If left unset, a new client ID is generated at each wallet start, for privacy reasons. To mine and use a credit balance on two different devices, you can use the --rpc-client-secret-key switch. A wallet's client secret key can be found using the new rpc_payments command in the wallet. Note: anyone knowing your RPC client secret key is able to use your credit balance. The wallet has a few new commands too: - start_mining_for_rpc: start mining to acquire more credits, regardless of the auto mining settings - stop_mining_for_rpc: stop mining to acquire more credits - rpc_payments: display information about current credits with the currently selected daemon The node has an extra command: - rpc_payments: display information about clients and their balances The node will forget about any balance for clients which have been inactive for 6 months. Balances carry over on node restart.
2019-10-24rpc: Include tag in get_info version stringNathan Dorfman1-1/+1
2019-10-24add a quick early out to get_blocks.bin when up to datemoneromooo-monero1-1/+15
2019-10-13p2p+rpc: don't skip p2p or rpc port bind failure by defaultxiphon2-4/+4
2019-10-07Print cdifficulty and don't serialize miner tx hash twiceDoyle1-1/+0
2019-09-27monerod can now sync from pruned blocksmoneromooo-monero2-7/+8
If the peer (whether pruned or not itself) supports sending pruned blocks to syncing nodes, the pruned version will be sent along with the hash of the pruned data and the block weight. The original tx hashes can be reconstructed from the pruned txes and theur prunable data hash. Those hashes and the block weights are hashes and checked against the set of precompiled hashes, ensuring the data we received is the original data. It is currently not possible to use this system when not using the set of precompiled hashes, since block weights can not otherwise be checked for validity. This is off by default for now, and is enabled by --sync-pruned-blocks
2019-09-25RandomX integrationHoward Chu2-2/+19
Support RandomX PoW algorithm
2019-09-25ban peers sending bad pow outrightmoneromooo-monero2-3/+3
PoW is expensive to verify, so be strict
2019-09-17functional_tests: add get_transaction_pool_statsmoneromooo-monero1-3/+3
Also fix part of the RPC results being returned as binary. This makes the RPC backward incompatible.
2019-09-16p2p: fix bans taking port into accountmoneromooo-monero1-3/+3
2019-09-07bootstrap_daemon: resolve CID 203915 (UNCAUGHT_EXCEPT)anonimal2-2/+2
The issue is triggered by the captured `this` in RPC server, which passes reference to throwable `core_rpc_server`: `core_rpc_server.cpp:164: m_bootstrap_daemon.reset(new bootstrap_daemon([this]{ return get_random_public_node(); }));` The solution is to simply remove noexcept from the remaining `bootstrap_daemon` constructors because noexcept is false in this context. >"An exception of type "boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<boost::asio::invalid_service_owner>>" is thrown but the throw list "noexcept" doesn't allow it to be thrown. This will cause a call to unexpected() which usually calls terminate()."
2019-09-02Changed the use of boost:value_initialized for C++ list initializerJesus Ramirez1-1/+1
2019-08-28rpc: don't include an address in mining_status when not miningmoneromooo-monero1-1/+2
Best case is an address mined previously and it'll get returned, worst case it was never initialized in the first place
2019-08-28rpc: move a leftover light wallet RPC out of daemon RPCmoneromooo-monero1-50/+0
2019-08-27daemon: automatic public nodes discovering and bootstrap daemon switchingxiphon5-35/+246
2019-08-26wallet, rpc: add a release field to get_versionmoneromooo-monero2-1/+4
It does not leak much since you can make a fair guess by RPC version already, and some people want to avoid non release clients when using third parties' nodes (because they'd never lie about it)
2019-08-20rpc: fix unitialized 'core_rpc_server::m_was_bootstrap_ever_used'xiphon1-0/+1
2019-08-19daemon: fix print_pl only printing public zone peersmoneromooo-monero2-7/+14
2019-07-31Add IPv6 supportThomas Winget4-1/+57
new cli options (RPC ones also apply to wallet): --p2p-bind-ipv6-address (default = "::") --p2p-bind-port-ipv6 (default same as ipv4 port for given nettype) --rpc-bind-ipv6-address (default = "::1") --p2p-use-ipv6 (default false) --rpc-use-ipv6 (default false) --p2p-require-ipv4 (default true, if ipv4 bind fails and this is true, will not continue even if ipv6 bind successful) --rpc-require-ipv4 (default true, description as above) ipv6 addresses are to be specified as "[xx:xx:xx::xx:xx]:port" except in the cases of the cli args for bind address. For those the square braces can be omitted.
2019-07-29rpc: implement get_public_nodes commandxiphon3-1/+90
2019-07-22Dropping cppzmq dependency; adding some zmq utilsLee Clagett3-71/+87
2019-07-16allow blocking whole subnetsmoneromooo-monero3-2/+87
2019-07-16p2p: store network address directly in blocked host listmoneromooo-monero1-4/+4
rather than their string representation
2019-07-03rpc: get_block_template add optional extra_nonceJethro Grassie2-1/+27
Circumvents the need to create a new blockhashing blob when you already know the data you want to set in the extra_nonce (so use this instead of reserve_size).
2019-07-01zmq: MacPorts latest fixJethro Grassie1-1/+1
2019-06-25rpc headers fixMichal vel m@lbit1-1/+1
2019-06-20rpc: set sanity_check_failed to false when successfulstoffu1-0/+1
2019-06-16Bans for RPC connectionsHoward Chu2-0/+24
Make bans control RPC sessions too. And auto-ban some bad requests. Drops HTTP connections whenever response code is 500.
2019-06-14rpc: restrict the recent cutoff size in restricted RPC modemoneromooo-monero1-0/+9
2019-06-12rpc: work around a GCC 7.4.0 (at least) bugmoneromooo-monero1-1/+3
In static member function ‘static boost::optional<cryptonote::rpc::output_distribution_data> cryptonote::rpc::RpcHandler::get_output_distribution(const std::function<bool(long unsigned int, long unsigned int, long unsigned int, long unsigned int&, std::vector<long unsigned int>&, long unsigned int&)>&, uint64_t, uint64_t, uint64_t, const std::function<crypto::hash(long unsigned int)>&, bool, uint64_t)’: cc1plus: warning: ‘void* __builtin_memset(void*, int, long unsigned int)’: specified size 18446744073709551536 exceeds maximum object size 9223372036854775807 [-Wstringop-overflow=]
2019-06-12rpc: fix get_transactions getting v1 txes from the txpoolmoneromooo-monero1-1/+2
It would try to get their prunable hash, but v1 txes don't have one
2019-06-10rpc: implement set_bootstrap_daemon methodxiphon3-27/+108
2019-06-09miner: fix double free of thread attributesston1th2-8/+2
issue: #5568
2019-06-04rpc: use ip address string representation for peer::host fieldxiphon1-1/+4
2019-06-01daemon: add more chain specific info in alt_chain_infomoneromooo-monero2-29/+50
2019-05-30rpc: in/out peers can now return the setting's valuemoneromooo-monero2-5/+17
2019-05-22Add ssl_options support to monerod's rpc mode.Lee Clagett3-84/+99
2019-05-10remove obsolete save_graph skeleton codemoneromooo-monero3-60/+0
2019-05-09rpc: fail update RPC when running offlinemoneromooo-monero1-0/+7
2019-05-09daemon: sort alt chains by heightmoneromooo-monero2-2/+2
2019-05-01fix wide difficulty conversion with some versions of boostmoneromooo-monero2-5/+5
2019-04-29add a few checks where it seems appropriatemoneromooo-monero1-1/+1
2019-04-26change SSL certificate fingerprint whitelisting from SHA1 to SHA-256moneromooo-monero1-0/+9
SHA1 is too close to bruteforceable
2019-04-25rpc: improve get_output_distributionmoneromooo-monero4-8/+34
It can now handle small reorgs without having to rescan the whole blockchain. Also add a test for it.
2019-04-23consensus: from v12, enforce >= 2 outputsmoneromooo-monero3-0/+9
2019-04-16rpc: add a pruned bool to the prune_blockchain callmoneromooo-monero2-1/+4
2019-04-15rpc: fix get_block_hashes.bin from wallet on pruned blockchainmoneromooo-monero2-8/+3
We want to get all blocks here, even pruned ones
2019-04-15rpc: omit irrelevant fields for pool txes in gettransactionsmoneromooo-monero1-4/+10
2019-04-15rpc: add relayed in get_transaction outputmoneromooo-monero2-5/+11
2019-04-15rpc: set default log category in core_rpc_server.hmoneromooo-monero1-0/+3
2019-04-14core_rpc_server: remove dummy assigning int to boolmoneromooo-monero1-3/+1
Coverity 197653
2019-04-12rpc: new sanity check on relayed transactionsmoneromooo-monero2-0/+13
This will weed out some transactions with silly rings
2019-04-12rpc.getblocktemplate: set reserved_offset to zero when reserve_size==0stoffu1-1/+4
2019-04-11rpc: fix off by one in get_heightmoneromooo-monero1-0/+1
2019-04-11functional_tests: add more blockchain related testsmoneromooo-monero2-3/+30
Related to emission, reorgs, getting tx data back, output distribution and histogram
2019-04-07Pass SSL arguments via one class and use shared_ptr instead of referenceLee Clagett1-12/+19
2019-04-06Change default SSL to "enabled" if user specifies fingerprint/certificateLee Clagett1-7/+12
Currently if a user specifies a ca file or fingerprint to verify peer, the default behavior is SSL autodetect which allows for mitm downgrade attacks. It should be investigated whether a manual override should be allowed - the configuration is likely always invalid.
2019-04-06Change SSL certificate file list to OpenSSL builtin load_verify_locationLee Clagett2-18/+8
Specifying SSL certificates for peer verification does an exact match, making it a not-so-obvious alias for the fingerprints option. This changes the checks to OpenSSL which loads concatenated certificate(s) from a single file and does a certificate-authority (chain of trust) check instead. There is no drop in security - a compromised exact match fingerprint has the same worse case failure. There is increased security in allowing separate long-term CA key and short-term SSL server keys. This also removes loading of the system-default CA files if a custom CA file or certificate fingerprint is specified.
2019-04-06rpc: merge the two get_info implementationsmoneromooo-monero1-62/+3
2019-04-05rpc: make wide_difficulty hexadecimalmoneromooo-monero1-1/+1
This should be friendlier for clients which don't have bignum support
2019-04-04wallet: new option to start background miningmoneromooo-monero2-0/+7
The setup-background-mining option can be used to select background mining when a wallet loads. The user will be asked the first time the wallet is created.
2019-04-04rpc.gettransactions: fill as_json with partial tx in pruned modestoffu1-12/+43
2019-04-01Add hash of top block to /getheight RPCHoward Chu2-2/+6
2019-03-24Make difficulty 128 bit instead of 64 bitmoneromooo-monero4-13/+60
Based on Boolberry work by: jahrsg <jahr@jahr.me> cr.zoidberg <crypto.zoidberg@gmail.com>
2019-03-24New interactive daemon command 'print_net_stats': Global traffic statsrbrunner73-1/+53
2019-03-21rpc: add miner tx hash to block header responsemoneromooo-monero2-1/+4
2019-03-17rpc: quantize db size up to 5 GB in restricted modemoneromooo-monero1-1/+3
2019-03-15wallet: move light wallet RPC out of core RPCmoneromooo-monero1-283/+0
It's not nothing to do with it
2019-03-09daemon: new mining_status commandmoneromooo-monero2-2/+35
2019-03-06rpc: make fill_pow restrictedmoneromooo-monero1-5/+10
It's slow work, so let's not expose it
2019-03-05Update 2019 copyrightbinaryFate19-19/+19
2019-03-05epee: add SSL supportMartijn Otto2-1/+12
RPC connections now have optional tranparent SSL. An optional private key and certificate file can be passed, using the --{rpc,daemon}-ssl-private-key and --{rpc,daemon}-ssl-certificate options. Those have as argument a path to a PEM format private private key and certificate, respectively. If not given, a temporary self signed certificate will be used. SSL can be enabled or disabled using --{rpc}-ssl, which accepts autodetect (default), disabled or enabled. Access can be restricted to particular certificates using the --rpc-ssl-allowed-certificates, which takes a list of paths to PEM encoded certificates. This can allow a wallet to connect to only the daemon they think they're connected to, by forcing SSL and listing the paths to the known good certificates. To generate long term certificates: openssl genrsa -out /tmp/KEY 4096 openssl req -new -key /tmp/KEY -out /tmp/REQ openssl x509 -req -days 999999 -sha256 -in /tmp/REQ -signkey /tmp/KEY -out /tmp/CERT /tmp/KEY is the private key, and /tmp/CERT is the certificate, both in PEM format. /tmp/REQ can be removed. Adjust the last command to set expiration date, etc, as needed. It doesn't make a whole lot of sense for monero anyway, since most servers will run with one time temporary self signed certificates anyway. SSL support is transparent, so all communication is done on the existing ports, with SSL autodetection. This means you can start using an SSL daemon now, but you should not enforce SSL yet or nothing will talk to you.
2019-03-04default initialize rpc structuresmoneromooo-monero1-140/+259
2019-03-04ArticMine's new block weight algorithmmoneromooo-monero2-0/+3
This curbs runaway growth while still allowing substantial spikes in block weight Original specification from ArticMine: here is the scaling proposal Define: LongTermBlockWeight Before fork: LongTermBlockWeight = BlockWeight At or after fork: LongTermBlockWeight = min(BlockWeight, 1.4*LongTermEffectiveMedianBlockWeight) Note: To avoid possible consensus issues over rounding the LongTermBlockWeight for a given block should be calculated to the nearest byte, and stored as a integer in the block itself. The stored LongTermBlockWeight is then used for future calculations of the LongTermEffectiveMedianBlockWeight and not recalculated each time. Define: LongTermEffectiveMedianBlockWeight LongTermEffectiveMedianBlockWeight = max(300000, MedianOverPrevious100000Blocks(LongTermBlockWeight)) Change Definition of EffectiveMedianBlockWeight From (current definition) EffectiveMedianBlockWeight = max(300000, MedianOverPrevious100Blocks(BlockWeight)) To (proposed definition) EffectiveMedianBlockWeight = min(max(300000, MedianOverPrevious100Blocks(BlockWeight)), 50*LongTermEffectiveMedianBlockWeight) Notes: 1) There are no other changes to the existing penalty formula, median calculation, fees etc. 2) There is the requirement to store the LongTermBlockWeight of a block unencrypted in the block itself. This is to avoid possible consensus issues over rounding and also to prevent the calculations from becoming unwieldy as we move away from the fork. 3) When the EffectiveMedianBlockWeight cap is reached it is still possible to mine blocks up to 2x the EffectiveMedianBlockWeight by paying the corresponding penalty. Note: the long term block weight is stored in the database, but not in the actual block itself, since it requires recalculating anyway for verification.
2019-02-27rpc: Allow submitting tx as hex blob over ZMQNathan Dorfman4-6/+59
2019-02-25daemon: add --public-node mode, RPC port propagation over P2Pxiphon4-9/+13
2019-02-21rpc: quantize db size up to 5 GB in restricted modemoneromooo-monero1-1/+8
2019-02-02epee: add SSL supportmoneromooo-monero2-3/+65
RPC connections now have optional tranparent SSL. An optional private key and certificate file can be passed, using the --{rpc,daemon}-ssl-private-key and --{rpc,daemon}-ssl-certificate options. Those have as argument a path to a PEM format private private key and certificate, respectively. If not given, a temporary self signed certificate will be used. SSL can be enabled or disabled using --{rpc}-ssl, which accepts autodetect (default), disabled or enabled. Access can be restricted to particular certificates using the --rpc-ssl-allowed-certificates, which takes a list of paths to PEM encoded certificates. This can allow a wallet to connect to only the daemon they think they're connected to, by forcing SSL and listing the paths to the known good certificates. To generate long term certificates: openssl genrsa -out /tmp/KEY 4096 openssl req -new -key /tmp/KEY -out /tmp/REQ openssl x509 -req -days 999999 -sha256 -in /tmp/REQ -signkey /tmp/KEY -out /tmp/CERT /tmp/KEY is the private key, and /tmp/CERT is the certificate, both in PEM format. /tmp/REQ can be removed. Adjust the last command to set expiration date, etc, as needed. It doesn't make a whole lot of sense for monero anyway, since most servers will run with one time temporary self signed certificates anyway. SSL support is transparent, so all communication is done on the existing ports, with SSL autodetection. This means you can start using an SSL daemon now, but you should not enforce SSL yet or nothing will talk to you.
2019-01-28Adding initial support for broadcasting transactions over TorLee Clagett3-26/+22
- Support for ".onion" in --add-exclusive-node and --add-peer - Add --anonymizing-proxy for outbound Tor connections - Add --anonymous-inbounds for inbound Tor connections - Support for sharing ".onion" addresses over Tor connections - Support for broadcasting transactions received over RPC exclusively over Tor (else broadcast over public IP when Tor not enabled).
2019-01-28rpc: fix internal daemon calls in restricted rpc getting partial datamoneromooo-monero2-159/+179
2019-01-22Pruningmoneromooo-monero4-19/+118
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-12-30wallet: do not display daemon controlled text if untrustedmoneromooo-monero1-12/+12
2018-12-18blockchain_db: speedup tx output gatheringmoneromooo-monero1-13/+16
We know all the data we'll want for getblocks.bin is contiguous
2018-12-07p2p: use vector instead of list for peer listsmoneromooo-monero1-3/+4
2018-12-04rpc: mask values that are nobody else's business in restricted RPCmoneromooo-monero1-24/+29
2018-11-28add command pop_blocksJason Wong3-0/+37
add new public method to Blockchain and update according to code review update after review: better lock/unlock, try catch and coding style
2018-11-27rpc: speed up the common get_output_distribution case while syncingmoneromooo-monero1-2/+19
2018-11-26rpc: speedup get_outs.binmoneromooo-monero1-1/+3
2018-11-23remove some unused codemoneromooo-monero1-72/+0
Found by codacy.com
2018-11-23tests: slow_memmem now returns size_tmoneromooo-monero1-1/+1
Makes more sense than uint64_t for an offset, and agrees with the %zu used to print results. Found by codacy.com
2018-11-21rpc: add version to get_infoJethro Grassie5-1/+11
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 06:19:02 +0000