|
I did not put any BTC into Britcoin at all and people are trading sucessfully.
|
|
|
|
|
Kensington at 20:30
* Genjix
* Lumos
* Lyspooner
We're meeting up because they want to put down deposits on Britcoin.co.uk, but we will turn this into a general meetup if anybody wants to come along. Be good to swap notes & share projects.
Cya
|
|
|
|
|
Enjoy your Coca-Cola laced with Cyanide + Anthrax
|
|
|
|
|
Yep, I get why it's a tree. But I'm wondering if there's a way to prettify it into a list like on my local machine.
|
|
|
|
How did you expect it to look?
Like the local machine (2nd one). I'm not making any changes there. |
|
|
|
|
>put in a couple grand for a site
That part.
However are you based in the US? Because I must warn you that you will have a major competitor in that market in addition to MtGox.
|
|
|
|
|
You're not being very realistic and depending on your expertise/requirements I could set you up for far less. Although it would be an operation you'd have to be actively involved in.
|
|
|
|
Shame some of the values on the exchange are so wild as it really skews the average.
OK, as per a few people's suggestions, it now uses the best rate. |
|
|
|
My workflow working on my Bitcoin site is: * Fetch encrypted database from server to localhost, unencrypt and load. * Add new features to local machine & test. * Push changes to gitorious (git push). * Login to remote server and pull changes (git pull). But my graph looks screwy: * d095816 (HEAD, master) Merge branch 'master' of git://gitorious.org/intersango/m
|\
| * 26810c9 (origin/master, origin/HEAD) force fixed precision in exchange rates SQL
* | 85590e6 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 2cc7743 fixed conversion function to stop float rounding errors.
* | f354456 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * f61ca2e changed exchange rate wording to reflect new alg.
* | 37af61e Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 08ec5ac fixed decimal places for exchanger.
| * ebc9a87 per nanotube's suggestion: switch buy to show sell rates & vice versa.
* | 607d762 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 59080d5 per nanotube's suggestion, use best rate for calc rate.
| * 3996ad3 best rates go at the top.
| * 4a29854 reformatted exchange rate SQL.
* | 793fdf5 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * fdd322a Ability to cancel requests as well as stricter viewing permissions.
| * e140119 protect viewing orders from outside intruders.
| * 69d49b0 cast to string before comparison.
| * dbcb489 fixed typo preventing orders showing up
* | 083d928 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 3770477 fix broken require path.
| * 7de5a0b moved into bank subdir. off by default to protected against user error.
* | 6341d52 Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
| * 09e2947 withdrawal script to GBP bank.
* | 341c06d Merge branch 'master' of git://gitorious.org/intersango/master
|\ \
| |/
How can I fix that? On my local machine it shows: * 26810c9 (HEAD, origin/master, master) force fixed precision in exchange rates SQL.
* 2cc7743 fixed conversion function to stop float rounding errors.
* f61ca2e changed exchange rate wording to reflect new alg.
* 08ec5ac fixed decimal places for exchanger.
* ebc9a87 per nanotube's suggestion: switch buy to show sell rates & vice versa.
* 59080d5 per nanotube's suggestion, use best rate for calc rate.
* 3996ad3 best rates go at the top.
* 4a29854 reformatted exchange rate SQL.
* fdd322a Ability to cancel requests as well as stricter viewing permissions.
* e140119 protect viewing orders from outside intruders.
* 69d49b0 cast to string before comparison.
* dbcb489 fixed typo preventing orders showing up
* 3770477 fix broken require path.
* 7de5a0b moved into bank subdir. off by default to protected against user error.
* 09e2947 withdrawal script to GBP bank.
* f066cf4 denominate all costs in terms of bitcoins.
* bdabf2d verification for bitcoin deposits are now instant.
* 4993f8c synchronise funds laying about.
* ee40599 actually perform query for real.
* ca1cf94 take command line argument.
* d170902 just to be safe.
* a82b1b1 stop it erroring on localhost.
* 5ff5220 actually perform bitcoin withdrawls now.
* de88367 verify only allows deposits.
* b90ec2b add to system in summa the unverified withdrawals.
* 50c2faa sub not add.
* dc719c1 improved summa algorithm
* c3e3ce9 moved missing function back out.
* 5988fe6 fixed missing function.
* 99c7d65 fix GMP problem behaviour.
|
|
|
|
And why do I defend floats: because simple things should be simple. Using GMP/BCMATH is overkill for 98% of what bitcoin JSON-RPC users will be doing.
As an aside: Using GMP (or similar) is overkill for two big reasons: - We already link with and use OpenSSL's bignum (CBigNum), so there is no need for an additional library for Big Maths
- It's just silly to want GMP when we already handle money properly internally, as int64. The only issues present are interface issues, and you don't need to link with GMP in order to display an int64 with a decimal point somewhere in the middle.
My Bitcoin branch doesn't use GMP. It's simply a change to AmountFromValue, ValueFromAmount and other functions that weren't using those helper methods. They're referring to me using GMP in PHP which I use for a range of reasons. Namely PHP not always having 64 bit ints: http://stackoverflow.com/questions/864058/how-to-have-64-bit-integer-on-php |
|
|
|
|
I thought long and hard about this and in the end decided against it.
If I'm running an exchange and I have jon, bill and dave all handling various currencies then I must trust them not to make an exchange/be a scammer. In the end I decided going with the many various exchanges is the best plan.
|
|
|
|
|
If you manage to gather lots of IVs then you can use ones that are the same/similar to do a statistical attack to discover the secret key. This is how WEP is cracked because it's IV is only 24 bit, and that's not long enough to ensure that the same key isn't used twice. There's also another flaw whereby you can inject special packets to make the AP spew IVs but that's another story :p
|
|
|
|
I own Britcoin and our source code is open. If you contact me then I can get you setup for a small fee as I'm doing with CCCMikey. The more people we have using this same software, the easier I can turn it into a safe, secure, easy to install piece of kit for setting up a Bitcoin exchange. Then we'll have lots of exchanges. |
|
|
|
|
YES
Pay him all the cash already you stingy cunts! Do you know how much effort has gone into that quality video?
He's gone beyond what was expected IMO. Too many people offering bounties on these forums and then not paying up after/changing their terms.
|
|
|
|
|
Pay him all the cash already you stingy cunts! Do you know how much effort has gone into that quality video?
He's gone beyond what was expected IMO. Too many people offering bounties on these forums and then not paying up after/changing their terms.
|
|
|
|
|
Show Posts
