You can take money out of a pending transaction without having to sign an entire new transaction (using the alternate SIGHASH modes), but you need to share some new data with your heir if you ever want to add more funds to the transaction.


It's in the code. There's no GUI for it yet.


You need to make sure you invalidate the transaction before it becomes locked.

nLockTime is enforced by the network, so there's no way to bypass it.

No. It's already in the protocol.

The current client wouldn't even recognize the script as being sent to you. It doesn't know how to solve it, so it just ignores it. You can't possibly spend such scripts unless you modify Bitcoin.

I installed the mod. You can ignore boards on your profile.

It's possible. There's no tool to do it, though.

No, it's just local ones. There's no way to get all network-wide orphan blocks. Some might only spread to a few dozen peers.

They're stored in your block database forever. You'll see them along with the other blocks if you use -printblock or -printblocktree.

I can't believe I've been logged in for almost 1% of my life...

Your guesses about Kiba are pretty accurate from what I've read.

Looks like kiba does, at 80+ days:
https://forum.bitcoin.org/index.php?action=stats

I'm second.

Why not just use Bitcoin Block Explorer's RSS feeds? Every address has a unique RSS feed.

A signature verifies some data. That signature verifies that the text between "BEGIN PGP SIGNED MESSAGE" and "BEGIN PGP SIGNATURE" was actually written by me.

To verify my signature, you need my public key. If you want to send me an encrypted message, you also encrypt it to my public key.

That public key is long because it has lots of signatures. It's smaller if you remove the signatures:
http://theymos.com/theymos.txt
(This is the exact same public key.)

No. In my posts in this topic, I have always assumed that the miner will never include the transaction in his own blocks. I am only concerned here with what the miner will do with other blocks with transactions he can't verify.

This should now be fixed.

This has been frequently requested.

If you find these notifications annoying, be aware that you can disable them in your profile.

Sorry, Linux crashed right after I went to sleep, and I didn't have panic_on_oops set, so it didn't restart.

I will look into this soon.

If storage ends up being really expensive (which I doubt), miners might use demurrage. I think it's a good solution for that (unlikely) case, in fact.

More than 50% of the miners need to agree before actually forgetting transactions, though. Otherwise you'll get the problems that I've described.

Block hash = block header hash.

A hash of the entire block is never made by Bitcoin, and no one uses such a hash for anything.

All of the block data is indirectly hashed through the hash tree. This is represented in the block hash.

The fee is not specified directly by the transaction. It is calculated by looking at the difference between input value (which is also not specified) and output value.

Ignoring the other problems with doing this, you could accept the transaction into your own blocks without knowing the exact fee, but you could not correctly verify other blocks that include the transaction. For all you know, the transaction you've forgotten permits a fee of 1000 BTC.


You don't gain any hashing power. Only disk space, which is cheap.

I believe the slang term is "newfag".