The open source driver bits are mostly there. The driver folks know how OpenCL will work, what ioctl(s) it will use.... once an open source OpenCL exists.
Actually, Mesa has a very early non-functional prototype that uses Gallium URL to non-functional OpenCL prototype?
|
|
|
Do you know of open source drivers that I can use instead?
Open source drivers won't get you an open source OpenCL compiler and implementation, unfortunately. The open source driver bits are mostly there. The driver folks know how OpenCL will work, what ioctl(s) it will use.... once an open source OpenCL exists.
|
|
|
2. (Yeah, i know, that i can't stop anybody from doing anything, but I'm just stating my opinion) Why do You people try so hard to kill bitcoin so quickly before it has a chance to get more audience ? I mean if You try to do every possible "dark businesses" such as drugs, prostitution, weapons through bitcoin, then You will quickly kill its [...] For God's sake, at least give it a some time before starting half-legal or illegal buisnesses. Maybe by then we will be strong enough and achieve enough critical mass that we can't be stopped anymore...
Agreed. Welcome to the selfish, paradoxical, self-destructive idiocy of "crypto-anarchism."
|
|
|
This is also about doing what is right, and this is the right thing to do. I get the arguments advocating caution, but sometimes you also have to take a stand on an issue too. There is a down side, and talking about concerns over that perhaps is useful.
Your stand could impact my money, and everyone else's. Don't pretend your actions could impact only you.
|
|
|
It's very, very easy to hook up to the JSON-RPC interface of the daemon with python. Unfortunately it's lacking a few key features like a full, official listtransactions command, so it would make for a rather stunted GUI.
Let's put that into the API. Full listtransactions has been rejected. <shrug> Plenty of people use it, so I'll continue publishing a working patch. It's tempting to publish a "useful patches" patchkit, to give these useful features to a wider audience.
|
|
|
IMO, bitcoin should remain an underground currency. While there are legitimate use for bitcoins, their security features will attract many "non-legitimate" users.. (i.e. M.O.M. services)
And thus doom bitcoin to be forever marginalized. I would rather see a large audience using bitcoin. I want to free the world from the constraints of central banking and fractional reserve banking. But that's not gonna happen if the majority of visible bitcoin purchases are for illegal or grey market goods and services. Wider distribution and use of bitcoin means wider distribution and use of freedom.
|
|
|
Basically, bring it on. Let's encourage Wikileaks to use Bitcoins and I'm willing to face any risk or fallout from that act.
Thanks for being willing to helpfully impose risk upon others. For people who are just starting to build businesses on bitcoin, this could be devastating to their new business. And it could permanently marginalize bitcoin, keeping it out of the mainstream for good. Is that really the end result the bitcoin community most desires? Some of us are working hard to build tools and programs that encourage businesses to invest their time, money and energy into bitcoin. It would be very sad to see all that go down the drain.
|
|
|
MIME type is clearly superior to "bitcoin://" type URL. Because after all, you might use http:// to download a .bitcoin file.
|
|
|
in the wikileaks case its a great danger.
+1, I agree completely We know that private and government forces are actively tracing, and trying to shut down, sources of wikileaks funding through all available means of pressure. Does it make sense to actively give multiple world governments incentive to shut down bitcoin? No matter how symathetic wikileaks' cause... if you care about bitcoin's success, the answer is no.
|
|
|
Not sure about C++, but in C, "static bool foo;" is guaranteed to initialize 'foo' to false.
|
|
|
Fantastic work. Are you able to get the 4way algorithm into the main client? It performs twice as well as the main client's algorithm on intel hardware, and seems to be working terrific on the AMD hardware.
4way is in the main client already -- albeit Linux-only, if I understand correctly. That's an open project for someone to tackle, if they're interested.
|
|
|
Yeah, I really don't see the advantage of bitcoin over cash for in-person transactions. I think the killer app is somehow micro-payment related.
Cash is physical. You gotta carry notes, get change, etc. I can get torn, degraded, takes up space, etc. bitcoins can have all the convenience of a credit card or debit card: just bump your phone against a reader, and you've purchased something with digital cash.
|
|
|
Based on the thread subject spelling, I bet I know what inspired this post... See the heroin store thread for a discussion along similar lines. My own opinion is that the US government loves to point to a technology, and make arguments in court along the lines of "the majority of uses are illegal / infringing / evil / etc., therefore, any use of that technology strongly implies illegality" I'm not making a political statement about drugs or gambling; that's just the practical reality one finds with today's law enforcement. The best way to make bitcoins a success is to convince legitimate, tax-paying, paperwork-filing merchants to accept bitcoins, and customers to pay them in bitcoins. Similar to how bitcoin's network remains intact: as long as >50% of the network is not evil, we need >50% of well known merchants to be upstanding citizens in their respective jurisdictions. One day, inevitably, law enforcement will have a bitcoin-related case, and having evidence of bitcoin's beneficial nature will be powerful and useful. Concrete example: presenting bitcoin as a way for donors to charities to remain anonymous is a powerful, positive argument for bitcoin. If the bitcoin "brand" is generally considered to be a den of thieves, scam artists, tax evaders, and criminals, it gains increased law enforcement attention, and will be marginalized away from the general public. I want bitcoin to be as broadly successful as possible.
|
|
|
Yes, true. Full automation is possible. Maybe you just need to ask.
I did. Multiple times. No response. But even ignoring that experience, simply going by the website, there is no send-payment interface. Google turns up a post indicating that the send-payment interface was turned off. All signs point to "go away" though I'm happy you're apparently a member of the Sekrit API Club.
|
|
|
5. I am making this forum post because you are sporadic in your response on IRC. I know that you're not doing it full time but it pains me all the same when I cannot launch my business due in part because of someone's non-responsive behavior.
Please respond to the concerns listed here so that I can make decisions and make plans for my business.
According to the mtgox.com website, email appears to be the preferred method of contact. I do not see any mention of IRC or bitcoin forums on there.
|
|
|
Pecunix is the best digital currency system. Sidd has always supported PGP and the slightly annoying "PIK" validation system is immune to keylogger trojans.
Generally agreed (well, I think bitcoin is a better system, due to fewer SPOFs). Full automation is possible
Not true, unfortunately. They have a payment receipt (shopping cart) API, but their send-payment API is either disabled or locked down to a select number of "blessed" users. Lack of a generally available send-payment API is pecunix's main technical flaw at this juncture.
|
|
|
Thanks for the info. I'll let the testnet client run for the night. What generate setting should bitcoind have? setgenerate set to true with limit to zero processors, or should setgenerate be set to false?
setgenerate controls the in-client miner. So, it may be set, or not, as you choose. These external miners use the 'getwork' JSON-RPC call, which works regardless of the setgenerate setting.
|
|
|
Missing mail is rare indeed.
Theft of mail obviously containing cash or other valuables is not unheard of...
|
|
|
You may find this patch to bitcoin helpful: diff --git a/main.cpp b/main.cpp index a1865a4..da85b0d 100644 --- a/main.cpp +++ b/main.cpp @@ -3273,8 +3273,11 @@ bool CheckWork(CBlock* pblock, CReserveKey& reservekey) uint256 hash = pblock->GetHash(); uint256 hashTarget = CBigNum().SetCompact(pblock->nBits).getuint256(); - if (hash > hashTarget) + if (hash > hashTarget) { + printf("proof-of-work check FAILED...\n hash: %s\ntarget: %s\n", + hash.GetHex().c_str(), hashTarget.GetHex().c_str()); return false; + } //// debug print printf("BitcoinMiner:\n");
This will show the proper, byte-reversed hash, and how close you came to the target. That is very helpful in verifying whether or not the algorithm is truly working.
|
|
|
|