Pages:
Author

Topic: OpenEx: Fee shares Thread[close] - page 4. (Read 12838 times)

hero member
Activity: 686
Merit: 504
always the student, never the master.
December 16, 2013, 02:14:06 PM
Update please.

server 1 has arrived.

http://dev2.openex.pw

justin is tweaking our api and rpc on here.

pen testing is still ongoing on the old server, with the feeling we would merge both branches eventually.

http://dev.openex.pw

CPU's for our main webserver is supposed to arrive this week, and setup is supposed to take no more than 72 hours when they arrive. on the 13th, i got a letter from the company saying it would be no more than 10 days.

other than that there aren't really any updates of note, unless you want to hear about my personal life(i had the flu last week so i've been in the bed for the most part.) we're due for some good news. One glaring problem is the fact that we don't use ajax to update the trade page, which could be annoying for traders. we should probably make it use ajax or something, trying to investigate a solution that would be efficient but not wasteful. we only need it to refresh when there are new orders, which is probably a bit beyond our expertise but i'm sure we will figure something out. we have a week! :-) if all goes as planned, it wouldn't be much of a stretch to expect launch by early next week.

the development thread is here. https://bitcointalk.org/index.php?topic=320975.60
full member
Activity: 214
Merit: 100
December 16, 2013, 11:59:46 AM
Update please.
legendary
Activity: 2674
Merit: 2965
Terminated.
December 12, 2013, 05:35:51 PM
ETA for the exchange?
sr. member
Activity: 323
Merit: 250
December 11, 2013, 08:27:12 AM
Might want to change the title r3wt.
hero member
Activity: 686
Merit: 504
always the student, never the master.
December 11, 2013, 12:34:53 AM
The code in github looked to me to be a pretty simple implementation.  Have you done any scalability or other testing on it?  If you manage to get some decent volume out of the gate - which is quite possible given the demand and the state of other exchanges right now - do you have a plan to scale it and keep the wheels on the bus without going underwater for awhile like what the cryptsy folks are dealing with?  Are you going to have an API for bots?  What kind of load might that represent?  Trade execution times?  Queues? Transactions?  Rollback?  What if the site crashes?  How will you reconcile the trade activity, what if not all of your queries succeed, are you going to wait for support tickets and do it manually, but then what if you have 4000 support tickets and you don't have enough data to reconstruct the market state and replay transactions?, error handling, etc. etc. etc.

the trading system has been completely reworked, from the wallets up, with rollback and a history table we're working on order stacking and combining at the moment. were pretty confident we've solved the issues of the first implementation. these changes are not necessarily reflected in the repo. i mentioned in the post prior to yours that justin was working on the api.
newbie
Activity: 14
Merit: 0
December 11, 2013, 12:07:05 AM
The code in github looked to me to be a pretty simple implementation.  Have you done any scalability or other testing on it?  If you manage to get some decent volume out of the gate - which is quite possible given the demand and the state of other exchanges right now - do you have a plan to scale it and keep the wheels on the bus without going underwater for awhile like what the cryptsy folks are dealing with?  Are you going to have an API for bots?  What kind of load might that represent?  Trade execution times?  Queues? Transactions?  Rollback?  What if the site crashes?  How will you reconcile the trade activity, what if not all of your queries succeed, are you going to wait for support tickets and do it manually, but then what if you have 4000 support tickets and you don't have enough data to reconstruct the market state and replay transactions?, error handling, etc. etc. etc.
hero member
Activity: 686
Merit: 504
always the student, never the master.
December 10, 2013, 11:21:34 PM
penetration testing position has been filled.

still seeking an additional moderator/support staff. ability to speak both chinese and english is desired.

Is the code necessary to trading coins finished?



yes. the entire site is more or less complete. the trading has been done for some time. the server company is having trouble stocking the processors we need, but they delivered us a smaller, temporary server to test the site on until our server is ready. we should have the site moved over tomorrow and begin our final stretch of testing/tweaking. justin is almost finished with the api, we're extremely close, and its been frustrating. our server was supposed to be here last week, and its still not ready.
full member
Activity: 214
Merit: 100
December 10, 2013, 11:16:37 PM
penetration testing position has been filled.

still seeking an additional moderator/support staff. ability to speak both chinese and english is desired.

Is the code necessary to trading coins finished?

hero member
Activity: 686
Merit: 504
always the student, never the master.
December 07, 2013, 03:59:38 PM
penetration testing position has been filled.

still seeking an additional moderator/support staff. ability to speak both chinese and english is desired.
hero member
Activity: 686
Merit: 504
always the student, never the master.
December 05, 2013, 07:11:11 PM
The share model was confusing some people, including the staff so i will attempt to explain it in further detail

Site revenue as calculated at the end of each weekly period.


20% Fee Shares- 20% of weekly revenue is split evenly amongst each fee share. total shares ever will be 1000.

20% site-20% of weekly revenue is tucked away for site operational costs.

20% administrators- 20% of weekly revenue is split evenly between justin and i(50-50)

40% staff - 40% of weekly revenue is split evenly amongst staff members.



