The 'amount' column in the 'transactions' view isn't resizable, and doesn't fit in a value I recently sent.
xxx.xxxxxxxx BTC is ok, but -xxx.xxxxxxxx BTC doesn't fit, and I see xxx.xxxxx... instead (dots replacing the last 3 digits of the amount)
Three figure sums probably aren't all that uncommon to be sending, and it looks pretty ugly when the value doesn't fit in the box.
|
|
|
We're back online.
The order matching won't start happening until 9pm server time, to give users a chance to cancel any outstanding orders.
The price hasn't moved significantly while the exchange was down, but it seems only polite to give people a chance to cancel orders that they may not have intended to leave on the exchange.
|
|
|
What is the technical difficulty?
It's a filesystem corruption issue. We will have to restore from backup. It appears that this was a hardware failure. The bitcoin wallet wasn't compromised.
|
|
|
jonathan, are you a time traveller from the future? You seem to be able to quote intersango messages days before they are written. i googled the message you wrote when you first wrote it, and it wasn't found anywhere... except in the future.
Next time you're in the future, could you grab me a screenshot of the bitcoin price chart please?
Thanks.
|
|
|
I had bitcoin-qt crash with a "Segmentation fault" error when I tried to open the 'options' dialog.
Running this command seems to have stopped the crashes: sudo apt-get remove qt-at-spi
Package qt-at-spi is installed by default when you install Ubuntu 11.10. It looks like this is a known bug in ubuntu's qt-at-spi package. You might want to include a note in the instructions about this. I had tried testing the Qt bitcoin client when it was first merged to the master branch but gave up due to these crashes. If I had known then that uninstalling qt-at-spi would fix them, I wouldn't have given up on the Qt client.
|
|
|
I built bitcoin-qt v0.5.0rc1 in Ubuntu 11.10 with the following packages installed and had the following problems. ||/ Name Version Description +++-=========================-=========================-================================================================== ii build-essential 11.5ubuntu1 Informational list of build-essential packages ii libboost-dev 1.46.1.1 Boost C++ Libraries development files (default version) ii libboost-filesystem-dev 1.46.1.1 filesystem operations in C++ (default version) ii libboost-program-options- 1.46.1.1 program options library for C++ (default version) ii libboost-system-dev 1.46.1.1 Operating system (e.g. diagnostics support) library (default versi ii libboost-thread-dev 1.46.1.1 portable C++ multi-threading (default version) ii libdb5.1++-dev 5.1.25-11 Berkeley v5.1 Database Libraries for C++ [development] ii libqt4-dev 4:4.7.4-0ubuntu8 Qt 4 development files ii libssl-dev 1.0.0e-2ubuntu4 SSL development libraries, header files and documentation ii qt4-qmake 4:4.7.4-0ubuntu8 Qt 4 qmake Makefile generator tool
- doc/readme-qt.rst says that 'libdb4.8++-dev' is required, but it doesn't exist in the current version of ubuntu (oneiric). Only one version exists, which is what I installed. This debian bug talks about the issue.
chris@chris:~/Programs/bitcoin$ apt-cache search 'libdb[0-9].*\+\+-dev' libdb5.1++-dev - Berkeley v5.1 Database Libraries for C++ [development]
- In the 'Send coins' tab, hovering over the address book icon pops up a tooltip saying "Choose adress [...]. "Adress" is missing a 'd'.
- In the same tab, clicking the address book icon opens a new window which has an 'ok' button but no 'cancel' button.
- bitcoin-qt is very noisy on standard output. Starting and just clicking through the 6 tabs along the top generates more than 3000 lines of text in the terminal that ran it. Could these messages go to the debug.log file if they're needed? Here's how it starts (piped through 'uniq -c' to remove duplicate lines):
chris@chris:~$ ~/Programs/bitcoin/bitcoin-qt | uniq -c 1 Connected to accessibility bus at: "unix:abstract=/tmp/dbus-9FhaHQgKgC,guid=5bbc0287bbabea8056017084000005f2" 1 Registered DEC: true 1 "sni-qt/3888" WARN 12:10:54.679 void StatusNotifierItemFactory::connectToSnw() Invalid interface to SNW_SERVICE 1 Invalid parent: 0xc39e6a8 QApplication(0xbf89afb4, name = "bitcoin-qt") 1420 Requesting child objects for an interface that is a virtual child itself. 1 not the same: QObject(0x0) QWidget(0xc6c30f8, name = "qt_scrollarea_viewport") at path: "/org/a11y/atspi/accessible/208417016/1" 1 Requesting child objects for an interface that is a virtual child itself. 20 Creating accessible with different object than the original interface! 1 show QLabel(0xcde6468, name = "label") 1 Creating accessible with different object than the original interface! 1 show QLabel(0xc5e2108, name = "label_2") 1 Creating accessible with different object than the original interface! 1 show QValidatedLineEdit(0xcdd71b0) 1 Creating accessible with different object than the original interface!
- I had bitcoin-qt crash with a "Segmentation fault" error when I tried to open the 'options' dialog. Sometimes I'm able to see the options dialog, and sometimes it crashes when I try to open it. I tried re-running bitcoin-qt, then immediately did settings->options, cancel, settings->options and it crashed then, after working the first time. I've rebuilt with debugging symbols and got a stack trace:
Program received signal SIGSEGV, Segmentation fault. 0xb415012d in QSpiAdaptor::checkInterface() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so (gdb) where #0 0xb415012d in QSpiAdaptor::checkInterface() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #1 0xb41562e0 in QSpiAdaptor::GetChildren() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #2 0xb4156c9e in QSpiAdaptor::getCacheItem() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #3 0xb414aecc in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #4 0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #5 0xb414bb7d in QSpiAccessibleBridge::notifyAccessibilityUpdate(int, QAccessibleInterface*, int) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #6 0xb77ff39e in QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #7 0xb7829d5e in QListView::selectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #8 0xb780943a in QAbstractItemView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #9 0xb798d9e2 in QListView::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #10 0xb78763e2 in QListWidget::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #11 0xb6fe2b7d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #12 0xb6ff1a6a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #13 0xb785fa9d in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #14 0xb7865c35 in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #15 0xb7866ca4 in QItemSelectionModel::select(QItemSelection const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #16 0xb78619e6 in QItemSelectionModel::select(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #17 0xb785fdc8 in QItemSelectionModel::setCurrentIndex(QModelIndex const&, QFlags<QItemSelectionModel::SelectionFlag>) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #18 0xb7872874 in QListWidget::setCurrentRow(int) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #19 0x08078b75 in OptionsDialog::OptionsDialog (this=0xbfffe510, parent=0x0) at src/qt/optionsdialog.cpp:85 #20 0x08068bea in BitcoinGUI::optionsClicked (this=0xbffff458) at src/qt/bitcoingui.cpp:308 #21 0x0827f170 in BitcoinGUI::qt_metacall (this=0xbffff458, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbfffe648) at build/moc_bitcoingui.cpp:110 #22 0xb6fe2b7d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #23 0xb6ff1a6a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #24 0xb726883d in QAction::triggered(bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #25 0xb7268adb in QAction::activate(QAction::ActionEvent) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #26 0xb7711b13 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #27 0xb77183af in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #28 0xb771b0f5 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #29 0xb72c9f98 in QWidget::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #30 0xb7719b6c in QMenu::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #31 0xb726fd54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #32 0xb7275dbb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #33 0xb6fdc19e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #34 0xb7270d15 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #35 0xb72fd9fa in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #36 0xb72fbe4d in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #37 0xb732824c in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #38 0xb6a8b25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #39 0xb6a8b990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #40 0xb6a8bc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #41 0xb700aada in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #42 0xb7327e3a in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #43 0xb6fdb1dd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #44 0xb6fdb421 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #45 0xb6fe019d in QCoreApplication::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #46 0xb726d8f4 in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #47 0x08064eb9 in main (argc=1, argv=0xbffff664) at src/qt/bitcoin.cpp:154 (gdb)
I then tried renaming my ~/.bitcoin/ folder and restarting. After that I had a much harder time getting it to crash. The options dialog appeared fine 5 or 6 times. I encrypted my (new, empty) wallet, and everything was still fine. Then I tried to change the passphrase a got a different crash: Creating accessible with different object than the original interface! Creating accessible with different object than the original interface! not the same: QObject(0x0) QPushButton(0x8c4efb0) at path: "/org/a11y/atspi/accessible/147124144" not the same: QObject(0x0) AskPassphraseDialog(0xbfffe520, name = "AskPassphraseDialog") at path: "/org/a11y/atspi/accessible/3221218592"
Program received signal SIGSEGV, Segmentation fault. 0xb7762fe4 in QAbstractScrollArea::viewport() const () from /usr/lib/i386-linux-gnu/libQtGui.so.4 (gdb) where #0 0xb7762fe4 in QAbstractScrollArea::viewport() const () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #1 0xb404c7b2 in ?? () from /usr/lib/i386-linux-gnu/qt4/plugins/accessible/libqtaccessiblewidgets.so #2 0xb414a0ab in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #3 0xb41505bb in QSpiAdaptor::getChild(int) const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #4 0xb4156426 in QSpiAdaptor::GetChildren() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #5 0xb4156c9e in QSpiAdaptor::getCacheItem() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #6 0xb414aecc in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #7 0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #8 0xb414b027 in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #9 0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #10 0xb414b554 in QSpiAccessibleBridge::objectToAccessible(QObject*) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #11 0xb4167fa4 in QSpiAccessible::getParentReference() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #12 0xb4156ba8 in QSpiAdaptor::getCacheItem() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #13 0xb414aecc in QSpiAccessibleBridge::notifyAboutCreation(QSpiAdaptor*) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #14 0xb414a57a in QSpiAccessibleBridge::interfaceToAccessible(QAccessibleInterface*, int, bool) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #15 0xb414bb7d in QSpiAccessibleBridge::notifyAccessibilityUpdate(int, QAccessibleInterface*, int) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #16 0xb77ff39e in QAccessible::updateAccessibility(QObject*, int, QAccessible::Event) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #17 0xb7683b07 in QAbstractButton::setText(QString const&) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #18 0xb772663b in QPushButton::QPushButton(QString const&, QWidget*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #19 0xb76b647f in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #20 0xb76b67c6 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #21 0xb76b7041 in QDialogButtonBox::setStandardButtons(QFlags<QDialogButtonBox::StandardButton>) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #22 0x0827cfd5 in Ui_AskPassphraseDialog::setupUi (this=0x8c24ff0, AskPassphraseDialog=0xbfffe520) at build/ui_askpassphrasedialog.h:108 #23 0x0827b352 in AskPassphraseDialog::AskPassphraseDialog (this=0xbfffe520, mode=AskPassphraseDialog::ChangePass, parent=0xbffff458) at src/qt/askpassphrasedialog.cpp:16 #24 0x0806aa59 in BitcoinGUI::changePassphrase (this=0xbffff458) at src/qt/bitcoingui.cpp:594 #25 0x0827f1ff in BitcoinGUI::qt_metacall (this=0xbffff458, _c=QMetaObject::InvokeMetaMethod, _id=15, _a=0xbfffe648) at build/moc_bitcoingui.cpp:115 #26 0xb6fe2b7d in QMetaObject::metacall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #27 0xb6ff1a6a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #28 0xb726883d in QAction::triggered(bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #29 0xb7268adb in QAction::activate(QAction::ActionEvent) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #30 0xb7711b13 in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #31 0xb77183af in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #32 0xb771b0f5 in QMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #33 0xb72c9f98 in QWidget::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #34 0xb7719b6c in QMenu::event(QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #35 0xb726fd54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #36 0xb7275dbb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #37 0xb6fdc19e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #38 0xb7270d15 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #39 0xb72fd9fa in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #40 0xb72fbe4d in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #41 0xb732824c in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #42 0xb6a8b25f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0 #43 0xb6a8b990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0 #44 0xb6a8bc2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0 #45 0xb700aada in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #46 0xb7327e3a in ?? () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #47 0xb6fdb1dd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #48 0xb6fdb421 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #49 0xb6fe019d in QCoreApplication::exec() () from /usr/lib/i386-linux-gnu/libQtCore.so.4 #50 0xb726d8f4 in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #51 0x08064eb9 in main (argc=1, argv=0xbffff664) at src/qt/bitcoin.cpp:154
|
|
|
3) Once again, even if we were hashing to form an attack, it would be like trying to create a block with difficulty 2^256. We're having trouble with just 400,000. The way the math works, our computing speed is pitiful, a tiny drop in the ocean, compared to what you need to mount a successful attack. If our computing power continues to raise EXPONENTIALLY for HUNDREDS OF THOUSANDS of years, then maybe we would begin to cover a small fraction of all the possible hashes.
SHA 256 is secure. Very secure.
If we use Moore's law, which says that processing speed roughly doubles every 2 years and the current network hash rate of 10 Ghash/s, we see that within 400 years we'll be able to crack SHA 256 in a day: >>> giga = math.pow(10,12) >>> current_hash_per_second = 10 * giga >>> current_hash_per_day = current_hash_per_second * 60 * 60 * 24 >>> search_space = math.pow(2,256) >>> math.log(search_space / current_hash_per_day, 2) * 2 392.8323821490522
Albert Einstein once declared compound interest to be "the most powerful force in the universe." Possibly. http://www.snopes.com/quotes/einstein/interest.asp
|
|
|
I wonder why the operator runs this service for free? Is he crazy?? ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Britcoin's help page used to say: Britcoin.co.uk is my decision to provide those living in the UK with a free exchange in order to promote awareness in the UK and allow UK residents to not miss out on the benefits of using bitcoins and being part of this great social change!
https://intersango.com/fees.php says: Right now as an introduction to the community, we are running a completely free service. We take no commission.
and: Our fees are subject to change and may change without notice. The fees which we have control over will be properly displayed and with adequate forewarning (at least 1 week).
|
|
|
In the bottom right corner in the 'additional links' box, "its" is spelled wrongly:
"and it's possible implications"
|
|
|
Interesting idea! :-) You would probably have to monitor though, whether you get enough funds this way and maybe turn it of if it's too much and add extra transfers if it's not enough. Given that transactions are still really cheap, I don't think I would go to the trouble of that. Neat trick though. =)
What's "too much"? What's the downside to having funds held by the 'green' address?
|
|
|
@BTCSports, Since I think you know a lot more about how betting works than I do, I would like your input on how to structure the bet.
I am saying that Bitcoin will outperform ALL of them.
How I imagine it would work is if the current (easy math) price of each is: Bitcoin is $10. Silver is $50 Gold is $1500 Dow Jones 10,000 points Nasdaq 2,000 points USD is $1
in two years if everything doubles (except the USD will still be worth $1USD) to:
Silver is $100 Gold is $300 Dow Jones 20,000 points Nasdaq 4,000 points
Bitcoins would need to be more than 100x more ($1,000 a coin) for me to win the bet.
Please let me know if anything is not clear, or you think I am missing something.
Couple of mistakes there. Twice $1500 is $3000, not $300. And if everything else gone up 100% and we want to outperform it by 100 times, we'll need to go up 10,000%, which would take the price of BTC from $10 to $1,010, not $1,000. Going to $1000 from $10 is 'only' 99 times more of a percentage gain than gold made.
|
|
|
Thanks for the bug find... I'm working on it. Please don't use v0.1 to V0.4
Perhaps you should edit your first post in this thread to say that. I had to get to page 3 before seeing any kind of a warning.
|
|
|
Currently Instawallets green address transfers require 2 transactions (from the specific wallet to the green address and then from the green address to the destination).
Note though, that this technique doesn't necessarily require 2 transactions. The green address could be replenished only from time to time with a single large transaction. But that is an optimization that I haven't implemented yet.
How about if you were to direct the 'change' from all withdrawals to your green address. So even if I do a regular withdrawal, the change gets returned to your green address. That way you should get away without ever having to manually 'replenish' the green address.
|
|
|
Checking the same getTrades.php API now shows that the trades at 8.5, 10.5, 12.5 have disappeared from the trade history: This is the same time period as I pasted a couple of posts up from here, and now only the nine 5.5 trades still exist in that time range: {"date":1315753350,"price":"5.51206","amount":"0.51","price_int":"551206","amount_int":"51000000","tid":"1315753350870615","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"5.51205","amount":"9.51","price_int":"551205","amount_int":"951000000","tid":"1315753350900809","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753353,"price":"5.50227","amount":"2.84442602","price_int":"550227","amount_int":"284442602","tid":"1315753353208319","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753362,"price":"5.50227","amount":"35","price_int":"550227","amount_int":"3500000000","tid":"1315753362025600","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753374,"price":"5.50217","amount":"1.1","price_int":"550217","amount_int":"110000000","tid":"1315753374882708","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753407,"price":"5.50217","amount":"19","price_int":"550217","amount_int":"1900000000","tid":"1315753407440568","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753420,"price":"5.50207","amount":"21","price_int":"550207","amount_int":"2100000000","tid":"1315753420123491","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753420,"price":"5.50227","amount":"9","price_int":"550227","amount_int":"900000000","tid":"1315753420149017","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753445,"price":"5.50227","amount":"8.51","price_int":"550227","amount_int":"851000000","tid":"1315753445862485","price_currency":"USD","item":"BTC","trade_type":"bid"},
Did an explanation from MtGox appear anywhere, whether official or unofficial?
|
|
|
What on earth is Skype doing on that list?
|
|
|
Here's the part of http://mtgox.com/api/0/data/getDepth.php where the price spiked. Note the isolated trades over $10. Looks like it must be a bug in the order matching: {"date":1315753350,"price":"8.56343","amount":"0.1","price_int":"856343","amount_int":"10000000","tid":"1315753350781803","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"8.51303","amount":"36.81","price_int":"851303","amount_int":"3681000000","tid":"1315753350846659","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"5.51206","amount":"0.51","price_int":"551206","amount_int":"51000000","tid":"1315753350870615","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"5.51205","amount":"9.51","price_int":"551205","amount_int":"951000000","tid":"1315753350900809","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"8.51105","amount":"4.05","price_int":"851105","amount_int":"405000000","tid":"1315753350960337","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"8.51103","amount":"28.5702","price_int":"851103","amount_int":"2857020000","tid":"1315753350982440","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753351,"price":"8.51102","amount":"3.05","price_int":"851102","amount_int":"305000000","tid":"1315753351004599","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753351,"price":"10.50328","amount":"5","price_int":"1050328","amount_int":"500000000","tid":"1315753351032421","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753352,"price":"8.50227","amount":"33.99","price_int":"850227","amount_int":"3399000000","tid":"1315753352779862","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753352,"price":"8.50227","amount":"10.6","price_int":"850227","amount_int":"1060000000","tid":"1315753352983925","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753353,"price":"8.50227","amount":"6.885","price_int":"850227","amount_int":"688500000","tid":"1315753353111261","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753353,"price":"5.50227","amount":"2.84442602","price_int":"550227","amount_int":"284442602","tid":"1315753353208319","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753362,"price":"5.50227","amount":"35","price_int":"550227","amount_int":"3500000000","tid":"1315753362025600","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753374,"price":"5.50217","amount":"1.1","price_int":"550217","amount_int":"110000000","tid":"1315753374882708","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753407,"price":"5.50217","amount":"19","price_int":"550217","amount_int":"1900000000","tid":"1315753407440568","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753408,"price":"12.50028","amount":"50.56934435","price_int":"1250028","amount_int":"5056934435","tid":"1315753408850547","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753420,"price":"5.50207","amount":"21","price_int":"550207","amount_int":"2100000000","tid":"1315753420123491","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753420,"price":"5.50227","amount":"9","price_int":"550227","amount_int":"900000000","tid":"1315753420149017","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753445,"price":"5.50227","amount":"8.51","price_int":"550227","amount_int":"851000000","tid":"1315753445862485","price_currency":"USD","item":"BTC","trade_type":"bid"},
If you ignore the dollar price and just look at the cents, it's a very smooth price movement. ( ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) .50227 to (5).50227 to (12).50028. I wonder what kind of a programming error could cause this.
|
|
|
Here's the part of http://mtgox.com/api/0/data/getTrades.php where the price spiked. Note the isolated trades over $10. Looks like it must be a bug in the order matching: {"date":1315753350,"price":"8.56343","amount":"0.1","price_int":"856343","amount_int":"10000000","tid":"1315753350781803","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"8.51303","amount":"36.81","price_int":"851303","amount_int":"3681000000","tid":"1315753350846659","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"5.51206","amount":"0.51","price_int":"551206","amount_int":"51000000","tid":"1315753350870615","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"5.51205","amount":"9.51","price_int":"551205","amount_int":"951000000","tid":"1315753350900809","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"8.51105","amount":"4.05","price_int":"851105","amount_int":"405000000","tid":"1315753350960337","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753350,"price":"8.51103","amount":"28.5702","price_int":"851103","amount_int":"2857020000","tid":"1315753350982440","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753351,"price":"8.51102","amount":"3.05","price_int":"851102","amount_int":"305000000","tid":"1315753351004599","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753351,"price":"10.50328","amount":"5","price_int":"1050328","amount_int":"500000000","tid":"1315753351032421","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753352,"price":"8.50227","amount":"33.99","price_int":"850227","amount_int":"3399000000","tid":"1315753352779862","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753352,"price":"8.50227","amount":"10.6","price_int":"850227","amount_int":"1060000000","tid":"1315753352983925","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753353,"price":"8.50227","amount":"6.885","price_int":"850227","amount_int":"688500000","tid":"1315753353111261","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753353,"price":"5.50227","amount":"2.84442602","price_int":"550227","amount_int":"284442602","tid":"1315753353208319","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753362,"price":"5.50227","amount":"35","price_int":"550227","amount_int":"3500000000","tid":"1315753362025600","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753374,"price":"5.50217","amount":"1.1","price_int":"550217","amount_int":"110000000","tid":"1315753374882708","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753407,"price":"5.50217","amount":"19","price_int":"550217","amount_int":"1900000000","tid":"1315753407440568","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753408,"price":"12.50028","amount":"50.56934435","price_int":"1250028","amount_int":"5056934435","tid":"1315753408850547","price_currency":"USD","item":"BTC","trade_type":"ask"}, {"date":1315753420,"price":"5.50207","amount":"21","price_int":"550207","amount_int":"2100000000","tid":"1315753420123491","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753420,"price":"5.50227","amount":"9","price_int":"550227","amount_int":"900000000","tid":"1315753420149017","price_currency":"USD","item":"BTC","trade_type":"bid"}, {"date":1315753445,"price":"5.50227","amount":"8.51","price_int":"550227","amount_int":"851000000","tid":"1315753445862485","price_currency":"USD","item":"BTC","trade_type":"bid"},
edit (Sun Sep 11 19:39:05 PDT 2011) : fixed URL - getTrades,php, not getDepth.php
|
|
|
Mt. Gox isn't saying what their FOREX fees and spreads are. If they're buying and selling currencies with no spread and no fee other than their Bitcoin trading fee, they're exploitable.
They don't say, but if you look any non-USD orderbook you can see by the gap between bid and ask prices that they're charging 2.5% on all non-USD trades in addition to the 0.6% or so commission. So they're fine so long as they're within 3% of the correct price.
|
|
|
'Price' box looks good.
Thanks. Impressive to get requested features implemented and live within 24 hours. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) Just please dont rush and Gox things up! Good point. I'll take a few days off before adding any more features. ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif)
|
|
|
|