Ok I have decided to offer two new ways to purchase BitShop. These are less expensive one-time download options for those people who don't want or need access to future updates.

BitShop One-Time Download (6 months support) - $14.99 USD

BitShop One-Time Download (no support) - $9.99 USD

I just realized that the copy of BitShop I uploaded had the curl ssl verification turned off. It should be on so that ssl certificates can be properly verified. Check line 25 of the lib/bit-sci.lib.php file to fix it yourself or just download 1.0.7 again and replace that file.

@Medow: no BitShop does not work as an open marketplace, all products must be created by the admin.

Well the admin login code is totally different from what it was before and it doesn't use cookies anymore so the problem cannot be the same. Are you getting any error messages when you try to login? What exactly happens when you try to login? Have you tried logging in with the tor client option?

Ok sorry about the wait guys, was a lot more work than I expected. But the wait is now over, behold BitShop v1.0.7. Anyone with any existing product keys should still be able to access their files in the client file area (look for the download icon in the new menu). It is a very large update so obviously there may be some bugs still to work out, just let me know if anyone has any problems. I haven't actually tested the new Coinbase and GoCoin callback scripts but I'm 90% confident they should work. I have the GoCoin gateway enabled on the official BitShop website so we'll know if it works soon enough.

New features include:

* redesigned menu of the two included themes
* user can now change language, currency, etc
* added shopping cart and customer login area
* added support for physical items and shipping
* added support for coupouns and vouchers
* now use bcmath to operate on decimal money values
* recoded ticker stuff to be more reliable
* overhauled the default payment gateway
* support for multiple gateways simultaneously
* added support for multiple admin accounts
* real amount paid recorded for accurate accounting
* support for custom list of bitcoin addresses
* support for 0 confs in default payment gateway
* support for almost any altcoin via the daemon RPC
* recoded gateway system to be totally modular
* added support for GoCoin payment gateway module
* added support for a couple of new explorer api's
* removed support for blockexplorer.com api
* improved scalability of star rating system
* several other misc bug fixes and improvements

Features planned for next version:

* group based permissions for accounts
* more control over accounts in admin area
* integrated ticket support system
* a wish list system for registered users
* misc speed and scalability improvements

How to update BitShop to v1.0.7 (for v9.9.1 to v1.0.6):

1) Make a backup of your existing BitShop files and database.
2) Upload new BitShop files and replace old files (can skip log files).
3) Run the update_db.php script then run the install.php script.
4) Login to the admin area and update your settings (old settings are lost)
5) Change your cron job commands to run the scripts in the "cron" folder.
6) You will have to reapply any customizations you made to BitShop.

You should also delete the following files:

