[What should volunteer translators do?]

You do not need to be a developer to help in the improvement of Bitcoin.

http://sourceforge.net/p/bitcoin/mailman/message/32255092/
Bitcoin Core 0.9.2 feature freeze is May 13th, 2014.  Now is the time for native non-English speakers to join Transifex to clean up the translations in all languages.  This is important for more than just Bitcoin because Litecoin will use these same translations.

What should volunteer translators do?
https://bitcointalk.org/index.php?topic=571414
Try the nightly builds of Bitcoin Core as it heads toward 0.9.2.  Not recommended for your production wallet.

https://www.transifex.com/projects/p/bitcoin/
Join Transifex as a translator and add your account to your language.

https://groups.google.com/forum/#!forum/bitcoin-translators
Join the Translator mailing list to receive announcements when translations are needed Bitcoin.  You will also receive notifications if other Bitcoin Project things in Transifex need translations (likely bitcoin.org).

The forum currently allows new users to send PM spam.  This is especially bad because it sends outgoing e-mail from the server which results in bitcointalk.org being classified as an e-mail spammer.

Even if new users were disallowed from sending PM's, or at least PM's that result in e-mail, that still would not protect the forum from being listed as an e-mail spammer.  Compromised old accounts could send spam PM and get the server in trouble.

One solution that would substantially help this is spam filtering of outgoing PM e-mail.  Perhaps the outgoing message can be piped through spamassassin.  Spam score and particular rules like URIBL's can be used to flag an account and possibly stop outgoing mail that could get the server in trouble.

[WARNING:]

Hi folks,

The Bitcoin Core developers have a desire to do a mostly bug-fix, cleanup and translation update release in v0.9.2 a few weeks from now.  You do not need to be a developer to help!  With these unofficial nightly builds, power users can more easily aid in testing of the master branch which will help to find bugs and polish things up faster.  Additionally translators can more easily run the latest code and see what strings need to be translated as we rapidly approach the next stable release.

WARNING: Nightly builds are potentially dangerous.  These builds are untested and may contain bugs.  While every effort is taken to maintain security of the build and web server, we are not responsible for anything that goes wrong.  It is up to the user to protect their own data, and to the community to use Gitian to independently make matching builds and to point out if something has gone horribly wrong.

Unofficial Nightly Builds
http://nightly.bitcoin.it
Builds will appear here roughly once a day.  Sometimes there will be no new build if nothing changed in master.
(This has nothing to do with the wiki.  They just provided a convenient subdomain and Cloudflare protection of the download server.)

Source and Binary Reproducibility
https://github.com/nightlybitcoin/bitcoin/branches
https://github.com/nightlybitcoin/bitcoin/releases
https://github.com/nightlybitcoin/gitian.sigs
All binary builds are byte-for-byte reproducible by using Gitian to build a particular tag in git.  For example, the 0.9.99.0-20140415-74dd52a branch denotes in a custom version tag v0.9.99.0-20140415-74dd52a with build date of 20140415 and the 74dd52a commit from master.  Sometimes the nightly build will contain PR's.  This particular tag includes PR 4042 and PR 4049 that are both important for the next release.

Bug Reporting
https://github.com/bitcoin/bitcoin/issues
If you run into any problem with these builds please search the Bitcoin Github issues to find if it is already a known problem.  If your issue is not yet reported, file a new ticket and explain the problem.  You should include the exact name of the build you are using (i.e. v0.9.99.0-20140415-74dd52a) so the developers know exactly what you are talking about.  It would be helpful if you include a link to the branch used to build it which can be obtained from the README-SOURCE within the Linux tarball or Windows download directory.  For example, a typical branch will look something like this.  Include that link in your issue ticket and it will save time of the developers.

TODO's ... any Volunteers?
* There are many things that can be done to improve these automated nightly builds.  One of the most important has to do with security of the binaries.  Since each build is byte-for-byte reproducible from each git tag with Gitian, it should be possible for two or more independent builders to validate the results in an automated fashion.  Anyone interested in doing this?

Builder Changelog
2014-05-21: MacOS X builds added.
2014-05-13: Separate builds for master and 0.9.2 branch.
2014-04-16: Add auto-commit to gitian.sigs.
2014-04-15: Add GPG signatures to git tag.
2014-04-15: Deployed.
2014-04-13: Implemented nightly auto builder.

[DPR Seized Coins owner, SEND US THE COINS!!!]