If you are confused at all, or could assist me in explaining this further, let me know.
hero member
Activity: 686
Merit: 504
always the student, never the master.
December 05, 2013, 01:45:54 PM
All of this really doesn't inspire confidence in the idea of trusting you people with my money!

well i'm sorry, but if you are expecting a company that will lie and put on a facade for you, you can go invest in BFL. If you want a company that's Open and Honest, we can talk.

r3wt
sr. member
Activity: 476
Merit: 250
December 05, 2013, 05:56:48 AM
All of this really doesn't inspire confidence in the idea of trusting you people with my money!
legendary
Activity: 1030
Merit: 1000
December 04, 2013, 02:27:47 PM
justin has shown up people, and has paid the BTC for wtman's shares.

Code:
Status: 0/unconfirmed
Date: 12/4/2013 12:00
From: unknown
To: 1Ck2N2rAkUW5puHwV613bxL4andygoPFcr (own address, label: r3wtnew)
Credit: 1.4996 BTC
Net amount: +1.4996 BTC
Transaction ID: 5ba5895273fbe29ed6d9012df96540acc68a437fb4e516a3ef17f3e56dee0a41


note that .5 was an incentive for Justin for his hardwork on the exchange, so the amount above is correct.

Wtman also sent 1 btc, and has asked for an additional 40 shares instead of being reimbursed.

Code:
Status: 0/unconfirmed
Date: 12/4/2013 11:56
From: unknown
To: 1D3zMQmXPsfaQFdscEN93BUhshm5xwJYmf (own address, label: wtman2)
Credit: 1.00 BTC
Net amount: +1.00 BTC
Transaction ID: d9a9e6d7b83f57d0bff63632a190d04f1e89989226fc49ee4b39a1455e60343e




Confirmed
full member
Activity: 136
Merit: 100
December 04, 2013, 02:25:02 PM
justin has shown up people, and has paid the BTC for wtman's shares.

Code:
Status: 0/unconfirmed
Date: 12/4/2013 12:00
From: unknown
To: 1Ck2N2rAkUW5puHwV613bxL4andygoPFcr (own address, label: r3wtnew)
Credit: 1.4996 BTC
Net amount: +1.4996 BTC
Transaction ID: 5ba5895273fbe29ed6d9012df96540acc68a437fb4e516a3ef17f3e56dee0a41


note that .5 was an incentive for Justin for his hardwork on the exchange, so the amount above is correct.

Wtman also sent 1 btc, and has asked for an additional 40 shares instead of being reimbursed.

Code:
Status: 0/unconfirmed
Date: 12/4/2013 11:56
From: unknown
To: 1D3zMQmXPsfaQFdscEN93BUhshm5xwJYmf (own address, label: wtman2)
Credit: 1.00 BTC
Net amount: +1.00 BTC
Transaction ID: d9a9e6d7b83f57d0bff63632a190d04f1e89989226fc49ee4b39a1455e60343e




Confirm.
full member
Activity: 136
Merit: 100
December 04, 2013, 02:20:51 PM
The plot thickens!

What the hell does a 14 year old have to do to get a restraining order put out against him? How did you even manage that?

Her mom got pissed off because her daughter liked me more than her own mother LOL
That is a long story short.
legendary
Activity: 980
Merit: 1000
December 04, 2013, 02:17:22 PM
Well, that was the most short lived bit of drama ever.

Carry on...
hero member
Activity: 686
Merit: 504
always the student, never the master.
December 04, 2013, 02:16:12 PM
justin has shown up people, and has paid the BTC for wtman's shares.

Code:
Status: 0/unconfirmed
Date: 12/4/2013 12:00
From: unknown
To: 1Ck2N2rAkUW5puHwV613bxL4andygoPFcr (own address, label: r3wtnew)
Credit: 1.4996 BTC
Net amount: +1.4996 BTC
Transaction ID: 5ba5895273fbe29ed6d9012df96540acc68a437fb4e516a3ef17f3e56dee0a41


note that .5 was an incentive for Justin for his hardwork on the exchange, so the amount above is correct.

Wtman also sent 1 btc, and has asked for an additional 40 shares instead of being reimbursed.

Code:
Status: 0/unconfirmed
Date: 12/4/2013 11:56
From: unknown
To: 1D3zMQmXPsfaQFdscEN93BUhshm5xwJYmf (own address, label: wtman2)
Credit: 1.00 BTC
Net amount: +1.00 BTC
Transaction ID: d9a9e6d7b83f57d0bff63632a190d04f1e89989226fc49ee4b39a1455e60343e


legendary
Activity: 980
Merit: 1000
December 04, 2013, 02:13:01 PM
The plot thickens!

What the hell does a 14 year old have to do to get a restraining order put out against him? How did you even manage that?
full member
Activity: 136
Merit: 100
December 04, 2013, 02:09:59 PM
Thanks for the laughs. Quality status updates on there! Cheesy


No probz :3
legendary
Activity: 980
Merit: 1000
December 04, 2013, 02:03:57 PM
Thanks for the laughs. Quality status updates on there! Cheesy
Pages:
Jump to: