summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJim <jim618@fastmail.co.uk>2013-06-27 20:50:00 +0100
committerbitcoindev <bitcoindev@gnusha.org>2013-06-27 19:50:07 +0000
commit02c9ed34d676b6420ee9009d71fb4c041113d231 (patch)
tree97a0f628c9ca283270a73b135adfafa5f5ab369e
parentec7ef2a63732928237930386aefbee7eb34a5361 (diff)
downloadpi-bitcoindev-02c9ed34d676b6420ee9009d71fb4c041113d231.tar.gz
pi-bitcoindev-02c9ed34d676b6420ee9009d71fb4c041113d231.zip
Re: [Bitcoin-development] Proposal: MultiBit as default desktop client on bitcoin.org
-rw-r--r--a2/027cd56d82df1d333a86fcb7394575ea79cd76231
1 files changed, 231 insertions, 0 deletions
diff --git a/a2/027cd56d82df1d333a86fcb7394575ea79cd76 b/a2/027cd56d82df1d333a86fcb7394575ea79cd76
new file mode 100644
index 000000000..5064cf38d
--- /dev/null
+++ b/a2/027cd56d82df1d333a86fcb7394575ea79cd76
@@ -0,0 +1,231 @@
+Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
+ helo=mx.sourceforge.net)
+ by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <jim618@fastmail.co.uk>) id 1UsICl-0006TG-Nh
+ for bitcoin-development@lists.sourceforge.net;
+ Thu, 27 Jun 2013 19:50:07 +0000
+Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of fastmail.co.uk
+ designates 66.111.4.26 as permitted sender)
+ client-ip=66.111.4.26; envelope-from=jim618@fastmail.co.uk;
+ helo=out2-smtp.messagingengine.com;
+Received: from out2-smtp.messagingengine.com ([66.111.4.26])
+ by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256)
+ (Exim 4.76) id 1UsICk-0007AB-B3
+ for bitcoin-development@lists.sourceforge.net;
+ Thu, 27 Jun 2013 19:50:07 +0000
+Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42])
+ by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id D7B8720B33
+ for <bitcoin-development@lists.sourceforge.net>;
+ Thu, 27 Jun 2013 15:50:00 -0400 (EDT)
+Received: from web3.nyi.mail.srv.osa ([10.202.2.213])
+ by compute2.internal (MEProxy); Thu, 27 Jun 2013 15:50:00 -0400
+Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99)
+ id AE8D0B00005; Thu, 27 Jun 2013 15:50:00 -0400 (EDT)
+Message-Id: <1372362600.25810.140661249292685.2513C2E6@webmail.messagingengine.com>
+X-Sasl-Enc: OaYqxBHcjaD/bSHG42fxJ9wBd/AzpGi25jT4hV5hXxrT 1372362600
+From: Jim <jim618@fastmail.co.uk>
+To: bitcoin-development@lists.sourceforge.net
+MIME-Version: 1.0
+Content-Transfer-Encoding: 7bit
+Content-Type: text/plain
+X-Mailer: MessagingEngine.com Webmail Interface - ajax-5ae8e04c
+In-Reply-To: <1372362018.21506.140661249289441.6E1B5441@webmail.messagingengine.com>
+References: <1372353053.10405.140661249237317.77984E1F@webmail.messagingengine.com>
+ <CAJHLa0Ncac9Xt-AQBnpghqqpfR-j6Xtd9qVQoUe2dPp0kJvz1A@mail.gmail.com>
+ <201306271804.51009.luke@dashjr.org>
+ <CAAS2fgRE+gj0NrDMk-WamSU+mADJM1EqgR-6Sa2MNCbwq-0Gdw@mail.gmail.com>
+ <1372360716.14869.140661249272837.1376DACB@webmail.messagingengine.com>
+ <1372362018.21506.140661249289441.6E1B5441@webmail.messagingengine.com>
+Date: Thu, 27 Jun 2013 20:50:00 +0100
+X-Spam-Score: -0.7 (/)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+ -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
+ sender-domain
+ 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
+ (jim618[at]fastmail.co.uk)
+ -0.0 SPF_PASS SPF: sender matches SPF record
+ 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in
+ digit (jim618[at]fastmail.co.uk)
+ 0.6 URIBL_SBL Contains an URL listed in the SBL blocklist
+ [URIs: dashjr.org]
+ -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
+ author's domain
+ 0.1 DKIM_SIGNED Message has a DKIM or DK signature,
+ not necessarily valid
+ -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
+X-Headers-End: 1UsICk-0007AB-B3
+Subject: Re: [Bitcoin-development] Proposal: MultiBit as default desktop
+ client on bitcoin.org
+X-BeenThere: bitcoin-development@lists.sourceforge.net
+X-Mailman-Version: 2.1.9
+Precedence: list
+List-Id: <bitcoin-development.lists.sourceforge.net>
+List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
+List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
+List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
+List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
+List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
+X-List-Received-Date: Thu, 27 Jun 2013 19:50:07 -0000
+
+I missed Greg's point on confirmations.
+It is definitely a challenge to explain/ visualize both:
++ has the transaction propagated the network ?
+and
++ it it confirmed/ buried in a block ?
+
+when those words probably don't mean much to
+the intended audience.
+
+The transaction status icons I *think* do it
+(explained here:
+https://multibit.org/en/help/v0.5/help_transactions.html).
+
+It basically boils down to:
+1) triangle or square : bad.
+2) filling circle : good
+3) tick mark : great.
+
+
+On Thu, Jun 27, 2013, at 08:40 PM, Jim wrote:
+> RE: 141.101.113.245
+>
+> http://whois.domaintools.com/141.101.113.245
+> gives it as CloudFlare - I suspect it is protecting
+> Mt Gox when we make our get for currency ticker info.
+>
+>
+> On Thu, Jun 27, 2013, at 08:18 PM, Jim wrote:
+> > A few replies, in order of point raised:
+> >
+> > Jeff:
+> > Arguments against multibit default:
+> > * Less testing, field experience on desktop
+> >
+> > Yes this is true - downloads of multibit have typically been around
+> > 1/7th to 1/5th of bitcoin-QT downloads. It helps of course that
+> > the bitcoinj networking/ object model is also used by Andreas
+> > as you note.
+> >
+> >
+> > Greg:
+> > I think Mike has squashed the deadlocking problems with reentrant
+> > locks (primarily in the Wallet). I haven't seen one in at least a month.
+> >
+> > We discussed proxy support on the bitcoinj mailing list a while ago
+> > and at the time the stumbling block was the Java library used for
+> > the networking (Netty) did not support it. Mike or Miron would
+> > know better than I if this is still the case.
+> >
+> > Change address behaviour will improve significantly when HD
+> > wallet support goes into multibit/ bitcoinj (I am hoping to get my
+> > bit done over the summer). Matija Mazi has been working on a
+> > Java impl of HD wallets so it is coming down the pipe but
+> > there is a lot to do yet.
+> >
+> > Connections out from MultiBit are:
+> > + 4 bitcoind nodes on port 8333
+> > + multibit.org (188.138.113.201) for help, current version info
+> > (and probably more in future)
+> > + the currency ticker will make HTTP gets to the source of
+> > whichever exchange(s) you have set up e.g MtGox, CampBX.
+> > This calls should disappear if you switch the currency conversion
+> > and ticker off.
+> >
+> > I think that is all the connections out I make.
+> >
+> > Mainly due to the exchanges abruptly changing their APIs and
+> > breaking things we are planning to put in intermediate
+> > "Exchange Data Provider" servers. Tim Molter is working on this
+> > in his XChange project. That will enable us to patch the server
+> > when things change and the multibits in the field won't be
+> > affected. There will probably be a couple of these initially
+> > for redundancy.
+> >
+> > Alex: Yes I think most users migrate to blockchain.info or,
+> > more recently coinbase.com. They are both good wallets
+> > but I'd like to keep Bitcoin as P2P as possible.
+> >
+> > Luke-Jr
+> > I think you are right here on the number of full nodes versus
+> > SPV nodes.
+> > I don't think we even know yet what are the working ratios of
+> > full nodes to SPV nodes. I haven't seen anybody do any
+> > analysis on this.
+> >
+> > I doubt multibit will ever participate in the Bitcoin network
+> > other than as an SPV client. All the optimisation is to reduce
+> > data traffic - it is effectively a mobile wallet that happens to
+> > live on a desktop. It is not really intended to be more than
+> > "a wallet for regular people to store and spend their bitcoin".
+> >
+> > In English the nomenclature for direction of the transactions
+> > is: "Sent to" and "Received with". To be honest I
+> > haven't transliterated the localisation files to check other
+> > language packs but the localisers are pretty good in my
+> > experience.
+> >
+> >
+> >
+> >
+> >
+> > On Thu, Jun 27, 2013, at 07:41 PM, Gregory Maxwell wrote:
+> > > On Thu, Jun 27, 2013 at 11:04 AM, Luke-Jr <luke@dashjr.org> wrote:
+> > > > On Thursday, June 27, 2013 5:30:21 PM Jeff Garzik wrote:
+> > > >> * Very real possibility of an overall net reduction of full nodes on P2P
+> > > >> network
+> > > > Even a reduction of *nodes at all*, as I've never seen a listening bitcoinj or
+> > > > MultiBit node. :/
+> > > > Jim, will MultiBit be adding p2p listening support?
+> > >
+> > > Without validation listening isn't currently very useful. :( Maybe it
+> > > could be somewhat more with some protocol additions.
+> > >
+> > > ------------------------------------------------------------------------------
+> > > This SF.net email is sponsored by Windows:
+> > >
+> > > Build for Windows Store.
+> > >
+> > > http://p.sf.net/sfu/windows-dev2dev
+> > > _______________________________________________
+> > > Bitcoin-development mailing list
+> > > Bitcoin-development@lists.sourceforge.net
+> > > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
+> >
+> >
+> > --
+> > https://multibit.org Money, reinvented
+> >
+> > ------------------------------------------------------------------------------
+> > This SF.net email is sponsored by Windows:
+> >
+> > Build for Windows Store.
+> >
+> > http://p.sf.net/sfu/windows-dev2dev
+> > _______________________________________________
+> > Bitcoin-development mailing list
+> > Bitcoin-development@lists.sourceforge.net
+> > https://lists.sourceforge.net/lists/listinfo/bitcoin-development
+>
+>
+> --
+> https://multibit.org Money, reinvented
+>
+> ------------------------------------------------------------------------------
+> This SF.net email is sponsored by Windows:
+>
+> Build for Windows Store.
+>
+> http://p.sf.net/sfu/windows-dev2dev
+> _______________________________________________
+> Bitcoin-development mailing list
+> Bitcoin-development@lists.sourceforge.net
+> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
+
+
+--
+https://multibit.org Money, reinvented
+
+