unconfirmed block reward from 2009 - 50 BTC - REWARD 0.1 BTC FOR HELPING

[btcnews2024]

I need some advice for an old wallet.dat i have
The wallet.dat contain a 2009 btc mined reward with this status:

Code:

Status: 0/unconfirmed, not in memory pool
Date: 25/6/09 09:44
Source: Generated
Credit: (not accepted)
Net amount: 0.00000000 BTC
Transaction ID: removed for confidentiality
Transaction total size: 107 bytes
Transaction virtual size: 107 bytes
Output index: 0

Generated coins must mature 101 blocks before they can be spent. When you generated this block, it was broadcast to the network to be added to the block chain. If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

Is it possible to re-broadcast or push this tx reward on the mempool?

Im running Bitcoin core full blockchain node on Ubuntu

Whoever helps me find out how to get confirmed this tx ill reward him with 0.1 BTC

[1714264599]

1714264599

[1714264599]

1714264599

[Btcspot]

 Hi, you probably havent resync to blockchain so bitcoin core didnt update i would try to go to the console in core and enter this: rescanblockchain then see if it shows up.

 If that wont work try here: https://www.blockchain.com/explorer/assets/btc/broadcast-transaction
 Let me know if you need more help.

[BitMaxz]

No, you can't just rebroadcast this transaction it's already rejected if you understand what it says on the transaction details under this

If it fails to get into the chain, its state will change to "not accepted" and it won't be spendable. This may occasionally happen if another node generates a block within a few seconds of yours.

This means this transaction didn't get into the chain due to another node generating a block within a few seconds than yours. Since this transaction was generated a long time ago there are lots of blocks already on the chain which is why this transaction is unspendable.

[logfiles]

A block from the past?

I don't think so. The last line in the text you shared gives a clue.

Hiding the transactions ID doesn't matter because the block is not part of the blockchain. Check the blocks that were mined on that day - https://blockchair.com/bitcoin/blocks?s=id(asc)&q=time(2009-06-25)# I don't think the block you are talking about is part of them.

[nc50lc]

Is it possible to re-broadcast or push this tx reward on the mempool?

No, that the coinbase transaction (not the exhange) of the block that you've mined.
Since it has status of "0/unconfirmed, not in memory pool", your node doesn't have that block where it's included.
Broadcasting the block (if you still has it) is no good either since there are already 14 years worth of blocks built on top of it.

