📅 Original date posted:2013-06-27
📝 Original message:On Thu, Jun 27, 2013 at 1:10 PM, Jim <jim618 at fastmail.co.uk> wrote:
> Hello Everybody,
>
> Over the last few months we have been steadily adding
> functionality to MultiBit including:
> + encrypted wallets
> + sign and verify message
> + stability improvements and bug fixes.
>
> As a result of these efforts I think MultiBit is now
> suitable for the entry level Bitcoin user. I propose
> that we put MultiBit as the default desktop client
> on the bitcoin.org "Choose your wallet" page.
>
> I think a typical new user comes to bitcoin.org from a
> google search or a Bitcoin news article. We want them to
> peruse the bitcoin.org site and try out a wallet. They
> should be able to get MultiBit up and running in a tea break.
> Then perhaps they get a colleague to send them some bitcoin
> from an Android phone by zapping a QR code.
This is definitely a great discussion to have. Here are some initial,
unprioritized thoughts. As an engineer, there is never a clear
answer, but a balance of costs and benefits.
Arguments in favor of moving away from Bitcoin-Qt/bitcoind for wallet services:
* Bitcoin-Qt is admittedly a very simple wallet. I see it's core
strengths more as a "P2P router" for the public blockchain data.
* Wallet feature innovation moves more slowly than
Armory/bitcoinj/blockchain.info.
* Requires the full blockchain, which is resource-intensive versus SPV.
Arguments in favor of retaining Bitcoin-Qt/bitcoind default:
* More field experience, code review and testing on desktop than others
* Very real possibility of an overall net reduction of full nodes on P2P network
Arguments in favor of multibit default:
* Good user interface, perhaps more friendly for entry level users as
you describe
* Based on bitcoinj, which has field experience and a very large
installed base thanks to Bitcoin Wallet/Schildbach
Arguments against multibit default:
* Less testing, field experience on desktop
I'm sure others can come up with a few more.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 15:03:57
in reply to nevent1q…2dvr
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 15:03:57Event JSON
{
"id": "502241ba00b01b94d212301b7d116635147b1205eb218a73782d0bc3676b163a",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686150237,
"kind": 1,
"tags": [
[
"e",
"5ec662796ac6f7c2f8d4618ee0bafe23cd8003de44ad7e1121634fb73b588358",
"",
"root"
],
[
"e",
"2e3a5da0b290d080a8de4654e78d179a75e911b46ab86557b7e5fe511cca70bf",
"",
"reply"
],
[
"p",
"e9799fb8f78387b0c1fd27d4d15afa550d214db447d801dae134d0d1703271ec"
]
],
"content": "📅 Original date posted:2013-06-27\n📝 Original message:On Thu, Jun 27, 2013 at 1:10 PM, Jim \u003cjim618 at fastmail.co.uk\u003e wrote:\n\u003e Hello Everybody,\n\u003e\n\u003e Over the last few months we have been steadily adding\n\u003e functionality to MultiBit including:\n\u003e + encrypted wallets\n\u003e + sign and verify message\n\u003e + stability improvements and bug fixes.\n\u003e\n\u003e As a result of these efforts I think MultiBit is now\n\u003e suitable for the entry level Bitcoin user. I propose\n\u003e that we put MultiBit as the default desktop client\n\u003e on the bitcoin.org \"Choose your wallet\" page.\n\u003e\n\u003e I think a typical new user comes to bitcoin.org from a\n\u003e google search or a Bitcoin news article. We want them to\n\u003e peruse the bitcoin.org site and try out a wallet. They\n\u003e should be able to get MultiBit up and running in a tea break.\n\u003e Then perhaps they get a colleague to send them some bitcoin\n\u003e from an Android phone by zapping a QR code.\n\nThis is definitely a great discussion to have. Here are some initial,\nunprioritized thoughts. As an engineer, there is never a clear\nanswer, but a balance of costs and benefits.\n\nArguments in favor of moving away from Bitcoin-Qt/bitcoind for wallet services:\n* Bitcoin-Qt is admittedly a very simple wallet. I see it's core\nstrengths more as a \"P2P router\" for the public blockchain data.\n* Wallet feature innovation moves more slowly than\nArmory/bitcoinj/blockchain.info.\n* Requires the full blockchain, which is resource-intensive versus SPV.\n\nArguments in favor of retaining Bitcoin-Qt/bitcoind default:\n* More field experience, code review and testing on desktop than others\n* Very real possibility of an overall net reduction of full nodes on P2P network\n\nArguments in favor of multibit default:\n* Good user interface, perhaps more friendly for entry level users as\nyou describe\n* Based on bitcoinj, which has field experience and a very large\ninstalled base thanks to Bitcoin Wallet/Schildbach\n\nArguments against multibit default:\n* Less testing, field experience on desktop\n\nI'm sure others can come up with a few more.\n\n-- \nJeff Garzik\nSenior Software Engineer and open source evangelist\nBitPay, Inc. https://bitpay.com/",
"sig": "e62c834a760d85f430f73134cba4fd159a451a5c01ede2717028f735ec8f6a32fbac4a91b5fafb484dadc34317927617879a65020d89bf7bf14d16a09d32b690"
}