Re: [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change

2015-10-08 Thread Rusty Russell via bitcoin-dev
Peter Todd writes: > On Tue, Oct 06, 2015 at 12:28:49PM +1030, Rusty Russell wrote: >> Peter Todd via bitcoin-dev >> writes: >> > However I don't think we've done a good job showing why we need to >> > implement this feature via nSequence. >> >> It could be implemented in other ways, but nSequen

Re: [bitcoin-dev] Mike Hearn, who coined the term SPV is Satoshi

2015-10-08 Thread Sriram Karra via bitcoin-dev
Off topic. On Oct 9, 2015 4:27 AM, "Boris Neklabaro via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: > Interesting: > > http://kke5edzhy54hiee5.onion/ > (requires Tor Browser) > > or without Tor Browser: > http://kke5edzhy54hiee5.onion.to/ > > >

Re: [bitcoin-dev] Why not checkpointing the transactions?

2015-10-08 Thread jl2012 via bitcoin-dev
You are mixing multiple issues. 1. It is not possible to "checkpoint" in a totally decentralized and trustless way. You need the whole blockchain to confirm its validity, as a single invalid tx in the history will invalidate ALL blocks after it, even if the invalid tx is irrelevant to you. 2

[bitcoin-dev] Making soft forks pluggable

2015-10-08 Thread Eric Lombrozo via bitcoin-dev
Before I scare anyone away, please here me out: It occurs to me it wouldn't be all that difficult to support the ability to define soft forks entirely as standalone units that can be trivially merged with Bitcoin Core. It would require a few changes in some places in the consensus code, but at

[bitcoin-dev] Why not checkpointing the transactions?

2015-10-08 Thread telemaco via bitcoin-dev
Hello, I have been working on database engineering for many years and there are some things i don't understand very well about how bitcoin architecture works. I have not written here because i would not like to disturb development with yet another of those far to implement ideas that does not

[bitcoin-dev] Mike Hearn, who coined the term SPV is Satoshi

2015-10-08 Thread Boris Neklabaro via bitcoin-dev
Interesting: http://kke5edzhy54hiee5.onion/(requires Tor Browser) or without Tor Browser:http://kke5edzhy54hiee5.onion.to/ ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev

Re: [bitcoin-dev] merged multisig inputs

2015-10-08 Thread Gregory Maxwell via bitcoin-dev
On Thu, Oct 8, 2015 at 7:55 PM, Boris Neklabaro via bitcoin-dev wrote: > Hi, > > Is it possible to merge 2 utxos spending from multiple P2SH inputs? Or > combined inputs P2SH and P2PKH in a single transaction? Yes, the signatures for separate inputs are entirely separate.

[bitcoin-dev] merged multisig inputs

2015-10-08 Thread Boris Neklabaro via bitcoin-dev
Hi, Is it possible to merge 2 utxos spending from multiple P2SH inputs? Or combined inputs P2SH and P2PKH in a single transaction? ___ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitco

Re: [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change

2015-10-08 Thread Peter Todd via bitcoin-dev
On Tue, Oct 06, 2015 at 12:28:49PM +1030, Rusty Russell wrote: > Peter Todd via bitcoin-dev > writes: > > However I don't think we've done a good job showing why we need to > > implement this feature via nSequence. > > It could be implemented in other ways, but nSequence is the neatest and > most

Re: [bitcoin-dev] CHECKSEQUENCEVERIFY - We need more usecases to motivate the change

2015-10-08 Thread Peter Todd via bitcoin-dev
On Sat, Oct 03, 2015 at 04:30:56PM +0200, Peter Todd via bitcoin-dev wrote: > BIP68 and BIP112 collectively define the CHECKSEQUENCEVERIFY semantics, Another issue that came to mind re: CSV review is that there isn't actually any one pull-req with all the code changes together, making it hard to