If you decided to rescan your blockchain (in case it's missed during IBD),
You can do it fast by rescanning only the old block heights where it might be included.
Use: rescanblockchain 0 33000 to scan only blocks from 2009,
replace "33000" if you want to scan more beyond your projected date, but it'll be slower.

[BlackHatCoiner]

Date: 25/6/09 09:44

You can verify that no block was mined in June, 25th 2009 09:44, by looking at a block explorer. The closest to that date are blocks 18021 (09:28) and 18022 (09:53), both of which have block rewards spent.

It also seems weird that your transaction's total size is 107 bytes, given that a P2PK coinbase reward was 135 bytes.

[btcnews2024]

this is the result i got from an online broadcast tx:

Code:

sendrawtransaction RPC error: {"code":-26,"message":"coinbase"}

[nc50lc]

this is the result i got from an online broadcast tx:

Code:

sendrawtransaction RPC error: {"code":-26,"message":"coinbase"}

Like we said, you can't just re-broadcast a coinbase transaction.

What you need to do to check for its integrity is to rescan the blockchain, following my command to limit the scan range should get it done within minutes.
The result will tell if it's really invalid or valid.
You can't just do that though if your node's blockchain is pruned, you'll need to re-download those old blocks.

[btcnews2024]

this is the result i got from an online broadcast tx:

Code:

sendrawtransaction RPC error: {"code":-26,"message":"coinbase"}

Like we said, you can't just re-broadcast a coinbase transaction.

What you need to do to check for its integrity is to rescan the blockchain, following my command to limit the scan range should get it done within minutes.
The result will tell if it's really invalid or valid.
You can't just do that though if your node's blockchain is pruned, you'll need to re-download those old blocks.

Thanks, i have full node blockchain data. I´ll try that and report you back the results. If it works, rest asure you will receive 0.1 BTC

[LoyceV]

If it works, rest asure you will receive 0.1 BTC

If it works, you've created a Bitcoin Fork in 2009, which was orphaned by the main chain. You're chasing something that's not going to work.

[btcnews2024]

If it works, rest asure you will receive 0.1 BTC

If it works, you've created a Bitcoin Fork in 2009, which was orphaned by the main chain. You're chasing something that's not going to work.

end of story, its categorized as "orphaned"

But im thinking.... why not creating a bitcoin fork to include all orphaned coinbase tx since genesis block up to this date? After all, the miners who received the "orphaned" made a computational work... so instead of a "race" to who finish first the "job" change it to "work as a service" and share proportionally with the miners based on their computational work done, which can be calculated.... in the counter side it will be a massive bitcoin price drop up to 80% - 75% ....  so the thing is will miners consensus approve this kind of fork or they wont just to keep their "monopoly" .... and here comes the real question... bitcoin wont descentralized after all mmm? what you guys think

[BlackHatCoiner]

After all, the miners who received the "orphaned" made a computational work...

They did offer their computational work, but this is not how it works. To receive reward, you need to work on the longest chain (difficulty-wise). The whole premise of Bitcoin is that you are incentivized to mine on the longest chain, and are disincentivized to work on the rest. If we were to follow this line of reasoning, then every time the chain reorged, we'd split into two separate currencies.

[LoyceMobile]

If it works, rest asure you will receive 0.1 BTC

If it works, you've created a Bitcoin Fork in 2009, which was orphaned by the main chain. You're chasing something that's not going to work.

end of story, its categorized as "orphaned"

But im thinking.... why not creating a bitcoin fork to include all orphaned coinbase tx since genesis block up to this date? After all, the miners who received the "orphaned" made a computational work... so instead of a "race" to who finish first the "job" change it to "work as a service" and share proportionally with the miners based on their computational work done, which can be calculated.... in the counter side it will be a massive bitcoin price drop up to 80% - 75% ....  so the thing is will miners consensus approve this kind of fork or they wont just to keep their "monopoly" .... and here comes the real question... bitcoin wont descentralized after all mmm? what you guys think

With 2009-difficulty and today's hashing power, anyone can create thousands of orphaned 2009 blocks. It's pointless, orphaned blocks lost the race.

[Yamane_Keto]

But im thinking.... why not creating a bitcoin fork to include all orphaned coinbase tx since genesis block up to this date?

The code is open source. You can do that and recover the 50, but I doubt that it will have a value, or at least equal to 0.1 Bitcoin.
If you broadcast that transaction at that time and received Bitcoin at your address, then you could access your money, but the work was not done, and in Bitcoin there was either a return obtained or someone else obtained it.

[nc50lc]

end of story, its categorized as "orphaned"

Just as expected.

But im thinking.... why not creating a bitcoin fork to include all orphaned coinbase tx since genesis block up to this date? After all, the miners who received the "orphaned" made a computational work...

Not all nodes has the same set of orphaned blocks, some nodes don't even know that a miner's orphaned block exists if it received the block from the longer chain first.
We can check that your orphaned block isn't received by our node by using getchaintips RPC.
So you're thinking of letting nodes from that fork accept block rewards from blocks that the whole network isn't aware of.

[btcnews2024]

im developing a BTC fork which will allow some orphaned coinbase tx to be included. For this particular reason, orphaned coinbase that will take into account there was non mempool transmision emited for the past 60 days and above.

This will allow orphaned coinbase to be allowed to re-sync and claim unclaimed reward which was not able to do it because of the 21 days timewindow to be included on the mempool...
more info ill be posting here.

Fork name: Julius Caesar (Roman Empire)

[Cricktor]

...

You're wasting your time with such a fork. There's a reason why abandoned branches (usually it's only one block "leaves", see https://fork.observer) of the blockchain are not considered a valid part of the blockchain (the chain with the most cumulated hashwork). This is how trustless PoW works and is supposed to be. Otherwise you open a lot of cans of worms for exploits. No one wants the latter.