Ok I couldn't find any direct calls in the API to do just this, nor a bot, so I wrote one with the support of a wrapper I modified from github (link in file).
https://github.com/hunterbunter/vircurex-python-shotgunbot
I've tested it and it seems to be behaving as intended, except I don't have the cryptofunds on hand at the moment to put it through it's pacing on 100+ orders (they're tied up testing my volatility bot). Each order has to to have a minimum btc volume of 0.0001 btc, so while I know my bot can handle it, I'm still not sure if Vircurex is going to complain. If anyone can test it out, that'd be great, otherwise I'll wait a few days for my testing run to finish and move some funds over to test.
https://github.com/hunterbunter/vircurex-python-shotgunbot
I've tested it and it seems to be behaving as intended, except I don't have the cryptofunds on hand at the moment to put it through it's pacing on 100+ orders (they're tied up testing my volatility bot). Each order has to to have a minimum btc volume of 0.0001 btc, so while I know my bot can handle it, I'm still not sure if Vircurex is going to complain. If anyone can test it out, that'd be great, otherwise I'll wait a few days for my testing run to finish and move some funds over to test.
I tried it, trying to spread 1000 I0Coins across 4401 satoshis through 4500 satoshis, but...
The API does have a limit of 100 open orders, it seems. I already have many hundred so the script was unable to place even a single order.
So to do this is going to require either doing it in the browser with some kind of browser-automation toolkit or plug-in, or waiting for VIrcurex to add it to the site itself (or to get rid of the limit on open orders in the API).
A couple of things I noticed:
- You spelt Satoshi(s) wrong.
- It claimed the 100 orders limit caused the order to fail to release, so I looked on the website in case that meant it had managed to queue them up waiting for release, figuring if so I could release them manually in the website. But they were not sitting there un-released waiting for me to release them. So maybe saying the order failed to release due to the 100 limit is not really quite right, since it seems to have failed to queue it up waiting for release not merely failed to release it?
- It was trying to place orders for slightly less than ten, so it was somehow failing to divide 1000 by 100 and arrive at 10, instead it was 9.99999990 .
-MarkM-
Thanks for the feedback. All this time I thought it was actually SaNtoshi. TIL it's not...fixed that.
The rounding error: That may have been my fault - I had a floating point rounding error that was causing a bug so I multiplied by 100,000,001 at some point, but that caused what you saw. I've changed the way I did it a little so it shouldn't happen now; if it does let me know. I also changed the feedback - you should have been getting a "order failed to open" error, not a release error, so I changed that to be more distinctive (it'll still show "order failed to release" if it was opened but couldn't be released).
The strangest thing, is that I just tested it with some shrapnel, and it actually let me put up more than 100 orders:
100 dvc @ 50001-50200, released 200 orders @ 0.5 dvc each
100 dvc @ 60001-60200, released 200 orders @ 0.5 dvc each
1000 i0c @ 4401 - 4500, released 100 orders @ 10 i0c each
EDIT: Then I placed another order and it came up with the "maximum orders reached" halfway through:
0.0267 btc and 300 dvc @ 1-200, released 53 btc orders correctly, then failed the rest (the dvc was probably going to fail anyway due to being too low volume, but still came up with max orders error)
git is updated with the new files.
I don't know what to make of it
The more we can get the word out about Devcoin the better.
