Using ~0.002 $/nsr, we should sell 2.4 mil NSR. This is the extent of the official crowdsourcing and will be all we are guarenteed to do this week.
All right. I am fine with this figure too.
same here. Let’s all take it easy now. Our infrastructure isn’t up there for 100% available service yet. I say we forget about changing nsr unit and more type of nubits for now and get all the basic infrastructure working first.
I’ve made changes to cointoolkit to enable nuexplorer.ddns.net, you can use it at:
https://backpacker69.github.io/cointoolkit/
You have to go to settings and change providers for nubits/nushares to nuexplorer.ddns.net
You are a boon!
Adjusted:
I planned to use only 1.2 million at once and lower the orders by 6% each step, but the situation is dire enough that we should aim at getting proceeds rather sooner than later,
I left the order at 500 Satoshis and added one at 450 Satoshis.
Well that is all there will be for the week. I see no reason to get all and spend all in the beginning of the week and 0 for the later times of the week. I say let time do its thing and execute like buybacks plus more randomness to discourage gaming.
Agreed. Will make the next steps smaller or the update interval longer.
What do you think about putting all NSR on the books at the same time, but in two orders, where one gets put x% below the other each time and the next time the other order gets moved?
Should I rather use all funds in one order?
The 10% move was not much different from the past buybacks, in fact it was an even smaller step.
I’m only not sure whether 500 Satoshis was a good start or too low.
There are traders who never read forums. I think putting all in one order might scare them. But that is probably only my brain burp.
So you think 2 orders are better?
I can make it 3 as well and always move the one that is at the biggest offset.
2 or 3 would be good if moving them isn’t too much trouble.
btw I just discovered these examples of polo api. doesn’t seem difficult to write a script to move the walls.
source https://poloniex.com/support/api/
PHP wrapper by compcentral: http://pastebin.com/iuezwGRZ
Python wrapper by oipminer: http://pastebin.com/8fBVpjaj
Node.js example of how to connect to the push API (requires autobahn): http://pastebin.com/dMX7mZE0
I wouldn’t want to test that when dealing with Nu funds.
It seems like I need to move them manually.
But thank you for the links. I might have a look at them for the next time.
I’d like to have an automated way to move orders as part of my mandate.
But I need to move only one no matter whether it’s one or three orders on the book.
NSR sell orders adjusted:
In numbers:
800,000 NSR @ 0.00000500
800,000 NSR @ 0.00000450
799,998 NSR @ 0.00000410
Next move will bring the 800,000 NSR @ 500 Satoshis to 370 Satoshis and leave the others untouched.
I think the way is clear: move the most expensive order to roughly 90% of the cheapest (and make some roundings).
Any suggestions to improve this or are you fine with it?
how many NSR are going to be sold within what time-frame? Can that already be (roughly) anticipated?
2.4 million NSR until Friday next week.
All according to “Standard and Core” motion and the buyback calculation.
Thanks!
NSR sell order adjusted
In numbers:
800,000 NSR @ 0.00000450
799,998 NSR @ 0.00000410
800,000 NSR @ 0.00000380
I seems seldom would buy lots of NSR at your price, within one week.
I’ve said that when you are in short of money, seldom will lend u money.
So called NBT<->NSR shift is the old “debt-to-equity swap” in real world.
NSR sell order adjusted
In numbers:
799,998 NSR @ 0.00000410
800,000 NSR @ 0.00000380
800,000 NSR @ 0.00000350
NSR sell order adjusted
In numbers:
800,000 NSR @ 0.00000380
800,000 NSR @ 0.00000350
799,998 NSR @ 0.00000325