Version 0.1.5 is now available. It includes the fix for the problem
Nicholas had, checking for disk full and changes to try to improve
things that were confusing.
Special thanks to Nicholas and Dustin for all their help and feedback!
Download link:
http://sourceforge.net/project/showfiles.php?group_id=244765&package_id=298441
Changes:
- disk full warning
- fixed a bug that could occur if dns lookup failed
- prevent entering your own address in the address book,
which confusingly changed the label for your own address
- moved change address button to menu under options
- tweaks to make it get connected faster
- close sockets on exit
- created minimum fee for transactions less than 1 cent
- hid the transaction-type selection box that only had one choice
- cleaned up ParseMoney a little
- slightly cleaner reformatting of message text
- changed the font in transaction details dialog
- added some explanation text to transaction details for generated coins
- reworded the description for transactions received with bitcoin address
Satoshi Nakamoto
http://www.bitcoin.org
Version 0.1.5 seems to be running trouble free. I have a list of 201
transactions, I've accumulated about bc8550. Transfers in and out seem
to work fine (after a bit of head-scratching to understand the labelling
of incoming transactions).
What's next?
Nicholas Bohm
--
Salkyns, Great Canfield, Takeley,
Bishop's Stortford CM22 6SX, UK
Phone 01279 870285 (+44 1279 870285)
Mobile 07715 419728 (+44 7715 419728)
PGP public key ID: 0x899DD7FF. Fingerprint:
5248 1320 B42E 84FC 1E8B A9E6 0912 AE66 899D D7FF
> What's next?
The next thing for v0.1.6 is to take advantage of multiple
processors to generate blocks. Currently it only starts one
thread. If you have a multi-core processor like a Core Duo or
Quad this will double or quadruple your production.
Later I want to add interfaces to make it really easy to integrate
into websites from any server side language.
Satoshi
http://www.bitcoin.org
On Sun, Feb 22, 2009 at 9:35 AM, Satoshi Nakamoto wrote:
>> What's next?
>
> The next thing for v0.1.6 is to take advantage of multiple
> processors to generate blocks. Currently it only starts one
> thread. If you have a multi-core processor like a Core Duo or
> Quad this will double or quadruple your production.
That sounds good. I'd also like to be able to run multiple coin/block
generators on multiple machines, all behind a single NAT address. I
haven't tried this yet so I don't know if it works on the current
software.
BTW I don't remember if we talked about this, but the other day some
people were mentioning secure timestamping. You want to be able to
prove that a certain document existed at a certain time in the past.
Seems to me that bitcoin's stack of blocks would be perfect for this.
> Later I want to add interfaces to make it really easy to integrate
> into websites from any server side language.
Right, and I'd like to see more of a library interface that could be
called from programming or scripting languages, on the client side as
well.
Hal
Hal Finney wrote:
> That sounds good. I'd also like to be able to run multiple coin/block
> generators on multiple machines, all behind a single NAT address. I
> haven't tried this yet so I don't know if it works on the current
> software.
The current version will work fine. They'll each connect over the
Internet, while incoming connections only come to the host that
port 8333 is routed to.
As an optimisation, I'll make a switch "-connect=1.2.3.4" to make
it only connect to a specific address. You could make your extra
nodes connect to your primary, and only the primary connects over
the Internet. It doesn't really matter for now, since the network
would have to get huge before the bandwidth is anything more than
trivial.
> BTW I don't remember if we talked about this, but the other day some
> people were mentioning secure timestamping. You want to be able to
> prove that a certain document existed at a certain time in the past.
> Seems to me that bitcoin's stack of blocks would be perfect for this.
Indeed, Bitcoin is a distributed secure timestamp server for
transactions. A few lines of code could create a transaction with
an extra hash in it of anything that needs to be timestamped.
I should add a command to timestamp a file that way.
> > > Later I want to add interfaces to make it really easy to integrate
> > > into websites from any server side language.
>
> Right, and I'd like to see more of a library interface that could be
> called from programming or scripting languages, on the client side as
> well.
Exactly.
Satoshi Nakamoto
http://www.bitcoin.org