Ok while playing with a few ways to implement this I can see I need to do more testing on this, I really don't want to shoot you down at the first sign this won't work. However this system that has been purposed, leaves us very vulnerable for attacks. The amount of MN just cant be this easy to manipulate, the amount of MN must remain higher then the request load at all time as to not allow attacks. Also this number can't be a moving variable based of a public demand so easily changed. This is why the price of 2000 OC has been set with a fixed compensation (reward %) as a way to control how many MN there are. Bc that number can't be moved up and down easily. I will work more on this to see if there is a way to secure it with some sort of almost Diff re-target equation. I'm still convinced that set amounts with stable long gradual number fluctuations is our most secure way to do this.
We have to build in
some method for discovering the market value of the service, ie what the job is worth.
In other words if a given mnode handles say 1% of our traffic (on say an average month) do we buy em (with OC) a hamburger, a hat, or a hummer?
The only way to find out is to offer them something and see if they show up, that's market price discovery.
(and in the beginning we have to make sure that this offer is more than enough)
If ppl are lining up to do this for say a hamburger a week (ie what a hamburger cost today if you paid in OC), were good.
if not lining up, we offer a hat, or 2 hats...
no line yet?... 20, 100, or 200 hats, then a hummer, whatever it takes.
But long before we get to the hummer or even 200 hats, somebody will take the job.
because they decided there is enough profit in it for their time, investment, and trouble.So in order to perceive the market, someone, or thing (cpu), has to bid, either the Mnodes, the devs, or the wallets (i think it should wallets).
At some point, with all our relevant commodity prices in flux, somebody has to offer a new price (this offer being a query to the market), based on historical time/investment for the task, the market will react to the new price (this reaction being the market's answer to the query).
Periodically (hourly, daily) somewhere in the system
one of the three available entities (wallet, devs, MN operators) has to rediscover the value (purchasing power) of transfer cost. This is what takes the blindness out of our payment play.
This entity will look at the value of oc and try to readjust the amount offered to equal the amount of purchasing power we currently wish to pay for the task.The amount of purchasing power we award/offer for a given node depends on how much more, or less, Mnode availability the market needs to stay vibrant.
In other words, do we need to pay an mnode operator the price of a hamburger, a hat, or a hummer for say every month of working for us? Time will tell very quickly and updates will be built into this system cycle.
So this price setting entity also needs to be able to perceive the condition of the trans network at any time:
Is the network satisfactory? Are there enough nodes available for smooth transfer? If 100 wallets tried to make transfers in the next 10 min would there be enough MN resources?
If this entity perceives the network as adequate, the price/offer stays the same. if the network appears deficient, the entity offers more, if there's a substantial surplus of node availability, the entity lowers the offer.
With this offer now standing,
the market responds, answering the question "is this enough?" if the answer is yes, nodes will want to work and our network availability checks will show an adequate trans availability during these periods between price adjustments.
Notice that these price awards could change every five minutes if needed. The value of OC and 'the cost/time involve with the task' are both subject to change, our system has to compensate for these two fluctuation, oc being the more volatile obviously.
In this (wallet entity) approach the market is responding to our standing [but changing] offer, as opposed to us responding to their multiple bids, which i think is cleanest.