Files
bitcoin/src
Gavin Andresen 6f8730752c Treat non-final transactions as non-standard
At least one service that accepted zero-confirmation transactions
was vulnerable because an attacker could send a transaction
with a lock time far in the future, and then have plenty of time in
which to get a double-spend mined (perhaps from a miner who wasn't
on the network when the first transaction was broadcast).

That is a variation on the "Finney attack". We still don't
recommend anybody accept 0-confirmation transactions as final
payment for anything. This change keeps non-final transactions
from appearing in the wallet, and, assuming most of the network
accepts this change, will prevent them from being relayed until
they are final.
2013-01-26 14:38:40 -05:00
..
2012-04-27 10:14:33 -04:00
2013-01-26 01:40:42 +01:00
2012-12-18 21:39:29 +01:00
2012-08-28 17:13:11 -04:00
2012-12-17 18:09:53 +08:00
2012-05-18 22:02:28 +08:00
2013-01-08 02:00:59 +01:00
2012-05-18 22:02:28 +08:00
2012-10-25 16:12:40 +02:00
2012-05-18 22:02:28 +08:00
2012-10-20 23:08:56 +02:00
2012-12-18 21:39:29 +01:00
2013-01-23 10:42:46 -05:00
2013-01-23 10:42:46 -05:00
2012-12-18 21:39:29 +01:00
2012-11-16 00:12:33 +01:00
2013-01-01 17:12:30 -05:00
2013-01-01 17:12:30 -05:00
2012-10-08 17:46:45 -04:00