/inc/admin/login.inc.php
/inc/admin/tickconfig.inc.php
/inc/pages/status.inc.php
/sci/ajax_hack.php
/sci/callback.php
/clean_trans.php
/goxgrab/*
/install/*

All your database tables will remain in tact except for the Transactions table, which means your order history will be cleared by the update. The table with all your old order data will remain there unless you manually remove it, BitShop just wont use it anymore.

Also it's worth mentioning that I haven't had time to do any translations so I've only included the American and British English files in 1.0.7. I'm not really a great translator anyway, I use machine translation for most things. I would prefer if I could get some proper translations.

New version should be released some time in the next 12 hours. Just have to finish up a few last changes to the admin area then update the official BitShop website.

The next version will have basic support for physical items but there are a few reasons I have avoided it. There are already many shop scripts out there which have advanced support for physical items, but not many which provide advanced support for digital items and an automatic delivery system. I wanted to keep BitShop focused on digital goods because it was a good match for digital currency, that is also why I don't really want to add support for PayPal and other traditional payment gateways. The other main reason I didn't want to add support for physical items is because it's just not a very simple task when you take into account shipping costs. To do it properly requires a complicated system which can calculate shipping costs based on zip codes. I have no real motivation to do any of that when other cart software offers those functions and BitShop was always designed to only support digital items.

But I have decided I will add basic support for physical items since it's not that hard if I don't worry about calculating the shipping costs dynamically, which is why I say it's only basic support for physical items. The admin will be able to input the weight of the item and that will be used to calculate the shipping cost. In the settings the admin will also be able to change the how much the weight affects the shipping cost. The other new thing it will do is ask for the buyer shipping details during checkout. It's not the most advanced system in the world but it should get the job done for most people who want to sell physical items. Like I said I'm not really willing to spend a whole lot of time focusing on support for physical items but if anyone has any better ideas I'm listening.

I apologize for the delay once again, I had to work on another project the last couple of days. Back working on BitShop now and it definitely should be finished by the end of this week, there's not very much left to do now.

I believe it's been like that for a several months now, maybe they didn't have enough volume. XCN is still alive though, I will be finished my work on BitShop soon and I'll be able to work on the Cryptonite web wallet again. I've also added a way for BitShop to use XCN and other altcoins.

It's already done, most things are already done, most of the work left is boring stuff like translations or recoding a lot of the admin area to make it work properly with all the changes I've made to the rest of the code base.

The new version will support multiple payment gateways simultaneously (default payment gateway, Coinbase, and hopefully also GoCoin). The customer will have the option to choose what payment gateway they want to use during checkout (admin can enable/disable gateways in any combination). Each gateway may or may not support multiple currencies, for example GoCoin supports BTC, LTC, and DOGE but Coinbase only supports BTC. I haven't added support for GoCoin yet but I'll be doing that within the next few days. The default payment gateway also now has RPC support so you can accept what ever altcoin you want if you're running the altcoin daemon. All the payment gateway code is now entirely modular so that new payment gateways can be easily installed into BitShop without messing around with existing BitShop code. I was even thinking about adding a PayPal module but that would be kind of against the principles of BitShop.

New version is coming along nicely now, should be finished within a week. Sorry it's taking a bit longer than expected but it really is a huge update and it will be well worth the wait, trust me.

They've been around a while. I don't know why they had to use the exact same name and currency code, I tried to convince them to change it but they wouldn't. Their coin doesn't seem to be listed on any exchanges and seems to be dead anyway.

I always give support in this thread and to anyone who contacts me directly by using the contact form on the BitShop website, although some times it may take me a day or two to respond.

I am currently visiting a relative but I have my laptop with me and I'm working on BitShop when I can. The new version of BitShop should be released within a week or two. It's a major update with many new features, including a shopping cart which will allow users to purchase multiple items at the same time, a revamped payment gateway, support for daemon RPC's to allow the use of altcoins, support for physical items with shipping addresses and shipping costs, and a member area which will allow customers to log in and check their order history, download files and codes they have previously purchased, among other things. I'm trying to do it in a way that doesn't impinge on the fast and anonymous checkout process.

Seems to be a problem with the bitcoincharts.com API. Changing to bitstamp should fix the issue. And I will try to add something in the next version of BitShop which allows the use of an alternative exchange rate. I might actually look for an alternative to the bitcoincharts API because it doesn't seem to be super reliable and the formatting of their markets.json file is stupid.

Potentially. I'm trying to set up the foundations for it now so support for physical should be coming soon if not the next release.

As I mentioned a few posts back the core dev will be unavailable for a little while longer. I am currently working on the new version of BitShop but when that's done I plan to give the web wallet another shot.

For anyone running BitShop 1.0.6 and unable to get the coinbase API working, you can download a patch for that problem here.

Also I should mention that I have started work on 1.0.7 and I have many large plans. It's going to include many awesome new features which will take BitShop to a whole new level.

@juffer: you'll need to edit your database. The CodeData field in the Codes table is of type TINYTEXT which limits it to 255 characters. Change the type to TEXT or VARCHAR(length) to set your own size limit.

No I was assuming that we could do asymmetric encryption directly with the EC keypairs just like with RSA but it turns out that might not be true. I suppose we could use RSA but then the stealth addresses would need to be even longer than they already are, and they're already much longer than a normal Bitcoin address, so making them even longer seems untenable. If we could use the EC keypairs for asymmetric encryption then we would avoid that problem because those long stealth addresses already contain the EC public key. We still need that in order to generate Q' so we can't just get rid of it.

Well both of my methods transmit a random number, the difference is the way the number is encrypted. In the first scenario we simply use the public key of the payee to encrypt it and then the payee will use his private key to decrypt it. But in the second scenario the first shared secret is computed using ECDH as usual, but instead of using it to produce Q', we use it to encrypt the random number with a symmetric cipher.

But the flaw you mentioned does still apply to my second scenario because if the payer were to have their private key compromised it would allow anyone to calculate the first shared secret and then decrypt the metadata, allowing them to see the second shared secret, thus allowing them to calculate Q' using a brute force tactic in which they use a list of all known stealth addresses to see if they can produce Q'.

Ephemeral keypairs have the same problem if they get leaked, it's just that they are only used that one time and then thrown away, so it's harder to accidentally leak an ephem keypair. I'll have to think about this problem some more. As mentioned earlier, the first scenario isn't really a good way to go either. I think I understand the point tacotime was making now. EC cryptography can't produce a truly asymmetric encryption scheme so it cannot be used the same way as RSA.

That seems pretty stupid to me. Wouldn't it mean both parties have to be online at the same time in order to do this? ECDH seems like a much more elegant solution to me.