summaryrefslogtreecommitdiff
path: root/src/serialization/json_object.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #5190Riccardo Spagni2019-03-171-0/+4
|\ | | | | | | 551104fb daemon: add --public-node mode, RPC port propagation over P2P (xiphon)
| * daemon: add --public-node mode, RPC port propagation over P2Pxiphon2019-02-251-0/+4
| |
* | Update 2019 copyrightbinaryFate2019-03-051-1/+1
| |
* | various: remove unused variablesmoneromooo-monero2019-03-041-1/+0
|/
* Pruningmoneromooo-monero2019-01-221-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Merge pull request #4753Riccardo Spagni2018-11-141-0/+4
|\ | | | | | | | | | | | | 157054b8 hardfork: initialize current_fork_index in ctor (moneromooo-monero) 2362baf7 network_throttle: initialize m_last_sample_time in ctor (moneromooo-monero) d9400f69 serializtion: add missing mainnet and stagenet fields for 0mq (moneromooo-monero) cbe0122b wallet2: initialize amount to 0 in tx_scan_info_t ctor (moneromooo-monero)
| * serializtion: add missing mainnet and stagenet fields for 0mqmoneromooo-monero2018-10-291-0/+4
| | | | | | | | Coverity 184940
* | Update ZMQ fee estimate and add ZMQ output distributionLee Clagett2018-10-231-0/+23
|/
* v8: per byte fee, pad bulletproofs, fixed 11 ring sizemoneromooo-monero2018-09-111-0/+8
|
* Fixed ZMQ-RPC for transactions and GET_BLOCKS_FASTLee Clagett2018-08-021-156/+172
|
* update get_info RPC and bump RPC versionvictorsintnicolaas2018-06-291-0/+2
|
* Update 2018 copyrightxmr-eric2018-01-261-1/+1
|
* add bulletproofs from v7 on testnetmoneromooo-monero2017-12-081-0/+41
|
* track double spending in the txpoolmoneromooo-monero2017-11-061-0/+2
| | | | | | | | | | | | | | Transactions in the txpool are marked when another transaction is seen double spending one or more of its inputs. This is then exposed wherever appropriate. Note that being marked with this "double spend seen" flag does NOT mean this transaction IS a double spend and will never be mined: it just means that the network has seen at least another transaction spending at least one of the same inputs, so care should be taken to wait for a few confirmations before acting upon that transaction (ie, mostly of use for merchants wanting to accept unconfirmed transactions).
* json_object: add missing do_not_relay to tx_in_pool serializationmoneromooo-monero2017-09-211-0/+1
|
* Fixes static_assert on arm and ppc buildsLee Clagett2017-09-191-1/+3
|
* Fix various oversights/bugs in ZMQ RPC server codeThomas Winget2017-09-051-55/+152
| | | | | | | | | - Add some RPC commands (and touch up a couple others) - some bounds checking - some better pointer management - const correctness and error handling -- Thanks @vtnerd for type help with serialization and CMake changes
* json serialization for rpc-relevant monero typesThomas Winget2017-09-051-0/+1068
Structured {de-,}serialization methods for (many new) types which are used for requests or responses in the RPC. New types include RPC requests and responses, and structs which compose types within those. # Conflicts: # src/cryptonote_core/blockchain.cpp
generated by cgit v1.2.3 (git 2.51.0) at 2026-08-16 22:35:22 +0000