They are live! They even got some press coverage:
http://www.zippycart.com/ecommerce-news/2796-ecommerce-solution-camp-bx-makes-bitcoin-legitimate.html
http://venturebeat.com/2011/07/07/camp-bx-bitcoin/
Also, they just announced a new affiliate program. The deal is the same as TradeHill.com, 10% off your trading fees if you sign up through an affiliate link such as this one (mine): https://CampBX.com/register.php?r=mdslj19rhcD
If you registered before the affiliate program started, email them, and they will get you the discount. (At least, they did it for me).
Their website claims they will disable your affiliate link if people complain that you are spamming it everywhere, so don't do that.
Topic: Camp BX Platform in Beta: Margin Trading, Short Selling, and Advanced Orders (Read 14213 times)
July 08, 2011, 04:41:58 PM
July 04, 2011, 10:29:50 AM
will lauch in 9 hours
July 03, 2011, 11:02:26 PM
Happy 4th of July everyone!
Our CampBX Testnet site has seen a fair amount of activity in its 11 day-old life. Our big thank you to users who alleviated the early Testcoin-shortage by selling massive lots.
Over past week, testnet had:
~90,000 coins traded
~1,400 individual orders executed
18 Usability tweaks implemented
1 bug fixed
3 Sev-3 security fixes implemented after McAfee Secure scan
We are planning to always keep the CampBX testnet available to users, where pro-traders can test new trading strategies without risk, and new users can get a glimpse of Bitcoin world.
However, we are temporarily going to disable testnet site for one week so that we can focus our team's energy in managing the livenet launch. Don't worry, your account info and coins will all be there when testnet comes back online next week.
Thank you all for your participation and for believing in Camp BX!
Stay tuned for our launch on July 5th...
Keyur
Our CampBX Testnet site has seen a fair amount of activity in its 11 day-old life. Our big thank you to users who alleviated the early Testcoin-shortage by selling massive lots.
Over past week, testnet had:
~90,000 coins traded
~1,400 individual orders executed
18 Usability tweaks implemented
1 bug fixed
3 Sev-3 security fixes implemented after McAfee Secure scan
We are planning to always keep the CampBX testnet available to users, where pro-traders can test new trading strategies without risk, and new users can get a glimpse of Bitcoin world.
However, we are temporarily going to disable testnet site for one week so that we can focus our team's energy in managing the livenet launch. Don't worry, your account info and coins will all be there when testnet comes back online next week.
Thank you all for your participation and for believing in Camp BX!
Stay tuned for our launch on July 5th...
Keyur
June 26, 2011, 01:28:04 PM
I miss a json api.
The API is ready, but we are planning to roll it out after the launch. Stay tuned!Good. That's interesting for you too, since it reduces traffic.
June 26, 2011, 01:17:29 PM
I miss a json api.
Dinox,
The API is ready, but we are planning to roll it out after the launch. Stay tuned!
Thank you,
Keyur
June 25, 2011, 07:06:57 PM
I miss a json api.
June 25, 2011, 05:57:42 PM
Quick update:
Some bug-fixes and additional feature requests have been tested and pushed in production:
1) BTC Deposit and Withdrawal records appear in the timeline now
2) Option to export entire timeline as a CSV file
3) Open orders now sorted by price, not date
4) A favicon has been added
Thank you to Holliday, JasonP, Fwaggle, and FreeMoney for your excellent ideas!
Some more feature requests from JasonP, Hazek, and Herman are in progress and we hope to be able to implement them soon!
Thank you,
Keyur
Some bug-fixes and additional feature requests have been tested and pushed in production:
1) BTC Deposit and Withdrawal records appear in the timeline now
2) Option to export entire timeline as a CSV file
3) Open orders now sorted by price, not date
4) A favicon has been added
Thank you to Holliday, JasonP, Fwaggle, and FreeMoney for your excellent ideas!
Some more feature requests from JasonP, Hazek, and Herman are in progress and we hope to be able to implement them soon!
Thank you,
Keyur
June 25, 2011, 12:43:10 PM
I tried several times yesterday, and was able to reproduce it each time. Today, I logged in and withdrew 1k BTC without issue.
I understand - this might have been due to one of the team members tweaking the files around the same time you attempted withdrawals.
June 25, 2011, 02:46:38 AM
Holliday,
Comma and 0.25 orders issues have been resolved.
Unfortunately we were not able to reproduce the 1000 BTC withdrawal issue. Can you please retry and see if you still have any troubles with the transfer?
Thank you,
- Keyur
Comma and 0.25 orders issues have been resolved.
Unfortunately we were not able to reproduce the 1000 BTC withdrawal issue. Can you please retry and see if you still have any troubles with the transfer?
Thank you,
- Keyur
June 24, 2011, 09:01:57 PM
Holliday,
Looking at the issues now. Will keep you posted.
Thank you,
Keyur
Looking at the issues now. Will keep you posted.
Thank you,
Keyur
June 24, 2011, 08:34:35 PM
Good catch Imperi! We took out the culprit button.
Wow that was fast!
June 24, 2011, 08:31:34 PM
I forgot my pass... is there any way to reset it? Sorry if it was already said somewhere in the thread.
edit:
Figured out. I do see an issue though.
The "Reset" button makes the window leave when you push it, without resetting the password. You must click "submit" which is really unclear.
edit:
Figured out. I do see an issue though.
The "Reset" button makes the window leave when you push it, without resetting the password. You must click "submit" which is really unclear.
Good catch Imperi! We took out the culprit button.
June 24, 2011, 08:27:53 PM
Have not read the thread but 1st observations are:
1. Collecting account info in registration over http == bad
2. Registration says, now go logon; come-on why didnt you set the session cookie?
3. Collecting user id and password over http for logon means it can be taken.
4. Session cookies over http mean they can be taken even if you send creds over https.
5. Tried to logon after registration and was told account would lockout in 5 tries, sure I entered right password why cant I log in.
6. Tried to logon again still said bad password and lockout in 5 times, shouldnt it be 4?
1. Collecting account info in registration over http == bad
2. Registration says, now go logon; come-on why didnt you set the session cookie?
3. Collecting user id and password over http for logon means it can be taken.
4. Session cookies over http mean they can be taken even if you send creds over https.
5. Tried to logon after registration and was told account would lockout in 5 tries, sure I entered right password why cant I log in.
6. Tried to logon again still said bad password and lockout in 5 times, shouldnt it be 4?
More:
1. Workflow for password reset is broken, after entering my reset password was redirected to the reset password form, entered user id again got new password again, had to close that tab and navigate back since this form looks like it was intended to be in a layer.
2. My IP was banned, I tried under 10 times to log in; glad you ban on suspicious activity but I wasnt doing anything other than trying to log on, check your thresholds.
3. No account providence stuff was done, if there is money in the accounts you want to make sure they can get back in if they mess up so you need to do this.
4. Learn from the mt gox fiasco, collect enough information you can validate providence if you have to "recover" accounts.
If you would like to discuss common authn mistakes in implementations like these PM me and we can discuss in detail.
SCG,
The livenet cookies and form submissions will be over HTTPS. The SSL is assigned to "campbx.com", and using it on "testnet.campbx.com" triggers ominous-sounding messages in many browsers. Due to this reason we are on HTTP for the trial.
Account providence fields are a good idea - we have added them to the feature list.
Your IP ban has been reset so you should be good to login again. The password is not allowed quotes / apostrophes.
Thank you,
Keyur
June 24, 2011, 08:22:19 PM
I forgot my pass... is there any way to reset it? Sorry if it was already said somewhere in the thread.
edit:
Figured out. I do see an issue though.
The "Reset" button makes the window leave when you push it, without resetting the password. You must click "submit" which is really unclear.
edit:
Figured out. I do see an issue though.
The "Reset" button makes the window leave when you push it, without resetting the password. You must click "submit" which is really unclear.
June 24, 2011, 08:17:10 PM
So, I made quite a few trades and I noticed that I can't fill orders at $.25 per BTC, but the orders exist.
Also, I can only view a certain amount of my trade history, what if I wanted to view all of it?
Is there a reason trades are limited to 500 BTC per trade? It gets tiresome reentering the same price over and over again.
Also, it would be sweet if there was a way to click to buy or sell from the market explorer.
I've been having fun with your market the past few days!
I hope my playing around has helped you in the testing phase. I think it's great that you opened up to the testnet first!
Edit: It would be nice to see the cumulative amount of fees I've paid.
Also, I can only view a certain amount of my trade history, what if I wanted to view all of it?
Is there a reason trades are limited to 500 BTC per trade? It gets tiresome reentering the same price over and over again.
Also, it would be sweet if there was a way to click to buy or sell from the market explorer.
I've been having fun with your market the past few days!
I hope my playing around has helped you in the testing phase. I think it's great that you opened up to the testnet first! Edit: It would be nice to see the cumulative amount of fees I've paid.
Holliday,
Thank you bringing the liquidity! We are glad you are stretching the system and helping us in the process. What you mentioned about not being able to fill orders at 0.25 may be the first bug in the code. I wrote that piece of the code, so I should be able to fix that for you in a little while.
500 BTC is just an internal limit to prevent a meltdown trade that we are all too familiar with now. On livenet, that amounts to ~$10,000 per trade. We can raise the limit to 1,000 here but going beyond this brings more dangers than opportunities for a vast majority of traders.
As for the history, We will provide a CSV file download option. That will also give you the ability to do all kinds of post-trade analysis including commissions-sigma that you are looking for. The limit on how much history is displayed is to limit performance impact under heavy usage.
Good chatting with you today!
Keyur
June 24, 2011, 07:54:34 PM
Have not read the thread but 1st observations are:
1. Collecting account info in registration over http == bad
2. Registration says, now go logon; come-on why didnt you set the session cookie?
3. Collecting user id and password over http for logon means it can be taken.
4. Session cookies over http mean they can be taken even if you send creds over https.
5. Tried to logon after registration and was told account would lockout in 5 tries, sure I entered right password why cant I log in.
6. Tried to logon again still said bad password and lockout in 5 times, shouldnt it be 4?
1. Collecting account info in registration over http == bad
2. Registration says, now go logon; come-on why didnt you set the session cookie?
3. Collecting user id and password over http for logon means it can be taken.
4. Session cookies over http mean they can be taken even if you send creds over https.
5. Tried to logon after registration and was told account would lockout in 5 tries, sure I entered right password why cant I log in.
6. Tried to logon again still said bad password and lockout in 5 times, shouldnt it be 4?
More:
1. Workflow for password reset is broken, after entering my reset password was redirected to the reset password form, entered user id again got new password again, had to close that tab and navigate back since this form looks like it was intended to be in a layer.
2. My IP was banned, I tried under 10 times to log in; glad you ban on suspicious activity but I wasnt doing anything other than trying to log on, check your thresholds.
3. No account providence stuff was done, if there is money in the accounts you want to make sure they can get back in if they mess up so you need to do this.
4. Learn from the mt gox fiasco, collect enough information you can validate providence if you have to "recover" accounts.
If you would like to discuss common authn mistakes in implementations like these PM me and we can discuss in detail.
June 24, 2011, 07:40:12 PM
Have not read the thread but 1st observations are:
1. Collecting account info in registration over http == bad
2. Registration says, now go logon; come-on why didnt you set the session cookie?
3. Collecting user id and password over http for logon means it can be taken.
4. Session cookies over http mean they can be taken even if you send creds over https.
5. Tried to logon after registration and was told account would lockout in 5 tries, sure I entered right password why cant I log in.
6. Tried to logon again still said bad password and lockout in 5 times, shouldnt it be 4?
1. Collecting account info in registration over http == bad
2. Registration says, now go logon; come-on why didnt you set the session cookie?
3. Collecting user id and password over http for logon means it can be taken.
4. Session cookies over http mean they can be taken even if you send creds over https.
5. Tried to logon after registration and was told account would lockout in 5 tries, sure I entered right password why cant I log in.
6. Tried to logon again still said bad password and lockout in 5 times, shouldnt it be 4?
June 24, 2011, 12:10:22 AM
This looks like a truly professional job. Keep up the good work, and I hope to see how it will perform in real life
Keep up the good work!
Keep up the good work!
June 23, 2011, 02:46:17 PM
I've got to say you're replies are very accommodating and professional which excites me to soon your exchange live and running.
June 23, 2011, 02:35:06 PM
Will there be a transaction history? I don't mean for the trades made on the site, but a list of deposits/withdraws of dollars/bitcoins.
Holliday,
Yes, we are implementing fund movement history later this week for following three transactions:
1) Bitcoin Withdrawals
2) USD Deposits
3) USD Withdrawals
We will not be able to show Bitcoin deposits, because it requires an un-elegant technical solution. This seemingly simple feature will have to wait for a mod to the core Bitcoin client.
Thank you,
Keyur
I don't understand. You need to know how much is deposited in order to credit it. Why can't you display it?
FM,
We don't see timestamps of individual deposit transactions. There is a much more elegant solution planned that will take some time to implement.
Hope this makes sense,
Keyur
So there will be a record of deposits, but not in the 'history' section since they aren't on a timeline?
Would it be so bad to list the time that the funds were credited to the account instead of the transaction being sent?
Yes we can do that and show an approximate time for the deposits. We will roll it out this weekend.
Thank you,
Keyur
Jump to: