aboutsummaryrefslogtreecommitdiff
path: root/src/init.cpp
Commit message (Collapse)AuthorAgeFilesLines
...
* | | Merge pull request #6055Wladimir J. van der Laan2015-05-061-1/+1
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | a8cdaf5 checkpoints: move the checkpoints enable boolean into main (Cory Fields) 11982d3 checkpoints: Decouple checkpoints from Params (Cory Fields) 6996823 checkpoints: make checkpoints a member of CChainParams (Cory Fields) 9f13a10 checkpoints: store mapCheckpoints in CCheckpointData rather than a pointer (Cory Fields)
| * | | checkpoints: move the checkpoints enable boolean into mainCory Fields2015-04-301-1/+1
| | | | | | | | | | | | | | | | | | | | This pertains to app-state, so it doesn't make sense to handle inside the checkpoint functions.
* | | | trivial: Merge pruning help message after Transifex commentWladimir J. van der Laan2015-05-041-5/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The prune help message was broken in nonsensical parts. Merge it into one, this is easier for translators. Reported by yahoe.001 on transifex.
* | | | Show an init message while activating best chainWladimir J. van der Laan2015-05-041-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | Connecting the chain can take quite a while. All the while it is still showing `Loading wallet...`. Add an init message to inform the user what is happening.
* | | | Merge pull request #6085Wladimir J. van der Laan2015-05-041-2/+2
|\ \ \ \ | |/ / / |/| | | | | | | | | | | b05a89b Non-grammatical language improvements (Luke Dashjr) 7e6d23b Bugfix: Grammar fixes (Corinne Dashjr)
| * | | Bugfix: Grammar fixesCorinne Dashjr2015-05-011-2/+2
| | | |
* | | | Merge pull request #6022Wladimir J. van der Laan2015-04-301-1/+1
|\ \ \ \ | |/ / / |/| | | | | | | b74dcb3 Separate CTranslationInterface from CClientUIInterface (Jorge Timón)
| * | | Separate CTranslationInterface from CClientUIInterfaceJorge Timón2015-04-161-1/+1
| | | |
* | | | Add block pruning functionalitymrbandrews2015-04-221-4/+86
| |/ / |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a -prune=N option to bitcoind, which if set to N>0 will enable block file pruning. When pruning is enabled, block and undo files will be deleted to try to keep total space used by those files to below the prune target (N, in MB) specified by the user, subject to some constraints: - The last 288 blocks on the main chain are always kept (MIN_BLOCKS_TO_KEEP), - N must be at least 550MB (chosen as a value for the target that could reasonably be met, with some assumptions about block sizes, orphan rates, etc; see comment in main.h), - No blocks are pruned until chainActive is at least 100,000 blocks long (on mainnet; defined separately for mainnet, testnet, and regtest in chainparams as nPruneAfterHeight). This unsets NODE_NETWORK if pruning is enabled. Also included is an RPC test for pruning (pruning.py). Thanks to @rdponticelli for earlier work on this feature; this is based in part off that work.
* | | Merge pull request #5911Wladimir J. van der Laan2015-04-201-6/+7
|\ \ \ | | | | | | | | | | | | | | | | 6be3562 rpc-tests: Add proxy test (Wladimir J. van der Laan) 67a7949 privacy: Stream isolation for Tor (Wladimir J. van der Laan)
| * | | privacy: Stream isolation for TorWladimir J. van der Laan2015-04-171-6/+7
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | | Make 'Default: %u' spacing consistent in help messageWladimir J. van der Laan2015-04-201-2/+2
| | | | | | | | | | | | Comment by pryds on Transifex.
* | | Fix typo in init.cpp interpration/interpretationMichael Ford2015-04-201-1/+1
|/ /
* | Merge pull request #5997Wladimir J. van der Laan2015-04-151-3/+4
|\ \ | | | | | | | | | 4e38217 Chainparams: Refactor: Remove redundant HashGenesisBlock() getter (Jorge Timón)
| * | Chainparams: Refactor: Remove redundant HashGenesisBlock() getterJorge Timón2015-04-121-3/+4
| | |
* | | Push down RPC reqWallet flagJonas Schnelli2015-04-121-5/+0
|/ /
* | Merge pull request #5951Wladimir J. van der Laan2015-04-081-0/+2
|\ \ | | | | | | | | | | | | 77650cc add -walletbroadcast=0 rpc test (Jonas Schnelli) 6f25262 wallet: make it possible to disable transaction broadcast (Wladimir J. van der Laan)
| * | wallet: make it possible to disable transaction broadcastWladimir J. van der Laan2015-04-011-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is an advanced feature which will disable any kind of automatic transaction broadcasting in the wallet. This gives the user full control of how the transaction is sent. For example they can broadcast new transactions through some other mechanism themselves, after getting the transaction hex through `gettransaction`. This just adds the option `-walletbroadcast=<0,1>`. Right now these transactions will get the status Status: conflicted, has not been successfully broadcast yet They shouldn't be shown as conflicted at all (`walletconflicts` is empty). This status will go away when the transaction is received through the network.
* | | Add a consistency check for the block chain data structuresPieter Wuille2015-03-271-2/+3
|/ / | | | | | | | | | | This adds a -checkblockindex (defaulting to true for regtest), which occasionally does a full consistency check for mapBlockIndex, setBlockIndexCandidates, chainActive, and mapBlocksUnlinked.
* | Fix --disable-wallet build after merge of #5681Wladimir J. van der Laan2015-03-241-0/+1
| |
* | refactor: move bdb (bitdb) interaction from init.cpp to wallet.cppJonas Schnelli2015-03-201-44/+13
| | | | | | | | this will remove db.h from init.cpp
* | [Move Only] Move wallet related things to src/wallet/Jonas Schnelli2015-03-121-3/+3
| | | | | | | | could once be renamed from /src/wallet to /src/legacywallet.
* | Fix - bitcoin-qt usage messageLuca Venturini2015-03-101-0/+13
| | | | | | | | | | | | | | . Closes the bug from commit e179eb3d9bfec7e67908242c71c87b716a41c97c ("bitcoin-qt -help" did not show any message) . Move all the options in init.cpp (there were already some options related to bitcoin-qt)
* | Help messages correctly formatted (79 chars)Luca Venturini2015-03-101-119/+123
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Help messages are formatted programmatically with FormatParagraph in order not to break existing strings in Transifex. The new format works even if the translation of the strings modifies the lenght of the message. Sqashed 6 commits in a single one. Help messages correctly formatted for SVGA text mode (132 chars) Help messages are formatted programmatically with FormatParagraph in order not to break existing strings in Transifex. The new format should work even if the translation of the strings modifies the lenght of the message. Fix - syntax error Correct formatting for 79 chars Correctly based on C++ functions Removed spare spaces from option strings Fix - syntax error
* | Merge pull request #5711Wladimir J. van der Laan2015-02-041-0/+22
|\ \ | | | | | | | | | | | | 5ebe095 Trim RPC command table (Wladimir J. van der Laan) 4401b2d Removed main.h dependency from rpcserver.cpp (Eric Lombrozo)
| * | Removed main.h dependency from rpcserver.cppEric Lombrozo2015-01-281-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | 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.
* | | Remove whitespaces before double colon in errors and logsPavel Janík2015-01-311-1/+1
|/ /
* | Merge pull request #5243Wladimir J. van der Laan2015-01-261-0/+5
|\ \ | | | | | | | | | ff09e31 sleep-wait on genesis block during init with -reindex (Matt Corallo)
| * | sleep-wait on genesis block during init with -reindexMatt Corallo2014-12-201-0/+5
| | |
* | | Merge pull request #4805Wladimir J. van der Laan2015-01-261-1/+3
|\ \ \ | | | | | | | | | | | | 44bc988 [Wallet] Do not flush the wallet in AddToWalletIfInvolvingMe(..) (Cozz Lovan)
| * | | [Wallet] Do not flush the wallet in AddToWalletIfInvolvingMe(..)Cozz Lovan2014-10-031-1/+3
| | | |
* | | | Restore RPC HTTP keepalives to default.Gregory Maxwell2015-01-161-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids a regression for issues like #334 where high speed repeated connections eventually run the HTTP client out of sockets because all of theirs end up in time_wait. Maybe the trade-off here is suboptimal, but if both choices will fail then we prefer fewer changes until the root cause is solved.
* | | | Add a -rpckeepalive and disable RPC use of HTTP persistent connections.Gregory Maxwell2015-01-141-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It turns out that some miners have been staying with old versions of Bitcoin Core because their software behaves poorly with persistent connections and the Bitcoin Core thread and connection limits. What happens is that underlying HTTP libraries leave connections open invisibly to their users and then the user runs into the default four thread limit. This looks like Bitcoin Core is unresponsive to RPC. There are many things that should be improved in Bitcoin Core's behavior here, e.g. supporting more concurrent connections, not tying up threads for idle connections, disconnecting kept-alive connections when limits are reached, etc. All are fairly big, risky changes. Disabling keep-alive is a simple workaround. It's often not easy to turn off the keep-alive support in the client where it may be buried in some platform library. If you are one of the few who really needs persistent connections you probably know that you want them and can find a switch; while if you don't and the misbehavior is hitting you it is hard to discover the source of your problems is keepalive related. Given that it is best to default to off until they're handled better.
* | | | Catch UTXO set read errors and shutdownPieter Wuille2015-01-081-1/+26
| | | |
* | | | Merge pull request #5535Wladimir J. van der Laan2015-01-071-0/+1
|\ \ \ \ | | | | | | | | | | | | | | | 1c52aad Require sufficent priority for relay of free transactions (Pieter Wuille)
| * | | | Require sufficent priority for relay of free transactionsPieter Wuille2014-12-301-0/+1
| | | | |
* | | | | namespace: remove boost namespace pollutionCory Fields2015-01-021-13/+12
|/ / / /
* | | | Merge pull request #5272Wladimir J. van der Laan2014-12-271-15/+20
|\ \ \ \ | | | | | | | | | | | | | | | 13f9031 init: minor parameter interaction updates (Philip Kaufmann)
| * | | | init: minor parameter interaction updatesPhilip Kaufmann2014-11-131-15/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - use __func__ instead of hard-coded function name for logging - update -discover help message to reflect newly added parameter interaction - use DEFAULT_LISTEN in a parameter interaction check instead a hard coded value
* | | | | en: Avoid ambiguous language regarding when transactions confirmLuke Dashjr2014-12-231-1/+1
| | | | |
* | | | | Merge pull request #5485Wladimir J. van der Laan2014-12-231-0/+15
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | aa279d6 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option. (Gregory Maxwell)
| * | | | | Enforce minRelayTxFee on wallet created tx and add a maxtxfee option.Gregory Maxwell2014-12-191-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the minRelayTxFee was only enforced on user specified values. It was possible for smartfee to produce a fee below minRelayTxFee which would just result in the transaction getting stuck because it can't be relayed. This also introduces a maxtxfee option which sets an absolute maximum for any fee created by the wallet, with an intention of increasing user confidence that the automatic fees won't burn them. This was frequently a concern even before smartfees. If the configured fee policy won't even allow the wallet to meet the relay fee the transaction creation may be aborted.
* | | | | | remove max orphan blocks config parameter since it is no longer functionalJameson Lopp2014-12-211-1/+0
| |_|_|/ / |/| | | |
* | | | | Added "Core" to copyright headerssandakersmann2014-12-191-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Github-Pull: #5494 Rebased-From: 15de949bb9277e442302bdd8dee299a8d6deee60
* | | | | make all catch() arguments constPhilip Kaufmann2014-12-171-3/+3
|/ / / / | | | | | | | | | | | | | | | | | | | | | | | | - I saw this on http://en.cppreference.com/w/cpp/language/try_catch and thought it would be a good idea - also unify used format to better be able to search for exception uses in our codebase
* | | | Make comments in main an init doxygen compatibleMichael Ford2014-12-021-5/+5
| | | | | | | | | | | | | | | | | | | | Fix typos where appropriate Update license/copyright
* | | | Remove -printblock, -printblocktree, and -printblockindexPieter Wuille2014-11-271-30/+0
| | | |
* | | | [REST] set REST API behind "-rest" optionJonas Schnelli2014-11-261-0/+1
| | | |
* | | | Merge pull request #5241Wladimir J. van der Laan2014-11-251-8/+3
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | a206950 Introduce separate flushing modes (Pieter Wuille) 51ce901 Improve chainstate/blockindex disk writing policy (Pieter Wuille)
| * | | | Improve chainstate/blockindex disk writing policyPieter Wuille2014-11-241-8/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There are 3 pieces of data that are maintained on disk. The actual block and undo data, the block index (which can refer to positions on disk), and the chainstate (which refers to the best block hash). Earlier, there was no guarantee that blocks were written to disk before block index entries referring to them were written. This commit introduces dirty flags for block index data, and delays writing entries until the actual block data is flushed. With this stricter ordering in writes, it is now safe to not always flush after every block, so there is no need for the IsInitialBlockDownload() check there - instead we just write whenever enough time has passed or the cache size grows too large. Also updating the wallet's best known block is delayed until this is done, otherwise the wallet may end up referring to an unknown block. In addition, only do a write inside the block processing loop if necessary (because of cache size exceeded). Otherwise, move the writing to a point after processing is done, after relaying.
generated by cgit v1.2.3 (git 2.25.1) at 2026-04-19 18:39:26 +0000