DPR Seized Coins owner, SEND US THE COINS!!!
Andrian Lep <andrian_blockchain@yahoo.com>    Sat, Feb 22, 2014 at 4:33 AM
Reply-To: Andrian Lep <andrian_blockchain@yahoo.com>
To: "wtogami@example.com" <wtogami@example.com>
Hello, Mr Togami.
We've EVIDENCE that you are the owner of this BTC address (DPR Seized Coins ) now.
It's really very lucky to have  144,341.5246317 BTC. We WILL contact the FBI and post on the bitcointalk.org at February 24.
Please send us more than 8,000 btc and at least 16,000ltc.
BTC:     1MRTW5uQf9sh8TAhQqFEEYSDRL3ir6zcXo

              1PHCPQi3mhMdaYADAqfdUp2agCHhgHUESV
             
              1BVVs5i35mrerWNV8EdMb3yEpM2urntU1V
 
               1PvXWDwV3CfMnrEUDG73MAvzBunxrkt7WT

LTC:       LV9xKPUFkvoinG5WNdpSuVkSDXP5VTh37S
Have a  good night!

I admit it.  This unaltered* screenshot was made by me.  I tried to pay the blackmail but the client fails when I click on send.  What do I do?  I have less than one day to pay or I am exposed.  Help!


















* The screenshot is real ... of Bitcoin-Qt patched to demonstrate watch-only addresses support which is not yet in the standard Bitcoin-Qt client..

[FIXED.]

FIXED.

Can you fix the MacOS X Bitcoin LevelDB data corruption issue?

https://bitcointalk.org/index.php?topic=337294.msg3718821#msg3718821
TEST THESE BUILDS NOW!

Bounty Funding: 10.00 BTC + 200.2 LTC
Gavin Andresen has pledged 5 BTC.  BitcoinTalk pledged 4 BTC.  Public donations have contributed 1 BTC.  Litecoin Dev Team pledges 200 LTC.  The public is encouraged to contribute to these addresses to increase the incentive to fix this sooner.

BTC: 1FZ1mSJXj8aJqdpwUcpigLBqJLwtTu46fA
LTC: LS1Rb3bb29TA9PEVGR64bV2cLxC7RdQi8A

Conditions
The bounty may be awarded under the following conditions.

• Document how anyone can consistently reproduce the data corruption.
• Explain why it happens.
• Write a code fix that is acceptable to the Bitcoin core developers and merged into Bitcoin.

The Bitcoin developers have ultimate deciding power of how to apportion the bounty award(s) based upon the merit of the contributions  This may encourage collaboration that may lead to a fix rather than hoarding of information.  Non-developers may be able to figure out #1.

These terms may be changed at any time for any or no reason.

Background
https://github.com/bitcoin/bitcoin/issues/2770
Since Bitcoin 0.8.x and the introduction of LevelDB, MacOS X users have been experiencing periodic LevelDB data corruption.  For some Mac users it has never happened, while for others it happens frequently.

https://github.com/bitcoin/bitcoin/pull/2916
https://github.com/bitcoin/bitcoin/pull/3000
https://github.com/bitcoin/bitcoin/pull/2933
Bitcoin master now contains two Mac-specific fsync patches and an upgrade to LevelDB 1.13.  Bitcoin 0.8.5 OMG3 and Litecoin 0.8.5.2-rc5 contains these same patches.  It is possible that a different Mac corruption issue was solved by these earlier patches, but users of these branches have reported continued corruption.  Curiously, corruption seems to happen after a clean shutdown and restart of the client.  All corruption reports seem to be from MacOS X 10.8.x and 10.9 users.  It is unclear if earlier versions of MacOS X are affected.  It is unknown if particular hardware or software configurations are involved.

https://github.com/bitcoin/bitcoin/issues/2785
Corruption with the same error message apparently is capable of fixing itself.  Not clear if this is true of the recent master branch.

GPG Signed message

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

