cryptopp_asm32 = 1350khash/s
This is faster than standard bitcoin client, yes? Anyway, how much patience do you have for testing?  Other readers.. your help in comparing 0.2 versus 0.2.2test* speed is welcomed. Here is a matrix of options, to see if 4way can be improved: |
|
|
|
After upgrading to Fedora 14 (GNU assembler 2.20.51.0.7-5.fc14 20100318), the bitcoin build fails as follows: cryptopp/sha.cpp: Assembler messages:
cryptopp/sha.cpp:436: Error: junk at end of line, first unrecognized character is `1'
cryptopp/sha.cpp:436: Error: backward ref to unknown label "1:"
The assembler code in bitcoin has not changed in recent commits, so the root cause pointed to the Fedora upgrade. Apparently, current releases of GNU assembler do not like overly long lines created by the assembler macros in cryptopp/cpu.h + cryptopp/sha.cpp. The fix is simple: add newlines to the assembler macros in cryptopp/cpu.h. Arguably the semi-colon line terminator is redundant when a real newline is added, but I'm posting what worked for me. This problem (and fix) impacts upstream Crypto++ also. Here are three possible fixes, pick the one you like best. alt1) Update bitcoin's cryptopp/cpu.h to upstream Crypto++ version. This is 100% upstream changes, with nothing from me. http://yyz.us/bitcoin/patch.bitcoin-asmfix1then apply newline build fix for new GNU assembler. http://yyz.us/bitcoin/patch.bitcoin-asmfix2alt2) Alternately, here is the newline build fix without an update to latest upstream Crypto++, aka the minimal bitcoin build fix. http://yyz.us/bitcoin/patch.bitcoin-asmfix-minimalalt3) Alternately, here is the newline build fix without an update to latest upstream Crypto++, with the semi-colons removed: http://yyz.us/bitcoin/patch.bitcoin-asmfix-nl-onlyThere Pick your favorite patch. |
|
|
|
I'm interested if this works at all. it does, installs and runs nice as usual, Did you test 'cryptopp_asm32' algorithm? so, with 0.2.1 '4way' i get 2400,
0.2.2-0.2.2test '4way' i get 1440.
hmmm. On my side, I upgraded Fedora 13 to Fedora 14, and changed -O2 to -O3 in compile flags. Gotta wonder what changed  I should also look into a better CPU architecture setting than the default. |
|
|
|
The page that they link to in today's tweet about Bitcoin is hard to find from their home page. When you click the "Donate" button on the home page, you are not given a Bitcoin option. Still, having them tweet about Bitcoin definitely helps build buzz. I'm going to send them another donation, and I urge other forum members to do the same. Be generous!
It's not easily highlighted, but from the big red 'Donate' button, you can go Learn other ways to help -> Other ways to help EFF which finally lands you at http://www.eff.org/helpout where bitcoin is mentioned near the top. |
|
|
|
A test version of cpuminer, with crypto++ 32-bit assembly implementation, has been pushed out to git, and a test installer for Windows uploaded at http://yyz.us/bitcoin/cpuminer-installer-0.2.2test.zipSHA1: c105454954b63c4f846ced958b553c87182b88e5 cpuminer-installer-0.2.2test.zip MD5: ce5fd9d17167080892b8d9c06f582660 cpuminer-installer-0.2.2test.zip I'm interested if this works at all. Should be faster for Windows users than the current Crypto++ implementation, I'm guessing. |
|
|
|
Transparency in general is good, but the complete inability to have a private conversation with another world government is bad. You're assuming that government leaders behave better in secret than they do in public. I don't think there's much evidence for that. Fallacious logic. I make no such assumption. The world is not black and white, and several in this thread seem to be making the mistaken assumption that "100% transparency is bad" implies "secrecy is always good." Reality is far more nuanced. Transparency and openness should be the default position, not an absolute and unbendable rule. |
|
|
|
|
Protocol versioning is very "coarse."
Smarter protocols export lists of capabilities, as well as a "major" version number. The major version number is left unchanged absent a major protocol rewrite. The capabilities list is how clients notify each other of what features / bugs / etc. they support.
bitcoin has a bit of this already. grep for 'nServices'
|
|
|
|
Sure there's a few hiccups by a government suddenly being pried open. But in the long term, it's of benefit to have everything in the open. Even if processes have to change, or become more inefficient.
A few hiccups and inefficiencies, such as continued repression of North Korea? Transparency in general is good, but the complete inability to have a private conversation with another world government is bad. A world without private conversations would be hell on earth. Every leader would be a slave to the mainstream press headline of the day -- and we all the press in every country is fair, accurate, balanced and complete, right? As a friend of mine noted: Every journalist that is a proponent of wikileaks, should publish every single source they ever had and the dealings with their sources. No more hiding behind protection of journalism sources. Then we can talk. The first and foremost casualty of complete, unconditional, immediate transparency would be the truth. Think about it. |
|
|
|
|
Version 0.2.2 released:
- VIA padlock works (lfm)
- minor bug fixes (lfm)
SHA1: b7ffda89f3b76302b948a715905105b4cf0c080f cpuminer-installer-0.2.2.zip
MD5: 716f883b92e93082e2dfa9a3130972cb cpuminer-installer-0.2.2.zip
See top of thread for URLs.
|
|
|
|
|
git updated with sha256_via, sha256_4way fixes.
|
|
|
|
Unless you have been to Tehran, you are getting your information from the controlled media, owned by the same banksters that foment the wars.
You count the wikileaks cables as "controlled media...owned by banksters"? Strange. |
|
|
|
jgarzik: trying your cpu-miner on via: bug in main pprogram segment violation: needs extra NULL check for sparse array in parse arg if (algo_names[i] != NULL &&
!strcmp(arg, algo_names[i])) {
Good catch. Applied similar patch. Thanks for taking a look! |
|
|
|
They don't like the idea of free radical hackers undermining those in power.
I don't like the idea of uninformed, naive hackers undermining the good that diplomats around the world are doing. Simple example: informed people think Wikileaks made reunification of North and South Korea more difficult, in the event of a North Korean collapse (predicted in 2-3 years after Mr. Kim's death). The Chinese have been quietly negotiating with the Koreans, Americans and Japanese on this issue. Now that a Chinese minister is shown publicly to support reunification (and thus a democratic, unified Korea), a pro-US position, he has been embarrassed, losing face before his peers. This strengthens the nationalistic, hardline communists opposing reunification, who want to keep a Chinese-friendly, autocratic buffer state between China and democratic South Korea -- thus leading to the continued enslavement of the North Koreans. "transparency is always good" is incredibly naive. The real world is not that simple, and peoples' lives really are at stake. |
|
|
|
A bus is more fuel efficient and should benefit from the economy of scale.
There would be more train tracks. Trucks are used for local transport of material instead.
This depends largely on population density and geography. A bus or subway train are incredibly wasteful and inefficient, if ridership is low. |
|
|
|
|
The draft spec on the wiki is incomplete crap.
Your example is missing obvious data central to bitcoin -- transaction and block data.
It also seems that your hashes shrank to 32 bits.
|
|
|
|
Yep -- the diplomats and wanna-be's over at http://blog.foreignpolicy.com/ seem to think the current consensus is that the leaked cables make the US look good: it is generally doing what people expect it is doing. Nothing sekrit or earth-shattering. |
|
|
|
Or, to put in military terms, we know that wikileaks' entire financial infrastructure is being actively targeted, and The Powers That Be have successfully destroyed one target in the past 24 hours. Only cannon fodder would stand up and wave a red flag that says "shoot me" at such a point in time |
|
|
|
Also, it would be nice if you explain what kind of "pressure" you're doing. You represent the rest of the bitcoiners here, so it's nice to know how bob182 is acting on our behalf.
bob182 is certainly not acting on my behalf, nor several others, as these threads seem to indicate. And for Pete's sake, bob182, please don't misrepresent yourself as some sort of official Bitcoin representative. Wikileaks is the enemy of major world powers right now, with many influential elites feeling that Assange committed an act of war against the United States, or, at a minimum, irrevocably disrupted world affairs. This is not some mailing list discussion or theoretical exercise; there are very real, very powerful organizations actively targetting wikileaks' network infrastructure, organizational infrastructure, and most importantly, financial infrastructure. It is extraordinarily unwise to make bitcoin such a highly visible target, at such an early stage in this project. There could be a lot of "collateral damage" in the bitcoin community while you make your principled stand. |
|
|
|
|
Nitpick: One need not be a node, in order to use bitcoins.
|
|
|
|
|
Show Posts
