For normal transactions yes.  For spam transactions no.  Quoting,

SHA1 sums for rc1:
5ca82c5b694fc432b4b342dde5cd1b145e265f13  bitcoin-0.3.23rc1-linux.tar.gz
8853206ec4d9e48bb41a0482ac1367f6fb01bcad  bitcoin-0.3.23rc1-src.tar.gz
12952b1c4a15ce55564500dace18ee22eb2feaa8  bitcoin-0.3.23rc1-win32-setup.exe

PGP signature of same: http://paste.pocoo.org/raw/405066/

See also https://github.com/kylegibson/poclbm for a poclbm fork that offers fallback support.  A bit easier than a proxy.

This is already possible.


Sounds like a great project.  Are you volunteering?


Shockingly...  people are already doing that which you describe as "very hard" simply by upgrading.

Re-read the part of my post about people voting with their downloads.
Then re-read the other post about transaction fees already changing.
Then read the thread on transaction fees changing to 0.0005.
And maybe study how mining works, too.


No idea what you're talking about here.

This problem has already been solved.

See this thread and https://github.com/kylegibson/poclbm

See my comments in this thread, also.

The forum just isn't suited for introducing new people to bitcoin, anymore.  It scares off more business-professionals than it attracts.

So...  you won't even tell the author of pushpool?

pushpool certainly cost me a lot more than "10 BTC + a whole day of hard work."

Zip for donations or thanks, just people asking for free support all the time, too.

You'd have to ask Gavin to be 100% sure, but I think that anybody working on software that deals with the bitcoin network should be welcome...

FWIW, all that is encoded into -dnsseed

No, that is completely random.  Mining does not affect your P2P connectivity.

'Generate Coins' has been removed in recent versions, anyway.

Two workarounds for slow bitcoin network:

1) Patience:  Wait a long time, possibly several hours.

2) Try the 0.3.23 release candidate, which attempts to address this problem.

The network has been flooded with new users, many of whom do not support incoming connections.  This causes a problem with the P2P code in versions <= 0.3.22.

If you are brand new to the network, -dnsseed may also help.

Bitcoin has always been a thinly traded market.  A $150k buy causes the price to skyrocket, 1000% or more.  A $150k sell causes a huge price drop, 60% or more.  $150k is nothing to a VC or bored trader.

This is precisely how thinly traded, volatile markets behave.  Penny stocks are quite similar (including all the vocal lovers and haters on twitter and various message boards).

More importantly, on weekends, bank transfers and big money are completely asleep.

Absolutely nothing has changed fundamentally about bitcoins in the past days/weeks.

Two workarounds:

1) Patience:  Wait a long time, possibly several hours.

2) Try the 0.3.23 release candidate, which attempts to address this problem.

The network has been flooded with new users, many of whom do not support incoming connections.  This causes a problem with the P2P code in versions <= 0.3.22.

Note to self -- actually compile the newly updated translations.

Yep.  It's just like any thinly traded penny stock.  A single VC or bored trader can skyrocket or tank the value.

A list of people who agree with you:

1. the dev team
2. major exchange operators
3. major pool operators
4. people trying to start bitcoin businesses
5. people trying to convince existing business to accept bitcoins

Well,

1. Big money and bank transfers are asleep on weekends.  Bitcoin always dips.

2. Bitcoin has always been a thin, highly volatile market.  After a huge rise amid "200,000% increase!" headlines on the front of Yahoo! Finance, you can expect huge drops.

Business professionals -- the people we are trying to convince to accept bitcoins -- are very turned off by the forums.

We are hoping to swap this forum with weusecoins, prefer a "professional code of conduct" and make that the primary forum.

Win32, Linux and source releases for bitcoin v0.3.23rc1 have been uploaded to
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/test/

This is another quick bugfix release, trying to deal with the influx of new bitcoin users.

Main items of note:

• P2P connect-to-node logic changed to reduce timeout a bit.  The network saw a huge influx of new users, who do not permit incoming connections.  This change is a short-term hack, to more quickly hunt for useful P2P connections.  Better "leaf node" logic is in the works, but this should let us limp along until then.
• Transaction fee reduced to 0.0005 for new transactions (see note below)
• Client will relay transactions with fees as low as 0.0001 BTC (see note below)

NOTE:  There has been some fee confusion recently.  Free transactions are supported and relayed as they always have been, according to special anti-spam rules.  See https://en.bitcoin.it/wiki/Transaction_fees for details.

Full git changelog:

Dean Lee (1):
      Updated Chinese Simp translation

Doug Huff (3):
      Fix rfc1918 and rfc3927 compliance for ignoring non-internet-routable host
      Add common temp files to .gitignore.
      Demystify a few magic numbers.

Han Lin Yap (2):
      Added Swedish translation
      Remove unused variable

Jeff Garzik (4):
      Bump version to 0.3.23.
      Reduce minimum TX fee for new transactions, to 0.0005.
      Lower minimum relay TX fee to 0.0001 (from 0.0005) BTC.
      Add minimal release process docs.

Matt Corallo (1):
      Fix CPU Usage bug when using -nolisten and have no connections.

Nils Schneider (1):
      create keypool in LoadWallet()

Pieter Wuille (3):
      Update transactions already in the wallet when rescanning.
      Fix for small change outputs
      Faster timeout when connecting

Gavin created bitcoin-development mailing list at SourceForge, for more focused devel talk.

The forum is rapidly becoming unusable for 'serious work'.