public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Mike Hearn <mike@plan99•net>
To: Wladimir <laanwj@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
Date: Tue, 24 Jun 2014 14:16:00 +0200	[thread overview]
Message-ID: <CANEZrP0sT3KTPatwNFO5gjwShkGQt=h6PjX-3Df2U9oXa=3JUA@mail.gmail.com> (raw)
In-Reply-To: <CA+s+GJADNS6zy--sk3W3q21inuSB5jkkRku14vxLXDXKf=vkvw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]

>
> Although Pieter and I disagree with regard to issue #4351, we agree on
> wanting to keep (or at least making) bitcoind as lean as possible.
> Maintaining extra indices for others doesn't fit in there - that's
> also why the address index patch was not merged. An 'index node' could
> be a different animal.


We definitely want to head in the direction of allowing a p2p node to be as
useful as possible within its resource constraints and optional advertising
of new (expensive) indexes is the way to go.

Sometimes I wonder if we should have an RPC or new socket based method
where additional programs could run along side Bitcoin Core and opt to
handle a subset of p2p commands. But then I think, that seems like a lot of
complexity for people who just want to help out the system, which I guess
is the bulk of our network now. Keeping their lives simple should have a
high priority. So a single unified program that just figures it out
automatically rather than expecting users to assemble a bag of parts seems
a goal worth striving for.

[-- Attachment #2: Type: text/html, Size: 1344 bytes --]

  reply	other threads:[~2014-06-24 12:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-23  9:50 Jorge Timón
2014-06-23 10:32 ` Wladimir
2014-06-23 20:15   ` Jorge Timón
2014-06-24  9:07     ` Wladimir
2014-06-24  9:44       ` Wladimir
2014-06-24 13:24         ` Thomas Voegtlin
2014-06-24 15:33       ` Justus Ranvier
2014-06-24 16:40         ` Jorge Timón
2014-06-25  5:43           ` Wladimir
2014-06-24  9:11     ` Mike Hearn
2014-06-24  9:40       ` Wladimir
2014-06-24 10:12         ` Mike Hearn
2014-06-24 11:29       ` Jorge Timón
2014-06-24 11:48         ` Tamas Blummer
2014-06-24 13:26           ` Jorge Timón
2014-06-24 13:37             ` Pieter Wuille
2014-06-24 11:58         ` Wladimir
2014-06-24 12:16           ` Mike Hearn [this message]
2014-06-24 12:41             ` Wladimir

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='CANEZrP0sT3KTPatwNFO5gjwShkGQt=h6PjX-3Df2U9oXa=3JUA@mail.gmail.com' \
    --to=mike@plan99$(echo .)net \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=laanwj@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