What is the purpose of the Radiant DAO Forum?

Radiant Capital operates as a DAO, or a Decentralized Autonomous Organization.

The DAO serves as the community-driven governance arm of Radiant Capital.

This forum is vital to the proper formation and organization of community-led initiatives which will determine the future of Radiant.

How does this forum work?

The forum is split into two main categories:

  1. Proposals
    This is a token-gated section for members of the Radiant DAO where RFP Ideas are submitted as topics using a template-based format. Because this section is directly part of the governance process, all submissions must adhere to a template format and be approved by a moderator before being made viewable to the public.

    The criteria for commenting and posting in this section can be viewed here.

  2. Feedback
    This category is open to anyone registered on the forum to provide informal feedback or ask questions pertaining to Radiant. Although not a formal part of the governance process, the Feedback category can serve as a staging ground for suggestions to take shape and find their way into a more formalized proposal.

What is an RFP?

An RFP (Radiant Foundation Proposal) is a document proposing a new feature, project, activity, goal, piece of information, or change to any proposal that has already been implemented.

RFPs are the basis of inciting meaningful change to the Radiant ecosystem. The creation and refinement of such proposals are how initiatives are ultimately taken to an on-chain vote via Snapshot.

You can view RFP-1, which outlines both the capacity of the DAO, as well as the RFP process, here.

How can I participate in the Radiant DAO?

The sole requirement for membership in the DAO is to have any given amount of RDNT tokens held within Radiant’s MultiFeeDistribution smart contract (hereby referred to as “locked RDNT”).

The DAO is comprised of two interconnected parts:

  1. Forum — community.radiant.capital
    • This website. This is the communications and discussion platform, where governance proposals, ideas, feedback and dialogue are introduced, discussed and refined.
  2. Voting — dao.radiant.capital
    • Proposals which have gone through due process and have been formalized into RFPs will subsequently be elevated to a formal on-chain vote.

All are welcome to begin discussing and collaborating on ideas & improvements for Radiant Capital.

Community discussion isn’t limited to this forum! The other primary hub for Radiant-related discussion and news is our Discord server.

What is token gating? Why am I being asked to authenticate my wallet?

Token gating is a process in which a user’s crypto wallet is authenticated to verify ownership of a certain asset (in this case, locked RDNT) in order to access certain functions on a platform.

To serve the needs of the DAO, we have custom-built an authentication process based on the Unlock Protocol framework.

This process connects your user account to your active wallet, granting you additional permissions on this forum.

The authentication process is gasless. Your 0x wallet address is encrypted and inaccessible to other forum members and moderators.

All wallet authentication data is periodically flushed every 12 hours, both as a security measure, and to ensure that user permissions accurately reflect a user’s token balance.

This utilizes the EIP-4361 standard for Ethereum-based authentication.

What are the two token-gated levels?

To participate in the Proposal section, you must first authenticate your wallet, which will check your balance of RDNT locked within the protocol’s MultiFeeDistributor contract. If you meet a certain criteria, you will be automatically granted one of two roles:

  • DAO-Member (≥1 locked RDNT)
    Grants you permission to comment on and upvote all RFP Ideas in the Proposal category.

  • DAO-Author (≥2500 locked RDNT)
    Grants you the additional ability to post new RFP Ideas in the Proposal category.

Why do I need 2500 locked RDNT in order to create an RFP?

It is vital to the integrity of the DAO that RFPs are initiated by actively engaged holders within the Radiant ecosystem. 2500 locked RDNT demonstrates both familiarity with our platform and commitment to its success.

How do I disconnect a previously-connected Metamask wallet to authenticate another?

The manual “Authenticate Wallet” feature defaults to a previously-connected Metamask wallet. To authenticate a different wallet (you might have different amounts of locked RDNT in different wallets for a certain reason), you must first use Metamask to remove the previously-connected wallet from connected sites, then select “Authenticate Wallet”

  1. Go to your wallet and expand the menu to access Connected sites option

  2. Expand Connected sites menu

  3. Disconnect community.radiant.capital from the connected sites list.

