Jump to content

All Activity

This stream auto-updates     

  1. Earlier
  2. Skaro
    Maaku talking about merge mining Freicoin until forward blocks fully developed: https://github.com/tradecraftio/tradecraft/issues/64
  3. Mark Friedenbach
    Freicoin version 12.1.3-10161 is now available from: Linux 32-bit: https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-linux32.zip Linux 64-bit: https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-linux64.zip macOS (app): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-osx.dmg macOS (server): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-osx64.tar.gz Windows 32-bit (installer): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-win32-setup.exe Windows 32-bit (zip): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-win32.zip Windows 64-bit (installer): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-win64-setup.exe Windows 64-bit (zip): https://s3.amazonaws.com/in.freico.stable/freicoin-v12.1.3-10161-win64.zip Source: https://github.com/tradecraftio/tradecraft/archive/v12.1.3-10161.zip This is a new point release, enabling soft-fork deployment of the block-final transaction protocol rule update, a prerequisite for segregated witness and forward blocks. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Freicoin-Qt (on Mac) or freicoind/freicoin-qt (on Linux). Downgrade warning Because release v12 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with pre-v12 versions of Freicoin or other software. If you want to downgrade after you have done a reindex with v12 or later, you will need to reindex when you first start Freicoin version v11 or earlier. This does not affect wallet forward or backward compatibility. Notable changes Soft-fork deployment code for block-final transactions This release includes a soft fork deployment, using the BIP9 deployment mechanism, to enforce a scheme for making the final transaction of a block accessible to miners, for use by future soft-forks. The deployment sets the 2nd bit (1 << 1) of the block version number between midnight 2 July 2019 and midnight 16 April 2020 to signal readiness for deployment. Note that as a residual effect of the coinbase-MTP soft-fork, the high-order nyble of a block's version field must 0b0011 until 2 October 2019 (0b001 to indicate version bits, and the highest version bit set). The "locktime" soft-fork is also being signaled for during this time, using the first (1 << 0) version bit. Please see the v12.1.2-10135 release notes for more information regarding that soft-fork deployment. The status of the block-final soft-fork deployment can be queried as the "blockfinal" soft-fork reported by the `getblockchaininfo` RPC call. Should this soft-fork activate, there are additional steps that miners will be required to undertake in order for their blocks to validate. If you maintain mining or pool software, please see the next section for instructions. For more information about the soft-fork change, please see <https://github.com/tradecraftio/tradecraft/pull/46> BIP9: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki Block-final transactions for miner commitments Commitments made by miners in bitcoin, such as to the segregated witness data structure, are placed in the coinbase transaction. This is the easiest choice, as it is the one place in the block which miners have free control over the contents, and which supports non-trivial amounts of arbitrary data. However it is not an optimal location: proofs of miner commitments require a Merkle tree proof of the coinbase transaction, which is log(N) sized (where N is the number of transactions in the block). It has been known for some time that should the commitment be placed in the LAST transaction of a block, the size of the Merkle proof can be considerably reduced, even to the point of being a constant 32B if the number of transactions in a block is of the form (2^Z) + 1 for some integer Z. Furthermore if the commitment is placed at the end of this block-final transaction then midstate compression can be used to reduce the amount of additional information required by a proof to around 100B total. This minimized proof size is of considerable importance when we consider SPV proofs of witness data to mobile clients, or or block header commitments providing log-sized "proofs of proof of work" for sidechain pegs and other protocols. Having the last transaction of a block available for miners to use is also vitally important, it turns out, for various schemes that involve protocol-managed pots of funds, such as rebateable fees or the cross-shard transfers that are a part of forward blocks. In these proposals "anyone-can-spend" user outputs of a certain form are collected (spent) by the final transaction of the block in which they appear, where they are then carried forward from block-to-block in an unending chain until they are redeemed at which point they pass to the coinbase transaction as "fee" and are paid out in an output subject to coinbase maturity rules. Although elegant, the trouble with using the final transaction of a block for these purposes is that every transaction in a block after the coinbase is required to have inputs, and therefore in order to create such block-final transactions the miner must have access to at least one mature output it controls in the UTXO set. The solution is to chain the transactions together so that the outputs of the final transaction of one block are used as the inputs to the next block's final transaction. To get the process started, the coinbase of the block where activation occurs contains at least one anyone-can-spend output of this special form, and the new rules activate when that coinbase's outputs mature 100 blocks later. A block-final transaction is required to spend ALL the outputs of the prior block's final transaction, and the outputs it creates must be spendable with an empty scriptSig. Because transactions are required to have at least one output, this ensures that there is always an input available for the next block's final transaction. Additionally a block-final transaction is also allowed to gather inputs from the current block, or the just-matured coinbase from 100 blocks back, but no other input sources are allowed. Instructions for miners to create block-final transactions Upon activation, blocks are REQUIRED to have block-final transactions as described above, and miners MUST update their software or else they will find their blocks orphaned by the network. On the block which the [BIP9]() status of the "blockfinal" soft-fork switches from "locked_in" to "active", the coinbase MUST contain an output that can be successfully spent with an empty scriptSig, for which `scriptPubKey = CScript([OP_TRUE])` suffices. It is not recommended that mining software re-implement the BIP9 version bits soft-fork activation logic, due to the inherent risk of reimplementing consensus code. Instead it is recommended that mining software include a zero-valued OP_TRUE output in their coinbase if all three of the following conditions are met: The block height is a multiple of 2016 (`nHeight % 2016 == 0`); The [BIP9]() status of the "blockfinal" soft-fork is reported as "active" in the output of the `getblockchaininfo` RPC; and There is no "blockfinal" section in the output of the `getblocktemplate` RPC. This will produce the initial output that is required to get the block-final transaction chain going. Once the initial output matures, mining software must also produce block-final transactions correctly, and the necessary information for doing so is provided in the output of the `getblocktemplate` RPC: { ... "blockfinal": { "prevout": [ { "txid": ...(string) "vout": ...(numeric) "amount": ...(numeric) }, ... ], }, "locktime": ...(numeric) "height": ...(numeric) } The block-final transaction needs to include as inputs ALL of the UTXOs specified in the "prevout" array. It also needs to include at least one trivially spendable output (e.g. OP_TRUE). Finally, the block-final `nLockTime` and `lock_height` fields should be set to the same values specified in the "locktime" and "height" fields from the output of `getblocktemplate`. Note that construction of the block-final transaction WILL require additional steps in future soft-forks, which is why it must be constructed by the miner. Pay close attention to release notes for future releases. 12.1.3-10161 Change log `12cf4e24` [Checkpoint] Add recent checkpoint, block #256000. `25c92385` [DNSseed] Add new DNS seeds run by Tradecraft developers. PR #46 [FinalTx] Add block-final transactions, which are a sort of "2nd coinbase" generated by the miner _after_ all other transactions in a block, and a BIP9 soft-fork deployment mechanism to coodinate activation of this feature. Credits Thanks to who contributed to this release, including: Kalle Alm Mark Friedenbach As well as everyone that helped translating on Transifex: https://www.transifex.com/tradecraft/freicoin-1/.
  4. Mark Friedenbach
    A few months ago I was working on the donation matching code in order to perform an audited final payment. In the process I was consolidating funds from the 320 cold-storage foundation addresses into a single master key that has never been on a computer connected to the internet. No funds have been destroyed, except those lost to demurrage as part of the consolidation. I don't have the address for this key on hand wihle typing this, but it shouldn't be hard to work out -- I believe it's currently the highest value address on the chain, and you can find it simply enough by following the foundation funds. Additionally the current plan is that no funds will be destroyed. I believe this is explained elsewhere in another thread, but the idea is to use the remaining funds after the final donation match as a sort of protocol-controlled slush-fund buffer used to pay out cross-shard transfers, movements in and out of confidential transactions, and other forms of "coinbase payouts" defined by the forward blocks protocol. This will allow freicoin to continue operating and be responsive even if growth in the forward blocks outpace the 1MB main chain and a confirmation backlog develops. Once added to this fund the coins can never be removed from it, so it is effectively the same as destruction but in a way that benefits the protocol. However since this involves soft-fork "anyone-can-spend" outputs, the funds obviously can't be moved there until the forward block rule set has been written and activated. Until then, I regretfully remain keeper of the keys.
  5. Skaro
    I see a lot of consolidation of foundation funds are being made in the original foundation public keys. Have some funds also been destroyed? The explorer API for foundation balance which simply sums funds in and out of foundation keys (including demurrage) shows the Foundation balance around 44 million.
  6. CSA

    Demurrage Fees

    CSA replied to CSA's topic in Freicoin Discussion

    I was thinking of a dynamic calculation of the demurrage fee. Right now it is 5%. And this could be also the End Goal if Freicoin is established in the Crypto Economy, but right now it is hurting more the development of the coin. Keeping Freicoin is punished, but there is no way to spend any coin or lend it to someone, So it would better to have a demurrage fee based on current hash rate / cost and total transactions. The demurrage Fee should pay out the miners and give them an incentive of 10% percent higher than real invested cost into mining. Additional the increase of transactions would be an indicator of real use and could be also used as a factor to set up market realistic Fee. Example: Very rough one! 30.000.000 MIL Freicoins are circulating = 1.500.000 is the current Demurrage = round about 15.000 Dollar So if the total mining cost is only, let say 5.000 Dollar, then the incentive for mining would be 300%. Additionally, there must be a way to limit the hashrate reaching BTC-Wasting-Energy rates. ( i assume here that all demurrage fee goes to miner, I am not sure if this fact) Maybe this is something that could be solved in sort of Chain-Governance, (what is Difficult, because manipulation could take please) Freicoin itself, should not become an "Energy-Wasting" Monster. An example is also Freicoin Exchange itself (without criticizing it!) Withdrawal fee is 2% in order to keep the demurrage outflows balanced. But I doubt somebody will accept the loss of 2% coins, if the price reaches a level, that would be really hard to accept. For me, Demurrage Fee should pay miners to keep the chain going. But it should be not a punishment, as, in a world of alternatives, every rational human being would avoid keeping Freicoin and seeking for alternatives (>1000 exists). In a monetary system only with Freicoin as a single currency, people would seek to invest the coins, as that is the main logic of the theory. PS: I have created a freicoin discord (unofficial one). It is pretty silent, but I would be glad if we got you also in. https://discord.gg/gX7MxM2 Ty
  7. Mark Friedenbach
    What about it?
  8. CSA
    Hello community, i would like to start the discussion about the demmurage fees of 5 Percent.
  9.    Skaro reacted to a post in a topic: New release: Freicoin v12.1.2-10135
  10. Mark Friedenbach
    I don't know if there's a paper or anything looking at that. It is more a statement of our experience competing with other SHA-256 coins, and the bitcoin cash ecosystem experiencing exactly the same thing a number of years later. This sort of discussion should probably happen on the GitHub issue.
  11. Skaro
    Ok. You said that "It has been demonstrated that this only works for the dominant coin of a proof-of-work system". Do you have a reference to this?
  12. Mark Friedenbach
    Yes it is a blocker for forward blocks (meaning: forward blocks depends on this being finished) because the difficulty adjustment algorithm can only be changed as a soft-fork simultaneously with deployment of forward blocks.
  13. Skaro
    Hi Mark. That sounds interesting. But first of all, I understand the link you sent me: "Investigate replacing difficulty adjustment algorithm". I'm not sure I understand what you wrote: "a blocker for deploying forward blocks". Are they talking about the same thing?
  14. Mark Friedenbach
    Skaro, maybe you could help out on the following issue, a blocker for deploying forward blocks? https://github.com/tradecraftio/tradecraft/issues/3 If so, I could provide a bit more detail about my current thinking in regards to that.
  15. Skaro
    I'm not the greatest coder but if you have a math or numerical methods problem I could help.
  16.    Skaro reacted to a post in a topic: New release: Freicoin v12.1.2-10135
  17. Mark Friedenbach
    Freicoin version 12.1.2-10135 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new point release, enabling soft-fork deployment of a collection of time-lock related protocol features. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Freicoin-Qt (on Mac) or freicoind/freicoin-qt (on Linux). Downgrade to a version < v12 Because release v12 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with pre-v12 versions of Freicoin or other software. If you want to downgrade after you have done a reindex with v12 or later, you will need to reindex when you first start Freicoin version v11 or earlier. This does not affect wallet forward or backward compatibility. Notable changes First version bits BIP9 softfork deployment This release includes a soft fork deployment to enforce BIP68 and BIP113 using the BIP9 deployment mechanism. The deployment sets the block version number to 0x30000001 between midnight 16 April 2019 and midnight 2 October 2019 to signal readiness for deployment. The version number consists of 0x30000000 to indicate version bits together with setting bit 0 to indicate support for this combined deployment, shown as "locktime" in the `getblockchaininfo` RPC call. (The leading bits to indicate version bits is actually 0x20000000, but version bits MUST be indicated and bit 28 set during this time period due to the earlier deployment of the coinbase-MTP soft-fork.) For more information about the soft forking change, please see: https://github.com/bitcoin/bitcoin/pull/7648 This specific backport pull-request to v0.12.1 of bitcoin, which this release is based off of, can be viewed at: https://github.com/bitcoin/bitcoin/pull/7543 Unlike bitcoin, this soft-fork deployment does NOT include support for BIP112, which provides the CHECKSEQUENCEVERIFY opcode. Support for checking sequence locks in script will be added as part of the script overhaul in segwit, scheduled for deployment with Freicoin v13. For more information regarding these soft-forks, and the implications for miners and users, please see the release notes accompanying v12.1-10123. [BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki [BIP65]: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki [BIP68]: https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki [BIP112]: https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki [BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki 12.1.2-10135 Change log `26c3508b` [Chainparams] Add recent checkpoint, block #250992. `989cc70c` [Consensus] Add activation logic for BIP68 and BIP113. Credits Thanks to who contributed to this release, including: Mark Friedenbach As well as everyone that helped translating on Transifex.
  18.    Skaro reacted to a post in a topic: New release: Freicoin v12.1-10123
  19.    Skaro reacted to a post in a topic: New release: Freicoin v12.1.1-10130
  20.    Skaro reacted to a post in a topic: The end of the foundation
  21. Mark Friedenbach
    For transparency's sake, here is the current listing of charitable organizations and the donations + matched funds that are owed to them: 'Abundant Currency Project', 29 (rejected) Donation: 0.00000000 Matched: 0.00000000 Payout: 0.00000000 Todo: 0.00000000 'Community Forge', 17 (validated) Donation: 1,996.60765506 Matched: 1,996.60765506 Payout: 1,096.20734614 Todo: 2,897.00796398 'Complementary Currency Resource Center', 28 (validated) Donation: 1,000.00000000 Matched: 1,000.00000000 Payout: 1,099.54585847 Todo: 900.45414153 'Cooperativa Integral Catalana', 14 (validated) Donation: 15,477.73483244 Matched: 15,477.73483244 Payout: 9,094.37501836 Todo: 21,861.09464652 'Drupal Commerce Marketplace', 16 (validated) Donation: 798.57617174 Matched: 798.57617174 Payout: 438.40659107 Todo: 1,158.74575241 'F-LAT', 27 (validated) Donation: 100.00420000 Matched: 100.00420000 Payout: 109.69829446 Todo: 90.31010554 'Free Knowledge Institute', 15 (validated) Donation: 3,695.07701553 Matched: 3,695.07701553 Payout: 2,623.76520409 Todo: 4,766.38882697 'Freicoin Alliance', 32 (validated) Donation: 1,286,335.57425855 Matched: 1,286,335.57425855 Payout: 1,105,617.40589899 Todo: 1,467,053.74261811 'Freicoin Foundation', 13 (validated) Donation: 79,751.56464159 Matched: 79,751.56464159 Payout: 16,930.21046862 Todo: 142,572.91881456 'FreiHemp Project', 33 (rejected) Donation: 0.00000000 Matched: 0.00000000 Payout: 0.00000000 Todo: 0.00000000 'Freimarkets protocol extension', 20 (validated) Donation: 17,595.86014102 Matched: 17,595.86014102 Payout: 13,304.66222175 Todo: 21,887.05806029 'IFLAS', 22 (validated) Donation: 1,997.61752895 Matched: 1,997.61752895 Payout: 1,097.31815021 Todo: 2,897.91690769 'INEVAL', 30 (validated) Donation: 500.00420000 Matched: 500.00420000 Payout: 524.24229693 Todo: 475.76610307 'Lifeboat Foundation', 19 (validated) Donation: 998.31990102 Matched: 998.31990102 Payout: 548.11904312 Todo: 1,448.52075892 'Munitario', 26 (validated) Donation: 1,000.00000000 Matched: 1,000.00000000 Payout: 1,096.49968184 Todo: 903.50031816 'New Economics Foundation', 21 (validated) Donation: 2,007.61912687 Matched: 2,007.61912687 Payout: 1,108.31726563 Todo: 2,906.92098811 'NWACPE Institute', 31 (validated) Donation: 88.91380667 Matched: 88.91380667 Payout: 93.40596225 Todo: 84.42165109 'Post Growth Institute', 24 (validated) Donation: 1,010.00420000 Matched: 1,010.00420000 Payout: 1,107.94076708 Todo: 912.06763292 'The Zaryvakhin Foundation', 23 (validated) Donation: 2,008.45545557 Matched: 2,008.45545557 Payout: 1,109.23580475 Todo: 2,907.67510639 'Umeed Foundation', 25 (validated) Donation: 0.00000000 Matched: 0.00000000 Payout: 0.00000000 Todo: 0.00000000 Totals: Donation: 1,416,361.93313501 Matched: 1,416,361.93313501 Payout: 1,156,999.35587376 Todo: 1,675,724.51039626 The first number "Donation" is how much freicoin in aggregate has been received at the donation addresses. "Matched" is the (tentative) amount the Freicoin Foundation would be contributing in up to 100% matches from initial-distribution funds. This number might change when the cycle-detection code is turned back on. "Payout" is the amount that has been paid out to the organization already, and "Todo" is what still needs to be paid.
  22. Skaro
    Hi Mark. Thanks. I was waiting for the 12.1 .1.
  23. Mark Friedenbach
    Freicoin version 12.1.1-10130 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new bug fix release, fixing an erroneous report of unexpected version / possible versionbits upgrade on all platforms. Upgrading to this release is recommended but not required. Please report bugs using the issue tracker at github: https://github.com/tradecraftio/tradecraft/issues How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Freicoin-Qt (on Mac) or freicoind/freicoin-qt (on Linux). Notable changes Erroneous versionbits upgrade notice The recent soft-fork to force vtx[0].nLockTime to be the current median-time-past requires that blocks signal for version bits and set bit #28, and to keep setting this bit once activated until 2 Oct 2019. On BIP9 versionbits-aware clients such as v12.1, this set bit is erroneously interpreted as activation of an unknown consensus rule, and the user is alerted to upgrade. This alert is generated in error and can be safely ignored in this case. However this category of alert is serious and so as to prevent user complacency in the future we are issuing a new point release to eliminate this warning. Beginning with v12.1.1, setting versionbit #28 will not trigger warnings about the activation of new consensus rules until 2 Oct 2019 (2 Apr 2019 on testnet). [BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki 12.1.1-10130 Change log `658b0cde1` [Alert] Do not warn about unexpected versionbits upgrade for the forced setting of bit 28 before Oct 2, 2019. `f338bd9d4` [BIP9] The last deployed pre-versionbits block version on Freicoin was 3, not 4. Credits Thanks to who contributed to this release, including: Fredrik Bodin Mark Friedenbach As well as everyone that helped translating on Transifex.
  24. Skaro
    Oh yeah
  25. Mark Friedenbach
    Freicoin version 12.1-10123 is now available from: Linux 32-bit Linux 64-bit macOS (app) macOS (server) Windows 32-bit (installer) Windows 32-bit (zip) Windows 64-bit (installer) Windows 64-bit (zip) Source This is a new major version release, bringing sequence locks and lock-time soft-fork, new features, and other improvements. Please report bugs using the issue tracker at github. Upgrading and downgrading How to Upgrade If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer (on Windows) or just copy over /Applications/Freicoin-Qt (on Mac) or freicoind/freicoin-qt (on Linux). Downgrade to a version < v12 Because release v12 and later will obfuscate the chainstate on every fresh sync or reindex, the chainstate is not backwards-compatible with pre-v12 versions of Freicoin or other software. If you want to downgrade after you have done a reindex with v12 or later, you will need to reindex when you first start Freicoin version v11 or earlier. Downgrade to a version < v10 Because release v10 and later makes use of headers-first synchronization and parallel block download (see further), the block files and databases are not backwards-compatible with pre-v10 versions of Freicoin or other software: Blocks will be stored on disk out of order (in the order they are received, really), which makes it incompatible with some tools or other programs. Reindexing using earlier versions will also not work anymore as a result of this. The block index database will now hold headers for which no block is stored on disk, which earlier versions won't support. If you want to be able to downgrade smoothly, make a backup of your entire data directory. Without this your node will need start syncing (or importing from bootstrap.dat) anew afterwards. It is possible that the data from a completely synchronised 0.10 node may be usable in older versions as-is, but this is not supported and may break as soon as the older version attempts to reindex. This does not affect wallet forward or backward compatibility. Notable changes Preparation for first version bits BIP9 softfork deployment This release includes all except for the activation logic for a soft fork deployment to enforce BIP68 and BIP113 using the BIP9 deployment mechanism. A future release of the v12 series will include the BIP9 activation parameters. For more information about the soft forking change, please see <https://github.com/bitcoin/bitcoin/pull/7648> This specific backport pull-request to v0.12.1 of bitcoin, which this release is based off of, can be viewed at <https://github.com/bitcoin/bitcoin/pull/7543> Unlike bitcoin, this soft-fork deployment does NOT include support for BIP112, which provides the CHECKSEQUENCEVERIFY opcode. Support for checking sequence locks in script will be added as part of the script overhaul in segwit, scheduled for deployment with Freicoin v13. [BIP9]: https://github.com/bitcoin/bips/blob/master/bip-0009.mediawiki [BIP65]: https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki [BIP68]: https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki [BIP112]: https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki [BIP113]: https://github.com/bitcoin/bips/blob/master/bip-0113.mediawiki BIP68 soft fork to enforce sequence locks for relative locktime BIP68 introduces relative lock-time consensus-enforced semantics of the sequence number field to enable a signed transaction input to remain invalid for a defined period of time after confirmation of its corresponding outpoint. For more information about the implementation, see <https://github.com/bitcoin/bitcoin/pull/7184> BIP113 locktime enforcement soft fork Freicoin v11 previously introduced mempool-only locktime enforcement using GetMedianTimePast(). This release seeks to consensus enforce the rule. Freicoin transactions currently may specify a locktime indicating when they may be added to a valid block. Current consensus rules require that blocks have a block header time greater than the locktime specified in any transaction in that block. Miners get to choose what time they use for their header time, with the consensus rule being that no node will accept a block whose time is more than two hours in the future. This creates a incentive for miners to set their header times to future values in order to include locktimed transactions which weren't supposed to be included for up to two more hours. The consensus rules also specify that valid blocks may have a header time greater than that of the median of the 11 previous blocks. This GetMedianTimePast() time has a key feature we generally associate with time: it can't go backwards. BIP113 specifies a soft fork enforced in this release that weakens this perverse incentive for individual miners to use a future time by requiring that valid blocks have a computed GetMedianTimePast() greater than the locktime specified in any transaction in that block. Mempool inclusion rules currently require transactions to be valid for immediate inclusion in a block in order to be accepted into the mempool. This release begins applying the BIP113 rule to received transactions, so transaction whose time is greater than the GetMedianTimePast() will no longer be accepted into the mempool. Implication for miners: you will begin rejecting transactions that would not be valid under BIP113, which will prevent you from producing invalid blocks when BIP113 is enforced on the network. Any transactions which are valid under the current rules but not yet valid under the BIP113 rules will either be mined by other miners or delayed until they are valid under BIP113. Note, however, that time-based locktime transactions are more or less unseen on the network currently. Implication for users: GetMedianTimePast() always trails behind the current time, so a transaction locktime set to the present time will be rejected by nodes running this release until the median time moves forward. To compensate, subtract one hour (3,600 seconds) from your locktimes to allow those transactions to be included in mempools at approximately the expected time. For more information about the implementation, see <https://github.com/bitcoin/bitcoin/pull/6566> BIP65 new opcode CHECKLOCKTIMEVERIFY This release includes several changes related to the BIP65 soft fork which redefines the existing NOP2 opcode as CHECKLOCKTIMEVERIFY (CLTV) so that a transaction output can be made unspendable until a specified point in the future. Freicoin v12 contains an implementation of CLTV which is not included in the locklock soft-fork deployment. It is currently anticipated that it will NOT be deployed to pre-segwit scripts, in order to preserve space for Forward Blocks scriptPubKey prefixes. For more information about the implementation, see <https://github.com/bitcoin/bitcoin/pull/6124> BIP112 new opcode CHECKSEQUENCEVERIFY BIP112 redefines the existing NOP3 as CHECKSEQUENCEVERIFY (CSV) for a new opcode in the Freicoin scripting system that in combination with BIP68 allows execution pathways of a script to be restricted based on the age of the output being spent. Freicoin v12 contains an implementation of CSV which is *not* included in the locklock soft-fork deployment. It is currently anticipated that it will NOT be deployed to pre-segwit scripts, in order to preserve space for Forward Blocks scriptPubKey prefixes. For more information about the implementation, see <https://github.com/bitcoin/bitcoin/pull/7524> SCRIPT_VERIFY_REQUIRE_VALID_SIGS A new rule is introduced which considers a transaction as non-standard if verification of that transaction requires a failed signature check, even if the script is written in such a way as to allow that failure. Evaluating such a script is still possible, but the CHECKSIG opcode must be provided with an empty / zero-length signature value, or k such empty values for a k-of-n CHECKMULTISIG. Since the mapping of signatures to keys was not previouly specified in the inputs of a CHECKMULTISIG, the additional extra/unused dummy argument to CHECKMULTISIG is required to be a bitfield specifying which public keys do NOT have corresponding signatures. Wallets which sign for multisig outputs MUST be updated to produce this bitfield in order for the generated transaction to be considered standard and relayed by upgraded nodes. This change is currently not scheduled for consensus enforcement, but eventually it will be as it is necessary in order to allow for batch validation of ECDSA signatures. For now it elimiates a source of witness malleability that presented a nuisance and possible DoS vector. Eventually soft-fork logic will be added to a future release once it is observed that most if not all wallets are producing conformant transactions. Implications for miners: No special action is required. Transactions which violate this rule will be rejected and not enter into your mempool, if you run with the default policy settings. Implications for users: In order to have your transactions relayed and reliably included in a block, your wallet must create the skipped key bitfield parameter for multisig scripts. The reference Freicoin wallet has been updated to generate these values. If your third party wallet software does not create conformant transactions, you may have Freicoin generate this value for you by passing the already-signed transaction through the `signrawtransaction` RPC, which will inject the proper skipped key bitfield when it re-serializes the scriptSig in its internal "combine signatures" step. Note that this necessarily malleates the transaction, changing its txid and invalidating any pre-signed dependent transactions. Finally, it is possible, though very unlikely, that someone out there has outputs controlled by a P2SH redeem script written in such a way as to require passing an invalid signature to a non-verify CHECKSIG (e.g. because the output of the CHECKSIG is then used as a branching condition), or by a multisig script where the dummy value is injected by the scriptPubKey or redeem script. If you know this applies to you, then you are encouraged in the strongest possible terms to move your funds to new scripts as quickly as possible. Once it is observed that people making regular transactions have upgraded, a soft fork to add SCRIPT_VERIFY_REQUIRE_VALID_SIGS to the consensus rules will be scheduled, which will make your funds permanently inaccessible. (If you are not sure if this applies to you, then it almost certainly does not. The development team's prior expectation is that nobody is using scripts in such a way as to have their funds permanently inaccessible as a result of this change, and they would only be doing so as a result of a conscious choice.) If you believe you are affected by these changes and are not able to move your funds, please contact the development team, e.g. by filing an issue on our issue tracker, or by email if your situation requires discretion. Signature validation using libsecp256k1 ECDSA signatures inside Freicoin transactions are now validated with libsecp256k1 instead of OpenSSL. Depending on the platform, this means a significant speedup for raw signature validation speed. The advantage is largest on x86_64, where validation is over five times faster. In practice, this translates to a raw reindexing and new block validation times that are less than half of what it was before. Libsecp256k1 has undergone very extensive testing and validation. A side effect of this change is that libconsensus no longer depends on OpenSSL. Block file and undo file size v10 introduced the time-delayed protocol-cleanup rule change, which required increasing the maximum block file size from 128 MB to nearly 2GB. This setting controls the size of the blk*.dat and rev*.dat files in the `blocks` subdirectory of the Freicoin data directory. Starting in v12, the original 128 MB limit is restored until the protocol cleanup rule change activates. Existing files will not be rewritten, however, so if you were at any point running a v10 or v11 client prior to 2 April 2021 you may have some historical block chain data files that are larger than 128 MB. This will not interfere with normal operation of your client. Should you wish to split these files up you will need to shutdown your node, delete the `blocks` subdirectory, and restart your node to re-download and re-index the block chain. Reduce upload traffic A major part of the outbound traffic is caused by serving historic blocks to other nodes in initial block download state. It is now possible to reduce the total upload traffic via the `-maxuploadtarget` parameter. This is *not* a hard limit but a threshold to minimize the outbound traffic. When the limit is about to be reached, the uploaded data is cut by not serving historic blocks (blocks older than one week). Moreover, any SPV peer is disconnected when they request a filtered block. This option can be specified in MiB per day and is turned off by default (`-maxuploadtarget=0`). The recommended minimum is 144 * MAX_BLOCK_SIZE (currently 144MB) per day. Whitelisted peers will never be disconnected, although their traffic counts for calculating the target. A more detailed documentation about keeping traffic low can be found in https://github.com/tradecraftio/tradecraft/blob/devel/doc/reduce-traffic.md. Direct headers announcement (BIP130) Between compatible peers, BIP130 direct headers announcement is used. This means that blocks are advertised by announcing their headers directly, instead of just announcing the hash. In a reorganization, all new headers are sent, instead of just the new tip. This can often prevent an extra roundtrip before the actual block is downloaded. With this change, pruning nodes are now able to relay new blocks to compatible peers. Memory pool limiting Previous versions of Freicoin had their mempool limited by checking a transaction's fees against the node's minimum relay fee. There was no upper bound on the size of the mempool and attackers could send a large number of transactions paying just slightly more than the default minimum relay fee to crash nodes with relatively low RAM. A temporary workaround for previous versions of Freicoin was to raise the default minimum relay fee. Freicoin v12 has a strict maximum size on the mempool. The default value is 300 MB and can be configured with the `-maxmempool` parameter. Whenever a transaction would cause the mempool to exceed its maximum size, the transaction that (along with in-mempool descendants) has the lowest total feerate (as a package) will be evicted and the node's effective minimum relay feerate will be increased to match this feerate plus the initial minimum relay feerate. The initial minimum relay feerate is set to 1000 kria per kB. Freicoin v12 also introduces new default policy limits on the length and size of unconfirmed transaction chains that are allowed in the mempool (generally limiting the length of unconfirmed chains to 25 transactions, with a total size of 101 KB). These limits can be overriden using command line arguments; see the extended help (`--help -help-debug`) for more information. Replace-by-fee transaction semantics Freicoin v12 introduces replace-by-fee transaction semantics, where one or more transactions in the mempool can be replaced by a conflicting transaction that pays a greater amount of fee. The criteria for replacing transactions is at this time unchanged from bitcoin's BIP125, except that ALL transactions are treated as having explicit replace-by-fee semantics regardless of whether it has any non-final inputs. Namely, One or more transactions currently in the mempool (original transactions) will be replaced by a new transaction (replacement transaction) that spends one or more of the same inputs if, (Rule #1 of BIP125 having to do with opt-in replace-by-signaling has been removed. All transactions are treated as replaceable.) The replacement transaction may only include an unconfirmed input if that input was included in one of the original transactions. (An unconfirmed input spends an output from a currently-unconfirmed transaction.) The replacement transaction pays an absolute fee of at least the sum paid by the original transactions. The replacement transaction must also pay for its own bandwidth at or above the rate set by the node's minimum relay fee setting. For example, if the minimum relay fee is 1 kria/byte and the replacement transaction is 500 bytes total, then the replacement must pay a fee at least 500 kria higher than the sum of the originals. The number of original transactions to be replaced and their descendant transactions which will be evicted from the mempool must not exceed a total of 100 transactions. Be advised that the Freicoin development team is looking into altering these rules further in future releases. Specifically, changes currently under consideration for future releases include: Batch replace-by-fee semantics in which potentially many replacement transactions are considered for simultaneous RBF replacement. This would allow a child transaction to provide the necessary fee to cover replacement of its unconfirmed and conflicting parent. This would necessarily have to be accompanied by batch transaction relay, where more than one transaction are relayed together at the network layer and processed as a group, in instances where the dependent transaction(s) pay higher fee rate than the parent. Strict fee-rate instead of absolute-fee consideration. The BIP125 rules for transaction replacement are not incentive aligned with miners in a blocks-always-full regime, who have incentives structured to make them care more about fee rate than absolute fee. No mechanims is provided for disabling transaction replacement. Should you wish to keep a transaction from being replaced in your own mempool, the `prioritisetransaction` RPC allows assigning a transaction an additional, fake fee with which to bias the replace-by-fee calculation. Implication for miners: you don't need to do anything. Your Freicoin node will automatically eject lower-fee transactions from its mempool in favor of transactions paying sufficiently higher fee, and the blocks you mine using block templates generated by your node will automatically include the transactions from your mempool paying the highest fees. Should you wish to keep a transaction from being replaced in your own mempool, and therefore chosen over conflicting transactions in blocks that you mine, you should make use of the `prioritisetransaction` RPC. Implication for users: transactions involving any outputs you do not have sole spending authority over should not be considered trusted until they have received a sufficient number of block confirmations. This was true before, but is even more relevant now. All transactions are considered replaceable, so there is nothing you or your wallet needs to do to signal this capability. Note that the graphical wallet in Freicoin v12 does not yet have support for creating transactions which conflict with known wallet transactions for the purpose of triggering mempool replacement. Such transactions can be generated with the JSON-RPC interface however, and the wallet will display details of conflicting transactions it does know about. [BIP125]: https://github.com/bitcoin/bips/blob/master/bip-0125.mediawiki RPC: Random-cookie RPC authentication When no `-rpcpassword` is specified, the daemon now uses a special 'cookie' file for authentication. This file is generated with random content when the daemon starts, and deleted when it exits. Its contents are used as authentication token. Read access to this file controls who can access through RPC. By default it is stored in the data directory but its location can be overridden with the option `-rpccookiefile`. This is similar to Tor's CookieAuthentication: see https://www.torproject.org/docs/tor-manual.html.en This allows running freicoind without having to do any manual configuration. Relay and Mining: Priority transactions Freicoin has a heuristic 'priority' based on coin value and age. This calculation is used for relaying of transactions which do not pay the minimum relay fee, and can be used as an alternative way of sorting transactions for mined blocks. Freicoin will relay transactions with insufficient fees depending on the setting of `-limitfreerelay=<r>` (default: `r=15` kB per minute) and `-blockprioritysize=<s>` (default `s=25000` or 25kB). In Freicoin v12, when mempool limit has been reached a higher minimum relay fee takes effect to limit memory usage. Transactions which do not meet this higher effective minimum relay fee will not be relayed or mined even if they rank highly according to the priority heuristic. Additionally, as a result of computational simplifications, the priority value used for transactions received with unconfirmed inputs is lower than in prior versions due to avoiding recomputing the amounts as input transactions confirm. External miner policy set via the `prioritisetransaction` RPC to rank transactions already in the mempool continues to work as it has previously. Note, however, that if mining priority transactions is left disabled, the priority delta will be ignored and only the fee metric will be effective. This internal automatic prioritization handling is being considered for removal entirely in future Freicoin releases, and the more accurate priority calculation for chained unconfirmed transactions will be restored in Freicoin v13. Automatically use Tor hidden services Starting with Tor version 0.2.7.1 it is possible, through Tor's control socket API, to create and destroy 'ephemeral' hidden services programmatically. Freicoin has been updated to make use of this. This means that if Tor is running (and proper authorization is available), Freicoin automatically creates a hidden service to listen on, without manual configuration. Freicoin will also use Tor automatically to connect to other .onion nodes if the control socket can be successfully opened. This will positively affect the number of available .onion nodes and their usage. This new feature is enabled by default if Freicoin is listening, and a connection to Tor can be made. It can be configured with the `-listenonion`, `-torcontrol` and `-torpassword` settings. To show verbose debugging information, pass `-debug=tor`. Notifications through ZMQ freicoind can now (optionally) asynchronously notify clients through a ZMQ-based PUB socket of the arrival of new transactions and blocks. This feature requires installation of the ZMQ C API library 4.x and configuring its use through the command line or configuration file. Please see [docs/zmq.md](/doc/zmq.md) for details of operation. Wallet: Transaction fees Various improvements have been made to how the wallet calculates transaction fees. Users can decide to pay a predefined fee rate by setting `-paytxfee=<n>` (or `settxfee <n>` rpc during runtime). A value of `n=0` signals Freicoin to use floating fees. By default, Freicoin will use floating fees. Based on past transaction data, floating fees approximate the fees required to get into the `m`th block from now. This is configurable with `-txconfirmtarget=<m>` (default: `2`). Sometimes, it is not possible to give good estimates, or an estimate at all. Therefore, a fallback value can be set with `-fallbackfee=<f>` (default: `0.0002` FRC/kB). At all times, Freicoin will cap fees at `-maxtxfee=<x>` (default: 0.10) FRC. Furthermore, Freicoin will never create transactions paying less than the current minimum relay fee. Finally, a user can set the minimum fee rate for all transactions with `-mintxfee=<i>`, which defaults to 1000 kria per kB. Wallet: Negative confirmations and conflict detection The wallet will now report a negative number for confirmations that indicates how deep in the block chain the conflict is found. For example, if a transaction A has 5 confirmations and spends the same input as a wallet transaction B, B will be reported as having -5 confirmations. If another wallet transaction C spends an output from B, it will also be reported as having -5 confirmations. To detect conflicts with historical transactions in the chain a one-time `-rescan` may be needed. Unlike earlier versions, unconfirmed but non-conflicting transactions will never get a negative confirmation count. They are not treated as spendable unless they're coming from ourself (change) and accepted into our local mempool, however. The new "trusted" field in the `listtransactions` RPC output indicates whether outputs of an unconfirmed transaction are considered spendable. Wallet: Merkle branches removed Previously, every wallet transaction stored a Merkle branch to prove its presence in blocks. This wasn't being used for more than an expensive sanity check. Since v12, these are no longer stored. When loading a v12 wallet into an older version, it will automatically rescan to avoid failed checks. Wallet: Pruning With v12 it is possible to use wallet functionality in pruned mode. This currently does not affect disk usage, but does limit future disk usage to around 1 GB as extrapolated from current numbers. However, rescans as well as the RPCs `importwallet`, `importaddress`, `importprivkey` are disabled. To enable block pruning set `prune=<N>` on the command line or in `freicoin.conf`, where `N` is the number of MiB to allot for raw block & undo data. A value of 0 disables pruning. The minimal value above 0 is 550. Your wallet is as secure with high values as it is with low ones. Higher values merely ensure that your node will not shut down upon blockchain reorganizations of more than 2 days - which are unlikely to happen in practice. In future releases, a higher value may also help the network as a whole: stored blocks could be served to other nodes. For further information about pruning, you may also consult the release notes of v11.3. `NODE_BLOOM` service bit Support for the `NODE_BLOOM` service bit, as described in BIP111, has been added to the P2P protocol code. BIP 111 defines a service bit to allow peers to advertise that they support bloom filters (such as used by SPV clients) explicitly. It also bumps the protocol version to allow peers to identify old nodes which allow bloom filtering of the connection despite lacking the new service bit. In this version, it is only enforced for peers that send protocol versions `>=70011`. For the next major version it is planned that this restriction will be removed. It is recommended to update SPV clients to check for the `NODE_BLOOM` service bit for nodes that report versions newer than 70011. Option parsing behavior Command line options are now parsed strictly in the order in which they are specified. It used to be the case that `-X -noX` ends up, unintuitively, with X set, as `-X` had precedence over `-noX`. This is no longer the case. Like for other software, the last specified value for an option will hold. RPC: Low-level API changes Monetary amounts can be provided as strings. This means that for example the argument to sendtoaddress can be "0.0001" instead of 0.0001. This can be an advantage if a JSON library insists on using a lossy floating point type for numbers, which would be dangerous for monetary amounts. The `asm` property of each scriptSig now contains the decoded signature hash type for each signature that provides a valid defined hash type. NOP2 has been renamed to CHECKLOCKTIMEVERIFY by BIP65 NOP3 has been renamed to CHECKSEQUENCEVERIFY by BIP112 The following items contain assembly representations of scriptSig signatures and are affected by this change: RPC `getrawtransaction` RPC `decoderawtransaction` RPC `decodescript` REST `/rest/tx/` (JSON format) REST `/rest/block/` (JSON format when including extended tx details) `freicoin-tx -json` For example, the `scriptSig.asm` property of a transaction input that previously showed an assembly representation of: 304502207fa7a6d1e0ee81132a269ad84e68d695483745cde8b541e3bf630749894e342a022100c1f7ab20e13e22fb95281a870f3dcf38d782e53023ee313d741ad0cfbc0c509001 400000 NOP2 now shows as: 304502207fa7a6d1e0ee81132a269ad84e68d695483745cde8b541e3bf630749894e342a022100c1f7ab20e13e22fb95281a870f3dcf38d782e53023ee313d741ad0cfbc0c5090[ALL] 400000 CHECKLOCKTIMEVERIFY Note that the output of the RPC `decodescript` did not change because it is configured specifically to process scriptPubKey and not scriptSig scripts. RPC: SSL support dropped SSL support for RPC, previously enabled by the option `rpcssl` has been dropped from both the client and the server. This was done in preparation for removing the dependency on OpenSSL for the daemon completely. Trying to use `rpcssl` will result in an error: Error: SSL mode for RPC (-rpcssl) is no longer supported. If you are one of the few people that relies on this feature, a flexible migration path is to use `stunnel`. This is an utility that can tunnel arbitrary TCP connections inside SSL. On e.g. Ubuntu it can be installed with: sudo apt-get install stunnel4 Then, to tunnel a SSL connection on 28638 to a RPC server bound on localhost on port 18638 do: stunnel -d 28638 -r 127.0.0.1:18638 -p stunnel.pem -P '' It can also be set up system-wide in inetd style. Another way to re-attain SSL would be to setup a httpd reverse proxy. This solution would allow the use of different authentication, load-balancing, on-the-fly compression and caching. A sample config for apache2 could look like: Listen 443 NameVirtualHost *:443 <VirtualHost *:443> SSLEngine On SSLCertificateFile /etc/apache2/ssl/server.crt SSLCertificateKeyFile /etc/apache2/ssl/server.key <Location /freicoinrpc> ProxyPass http://127.0.0.1:8638/ ProxyPassReverse http://127.0.0.1:8638/ # optional enable digest auth # AuthType Digest # ... # optional bypass freicoind rpc basic auth # RequestHeader set Authorization "Basic <hash>" # get the <hash> from the shell with: base64 <<< freicoinrpc:<password> </Location> # Or, balance the load: # ProxyPass / balancer://balancer_cluster_name </VirtualHost> Mining Code Changes The mining code in v12 has been optimized to be significantly faster and use less memory. As part of these changes, consensus critical calculations are cached on a transaction's acceptance into the mempool and the mining code now relies on the consistency of the mempool to assemble blocks. However all blocks are still tested for validity after assembly. Other P2P Changes The list of banned peers is now stored on disk rather than in memory. Restarting freicoind will no longer clear out the list of banned peers; instead a new RPC call (`clearbanned`) can be used to manually clear the list. The new `setban` RPC call can also be used to manually ban or unban a peer. 12.1-10123 Change Log Detailed release notes follow. This overview includes changes that affect behavior, not code moves, refactors and string updates. For convenience in locating the code changes and accompanying discussion, both the pull request and git merge commit are mentioned. RPC and REST #6121 `466f0ea` Convert entire source tree from json_spirit to UniValue (Jonas Schnelli) #6234 `d38cd47` fix rpcmining/getblocktemplate univalue transition logic error (Jonas Schnelli) #6239 `643114f` Don't go through double in AmountFromValue and ValueFromAmount (Wladimir J. van der Laan) #6266 `ebab5d3` Fix univalue handling of \u0000 characters. (Daniel Kraft) #6276 `f3d4dbb` Fix getbalance * 0 (Tom Harding) #6257 `5ebe7db` Add `paytxfee` and `errors` JSON fields where appropriate (Stephen) #6271 `754aae5` New RPC command disconnectnode (Alex van der Peet) #6158 `0abfa8a` Add setban/listbanned RPC commands (Jonas Schnelli) #6307 `7ecdcd9` rpcban fixes (Jonas Schnelli) #6290 `5753988` rpc: make `gettxoutsettinfo` run lock-free (Wladimir J. van der Laan) #6262 `247b914` Return all available information via RPC call "validateaddress" (dexX7) #6339 `c3f0490` UniValue: don't escape solidus, keep espacing of reverse solidus (Jonas Schnelli) #6353 `6bcb0a2` Show softfork status in getblockchaininfo (Wladimir J. van der Laan) #6247 `726e286` Add getblockheader RPC call (Peter Todd) #6362 `d6db115` Fix null id in RPC response during startup (Forrest Voight) #5486 `943b322` [REST] JSON support for /rest/headers (Jonas Schnelli) #6379 `c52e8b3` rpc: Accept scientific notation for monetary amounts in JSON (Wladimir J. van der Laan) #6388 `fd5dfda` rpc: Implement random-cookie based authentication (Wladimir J. van der Laan) #6457 `3c923e8` Include pruned state in chaininfo.json (Simon Males) #6456 `bfd807f` rpc: Avoid unnecessary parsing roundtrip in number formatting, fix locale issue (Wladimir J. van der Laan) #6380 `240b30e` rpc: Accept strings in AmountFromValue (Wladimir J. van der Laan) #6346 `6bb2805` Add OP_RETURN support in createrawtransaction RPC call, add tests. (paveljanik) #6013 `6feeec1` [REST] Add memory pool API (paveljanik) #6576 `da9beb2` Stop parsing JSON after first finished construct. (Daniel Kraft) #5677 `9aa9099` libevent-based http server (Wladimir J. van der Laan) #6633 `bbc2b39` Report minimum ping time in getpeerinfo (Matt Corallo) #6648 `cd381d7` Simplify logic of REST request suffix parsing. (Daniel Kraft) #6695 `5e21388` libevent http fixes (Wladimir J. van der Laan) #5264 `48efbdb` show scriptSig signature hash types in transaction decodes. fixes #3166 (mruddy) #6719 `1a9f19a` Make HTTP server shutdown more graceful (Wladimir J. van der Laan) #6859 `0fbfc51` http: Restrict maximum size of http + headers (Wladimir J. van der Laan) #5936 `bf7c195` [RPC] Add optional locktime to createrawtransaction (Tom Harding) #6877 `26f5b34` rpc: Add maxmempool and effective min fee to getmempoolinfo (Wladimir J. van der Laan) #6970 `92701b3` Fix crash in validateaddress with -disablewallet (Wladimir J. van der Laan) #5574 `755b4ba` Expose GUI labels in RPC as comments (Luke-Jr) #6990 `dbd2c13` http: speed up shutdown (Wladimir J. van der Laan) #7013 `36baa9f` Remove LOCK(cs_main) from decodescript (Peter Todd) #6999 `972bf9c` add (max)uploadtarget infos to getnettotals RPC help (Jonas Schnelli) #7011 `31de241` Add mediantime to getblockchaininfo (Peter Todd) #7065 `f91e29f` http: add Boost 1.49 compatibility (Wladimir J. van der Laan) #7087 `be281d8` [Net]Add -enforcenodebloom option (Patrick Strateman) #7044 `438ee59` RPC: Added additional config option for multiple RPC users. (Gregory Sanders) #7072 `c143c49` [RPC] Add transaction size to JSON output (Nikita Zhavoronkov) #7022 `9afbd96` Change default block priority size to 0 (Alex Morcos) #7141 `c0c08c7` rpc: Don't translate warning messages (Wladimir J. van der Laan) #7312 `fd4bd50` Add RPC call abandontransaction (Alex Morcos) #7222 `e25b158` RPC: indicate which transactions are replaceable (Suhas Daftuar) #7472 `b2f2b85` rpc: Add WWW-Authenticate header to 401 response (Wladimir J. van der Laan) #7469 `9cb31e6` net.h fix spelling: misbeha{b,v}ing (Matt) #7739 `7ffc2bd` Add abandoned status to listtransactions (jonasschnelli) Configuration and command-line options #6164 `8d05ec7` Allow user to use -debug=1 to enable all debugging (lpescher) #5288 `4452205` Added `-whiteconnections=<n>` option (Josh Lehan) #6284 `10ac38e` Fix argument parsing oddity with -noX (Wladimir J. van der Laan) #6489 `c9c017a` Give a better error message if system clock is bad (Casey Rodarmor) #6462 `c384800` implement uacomment config parameter which can add comments to user agent as per BIP-0014 (Pavol Rusnak) #6647 `a3babc8` Sanitize uacomment (MarcoFalke) #6742 `3b2d37c` Changed logging to make -logtimestamps to work also for -printtoconsole (arnuschky) #6846 `2cd020d` alias -h for -help (Daniel Cousens) #6622 `7939164` Introduce -maxuploadtarget (Jonas Schnelli) #6881 `2b62551` Debug: Add option for microsecond precision in debug.log (Suhas Daftuar) #6776 `e06c14f` Support -checkmempool=N, which runs checks once every N transactions (Pieter Wuille) #6896 `d482c0a` Make -checkmempool=1 not fail through int32 overflow (Pieter Wuille) #6993 `b632145` Add -blocksonly option (Patrick Strateman) #7323 `a344880` 0.12: Backport -bytespersigop option (Luke-Jr) #7386 `da83ecd` Add option `-permitrbf` to set transaction replacement policy (Wladimir J. van der Laan) #7290 `b16b5bc` Add missing options help (MarcoFalke) #7440 `c76bfff` Rename permitrbf to mempoolreplacement and provide minimal string-list forward compatibility (Luke-Jr) Block and transaction handling #6203 `f00b623` Remove P2SH coinbase flag, no longer interesting (Luke-Jr) #6222 `9c93ee5` Explicitly set tx.nVersion for the genesis block and mining tests (Mark Friedenbach) #5985 `3a1d3e8` Fix removing of orphan transactions (Alex Morcos) #6221 `dd8fe82` Prune: Support noncontiguous block files (Adam Weiss) #6124 `41076aa` Mempool only CHECKLOCKTIMEVERIFY (BIP65) verification, unparameterized version (Peter Todd) #6329 `d0a10c1` acceptnonstdtxn option to skip (most) "non-standard transaction" checks, for testnet/regtest only (Luke-Jr) #6410 `7cdefb9` Implement accurate memory accounting for mempool (Pieter Wuille) #6444 `24ce77d` Exempt unspendable transaction outputs from dust checks (dexX7) #5913 `a0625b8` Add absurdly high fee message to validation state (Shaul Kfir) #6177 `2f746c6` Prevent block.nTime from decreasing (Mark Friedenbach) #6377 `e545371` Handle no chain tip available in InvalidChainFound() (Ross Nicoll) #6551 `39ddaeb` Handle leveldb::DestroyDB() errors on wipe failure (Adam Weiss) #6654 `b0ce450` Mempool package tracking (Suhas Daftuar) #6715 `82d2aef` Fix mempool packages (Suhas Daftuar) #6680 `4f44530` use CBlockIndex instead of uint256 for UpdatedBlockTip signal (Jonas Schnelli) #6650 `4fac576` Obfuscate chainstate (James O'Beirne) #6777 `9caaf6e` Unobfuscate chainstate data in CCoinsViewDB::GetStats (James O'Beirne) #6722 `3b20e23` Limit mempool by throwing away the cheapest txn and setting min relay fee to it (Matt Corallo) #6889 `38369dd` fix locking issue with new mempool limiting (Jonas Schnelli) #6464 `8f3b3cd` Always clean up manual transaction prioritization (Casey Rodarmor) #6865 `d0badb9` Fix chainstate serialized_size computation (Pieter Wuille) #6566 `ff057f4` BIP-113: Mempool-only median time-past as endpoint for lock-time calculations (Mark Friedenbach) #6934 `3038eb6` Restores mempool only BIP113 enforcement (Gregory Maxwell) #6965 `de7d459` Benchmark sanity checks and fork checks in ConnectBlock (Matt Corallo) #6918 `eb6172a` Make sigcache faster, more efficient, larger (Pieter Wuille) #6771 `38ed190` Policy: Lower default limits for tx chains (Alex Morcos) #6932 `73fa5e6` ModifyNewCoins saves database lookups (Alex Morcos) #5967 `05d5918` Alter assumptions in CCoinsViewCache::BatchWrite (Alex Morcos) #6871 `0e93586` nSequence-based Full-RBF opt-in (Peter Todd) #7008 `eb77416` Lower bound priority (Alex Morcos) #6915 `2ef5ffa` [Mempool] Improve removal of invalid transactions after reorgs (Suhas Daftuar) #6898 `4077ad2` Rewrite CreateNewBlock (Alex Morcos) #6872 `bdda4d5` Remove UTXO cache entries when the tx they were added for is removed/does not enter mempool (Matt Corallo) #7062 `12c469b` [Mempool] Fix mempool limiting and replace-by-fee for PrioritiseTransaction (Suhas Daftuar) #7276 `76de36f` Report non-mandatory script failures correctly (Pieter Wuille) #7217 `e08b7cb` Mark blocks with too many sigops as failed (Suhas Daftuar) #7387 `f4b2ce8` Get rid of inaccurate ScriptSigArgsExpected (Pieter Wuille) #7543 `834aaef` Backport BIP9, BIP68 and BIP112 with softfork (btcdrak) P2P protocol and network code #6172 `88a7ead` Ignore getheaders requests when not synced (Suhas Daftuar) #5875 `9d60602` Be stricter in processing unrequested blocks (Suhas Daftuar) #6256 `8ccc07c` Use best header chain timestamps to detect partitioning (Gavin Andresen) #6283 `a903ad7` make CAddrMan::size() return the correct type of size_t (Diapolo) #6272 `40400d5` Improve proxy initialization (continues #4871) (Wladimir J. van der Laan, Diapolo) #6310 `66e5465` banlist.dat: store banlist on disk (Jonas Schnelli) #6412 `1a2de32` Test whether created sockets are select()able (Pieter Wuille) #6498 `219b916` Keep track of recently rejected transactions with a rolling bloom filter (cont'd) (Peter Todd) #6556 `70ec975` Fix masking of irrelevant bits in address groups. (Alex Morcos) #6530 `ea19c2b` Improve addrman Select() performance when buckets are nearly empty (Pieter Wuille) #6583 `af9305a` add support for miniupnpc api version 14 (Pavel Vasin) #6374 `69dc5b5` Connection slot exhaustion DoS mitigation (Patrick Strateman) #6636 `536207f` net: correctly initialize nMinPingUsecTime (Wladimir J. van der Laan) #6579 `0c27795` Add NODE_BLOOM service bit and bump protocol version (Matt Corallo) #6148 `999c8be` Relay blocks when pruning (Suhas Daftuar) #6588 `cf9bb11` In (strCommand == "tx"), return if AlreadyHave() (Tom Harding) #6974 `2f71b07` Always allow getheaders from whitelisted peers (Wladimir J. van der Laan) #6639 `bd629d7` net: Automatically create hidden service, listen on Tor (Wladimir J. van der Laan) #6984 `9ffc687` don't enforce maxuploadtarget's disconnect for whitelisted peers (Jonas Schnelli) #7046 `c322652` Net: Improve blocks only mode. (Patrick Strateman) #7090 `d6454f6` Connect to Tor hidden services by default (when listening on Tor) (Peter Todd) #7106 `c894fbb` Fix and improve relay from whitelisted peers (Pieter Wuille) #7129 `5d5ef3a` Direct headers announcement (rebase of #6494) (Pieter Wuille) #7079 `1b5118b` Prevent peer flooding inv request queue (redux) (redux) (Gregory Maxwell) #7166 `6ba25d2` Disconnect on mempool requests from peers when over the upload limit. (Gregory Maxwell) #7133 `f31955d` Replace setInventoryKnown with a rolling bloom filter (rebase of #7100) (Pieter Wuille) #7174 `82aff88` Don't do mempool lookups for "mempool" command without a filter (Matt Corallo) #7179 `44fef99` net: Fix sent reject messages for blocks and transactions (Wladimir J. van der Laan) #7181 `8fc174a` net: Add and document network messages in protocol.h (Wladimir J. van der Laan) #7125 `10b88be` Replace global trickle node with random delays (Pieter Wuille) #7415 `cb83beb` net: Hardcoded seeds update January 2016 (Wladimir J. van der Laan) #7438 `e2d9a58` Do not absolutely protect local peers; decide group ties based on time (Gregory Maxwell) #7439 `86755bc` Add whitelistforcerelay to control forced relaying. [#7099 redux] (Gregory Maxwell) #7482 `e16f5b4` Ensure headers count is correct (Suhas Daftuar) #7804 `90f1d24` Track block download times per individual block (sipa) #7832 `4c3a00d` Reduce block timeout to 10 minutes (laanwj) Validation #5927 `8d9f0a6` Reduce checkpoints' effect on consensus. (Pieter Wuille) #6299 `24f2489` Bugfix: Don't check the genesis block header before accepting it (Jorge Timón) #6361 `d7ada03` Use real number of cores for default -par, ignore virtual cores (Wladimir J. van der Laan) #6519 `87f37e2` Make logging for validation optional (Wladimir J. van der Laan) #6351 `2a1090d` CHECKLOCKTIMEVERIFY (BIP65) IsSuperMajority() soft-fork (Peter Todd) #6931 `54e8bfe` Skip BIP 30 verification where not necessary (Alex Morcos) #6954 `e54ebbf` Switch to libsecp256k1-based ECDSA validation (Pieter Wuille) #6508 `61457c2` Switch to a constant-space Merkle root/branch algorithm. (Pieter Wuille) #6914 `327291a` Add pre-allocated vector type and use it for CScript (Pieter Wuille) #7500 `889e5b3` Correctly report high-S violations (Pieter Wuille) #7821 `4226aac` init: allow shutdown during 'Activating best chain...' (laanwj) #7835 `46898e7` Version 2 transactions remain non-standard until CSV activates (sdaftuar) Build system #6210 `0e4f2a0` build: disable optional use of gmp in internal secp256k1 build (Wladimir J. van der Laan) #6214 `87406aa` [OSX] revert renaming of Bitcoin-Qt.app and use CFBundleDisplayName (partial revert of #6116) (Jonas Schnelli) #6218 `9d67b10` build/gitian misc updates (Cory Fields) #6269 `d4565b6` gitian: Use the new bitcoin-detached-sigs git repo for OSX signatures (Cory Fields) #6418 `d4a910c` Add autogen.sh to source tarball. (randy-waterhouse) #6373 `1ae3196` depends: non-qt bumps for 0.12 (Cory Fields) #6434 `059b352` Preserve user-passed CXXFLAGS with --enable-debug (Gavin Andresen) #6501 `fee6554` Misc build fixes (Cory Fields) #6600 `ef4945f` Include bitcoin-tx binary on Debian/Ubuntu (Zak Wilcox) #6619 `4862708` depends: bump miniupnpc and ccache (Michael Ford) #6801 `ae69a75` [depends] Latest config.guess and config.sub (Michael Ford) #6938 `193f7b5` build: If both Qt4 and Qt5 are installed, use Qt5 (Wladimir J. van der Laan) #7092 `348b281` build: Set osx permissions in the dmg to make Gatekeeper happy (Cory Fields) #6980 `eccd671` [Depends] Bump Boost, miniupnpc, ccache & zeromq (Michael Ford) #7424 `aa26ee0` Add security/export checks to gitian and fix current failures (Cory Fields) #7487 `00d57b4` Workaround Travis-side CI issues (luke-jr) #7606 `a10da9a` No need to set -L and --location for curl (MarcoFalke) #7614 `ca8f160` Add curl to packages (now needed for depends) (luke-jr) #7776 `a784675` Remove unnecessary executables from gitian release (laanwj) Wallet #6183 `87550ee` Fix off-by-one error w/ nLockTime in the wallet (Peter Todd) #6057 `ac5476e` re-enable wallet in autoprune (Jonas Schnelli) #6356 `9e6c33b` Delay initial pruning until after wallet init (Adam Weiss) #6088 `91389e5` fundrawtransaction (Matt Corallo) #6415 `ddd8d80` Implement watchonly support in fundrawtransaction (Matt Corallo) #6567 `0f0f323` Fix crash when mining with empty keypool. (Daniel Kraft) #6688 `4939eab` Fix locking in GetTransaction. (Alex Morcos) #6645 `4dbd43e` Enable wallet key imports without rescan in pruned mode. (Gregory Maxwell) #6550 `5b77244` Do not store Merkle branches in the wallet. (Pieter Wuille) #5924 `12a7712` Clean up change computation in CreateTransaction. (Daniel Kraft) #6906 `48b5b84` Reject invalid pubkeys when reading ckey items from the wallet. (Gregory Maxwell) #7010 `e0a5ef8` Fix fundrawtransaction handling of includeWatching (Peter Todd) #6851 `616d61b` Optimisation: Store transaction list order in memory rather than compute it every need (Luke-Jr) #6134 `e92377f` Improve usage of fee estimation code (Alex Morcos) #7103 `a775182` [wallet, rpc tests] Fix settxfee, paytxfee (MarcoFalke) #7105 `30c2d8c` Keep track of explicit wallet conflicts instead of using mempool (Pieter Wuille) #7096 `9490bd7` [Wallet] Improve minimum absolute fee GUI options (Jonas Schnelli) #6216 `83f06ca` Take the training wheels off anti-fee-sniping (Peter Todd) #4906 `96e8d12` Issue#1643: Coinselection prunes extraneous inputs from ApproximateBestSubset (Murch) #7200 `06c6a58` Checks for null data transaction before issuing error to debug.log (Andy Craze) #7296 `a36d79b` Add sane fallback for fee estimation (Alex Morcos) #7293 `ff9b610` Add regression test for vValue sort order (MarcoFalke) #7306 `4707797` Make sure conflicted wallet tx's update balances (Alex Morcos) #7381 `621bbd8` [walletdb] Fix syntax error in key parser (MarcoFalke) #7491 `00ec73e` wallet: Ignore MarkConflict if block hash is not known (Wladimir J. van der Laan) #7502 `1329963` Update the wallet best block marker before pruning (Pieter Wuille) #7715 `19866c1` Fix calculation of balances and available coins. (morcos) GUI #6217 `c57e12a` disconnect peers from peers tab via context menu (Diapolo) #6209 `ab0ec67` extend rpc console peers tab (Diapolo) #6484 `1369d69` use CHashWriter also in SignVerifyMessageDialog (Pavel Vasin) #6487 `9848d42` Introduce PlatformStyle (Wladimir J. van der Laan) #6505 `100c9d3` cleanup icons (MarcoFalke) #4587 `0c465f5` allow users to set -onion via GUI (Diapolo) #6529 `c0f66ce` show client user agent in debug window (Diapolo) #6594 `878ea69` Disallow duplicate windows. (Casey Rodarmor) #5665 `6f55cdd` add verifySize() function to PaymentServer (Diapolo) #6317 `ca5e2a1` minor optimisations in peertablemodel (Diapolo) #6315 `e59d2a8` allow banning and unbanning over UI->peers table (Jonas Schnelli) #6653 `e04b2fa` Pop debug window in foreground when opened twice (MarcoFalke) #6864 `c702521` Use monospace font (MarcoFalke) #6887 `3694b74` Update coin control and smartfee labels (MarcoFalke) #7000 `814697c` add shortcurts for debug-/console-window (Jonas Schnelli) #6951 `03403d8` Use maxTxFee instead of 10000000 (MarcoFalke) #7051 `a190777` ui: Add "Copy raw transaction data" to transaction list context menu (Wladimir J. van der Laan) #6979 `776848a` simple mempool info in debug window (Jonas Schnelli) #7006 `26af1ac` add startup option to reset Qt settings (Jonas Schnelli) #6780 `2a94cd6` Call init's parameter interaction before we create the UI options model (Jonas Schnelli) #7112 `96b8025` reduce cs_main locks during tip update, more fluently update UI (Jonas Schnelli) #7206 `f43c2f9` Add "NODE_BLOOM" to guiutil so that peers don't get UNKNOWN[4] (Matt Corallo) #7282 `5cadf3e` fix coincontrol update issue when deleting a send coins entry (Jonas Schnelli) #7319 `1320300` Intro: Display required space (MarcoFalke) #7318 `9265e89` quickfix for RPC timer interface problem (Jonas Schnelli) #7327 `b16b5bc` [Wallet] Transaction View: LastMonth calculation fixed (crowning-) #7364 `7726c48` [qt] Windows: Make rpcconsole monospace font larger (MarcoFalke) #7384 `294f432` [qt] Peertable: Increase SUBVERSION_COLUMN_WIDTH (MarcoFalke) Tests and QA #6305 `9005c91` build: comparison tool swap (Cory Fields) #6318 `e307e13` build: comparison tool NPE fix (Cory Fields) #6337 `0564c5b` Testing infrastructure: mocktime fixes (Gavin Andresen) #6350 `60abba1` add unit tests for the decodescript rpc (mruddy) #5881 `3203a08` Fix and improve txn_doublespend.py test (Tom Harding) #6390 `6a73d66` tests: Fix bitcoin-tx signing test case (Wladimir J. van der Laan) #6368 `7fc25c2` CLTV: Add more tests to improve coverage (Esteban Ordano) #6414 `5121c68` Fix intermittent test failure, reduce test time (Tom Harding) #6417 `44fa82d` [QA] fix possible reorg issue in (fund)rawtransaction(s).py RPC test (Jonas Schnelli) #6398 `3d9362d` rpc: Remove chain-specific RequireRPCPassword (Wladimir J. van der Laan) #6428 `bb59e78` tests: Remove old sh-based test framework (Wladimir J. van der Laan) #5515 `d946e9a` RFC: Assert on probable deadlocks if the second lock isnt try_lock (Matt Corallo) #6287 `d2464df` Clang lock debug (Cory Fields) #6465 `410fd74` Don't share objects between TestInstances (Casey Rodarmor) #6534 `6c1c7fd` Fix test locking issues and un-revert the probable-deadlines assertions commit (Cory Fields) #6509 `bb4faee` Fix race condition on test node shutdown (Casey Rodarmor) #6523 `561f8af` Add p2p-fullblocktest.py (Casey Rodarmor) #6590 `981fd92` Fix stale socket rebinding and re-enable python tests for Windows (Cory Fields) #6730 `cb4d6d0` build: Remove dependency of bitcoin-cli on secp256k1 (Wladimir J. van der Laan) #6616 `5ab5dca` Regression Tests: Migrated rpc-tests.sh to all Python rpc-tests.py (Peter Tschipper) #6720 `d479311` Creates unittests for addrman, makes addrman more testable. (Ethan Heilman) #6853 `c834f56` Added fPowNoRetargeting field to Consensus::Params (Eric Lombrozo) #6827 `87e5539` [rpc-tests] Check return code (MarcoFalke) #6848 `f2c869a` Add DERSIG transaction test cases (Ross Nicoll) #6813 `5242bb3` Support gathering code coverage data for RPC tests with lcov (dexX7) #6888 `c8322ff` Clear strMiscWarning before running PartitionAlert (Eric Lombrozo) #6894 `2675276` [Tests] Fix BIP65 p2p test (Suhas Daftuar) #6863 `725539e` [Test Suite] Fix test for null tx input (Daniel Kraft) #6926 `a6d0d62` tests: Initialize networking on windows (Wladimir J. van der Laan) #6822 `9fa54a1` [tests] Be more strict checking dust (MarcoFalke) #6804 `5fcc14e` [tests] Add basic coverage reporting for RPC tests (James O'Beirne) #7045 `72dccfc` Bugfix: Use unique autostart filenames on Linux for testnet/regtest (Luke-Jr) #7095 `d8368a0` Replace scriptnum_test's normative ScriptNum implementation (Wladimir J. van der Laan) #7063 `6abf6eb` [Tests] Add prioritisetransaction RPC test (Suhas Daftuar) #7137 `16f4a6e` Tests: Explicitly set chain limits in replace-by-fee test (Suhas Daftuar) #7216 `9572e49` Removed offline testnet DNSSeed 'alexykot.me'. (tnull) #7209 `f3ad812` test: don't override BITCOIND and BITCOINCLI if they're set (Wladimir J. van der Laan) #7226 `301f16a` Tests: Add more tests to p2p-fullblocktest (Suhas Daftuar) #7153 `9ef7c54` [Tests] Add mempool_limit.py test (Jonas Schnelli) #7170 `453c567` tests: Disable Tor interaction (Wladimir J. van der Laan) #7229 `1ed938b` [qa] wallet: Check if maintenance changes the balance (MarcoFalke) #7308 `d513405` [Tests] Eliminate intermittent failures in sendheaders.py (Suhas Daftuar) #7468 `947c4ff` [rpc-tests] Change solve() to use rehash (Brad Andrews) Miscellaneous #6213 `e54ff2f` [init] add -blockversion help and extend -upnp help (Diapolo) #5975 `1fea667` Consensus: Decouple ContextualCheckBlockHeader from checkpoints (Jorge Timón) #6061 `eba2f06` Separate Consensus::CheckTxInputs and GetSpendHeight in CheckInputs (Jorge Timón) #5994 `786ed11` detach wallet from miner (Jonas Schnelli) #6387 `11576a5` [bitcoin-cli] improve error output (Jonas Schnelli) #6401 `6db53b4` Add BITCOIND_SIGTERM_TIMEOUT to OpenRC init scripts (Florian Schmaus) #6430 `b01981e` doc: add documentation for shared library libbitcoinconsensus (Braydon Fuller) #6372 `dcc495e` Update Linearize tool to support Windows paths; fix variable scope; update README and example configuration (Paul Georgiou) #6453 `8fe5cce` Separate core memory usage computation in core_memusage.h (Pieter Wuille) #6149 `633fe10` Buffer log messages and explicitly open logs (Adam Weiss) #6488 `7cbed7f` Avoid leaking file descriptors in RegisterLoad (Casey Rodarmor) #6497 `a2bf40d` Make sure LogPrintf strings are line-terminated (Wladimir J. van der Laan) #6504 `b6fee6b` Rationalize currency unit to "BTC" (Ross Nicoll) #6507 `9bb4dd8` Removed contrib/bitrpc (Casey Rodarmor) #6527 `41d650f` Use unique name for AlertNotify tempfile (Casey Rodarmor) #6561 `e08a7d9` limitedmap fixes and tests (Casey Rodarmor) #6565 `a6f2aff` Make sure we re-acquire lock if a task throws (Casey Rodarmor) #6599 `f4d88c4` Make sure LogPrint strings are line-terminated (Ross Nicoll) #6630 `195942d` Replace boost::reverse_lock with our own (Casey Rodarmor) #6103 `13b8282` Add ZeroMQ notifications (João Barbosa) #6692 `d5d1d2e` devtools: don't push if signing fails in github-merge (Wladimir J. van der Laan) #6728 `2b0567b` timedata: Prevent warning overkill (Wladimir J. van der Laan) #6713 `f6ce59c` SanitizeString: Allow hypen char (MarcoFalke) #5987 `4899a04` Bugfix: Fix testnet-in-a-box use case (Luke-Jr) #6733 `b7d78fd` Simple benchmarking framework (Gavin Andresen) #6854 `a092970` devtools: Add security-check.py (Wladimir J. van der Laan) #6790 `fa1d252` devtools: add clang-format.py (MarcoFalke) #7114 `f3d0fdd` util: Don't set strMiscWarning on every exception (Wladimir J. van der Laan) #7078 `93e0514` uint256::GetCheapHash bigendian compatibility (arowser) #7094 `34e02e0` Assert now > 0 in GetTime GetTimeMillis GetTimeMicros (Patrick Strateman) #7617 `f04f4fd` Fix markdown syntax and line terminate LogPrint (MarcoFalke) #7747 `4d035bc` added depends cross compile info (accraze) #7741 `a0cea89` Mark p2p alert system as deprecated (btcdrak) #7780 `c5f94f6` Disable bad-chain alert (btcdrak) Tradecraft pull requests #25 Add SCRIPT_VERIFY_REQUIRE_VALID_SIGS flag and make standard The SCRIPT_VERIFY_REQUIRE_VALID_SIGS enforces that every signature check passes when the signature field is non-empty (softfork safe, replaces BIP62 rule 7). It is still possible for the non-VERIFY forms of CHECKSIG or CHECKMULTISIG to be executed and return false, but you MUST do so by passing in an empty (OP_0) signature. The way this is implemented is different for the two opcodes: CHECKSIG and CHECKSIGVERIFY will abort script validation with error code SCRIPT_ERR_FAILED_SIGNATURE_CHECK if the signature validation code returns false for any reason other than the passed-in signature being the empty. CHECKMULTISIG and CHECKMULTISIGVERIFY present a significant challenge to enforcing this requirement in that the original data format did not indicate which public keys were matched with which signatures, other than the ordering. For a k-of-n multisig, there are n-choose-(n-k) possibilities. For example, a 2-of-3 multisig would have three public keys matched with two signatures, resulting in three possible assignments of pubkeys to signatures. In the original implementation this is done by attempting to validate a signature, starting with the first public key and the first signature, and then moving to the next pubkey if validation fails. It is not known in advance to the validator which attempts will fail. Thankfully, however, a bug in the original implementation causes an extra, unused item to be removed from stack after validation. Since this value is given no previous consensus meaning, we use it as a bitfield to indicate which pubkeys to skip. Enforcing this requirement is a necessary precursor step to performing batch validation, since in a batch validation regime individual pubkey-signature combinations would not be checked for validity. Like bitcoin's SCRIPT_VERIFY_NULLDUMMY, this also serves as a malleability fix since the bitmask value is provided by the witness. #36 Delay block file size increase until after the protocol cleanup rules activate This is a follow-up to #26 included in Freicoin v10.4. By comparing against `GetAdjustedTime` we can check if we are running in the protocol cleanup regime, and only then use the higher limits for block file size. In the mean time we'll still use smaller block files which is beneficial for pruning. It's slightly layer violating to access the chain consensus parameters in some cases, e.g. from the network and protocol message handling code. But it doesn't break the build and is better than the alternative. #37 Remove ability to "opt-out" from replace-by-fee semantics. Bitcoin v0.12 introduces "opt-in" replace-by-fee semantics. This was an unfortunate political compromise as a result of situational context we are fortunate not to have to deal with. There is no such thing as optionality to RBF because there is no way to prevent transaction replacement in miner mempools. It is trivial to execute a double-spend even when the transaction being replaces is not BIP125 compatible, and there are tools available to do this. Supporting this feature and advertising it is confusing and a potential source of security failures. #40 Re-enable RPC regression tests from bitcoin with "bitcoin mode" (no demurrage) regtest chain For the past couple of releases the majority of RPC regression tests have bee disabled due to their implementation making certain assumptions about the behavior of the chain, such as blocks having 50 BTC subsidy, and not taking into account value decay due to demurrage. For example: A test that mines 25 blocks, then 100 blocks for maturity, and checks that the available balance is 1250 coins is intending to test the wallet coinbase maturity code, not the block reward schedule. (These tests needed updating because the freicoin subsidy schedule is different from bitcoin's.) A test that records the wallets balance, sends all available coins to a external address, checks the new balance is zero, then reorgs to a longer chain containing a double-spends back to itself and checks the wallet balance has returned to its original value is not supposed to be testing for demurrage. (These tests needed updating because wallet balances decay with each mined block.) Previously we updated these tests individually, but this proved difficult to maintain. In recent rebasing efforts we delayed introduction of demurrage and changing subsidy until the end so the tests could at least be run against earlier patches. This PR introduces a more long-term solution. This PR changes the subsidy on regtest to resemble bitcoin's (50 coins per block), and introduces a new consensus-impacting option `-notimeadjust` (only available with `-regtest`) which disables demurrage / time-value adjustment. Running the JSON-RPC python test framework with the `--bitcoin-mode` command line option turns on this no-demurrage mode. #41 Fix final jsonrpc tests Re-enables the final set of tests disabled by the demurrage patch set. The problem here was not just demurrage but also the fact that the input truncation and ALU demurrage soft-forks hadn't activated on the regtest chain. Credits Thanks to everyone who directly contributed to this release: accraze Adam Weiss Alex Morcos Alex van der Peet AlSzacrel Altoidnerd Andriy Voskoboinyk antonio-fr Arne Brutschy Ashley Holman Bob McElrath Braydon Fuller BtcDrak Casey Rodarmor centaur1 Chris Kleeschulte Christian Decker Cory Fields crowning- daniel Daniel Cousens Daniel Kraft David Hill dexX7 Diego Viola Elias Rohrer Eric Lombrozo Erik Mossberg Esteban Ordano EthanHeilman Florian Schmaus Forrest Voight Gavin Andresen Gregory Maxwell Gregory Sanders / instagibbs Ian T Irving Ruan Jacob Welsh James O'Beirne Jeff Garzik Johnathan Corgan Jonas Schnelli Jonathan Cross João Barbosa Jorge Timón Josh Lehan J Ross Nicoll Karl-Johan Alm kazcw Kevin Cooper lpescher Luke Dashjr MarcoFalke Mark Friedenbach Matt Matt Bogosian Matt Corallo Matt Quinn Micha Michael Michael Ford / fanquake Midnight Magic Mitchell Cash mrbandrews mruddy Nick NicolasDorier Patrick Strateman Paul Georgiou Paul Rabahy Pavel Janík / paveljanik Pavel Vasin Pavol Rusnak Peter Josling Peter Todd Philip Kaufmann Pieter Wuille ptschip randy-waterhouse rion Ross Nicoll Ryan Havar Shaul Kfir Simon Males Stephen Suhas Daftuar tailsjoin Thomas Kerin Tom Harding tulip unsystemizer Veres Lajos Wladimir J. van der Laan xor-freenet Zak Wilcox zathras-crypto As well as everyone that helped translating on Transifex.
  26. Skaro
    Latest version 12.1 released April 1 2019 http://freico.in/download/
  27. Skaro
    Oops I didn’t see this thread. it’s raininng wallets.
  28. Skaro
    Latest version 12.1 released April 1 2019 http://freico.in/download/ They keep coming faster than we can download them now! thank you for your hard work , Mark.
  1. Load more activity
×
×
  • Create New...