Skip to archive
Degrees of SatoshiFollow the connections.
Degrees of Satoshi/ Satoshi record

Public-record atlas · Edition 1.0.0

Satoshi, in the record.

A searchable catalogue of the messages, quotation records and recipient-published correspondence attached to the Satoshi Nakamoto identity. Every entry keeps its date, channel, provenance and route back to context.

Scope / read first

“All known” requires a boundary.

This edition indexes every Satoshi-authored public message enumerable in the pinned Complete Satoshi source snapshot: 39 mailing-list messages and 542 active-era forum posts. It also maps all 162 entries in that archive’s curated quotation index and registers major private collections later published by recipients or introduced in court.

It cannot contain every communication Satoshi ever wrote. Deleted posts, private-board material, lost mailboxes and undisclosed correspondence are unknowable. BitcoinTalk’s public profile counter reports 575 posts, while 539 are currently enumerable; the archive preserves that discrepancy instead of manufacturing missing records.

Coverage manifest

What is counted—and where it came from.

Counts refer to records, not necessarily distinct ideas. Cross-posted releases and quoted reply chains can repeat material across venues.

Coverage of the public Satoshi Nakamoto message and quotation archive
CorpusCoverageEnumerable materialProvenanceSource
Cryptography Mailing List31 October 2008—25 January 200918 Satoshi-authored public messagescontemporaneous public originalOpen index ↗
bitcoin-list10 December 2008—13 December 201016 Satoshi-authored public messagescontemporaneous public originalOpen index ↗
P2P Research List11—13 February 20095 Satoshi-authored public messagesarchival mirrorOpen index ↗
P2P Foundation11—18 February 20093 active-era public postsarchival mirrorOpen index ↗
BitcoinTalk22 November 2009—12 December 2010539 currently enumerable public postscontemporaneous public originalOpen index ↗
The Quotable Satoshi31 October 2008—7 March 2014162 curated quotation entries; not an exhaustive quotation concordancearchival indexOpen index ↗

The correspondence ledger

Search the public record by coordinate.

Search covers subjects, venue labels and editorial topics. The page republishes metadata and tightly limited excerpts; every result links to the complete archival text and original location where available.

Search results

583 records

