From: Amir Taaki <zgenjix@yahoo•com>
To: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] BIP 33 - Stratized Nodes
Date: Wed, 16 May 2012 10:37:32 -0700 (PDT) [thread overview]
Message-ID: <1337189852.2839.YahooMailNeo@web121001.mail.ne1.yahoo.com> (raw)
In-Reply-To: <CAMGNxUuPYYtTB=aOyQjb7Gw=RZODFry=7DWkWST0EN_67rjK8g@mail.gmail.com>
> 1) This is cool and useful (but see 3)
> 2) This is significantly less secure than validating an entire blockchain; it's certainly worth working out some use cases here in more detail than just a sample conversation. More on this below
> 3) What about discovery? Will a client now have the chance to look for NODE_STRATIZED clients on IRC? How do you envision a stratized server decides which transactions to relay/store? Or is it just a caching layer in front of a high quality blockchain service? If it is just a caching service, the question of cache hits / misses is an interesting one as well.
Stratized nodes do discovery as normal. Service nodes are explicitly chosen like IRC servers are for IRC clients.
> 4) What are the economic motivations to run a stratized server? Other than cheating people of course.
None. Same as BitTorrent super-nodes, Tor relays or email servers. People don't need economic motivation for everything.
> 5) Seems like a 'send me everything for this source address' is going to save a lot of roundtrip conversations for what I imagine the most common request will be.
That's a bad idea. I prefer to keep each request minimal to prevent resource starvation and simplify the protocol (while shifting the onus onto the client). Also the history can be resolved with multiple services while the data is being downloaded and sorted.
prev parent reply other threads:[~2012-05-16 17:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 16:34 Amir Taaki
2012-05-16 16:46 ` Mike Hearn
2012-05-16 17:32 ` Amir Taaki
2012-05-16 18:22 ` Jeff Garzik
2012-05-16 16:49 ` Peter Vessenes
2012-05-16 17:37 ` Amir Taaki [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=1337189852.2839.YahooMailNeo@web121001.mail.ne1.yahoo.com \
--to=zgenjix@yahoo$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/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