I've been thinking of creating a Canadian-only exchange. This looks like quite an interesting project to help me do so.
Topic: Intersango exchange (formerly Britcoin) - page 15. (Read 75372 times)
Yeah Dooglus, nicely done.
I've been thinking of creating a Canadian-only exchange. This looks like quite an interesting project to help me do so.
I've been thinking of creating a Canadian-only exchange. This looks like quite an interesting project to help me do so.
Good work dooglus! 
Thanks dooglus for your help. We sent you 10 BC for your help 
After some testing, we're going to pull that change.
Did you get my email dooglus?
After some testing, we're going to pull that change.
Did you get my email dooglus?
BTW is anyone in London and want to meet up later? We might get a pizza or something with a few other community members.
Would love to meet up one day, but split between Brighton and being somewhat nomadic currently.
Quick question about Britcoin BTC deposits.
Britcoin issues a new deposit address whenever it detects a transfer to that address. Which is good.
What happens if I use that address twice; i.e. I fund it from two sources? Will Britcoin accept multiple transfers to that one address, or do I have to use the newly issued address?
Britcoin issues a new deposit address whenever it detects a transfer to that address. Which is good.
What happens if I use that address twice; i.e. I fund it from two sources? Will Britcoin accept multiple transfers to that one address, or do I have to use the newly issued address?
This is exactly what I refer to. Is genjix aware of this?
I don't know but he's posted on this thread since I've been pointing the problem out.
I just noticed another bug. https://britcoin.co.uk/api/ticker.php shows
Code:
{"ticker": {"vol": 682.0541134, "buy": 10.61, "sell": 10.79, "last": 0.5}}
where 'last' is meant to the be price of the last trade made. It's been stuck at 0.5 for hours now while trades have been made all between 10.6 and 10.8 GBP/BTC.
It turns out that the SQL query is wrong, and it's really showing the price of the first transaction not the last one.
Fix here: https://gitorious.org/~dooglus/intersango/dooglus-intersango/commit/26f2cfa89affcc60cb4de92479e96847cc1afe52
which chart are you referring to?
This chart: http://bitcoincharts.com/charts/britcoinGBP#rg60zczsg2011-06-23zeg2011-06-23ztgOzm1g10zm2g25
See also https://britcoin.co.uk/api/getTrades.php for numerical data:
Code:
{"date": 1308779642, "price": 10.1702, "amount": 0.94},
{"date": 1308780181, "price": 10.2041, "amount": 0.00599566},
{"date": 1308780782, "price": 500.0000, "amount": 0.01},
{"date": 1308780841, "price": 5000.0000, "amount": 0.001},
{"date": 1308781381, "price": 10.2041, "amount": 0.48400469},
{"date": 1308781441, "price": 10.0000, "amount": 0.8},
Code:
1308780782 -> Wed Jun 22 15:13:02 2011 PST
1308780841 -> Wed Jun 22 15:14:01 2011 PST
so about 3 hours ago.
I suspect someone read my posts here about a bug that causes all trades here to happen at the rate posted by new orders rather than existing ones, and wanted to try it out.
If you attempt to buy 0.001 coins at 5000 BTC/GBP, you will be matched at that rate. You can pay as much as you like. That's the bug my patch fixes ( see https://gitorious.org/~dooglus/intersango/dooglus-intersango/commit/98961ecd84e6d8da2e7f4df3d15a90f4e1534dcb for the patch ).
Looking back a bit, it happened too:
Code:
{"date": 1308743881, "price": 10.0000, "amount": 0.06},
{"date": 1308746401, "price": 9.8000, "amount": 1},
{"date": 1308747301, "price": 270.2703, "amount": 0.111},
{"date": 1308747541, "price": 9.7600, "amount": 0.01},
{"date": 1308747541, "price": 9.7600, "amount": 0.01},
Somebody paid $27 for 0.111 BTC at Wed Jun 22 05:55:01 2011 PST - because that's what they asked for.
http://bitcoincharts.com/charts/britcoinGBP#rg60zigDailyzczsg2011-06-13zeg2011-06-21ztgOzm1g10zm2g25 shows people also paid far too much for BTC on 13-Jun and 21-Jun.
This is exactly what I refer to. Is genjix aware of this?
BTW is anyone in London and want to meet up later? We might get a pizza or something with a few other community members.
i'll be back in london next week, up for some good pizza for sure
which chart are you referring to?
This chart: http://bitcoincharts.com/charts/britcoinGBP#rg60zczsg2011-06-23zeg2011-06-23ztgOzm1g10zm2g25
See also https://britcoin.co.uk/api/getTrades.php for numerical data:
Code:
{"date": 1308779642, "price": 10.1702, "amount": 0.94},
{"date": 1308780181, "price": 10.2041, "amount": 0.00599566},
{"date": 1308780782, "price": 500.0000, "amount": 0.01},
{"date": 1308780841, "price": 5000.0000, "amount": 0.001},
{"date": 1308781381, "price": 10.2041, "amount": 0.48400469},
{"date": 1308781441, "price": 10.0000, "amount": 0.8},
Code:
1308780782 -> Wed Jun 22 15:13:02 2011 PST
1308780841 -> Wed Jun 22 15:14:01 2011 PST
so about 3 hours ago.
I suspect someone read my posts here about a bug that causes all trades here to happen at the rate posted by new orders rather than existing ones, and wanted to try it out.
If you attempt to buy 0.001 coins at 5000 BTC/GBP, you will be matched at that rate. You can pay as much as you like. That's the bug my patch fixes ( see https://gitorious.org/~dooglus/intersango/dooglus-intersango/commit/98961ecd84e6d8da2e7f4df3d15a90f4e1534dcb for the patch ).
Looking back a bit, it happened too:
Code:
{"date": 1308743881, "price": 10.0000, "amount": 0.06},
{"date": 1308746401, "price": 9.8000, "amount": 1},
{"date": 1308747301, "price": 270.2703, "amount": 0.111},
{"date": 1308747541, "price": 9.7600, "amount": 0.01},
{"date": 1308747541, "price": 9.7600, "amount": 0.01},
Somebody paid $27 for 0.111 BTC at Wed Jun 22 05:55:01 2011 PST - because that's what they asked for.
http://bitcoincharts.com/charts/britcoinGBP#rg60zigDailyzczsg2011-06-13zeg2011-06-21ztgOzm1g10zm2g25 shows people also paid far too much for BTC on 13-Jun and 21-Jun.
which chart are you referring to?
Recently there have been unrealistic trades, apparently, shown on BitCoin Charts. Recently there were BitCoins sold for 5000 each, apparently?
Is something wrong with the site (Charts or Britcoin?) These can't be right.
Is something wrong with the site (Charts or Britcoin?) These can't be right.
Quote from: genjix
Yep. This will be fixed by the end of the day. We got the problem fixed.
Thanks for sorting out the 13th June problem, Already bought and withdrew some bitcoins yayy!
Can you give us an update about the payments on the 13th?
Have you managed to access them yet and do you know when you'll be able to credit the accounts? also, will the 30 day notice from the bank affect these payments in any way?
Many thanks
Have you managed to access them yet and do you know when you'll be able to credit the accounts? also, will the 30 day notice from the bank affect these payments in any way?
Many thanks
Yep. This will be fixed by the end of the day. We got the problem fixed.
Can you give us an update about the payments on the 13th?
Have you managed to access them yet and do you know when you'll be able to credit the accounts? also, will the 30 day notice from the bank affect these payments in any way?
Many thanks
Have you managed to access them yet and do you know when you'll be able to credit the accounts? also, will the 30 day notice from the bank affect these payments in any way?
Many thanks
BTW is anyone in London and want to meet up later? We might get a pizza or something with a few other community members.
Bit far for me I'm in norwich
Would be good to arrange a bitcoin boffin meet though I've taken a look at the cron/process_orders.php code and compared it to the doc/process_order documentation. It turns out that the code isn't doing what the documentation says it is [...]
I made a clone of the git repository and made some changes to fix these problems:
1) process new book entries in the order they arrive
2) chew through the existing order book matching best prices first
3) when a new order meets an existing order, use the price specified in the existing order, so if there are cheap coins available, it's impossible to buy expensive coins before the cheap coins are gone.
https://gitorious.org/~dooglus/intersango/dooglus-intersango
I've done some basic testing on my local install and it seems fine, but please review the code!
One question:
If you place an order "I want to buy 10 bitcoins for $100" and it turns out there are coins available for less, would you want to
(a) buy 10 bitcoins and get change from your $100, or
(b) spend $100 and get more than 10 bitcoins
Likewise, if I say "sell 10 bitcoins for $100" and someone wants to buy them for more, should it:
(a) sell until you have $100 and keep some bitcoins around, or
(b) sell all the bitcoins and give you more than $100
It strikes me that in both cases the sensible thing to do is option (b) - don't worry about exceeding what the user said they wanted to get, keep going until they've traded away everything they said they wanted to trade.
Right?
Currently the code is stopping early, doing option (a) in effect when lots of small orders are matched, and option (b) when your order is matched by a single large order.
BTW is anyone in London and want to meet up later? We might get a pizza or something with a few other community members.
There's no letter. It's been an ongoing thing with LLoyds for nearly 2 weeks now everyday. They think our business is too high risk for them, so we've been given a 30 day notice to move to another bank.
Anyway, it's too difficult answering every small message here otherwise I/we won't get any work done. I think everything should be OK since we have several contingency plans already in place from before. The new setup will either be rescinding the LLoyds notice (somewhat likely) or registering under a sole trader before forming a new LL to move the account to. Currently Britcoin runs under the Bitcoin Consultancy umbrella, so we'd be maybe looking to form a new platform for Britcoin (either Britcoin or an exchange group under Intersango) and find a backer.
I'm trying to stay away from backers if possible since that could mean turning the Britcoin platform into a 'product' rather than a service, and mean making the sourcecode closed. Wherever possible I want to stay away from making political decisions that negatively affect the quality of the site... But it might be something my hand will be forced to do. I've already been fighting a ton with everyone to keep this software as an open platform but it's exhausting. We have the new exchange in the works which we plan to roll out (intersango 2). I hope it's opensourced.
Anyway, it's too difficult answering every small message here otherwise I/we won't get any work done. I think everything should be OK since we have several contingency plans already in place from before. The new setup will either be rescinding the LLoyds notice (somewhat likely) or registering under a sole trader before forming a new LL to move the account to. Currently Britcoin runs under the Bitcoin Consultancy umbrella, so we'd be maybe looking to form a new platform for Britcoin (either Britcoin or an exchange group under Intersango) and find a backer.
I'm trying to stay away from backers if possible since that could mean turning the Britcoin platform into a 'product' rather than a service, and mean making the sourcecode closed. Wherever possible I want to stay away from making political decisions that negatively affect the quality of the site... But it might be something my hand will be forced to do. I've already been fighting a ton with everyone to keep this software as an open platform but it's exhausting. We have the new exchange in the works which we plan to roll out (intersango 2). I hope it's opensourced.
Did lloyds say why they're closing the account?
Feel free to post a scan of the letter, genjix...
Did lloyds say why they're closing the account?
I can somewhat understand their suspicions, but there's no fraud and you're not a business. If they have no evidence of any wrongdoing then it sounds like they're just being petty.
I can somewhat understand their suspicions, but there's no fraud and you're not a business. If they have no evidence of any wrongdoing then it sounds like they're just being petty.
Jump to: