This repository has been archived by the owner on Oct 31, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 286
Trading system prototype #5
Labels
Comments
@badb are you working on that? |
No. We have a first prototype version, but it should further developed. First we must change current simple version to fit payment system model, then we may make further experiments. |
banasiakadam60
added a commit
that referenced
this issue
May 30, 2016
Proposal for a new trading system
I'm closing this issue for know. We will create a new one with updated description after we prepared task & transaction protocol description. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Requestor broadcast his task with maximum price. All providers who can compute task for price lower than defined will be accepted. Final price equals to price offered by provider multiplied by computation time.
Requestor broadcast his task with maximum price. For some time offers from providers are collected. Finally the set of best providers is chosen. Function for provider validation should be take price, performance and reputation as parameters.
Providers may try to cheat and declare too high performance and too high computation time. Therefore requester will try to predict computation time. Benchmark will be run on requester's computer to compute his performance and expected time. Based on this result requester will to predict computation time for each provider based on their performance. Provider will have to accept this time multiplied by declared price as a fixed remuneration for computation. For each subtasks there is defined timeout so there's no risk of computing a subtask forever.
The text was updated successfully, but these errors were encountered: