It looks that this request doesn’t have a majority to pass. Please provide some feedback if you are not voting for this proposal and I will try to explain, withdraw or change the request where possible.
When this grant hasn’t passed on the 12th which it looks like, I feel obliged to stop operation at least temporarily or use some of the rollover funds. Will only do that when the last 100 blocks shows a majority of the votes during a couple of hours.
Your numbers have SouthExchange USD/NBT with 1,000 target but paying out 1080 NBT over 60 days. That would be true if there were a 5,000 NBT target. I believe your grant should be less by 864 NBT.
Is your fee 300 or 150? It says 300 in the text but then uses 150 in the calculation.
Also, your tolerance is written in the grant as 8.5% not 9%. Typos make for interesting ambiguities for a contract. Of course, neither would be in compliance anyway, as the fee on NBT/BTC CCEDK is 0.2%.
Does south exchange even exist? I can’t find their website anywhere. I’m not sure I am comfortable with you opening operation on two new pairs at once, especially for a 60 day term with no plan for midterm parameter adjustment.
Ouch, some quality issues due to time constraints. Not good!
The motion has been up as a draft for over a week before being brought up for voting. Glad at least someone picked it up. Thanks Nagalim.
You are right. You got me there on a nasty copy/paste error. Will burn the excess of 864 NBT on passing of this grant. Have updated the OP accordingly.
The intention was 150 NBT/month, total 300 NBT. Will keep it on 150 NBT as the calculation is based on that. My punishment for making these mistakes.
Not good again. However the motion says 0.85 so I will stick to that for now. Will update the change log in OP, this doesn’t change the motion.
On CCEDK:
NBT/USD fee = 0.2%
NBT/EUR fee = 0.15%
NBT/BTC fee = 0.001%
So except for the NBT/USD pair I believe I’m compliant
South Exchange is 0.2%, however as you know I can only set one tolerance parameter for all pairs on the pool. Until the software has a feature to set this by pair I’m good to adjust to 1% on all pairs.
That is not easy to change now unfortunately. I still haven’t seen a wrapper though. Even once it is published I like to test it for a week or so. So effectively it will be less than a 2 month term anyway. I chose the 2 months to reduce the voting fatigue and the liquidity provided is very low. We are talking a cost of max. 195 NBT/month for both pairs assuming they are 100% effective and running for the full 2 months period. I consider that amount a test period anyway. Happy to comply to any motion to raise or lower that amount after the wrapper has been tested successfully or raise a motion on a request myself.
Fine, I’ll vote for it (begrudgingly, lol). I’m not sure about the ccesk btc fee, the trading page says 0.2% but I haven’t actually tried trading there.
You can take the 300 nbt. It mentions 300 nbt pretty explicitly and your grant is too much anyway.
Can confirm a 3h outage unfortunately. It is back up and running now. There is something wrong in the code.
I’m spending a lot of time to find out what is going on, but can’t get my finger on what is triggering it.
I’m getting this error out of the blue:
2015/10/10-21:21:38 ERROR: exception caught in main loop: list index out of range
It crashes the server.py in a way that it is no longer responsive.
There is a relation with the config.py, but still puzzled what is wrong. It appears to be the same cause as the previous outages.
Just transferred the backpay for the scheduled restart yesterday. That is about 22h against the old rates.
The backpay for the time before the outage today (~10h against new rates) is on hold until the server has done 2 automatic payouts without further outages.