https://bitcointalk.org/index.php?topic=337294
These addresses contain public donations to be added to the Bitcoin MacOS X corruption fix bounty.
BTC: 1FZ1mSJXj8aJqdpwUcpigLBqJLwtTu46fA
LTC: LS1Rb3bb29TA9PEVGR64bV2cLxC7RdQi8A
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQQcBAEBCAAGBQJSiaeFAAoJELEXnrc0fcENmRsf/3c/w53R2EHX62L+QimS96Rj
J+GPSpVQQRFOFr19OM+efjC1ydoZ3N/suYI1FynQ9nX4RzmCW5ZwbxMtl6wnEw7h
oIqv+ufnD0XEpkFr+g32JdoRNN2KprrMH4Cr2oLI0w+Oqv32jLveoRIqSzIArCId
U9ZVPcvFvKa9hWJrnM9KJQW6NgsGsKW3WBk5n/Wcbp4PYUn9ZC0taRMq2NbakSwk
RaNf6yFSC1wWb2dD6eE+1UiXBCidyK0cVUMkjCRoA0eRqZqy2cJwELmOrJ1RHlgP
6K9Y6MuelTPxhXNa/NNq/sVAbhOmtAeyJ5ApuTuvjd1gpKpS14bFEHY7yFf/dv7A
t0Z43xqQ8FVJ9HnYKY0T6d5W30L31bz5EZvhTQsa+IzfrQeBXGu1ecXM6dSlkcpf
KkJQdyLZ2W72roq+RjF5eOsLmlW9+Xyk7pMSn403oMlMY5EpJByAO8znomq0XEkq
UWPqfzjF2ptXGt6JqPdXx2La3w/jd+GNpHFsA65xZlcgYls/LXyq6483jDz3qPUS
L6WZJZh5BrE4yfmIcTh8LUdiVj7fzlZs3r7CKmD8pv3mtsLpqAZGNiFdK8uMuerp
h+2rPreMxGN7AqN28xdo5WOhqCAersoJQuwz3yQcGtXqnqcVTCBUCoaDpFxExlIK
BHKuGW6awyd1akgKz46aWjlDnWuJ94ZY90tkKPXtSe2XhMZHtq5gYzxpv6qEEFo4
ikDpxyaoDMK7GOdUW0FGY9ZSELWjuPSIwjip/5KN5Z51/TaUeiOQmhxQJLIHKNY3
SMj+wNJLb+FTdlOPBEqYAu3WPPG9ye73ADudt1N36ELLqFcvjsB1RzqntpogEHXR
T+I2VOTtbMvCPqbKdy5FijOERfjRIfrfXirovboLb/iP8ouhbuH7JHcj2niFshaL
i6MBAB2eTTh9LlNx3B1w/ESQuYJlR4NsHDiGmWQGHAEHw6LaCVT7MDh2fmag+1Jx
vDF2LdcCnRCgP5mSv+ZeJv7MvpeJ84UL3SlkB6iKZyD1+EJMyTB7f7xLbyWZSp+v
To7lqJBxk1PbqcRl9rYX7jdW4b4ztsr8FNxOvw5jxcPGZ0Mc9eb9ln6Nl+hx4PBv
jg4j4emg9uAPqRZn8KgJ1OL+wYE5Lw74mu3CP63pBmRVSl894janSUhKc4Z3ToF2
9kf81jVWudmRrVzQhiYA8vlrbC1Bc3nhlrX0KlF8VdREvptfV9PMbOAZdW96u4Mt
1lbqv2ZNWqxOon7Q3HKOcOo3uNvhv0sYItXSygZx5Z/chmBBRQrrJDCdHUw+WhR8
UGNsSL+Rz2vFeAc/W6jrlw3dId/wK+H36vDW8X4bSY6rVi+HhxZNoAPihUNNFy4=
=o/b5
-----END PGP SIGNATURE-----

[Centralization at large mining pools is a long-term risk to the safety and security of the Bitcoin network. p2pool-like mining is vitally important as it does not create systemic risk in the form of centralized pools. p2pool also benefits the network by substantially boosting the quantity of listening relay nodes across the world. On November 8th, 2013, the Litecoin Dev Team awarded a ~$2,000 grant (and $1,000 more on December 29th) to Forrest Voight in support of development to improve the scalability of the p2pool decentralized mining network.]

Centralization at large mining pools is a long-term risk to the safety and security of the Bitcoin network.  p2pool-like mining is vitally important as it does not create systemic risk in the form of centralized pools.  p2pool also benefits the network by substantially boosting the quantity of listening relay nodes across the world.  On November 8th, 2013, the Litecoin Dev Team awarded a ~$2,000 grant (and $1,000 more on December 29th) to Forrest Voight in support of development to improve the scalability of the p2pool decentralized mining network.

p2pool-13 enabled massive growth of decentralized mining since mid-July 2013

Our previous support of forrestv enabled the release of ASIC-capable p2pool-13.x for p2pool BTC along with minor improvements to scalability and dust reduction that were of benefit to both the Bitcoin and Litecoin networks.  This new grant is to encourage further research & development that would allow p2pool to comfortably scale to a much larger size.

p2pool Research & Development Ideas Document
https://docs.google.com/document/d/1fbc6yfMJMFAZzVG6zYOwZJvYU0AhM4cvd4bUShL-ScU/edit
Several different proposals are being brainstormed in this document.  Please add comments to the document or reply in this thread if you have ideas.

$2,000 is not enough for this important cause.  Join us in support of Decentralized Mining!
Decentralized mining is vitally important to the long-term security of the Bitcoin network.  $2,000 is too small for this important purpose, so I urge you to please join us in donating to support these important development goals.

