Code Monkey home page Code Monkey logo

Comments (3)

djstrikanova avatar djstrikanova commented on July 19, 2024

I think there will be interest at some point to allow the DAO to choose a percentage of these network fees to be burned as well. There was a proposal passed on this a while back

https://dao.effect.network/proposals/17

from effect-network.

jeisses avatar jeisses commented on July 19, 2024

I think there will be interest at some point to allow the DAO to choose a percentage of these network fees to be burned as well. There was a proposal passed on this a while back

https://dao.effect.network/proposals/17

Thanks for bringing that up, we should keep this in mind.

Currently all fees are being collected to feepool.efx and from there they are distributed to guardians every cycle.

This might be the right place to actually perform the burn - maybe we can use a vector of "fees" that are taken from the worker, that can be configured by the DAO.

The default value would be:

  • 5% guardians
  • 5% burned

The remainder of the value would always go to the worker (90% in the above case).

I also had a discussion with Laurens about taking the fees on publishbatch instead of payout. This means fees will come in quicker, and the logic is more "requester pays fees" than "worker pays fees" (example: from the task reward 100% goes to the worker; the requester would just pay on top). This also works nicer if network fees change in the future.

from effect-network.

laurensV avatar laurensV commented on July 19, 2024

To expand a bit on the discussion me and Jesse had: In order to do it on publishbatch we also have to implement an additional check to see if the batch is funded for both the fees and the costs for the tasks, but it would save quite a lot of time in the frontend adjusting for fees in worker payouts, so I prefer the publishbatch option. It also shows better that the fees are being paid by the requester, not the worker.

A downside to this is that if you decide to cancel your batch or not all tasks get done, you already paid the fee for all tasks in your batch (while with the payout option you only pay fees for tasks that are actually done), but I don't think its that big of a problem.

from effect-network.

Related Issues (20)

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.