Guardian Network

DAO Guardian System

  • Every Aragon user who stake a minimum amount of ANT becomes a Guardian of the Aragon DAO with a GuardianID (BrightID)
  • Once an Aragon Guardian you can choose different Aragon roles. Each of the roles may require different requirements. All roles are linked to the GuardianID
  • The first roles for the Aragon DAO will be Court Juror & Voter
  • Every guardian has a certain level based on their role activities within each DAO.
  • All role activities are rewarded with XP and linked to the Guardian ID (brightID). 1XP = 0,01$ value added to a DAO
  • The more active your are in your roles the more XP you gain the higher your Guardian Level in each DAO.
  • the more XP your earn (every DAO has different parameters)…
    ** the more daily ANT you get :star:
    ** the higher your voting power for your staked/delegated ANT
    ** the more likely you get chosen for limited roles
    ** the more Role Boosters you will get :star: :star:
  • This Guardian System can be implemented and adapted by any Aragon DAO.

:star: daily ANT / passive income will be paid at the beginning with the ANDAO treasury money. Once the treasury runs out of ANT we need ANT inflation. In this way ANT will go from the unproductive ANT holders to the productive ANT holders (Guardians). This benefits the hole ecosystem cause the value increase by supporting the most active users in our ecosystem will create more value than the cost of the inflation. I think a health inflation would be 10% per year and perhaps every 2 years it reduces by 1% til it stabilise at 3-4%

:star: :star: XP earnings for each role gets monitored on chain and linked to the GuardiansID in order to reward guardians with Boosters (rewards/benefits) tailored to the specific roles. For example if a guardian earned a certain amount of XP as a juror s/he will get selected for a case more likely (juror boosters) or if s/he worked as an ANT delegate s/he will get ranked higher in the delegate ranking (delegate boosters)


In the near future there will be no Aragon Association. There will be only ANT holders, Aragon users and Aragon Guardians. An Aragon team member who is a developer at the Association today will be a Guardian with a developer role tomorrow. The Aragon Ecosystem will become an open real life game. All Aragon DAOs will be able to get gamified by just implementing the Guaridan System. Every DAO can create roles and implement a reward system for their guardians.

Every Guardian will be able to create their unique personal Avatar/NFT, which s/he can use in the guardian system to earn xp and level up. This avatar is linked to the guardianID and only has power in the hands of the rightful owner. daos will give artefacts/badges/nfts to the avatars for reaching certain milestones/levels. each artefact has different features and conditions (earned a certain amount of XP in a specific DAO role). For example a certain Aragon-Court badge can only be worn by an avatar/guardian with a certain Aragon-Court XP amount. When equipped it gives the holder for example a 10% higher chance to get elected in the Aragon-Court. Users can sell the artefacts on the open market. avatars can only wear a certain amount of artefacts.

Each Guardian has its own DAO with a governance token. The GuardianDAO holds the NFT/Avatar gets the revenue from roles etc. The DAO is linked to the GuardianID. Similar to bitclout users can purchase the GuardianDAO token based on the universal XP/$ Guardian curve. The money goes into the GuardianDAO and only get spent based on the GuardianDAO Agreement which is protected by Aragon Court/Govern. The more XP a Guardian earned the more tokens s/he mints and the higher the token price. the newly minted governance tokens get distributed to the holders of the token. GuardianDAO token can be swapped with other GuardianDAO tokens based on the XP/$ curves. Each GuardianDAO gets represented by the Guardians Avatar. When making a post for example in the Guardians Network the post will be ranked based on earned XP from verified DAOs (token marketcap).

The Guardian Network will be a Social Network similar to Decentralized Social (DESO) where developers can build social apps on top of the Guardian Network to empower and connect GuardianDAOs and DAOs in general.


I think this is a fantastic proposal and it aligns well with other ideas I’ve been developing.

A concept for rewarding voting participation in a healthy way:

An implementation of Commitment voting:

And Delegation:

The only bit I’m not sure is Guardians being the only ones who one can be delegate to. That would mean that Guardians are the voters that matter most and if they also get drafted through Court, the separation of powers suffers.


so everyone will have an Aragon score based on how much s/he participate? based on this score you get more or less passive income?

What about if we define active aragon user as Guradians? So in order to become an guardian you have to stake ANT. I think this is very important because only then you have skin in the game. Also we want to reward users to become Guardians because they are the backbone of aragon

1 Like

