https://github.com/bitcoin/bitcoin/pull/3656

MagicalTux commented 2 hours ago
Just to update this thread, it seems that this discussion is mostly stale now. We (at MtGox) will implement this new hash index in our transactions database and start working with it (we will announce a maintenance as we will have to stop bitcoin deposits too during the database schema update) and will start providing this new hash when customers are withdrawing bitcoins, litecoins, or any other coin based on Bitcoin we may support in the future.

We will also provide an API that will allow our customers to use this hash to retrieve the transaction hash as seen in the blockchain once the transaction is confirmed, and will hope others (blockchain.info?) will index this value one day.

We also invite other exchanges and businesses which may need to keep track of bitcoins they send to use this same method, since dealing with multiple variations of the same thing wouldn't be very productive.

If nobody does it, we will also post some test vectors for regular (in=>out) transactions in the near future.

Gox is the joke. They started this. The press release was spiteful and vindictive of the bitcoin protocol after all the news articles of "mtgox halts withdrawals", MT cut off the nose of bitcoin to spite it's face.

Does anyone know how many qubits it would take to solve common tasks such as SHA1 or SHA256 hashes or other?

don't use 3. use 2.7.3

If those git commands dont work you can download the zip file of goxtool manually, and put it into the goxtool directory.
(not a git expert so idk how to best explain this while the author is asleep)

Fixed the 99999 problem, also added Trailing stop loss market sells.

Trailing stop loss market sells can now be used, by setting price to a negative number ("negative price") meaning the distance away from the current price to set the stop loss to. (ie: -5, if current price is $115, stop loss price will be $110. If the price goes up to $125, the stop loss trails behind it as $120, and if the price now drops to $120 or below, we will take profits and sell off at $120

"Stop-Gain Market buys" are something else entirely. if the price is going up and you dont want to be left behind, this is when you use the "negative size" to tell the bot to BUY instead of sell, once the target price is reached.

To recap:
+Size , +Price = Stop Loss Market Sell ("size" BTC will be sold at market, when price falls at or below "Price")
+Size,  -Price = TRAILING Stop Loss Market sell (same as the first one, except the stop loss target price will start off at the current price minus "Price", as the market goes up, the stop target will compensate, and should the price fall below the new adjusted target (the sell will fire and PROFITS will be taken).
-Size,  +Price = Stop GAIN market BUY ("size" BTC (the negative signifies a buy), will be BOUGHT at market, when the price climbs at or above "Price")
WARNING: -Size, -Price <---- DONT try do it, i did not create something to handle this, and it has to be coded before it can work, (refer to https://bitcointalk.org/index.php?topic=176489.msg2022346#msg2022346 ) for a theoretical run through of what it would do.

Sorry, I fixed it now. Anyone who was having problems with stop loss orders should try the new version, and it now does "Stop-Gain Buy" orders, if you use a negative BTC as the amount, and price as the target price.

I made some performance optimizations: I've speeded it up by a factor of 2, So instead of using 5-10% CPU, it should only use 2-5%
Sample Proof:
https://raw.github.com/genbtc/goxgui/master/performance.png
Running 3 instances at the same time, each with different code, I found some ways to speed it up.
The numbers below are for twice the length of time as the picture, just to smooth any errors out.
Version:  CPU Usage Time
older Main Fork (w/ total column, "Before"): 2:40
genBTC fork (with total column,    "After")  : 1:10
Newest Main (no total column,  "Removed) : 0:30

Changes are live on the git.


This shouldn't happen. I'm not sure why that path got inserted in there when I compiled the .exe, I've removed any reference to those now, and the new version is on the github. If you are getting those errors of course the stop loss isnt gonna work. Also, I have invented a way to do the "Stop-Gain" - Buy if price is above certain price.. Just enter the amount of BTC as negative, and the price as the trigger price to buy. "Negative BTC" means do Stop-Gain Buy @ target price.

Yes. He is working on it. He removed it because there was a CPU utilization issue (it recalculates the total every time a new depth message comes in, which I guess its using up CPU cycles on laptops), but not really an issue for me, so i kept it in my version @ https://github.com/genbtc/goxgui

OK, I've updated the forked repo. The multi-currency support was just too big of an update for me to include right now. For the stop loss orders, user orders  and ticker tab/ticker title bar, download it from https://github.com/genbtc/goxgui  
Also, the "Total:" Bitcoins column is still present as this is one of the best features that I use goxGUI for. (i usually place my orders about 3000 coins away from the spread, so big whales can hit them ) So in my version it is still there but it is removed in his latest version. (see screenshots)
Also, you can edit the "Fiat" and "Target" currency in the "Various Settings" window, which changes the .ini file for goxtool so it will actually trade in different fiat currencies, and show that currency's wallet. (but the decimals are wrong for JPY and SEK)
The authentication and password tabs have been moved into "Preferences" and you can supply your own password. The "Apply" button will run one final check if everything is valid, and enable the OK button to Write everything to the config file and restart the socket with your new credentials.

Click the stop orders tab. It should say "NO STOP ORDERS     YET" in the box below.
In the size box, enter: 1 (for 1 BTC)
In the price box, enter: 100 (for 100 USD)
This will sell 1 BTC when the price falls below $100.

I have come to the conclusion you maybe are trying to use decimals without the leading 0. If you are using sizes under 1 BTC, you have to include the leading 0 such as: 0.125

I'm working on updating my fork to sebastopols  latest  version. The password stuff should be easier. I still am not sure why your stop loss order didnt work if the rest of normal trades can trade.

Did you grant the API key "trade" access in addition to "Get-info" in the mtgox website's security tab?  (did you try to do normal trades?) - it should work...... no errors? contact me on IRC>...

Once you enter the API key and Secret, they are encrypted in the .ini file. Previously the password they were encrypted with was hardcoded, not user-choosable and I found this odd (security hole). So I cobbled together the method that you see in my forked version, and heres the instructions.
1) Download the fork from https://github.com/genbtc/goxgui
2) The program will generate a new blank config file on first run. (Don't try to import the old one)
3) Click the Options Menu, go to Preferences, and enter your API Key and Secret
4) Enter a Password of your own choosing.......
5) Hit Apply to check for errors, and then click OK if verified.
6) The program will encrypt the API Key/Secret and store it in the INI file.

