The connection won't get through at all if the port is not forwarded.

http://btc2psc.bt.funpic.org/ Sell your Bitcoins for 10€ Paysafecard codes.

Welcome! Open source rocks.

The coins go to the machine that the sender connects to. You need to do port forwarding to direct the incoming connections at port 8333 to the correct subnet address. Instructions: www.portforwarding.com.

Not possible, the software doesn't allow that.


I guess the money will just be lost in that case.

http://www.livingsoulnation.org/ "LivingSoulNation.org is now using Bitcoin as its currency. Use it to trade with us or use it to donate Bitcoin(s)."

Not sure what they trade, though

What is interesting is that MB closed my account when the permission request was rejected. I had previously used the account for some small transactions. I asked them for a reason, but so far they haven't replied.

It's somewhat difficult to find a suitable payment gateway which supports incoming and outgoing transactions when PayPal and Moneybookers are not options. Google Checkout doesn't forbid money exchange and has a useful reputation system, but as far as I understand, they don't support sending money without the receiver being a merchant.

I've noticed that mainstream payment systems (credit cards, internet services etc.) typically cost about 1-5% of the transaction + various other fees up to hundreds of dollars. Bitcoin transactions are practically free, which already makes the system superior to the existing ones, not to mention the other advantages. We could use the low transaction costs (or should we say free?) more as a selling point.

Facebook marketplace seems like a good place to non-professionally sell and buy stuff for bitcoins. When you sell stuff, you're not limited to announcing the item price in a mainstream currency, you can write the price freely in a text field. When you buy stuff, you can ask people if they accept the payment in bc.

Good idea, made sticky  

The user gets 50 coins when he has created 1 block. The coins can be used (they "mature") when 120 blocks have been generated by the whole network after he created the block. The number of blocks of a transaction means the number of new blocks in the whole block chain after the transaction. The whole block chain grows ad infinitum.

Moneybookers didn't approve of my service. Any other ideas for an international payment service?

I think it was some technical limitation. Satoshi could tell more about this?

Unfortunately you can't attach a message when you send to a Bitcoin address. It's possible only when sending to an IP. Sending 0 coins is also not possible.

If you want to track payments, you can give a new Bitcoin address to each customer. How to make a new address: Options -> Change your address. We could perhaps make this easier by adding next to "Send Coins" a button "Receive Coins", which would create you the new address and ask for its label.

I've coded a web service that enables automatic money exchange of bitcoins. Send me a PM if you want to check out the site. Now I just need 1) the command line access to Bitcoin 2) permission from Moneybookers to do money exchange (or change to another system) and 3) some testing. The reserve euros for buying coins will be from myself and hopefully some other donators, and the profit will be added to the backup capital. I'll adjust my pricing according to supply and demand so that I'll never run out of either bitcoins or euros. It's the only sensible pricing in the long run.

It will be a more professional-style service than the currently existing ones. That will make it possible to market the system to people who already sell stuff. The first users will probably need to be some sort of idealists, as the immediate economic advantage of adopting bitcoin is not too big. It's ok if they just immediately traded to euros/dollars all the bitcoins they get from customers. Just that they accept bitcoins is absolutely great, as it increases the trust in the currency. We could make a "Trade" page on the bitcoin.org main site, where you can get your web shop address if you add some kind of a "we accept Bitcoins" -logo on your site.

When we reach the critical mass of maybe 20-100 shops accepting Bitcoin, the growth of the Bitcoin economy might jump to a whole another level.

Sounds good. Are you planning a bitcoin <-> euro/dollar service only, or are you going to enable trading other goods as well? That would be like an auction site where you trade stuff for bitcoins.

Moneybookers allows currency exchange after their approval. I'll check out if there are other options anyway.

Damn, that sucks. That prevents the creation of at least high-profile PayPal exchange services. I'll have to think of some other payment service that can support automation. PayPal would have been the easiest.


There's certainly demand on the market for accessing your money from any computer and not having to worry about backups, and I believe web UI's will sooner or later emerge to fill that need when the number of Bitcoin users increases. Centralized access points like the web UI wouldn't threaten the whole decentralized nature of the system. You'd still have the advantages of a stable currency base and anonymous transactions. The service would not be a bank in the sense that they can't borrow the "deposited" coins to anyone, because the "depositor" may still have backups of the coins and use them at any time.

On the other hand, the mobile client is also a great idea and satisfies the need for usability at any location. Backups of the wallet would be necessary though - you don't want to lose all your money when you drop your phone into the ocean or if it just gets broken. One option would be in-built FTP backups (might be too difficult for n00bs though).

In addition to the semi-automatic Bitcoin<->PayPal exchange service I'm working on right now, I guess we'll also need a Bitcoin web UI to make the product a breakthrough hit. For many people it's too difficult or bothersome to install and run a node on their own computer, or maybe some don't even have a computer of their own.

A web UI also makes it easier to use your coins from any location with an Internet connection. The need to make backups all the time decreases, as the server does it automatically. Of course you can also download backups of the coins onto your own computer.

The service would have the advantages and disadvantages of centralization: easier access and no need to maintain the program on your own machine, but on the other hand it makes the system more vulnerable. A server storing a lot of money becomes an attractive target for hackers, so banking grade security would be required. A central server is also easier to be shut down for political reasons, so maybe backups should be maintained in different countries.

Some ideas:
- The coins stored on the server would be encrypted with the username and password, so if someone gets the disks, he can't read the coins easily. When setting your password, there should be a widget that shows the password strength.

- For additional security you could order a list of 100 one-use keys snail mailed to your home. Each time you log in, one of these would be required, so all your money can't be stolen by just intercepting the username and password. This technique is used by some banks here.

"Confirmation" would be more informative than "block". It's good if the user can relate the number of "confirmations" to the number of "blocks" in the status bar.

Congratulations and welcome to the forum 


The number of blocks of a transaction is the amount of new blocks that have been generated by the whole network after the transaction. Each new block in the chain means new coins to its creator. One "generated" -transaction in your transaction list means that you have generated one block. You're not the first one to find the concept of a "block" a bit confusing on the first sight.


There's no confirmation of incoming transactions when someone sends to your Bitcoin address, all transactions are automatically completed. Did the transaction show up in the transaction list?


Other nodes aren't going to know which IP you're sending to, your client just connects directly to it. Both IP's are fine as long as the connection routes to the right computer. Anyway, I'd use the inner address inside a network for simplicity.