Editing
Roll ups
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Roll up process == A roll up consists of off-chain work that will be policed by other DAO members. This section gives a basic outline of how a generic roll-up process functions, following standard [[DGF workflow|DGF work flow]]. A roll-up Work Smart Contract (rWSC) is made to specify the standards the rWorker must adhere to in performing the roll up, and to automate the [[executive governance]] of the work. # rWorkers encumber their rREP into r[[Availability smart contract|ASC]]<nowiki/>s to signal their availability to perform roll up work. # The rWSC pseudorandomly picks an rWorker, weighted according REP encumbered in all rASCs. # The rWorker does the roll-up work off chain as prescribed in the rWSC. # The rWorker submits their evidence of the completion of their work using the rWSC to the Forum. # The rWSC sends the $ fees for the work and the rWorker's rREP to open a Validation Pool: ## The VPSC mints and distributes the proper new REP created during the work and distributes the $ fee to all rWorkers via the REP salary. === Example Validation Pool roll up === ''Main page: [[Validation Pool roll up]]'' On-chain voting is inefficient and prohibitively expensive. However, voting is necessary for decentralized [[governance]]. To maintain robust decentralization, every member of the DAO should be permitted equal opportunity to participate in policing by voting with their REP tokens. But each time a member votes with a REP token becomes a separate transaction. Also, properly participating members should have their REP holdings augmented with newly minted tokens (to solve the "nothing at stake problem"), which necessitates yet another transaction. Instead of doing all of these operations separately and on chain, it is more efficient to handle the operations off chain, then roll up the result in a single transaction in a single block. Even better, efficiency is improved if we bundle together a sequence of several separate instantiations of Validation Pools. Therefore a roll up is required. Fortunately, DGF is designed for the express purpose of governing off-chain work. For explicit details of a Validation Pool roll up, see [[Validation Pool roll up|this page]].
Summary:
Please note that all contributions to DAO Governance Wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see
DAO Governance Wiki:Copyrights
for details).
Do not submit copyrighted work without permission!
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Create account
Log in
Namespaces
Page
Discussion
English
Views
Read
Edit
Edit source
View history
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
What links here
Related changes
Special pages
Page information