This will store your password, and auto-login everytime you launch it next time.

https://github.com/genbtc/goxgui

Thats my forked version. The two most important changes are the user orders and the Stop Loss Orders tabs. Consider it an even more developmental version. I just added the stop-loss bot tonight, and I tested it for a few hours, but I can't forsee bugs, but especially when using this to trade, please test it out in SIMULATION mode first, (edit goxtool\stoploss.py and change SIMULATION = False to SIMULATION = True).

No. You need to use the API key. Go to: https://mtgox.com/security and click on Advanced API Key Creation: Then type any name and give it Get Info and Trade rights, and hit Create Key. The following codes are what you copy into the program.

Here is the windows exe. Also, I can vouch for HIS code being clear of malicious intent, since I read it all. The exe is theoretically de-compilable (the source is extractable in binary somehow) but if you want to be extra careful about stuff, just run this program in a sandbox and block it from accessing any other websites other than *.mtgox.com

http://www.mediafire.com/download.php?41gu8b0ze1197po

This link above is the .exe of the version with "compress order-spam below 0.6 BTC", and "show Size and Total in BTC, not USD"

Also working on a new version: http://i.imgur.com/LtCPbCD.png
This is page 2: http://i.imgur.com/xuJTnOG.png

From one Developer to another developer: I am trying to learn PyQT as I go since I never did it before. But so far I have come up with the shell of the GUI now I just need to hook the slots into it. Maybe we can work together? I have a _lot_ of code from my other project. One major thing as you can see from the screenshot is the "Authentication" tab. theres no reason to be looking at that everytime you trade. BUT what is a major flaw is the hardcoded "ffuuuuuu" ironic bit You know what i mean. This has to be replaced by an actual user-generated one, that is Created through this new tab, and then verified with a dialog box when you launch the program. Maybe the process could work something like: On 1st launch = Create password before spawning QApplication, then theres no need to relaunch. Then everytime you load up you can choose to run in authenticated mode "Log In? Ebter your Password or Cancel"

He included a windows startup script. it's in the "run" directory, should just be able to double click on start_win.bat .....

Failing that, you may need to edit this file, mine looks like:

set PYTHONPATH=%PYTHONPATH%;..\goxgui;..\goxtool
cd ..\goxgui\
start pythonw application.py

Also just wanted to let you know that this DOES compile into a single EXE very easily. it ends up being around 8.3mb.
The command to generate it is something like this:


Where specfile.spec is:

I think i found a bug.... Line #13 in adaptor.py gave me the error of: 
when I went to place an order.
Changing the 2nd arg to "long long" seemed to fix it (and would make sense, since the first two args are usually quite the same size and the second one would usually be even longer (the above is price,volume,typ,oid,status)
Output Similar to:

To anyone whos on windows, if you rename "application.py" to application.pyw, Python won't launch the blank command prompt window before launching the GUI.
(though you will also have to modify the startup script - i already did anyway.)
mine now looks like this:
@echo off
set PYTHONPATH=%PYTHONPATH%;.\;.\ui
..\application.pyw

Also, the setx command in the format setx PYTHONPATH %PYTHONPATH%;.\;.\ui (or whatever the proper paths are for you, sets the path in the REGISTRY) so you dont have to keep setting it everytime.