Yes, that's what I'm trying to achieve, a more or less automatic re-entrance.
...
If you look at this screenshot under "Auto collateral tasks"...
... this will be a mechanism you can setup to let your servicenode automatically do all kinds of things so it can quickly react when the "collateral market" changes.
For example you can say here:
If your current COLLATERAL falls lower than the MEAN of all other collaterals in the network, then go ahead and ADD enough SPR so that your COLLATERAL is again atleast as large as the MEAN.
There will be more such trigger points you can define in an IFTTT (if this then that) fashion.
This is a great explanation. It definitely cleared things up and I'm even more excited than I was - it's nice to be able to tangibly imagine how we will actually be able to run our service nodes!
I really like that you are attempting to make it user friendly. It seems as though your approach will limit frustrations with maintaining Service Nodes, which I'm sure is your goal. Being able to "fire and forget" will be nice for a lot of people. I am so excited to see this in action. I second minerpage!!
I am doing experiments with letting your servicenode be prepared so that it can automatically react to a constantly changing situation.
Sounds like testing the finishing touches to me!!!!!
