aboutsummaryrefslogtreecommitdiff
path: root/src/rpcnet.cpp
Commit message (Collapse)AuthorAgeFilesLines
* Add relaytxes status to getpeerinfoPeter Todd2015-11-201-0/+2
|
* add (max)uploadtarget infos to getnettotals RPC helpJonas Schnelli2015-11-121-1/+10
|
* Merge pull request #6870Wladimir J. van der Laan2015-10-291-2/+2
|\ | | | | | | | | | | | | 040c0ea Init: Cleanup error and warning strings (MarcoFalke) 6782f58 [trivial] Latest config.guess (MarcoFalke) bf68191 [trivial] rpcnet: fix typo (MarcoFalke) 95f4291 [trivial] Rewrite help text for feature enabled by default (MarcoFalke)
| * [trivial] rpcnet: fix typoMarcoFalke2015-10-231-2/+2
| |
* | Introduce -maxuploadtargetJonas Schnelli2015-10-261-0/+9
|/ | | | | | | * -maxuploadtarget can be set in MiB * if <limit> - ( time-left-in-24h-cycle / 600 * MAX_BLOCK_SIZE ) has reach, stop serve blocks older than one week and filtered blocks * no action if limit has reached, no guarantee that the target will not be surpassed * add outbound limit informations to rpc getnettotals
* [Univalue] add univalue over subtreeJonas Schnelli2015-10-011-1/+1
| | | | similar to secp256k1 include and compile univalue over a subtree
* [Qt] banlist, UI optimizing and better signal handlingJonas Schnelli2015-09-161-1/+0
|
* [Qt] add ui signal for banlist changesJonas Schnelli2015-09-161-0/+5
|
* Report minimum ping time in getpeerinfoMatt Corallo2015-09-031-0/+2
|
* Merge pull request #6462Wladimir J. van der Laan2015-08-051-2/+1
|\ | | | | | | | | 7b79cbd limit total length of user agent comments (Pavol Rusnak) 557f8ea implement uacomment config parameter which can add comments to user agent as per BIP-0014 (Pavol Rusnak)
| * limit total length of user agent commentsPavol Rusnak2015-08-051-2/+1
| | | | | | | | Reworked-By: Wladimir J. van der Laan <[email protected]>
| * implement uacomment config parameterPavol Rusnak2015-07-311-1/+1
| | | | | | | | which can add comments to user agent as per BIP-0014
* | Rationalize currency unit to "BTC"Ross Nicoll2015-08-031-1/+1
|/ | | | | | | | | Previously various user-facing strings have used inconsistent currency units "BTC", "btc" and "bitcoins". This adds a single constant and uses it for each reference to the currency unit. Also adds a description of the unit for --maxtxfee, and adds the missing "amount" field description to the (deprecated) move RPC command.
* TRIVIAL: Missing includesJorge Timón2015-07-231-0/+2
|
* use CBanEntry as object container for banned nodesJonas Schnelli2015-07-021-4/+8
| | | | | | | - added a reason enum for a ban - added creation time for a ban Using CBanEntry as container will keep banlist.dat extenable.
* banlist.dat: store banlist on diskJonas Schnelli2015-07-021-0/+2
|
* fix lock issue for QT node diconnect and RPC disconnectnodeJonas Schnelli2015-06-191-2/+2
|
* setban: add RPCErrorCodeJonas Schnelli2015-06-171-1/+1
|
* setban: rewrite to UniValue, allow absolute bantimeJonas Schnelli2015-06-171-11/+16
|
* rename json field "bannedtill" to "banned_until"Jonas Schnelli2015-06-171-1/+1
|
* [RPC] extend setban to allow subnetsJonas Schnelli2015-06-171-16/+28
|
* [RPC] add setban/listbanned/clearbanned RPC commandsJonas Schnelli2015-06-171-0/+89
|
* New RPC command disconnectnodeAlex van der Peet2015-06-161-0/+22
|
* Add paytxfee to getwalletinfo, warnings to getnetworkinfoStephen2015-06-111-0/+2
|
* use const references where appropriatePhilip Kaufmann2015-06-041-9/+8
|
* Remove JSON Spirit wrapper, remove JSON Spirit leftoversJonas Schnelli2015-06-041-9/+8
| | | | | | - implement find_value() function for UniValue - replace all Array/Value/Object types with UniValues, remove JSON Spirit to UniValue wrapper - remove JSON Spirit sources
* remove JSON Spirit UniValue wrapperJonas Schnelli2015-06-041-8/+8
|
* expicit set UniValue type to avoid empty valuesJonas Schnelli2015-06-041-16/+16
|
* Convert tree to using univalue. Eliminate all json_spirit uses.Jeff Garzik2015-06-041-4/+4
|
* privacy: Stream isolation for TorWladimir J. van der Laan2015-04-171-1/+2
| | | | | | | | | | | | | According to Tor's extensions to the SOCKS protocol (https://gitweb.torproject.org/torspec.git/tree/socks-extensions.txt) it is possible to perform stream isolation by providing authentication to the proxy. Each set of credentials will create a new circuit, which makes it harder to correlate connections. This patch adds an option, `-proxyrandomize` (on by default) that randomizes credentials for every outgoing connection, thus creating a new circuit. 2015-03-16 15:29:59 SOCKS5 Sending proxy authentication 3842137544:3256031132
* Removed main.h dependency from rpcserver.cppEric Lombrozo2015-01-281-2/+8
| | | | | | | | Rebased by @laanwj: - update for RPC methods added since 84d13ee: setmocktime, invalidateblock, reconsiderblock. Only the first, setmocktime, required a change, the other two are thread safe.
* Merge pull request #5476Wladimir J. van der Laan2015-01-021-0/+2
|\ | | | | | | | | 73caf47 Display time offset in the debug window's Peers tab (Pavel Janík) 26a6bae Add time offset to getpeerinfo output (Pavel Janík)
| * Add time offset to getpeerinfo outputPavel Janík2014-12-151-0/+2
| |
* | Added "Core" to copyright headerssandakersmann2014-12-191-1/+1
|/ | | | | Github-Pull: #5494 Rebased-From: 15de949bb9277e442302bdd8dee299a8d6deee60
* Update comments in src/rpc* to be doxygen compatibleMichael Ford2014-11-201-1/+1
|
* Separate protocol versioning from clientversionCory Fields2014-10-291-0/+1
|
* RPC additions after headers-firstPieter Wuille2014-10-141-2/+13
|
* Headers-first synchronizationPieter Wuille2014-10-141-1/+0
| | | | | | | | | | | | | | | Many changes: * Do not use 'getblocks', but 'getheaders', and use it to build a headers tree. * Blocks are fetched in parallel from all available outbound peers, using a limited moving window. When one peer stalls the movement of the window, it is disconnected. * No more orphan blocks. At all. We only ever request a block for which we have verified the headers, and store it to disk immediately. This means that a disk-fill attack would require PoW. * Require protocol version 31800 for every peer (released in december 2010). * No more syncnode (we sync from everyone we can, though limited to 1 during initial *headers* sync). * Introduce some extra named constants, comments and asserts.
* update getnetworkinfo help with subversionPhilip Kaufmann2014-10-011-18/+24
| | | | | | - add missing subversion field to getnetworkinfo help - fix style and format errors in help string - remove unneeded int casts
* RPC getnetworkinfo: export local node's client sub-version stringJeff Garzik2014-09-251-0/+3
|
* typo fix of booleamn to booleanimharrywu2014-09-181-1/+1
|
* minor changes for help message of getpeerinfoPhilip Kaufmann2014-09-161-2/+2
|
* header include cleanupPhilip Kaufmann2014-09-141-0/+1
| | | | - ensures alphabetical ordering for includes etc. in source file headers
* Add detailed network info to getnetworkinfo RPCWladimir J. van der Laan2014-08-181-5/+28
| | | | | | | | | | | This commit adds per-network information to the getnetworkinfo RPC call: - Is the network limited? - Is the network reachable - Which proxy is used for this network, if any Inspired by #2575.
* fix help message for RPC getpeerinfoPhilip Kaufmann2014-07-171-2/+1
|
* Add peerid to getpeerinfo to allow correlation with the logs.Gregory Maxwell2014-07-151-0/+2
| | | | This seems to have been missed in 3764.
* Introduce whitelisted peers.Pieter Wuille2014-07-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | This adds a -whitelist option to specify subnet ranges from which peers that connect are whitelisted. In addition, there is a -whitebind option which works like -bind, except peers connecting to it are also whitelisted (allowing a separate listen port for trusted connections). Being whitelisted has two effects (for now): * They are immune to DoS disconnection/banning. * Transactions they broadcast (which are valid) are always relayed, even if they were already in the mempool. This means that a node can function as a gateway for a local network, and that rebroadcasts from the local network will work as expected. Whitelisting replaces the magic exemption localhost had for DoS disconnection (local addresses are still never banned, though), which implied hidden service connects (from a localhost Tor node) were incorrectly immune to DoS disconnection as well. This old behaviour is removed for that reason, but can be restored using -whitelist=127.0.0.1 or -whitelist=::1 can be specified. -whitebind is safer to use in case non-trusted localhost connections are expected (like hidden services).
* remove SOCKS4 support from core and GUIPhilip Kaufmann2014-07-071-1/+1
| | | | - now we support SOCKS5 only
* Move fee policy out of coreGavin Andresen2014-07-031-1/+1
|
* Track peers' available blocksPieter Wuille2014-06-291-0/+1
|