From: "theymos" <theymos@mm.st>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] multisig, op_eval and lock_time/sequence...
Date: Wed, 09 Nov 2011 16:13:36 -0600 [thread overview]
Message-ID: <1320876816.29760.140660996851709@webmail.messagingengine.com> (raw)
In-Reply-To: <CABsx9T3ESoZ21h_V0a8PZAN4MS+KRZ8eVjKc47p9wgJmH0jt-g@mail.gmail.com>
For now I think requiring direct-connection negotiation is best for these kinds of things. A direct connection is OK in most cases, and more complicated schemes will be more likely to fail. Maybe the IP transactions protocol can be used.
In the future, I imagine that users of ultra-lightweight clients will connect to a new P2P network built on top of the core Bitcoin network in order to receive block headers and info about sent/received transactions without leeching off of the few full nodes. This network could also be used for indirect transaction negotiation, which is similar to the goal of finding your own received transactions.
On Wednesday, November 09, 2011 3:02 PM, "Gavin Andresen" <gavinandresen@gmail.com> wrote:
> a nValue=0 transaction can be considered 'immediately spent'
I believe it's possible to spend a 0-value output, so they can't be considered automatically spent.
next prev parent reply other threads:[~2011-11-09 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 10:22 [Bitcoin-development] multisig, op_eval and lock_time/sequence Michael Grønager
2011-11-09 14:43 ` Alan Reiner
2011-11-09 15:22 ` Alan Reiner
2011-11-09 19:13 ` Gavin Andresen
2011-11-09 20:02 ` Gavin Andresen
2011-11-09 20:31 ` Michael Grønager
2011-11-09 21:18 ` Gavin Andresen
2011-11-09 21:32 ` Joel Joonatan Kaartinen
2011-11-09 22:13 ` theymos [this message]
2011-11-09 20:03 ` Michael Grønager
2011-11-10 3:00 ` Alan Reiner
2011-11-10 9:55 ` Michael Grønager
2011-11-10 12:56 ` Alan Reiner
2011-11-12 16:58 ` Mike Hearn
2011-11-12 17:10 ` Alan Reiner
2011-11-12 17:16 ` Mike Hearn
2011-11-12 17:25 ` Alan Reiner
2011-11-12 17:38 ` Mike Hearn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1320876816.29760.140660996851709@webmail.messagingengine.com \
--to=theymos@mm.st \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox