Verification, Mediation & Job Pricing on Lilypad v1
Current State
Last updated
Current State
Last updated
You can read a much more thorough and academic explanation on these ideas in the and V1 Research Documents
This page also comes with a warning:
We didn't want to hold back on releasing a testnet build that developers could use straight away to build their awesome ideas on, however, it's worth noting that Lilypad v1 is a minimal modicum-based testnet and the implemented mediation and game theory on this testnet is very much at baby 👶 stage - as are many other aspects of the robust compute network that we are working hard to build.
There is currently no verification on smart contract-called Lilypad jobs
Verification DOES exist on the CLI version, however.
How can nodes be trusted to do the compute job?
A resource provider node (compute node), is currently required to put down a deposit of funds before any compute jobs arrive.
On a network of compute nodes, there is also mediator nodes, whose job is to check that nodes in the network are correctly running the submitted jobs (eg. by running the job itself to check for correctness)
💡Fun fact: This is also why all jobs on the network currently need to be deterministic!
If a resource node is found to have cheated and not run the job, the penalty for doing so is high & their deposit is significantly slashed. While not every job will be verified for truthiness, a good analogy is to think of a train ticket inspector on a train. You may not always have your ticket checked, but if the fine for not buying a train ticket is high enough (let's say several ether!), then you will more than likely spend a small amount of Gwei buying the ticket, rather than risking the fine and being kicked off the train. 🚃 Currently, the mediation (or checking that nodes in the network are correctly running submitted jobs) that happens on a smart contract called job is provided by a Lilypad default mediator. However, if you don't trust our mediator then you can run your own mediator and run compute nodes that trust your mediator instead.
While not every job will take the same amount of time or compute resources to run, currently the network prices all jobs at the same amount. This will change in future versions to more accurately calculate and charge for the compute resource requirements of a job as well as compensating the compute nodes appropriately.
Read more about these ideas in the & V1 Research Documents
