Git Product home page Git Product logo

Comments (4)

posix4e avatar posix4e commented on August 13, 2024

I am not sure how this would require a smart contract change. In theory staking based whitelists could be external to the protocol

from fortune.

vkomodey avatar vkomodey commented on August 13, 2024

They might be. But the current Escrow has statuses Pending and Launched. So when the Escrow is created - it gets the Launched status. After the requester specified details like manifest and oracles - it goes to the Pending state. While I see the validation phase as something between these 2 steps.

The validation is somewhat stopping the actual work if input data is incorrect or inappropriate. Also, we should make a payment to validators when they did their work(and ideally it should be before the actual work since they are not really connected to workers and exchanges). So current Escrow setup does not control these aspects very well and I'd like to see smart contracts as a job's source of truth. So everyone might have a look at the contract and understand, what is going on here

from fortune.

posix4e avatar posix4e commented on August 13, 2024

Here’s how it should work.

  1. The entity which wants to post jobs to the oracle network should prestake HMT so oracles will safely accept jobs from it.
  2. the entity which posts jobs to oracle network should scan the job to make sure it’s acceptable.
  3. If oracles detect abuse, they can strike the staked Hmt

from fortune.

vkomodey avatar vkomodey commented on August 13, 2024

currently, each "trusted" party can withdraw any amount of HMT to anybody. so this can be used for payout HMTs for the oracle who noticed something, instead of workers, for example

small note. if we'd like the job to be canceled after that - oracles should not withdraw 100% of HMTs. because the current contract does not allow to cancel Escrows without tokens on their balance

so this issue can be rephrased to the next one:

Add a proper validation for the exchange, recording, and reputation oracles. Each of them should be able to withdraw HMTs in case of invalid manifest if the validation failed. The validation list for each party is:

  • the exchange oracle checks the manifest
  • the recording oracle checks the manifest and exchanges results
  • the reputation oracle checks the manifest and results from the recording oracle

from fortune.

Related Issues (19)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.