I created a little performance counter for myself to use locally, you guys are welcome to try it. Satoshi, maybe you could integrate this or something similar and put an option in there to turn it on/off? It spams up your debug.log and shows the performance of each thread.. it also shows on the UI in the status bar where it used to say 'Generating'. Patch: http://heliacal.net/~solar/bitcoin/bitcoin-svn-79-perfcounter-2010-06-02.patchScreenshot:  |
|
|
|
|
I'm not sure what you mean by again (I'm not the developer).. anyway I'm just trying to explain why I don't think you should use it to accept payments. Sending payments to a hostname is not reliable for the reasons I said above, and the biggest problem is that there is no way to even know that the payment went to the wrong place, for the sender. There is a better (reliable) alternative using one time bitcoin addresses.
What I was getting at is that there is no authentication and no way to know if the payment got there with internet address based transactions. I think the internet address based payments are only for testing locally. The option is there but I don't think it's suitable for using on the internet or any multi-user network.
If there was any real amount of internet address based transactions and tor users I would set up an exit node just to intercept any tor based payments.. I still may do it just to see if I can get any because it's just another way to make a few more bitcoins per day.
I guess what I'm trying to say that it is the equivalent of leaving a pile of cash in your driveway with a rock on top of it to keep it from blowing away in the wind. Anyone can just go pick it up and so if you're a service provider you would not want to encourage your customers to pay you in that way, because it would just cause problems when the customer says they paid and the service provider says they didn't receive it. The only reason it's even possible to use on the internet right now is because unlike cash which has perceived value to a lot of people, bitcoins are like a pile of rocks to random internet users, they just walk by. If there are all these piles of bitcoins in everybody's driveway and people start figuring out that they're valuable, you can bet they'll start disappearing, so it's best not to put them there in the first place.
Laszlo
|
|
|
|
|
I think the idea is that if NLS is using a tooth pick to go mining and he's valuing the bitcoins based on his time/materials invested, you can just get a bulldozer and mine faster than him and compete, which would encourage him to find a more efficient method or invest in cheaper internet or something. The value of it, as always, is what someone is willing to trade for it, not what any one individual claims it is.
|
|
|
|
There are security implications with sending payments to a 'hostname' instead of an internet address. TCP is difficult to forge, however DNS is trivial. It is not a good idea to send payments to a hostname. Whether it is an oversight or intentional, it probably should not be used for anything where fraud is a concern. Here's something I quickly googled up for anyone interested: http://adventuresinsecurity.com/Papers/DNS_Cache_Poisoning.pdfIt is not even really an attack, it's just how it works.. This is why once people figured out that DNS was unreliable, things like .rhosts for rsh went out of style and ssh uses public keys instead. It still does some DNS checking to see if the key changed, which could indicate that the DNS has been used to divert your connection to another host. It is very easy for me to make your computer think that someone-accepting-bitcoins.somedomain.sometld is MY computer, especially if I know you will be sending payment to it.. however if somedomain.sometld is some popular well known service like an exchange, I can just go trying to poison every bitcoin user's cache randomly and see how many I get. I know every node's network address so I can figure out who their provider is, thus I can easily narrow down which recursors they're likely to be using, so it makes attacking it a lot nicer rather than blindly messing with a bunch of random resolvers that may or may not have any effect. Many internet DNS servers will just accept any random data you send them, though there have been attempts to patch these things and work around some of the really trivial attacks. In the end though, it is the DNS protocol that's at fault and it is not easily patchable without replacing it. There are things in the works to make the protocol more secure and such, but until it's adopted by the entire internet, there will always be places to mess with it. It is not even a good idea to send payment to an internet address in my opinion, because the way it is implemented in bitcoin right now, you don't know if you connected to the right node. There is no pre-shared password or public key to verify manually. While it is not feasible to take over an existing TCP connection, it is possible to use NAT to divert it. In this case the attacker would have to have control of a router along the way to your destination, but in the case of Tor anyone can run an exit node and just accept all the bitcoin payments.. it's really easy to do that because they're all on port 8333 so I can just DNAT every connection to 8333 to my own bitcoin host. Just don't use hostnames or internet addresses - use bitcoin addresses. |
|
|
|
|
Thanks for the trade BitcoinFX!
|
|
|
|
|
I ran into some technical problems while experimenting with this and didn't get much farther than the Mac OS version. It seems that the NVIDIA CUDA 3.0 SDK for linux at least is very buggy when it comes to OpenCL. It never quite worked right on Mac OS either, it just leaks a lot of memory (the OpenCL implementation, not bitcoin). I will post an update if I come up with some solutions but I think the issues in the CUDA SDK will just have to be addressed by the vendor.. this stuff is all very beta right now, but I will keep my eye open for any new developments with the SDKs. I do not have an AMD GPU so I have not been able to develop for that at all, but their support is pretty spotty right now too, almost all of the current cards are listed as experimental support.
I think this tech has a lot of potential but I think most people who are using it for anything real are rolling their own vendor specific solutions. I would rather not pass out something that only partially works and only works for a few people.
|
|
|
|
It only verifies the last few as it is, to speed things up, but it doesn't work backwards. Satoshi has mentioned a simplified payment verification system that he is planning to implement, which would allow payment only clients which do not have to verify all the blocks - he just hasn't written it yet. I think even if you could just have someone 'click here to install instantly' it wouldn't do any good because they wouldn't have any bitcoins and they wouldn't know what a bitcoin is  |
|
|
|
|
So the bank wire thing, I need an account in europe for that to be free? It seems like I would need to exchange a ton of bitcoins to make the 30 euro fee worth it.
Is there some way I can establish an account online for that?
|
|
|
|
|
BitcoinFX, I requested an exchange, however the 'Your Bitcoin address' field would not accept a bitcoin address - it would only let me continue if I put an email address in there.
|
|
|
|
I just think it would be interesting if I could say that I paid for a pizza in bitcoins |
|
|
|
|
So nobody wants to buy me pizza? Is the bitcoin amount I'm offering too low?
|
|
|
|
|
The payments won't get lost because bitcoin writes the data to disk immediately, but in your game you would definitely want to perform the same 'flush' operation to commit the transaction to disk before you display the address to the player. Other than that, everything you described sounds good to me.. the JSON-RPC communication to the daemon is exactly how it is intended to be integrated right now and it sounds like you have a good understanding of the concept already.
|
|
|
|
Teppy, there is a JSON-RPC feature built into the client and that is how people generate integrate it into a web site or other software. You can send a command to the client to generate an address. The address that is created is yours forever, and it just allows you to receive payments, but regardless of which address the payment went to, it goes to your wallet. The coins are 'in' your wallet file and not owned by your address - you don't have to forward it back to your main one. Check out this thread http://bitcointalk.org/index.php?topic=63.0 |
|
|
|
|
You can create new addresses all you want.. the way most people are doing this is they generate a new address for the user and display it to them. When payment is received to that address it credits the user. You can just generate a new address for each transaction, like a transaction ID essentially. Link2VOIP automated it all and some others have as well, simply by using the built in JSON-RPC functionality.
Satoshi would have to address the other questions about including messages..
|
|
|
|
|
Teppy, just so you know, you can't include a message if you send to a bitcoin address, only if you send to an IP address. The way we usually do it is we issue a new address to each person we ask to send us money so that we know it was that person who sent it.
|
|
|
|
|
If it only has 15 connections and you say you've opened the port, it doesn't sound like you did it right.
If you are using a NAT router and are not directly connected to the internet you need to set up your router to 'destination NAT' that port to your bitcoin computer. You are using a NAT router if your computer's internet address is 192.168.x.x, 10.x.x.x or 172.16.x.x.
On the other hand, you aren't losing out on anything by not having the port open. It will work fine even with just 1 connection.
From your screen shot it looks like everything is working correctly and you are generating coins, you just need to wait about a day for it to 'grow' before you can spend it.
|
|
|
|
A lot of pizza places have online ordering, my wife and I use that sometimes with Papa John's. Almost all of them will accept credit cards by phone as well |
|
|
|
|
Jacksonville, Florida
zip code 32224
United States
|
|
|
|
|
I'll pay 10,000 bitcoins for a couple of pizzas.. like maybe 2 large ones so I have some left over for the next day. I like having left over pizza to nibble on later. You can make the pizza yourself and bring it to my house or order it for me from a delivery place, but what I'm aiming for is getting food delivered in exchange for bitcoins where I don't have to order or prepare it myself, kind of like ordering a 'breakfast platter' at a hotel or something, they just bring you something to eat and you're happy!
I like things like onions, peppers, sausage, mushrooms, tomatoes, pepperoni, etc.. just standard stuff no weird fish topping or anything like that. I also like regular cheese pizzas which may be cheaper to prepare or otherwise acquire.
If you're interested please let me know and we can work out a deal.
Thanks,
Laszlo
|
|
|
|
|
Show Posts
