What can make an unconfirmed transaction (0-conf) an invalid one other than Double-spend?
What can make an unconfirmed transaction (0-conf) an invalid one other than Double-spend?
It's obvious that inputs that already been spent will make the transaction invalid (pure double-spend scenario), but is there's anything else that could make a tx invalid?
Invalid inputs? Invalid signature or other data?
For example, if I have a program that manages a wallet (keypairs are exclusively managed by it, and not by any human, and it's source is public) and it sends payments, can the recipient be insured that even 0-conf tx will be eventually valid and processes?
https://ift.tt/2x0Tkvg
Comments
Post a Comment