1 2016-04-03 11:45:15 <runeks> Is the secp256k1 library intended to be used in such a way that any signature it verifies will necessarily be valid in a Bitcoin transaction (to the Bitcoin network), but not necessarily the other way around? Ie. OpenSSL might accept some signatures as valid that secp256k1 wouldn't, but the opposite should never occur.
2 2016-04-03 12:44:33 <anuanuanu> Hello - question for the room: is there a way to find out how many times the blockchain has had two different valid blocks broadcasted by two different miners creating a fork in the blockchain? My understanding is that this would create a fork and eventually the fork with the most amount of work will prevail as the valid one. I am curious to understand how often this occurs? Is there somewhere that I can look to find o
3 2016-04-03 12:44:33 <anuanuanu> In these situations what block depth was reached before the blockchain resolved itself?
4 2016-04-03 12:57:53 <anuanuanu> how often has  unintentional consensus forks been observed in the bitcoin blockchain?
5 2016-04-03 13:07:35 <waxwing> i'm testing on regtest and tried to make a transaction with sighash_none, and got "insufficient priority". is there some rule about that?
6 2016-04-03 13:19:31 <waxwing> seems the same with SINGLE instead of NONE . it's not the fees it seems.
7 2016-04-03 13:21:27 <waxwing> ok, cancel, sorry it was just a zero output amount.