From: Mike Hearn <mike@plan99•net>
To: Brian McQueen <mcqueenorama@gmail•com>
Cc: Bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Transaction Delivery and Storage
Date: Wed, 5 Oct 2011 17:17:30 +0200 [thread overview]
Message-ID: <CANEZrP02QiScfqWWBR7jNjZ9nDT7KkWuzK4Ua9NtVEwyiDAWKA@mail.gmail.com> (raw)
In-Reply-To: <CAPfzCrS87dJwHC=HQAVcfm8Fm9r5LdENg5s9JUnLuZr+sgh+jg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 331 bytes --]
I imagine a lot of the things on the contracts page will be implemented by
specialized software that interacts with the Bitcoin network directly.
Transactions would then be moved around, for example, by having clients do
HTTP POSTs of protocol buffers to servers that are listening and know how to
interpret the received messages.
[-- Attachment #2: Type: text/html, Size: 363 bytes --]
prev parent reply other threads:[~2011-10-05 15:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-05 5:18 Brian McQueen
2011-10-05 5:23 ` Gregory Maxwell
2011-10-05 15:17 ` Mike Hearn [this message]
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=CANEZrP02QiScfqWWBR7jNjZ9nDT7KkWuzK4Ua9NtVEwyiDAWKA@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mcqueenorama@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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