I'm confused, if the "forum" is paying to the forum for advertising, why not just take one slot out of the bidding?
Because if someone will pay more than 6.5 BTC for it, they can have it. If the forum bid is for this critically important Public Service Announcement, I might suggest an alternative approach that may be a better outcome for all three parties. Instead of excluding one paid slot to enable the PSA, why not make one slot "XYZ sponsors the critical MacOS X corruption fix bounty!" The cost of such a slot would be higher than a typical ad, but the PR value of supporting such an important cause that benefits the entire Bitcoin ecosystem may be worth that extra one-time expense. Posting an ad reading "Brand name sponsors critical Bitcoin fix." has a greater potential to gain credibility over a typical "You want my product/service" that you normally see in an advertisement. Thoughts? (Perhaps this MBA school thing was useful for something after all...) |
|
|
|
|
You can "hardware accelerate" Bitcoin by using a x86_64 binaries instead of 32bit. The hashing functions and signature validation is *much* faster on 64bit.
Linux distributes 64bit and 32bit binaries. Currently Windows and Mac builds are 32bit only and could be faster if there were 64bit builds. The developers don't want to do additional 64bit builds because that would be more time in QA testing, so there would be a cost in paying developers to make and test it.
|
|
|
|
Since 0.8x I have the corrupt db (and thus forced rescan) each time that my computer powers off due to battery/electrical failure.
Wtogami: try to power off your computer without shuttind down Bitcoin-QT, the db will probably be damaged.
0.8.5 OMG3 has three patches that prevent other corruption, although not the particular issue of this bounty. Also we have never seen corruption on 10.6.8. |
|
|
|
This is on Litecoin 0.8.5.2-rc5 (same as Bitcoin 0.8.5 OMG3) running on MacOS 10.6.8 where it does not corrupt itself. Does not corrupt or you cannot get it corrupted ? If the latter, then you solved the first step in this bounty but didn't announce it ? MacOS X 10.6.8 does not seem to corrupt with native Bitcoin-Qt as far as I can tell, so this test doesn't tell us anything. I am only pointing out that it is possible. |
|
|
|
|
The bounty was claimed in March. The resulting wallet was incomplete and screwed many users with bugs. We are in the process of rewriting the entire stack to be long-term maintainable.
|
|
|
|
If anything, this should serve as a warning for picking up cool new shiny things.
I take there was some discussion about why picking LevelDB was the right choice, surely it wasn't considered only because it performs faster than BDB and is developed at Google ? After that surely there were some good testing in various systems, since this is a very new low level storage, yes ?
I'm just mocking here, obviously. Good luck finding and fixing the issues.
It's working quite well on Linux and Windows. Also the old BDB corrupted on all platforms, although less often than Mac users experience this current issue. |
|
|
|
wtogami,
I can confirm that it has nothing to do with time machine, I do not have time machine.
What version exactly are you running? There have been multiple fixes. Please verify specifically with Bitcoin 0.8.5 OMG3. |
|
|
|
https://bitcointalk.org/index.php?topic=337294A few of you commented that you experience continued corruption even with all the patches in Bitcoin OMG3. Gavin Andresen says it happens in Bitcoin master too. A bounty is now funded by Gavin and Litecoin Dev. Mac users, please consider adding to the bounty to increase incentive of someone to fix this sooner.
|
|
|
|
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 LTCGavin 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. ConditionsThe 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. Backgroundhttps://github.com/bitcoin/bitcoin/issues/2770Since 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/2916https://github.com/bitcoin/bitcoin/pull/3000https://github.com/bitcoin/bitcoin/pull/2933Bitcoin 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/2785Corruption 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-----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-----
|
|
|
|
https://bitcointalk.org/index.php?topic=329860.0Subpool is one of the several approaches in the p2pool R&D brainstorming document. Please donate to forrestv to increase incentive for him to work on these goals to allow true decentralized mining to grow much larger. We donated $2,000 to start this fund raiser on November 8th.
|
|
|
|
That is outbound, there is no limit for inbound. One IP address could theoretically fill all incoming listening slots of the entire world. That is unless they used something like my iptables rule above. Some of the devs indicated that they would welcome an option for this kind of behavior in bitcoind itself. |
|
|
|
If you are running a bitcoin listening node on Linux, this example iptables rule would help to limit the number of incoming connections coming from the same IPv4 subnet. # Reject TCP connection if quantity of connections per class C network is exceeded.
# "--connlimit-above 2" is default in this example. The limit can be increased if
# your server has sufficient RAM to handle an increased bitcoin.conf maxconnections=
# parameter much higher than the default 150 simultaneous connections.
-A INPUT -p tcp --syn --dport 8333 -m connlimit --connlimit-above 2 --connlimit-mask 24 -j REJECT --reject-with tcp-reset
# Allow TCP connection if not rejected by the previous limit
-A INPUT -m state --state NEW -m tcp -p tcp --dport 8333 -j ACCEPT
# This TCP connection limit per source class C subnet is similar to a Slowloris
# HTTP DoS mitigation measure, except it is safe to have a very small limit.
# It is non-fatal for legitimate clients to fail to connect because there exist
# plenty of other legitimate nodes to choose from that offer the same service.
# It is more important to allow random, distributed clients to connect with a 90%
# success rate than it is to that ensure 100% of clients are able to connect.
|
|
|
|
|
Impressive. It seems he was totally compromised, bitcointalk account and GPG key. It isn't clear what agenda is trying to be achieved by the leaker.
|
|
|
|
https://bitcointalk.org/index.php?topic=329860November 8th, 2013, the Litecoin Dev Team awarded a ~$2,000 grant to Forrest Voight in support of development to improve the scalability of the p2pool decentralized mining network. Please read the thread for more details.
|
|
|
|
|
Show Posts
