|
Title: How is this tx confirming? Post by: spin on October 03, 2014, 07:57:10 AM I am ignoring spam dust but how is this tx confirming? I thought tx with outputs that are too small should not confirm?
https://insight.bitpay.com/tx/3604367170e2340c757e7e956c583a2860a86982f3f830296003926052a64ec1 http://btc.blockr.io/tx/info/3604367170e2340c757e7e956c583a2860a86982f3f830296003926052a64ec1 Thanks. Title: Re: How is this tx confirming? Post by: Muhammed Zakir on October 04, 2014, 04:04:59 PM You may want to read this : https://bitcoin.org/en/developer-guide#standard-transactions .
Quote Abstract. If you create a redeem script, hash it, and use the hash in a P2SH output, the network sees only the hash, so it will accept the output as valid no matter what the redeem script says. This allows payment to non-standard pubkey script almost as easily as payment to standard pubkey scripts. However, when you go to spend that output, peers and miners using the default settings will check the redeem script to see whether or not it’s a standard pubkey script. If it isn’t, they won’t process it further—so it will be impossible to spend that output until you find a miner who disables the default settings. ~~MZ~~ |