📅 Original date posted:2011-06-16
🗒️ Summary of this message: Scaling-up issues, wallet security, and unit testing framework are critical needs for Bitcoin. Testing in the field is more effective than unit testing.
📝 Original message:On Thu, Jun 16, 2011 at 12:32 PM, Gavin Andresen
<gavinandresen at gmail.com> wrote:
> 1) Scaling-up issues, like disconnections when downloading the block chain.
>
> 2) Wallet security.
Agreed, though security professionals (and luke-jr) are already
pointing out the wallet crypto mainly eliminates a bit of bad PR,
rather than being a major crime deterrent.
zooko on IRC had a pretty good suggestion: introduce a built-in
facility for air-gapped wallets (multiple wallets), so that loss of
your everyday transactional wallet does not mean loss of everything.
You can do this manually, but we need something for all the people who
(a) don't know crypto, and (b) simply download and run the client
without thinking much about security.
> 3) Unit testing framework. There was a PULL that had the start of
> boost unit tests; I think that is a critical need, along with a good
> suite of test cases.
Three points, on testing:
T1) autotools has a minimal testing framework built into it. "make
check" builds, and then runs tests. Each test is a program or script,
that returns 0 on success and 1 on failure. "make distcheck" builds,
runs tests, and then creates the distribution tarball if the tests
succeed.
T2) I wouldn't narrow the focus to "unit tests", as stress tests and
other comprehensive, automated tests are quite useful as well
but most importantly...
T3) Don't hold v0.4 release for this. As we say in kernel-land, we
have a test lab called "the internet" Test suites have clear software
engineering value, but they largely "guard the past" -- making sure
you don't repeat past mistakes, rather than being a good indicator of
possible upcoming problems. The best testing is always in the field.
That always finds more problems than unit testing ever does.
--
Jeff Garzik
exMULTI, Inc.
jgarzik at exmulti.com
Jeff Garzik [ARCHIVE] /
npub1kf…f3f58
2023-06-07 01:38:25
in reply to nevent1q…up9v
Author Public Key
npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58Published at
2023-06-07 01:38:25Event JSON
{
"id": "7aa520ae379473fb6bd12443e8adac0b3d34882e6852c6439c464aec4056db3e",
"pubkey": "b25e10e25d470d9b215521b50da0dfe7a209bec7fedeb53860c3e180ffdc8c11",
"created_at": 1686101905,
"kind": 1,
"tags": [
[
"e",
"210b9203240ad106b92714cbc619bb3695fd79f3063e1a4523dba8506c0f7178",
"",
"root"
],
[
"e",
"0bf390a8afaa87cf75bab5c49647eb0505923f8e363fcc0bbd9e82d355ca5376",
"",
"reply"
],
[
"p",
"6ac6a519b554d8ff726a301e3daec0b489f443793778feccc6ea7a536f7354f1"
]
],
"content": "📅 Original date posted:2011-06-16\n🗒️ Summary of this message: Scaling-up issues, wallet security, and unit testing framework are critical needs for Bitcoin. Testing in the field is more effective than unit testing.\n📝 Original message:On Thu, Jun 16, 2011 at 12:32 PM, Gavin Andresen\n\u003cgavinandresen at gmail.com\u003e wrote:\n\u003e 1) Scaling-up issues, like disconnections when downloading the block chain.\n\u003e\n\u003e 2) Wallet security.\n\nAgreed, though security professionals (and luke-jr) are already\npointing out the wallet crypto mainly eliminates a bit of bad PR,\nrather than being a major crime deterrent.\n\nzooko on IRC had a pretty good suggestion: introduce a built-in\nfacility for air-gapped wallets (multiple wallets), so that loss of\nyour everyday transactional wallet does not mean loss of everything.\n\nYou can do this manually, but we need something for all the people who\n(a) don't know crypto, and (b) simply download and run the client\nwithout thinking much about security.\n\n\n\u003e 3) Unit testing framework. There was a PULL that had the start of\n\u003e boost unit tests; I think that is a critical need, along with a good\n\u003e suite of test cases.\n\nThree points, on testing:\n\nT1) autotools has a minimal testing framework built into it. \"make\ncheck\" builds, and then runs tests. Each test is a program or script,\nthat returns 0 on success and 1 on failure. \"make distcheck\" builds,\nruns tests, and then creates the distribution tarball if the tests\nsucceed.\n\nT2) I wouldn't narrow the focus to \"unit tests\", as stress tests and\nother comprehensive, automated tests are quite useful as well\n\nbut most importantly...\n\nT3) Don't hold v0.4 release for this. As we say in kernel-land, we\nhave a test lab called \"the internet\" Test suites have clear software\nengineering value, but they largely \"guard the past\" -- making sure\nyou don't repeat past mistakes, rather than being a good indicator of\npossible upcoming problems. The best testing is always in the field.\nThat always finds more problems than unit testing ever does.\n\n-- \nJeff Garzik\nexMULTI, Inc.\njgarzik at exmulti.com",
"sig": "b566532809cfe907eee8f2ef7bf7d483d9cc40f37bf9edd89769c32d40ded95bdc096f4e19ccf91cd860edca5e8dbdda174dc3474d53980dd21f8629483e135f"
}