If you have Photoshop or GIMP you can easily change the transparency of those text boxes. But I might release another version of the note where the QR boxes are the same size. I thought the private key would generate a larger QR image because it was longer than the address so I made it slightly larger, but it doesn't really seem like there is any noticeable difference (although the difference in size actually seems to depend on which QR generator you use).

You can go ahead and use it if you want, there's a license file with the PSD files which covers the images with the GNU General Public License and it includes a link to my website (if that's what you were trying to say, not sure).

Depends on what you want to do with them. I designed this note because I wanted to store some of my BTC "offline", so I'm going to have it in a safe place I don't really care about encrypting the private key. The best thing to do though is place a hologram over it and the QR code for it.

Front:


Back:


Download PSD Files

Bitcoin is not a legal tender of any nation, meaning it's also not a "foreign currency". No government controls bitcoin or claims to use it as a legal tender and there is no central bank for bitcoin. If anything bitcoin is a "global currency" which can be used by anyone with internet access. The way the Act is written doesn't appear to cover bitcoin, because it specifically talks about foreign currencies but doesn't deal with currencies which have no connection to a single government.

Yes it should be capable of handling multi-sig transactions and other types of complex transactions like bitcoin, but probably not all the types of transactions that bitcoin supports. And I'm not exactly sure how colored coins are supposed to work, but it seems like something which is layered on top of bitcoin and I see no reason it couldn't be layered on top of the mini-blockchain scheme in a similar way. Of course we could include something in the protocol which makes it easier to "color" coins. I'd need to look into the colored coin idea more before giving you a proper answer.

Well until we actually have a purely P2P and open source version of Ripple in operation that seems like a mute question to me.
The only reason Ripple is able to do some of the things it does is because it makes use of centralized servers.

The main thing that you are not taking into consideration is the fact that we wont reach 1 billion accounts in the account tree for an extremely long time, and by then it wont be unreasonable to expect people to deal with those sorts of large data sets (presumably). Now calculate how long it would take for the bitcoin blockchain to reach 300GB at the current rate of growth. Not too long I'm willing to bet, even with good pruning.

Furthermore, each account will be much smaller than 200 bytes, it will be closer to the 54 byte example you gave on the last page. No higher than 80 bytes in the worste case. If we assume 60 bytes instead of 200 bytes per account you'll find that it's only 55 gigabytes required. Also, the mini-blockchain will probably keep 1 weeks history or less, a full month is far too long if we need to account for very large transaction rates.

EDIT: But I do agree the system is not perfect and has its limitations, like any decentralized system. The answer is multiple competing crypto-currencies as you mentioned in your last post. But I don't think we would need thousands or even hundreds of coins, if we were to use the mini-blockchain / account tree scheme for those crypto-currencies, a few dozen or so could handle the entire worlds transaction needs I believe.

Well lexxus said he will begin working on it at the start of August but that's about the only plan we have so far.
I will now perform my mystic coder dance in order to attract a torrential flood of developers into the project.
lol... seriously though folks we need all the help we can get, I really want to see this get developed and tested.

The RSA keys don't get saved anywhere except where you save them. The private key is supposed to be saved in a safe place and the public key needs to be put in the main config file. If you re-install the store you could use the same keys or you could generate a new set.

I'm not sure, I'd have to take a look. Maybe PM me the contents of the main config file (remove the database and admin passwords) and I'll see if anything looks like it's set up wrong.

Strange. Did you upgrade to the latest version or install it fresh? It may be that you didn't upgrade properly... if not there's likely to be a problem with your config file.

ac is a cookie so it looks like your browser is having trouble dealing with cookies like I thought. Have you tried using another browser yet?

Indeed, it would be silly to develop the first client for mobile platforms because we need the hashing power of desktop CPU's and GPU's.

Now for a bit of good news. I finally think I figured out what was causing those random errors when confirming a transaction. I wasn't really sure it was a real bug because I'd never seen it myself and only had it reported to me by 1 or 2 people. However I was looking at the code and I realized why it might actually be a real bug.

The script changes between using the blockchain.info and the blockexplorer.com API's every few calls, however the script always double checks a payment before it will confirm it. I believe the problem would occur when the payment was confirmed with one of the API's and then when it went to double-check the payment it would switch to the other API, which didn't yet show the payment had been confirmed. So basically it would fail upon double checking the payment because one of the API's was lagging behind.

I believe I have now fixed this problem with the latest release (version 0.9.1). Now when it double-checks the payment it should use the same API that it used to confirm the payment. Hopefully that should solve the problem and that random bug will disappear.

The reason it doesn't have a user registration system is because it's designed to only sell digital stuff. I decided that there's no real point to having a registration system if you're selling digital items for BTC because everything can be automated and it makes the process much faster.

That's why there is no item cart either, the buyer can only purchase one item at a time, similar to eBay, because at the end of the confirmation process the buyer will automatically receive the file/codes for the single item they purchased, and it would be difficult to change that now.

So basically it's not designed to be like a typical shopping cart software, it's uniquely tailored to handle digital items and codes. That's a specific design choice I made because it's very difficult to make it support both support physical items and digital items at the same time.

Sorry to give you such a disappointing answer but I don't really plan to add support for physical items.

Yeah that's something a lot of people have requested but it's one of those updates I've been trying to avoid because it'll probably be fairly difficult to do. I will add that feature in one of the upcoming releases though.

Have you setup the configuration files properly and added your public RSA key to the SCI configuration file?

I recently made a rather large update to the script so the installation video needs to be updated a little bit. But it should be fairly easy to work out.

And if you have cookies disabled that might explain the admin login problem and perhaps the other problems as well. Try using another web browser and see what happens.

Well at this point I'm not too concerned with things such as the logo, but if you want to have a go at making a logo that's cool. I don't really know what info you need... the name of the currency is Peercash and the currency code is XPC. You shouldn't need anything more than that for the logo. I will use your logo if it's good but I can't guarantee it'll be used.

Well I don't really think Java is a bad language to write in, but I am feeling like C++ is a better option because most programmers who are familiar with bitcoin technology have worked with the C++ implementation and we might be able to get things done quicker if we go that way.

Yes that is the currency code we are going with.