Satoshi public correspondence records

  1. REC 001

    Bitcoin: A Peer-to-Peer Electronic Cash System

    30 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designproof of worktransactionscryptocurrencynodes
  2. REC 002

    Bitcoin P2P e-cash paper

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdouble spendingminingnodesprivacy
  3. REC 003

    Bitcoin P2P e-cash paper

    3 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdouble spendingnodesscalabilitytransactions
  4. REC 004

    Bitcoin P2P e-cash paper

    4 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designminingnodessecurity
  5. REC 005

    Bitcoin P2P e-cash paper

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designnodesprivacymotivesp2p networks
  6. REC 006

    Bitcoin P2P e-cash paper

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsdifficultyminingnodes
  7. REC 007

    Bitcoin P2P e-cash paper

    6 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdouble spendingminingnodesproof of work
  8. REC 008

    Bitcoin P2P e-cash paper

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designminingnodesproof of workreleases
  9. REC 009

    Bitcoin P2P e-cash paper

    4 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designnodesproof of worktransactions
  10. REC 010

    Bitcoin P2P e-cash paper

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsfeesnodesproof of work
  11. REC 011

    Bitcoin P2P e-cash paper

    6 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdifficultydouble spendingfeesmining
  12. REC 012

    Bitcoin P2P e-cash paper

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdifficultyfeesminingnodes
  13. REC 013

    Bitcoin P2P e-cash paper

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdouble spendingminingnodestransactions
  14. REC 014

    Bitcoin P2P e-cash paper

    6 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designbitcoin economicsdouble spendingfees
  15. REC 015

    Bitcoin P2P e-cash paper

    3 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designbitcoin economicsdouble spendingmining
  16. REC 016

    Bitcoin P2P e-cash paper

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designnodesreleasesscalabilitytransactions
  17. REC 018

    Bitcoin v0.1 released

    5 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designbitcoin economicsdifficultydouble spending
  18. REC 019

    [bitcoin-list] Bitcoin v0.1.2 now available

    Bitcoin v0.1.2 is now available for download. See [link] for the download link. All the problems I've been…
    bitcoin designnodesreleasestransactions
  19. REC 020

    [bitcoin-list] Bitcoin v0.1 Alpha release notes

    Release notes for Bitcoin v0.1 Alpha Bitcoin is a new electronic cash system that uses a peer-to-peer network…
    addressesbitcoin designbitcoin economicsdifficultydouble spending
  20. REC 021

    [bitcoin-list] Bitcoin v0.1.3

    It looks like we're through with the worst of the Internet connection issues. 0.1.3 fixed a problem where…
    bitcoin designminingnodesreleases
  21. REC 022

    Bitcoin v0.1 released

    4 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designbitcoin economicsfeesproof of work
  22. REC 023

    Re: [bitcoin-list] Bitcoin v0.1 released

    I would be surprised if 10 years from now we're not using electronic currency in some way, now…
    addressesbitcoin designbitcoin economicsfeesproof of work
  23. REC 024

    Bitcoin v0.1 released

    Hal Finney wrote: Another factor that would mitigate spam if POW tokens have value: there would be a…
    bitcoin designbitcoin economicsprivacyreleasessecurity
  24. REC 025

    Re: [bitcoin-list] Problems

    From: Nicholas Bohm 2009-01-25 10:17 What's the problem you're having? If you send me your debug.log file directly…
    bitcoin designtransactions
  25. REC 026

    [bitcoin-list] Bitcoin v0.1.5 released

    Version 0.1.5 is now available. It includes the fix for the problem Nicholas had, checking for disk full…
    addressesbitcoin designfeesminingnodes
  26. REC 027

    Bitcoin open source implementation of P2P currency

    8 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designbitcoin economicsdouble spendingfees
  27. REC 028

    [p2p-research] Bitcoin open source implementation of P2P currency

    I've developed a new open source P2P e-cash system called Bitcoin. It's completely decentralized, with no central server…
    addressesbitcoin designbitcoin economicsdouble spendingfees
  28. REC 029

    [p2p-research] Bitcoin open source implementation of P2P currency

    Martien van Steenbergen wrote: </i>><i> His concept makes sure money is anonymous unless it is compromised, i.e. </i>><i>…
    bitcoin designbitcoin economicsdouble spendingnodesprivacy
  29. REC 030

    [p2p-research] Bitcoin open source implementation of P2P currency

    Martien van Steenbergen wrote: > Would love to also see support for not having to supply and >…
    bitcoin designbitcoin economicsnodestransactions
  30. REC 031

    [p2p-research] Bitcoin open source implementation of P2P currency

    Michel Bauwens wrote: </i>><i> able to use it in real life? </i> It's fully operational and the network…
    addressesbitcoin designbitcoin economicsnodesreleases
  31. REC 032

    [p2p-research] Bitcoin P2P e-currency v0.1 released

    Announcing the release of Bitcoin, a new open source peer-to-peer electronic cash system that's completely decentralized, with no…
    addressesbitcoin designbitcoin economicsdifficultydouble spending
  32. REC 033

    Bitcoin open source implementation of P2P currency

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicscryptocurrency
  33. REC 034

    Bitcoin open source implementation of P2P currency

    4 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsdifficultyfeesmining
  34. REC 035

    Re: [bitcoin-list] Bitcoin v0.1.5 released

    The next thing for v0.1.6 is to take advantage of multiple processors to generate blocks. Currently it only…
    bitcoin designminingreleases
  35. REC 036

    Re: [bitcoin-list] Bitcoin v0.1.5 released

    Hal Finney wrote: The current version will work fine. They'll each connect over the Internet, while incoming connections…
    addressesbitcoin designnodesreleasesscalability
  36. REC 037

    Re: [bitcoin-list] Does Bitcoin Crash in Windows?

    Liberty Standard wrote: I haven't had any reports of crashes in v0.1.5. It's been rock solid for me…
    bitcoin designreleases
  37. REC 038

    Welcome to the new Bitcoin forum!

    Welcome to the new Bitcoin forum! The old forum can still be reached here: [link] I'll repost some…
    bitcoin design
  38. REC 041

    Re: Repost: Bitcoin Maturation

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designminingnodesproof of worktransactions
  39. REC 042

    Re: Repost: Request: Make this anonymous?

    There will be a proxy setting in version 0.2 so you can connect through TOR. I've done a…
    nodesprivacyreleases
  40. REC 044

    Re: Repost: How anonymous are bitcoins?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designnodesprivacyreleases
  41. REC 047

    [OLD THREAD] Bitcoin version 0.2 development status

    We've been working hard on improvements for the next version release. Martti (sirius-m) added some nice features to…
    bitcoin designminingnodesreleases
  42. REC 048

    Re: A few suggestions

    Helpful suggestions, thanks. That's a good idea. The side accepting the connection just needs to withhold from sending…
    nodesprivacytransactions
  43. REC 049

    Re: A few suggestions

    That's a good approach for mobile. Programmatic API used by PHP (any language) to present a web UI…
    bitcoin designnodesreleases
  44. REC 050

    Re: Questions about Bitcoin

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designbitcoin economicsnodesprivacy
  45. REC 051

    Re: Questions about Bitcoin

    That's true, with the send-to-IP option, you are sending to whoever answers that IP. Sending to a bitcoin…
    addressesbitcoin designtransactions
  46. REC 052

    Re: A few suggestions

    Right, the SVN has the almost-release-candidate 0.2 source, which can also be built and run on Linux. It…
    addressesbitcoin designminingnodesprivacy
  47. REC 053

    Re: A few suggestions

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    miningnodes
  48. REC 054

    Re: A few suggestions

    Mac support would be nice. wxWidgets really pays off for cross platform. Please don't try PPC. PPC is…
    bitcoin designnodesscalability
  49. REC 055

    Re: A few suggestions

    There would be a command line switch at runtime to tell it to run without UI. All it…
    bitcoin economicsnodestransactions
  50. REC 056

    Re: A few suggestions

    It looks like the implicit conversion from std::string to wxString isn't working. That's used everywhere, the conversion needs…
    releases
  51. REC 057

    Re: A few suggestions

    Then it must be something you're doing differently with building or configuring wxWidgets. What options did you use…
    releases
  52. REC 058

    Bitcoin 0.2 released!

    Bitcoin version 0.2 is here! Download links: [link] [link] [link] New Features Martti Malmi - Minimize to system…
    bitcoin designminingprivacyreleases
  53. REC 059

    [bitcoin-list] Bitcoin 0.2 released

    Bitcoin 0.2 is here! Download (Windows, and now Linux version available) [link] New Features Martti Malmi - Minimize…
    bitcoin designminingprivacyreleases
  54. REC 062

    Re: Is my second Transaction working correctly? +Transfer Question

    The transfer is immediate if you send by IP address. If you send by bitcoin address and the…
    addressesbitcoin designnodestransactions
  55. REC 064

    Re: Number of connections?

    Coins generate at the same speed with any number of connections >= 1. More connections just add redundancy.…
    miningnodes
  56. REC 066

    Re: Bitcoin crash when sending coins

    That is what happens if you copy wallet files around. If you copy your wallet file to a…
    addressesbitcoin designtransactions
  57. REC 067

    Re: A newb's test - anyone want to buy a picture for $1?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designnodestransactions
  58. REC 068

    Re: Blocks never stop generating?

    Where it says "# blocks" in the status column I'm changing it to say "# confirmations". That might…
    miningtransactions
  59. REC 069

    Re: Bitcoin crash when sending coins

    The resync idea would go through your wallet and check it against the block index to find any…
    addressesbitcoin designtransactions
  60. REC 070

    Re: Payment server

    That's the right way to do it as riX says. The software can generate a new bitcoin address…
    addressesbitcoin designminingtransactions
  61. REC 071

    Re: A newb's test - anyone want to buy a picture for $1?

    The recommended ways to do a payment for an order: 1) The merchant has a static IP, the…
    addressesbitcoin designnodesscalabilitytransactions
  62. REC 073

    Re: Bitcoin crash when sending coins

    I uploaded this fix to the SVN. It watches for spent coins and updates your wallet on load…
    addressesbitcoin designreleasestransactions
  63. REC 075

    Re: Questions about Addresses

    Port forwarding forwards a port to one computer. It tells the router which computer handles connections to that…
    addressesbitcoin designbitcoin economicsnodestransactions
  64. REC 076

    Re: TOR and I2P

    When using proxy port 9050, it will only make one attempt to connect to IRC, then give up,…
    addressesbitcoin designnodesprivacy
  65. REC 077

    Proof-of-work difficulty increasing

    We had our first automatic adjustment of the proof-of-work difficulty on 30 Dec 2009. The minimum difficulty is…
    bitcoin economicsdifficultyminingnodesprivacy
  66. REC 078

    Re: Questions about Addresses

    That's not possible. You've handed control of the money over to the recipient's keypair. Only that key can…
    security
  67. REC 079

    Re: Repost: Request: Make this anonymous?

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designnodesprivacytransactions
  68. REC 080

    Re: How divisible are bitcoins and other market/economic questions

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin economicsbitcoin design
  69. REC 081

    Re: Make your "we accept Bitcoin" logo

    No, sorry. I've been meaning to redo it. The largest icon that still looks good is the 20x20…
    bitcoin designreleasesscalability
  70. REC 082

    Bitcoin client and website translation

    Thank you for the offer to help translate. That is probably the best way you could help. I…
    bitcoin designminingreleases
  71. REC 083

    Bitcoin client and website translation

    It's much easier to have a single binary and multiple .mo files. It's too much maintenance work to…
    bitcoin designreleases
  72. REC 084

    Re: Simple to implement feature requests

    There are command line options: bitcoin -addnode=1.2.3.4 to tell bitcoin about a node to connect to bitcoin -connect=1.2.3.4…
    bitcoin designnodesprivacy
  73. REC 086

    Re: What's with this odd generation?

    There's a small transaction fee for very large transactions. The node that generates the block that contains the…
    addressesfeesminingnodestransactions
  74. REC 087

    Re: DEB Package?

    Am I missing something? Is there something wrong with the 32-bit linux precompiled binary on bitcoin.org? The bitcoin…
    bitcoin designreleases
  75. REC 088

    Re: Repost: Request: Make this anonymous?

    True, sending by IP through Tor trades one problem for another. The Tor exit node can see the…
    addressesbitcoin designnodesprivacytransactions
  76. REC 090

    Re: What's with this odd generation?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    feesminingnodestransactions
  77. REC 091

    Re: What's with this odd generation?

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    feesminingnodestransactionsbitcoin economics
  78. REC 092

    Re: Proof-of-work difficulty increasing

    14/02/2010 0000000065465700000000000000000000000000000000000000000000000000 2009 1.00 30/12/2009 1.18 +18% 11/01/2010 1.31 +11% 25/01/2010 1.34 +2% 04/02/2010 1.82 +36% 14/02/2010 2.53…
    difficultyminingnodesproof of work
  79. REC 093

    Re: Setting up multiple bitcoin machines behind NAT

    Right now there isn't a port number setting to do that. It's a feature yet to be implemented.…
    bitcoin designnodesscalability
  80. REC 094

    Re: Proof-of-work difficulty increasing

    I thought about that but there wasn't a practical way to do smaller increments. The frequency of block…
    difficultyminingnodesproof of worktransactions
  81. REC 095

    Re: Proof-of-work difficulty increasing

    2 seconds of latency in both directions should reduce your generation success by less than 1%. Probably OK,…
    bitcoin designdifficultyminingnodesproof of work
  82. REC 096

    Re: Bitcoin client and website translation

    I updated the SVN with changes to support translation. Translatable strings are all enclosed in _(""), and we're…
    bitcoin designreleases
  83. REC 097

    Re: Number of connections

    Nodes stop trying to initiate connections once they have 15. If you can accept incoming connections, then you…
    bitcoin designdifficultyminingnodesprivacy
  84. REC 098

    Post your static IP

    It would be nice to have a list of static IPs for new users to send test donations…
    addressesbitcoin designnodestransactions
  85. REC 099

    Re: Current Bitcoin economic model is unsustainable

    3 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsdifficultyminingeconomics
  86. REC 100

    UI improvements

    Uploaded some UI changes to SVN as version 0.2.5. Instead of View->Show Generated, we now have tabs: -…
    addressesbitcoin designminingreleasestransactions
  87. REC 101

    Re: generation slowed down dramatically

    Just a random streak of bad luck. It looks steady to me. Competition doesn't have an effect until…
    difficultymining
  88. REC 102

    Re: UI improvements

    There are now "Sending" and "Receiving" tabs in the Address Book. Your addresses are referred to as "receiving…
    addressesreleasestransactions
  89. REC 103

    Re: Bitcoin Address Collisions

    There's a separate public/private keypair for every bitcoin address. You don't have a single private key that unlocks…
    addressesbitcoin designminingnodesprivacy
  90. REC 105

    Command Line and JSON-RPC

    Version 0.2.6 on SVN can now run as a daemon and be controlled by command line or JSON-RPC.…
    bitcoin designminingnodesreleases
  91. REC 106

    Re: Bitcoin Address Collisions

    No, each generated transaction uses a new, single-use address. Nothing uses the address in the main window, it's…
    addressesbitcoin designminingtransactions
  92. REC 107

    Re: URI-scheme for bitcoin

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designtransactions
  93. REC 108

    Re: Command Line and JSON-RPC

    How much "dealing with" does GTK actually require? Is it just a matter of "sudo apt-get install libgtk2.0-0"…
    bitcoin designreleases
  94. REC 110

    Re: Make your "we accept Bitcoin" logo

    If you GPL stuff, I have to avoid using it. Nothing against GPL per-se, but Bitcoin is an…
    bitcoin design
  95. REC 112

    Re: Proof-of-work difficulty increasing

    The automatic adjustment happened earlier today. 24/02/2010 0000000043b3e500000000000000000000000000000000000000000000000000 24/02/2010 3.78 +49% I updated the first post.
    difficultyproof of work
  96. REC 114

    Re: Command Line and JSON-RPC

    OK, I made a build target bitcoind that only links wxBase and does not link GTK. Version 0.2.7…
    feesnodesreleases
  97. REC 115

    Re: Proof-of-work difficulty increasing

    The formula is based on the time it takes to generate 2016 blocks. The difficulty is multiplied by…
    difficultyminingproof of work
  98. REC 116

    Re: Command Line and JSON-RPC

    wx/clipbrd.h isn't used, move it inside the #if wxUSE_GUI. Updated headers.h on SVN. Sorry, I linked to wxbase…
    releases
  99. REC 117

    Re: New icon/logo

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    feesnodesreleasesbitcoin design
  100. REC 118

    Re: Command Line and JSON-RPC

    Are you using wxWidgets 2.9.0? I don't recommend using anything other than 2.9.0. It looks like they've got…
    bitcoin design
  101. REC 120

    Re: wxWidgets 2.9.0

    In the Windows world, "unicode" means UTF-16 (wchar). 2.8 has two build variations, ANSI and UTF-16 (unicode). The…
    releases
  102. REC 122

    Re: Money Transfer Regulations

    When there's enough scale, maybe there can be an exchange site that doesn't do transfers, just matches up…
    bitcoin designscalabilitytransactions
  103. REC 124

    Re: bitcoin auto-renice-ing

    It sets different priorities for each thread. The generate threads run at PRIO_MIN. The other threads rarely take…
    bitcoin designbitcoin economicsmining
  104. REC 125

    Idea for file hosting and proxy services

    When you want to upload an image to embed in a forum post, there are services like imageshack,…
    feesprivacyscalabilitytransactions
  105. REC 126

    Re: On IRC bootstrapping

    Thanks soultcer for talking with the Freenode staffer. Good to know it's OK at the current size, and…
    bitcoin designnodesprivacyreleases
  106. REC 127

    Re: Idea for file hosting service

    That's a great idea. There's a thriving business in those services, but I've always thought the standard payment…
    privacytransactions
  107. REC 128

    Re: who is bitcoin.com

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsprivacygeneral
  108. REC 129

    Re: Exchange Methods

    LR and Pecunix have many established exchanges to paper currencies by various payment methods, and a number of…
    bitcoin designbitcoin economicsprivacytransactions
  109. REC 130

    Re: Idea for file hosting and proxy services

    Title changed. It helps that we have someone with actual experience running a proxy service. Do you think…
    general
  110. REC 131

    Re: Idea for file hosting and proxy services

    Mihalism Multi Host is a popular open source PHP file hosting server. It's geared toward image hosting, but…
    bitcoin designbitcoin economicsminingscalabilitytransactions
  111. REC 132

    Re: Could the bitcoin network be destroyed by someone generating endless bitcoin add

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designminingnodes
  112. REC 133

    Re: For a website taking payments with bitcoins, better: IP or bitcoin addresses?

    That's a good idea. At the very least a warning dialog explaining that it'll connect to the IP…
    bitcoin designtransactions
  113. REC 134

    Re: URI-scheme for bitcoin

    There you go, we could easily do it the same way, like: [link] <bitcoinaddress>;amount=<amount> Bitcoin can answer port…
    addressesbitcoin designtransactions
  114. REC 136

    Re: removing bitcoin addresses

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designminingtransactions
  115. REC 137

    Re: Setting up multiple bitcoin machines behind NAT

    At the moment, it always assumes the incoming port is 8333, so it would tell other bitcoin nodes…
    bitcoin designnodes
  116. REC 138

    Re: Is there a way to automate bitcoin payments for a website?

    A little late, but in case anyone else has the same issue. The compile dump had 2 warnings…
    bitcoin designreleasestransactions
  117. REC 139

    Re: Ummmm... where did my bitcoins go?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designminingnodesreleasestransactions
  118. REC 141

    JSON-RPC programming tips using labels

    I added label related functions to help with managing multiple addresses per user. New or renamed functions are:…
    addressesbitcoin economicstransactions
  119. REC 142

    Re: Tracing a coin's lineage

    This is on my list. I will soon make the "Your Bitcoin Address:" window automatically change whenever you…
    addressesbitcoin designreleasestransactions
  120. REC 143

    Re: CLI bitcoin generation

    Yeah, that actually is what it is. getallreceived 0 should do what you want. (now it's renamed to…
    addressesbitcoin designminingtransactions
  121. REC 145

    Re: Website translations

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designreleases
  122. REC 146

    Re: Odd amount of generated coins

    In the SVN version, if a transaction requires a transaction fee, it says "This transaction is over the…
    feesminingnodesreleasestransactions
  123. REC 148

    Re: Hostnames instead of IP Addresses

    The current sending by IP is not very useful: it connects to the IP, so you'd like to…
    addressesbitcoin designminingnodesprivacy
  124. REC 149

    Re: Proof-of-work difficulty increasing

    That's a good idea. I'm not sure where exactly to fit that in, but it could certainly calculate…
    addressesdifficultyminingnodesproof of work
  125. REC 151

    Re: On IRC bootstrapping

    Bitcoin has its own distributed address directory using the "addr" message. It's about time we coded in a…
    addressesbitcoin designnodes
  126. REC 152

    Re: Hostnames instead of IP Addresses

    SirArthur has a good point about the normal online merchant case, which is what the send-by-IP option is…
    addressesbitcoin designprivacytransactions
  127. REC 153

    Re: Dealing with SHA-256 Collisions

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    releasessecurityencryption
  128. REC 154

    Re: Technical clarifications

    3) Nothing, if sending by bitcoin address 5) It is decentralised. After you have connected to the network…
    addressesbitcoin designnodestransactions
  129. REC 156

    Re: What is the incentive to collect transactions?

    The premise is false. Adding more transactions to the block you're working on does NOT slow down your…
    miningnodestransactions
  130. REC 157

    Re: URI-scheme for bitcoin

    [link] or [link] <bitcoinaddress><separatorchar>1.2.3.4&amount=200.00 But as long as the link is already doing the typing for you, I…
    addressesbitcoin designtransactions
  131. REC 158

    Re: Website translations

    Thanks DataWraith! The German translation is uploaded to SVN. This is great, we've already got 3 major languages.
    releases
  132. REC 160

    Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designnodesreleasestransactions
  133. REC 161

    Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designfeesnodesreleasestransactions
  134. REC 163

    Re: Get 5 free bitcoins from freebitcoins.appspot.com

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designminingtransactionsgeneral
  135. REC 164

    Re: Bitcoin in Ubuntu 10.04

    This is now fixed in the SVN version. 1) Menu bar default color. 2) Balance bar not a…
    addressesbitcoin designprivacyreleases
  136. REC 165

    Re: Dying bitcoins

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    miningbitcoin economics
  137. REC 166

    Re: Proof-of-work difficulty increasing

    I integrated the hashmeter idea into the SVN version. It displays khash/s in the left section of the…
    bitcoin designdifficultyminingproof of workreleases
  138. REC 167

    Re: Bitcoin in Ubuntu 10.04

    On Ubuntu 10.04 it wouldn't remove the taskbar button cleanly, so I made it leave it there. But…
    bitcoin designreleases
  139. REC 168

    0.3 almost ready -- please test the Mac version!

    I finished everything on my list to do for version 0.3. The code on SVN is about ready…
    releases
  140. REC 169

    Re: How fast do the fastest computers generate bitcoins?

    I've noticed that hashing performance doesn't vary as much between CPUs as you'd expect. Compared to an old…
    miningreleases
  141. REC 171

    Re: Proof-of-work difficulty increasing

    Agree. Certainly too trivial to clutter the user's attention with. I changed it to every 30 minutes. If…
    difficultyproof of work
  142. REC 175

    Re: 0.3 almost ready

    davidonpda, were you also running laszlo's build previously? Check if the "%appdata%" directory exists, and "%appdata%\bitcoin" Try: rename…
    bitcoin designreleases
  143. REC 176

    Re: 0.3 almost ready

    You figured it out faster than I could post a reply. It looks like laszlo's build of Berkeley…
    addressesbitcoin designminingreleasestransactions
  144. REC 177

    Re: 0.3 almost ready

    Laszlo figured out that enabling some more optimisation increased performance about 20%, so 0.3 hashes 20% faster than…
    releases
  145. REC 180

    Re: 0.3 almost ready

    Thanks virtualcoin, that's a perfect comparison. The 8% speedup from 32-bit Windows (2310k) to 32-bit Linux (2500k) is…
    releases
  146. REC 181

    Re: Bitcoin clients getting k-lined from the IRC bootstrapping channel

    We need more details about what happened MadHatter. Both 0.2 and 0.3 have a backup way of getting…
    bitcoin designnodes
  147. REC 184

    Re: Bitcoin clients getting k-lined from the IRC bootstrapping channel

    Freenode is too visible, right in the middle of where all those users and moderators are hanging out.…
    bitcoin designnodes
  148. REC 189

    Re: Building BitCoin Client completely Headless

    The linux release candidate in the "1.3 almost ready" thread contains prebuilt bitcoind.
    bitcoin designreleases
  149. REC 192

    Re: IPv6, headless client, and more

    Welcome, Harry. I hadn't thought about starting out using bitcoind without using bitcoin first. I guess for now,…
    bitcoin designfeesmining
  150. REC 195

    Re: Feature Request: Limiting Connections

    Thanks for the feedback on this. One thing we could do is lower the outbound connections from 15…
    feesnodesreleases
  151. REC 201

    Re: Slashdot Submission for 1.0

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin economicsprivacyreleasesgeneral
  152. REC 202

    Bitcoin 0.3 released!

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsminingnodesreleases
  153. REC 204

    [bitcoin-list] Bitcoin 0.3 released!

    Announcing version 0.3 of Bitcoin, the P2P cryptocurrency! Bitcoin is a digital currency using cryptography and a distributed…
    bitcoin designbitcoin economicsminingnodesreleases
  154. REC 206

    Re: bitcoin 0.3 win64 - broken access to APPDATA if non-latin characters in username

    Thanks for finding that. We switched from ANSI in 0.2 to UTF-8 in version 0.3, so it must…
    bitcoin designreleasestransactions
  155. REC 207

    Re: Anonymity

    It's hard to imagine the Internet getting segmented airtight. It would have to be a country deliberately and…
    double spendingnodesprivacyreleasestransactions
  156. REC 208

    Re: bitcoin 0.3 win64 - broken access to APPDATA if non-latin characters in username

    I think I see where the problem is. Coincidentally, I recently coded a replacement for the function in…
    bitcoin designbitcoin economicsreleases
  157. REC 209

    Re: BTC Vulnerability? (Massive Attack against BTC system. Is it really?)

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin economicssecurityeconomics
  158. REC 210

    Re: bitcoin 0.3 win64 - broken access to APPDATA if non-latin characters in username

    I tested this with a non-lower-ASCII account name on XP and confirmed the bug, then tested that the…
    bitcoin designreleasestransactions
  159. REC 212

    Re: Major Meltdown

    True, if it happened suddenly. If it happens gradually, we can still transition to something stronger. When you…
    releasestransactions
  160. REC 213

    Re: No blocks downloaded... why?

    So that was responsible for keeping blocks from downloading? The link: "Win32 CPU Cycles vs 'Live Protection' Engines"…
    mining
  161. REC 215

    Re: stopped prodicing coins

    Thanks for making that calculator. The difficulty doubled a day or two ago, plus it's just random and…
    difficultyprivacy
  162. REC 216

    Re: Building Bitcoin 0.3

    It doesn't work with wxWidgets 2.8, it needs wxWidgets 2.9. Unfortunately, there isn't a Debian package of wxWidgets…
    bitcoin designreleases
  163. REC 217

    Re: bitcoin auto-renice-ing

    Laszlo corrected this, but unfortunately it was too late to make it into 0.3.0. There will probably be…
    bitcoin design
  164. REC 218

    Re: Stuck on 513 blocks

    This is the second time I've seen this "Live Protection" problem reported. It must be blocking the program's…
    nodestransactions
  165. REC 220

    Re: Runaway CPU usage for 64bit BitCoin (Linux Client)

    After it initially tries incorrectly to set itself to the lowest priority, the generate thread only changes its…
    bitcoin designminingnodesreleases
  166. REC 221

    Re: Warning this block was not received by any other nodes

    Microsoft Security Essentials Live Protection is blocking your communication with the network. You have connections, which tricks Bitcoin…
    bitcoin designnodessecuritytransactions
  167. REC 222

    Re: Hash/sec Throttling for Democracy

    This is a common point of confusion. There's no such thing as being 1% towards solving a block.…
    miningprivacy
  168. REC 223

    Re: Scalability

    3 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designfeesminingnodesscalability
  169. REC 224

    Re: Runaway CPU usage for 64bit BitCoin (Linux Client)

    OK, the undocumented switch "-minimizetotray" which re-enables the option. I uploaded the change to SVN.
    bitcoin designreleases
  170. REC 225

    Re: [Bitcoin 0.3.0] Runtime error

    More directly, this: [link] I will be posting release candidate of 0.3.1 with this fix shortly. Please try…
    bitcoin designreleases
  171. REC 226

    Re: Static Linux x86_64 bins for those having libcrypto troubles

    We don't even specify linking glibcxx_3.4.11, so gcc must automatically link it behind the scenes. There's probably a…
    releases
  172. REC 228

    Bitcoin 0.3.1 released

    This is a bugfix maintenance release. It is now uploaded to SourceForge. Mac OS X didn't need any…
    bitcoin designminingreleases
  173. REC 230

    Re: 0.3.1 release candidate, please test

    I don't think you have a particular problem, I think your system is laggy because you're running a…
    miningreleasestransactions
  174. REC 232

    Re: Website and software translations

    I uploaded an updated bitcoin.po for 0.3.1 attached to this message: [link] please use it if you're starting…
    bitcoin designreleases
  175. REC 234

    Re: Website and software translations

    Thanks for the Spanish and French translations! The edited and updated .po files are attached. I uploaded these…
    releases
  176. REC 235

    Re: 0.3.1 release candidate, please test

    I was not able to reproduce this. I have dual-proc, so I ran two memory hogs. Bitcoin got…
    bitcoin designminingreleases
  177. REC 238

    Re: "SetIcons(): icon bundle doesn't contain any suitable icon"

    That's surprising that we've never heard of that before now. Maybe you're the first person to ever run…
    general
  178. REC 239

    Re: Runaway CPU usage for 64bit BitCoin (Linux Client)

    The fix for the thread priority level on linux is available in the 0.3.1 release candidate here: [link]
    bitcoin designreleases
  179. REC 240

    Re: 0.3.1 release candidate, please test

    It could go either way. The Startup folder has the advantage that the end user can see it…
    bitcoin designreleases
  180. REC 241

    Re: "SetIcons(): icon bundle doesn't contain any suitable icon"

    What is "120DPI mode"? Is that an actual setting somewhere? Sounds like an obscure enough candidate. I suppose…
    general
  181. REC 242

    Re: 0.3.1 release candidate, please test

    Run it with the undocumented switch -minimizetotray and the option is available in the options menu. I don't…
    releases
  182. REC 244

    Re: "SetIcons(): icon bundle doesn't contain any suitable icon"

    That must be it then. It must be looking for a larger icon like 20x20 but we don't…
    general
  183. REC 245

    Re: Proof-of-work difficulty increasing

    The proof-of-work difficulty is currently 45.38. (see [link] ) It's about to increase again in a few hours.…
    difficultyproof of work
  184. REC 246

    Re: Assertion Failure - Ubuntu Lucid

    That's the first time I've seen this error. How many blocks do you have? (in the status bar)…
    bitcoin design
  185. REC 247

    Re: Fedora 13 libcrypto

    Please try the 0.3.1 release candidate, it should at least resolve the libcrypto dependency: [link] Let me know…
    releases
  186. REC 248

    Re: Resending transaction

    Bitcoin automatically rebroadcasts your transactions if it receives new blocks that don't contain them. It may take about…
    bitcoin designnodestransactions
  187. REC 249

    Re: 0.3.1 release candidate, please test

    Because of all the dependencies that different systems don't have. It's easier to just static link what we…
    releases
  188. REC 252

    Re: Request: expected bitcoins per day display

    Many businesses are like that. For a car salesman, when will the next customer walk in the door?…
    difficultymining
  189. REC 253

    Re: Proof-of-work difficulty increasing

    It adjusted to 181.54 a few minutes ago. Typical time to get a block is about a week…
    difficultyminingnodesproof of work
  190. REC 254

    Re: Source code documentation

    It's in init.cpp. It's a wxWidgets app, so it doesn't have a main() function. It may in a…
    addressesbitcoin designreleasestransactions
  191. REC 255

    Re: 0.3.1 release candidate, please test

    Good point. If you're going to have more than 8 LAN nodes connect to one gateway node, then…
    nodesreleasestransactions
  192. REC 256

    Re: Proof-of-work difficulty increasing

    Yes, about 20 hours. (120 conf / 6 blocks per hour = 20 hours) That's the normal length…
    difficultyproof of work
  193. REC 258

    Re: The dollar cost of bitmining energy

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    difficultymining
  194. REC 259

    Re: Website integration for bitcoin

    I've been trying to encourage someone to write and release some sample Python code showing the recommended way…
    bitcoin designreleases
  195. REC 260

    Re: Proof-of-work difficulty increasing

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    difficultyminingnodesproof of work
  196. REC 261

    Sample account system using JSON-RPC needed

    We need someone to write sample code, preferably Python or Java, showing the recommended way to use the…
    addressesbitcoin designtransactions
  197. REC 262

    Re: Bitcoin 0.3.1 released

    I uploaded windows 0.3.1 rc1 and linux 0.3.1 rc2 to SourceForge and updated the links on the homepage.…
    bitcoin designreleases
  198. REC 263

    Re: A New Currency System for the World

    0.3.1 fixes that, sets the generate threads to the lowest priority. Download links are on the homepage now.
    bitcoin economicsmining
  199. REC 264

    Re: BUG Report: Rounding glitch

    It must be a rounding error when getinfo converts to floating point to return the JSON-RPC result. The…
    bitcoin designbitcoin economics
  200. REC 265

    Re: Privacy versus Safety: handling change

    We should queue up a supply of pre-made addresses in the wallet to use when a new address…
    addressesbitcoin economicsprivacytransactions
  201. REC 266

    Re: Nenolod, the guy that wants to prove Bitcoin doesn't work.

    0.3.2 has some security safeguards to lock in the block chain up to this point and limit the…
    bitcoin designminingsecurity
  202. REC 267

    Bitcoin 0.3.2 released

    Download links available now on bitcoin.org. Everyone should upgrade to this version. - Added a simple security safeguard…
    bitcoin designminingnodesreleasesscalability
  203. REC 268

    Re: Bitcoin snack machine (fast transaction problem)

    I believe it'll be possible for a payment processing company to provide as a service the rapid distribution…
    bitcoin designdouble spendingminingnodesreleases
  204. REC 270

    Re: Bitcoin 0.3.2 released

    I went about 200 blocks back. The block chain was a clean straight line without branches, and there…
    bitcoin designreleases
  205. REC 271

    Re: Source code documentation

    I didn't realize you were going to document all the intentionally undocumented commands. They're unsupported and not intended…
    general
  206. REC 273

    Re: Bitcoin snack machine (fast transaction problem)

    I didn't say impermeable, I said good-enough. The loss in practice would be far lower than with credit…
    bitcoin designnodestransactions
  207. REC 275

    Re: URI-scheme for bitcoin

    That's what I thought too. Now I'm hearing a report that it IS possible for javascript to do…
    bitcoin designsecurity
  208. REC 276

    Re: Bitcoin 0.3.2 released

    The change list is basically encompassed by what's listed in the first message. Everyone should upgrade to get…
    bitcoin designreleasessecurity
  209. REC 277

    JSON-RPC password

    I uploaded to SVN my changes to add a password to JSON-RPC. If you're set up to build,…
    bitcoin designminingnodesreleasessecurity
  210. REC 282

    Warning: don't use -server or bitcoind where you web browse (v0.3.2 and lower)

    Don't use the -server or -daemon switch or run bitcoind on a machine where you use a web…
    addressesreleasessecurity
  211. REC 283

    Re: JSON-RPC password

    So you drop a settings file in the ~/.bitcoin directory, that sounds better. In the "no password is…
    bitcoin designsecurity
  212. REC 284

    Re: They want to delete the Wikipedia article

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designgeneral
  213. REC 285

    Re: JSON-RPC password

    Still need to know what's the most typical settings file format on Linux. Is there a standard file…
    bitcoin designbitcoin economicssecurity
  214. REC 286

    Re: JSON-RPC password

    I was researching config file formats, here's a comparison. YAML is massive. I'm not sure there's a lightweight…
    bitcoin economicsfeesreleasessecurity
  215. REC 287

    Re: JSON-RPC password

    Thanks for that survey! I find "key value" a little unnatural. There ought to be a more definite…
    bitcoin designbitcoin economicsprivacysecurity
  216. REC 288

    Re: JSON-RPC password

    boost::program_options has the same "key=value" format. Gavin pointed out we can use it in a simple way as…
    bitcoin economicssecurity
  217. REC 289

    Re: JSON-RPC password

    In many of the contexts of this RPC stuff, you can print to the console with fprintf(stdout, like…
    bitcoin designsecurity
  218. REC 291

    Re: JSON-RPC password

    Gavin's changes look good. I think everything is complete. Here's a test build, please test it! [link] [link]
    releasessecurity
  219. REC 292

    Re: bitcoind not responding to RPC

    If I recall correctly, 500 is the prescribed status code for JSON-RPC error responses. There is still a…
    addressesbitcoin design
  220. REC 293

    Faster initial block download (5x faster)

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesreleasessecuritytransactionsbitcoin design
  221. REC 298

    Re: Warning: don't use -server or bitcoind on a machine where you web browse

    The JSON-RPC HTTP authentication feature in 0.3.3 solves this problem.
    general
  222. REC 299

    Version 0.3.2.5 -- please test!

    Please test 0.3.2.5 in preparation for the 0.3.3 release! This build is looking good and should be the…
    releases
  223. REC 300

    Re: Reading/Writing Blocks and FLATDATA

    FLATDATA was a workaround to serialize a fixed field length array. There was a cleaner way to make…
    general
  224. REC 303

    Bitcoin 0.3.3 released -- PLEASE UPGRADE

    Please upgrade to 0.3.3! Important security improvements were made in 0.3.2 and 0.3.3. New features: - Gavin Andresen's…
    bitcoin designreleasessecurity
  225. REC 305

    Re: Stealing Coins

    Red, thanks for telling me privately first! Please go ahead and post it (and relieve the suspense for…
    addressesbitcoin designsecuritytransactions
  226. REC 306

    Re: Stealing Coins

    You would still have to sign it with public key 654321. You need to find a collision using…
    addressesbitcoin designminingtransactions
  227. REC 307

    Re: Stealing Coins

    2^80 is if you can use a birthday attack. You can't use a birthday attack for this, so…
    bitcoin designbitcoin economicsdifficultysecuritytransactions
  228. REC 311

    Re: md5?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesbitcoin designgeneral
  229. REC 312

    Re: Stealing Coins

    Sorry, actually it's ECDSA (Elliptic Curve Digital Signature Algorithm) not RSA. I shouldn't have said "prime numbers". ECDSA…
    mining
  230. REC 313

    bitcoind without wxWidgets

    I replaced the last of the few wxBase dependencies in bitcoind. bitcoind now compiles without wxWidgets or wxBase…
    releases
  231. REC 316

    Re: Proof-of-work difficulty increasing

    New difficulty factor 244.213223092 +35% I updated the first post. date, difficulty factor, % change 2009 1.00 30/12/2009…
    difficultyprivacyproof of work
  232. REC 317

    Re: Bitcoin x86 for Windows

    I added a subset of the Crypto++ 5.6.0 library to the SVN. I stripped it down to just…
    bitcoin designminingreleases
  233. REC 319

    Re: Having problems specifing -datadir

    It was able to reproduce this. The database doesn't like the relative path. "bitcoind -datadir=./subdir getinfo" works against…
    general
  234. REC 320

    Re: Build error SVN r115 on my Mac: workaround

    Was that the only thing I broke in the OSX build?! Does it actually work after just that…
    releases
  235. REC 322

    Re: Scalability and transaction rate

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designminingnodesscalabilitytransactions
  236. REC 324

    *** ALERT *** Upgrade to 0.3.6

    Please upgrade to 0.3.6 ASAP! We fixed an implementation bug where it was possible that bogus transactions could…
    bitcoin designminingnodesreleasestransactions
  237. REC 326

    Re: *** ALERT *** version 0.3.6

    SVN is updated with version 0.3.6. Uploading Windows build of 0.3.6 to Sourceforge now, then will rebuild linux.
    releases
  238. REC 327

    Re: *** ALERT *** Upgrade to 0.3.6 ASAP!

    0.3.6 Linux build is back to the old makefile.unix. It static links libjpeg so that shouldn't be a…
    releases
  239. REC 328

    Re: *** ALERT *** Upgrade to 0.3.6 ASAP!

    "./bitcoin: /lib64/libc.so.6: version `GLIBC_2.11' not found (required by ./bitcoin)" isn't a new problem that started with 0.3.6 is…
    bitcoin designreleases
  240. REC 329

    Re: Implementation bug prior to 0.3.6

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designsecurity
  241. REC 330

    Re: Transaction disappeared in the void...

    If the transaction didn't go out immediately at first, like if you weren't connected at the time, it…
    releasestransactions
  242. REC 332

    Re: *** ALERT *** Upgrade to 0.3.6 ASAP!

    We don't really need pre-compiled header. It only makes it compile slightly faster. I think I'll just get…
    releases
  243. REC 333

    [bitcoin-list] Alert: upgrade to bitcoin 0.3.6

    Please upgrade to 0.3.6 ASAP to get an important bugfix. See the bitcoin.org homepage for download links.
    bitcoin designreleases
  244. REC 334

    Re: Bug: "Immature" coins lost in wallet.dat during transaction

    I don't get how it let you send if it was not matured. Your balance would have been…
    addressestransactions
  245. REC 335

    Re: [PATCH] implement 'listtransactions'

    What are you needing to use listtransactions for? The reason I didn't implement listtransactions is I want to…
    releasestransactions
  246. REC 336

    Re: *** ALERT *** Upgrade to 0.3.6 ASAP!

    I can't understand why you're having so much pain. I just followed the instructions in build-unix.txt. I made…
    releases
  247. REC 337

    Re: *** ALERT *** Upgrade to 0.3.6 ASAP!

    Except that wouldn't work for boost 1.40+ (on Ubuntu 10.04), where you need to get libboost-all-dev. Seems they…
    bitcoin designreleases
  248. REC 338

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    That's amazing... So are you saying you use 128-bit registers to SIMD four 32-bit data at once? I've…
    bitcoin economics
  249. REC 339

    Webpage idea: Next predicted difficulty change

    It would be neat if someone had a page (like that handy calculator at [link] ) that projects…
    difficultyprivacy
  250. REC 341

    Re: Linux version => No GUI after upgrade. WTF?

    Did it print anything to the console? Are you sure you didn't run "bitcoind"? Try version 0.3.7.
    releases
  251. REC 342

    Re: Mac Client Problems Outlined...

    "Minimize to the tray instead of the taskbar" & "Minimize to the tray on close" must not be…
    bitcoin designreleases
  252. REC 344

    Re: Protocol Buffers for Bitcoin

    The reason I didn't use protocol buffers or boost serialization is because they looked too complex to make…
    bitcoin designnodesreleasestransactions
  253. REC 346

    Re: Bitcoind x86 binary for CentOS

    I urge you not to use BDB 4.8. The database/log0000* files will be incompatible if anyone uses your…
    releases
  254. REC 347

    Re: Content-Length header and 500 (was Re: Authentication, JSON RPC and Python)

    I guess we should try to support the case where there's no Content-Length parameter. I don't want to…
    general
  255. REC 348

    Re: What happens when network is split for prolonged time and reconnected?

    creighto: I agree with that idea. After a few hours, it should be possible for the client to…
    bitcoin designdouble spendingminingnodestransactions
  256. REC 349

    Please upgrade to 0.3.8!

    Version 0.3.8 adds an important security improvement. Everyone should upgrade to get this change. The new safety feature…
    miningnodesreleasessecuritytransactions
  257. REC 350

    Re: Bitcoind x86 binary for CentOS

    I'd rather you didn't make a build of the 1000 node connecting version available. It won't take very…
    nodesreleases
  258. REC 352

    Re: Building initial transaction trust through "coin ripping"

    The software is designed to support things like this. I was going to post details of the plans…
    releasestransactions
  259. REC 353

    Re: Flood attack 0.00000001 BC

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designsecuritytransactionsmicropayments
  260. REC 354

    Re: Flood attack 0.00000001 BC

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designfeesnodesscalabilitysecurity
  261. REC 356

    Re: Flood attack 0.00000001 BC

    I don't know a way to implement that. The transaction fee to the block creator uses a special…
    feesprivacysecuritytransactions
  262. REC 357

    Re: Who's the Spanish jerk draining the Faucet?

    Silently failing would look bad. Definitely needed. What rate are you thinking of? Ultimately, it's better to rate…
    general
  263. REC 358

    Re: bitcoind transaction to ip address

    It's not implemented. It turned out nobody liked that mode of transfer anyway, so it hasn't had much…
    addressestransactions
  264. REC 359

    Re: Transaction Overload Solution

    I can't think of a way to implement that. All the transaction fees would be additional transactions. What…
    feestransactions
  265. REC 360

    Re: Flood attack 0.00000001 BC

    If you're only going to have one person work on building the block, that could take days. Oh,…
    feesnodesreleasessecuritytransactions
  266. REC 361

    Re: A proposal for a semi-automated Escrow mechanism

    A transaction can be written that requires two signatures to spend it next. You write a payment that…
    privacyreleasestransactions
  267. REC 363

    Re: Bitcoin minting is thermodynamically perverse

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsdouble spendingminingnodes
  268. REC 364

    Re: A proposal for a semi-automated Escrow mechanism

    Really? Do you think people won't be able to understand the benefit? (If your response is an argument…
    transactions
  269. REC 366

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    Sorry about that. CRITICAL_BLOCK isn't perfect. You have to be careful not to break or continue out of…
    general
  270. REC 367

    Re: bitcoin generation broken in 0.3.8?

    I found that SSE2 only added a slight 2% speedup, which didn't seem worth the incompatibility. I was…
    bitcoin designminingreleases
  271. REC 368

    Version 0.3.8.1 update for Linux 64-bit

    When we switched to Crypto++ 5.6.0 SHA-256 in version 0.3.6, generation got broken on the Linux 64-bit build.…
    miningreleases
  272. REC 369

    Re: What could be the transition plan to Y2038 compliant Bitcoin?

    unsigned int is good until 2106. Surely the network will have to be totally revamped at least once…
    bitcoin designnodes
  273. REC 370

    Re: bitcoin generation broken in 0.3.8? (64-bit)

    I uploaded 0.3.8.1 for Linux with re-built 64-bit. I ran a difficulty 1 test with it and it…
    bitcoin designdifficultymining
  274. REC 371

    Re: Version 0.3.8.1 update for Linux 64-bit

    That's a good point, I believe you could run with generation off if you don't have SSE2. How…
    miningreleases
  275. REC 373

    Re: Bitcoin minting is thermodynamically perverse

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designmining
  276. REC 374

    Re: Version 0.3.8.1 update for Linux 64-bit

    SVN rev 128: disable SSE2 on 32-bit. This may only disable it for MSVC and GCC. Other compilers…
    releases
  277. REC 375

    Re: Not a suggestion

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdouble spendingnodestransactionsprivacy
  278. REC 376

    Re: Escrow

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    releasestransactionsgeneral
  279. REC 377

    Re: Compile error in SVN r127

    Updated SVN. Thanks. There's little hope of not repeatedly stumbling over that in the future. It doesn't break…
    releases
  280. REC 378

    Re: Not a suggestion

    Still thinking this idea through... The only job the network needs to do is to tell whether a…
    bitcoin designbitcoin economicsminingnodesprivacy
  281. REC 379

    Re: Lost large number of bitcoins

    You can get away with backing up without stopping the client if you don't do anything or receive…
    addressesbitcoin designtransactions
  282. REC 380

    Re: Where is the separate discussion devoted to possible Bitcoin weaknesses.

    It doesn't have to be such a breaking change. New nodes could accept old transactions for a long…
    bitcoin designfeesnodesproof of workreleases
  283. REC 381

    Re: Flood attack 0.00000001 BC

    It would be nice to keep the blk*.dat files small as long as we can. The eventual solution…
    bitcoin designfeesnodesscalabilitysecurity
  284. REC 383

    Re: Not a suggestion

    Are you back to talking about the existing Bitcoin system here? I was talking about in the hypothetical…
    bitcoin designminingnodestransactions
  285. REC 384

    Re: BSD detection

    This is in SVN rev 130. Check that it compiles right. Code: #if (defined(__unix__) || defined(unix)) && !defined(USG)…
    releases
  286. REC 386

    Re: Bitcoin Watchdog Service

    True, there would probably be someone with a dial-up modem or satellite dish internet. Rarer would be someone…
    bitcoin designminingnodesprivacytransactions
  287. REC 388

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    That big of a difference in speed, by a factor of 4 or 6, feels like it's likely…
    feesprivacyreleases
  288. REC 389

    Re: Bugfixes in SVN rev 130

    No, that's not what it is. -paytxfee allows you to include a transaction fee with your transactions. If…
    feesreleasestransactions
  289. REC 390

    Re: Bitcoin Watchdog Service

    Which doesn't matter because you can't access sourceforge to download the software either. If you've ever been connected…
    bitcoin designnodes
  290. REC 391

    Version 0.3.9 rc1, please test

    Here's a test build if you'd like to help test before 0.3.9 is released. (or if you'd rather…
    bitcoin designreleases
  291. REC 392

    Re: Not a suggestion

    I'm not grasping your idea yet. Does it hide any information from the public network? What is the…
    addressesbitcoin designbitcoin economicsminingnodes
  292. REC 393

    Re: Proposed change to sendtoaddress API call

    It's too soon to start junking up the API for backward compatibility at all costs. Just return "<txid>".
    transactions
  293. REC 394

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    MinGW on Windows has trouble compiling it: g++ -c -mthreads -O2 -w -Wno-invalid-offsetof -Wformat -g -D__WXDEBUG__ -DWIN32 -D__WXMSW__…
    releases
  294. REC 395

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    If you haven't already, try aligning thash. It might matter. Couldn't hurt. No help from -O0, same error.…
    releases
  295. REC 396

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    Got the test working on 32-bit with MinGW GCC 4.5. Exactly 50% slower than stock with Core 2.
    general
  296. REC 397

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    MinGW GCC 4.5.0: Crypto++ doesn't work, X86_SHA256_HashBlocks() never returns I only got 4-way working with test.cpp but not…
    releases
  297. REC 398

    Re: 4 hashes parallel on SSE2 CPUs for 0.3.6

    On both MinGW GCC 4.4.1 and 4.5.0 I have it working with test.cpp but SIGSEGV when called by…
    bitcoin designreleases
  298. REC 399

    tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10

    0.3.10 has tcatm's 4-way SSE2 as an option switch. Use the switch "-4way" to turn it on. Without…
    general
  299. REC 400

    Re: Potential disaster scenario

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin economicsminingtransactions
  300. REC 403

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit 0.3.9 rc2

    I just uploaded a quick build so testers can check if I built it right. (I don't have…
    releases
  301. REC 404

    [bitcoin-list] ALERT - we are investigating a problem

    *** WARNING *** We are investigating a problem. DO NOT TRUST ANY TRANSACTIONS THAT HAPPENED AFTER 15.08.2010 17:05…
    bitcoin designtransactions
  302. REC 405

    Re: overflow bug SERIOUS

    Here's the preliminary change. Look right? I have more changes to make, this isn't all of it. Will…
    releasessecurity
  303. REC 406

    Re: overflow bug SERIOUS

    It would help if people stop generating. We will probably need to re-do a branch around the current…
    miningreleasessecurity
  304. REC 407

    Re: overflow bug SERIOUS

    Once you have an update, you could download knightmb's block chain. You'll want one that's old enough that…
    security
  305. REC 408

    Re: overflow bug SERIOUS

    Patch is uploaded to SVN rev 132! For now, recommended steps: 1) Shut down. 2) Download knightmb's blk…
    nodesreleasessecurity
  306. REC 409

    Re: overflow bug SERIOUS

    Don't update the block chain download. When you take someone's block chain download, you don't want it right…
    bitcoin designreleasessecurity
  307. REC 411

    Re: overflow bug SERIOUS

    Starting at 67000 is perfect . Yeah, at the moment you'll stop at 74638. It should start slowly…
    bitcoin designminingnodesreleasessecurity
  308. REC 413

    Version 0.3.10 - block 74638 overflow PATCH!

    Version 0.3.10 patches the block 74638 overflow bug. [link] The Linux version includes tcatm's 4-way SSE2 SHA-256 that…
    bitcoin designdouble spendingminingreleasessecurity
  309. REC 414

    Re: 0.3.10.1 Question on where block should be

    I suspect there's some difficulty receiving blocks if all the nodes you're connected to are 0.3.9 or lower.…
    difficultynodes
  310. REC 415

    Re: 0.3.10.1 Question on where block should be

    For now, can some people running 0.3.10 with static IP who can receive incoming connections post their IP?…
    nodestransactions
  311. REC 416

    Re: overflow bug SERIOUS

    Right, it will get reincorporated into the fixed chain. The transaction won't disappear, it'll still be visible on…
    miningsecuritytransactions
  312. REC 418

    Re: overflow bug SERIOUS

    1) Once more than 50% of the node power is upgraded and the good chain overtakes the bad,…
    nodesreleasessecuritytransactions
  313. REC 419

    Re: overflow bug SERIOUS

    The bad chain is also slowed down as more nodes upgrade. We've already generated 14 blocks since 74638.…
    miningnodesreleasessecurity
  314. REC 420

    Re: overflow bug SERIOUS

    On Windows, findstr /c:"version message" debug.log It looks like the bad chain was on block 74678 recently. Can't…
    difficultyreleasessecurity
  315. REC 421

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit 0.3.9 rc2

    GCC 4.3.3 doesn't support -march=amdfamk10. I get: sha256.cpp:1: error: bad value (amdfamk10) for -march= switch Hey, you may…
    bitcoin economics
  316. REC 422

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit 0.3.9 rc2

    That works. That's strange... are we sure that's the same thing? tcatm, try amdfam10 and make sure you…
    general
  317. REC 423

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10

    cpu family 6 model 26 stepping 4 is an Intel Core i7. That's a 23% speedup with -4way,…
    general
  318. REC 424

    Re: overflow bug SERIOUS

    It looks like we overtook the bad chain somewhere around 74689. 0.3.9 and lower nodes have been responding…
    double spendingnodesreleasessecurity
  319. REC 426

    Re: [PATCH] Automatic block validation

    That's a difficult approach. We need to cause a reorg, which will disconnect the invalid chain. This is…
    double spendingprivacyreleasestransactions
  320. REC 430

    Checking the block chain on load

    SVN rev 139 does a basic check of the block chain after loading. With this we wouldn't have…
    bitcoin designdouble spendingreleases
  321. REC 431

    Re: checkpointing the block chain

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designdouble spendingproof of work
  322. REC 432

    Re: overflow bug SERIOUS

    Un-upgraded nodes have the correct chain most of the time, but they are still trying to include the…
    double spendingminingnodesreleasessecurity
  323. REC 434

    Re: New screenshots to the front page?

    Definitely. The old screenshots of 0.1 are very outdated. Windows Aero is a good choice. Windows is still…
    transactions
  324. REC 435

    Re: Difficulty: More nodes active, or faster nodes?

    The performance numbers posted from a VIA C7's hardware SHA-256 weren't astronomical. Only in the 1500 khash/s range.…
    difficultynodes
  325. REC 436

    Re: Checking the block chain on load

    In the next SVN rev, I'll make it only go back to the last checkpoint at block 74000.…
    proof of workreleases
  326. REC 437

    Re: Convert Bitcoin to GTK: Yes? No? wx is better?

    wxWidgets 2.9 is their first UTF-8 version. We are UTF-8 on all platforms including Windows. The distro packages…
    bitcoin designreleases
  327. REC 438

    Re: HOWTO: Compiling Bitcoin on Ubuntu 10.04 (Karmic)

    That's a really well written walkthough. Someone should confirm if they followed it and didn't run into any…
    bitcoin designtransactions
  328. REC 439

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10

    That's the first I've heard anyone say i5 was slower. Everyone else has said 4way was faster on…
    releasestransactions
  329. REC 441

    Need a post writing up some things users should know

    I'm not sure what to call it, but we could use a post that lists these things users…
    addressesreleasessecurity
  330. REC 442

    Re: Hypothetical question on lost coins / transfers

    That's right. You don't need to be re-broadcasting your transactions for it to work. When any node disconnects…
    nodestransactions
  331. REC 443

    Re: Need a post writing up some things users should know

    The clock part will be covered in the next release (0.3.11 or higher). SVN rev 141 pops up…
    releases
  332. REC 444

    Re: 28 days without generation, i have 4200khash/s

    Search debug.log for "proof-of-work found". If you find any, then check for any errors right after that. The…
    miningproof of workreleases
  333. REC 445

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10

    Thanks for clearing that up. I read the link someone posted about AMD making that change around 2007,…
    general
  334. REC 446

    Development of alert system

    I've been working on writing the alert system. Alerts are broadcast through the network and apply to a…
    nodesreleasessecuritytransactions
  335. REC 447

    Re: integrating digital payments into p2p protocols

    Hey Zooko! I wanted to thank you for posting about Bitcoin on your blog a year or two…
    bitcoin designtransactions
  336. REC 448

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10

    This probably explains why hyperthreading increases performance with -4way. If three SSE2 units is excessive, then hyperthreading would…
    general
  337. REC 449

    Re: Development of alert system

    If you're so paranoid that you're getting hysterical over this, then surely you're paranoid enough that if a…
    security
  338. REC 451

    Re: Development of alert system

    It can't do arbitrary actions remotely. Maybe some of you are responding to other posters who suggested the…
    nodesreleasesscalabilitysecuritytransactions
  339. REC 453

    Re: Development of alert system

    WRT the alert system, who cares? The most the key can do is temporarily disable six json-rpc commands…
    miningnodesreleases
  340. REC 456

    Re: RFC: remove DB_PRIVATE flag

    Can you provide more details about what removing DB_PRIVATE does? I can't remember if I had a specific…
    nodesprivacy
  341. REC 457

    Re: Need a post writing up some things users should know

    Any backup process/procedure would just be a stopgap until there's time to properly work on coding solutions in…
    transactions
  342. REC 458

    Re: auto backing up of wallet.dat

    I started posting in the other topic but I'll repeat here, this thread seems more specific to the…
    addressesminingtransactions
  343. REC 459

    Re: Gentoo Linux Ebuild

    Try -datadir= Last time I tried $(shell /usr/bin/wx-config), there was immediate hollering about build problems with it. There…
    releases
  344. REC 461

    Re: auto backing up of wallet.dat

    I doubt there's an mmap(2) on Windows. I'd rather call an existing file copy function than make and…
    addresses
  345. REC 463

    Re: New web service: obtain dump of bitcoin block NNNN

    That's kind of interesting as an upside-down bar chart of how many blocks were produced each day. The…
    bitcoin design
  346. REC 464

    Re: Bitcoins are most like shares of common stock

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    generalbitcoin economics
  347. REC 465

    Re: Bitcoin does NOT violate Mises' Regression Theorem

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsnodesprivacyeconomics
  348. REC 466

    Version 0.3.11 with upgrade alerts

    Version 0.3.11 is now available. Changes: - Some blk*.dat checking on load - Built the -4way code with…
    miningnodesreleasessecuritytransactions
  349. REC 467

    Re: tcatm's 4-way SSE2 for Linux 32/64-bit is in 0.3.10

    The simplification is intentional. There will only be more than one thash[7]=0 in one out of 134,217,728 cases.…
    general
  350. REC 468

    Re: Version 0.3.11 with upgrade alerts

    What OS? I ran the Windows and 64-bit Linux version and checked the about dialog. The Mac version…
    releases
  351. REC 469

    Re: Big endian code problems

    The code assumes little-endian throughout and was written with the intention of never being ported to big-endian. Every…
    nodes
  352. REC 470

    Re: CryptoPP Assertion Error

    You can probably just comment out the line cryptopp/secblock.h:187 //assert(false); Let me know if it works, and watch…
    releases
  353. REC 471

    Re: Warning : Check your system ( Help me )

    Any suggestions for better text to put for this error message so the next person will be less…
    nodes
  354. REC 472

    Re: HTTP status codes from the JSON-RPC api

    This is in SVN rev 147. This is more standard, and although json-rpc 1.0 didn't specify the format…
    addressesreleases
  355. REC 475

    Re: bitcoind as daemon in OSX

    Can you build? Try changing line 78 of init.cpp from: #ifdef __WXGTK__ to: #ifndef __WXMSW__ If that works,…
    releases
  356. REC 476

    Re: Always pay transaction fee?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    feesnodestransactions
  357. REC 477

    Version 0.3.12

    Version 0.3.12 is now available. Features: - json-rpc errors return a more standard error object. (thanks to Gavin…
    nodesreleasestransactions
  358. REC 478

    Re: Always pay transaction fee?

    2 quotation entries are indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    feesnodestransactionsscalability
  359. REC 479

    Re: Version 0.3.12

    Bitcoin clients currently only create and recognize transactions that match two possible templates. Those are some quick tests…
    bitcoin designnodesreleasestransactions
  360. REC 480

    Re: Bitcoin Blogger: Is It Better To Buy Or Generate Bitcoins?

    Did you try -4way? AMD Phenom (I think 4-core) CPUs are doing about 11,000khps with -4way, about 100%…
    bitcoin designmining
  361. REC 482

    Re: Won't let me send coins because it requires a transaction fee?

    What version is the one where this happened? Release build, or built it yourself? Which operating system? Were…
    addressesbitcoin designfeesreleasestransactions
  362. REC 483

    Re: Won't let me send coins because it requires a transaction fee?

    I think I know what happened. Doubleclick on the generated transaction. It probably has a sub-0.01 transaction fee…
    feesminingtransactions
  363. REC 484

    Re: Won't let me send coins because it requires a transaction fee?

    The fix is in SVN rev 151. You will be able to send your stuck 0.01 (actually 0.01000010)…
    feesreleasestransactions
  364. REC 486

    Re: Running on a port other than 8333

    Is there a way to open BerkeleyDB exclusive? DB_PRIVATE is the worst of both worlds. DB_PRIVATE is not…
    general
  365. REC 490

    Re: Issues building bitcoin on Windows 7

    The lines it's tripping on: Code: ERROR extern map<string, string> mapAddressBook; ERROR extern CCriticalSection cs_mapAddressBook; ERROR extern vector<unsigned…
    bitcoin designprivacyreleases
  366. REC 491

    Re: Bug? /usr/bin/bitcoind ""

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin design
  367. REC 492

    Re: The case for removing IP transactions

    Probably best to disable receiving by IP unless you specifically intend to use it. This is a lot…
    addressesbitcoin designprivacyreleasestransactions
  368. REC 493

    Re: Message Encryption as a built-in feature?

    Theymos already said this... ECDSA does not support encrypting messages. Only digital signatures.
    general
  369. REC 494

    Re: Always pay transaction fee?

    I implemented this change in SVN rev 157. The reason I previously made it so high was to…
    feesminingreleasestransactions
  370. REC 495

    Internal version number

    In the next release (0.3.13), I'm going to change the format of the internal version number integer from…
    releases
  371. REC 496

    Re: Warning : Check your system ( Help me )

    I don't understand, are you under the impression that the program sets the system clock? It doesn't. We…
    nodessecurity
  372. REC 497

    Re: Porn

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designgeneral
  373. REC 498

    Re: How divisible are bitcoins - the technical side

    I would not encourage using the extra decimal places. They're only intended for future use. You are correct…
    general
  374. REC 500

    Re: How To Make a Distributed BitCoin Escrow Service

    It's not implemented yet, but the network can support a transaction that requires two signatures. It's described here:…
    bitcoin designnodestransactions
  375. REC 501

    Re: I broke my wallet, sends never confirm now.

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    addressesprivacyreleasestransactions
  376. REC 503

    0.3.13 RC1 for Windows, please test

    0.3.13 release candidate, to be released soon so please test: [link] - don't count or spend payments until…
    addressesnodesreleasestransactions
  377. REC 504

    Re: BitCoin Wikipedia page DELETED!!!

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsnodesgeneral
  378. REC 505

    Re: Prioritized transactions, and tx fees

    It ramps up the fee requirement as the block fills up: <50KB free 50KB 0.01 250KB 0.02 333KB…
    bitcoin economicsfeestransactions
  379. REC 506

    Re: Prioritized transactions, and tx fees

    True, the switch should be something more dynamic that pays per KB. It's harder to think of how…
    feestransactions
  380. REC 509

    Version 0.3.13, please upgrade

    Version 0.3.13 is now available. You should upgrade to prevent potential problems with 0/unconfirmed transactions. Note: 0.3.13 prevents…
    addressesnodesreleasestransactions
  381. REC 511

    Re: Version 0.3.13, please upgrade

    Could a few people please run this special build? It'll amnesty the dust spam transactions, which will clear…
    bitcoin designminingreleasestransactions
  382. REC 513

    Re: Version 0.3.13, please upgrade

    Code: diff -u old\main.cpp new\main.cpp --- old\main.cpp Sun Oct 03 20:57:20 2010 +++ new\main.cpp Sun Oct 03 20:57:54…
    feesreleasestransactions
  383. REC 514

    Re: Version 0.3.13, please upgrade

    Transactions aren't accepted or displayed as 0/unconfirmed until your node has a path of transactions back to the…
    addressesfeesminingnodesreleases
  384. REC 515

    Re: [PATCH] increase block size limit

    +1 theymos. Don't use this patch, it'll make you incompatible with the network, to your own detriment. We…
    nodesreleases
  385. REC 516

    Re: How to overthrow the GPU Oligarchs

    This is the point of confusion. extraNonce is not part of the block header, it is part of…
    miningproof of worktransactions
  386. REC 517

    Re: Version 0.3.13, please upgrade

    ShadowOfHarbringer, is yours faster with -4way? If it is, then I'm thinking that any AMD that supports 64-bit…
    releases
  387. REC 518

    Re: Memory leak

    You're connecting to yourself. All 21 connection attempts were to a node with version 31300 (0.3.13). Not everyone…
    nodesreleases
  388. REC 519

    Re: Version 0.3.13, please upgrade

    Make sure you keep your node online so it'll keep rebroadcasting transaction b412a0. It haven't seen it rebroadcast…
    nodesreleasestransactions
  389. REC 521

    Re: Website and software translations

    poedit does it. Either get the src directory from a release, or download it with SVN. Place your…
    bitcoin designreleases
  390. REC 522

    Re: [PATCH] increase block size limit

    It can be phased in, like: if (blocknumber > 115000) maxblocksize = largerlimit It can start being in…
    releases
  391. REC 523

    Re: Website and software translations

    poedit reorganised the file for some reason. I re-ran update from sources and it put it back in…
    double spendingreleases
  392. REC 524

    Re: I broke my wallet, sends never confirm now.

    That's going to be more of a SelectCoins thing. SVN rev 161 has a refinement to recursively determine…
    addressesprivacyreleasestransactions
  393. REC 525

    Re: Tor connections not working reliably, many seednodes offline

    Maybe you were just unlucky to have an exit node without reverse lookup. The IRC server's response doesn't…
    nodesprivacytransactions
  394. REC 526

    Re: The Niche List

    Repeating myself here, but there is open source software for that, so it would just be a matter…
    bitcoin designtransactions
  395. REC 527

    Key pool feature for safer wallet backup

    SVN rev 163 (ver 0.3.13.3) has the key pool feature. Pre-generated new keys are aged in a queue…
    addressesminingreleasestransactions
  396. REC 528

    Version 0.3.14

    Version 0.3.14 is now available [link] Changes: - Key pool feature for safer wallet backup Gavin Andresen: -…
    addressesnodesreleases
  397. REC 530

    Re: ERROR - PLEASE HELP ME!

    He was generating invalid blocks at difficulty 1.0. He must have a corrupted entry in his blk0001.dat or…
    difficultyminingsecuritytransactions
  398. REC 531

    Re: ERROR - PLEASE HELP ME!

    OK, if it really won't get past block 1698 on redownload, then we're in stranger territory. Yes, possibly…
    general
  399. REC 532

    Re: Win7 64bit since last patch Tues now crashes

    This is the important clue. I believe it's saying it crashed in that. Maybe there are other versions…
    releases
  400. REC 533

    Re: Suggestion: Allow short messages to be sent together with bitcoins ?

    ECDSA can't encrypt messages, only sign signatures. It would be unwise to have permanently recorded plaintext messages for…
    addressesbitcoin designnodes
  401. REC 534

    Re: Multiple Wallets, one computer

    I have the beginning of something like this. It's mostly like what Gavin described. Some more rpc interface:…
    addressestransactions
  402. REC 535

    Re: Multiple Wallets, one computer

    Here's some pseudocode of how you would use the account based commands. It sure makes website integration a…
    transactions
  403. REC 536

    Re: Win7 64bit since last patch Tues now crashes

    The only thing I can think of is to see if there are other versions of mingwm10.dll you…
    releases
  404. REC 537

    Re: New icon/logo

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    generalbitcoin design
  405. REC 538

    Re: Some testing that I did on the testnetwork, my findings.

    Thank you for limiting flood tests to the testnet. Version 0.3.15 combines several features to help legitimate transactions…
    feesnodesreleasessecuritytransactions
  406. REC 539

    Version 0.3.15

    Version 0.3.15 is now available. Changes: - paytxfee switch is now per KB, so it adds the correct…
    feesminingreleasestransactions
  407. REC 540

    Re: Some testing that I did on the testnetwork, my findings.

    You should use at least some priority in case a flood comes along before the next block. As…
    nodestransactions
  408. REC 541

    Re: Need OP_BLOCKNUMBER to allow "time" limited transactions

    We can't safely do OP_BLOCKNUMBER. In the event of a block chain reorg after a segmentation, transactions need…
    double spendingreleasestransactions
  409. REC 542

    Re: Transaction / spam flood attack currently under way

    I'm doing something like that. Priority is a more formalised version of the concept you're describing. Yes, like…
    feesreleasessecuritytransactions
  410. REC 543

    Re: OpenCL miner for the masses

    Thanks m0mchil for keeping up on the updates! GPU miners, please upgrade as soon as possible to shut…
    miningreleasestransactions
  411. REC 544

    New getwork

    I uploaded a redesign of m0mchil's getwork to SVN rev 189 (version 31601) m0mchil's external bitcoin miner idea…
    bitcoin designminingnodesproof of workreleases
  412. REC 546

    Re: New getwork

    getwork does the byte-reversing. midstate, data and hash1 are already big-endian, and you pass data back still big-endian,…
    miningproof of workreleases
  413. REC 547

    Re: OpenCL miner for the masses

    A revised version of getwork is now in the official client, but the miners need to be updated…
    bitcoin designminingreleases
  414. REC 548

    Re: RFC: ship block chain 1-74000 with release tarballs?

    It's not the downloading that takes the time, it's verifying and indexing it. Bandwidthwise, it's more efficient than…
    bitcoin designreleasesscalability
  415. REC 549

    Version 0.3.17

    Version 0.3.17 is now available. Changes: - new getwork, thanks m0mchil - added transaction fee setting in UI…
    feesreleasestransactions
  416. REC 550

    Re: RFC: ship block chain 1-74000 with release tarballs?

    I tested it on a slow 7 year old drive, where bandwidth and CPU were clearly not the…
    nodesreleasesscalabilitytransactions
  417. REC 553

    Re: New demonstration CPU miner available

    You should try it with tcatm's 4-way SSE2 SHA in sha256.cpp. It compiles fine as a C file,…
    bitcoin designminingreleases
  418. REC 554

    Re: Cooperative mining

    ribuck's description is spot on. Pool operators can modify their getwork to take one additional parameter, the address…
    addressesbitcoin designminingprivacytransactions
  419. REC 555

    Re: RFC: ship block chain 1-74000 with release tarballs?

    Despite everything else said, the current next step is: In particular, I suspect that more read caching might…
    bitcoin designnodesprivacyreleases
  420. REC 556

    Re: Is safe running bitcoins with the same wallet on more computers simultaneously?

    Very much not. Using multiple copies of wallet.dat is not recommended or supported, in fact all of Bitcoin…
    addressesbitcoin designmining
  421. REC 557

    Re: RFC: ship block chain 1-74000 with release tarballs?

    It seems like you're inclined to assume everything is wrong more than is actually so. Writing the block…
    releasestransactions
  422. REC 558

    Re: Incompatible wallet format with latest bitcoin-git ?

    What was this wallet used with? An early accounts patch or git build? It's while loading the wallet.…
    addressesbitcoin designreleases
  423. REC 559

    Re: RFC: ship block chain 1-74000 with release tarballs?

    That's a good optimisation. I'll add that next time I update SVN. More generally, we could also consider…
    addressesreleases
  424. REC 560

    Re: Wikileaks contact info?

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin design
  425. REC 561

    Re: JSON-RPC method idea: list transactions newer than a given txid

    It's not safe to use listtransactions this way. I know I've been criticized for being reluctant about listtransactions.…
    bitcoin designdouble spendingfeessecuritytransactions
  426. REC 562

    Re: JSON-RPC method idea: list transactions newer than a given txid

    Then how do you cope with the issues I listed in the message you quoted?
    transactions
  427. REC 563

    [bitcoin-list] Bitcoin 0.3.18 is released

    Version 0.3.18 is now available. Changes: - Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17 and…
    addressesbitcoin designreleasestransactions
  428. REC 564

    Version 0.3.18

    Changes: - Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17 and then upgraded again - IsStandard()…
    addressesreleasestransactions
  429. REC 565

    Re: JSON-RPC method idea: list transactions newer than a given txid

    I'm not talking about the normal risk for a given minconf level, I'm talking about additional pitfalls from…
    addressestransactions
  430. REC 566

    Re: Version 0.3.18

    New transaction templates can be added as needed. Within a few days, there will be plenty of GPU…
    addressesbitcoin designfeesnodesreleases
  431. REC 567

    Re: Version 0.3.18

    I came to agree with Gavin about whitelisting when I realized how quickly new transaction types can be…
    nodesreleasestransactions
  432. REC 568

    Re: JSON-RPC method idea: list transactions newer than a given txid

    As long as the interface is designed for things like showing the user the last N transactions history,…
    transactions
  433. REC 570

    Re: BitDNS and Generalizing Bitcoin

    I think it would be possible for BitDNS to be a completely separate network and separate block chain,…
    bitcoin designdifficultyminingnodesproof of work
  434. REC 571

    Re: BitDNS and Generalizing Bitcoin

    The incentive is to get the rewards from the extra side chains also for the same work. While…
    bitcoin designminingnodesreleases
  435. REC 572

    Re: Fees in BitDNS confusion

    Not locktime. There's a possible design for far in the future: You intentionally write a double-spend. You write…
    addressesbitcoin designdouble spendingfeesmining
  436. REC 573

    Re: BitDNS and Generalizing Bitcoin

    Piling every proof-of-work quorum system in the world into one dataset doesn't scale. Bitcoin and BitDNS can be…
    bitcoin designnodesproof of workreleasesscalability
  437. REC 574

    Accounts example code

    Some sample pseudocode using the new Accounts based commands in 0.3.18. print "send to " + getaccountaddress(username) +…
    transactions
  438. REC 575

    Re: BitDNS and Generalizing Bitcoin

    Right, the exchange rate between domains and bitcoins would float. A longer interval than 10 minutes would be…
    bitcoin designfeesminingnodestransactions
  439. REC 576

    Re: BitDNS and Generalizing Bitcoin

    I agree. All transactions, IP changes, renewals, etc. should have some fee that goes to the miners. You…
    bitcoin designfeesminingnodestransactions
  440. REC 577

    Re: BitDNS and Generalizing Bitcoin

    @dtvan: all 3 excellent points. 1) IP records don't need to be in the chain, just do registrar…
    bitcoin designminingnodes
  441. REC 578

    Re: Bitcoin and buffer overflow attacks

    If you ever find anyone who turned it on. It's disabled by default. It's all STL. There are…
    bitcoin designsecurity
  442. REC 580

    Re: PC World Article on Bitcoin

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designgeneral
  443. REC 581

    Added some DoS limits, removed safe mode (0.3.19)

    There's more work to do on DoS, but I'm doing a quick build of what I have so…
    releasessecurity
  444. REC 582

    [bitcoin-list] Bitcoin 0.3.19 is released

    This is a minor release to add some DoS protection. Changes: - Added some DoS limits, though it's…
    bitcoin designreleasessecurity
  445. REC 583

    Bitcoin open source implementation of P2P currency

    1 quotation entry is indexed from this record. Open the archival copy for the complete wording and surrounding thread.

    bitcoin designbitcoin economicsidentity

Quotation index

162 passages, attached to their parent records.

The Satoshi Nakamoto Institute’s quotation set is curated, not exhaustive. Each entry remains linked to its message or the white paper; additional passages from the same source are indexed without mass republication.

  1. Q 001

    Bitcoin: A Peer-to-Peer Electronic Cash System

    “A purely peer-to-peer version of electronic cash would allow online payments to…”
    cryptocurrency
  2. Q 002

    Bitcoin: A Peer-to-Peer Electronic Cash System

    “We propose a solution to the double-spending problem using a peer-to-peer network.…”
    proof of workdouble spending
  3. Q 003

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    trusted third parties
  4. Q 004

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    trusted third parties
  5. Q 005

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    trusted third partiescryptocurrency
  6. Q 006

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    double spendingproof of work
  7. Q 007

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    transactions
  8. Q 008

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    economicsdouble spending
  9. Q 009

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    nodescryptocurrencytransactions
  10. Q 010

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    transactions
  11. Q 011

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    proof of work
  12. Q 012

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    proof of work
  13. Q 013

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    proof of work
  14. Q 014

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    proof of workdifficulty
  15. Q 015

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    bitcoin designnodesproof of work
  16. Q 016

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    nodesproof of work
  17. Q 017

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    transactions
  18. Q 018

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    miningbitcoin economics
  19. Q 019

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    feesbitcoin economics
  20. Q 020

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    miningbitcoin economics
  21. Q 021

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    bitcoin design
  22. Q 022

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    bitcoin design
  23. Q 023

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    bitcoin designnodes
  24. Q 024

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    transactionsbitcoin design
  25. Q 025

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    transactions
  26. Q 026

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    transactionsprivacytrusted third parties
  27. Q 027

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    addressesprivacy
  28. Q 028

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    miningproof of work
  29. Q 029

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    bitcoin designtrusted third parties
  30. Q 030

    Bitcoin: A Peer-to-Peer Electronic Cash System

    Additional indexed passage—full wording remains at the cited source.

    nodesmining
  31. Q 031

    Bitcoin P2P e-cash paper

    “I've been working on a new electronic cash system that's fully peer-to-peer,…”
    bitcoin design
  32. Q 032

    Bitcoin P2P e-cash paper

    “The main properties: Double-spending is prevented with a peer-to-peer network. No mint…”
    bitcoin design
  33. Q 033

    Bitcoin P2P e-cash paper

    “Long before the network gets anywhere near as large as that, it…”
    double spending
  34. Q 034

    Bitcoin P2P e-cash paper

    “Only people trying to create new coins would need to run network…”
    nodes
  35. Q 035

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    nodes
  36. Q 036

    Bitcoin P2P e-cash paper

    “The requirement is that the good guys collectively have more CPU power…”
    mining
  37. Q 037

    Bitcoin P2P e-cash paper

    “There would be many smaller zombie farms that are not big enough…”
    mining
  38. Q 038

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    mining
  39. Q 039

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    mining
  40. Q 040

    Bitcoin P2P e-cash paper

    “Yes, but we can win a major battle in the arms race…”
    motives
  41. Q 041

    Bitcoin P2P e-cash paper

    “Governments are good at cutting off the heads of a centrally controlled…”
    p2p networksgovernment
  42. Q 042

    Bitcoin P2P e-cash paper

    “As computers get faster and the total computing power applied to creating…”
    miningdifficulty
  43. Q 043

    Bitcoin P2P e-cash paper

    “The fact that new coins are produced means the money supply increases…”
    bitcoin economics
  44. Q 044

    Bitcoin P2P e-cash paper

    “Right, nodes keep transactions in their working set until they get into…”
    nodes
  45. Q 045

    Bitcoin P2P e-cash paper

    “Receivers of transactions will normally need to hold transactions for perhaps an…”
    transactions
  46. Q 046

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    double spending
  47. Q 047

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    nodesminingproof of work
  48. Q 048

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    transactions
  49. Q 049

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    nodes
  50. Q 050

    Bitcoin P2P e-cash paper

    “It's not a problem if transactions have to wait one or a…”
    transactions
  51. Q 051

    Bitcoin P2P e-cash paper

    “The proof-of-work chain is the solution to the synchronisation problem, and to…”
    proof of work
  52. Q 052

    Bitcoin P2P e-cash paper

    “A transaction will quickly propagate throughout the network, so if two versions…”
    nodes
  53. Q 053

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    nodesproof of work
  54. Q 054

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    proof of work
  55. Q 055

    Bitcoin P2P e-cash paper

    “If you're having trouble with the inflation issue, it's easy to tweak…”
    feesbitcoin economics
  56. Q 056

    Bitcoin P2P e-cash paper

    “When there are multiple double-spent versions of the same transaction, one and…”
    double spending
  57. Q 057

    Bitcoin P2P e-cash paper

    “The receiver of a payment must wait an hour or so before…”
    double spending
  58. Q 058

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    double spending
  59. Q 059

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    difficulty
  60. Q 060

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    transactions
  61. Q 061

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    nodes
  62. Q 062

    Bitcoin P2P e-cash paper

    “The proof-of-work chain is a solution to the Byzantine Generals' Problem. I'll…”
    proof of work
  63. Q 063

    Bitcoin P2P e-cash paper

    “It's very attractive to the libertarian viewpoint if we can explain it…”
    motives
  64. Q 064

    Bitcoin P2P e-cash paper

    “Broadcasts will probably be almost completely reliable. TCP transmissions are rarely ever…”
    nodesmining
  65. Q 065

    Bitcoin P2P e-cash paper

    “I'll try and hurry up and release the sourcecode as soon as…”
    releases
  66. Q 066

    Bitcoin P2P e-cash paper

    “A basic transaction is just what you see in the figure in…”
    transactions
  67. Q 067

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    double spending
  68. Q 068

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    double spending
  69. Q 069

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    proof of workmining
  70. Q 070

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    bitcoin economics
  71. Q 071

    Bitcoin P2P e-cash paper

    “The credential that establishes someone as real is the ability to supply…”
    proof of work
  72. Q 072

    Bitcoin P2P e-cash paper

    “The race is to spread your transaction on the network first. Think…”
    double spending
  73. Q 073

    Bitcoin P2P e-cash paper

    Additional indexed passage—full wording remains at the cited source.

    transactions
  74. Q 074

    Bitcoin P2P e-cash paper

    “I believe I've worked through all those little details over the last…”
    releasesbitcoin design
  75. Q 075

    Bitcoin v0.1 released

    “Announcing the first release of Bitcoin, a new electronic cash system that…”
    releases
  76. Q 076

    Bitcoin v0.1 released

    “If you can keep a node running that accepts incoming connections, you'll…”
    nodes
  77. Q 077

    Bitcoin v0.1 released

    Additional indexed passage—full wording remains at the cited source.

    mining
  78. Q 078

    Bitcoin v0.1 released

    Additional indexed passage—full wording remains at the cited source.

    transactions
  79. Q 079

    Bitcoin v0.1 released

    Additional indexed passage—full wording remains at the cited source.

    bitcoin economics
  80. Q 080

    Bitcoin v0.1 released

    “I would be surprised if 10 years from now we're not using…”
    cryptocurrency
  81. Q 081

    Bitcoin v0.1 released

    “It can already be used for pay-to-send e-mail. The send dialog is…”
    micropayments
  82. Q 082

    Bitcoin v0.1 released

    Additional indexed passage—full wording remains at the cited source.

    micropayments
  83. Q 083

    Bitcoin v0.1 released

    Additional indexed passage—full wording remains at the cited source.

    micropaymentsbitcoin economics
  84. Q 084

    Bitcoin open source implementation of P2P currency

    “I've developed a new open source P2P e-cash system called Bitcoin. It's…”
    releasesbitcoin design
  85. Q 085

    Bitcoin open source implementation of P2P currency

    “The root problem with conventional currency is all the trust that's required…”
    economics
  86. Q 086

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    micropaymentsprivacybanks
  87. Q 087

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    encryption
  88. Q 088

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    cryptocurrency
  89. Q 089

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    transactions
  90. Q 090

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    double spending
  91. Q 091

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    bitcoin design
  92. Q 092

    Bitcoin open source implementation of P2P currency

    “A lot of people automatically dismiss e-currency as a lost cause because…”
    cryptocurrency
  93. Q 093

    Bitcoin open source implementation of P2P currency

    “It is a global distributed database, with additions to the database by…”
    bitcoin design
  94. Q 094

    Bitcoin open source implementation of P2P currency

    “You could say coins are issued by the majority. They are issued…”
    bitcoin economics
  95. Q 095

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    bitcoin economics
  96. Q 096

    Bitcoin open source implementation of P2P currency

    Additional indexed passage—full wording remains at the cited source.

    bitcoin economics
  97. Q 097

    Re: Repost: Bitcoin Maturation

    “Think of it as a cooperative effort to make a chain. When…”
    mining
  98. Q 098

    Re: Repost: How anonymous are bitcoins?

    “For greater privacy, it's best to use bitcoin addresses only once.”
    privacytransactions
  99. Q 099

    Re: Questions about Bitcoin

    “Those coins can never be recovered, and the total circulation is less.…”
    bitcoin economics
  100. Q 100

    Re: Questions about Bitcoin

    “Being open source means anyone can independently review the code. If it…”
    trusted third parties
  101. Q 101

    Re: A few suggestions

    “The average total coins generated across the network per day stays the…”
    mining
  102. Q 102

    Re: A few suggestions

    “We should have a gentleman's agreement to postpone the GPU arms race…”
    mining
  103. Q 103

    Re: A newb's test - anyone want to buy a picture for $1?

    “I very much wanted to find some way to include a short…”
    bitcoin design
  104. Q 104

    Re: How divisible are bitcoins and other market/economic questions

    “Eventually at most only 21 million coins for 6.8 billion people in…”
    bitcoin economicsbitcoin design
  105. Q 105

    Re: How divisible are bitcoins and other market/economic questions

    “If it gets tiresome working with small numbers, we could change where…”
    bitcoin design
  106. Q 106

    Re: Repost: Request: Make this anonymous?

    “Bitcoin is still very new and has not been independently analysed. If…”
    privacy
  107. Q 107

    Re: Repost: Request: Make this anonymous?

    “You could use TOR if you don't want anyone to know you're…”
    privacy
  108. Q 108

    Re: What's with this odd generation?

    “I'm sure that in 20 years there will either be very large…”
    bitcoin economics
  109. Q 109

    Re: What's with this odd generation?

    “In a few decades when the reward gets too small, the transaction…”
    bitcoin economicsfees
  110. Q 110

    Re: What's with this odd generation?

    “If you're sad about paying the fee, you could always turn the…”
    nodesminingfees
  111. Q 111

    Re: Current Bitcoin economic model is unsustainable

    “A rational market price for something that is expected to increase in…”
    economics
  112. Q 112

    Re: Current Bitcoin economic model is unsustainable

    “The price of any commodity tends to gravitate toward the production cost.…”
    economicsbitcoin economics
  113. Q 113

    Re: Current Bitcoin economic model is unsustainable

    Additional indexed passage—full wording remains at the cited source.

    bitcoin economics
  114. Q 114

    Re: URI-scheme for bitcoin

    “That would be nice at point-of-sale. The cash register displays a QR-code…”
    transactions
  115. Q 115

    Re: New icon/logo

    “How does everyone feel about the B symbol with the two lines…”
    bitcoin design
  116. Q 116

    Re: who is bitcoin.com

    “The price of .com registrations is lower than it should be, therefore…”
    general
  117. Q 117

    Re: removing bitcoin addresses

    “Bitcoin addresses you generate are kept forever. A bitcoin address must be…”
    bitcoin design
  118. Q 118

    Re: Could the bitcoin network be destroyed by someone generating endless bitcoin add

    “When you generate a new bitcoin address, it only takes disk space…”
    bitcoin design
  119. Q 119

    Re: Ummmm... where did my bitcoins go?

    “Simplified Payment Verification is for lightweight client-only users who only do transactions…”
    bitcoin design
  120. Q 120

    Re: Website translations

    “Does anyone want to translate the Bitcoin client itself? It would be…”
    releases
  121. Q 121

    Re: Dealing with SHA-256 Collisions

    “SHA-256 is very strong. It's not like the incremental step from MD5…”
    encryption
  122. Q 122

    Re: Dealing with SHA-256 Collisions

    “If SHA-256 became completely broken, I think we could come to some…”
    encryption
  123. Q 123

    Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG

    “The nature of Bitcoin is such that once version 0.1 was released,…”
    bitcoin design
  124. Q 124

    Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG

    “The design supports a tremendous variety of possible transaction types that I…”
    transactionsbitcoin design
  125. Q 125

    Re: Get 5 free bitcoins from freebitcoins.appspot.com

    “Excellent choice of a first project, nice work. I had planned to…”
    general
  126. Q 126

    Re: Transactions and Scripts: DUP HASH160 ... EQUALVERIFY CHECKSIG

    “Since 2007. At some point I became convinced there was a way…”
    bitcoin design
  127. Q 127

    Re: Dying bitcoins

    “Lost coins only make everyone else's coins worth slightly more. Think of…”
    bitcoin economics
  128. Q 128

    Re: Slashdot Submission for 1.0

    “Writing a description for this thing for general audiences is bloody hard.…”
    general
  129. Q 129

    Bitcoin 0.3 released!

    “Announcing version 0.3 of Bitcoin, the P2P cryptocurrency! Bitcoin is a digital…”
    releases
  130. Q 130

    Re: BTC Vulnerability? (Massive Attack against BTC system. Is it really?)

    “When someone tries to buy all the world's supply of a scarce…”
    economics
  131. Q 131

    Re: They want to delete the Wikipedia article

    “The timing is strange, just as we are getting a rapid increase…”
    general
  132. Q 132

    Re: Scalability

    “The design outlines a lightweight client that does not need the full…”
    scalabilitynodes
  133. Q 133

    Re: Scalability

    “I anticipate there will never be more than 100K nodes, probably less.…”
    scalabilitynodes
  134. Q 134

    Re: Scalability

    Additional indexed passage—full wording remains at the cited source.

    nodes
  135. Q 135

    Re: Proof-of-work difficulty increasing

    “Right, the difficulty adjustment is trying to keep it so the network…”
    difficulty
  136. Q 136

    Re: The dollar cost of bitmining energy

    “Difficulty just increased by 4 times, so now your cost is US$0.02/BTC.”
    difficulty
  137. Q 137

    Faster initial block download (5x faster)

    “By making some adjustments to the database settings, I was able to…”
    bitcoin design
  138. Q 138

    Re: md5?

    “For future reference, here's my public key. It's the same one that's…”
    general
  139. Q 139

    Re: Implementation bug prior to 0.3.6

    “Actually, it works well to just PM me. I'm the one who's…”
    bitcoin design
  140. Q 140

    Re: Scalability and transaction rate

    “The current system where every user is a network node is not…”
    nodes
  141. Q 141

    Re: Flood attack 0.00000001 BC

    “Bitcoin isn't currently practical for very small micropayments. Not for things like…”
    micropayments
  142. Q 142

    Re: Flood attack 0.00000001 BC

    “Forgot to add the good part about micropayments. While I don't think…”
    micropayments
  143. Q 143

    Re: Bitcoin minting is thermodynamically perverse

    “It's the same situation as gold and gold mining. The marginal cost…”
    bitcoin economics
  144. Q 144

    Re: Bitcoin minting is thermodynamically perverse

    “Proof-of-work has the nice property that it can be relayed through untrusted…”
    proof of work
  145. Q 145

    Re: Bitcoin minting is thermodynamically perverse

    “The heat from your computer is not wasted if you need to…”
    mining
  146. Q 146

    Re: Escrow

    “Then you must also be against the common system of payment up…”
    general
  147. Q 147

    Re: Not a suggestion

    “It's hard to think of how to apply zero-knowledge-proofs in this case.”
    privacyzero knowledge
  148. Q 148

    Re: Potential disaster scenario

    “Some places where generation will gravitate to: 1) places where it's cheapest…”
    mining
  149. Q 149

    Re: checkpointing the block chain

    “There is no way for the software to automatically know if one…”
    proof of work
  150. Q 150

    Re: Bitcoin does NOT violate Mises' Regression Theorem

    “As a thought experiment, imagine there was a base metal as scarce…”
    economics
  151. Q 151

    Re: Bitcoins are most like shares of common stock

    “Bitcoins have no dividend or potential future dividend, therefore not like a…”
    bitcoin economics
  152. Q 152

    Re: Always pay transaction fee?

    “Another option is to reduce the number of free transactions allowed per…”
    feesnodes
  153. Q 153

    Re: Always pay transaction fee?

    “The threshold can easily be changed in the future. We can decide…”
    scalability
  154. Q 154

    Re: Always pay transaction fee?

    “Currently, paying a fee is controlled manually with the -paytxfee switch. It…”
    fees
  155. Q 155

    Re: Bug? /usr/bin/bitcoind ""

    “I don't know anything about any of the bug trackers. If we…”
    bitcoin design
  156. Q 156

    Re: Porn

    “Bitcoin would be convenient for people who don't have a credit card…”
    general
  157. Q 157

    Re: BitCoin Wikipedia page DELETED!!!

    “I wish rather than deleting the article, they put a length restriction.…”
    general
  158. Q 158

    Re: I broke my wallet, sends never confirm now.

    “As you figured out, the root problem is we shouldn't be counting…”
    transactions
  159. Q 159

    Re: New icon/logo

    “I'm happy if someone with artistic skill wants to contribute alternatives. The…”
    bitcoin design
  160. Q 160

    Re: Wikileaks contact info?

    “The project needs to grow gradually so the software can be strengthened…”
    bitcoin design
  161. Q 161

    Re: PC World Article on Bitcoin

    “It would have been nice to get this attention in any other…”
    general
  162. Q 162

    Bitcoin open source implementation of P2P currency

    “I am not Dorian Nakamoto.”
    identity