For 10% inflation to generate more value than it “costs” I’d suggest that Guardians are not the only ones who should benefit from this, but community contributors in general. Also considering the project has been live for 5 years, maybe 10% reduction to previous contributors is a bit steep, but we could run a vote to find the right number.

1 Like

Everyone can become a guardian and apply for different roles in the aragon ecosystem.

no clue just first suggestion didn’t put much thought into it

1 Like

I like this proposal, but it seems to require code upgrade to Aragon Court v2, so it will take some time to integrate and audit. In case DID (BrightID) is attached, I suggest to also include branched courts and qualification proofs in the scope of AC v2. The general idea, is that only guardians with qualification proof attached to their DID can be elected to rule over cases in that branch. It should be also possible to set custom fees for different branches of AC, the main use case for branched court would be more complex cases, which are hard to verify by a common person, like deliveries of IT products and financial contracts.

Branched courts can be potentially sold as a product to other DAOs so they can tailor jurisdiction comfortable for them in scope of custom Govern disputer. Though monetisation of such product is a topic for another discussion.

I don’t understand. Why does this require code update to Aragon Court v2?
I was thinking that everyone can become a Guardian and get the jurors role assigned as long as s/he stakes the minimum ANT required for this role. Every guardian has a brightID to link the XP, Level and roles to it. Perhaps for the main court role you just need to stake a certain amount of ANT but if you want to take part in specialised/sub court roles perhaps you need to pass a test or something not sure.

I feels branch courts are an interested concept but i don’t understand how they are relevant to this proposal. I would like to know more about it. Is this the aragon v2. proposal Proposal: Aragon Court deployment to Polygon ?

I think Aragon Court deployment to sidechains can be done in the scope of the current codebase. My main concern is that the current Aragon Court code doesn’t utilize DID in any way. So if we keep all DID interactions fully off-chain, then you are right and it doesn’t require an update of AC code.

I assumed you suggested integrating DID into the guardian drafting process on-chain, so it will affect on-chain logic (chance to be drafted for the case etc). If it was the case, I would include more changes, which I mentioned. I hope it makes more sense now.


What do we have to consider in oder to make this proposal reality? How would we develop the features mentioned in the proposal (bullet list)?

  • Every Aragon user who stake a minimum amount of ANT becomes a Guardian with a GuardianID (BrightID).
  • Once a Guardian you can choose different Aragon roles. Each of the roles may require different requirements. All roles are linked to the GuardianID
  • All actions are rewarded with XP and linked to the Guardian ID (brightID).
  1. upgrade to Aragon Court v2 in order to integrate BrightID/GuardianID into Aragon Court and reward jurors with boosters. @voronchuk
  2. thesis-on/proposal-for Web3 decentralized identity system model for platform(DApp layer) builders #identityAlliance @BrightIDProject @identityindex

Idea how to implement BrightID/GuardianID from @bitsikka BrightID Discord Admin

Let it be clear that BrightID - the public key - the node in the social graph stored and processed by BrightID nodes - is mostly private. You can find your public key in Menu → Copy Explorer Code. That key although a “public key” is not even known to integrated apps as far as I know. - Node in social graph that represents you holds no PII(Personally Identifiable Information). - Your name, Photo is actually only stored locally in your phone. Optionally when you supply password they are stored encrypted (currently in BrightID managed centralized server) so that you can recover your contacts/pfp/names when you do Social Recovery (edited)

What you are talking about is storing PIIs. A complementary standard / solution exists. What you could do is use W3C standard for decentralized identity called DID specification. DIDs are implemented by Ceramic network and few others. DIDs are all about data data data. You can store any/all kinds of user data. Behind the scene I believe Ceramic can store data in IPFS, Araweve, Filecoin or any other decentralized storage solutions. Just like one BrightID can be associated with multiple Wallets, Web2 accounts, Discord accounts or what have you (BrightID calls each app “context” and the ids they use “context-ids”) one can also associate DIDs. DID data is owned and controlled by the user themselves. (edited)

BrightID itself might be using DIDs to store a person’s name and pfp in DID thus moving away from having to store encrypted in centralized servers. Thus, also giving user’s data back to user with autonomy.

The magic that makes “context-ids” un-linkable to BrightID pk is called “Blind Signature”. Most of these are discussed in BrightID :classical_building:forum posts and Github issues.

Hope that helps improve your mental model of where BrightID fits in the system you are designing.

Here is how I saw it(the user model) a while ago. Still see it that way.

1 Like