joe2015 at openmailbox.org [ARCHIVE] on Nostr: 📅 Original date posted:2016-01-12 📝 Original message:On 2016-01-05 09:26, ...
📅 Original date posted:2016-01-12
📝 Original message:On 2016-01-05 09:26, joe2015--- via bitcoin-dev wrote:
> On 2016-01-05 02:04, Nick ODell wrote:
>> How are you collecting fees from the transactions in the block?
>
> Probably the simplest way to do this is to map the new-rules coinbase
> tx (which collects the block reward and fees) into an old-rules legacy
> coinbase tx (which collects the block reward only). Care must be
> taken to ensure the mapping is not reversible. I will update my
> implementation in due course.
The redesigned implementation is here:
https://github.com/ZoomT/bitcoin/tree/2015_2mb_blocksize
https://github.com/jgarzik/bitcoin/compare/2015_2mb_blocksize...ZoomT:2015_2mb_blocksize
The new version maps the Merkle root onto a 'legacy' coinbase
transaction, solving the problem with fees.
--joe.
📝 Original message:On 2016-01-05 09:26, joe2015--- via bitcoin-dev wrote:
> On 2016-01-05 02:04, Nick ODell wrote:
>> How are you collecting fees from the transactions in the block?
>
> Probably the simplest way to do this is to map the new-rules coinbase
> tx (which collects the block reward and fees) into an old-rules legacy
> coinbase tx (which collects the block reward only). Care must be
> taken to ensure the mapping is not reversible. I will update my
> implementation in due course.
The redesigned implementation is here:
https://github.com/ZoomT/bitcoin/tree/2015_2mb_blocksize
https://github.com/jgarzik/bitcoin/compare/2015_2mb_blocksize...ZoomT:2015_2mb_blocksize
The new version maps the Merkle root onto a 'legacy' coinbase
transaction, solving the problem with fees.
--joe.