Published private sets

Correspondence disclosed by recipients and courts.

These collections are not folded into the 581-message public total. They vary in completeness, counting method and provenance.

  1. Adam Back
    court exhibited

    20 August 2008—10 January 2009 · Five-email court exhibit. Filed evidence supplies a dated exhibit; the collection is not counted among the 581 contemporaneous public messages.

  2. Wei Dai
    recipient published

    22 August 2008—10 January 2009 · Three published emails; two from Satoshi. Recipient-authorized publication concerning b-money and the draft paper.

  3. Hal Finney
    recipient published

    November 2008—January 2009 · Recipient-supplied email set; normalized counts vary. A recipient-preserved PDF documents testing and debugging around Bitcoin’s launch.

  4. Dustin Trammell
    recipient published

    11—25 January 2009 · 22 individual mailbox files plus aggregate mailbox. A Wayback-preserved recipient release; quoted chains can duplicate earlier messages.

  5. Mike Hearn
    recipient published

    12 April 2009—23 April 2011 · Five recipient-published Gmail threads. The fifth thread contains Satoshi’s statement that the project was in other contributors’ hands.

  6. Martti Malmi
    recipient published

    2 May 2009—22 February 2011 · 260 numbered emails in the published collection. Malmi labels the release incomplete because messages from another address were not retained.

  7. Jon Matonis
    recipient published

    4 March 2010 · One published message. A small recipient-published set, listed separately from enumerable public mailing lists.

  8. Laszlo Hanyecz
    recipient published

    May 2010 · One fragile recipient-published excerpt. The surviving publication is narrow and should not be described as a complete mailbox.

  9. Gavin Andresen
    recipient published

    26 April 2011 · Final two-message exchange. A recipient-published copy documents the late handoff period without proving a civil identity.