forrestv's GPG signed statement: http://im.forre.st/pb/50065825.txt

Code:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I, Forrest Voight, am working to improve the scalability
of P2Pool and decrease the dust payouts created by it.

I control these two donation addresses:

BTC: 1KxvX5Hx8nh36ig2gT5bpeEcqLQcwJsZGB
LTC: LPfkfi2tMuGSc64PZTsP9Amt367hwAUQzY
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJSfmA2AAoJEKgljXA1bAEgM7oQAKZwuhvmGqy/RMjiFGBrJFtK
PN3wwn0g62cMH/JLGqfRAAYBxsjOY1l53VwGFLU1cBTB5yztigIAbjunf9UmYsgL
r7vtOCYL6RWv5+oFx4yC1JmFJXs0LkDhrhOwtLNlCi58h8TI77aMay6XiQ9ynsh3
W+AS6J8cQwjEtogGG0thk3SWkI1E6eZHrC9T2UjnOMUPHMsBpFqw35RXpXvtw0Yr
jAdFPPo0qCZA4BiwuhAkwuF7nVWp56YzRAwrwgx1s5cBR2l8049kDsOum4/mnU3b
3tDxZ9cFvO+x5AIuf/QQbguBeQ2tGaLLsDNxiLjIW4OUMO3Lw6wQJhogEZIPW1Ao
CUmAMhdCSdqE6SmmhOMM9xyJL6XAVhYrCEEZOg5toU7+aBfzsTZPEUNJUX+fgy6v
QjUUM0subv6rM+Ft8HgwoDdslmYog0QPlCzA0FvLMpP9MnKKvuYh02HzlVS8PnOo
FI1rN2pHlvKht6NW4HidGyg5uTES1p8M2wt4Ls63E+ar7fXChzw6p9T9ESAY59wh
7VaH8W01EPWpnE1w6XtlKV/rtk3PaCYWLIb54WMwLP8DeH2wB4R7PRfhZgoFWFt2
XWT+Jt6Llywf/zMPw37aFgITreUYhamEQYWCVpc8VE6YsHfs7m0VCcBwT4fP041S
l9N6cL309hKjUltMDrOO
=5Vpm
-----END PGP SIGNATURE-----

To be clear, forrestv is not a Litecoin Dev.  We just consider his work to be vitally important so we encourage the entire community to support his efforts to protect the Bitcoin network.  If someone else has a feasible implementation even better than p2pool then we may be interested in supporting that too.

Why is Litecoin supporting this cause?
Litecoin Dev takes part in several substantive efforts in support of Bitcoin because we are in the same boat in terms of technology development and the needs to protect the network.  Litecoin gives back to Bitcoin and will increasingly do more in the coming year.

• Litecoin 0.8 contains some patches that differ from Bitcoin 0.8, backported fixes from Bitcoin 0.9, and other things not yet merged in Bitcoin 0.9.  Our testing on a smaller scale with real users and real money on the line has enabled finding bugs and further verifying patches before code shipped in Bitcoin 0.8.x and 0.9.
• Those improvements to 0.8 are also published in Bitcoin 0.8.5 OMG, a well-tested branch of Bitcoin 0.8.5 plus many bug fixes and mature features beyond the standard 0.8.5.  This branch has also helped to find bugs before they reach Bitcoin 0.9.  p2pool miners may like the disablewallet feature.
• Litecoin Dev also supports various Bitcoin devs including forrestv in support of work important to both features and network security.
  

[Update Nov 13, 2014:]

Update Nov 13, 2014:
https://github.com/litecoin-project/bitcoinomg
0.9.3 plus many backports including watch-only.  Can you help to test especially the watch-only parts?

Bitcoin OMG is an unofficial branch of Bitcoin 0.9.x plus well-tested features backported from Bitcoin master.

It is the intent for Bitcoin OMG to be relatively conservative and usable after wide-spread testing, but please be careful and make backups of wallet.dat.

Historically this branch has helped to find bugs in Bitcoin master before they go into the next official release.

Feature Highlights - stuff backported from Bitcoin master

• Watch-only
• and lots more! read the commits in the source below

Git Source
https://github.com/litecoin-project/bitcoinomg/commits/OMG-0.9

Binary Downloads
http://download1.rpmfusion.org/~warren/bitcoin-0.9.3-OMG30/
Please use GPG to verify the integrity of each download.

Gitian Build Verification
https://github.com/litecoin-project/gitian.sigs.omg
You can follow the directions here to compare your gitian builds to better ensure that the build was not compromised.