| /dports/net-p2p/bitcoin/bitcoin-22.0/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/bitcoin-daemon/bitcoin-22.0/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/bitcoin-utils/bitcoin-22.0/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/litecoin/litecoin-0.18.1/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/litecoin-daemon/litecoin-0.18.1/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/litecoin-utils/litecoin-0.18.1/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/namecoin-utils/namecoin-core-nc0.21.0.1/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/namecoin/namecoin-core-nc0.21.0.1/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/namecoin-daemon/namecoin-core-nc0.21.0.1/doc/release-notes/ |
| H A D | release-notes-0.14.1.md | 48 In previous versions, getblocktemplate required segwit support from downstream
50 now supports non-segwit clients even after activation, by removing all segwit
51 transactions from the returned block template. This allows non-segwit miners to
52 continue functioning correctly even after segwit has activated.
55 non-segwit clients to not signal for the segwit version-bit. Since this is no
56 longer an issue, getblocktemplate now always recommends signalling segwit for
58 required criteria for safe activation, not actually producing segwit-enabled
97 - #9912 `fc3d7db` Optimize GetWitnessHash() for non-segwit transactions (sdaftuar)
111 - #9955/#10006 `569596c` Don't require segwit in getblocktemplate for segwit signalling or mining (…
|
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/zetacoin/zetacoin-0.13.2.1/doc/release-notes/ |
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/zetacoin-utils/zetacoin-0.13.2.1/doc/release-notes/ |
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/zetacoin-daemon/zetacoin-0.13.2.1/doc/release-notes/ |
| H A D | release-notes-0.13.1.md | 6 segwit softfork, various bugfixes and performance improvements, as well as
49 Segregated witness (segwit) is a soft fork that, if activated, will
148 Activation for the segwit soft fork is being managed using BIP9
150 tracking which blocks signal support for segwit at the beginning of the
153 signal support for segwit, the soft fork will be locked in. After
154 another 2,016 blocks, segwit will activate.
156 For more information about segwit, please see the [segwit FAQ][], the
162 [Segwit FAQ]: https://bitcoincore.org/en/2016/01/26/segwit-benefits/
189 consensus rule both for non-segwit transactions and segwit transactions,
195 as segwit.
[all …]
|
| /dports/net-p2p/litecoin-daemon/litecoin-0.18.1/src/ |
| H A D | outputtype.cpp | 68 CTxDestination segwit = WitnessV0KeyHash(keyid); in GetAllDestinationsForKey() local
69 CTxDestination p2sh = CScriptID(GetScriptForDestination(segwit)); in GetAllDestinationsForKey()
70 return std::vector<CTxDestination>{std::move(keyid), std::move(p2sh), std::move(segwit)}; in GetAllDestinationsForKey()
|
| /dports/net-p2p/litecoin-utils/litecoin-0.18.1/src/ |
| H A D | outputtype.cpp | 68 CTxDestination segwit = WitnessV0KeyHash(keyid); in GetAllDestinationsForKey() local
69 CTxDestination p2sh = CScriptID(GetScriptForDestination(segwit)); in GetAllDestinationsForKey()
70 return std::vector<CTxDestination>{std::move(keyid), std::move(p2sh), std::move(segwit)}; in GetAllDestinationsForKey()
|
| /dports/net-p2p/litecoin/litecoin-0.18.1/src/ |
| H A D | outputtype.cpp | 68 CTxDestination segwit = WitnessV0KeyHash(keyid); in GetAllDestinationsForKey() local
69 CTxDestination p2sh = CScriptID(GetScriptForDestination(segwit)); in GetAllDestinationsForKey()
70 return std::vector<CTxDestination>{std::move(keyid), std::move(p2sh), std::move(segwit)}; in GetAllDestinationsForKey()
|
| /dports/net-p2p/qtum/qtum-mainnet-fastlane-v0.20.3/src/ |
| H A D | outputtype.cpp | 73 CTxDestination segwit = WitnessV0KeyHash(keyid); in GetAllDestinationsForKey() local
74 CTxDestination p2sh = ScriptHash(GetScriptForDestination(segwit)); in GetAllDestinationsForKey()
75 return Vector(std::move(p2pkh), std::move(p2sh), std::move(segwit)); in GetAllDestinationsForKey()
|