Method / reuse

A versioned index, not an identity claim.

Public records are filtered to Satoshi-authored entries, normalized to ISO timestamps while preserving raw timestamps, linked to a pinned upstream commit, and hashed after quoted reply blocks and contact details are removed. The 2014 P2P Foundation message is excluded from the documented-era total. No message here establishes a civil identity.

Reproducible source snapshot: Satoshi Nakamoto Institute repository commit c412eb84a1d97df9114a6bf4dea300820965c0a7 ↗, retrieved 9 August 2026. Exact upstream byte counts and SHA-256 digests are recorded in the JSON dataset; release-file hashes are in the checksum manifest.

Degrees of Satoshi editorial project. “Satoshi Nakamoto Quotes and Correspondence Archive.” Degrees of Satoshi, version 1.0.0. Published 9 August 2026; last reviewed 10 August 2026. https://degreesofsatoshi.com/satoshi/correspondence/

Source archives retain their own rights and terms. This edition republishes metadata and short excerpts for research and discovery; use the cited record for complete wording. Read the editorial and correction standards.

Direct answers

Archive questions

Does this contain everything Satoshi ever wrote?

No. It indexes every Satoshi-authored public message enumerable in a named archival snapshot and separately registers published private collections. Lost, deleted, private and undisclosed communications cannot be known.

Why do BitcoinTalk totals differ?

The public profile counter reports 575 posts, while 539 posts are currently enumerable in the archival dataset. Deleted or inaccessible material prevents a perfect reconstruction.

Is the 2014 P2P Foundation message treated as authentic?

No. It is indexed as disputed post-dormancy account activity and excluded from the 581-message documented project-era total.

Why are some quotation entries not reproduced in full?

The archive prioritizes context, provenance and source links. It republishes only short excerpts while indexing every quotation record in the pinned source collection.