FAQ-Disconnecting a wallet
FAQ-Disconnecting a wallet1468×1026 67.8 KB

How do I propose an RFP Idea?

It may seem confusing at first, but RFPs can be put up for discussion fairly easily.

  1. Authenticate your wallet, ensuring you have adequate permissions.
  2. Select from the navigation panel.
  3. Select “Radiant Foundation Proposals (RFPs)” from the category drop-down menu.
  4. Choose one applicable RFP category tag for your new proposal.
    737×263 14.2 KB

Don’t worry if your submission isn’t immediately viewable–all RFP submissions must be approved by a moderator first.

Once approved, your RFP will be open to user feedback. Be sure to stay involved with this process to provide clarification if needed, and to ensure your proposal is given serious consideration.

What is the life cycle of an RFP?

RFPs go through a process involving several checks and balances to ensure each proposal operates within the best interest of the DAO.

Here are the stages an RFP goes through before it is voted on via Snapshot:

  1. A DAO-Author initiates a foundation proposal (RFP Idea).
  2. One of the DAO Moderators approves the initial submission, and it becomes viewable to public.
  3. All RFP Idea submissions automatically enter a 7 day feedback period, in which they are presented to the DAO community for informal feedback.
  4. The submission topic automatically archives. The proposer can now directly submit a formal RFP Draft to the DAO Administrator via pre-determined RFP templates.
  5. RFP Draft is reviewed by the DAO Administrator, and will either be approved or not approved, based on whether it adheres to the DAO guidelines.
    • If an RFP Draft is approved as complying with DAO-approved guidelines, it becomes a Pending RFP.
    • If an RFP Draft fails to comply with DAO-approved guidelines, it is eligible for resubmission except in cases of violation of the law or reasonable suspicion of fraud or other misleading information.
  6. Pending RFPs that have passed RFP Moderation will then either be tagged as “Approved to Vote” or “Needs Administrative Review”
    • Approved to Vote: any pending RFP whose costs, content, and implications are considered to be straightforward and of no risk to the well-being of the DAO.
    • Needs Administrative Review: any pending RFP whose costs, content, or implications are considered to be complicated or a potential risk to the well-being of the DAO. Any Pending RFP that is tagged as “Needs Administrative Review” must pass a Council vote before proceeding.
  7. Drafts that have passed their respective approval processes will become a Live RFP on Snapshot during the next Weekly RFP Release. These RFPs are now open to the formal on-chain voting process.
  8. If the on-chain vote passes, the RFP becomes ratified and will move to implementation.

When are Weekly RFPs released to Snapshot?

New RFPs tagged as “Approved to Vote” are released in batches every Thursday at 9PM ET.

How does the on-chain RFP voting process work?

All RFPs released to vote will undergo a 24hr delayed “warm-up phase,” in which the RFP is submitted to Snapshot for public view, but is not yet committed to the blockchain or eligible for voting. This gives the Author, Council and/or Admin time to correct any errata before the proposal details are permanently locked on-chain. The warm-up phase only provisions for
typographical or numerical errors and not for significant changes to the RFP content itself.

Once live on Snapshot, Live RFPs are open to voting until Weekly Voting Close, which is when all active Live RFPs close for voting at approximately 9PM ET on the Wednesday following their release.

What criteria are needed for a Snapshot RFP to pass?

The quorum requirement for a Live RFP will be 10% of the circulating supply of locked RDNT.

Once quorum has been met, a Live RFP may only be passed with greater than 50% of votes cast “In favor”.

A Live RFP which has not received greater than 50% of votes cast “In favor” will not be passed.

A Live RFP which has met quorum and achieved greater than 50% of votes cast “Infavor” will be deemed an Accepted Final RFP.