The coin code probably doesn't enforce the 1000 being sent to the dib address (I didn't look at the code), it probably only creates those blocks for mining. A miner probably just modified the code to create blocks with 20 instead of 1000. The coin code should check this reward and reject blocks that do not have the proper reward to the dib address.
The coinbase field may contain arbitrary data, see https://bitcoin.org/en/glossary/coinbase
Topic: 0.2 BTC bounty: Long time standing coinbase transaction issue needs explanation (Read 352 times)
June 27, 2015, 01:35:59 AM
June 27, 2015, 01:01:58 AM
Will pay 0.2 BTC bounty for the best explanation of why this is occurring. The thread community should decide on who has the correct, or best, answer. The bounty will be paid to the first correct responding party but it can be split up too, and the community can decide this.
Here is the issue:
Altcoin GreenCoin was released in June 2014. The coinbase transaction was designed to send two 1000 coin payments per block: one to the miner and one to a pre-assigned address (GZdib... is the pre-defined addy). There are currently some blocks that pay 1980 to the miner and only 20 to the pre-defined addy.
When GreenCoin was first released it was an independently mined scrypt. At block 150,000 it was forked to incorporate merged mining (Sept. 26th 2014). The first instance of the error was noted on or around 12/4/14. Block 246,503 may have one of the first instances of the error. The benefitting miner's address is always: GQiGwRM5UTdGDeBoCqaGwHbQLenxqMq3U9
I'm wondering about this coinbase transaction issue again. here's a simple coinbase transaction description.
Here is link to a proper transaction:
http://gre-be.cloudapp.net/index.php?transaction=3bb2fe0b2f7f3f419c9d49888326b2bbbf987e89be334cfaf37a21cf7c9bf96e
note the Coinbase: 041199461b010152
and Sequence: 4294967295
and here is an improper transaction:
http://gre-be.cloudapp.net/index.php?transaction=bf6ebc011abcdba2a22470387bd270896cd14e564c9407f8638933bc4da2eef4
Coinbase: 03661e08062f503253482f044d1a8e550858000000000000002cfabe6d6d5f5f5f5f5f5f5f5f5f5 f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f
Sequence: 0
Note all the weird f5's (?)
Additionally I have an interest in fork-fixing or re-releasing this coin with the fix and additional upgrades / new features so any devs out there. I know you dev guys get solicitations all the time but GreenCoin has a substantial environmental imperative, some funding and motivation to begin expanding this summer. You can read about the central premise here:
GreenCoin main thread: https://bitcointalksearch.org/topic/anngre-greencoin-a-blockchain-based-social-carbon-ecosystem-957976
Website Help page: http://www.grcoin.com/pages/help
tl;dr whitepaper: http://www.grcoin.com/GreenCoin-Abstract_v1.0.pdf
Here is the issue:
Altcoin GreenCoin was released in June 2014. The coinbase transaction was designed to send two 1000 coin payments per block: one to the miner and one to a pre-assigned address (GZdib... is the pre-defined addy). There are currently some blocks that pay 1980 to the miner and only 20 to the pre-defined addy.
When GreenCoin was first released it was an independently mined scrypt. At block 150,000 it was forked to incorporate merged mining (Sept. 26th 2014). The first instance of the error was noted on or around 12/4/14. Block 246,503 may have one of the first instances of the error. The benefitting miner's address is always: GQiGwRM5UTdGDeBoCqaGwHbQLenxqMq3U9
I'm wondering about this coinbase transaction issue again. here's a simple coinbase transaction description.
Here is link to a proper transaction:
http://gre-be.cloudapp.net/index.php?transaction=3bb2fe0b2f7f3f419c9d49888326b2bbbf987e89be334cfaf37a21cf7c9bf96e
note the Coinbase: 041199461b010152
and Sequence: 4294967295
and here is an improper transaction:
http://gre-be.cloudapp.net/index.php?transaction=bf6ebc011abcdba2a22470387bd270896cd14e564c9407f8638933bc4da2eef4
Coinbase: 03661e08062f503253482f044d1a8e550858000000000000002cfabe6d6d5f5f5f5f5f5f5f5f5f5 f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f5f
Sequence: 0
Note all the weird f5's (?)
Additionally I have an interest in fork-fixing or re-releasing this coin with the fix and additional upgrades / new features so any devs out there. I know you dev guys get solicitations all the time but GreenCoin has a substantial environmental imperative, some funding and motivation to begin expanding this summer. You can read about the central premise here:
GreenCoin main thread: https://bitcointalksearch.org/topic/anngre-greencoin-a-blockchain-based-social-carbon-ecosystem-957976
Website Help page: http://www.grcoin.com/pages/help
tl;dr whitepaper: http://www.grcoin.com/GreenCoin-Abstract_v1.0.pdf
Jump to: