ReZor DAO

Welcome to ReZor DAO, your decentralized hub for managing discussions, proposals, and referenda. This guide walks you through the main sections of the interface, helping you understand and participate in the governance process effortlessly.

Why DAO Systems Matter?

A Decentralized Autonomous Organization (DAO) represents a fundamental shift in how communities coordinate, govern, and evolve. Unlike traditional organizations that rely on centralized leadership and opaque decision-making, DAOs are designed to be:

  • Transparent: All decisions, votes, and fund allocations are recorded on-chain, visible to all.

  • Community-Owned: Token holders—not CEOs or boards—directly influence outcomes.

  • Trustless and Autonomous: Smart contracts handle governance logic without needing intermediaries.

Why ReZor DAO Specifically?

ReZor DAO focuses on:

  • Streamlining proposal creation through Preimages

  • Enabling transparent decision-making via Referenda

  • Facilitating dialogue with Discussions

  • Supporting flexible governance with Delegation

The system matters because it puts control and responsibility into the hands of its users, allowing innovation, accountability, and evolution to occur collectively.

1. Dashboard Overview

When you log in to ReZor DAO, you're greeted with the Overview Page — the central hub that reflects the DAO's health and activity. It provides immediate visibility into the operational state of governance processes.

1.1 Why the Dashboard Overview Page Matters

The Overview page is not just a visual dashboard; it serves several critical functions:

  • Governance Awareness: Gives participants a quick snapshot of current and past activities.

  • Transparency: Displays all on-chain activity counts in real time.

  • Decision Readiness: Helps users prioritize where to engage — drafting, discussion, voting, or delegation.

1.2 Summary Metrics Explained

These four metrics form the core of your governance insights:

  • Total Preimages:

    • The total number of draft proposals (preimages) submitted. This indicates how active proposal ideation is within the DAO.

  • Total Referenda:

    • Represents all finalized proposals that have reached the voting stage. Higher numbers suggest good follow-through on drafts.

  • Approved Referenda:

    • The number of proposals that were passed successfully via voting. This reflects how much consensus and actionability exist within the DAO.

  • Active Referenda:

    • The proposals are currently undergoing voting. Monitoring this ensures users do not miss out on timely participation.

1.3 Main Navigation Menu

Use the menu on the left to navigate:

  1. Overview

    • Summary metrics and latest activity.

    • Quick snapshot of all DAO interactions.

  2. Discussions

    • Community conversations around proposals.

    • If it shows "No data", it indicates no discussions have been initiated yet.

  3. Preimages

    • Draft stage of a proposal before it's officially submitted.

    • You can review or create new preimages here.

    • E.g., Shows (3), indicating three preimages exist.

  4. Proposals

    • Finalized proposals are ready for voting.

    • E.g., If it shows (3), indicating three proposals are live.

  5. Delegate

    • Allows you to assign your voting power to another address so they can vote on your behalf.

1.4 Using ReZor DAO in 4 Steps

Step 1: Explore Existing Items

  • View ongoing preimages and proposals via the respective tabs.

  • Check Active Referenda to see what’s open for voting.

Step 2: Participate

  • Join Discussions to share your views.

  • Vote on Active Referenda once you're logged in.

Step 3: Propose a Change

  • Create a Preimage (draft idea).

  • Submit it for voting to turn it into a Proposal.

  • Await results via Referenda status (active, approved, or rejected).

Step 4: Delegate

  • Delegate your vote

  • View and track delegation

  • Revoke (undelegate) when needed

2. Login Options

To interact with ReZor DAO features, you must first log in. ReZor DAO supports two secure login methods:

2.1 Email/Password Login

  • Enter your Username or Email

  • Enter your Password

  • Click Login

Forgot your password? Use the "Forgot Password?" link to reset it.

2.2 Talisman Wallet Connect

  • Click the “Talisman Wallet Connect” button.

  • A pop-up will request access to your wallet addresses.

  • Click "Got it!" to authorize.

  • Once connected, your wallet becomes your identity across ReZor DAO.

Don’t have an account? Click “Sign Up” to register.

2.2.1 Signing Up with Talisman Wallet — Step-by-Step Guide

To participate in ReZor DAO using your Web3 identity, follow these steps to set up your Talisman Wallet and link it to the DAO platform.

Step 1: Install Talisman Wallet

  1. Visit the Talisman Wallet website

  2. Download and install the browser extension for Chrome or Firefox

  3. Open the extension:

    • Accept the terms and privacy policy

    • Set a secure password for your wallet

You’re now ready to configure your network.

Step 2: Add ReZor Network

  1. Open the Talisman Wallet extension

  2. Navigate to Manage Network

  3. Click Add Network

  1. Click “Add Network”

In the form, enter the following:

Field

Value

RPC URL

https://rpc-testnet.rezorchain.com

Chain ID

Will be auto-fetched from the RPC

Network Name

ReZor

Currency Symbol

RZR

Token Decimals

18

  1. Click “Add Network”

Tip: Once added, search “ReZor” in your wallet to confirm it's connected.

Step 3: Add Network in Polkadot

  1. Go to the Settings tab at the top navigation bar.

  2. From the left-side panel, select “Networks & Tokens.”

  1. Ensure Polkadot is selected.

  2. Click the “+ Add network” button in the top-right.

  3. Now, fill in the Network Details

On the Edit Custom Substrate Network screen, enter the following:

  • RPC URL: wss://wss-testnet.rezorchain.com (Paste this under the RPC URLs field)

  • Network Name: ReZor

  • Account Format: Leave it as Polkadot (default)

  • Token Details:

    • Native Token Symbol: RZR

    • Token Decimal: 18

    • CoinGecko ID: Leave empty (optional)

  • Explorer URL: Leave empty or provide a ReZor Explorer URL.

  • Enable “This is a testnet”: Check this option to mark the network as testnet.

  • Display Balances: Toggle to Yes to see token balances on this network.

Step 4: Now Create a New Ethereum Account

  1. In Talisman, go to “Manage Accounts.”

  1. Click “Add Account”

  1. Choose “New” → “New Ethereum Account”

  2. Enter an Account Name (e.g., ReZor Main)

  3. Click Create

Your new Ethereum-compatible address will now be listed under your wallet accounts.

Step 5: Sign Up on ReZor DAO

  1. Visit the ReZor DAO app

  2. On the homepage, click Sign Up

  1. Fill in:

    • Username

    • Email

    • Password

  2. Complete registration

Step 5: Link Your Wallet in ReZor DAO

  1. After login, click on your Username in the top-right corner

  2. Go to “View Profile”

  1. Click “Link Address”

  2. A modal will appear:

    • Click “Select Wallet”

    • Choose Talisman Wallet

  3. Your list of Talisman accounts will be displayed

  4. Select the one you created and click “Link Address”

  1. Approve the request in your Talisman Wallet extension

Your wallet is now connected and ready to propose, vote, and sign transactions in ReZor DAO!

3. New to ReZor? Here's How to Sign Up via Email /Password

Click the "Sign Up" link and follow these steps:

Step 1: Create an Account

  • Enter a Username

  • Enter your Email

  • Click Next

Step 2: Set Password

  • Create a secure password

  • Confirm and proceed

Alternative: You can skip email/password setup by using Talisman Wallet Connect to register and login instantly.

Step 3: Verify Email

  • You’ll receive a 6-digit verification code

  • Enter the code into the input fields

  • Click Verify Code

Tip: If you don't see the email, check your spam/junk folder. If needed, click “Resend” after the countdown.

4. ReZor Dashboard Tour

Once signed in, you land on the Overview screen with four key metrics:

Metric

Description

Total Preimages

Number of drafted proposals

Total Referenda

Proposals submitted for voting

Approved Referenda

Successfully passed proposals

Active Referenda

Live votes open to DAO members

4.1 Navigating the DAO

Use the sidebar to explore:

  1. Overview: See system-wide metrics and latest activity

  2. Discussions: Engage in conversations around ideas or proposals

  3. Preimages: Submit or review draft proposals

  4. Proposals: Vote on formal proposals and monitor their status

4.2 Discussions Tab

The Discussions tab is your space to share and shape ideas before they become formal governance actions. It’s the first step in Rezor’s decentralized decision-making workflow.

Having Discussions summarized in the Overview ensures that even users who don’t enter every section can still track active ideas and emerging consensus. This increases transparency, participation, and engagement across the platform.

What You Can Do in Discussions:

  • Start a New Discussion: Pitch a new idea or concern to the community. Just click "New Discussion," add a title, topic, and your thoughts.

  • Browse Existing Discussions: View a chronological list of community-generated content.

  • Engage: Participate by replying to others’ posts, providing feedback, or showing support (e.g., via upvotes, where applicable).

Fields Displayed in Each Discussion:

  • Title: A short headline of the topic.

  • Topic: Category chosen by the creator.

  • Creator: Username of the person who posted.

  • Created: How long ago it was posted.

4.3 Preimage tab

What is a Preimage?

In ReZor DAO, a Preimage is the draft version of a proposal. It contains the technical information needed to later convert it into a Referendum. Think of it as the proposal's "blueprint."

Once a Preimage is created:

  • It appears in the Preimage tab

  • It awaits promotion to a Referendum by being requested

When you click the “Preimages” tab or see it under Latest Activity, the table includes:

  • Hash: Unique identifier of the preimage (clickable for details)

  • Proposer: Wallet address of the user who submitted it

  • Deposit: Amount locked to submit the preimage

  • Arguments: Function calls or remarks included

  • Size: Byte size of the payload

  • Status: Whether it's requested or not

  • Created At: Timestamp of submission

This area bridges the gap between idea (discussion) and formal proposal.

4.4 Proposal Tab

Once a Preimage is requested and validated, it becomes a Proposal, and eventually a Referendum — a live vote the DAO community can participate in.

What Is a Proposal?

A proposal is a binding on-chain action derived from a preimage, submitted for the community to vote on through a referendum.

Key Fields Displayed:

  • Referendum Index: A unique ID associated with each voting round.

  • Proposal Hash: The hash that links to the preimage logic.

  • Origins: Describes the origin of the call (e.g., root or council).

  • Status Action: Specifies what type of decision event is tied to the proposal.

  • Proposed By: Wallet address of the submitter.

  • Submitted Time: When the proposal entered the queue.

  • Status: Current lifecycle stage (e.g., Preparing, Voting, Decided).

Proposals transition to Referenda, which are listed in the Referenda tab for public voting once prepared and scheduled. This ensures a complete audit trail from idea → to draft → to decision.

From Proposal to Referendum

Once a proposal is submitted:

  1. It gets assigned a Referendum Index

  2. It shows up in the Proposals tab

  3. Status appears as Preparing

  4. It will move to Active status when opened for voting

5. Discussions

The Discussions module serves as the DAO’s primary space for open communication. It allows members to share ideas, flag issues, raise suggestions, or seek feedback before advancing to formal proposals.

In typical governance workflows, discussions precede decision-making. This module acts as the staging ground for community input and consensus-building.

The main panel shows all existing posts, each with:

  • Title or message summary

  • Author

  • Timestamp

  • Reactions (likes/dislikes)

  • Comment count

  • Category or tag

Organize What You See with Sorting

Use the “Sort By” dropdown in the top-right corner of the list to reorder posts:

  • Last Commented – See which threads are currently active.

  • Newest First – Review the latest ideas and questions.

  • Oldest First – Catch up on earlier posts you may have missed.

5.1 Where to Begin

To start a new thread, navigate to the Discussions tab from the left-hand sidebar and click on the “+ Add Post” button located in the top-right corner of the page.

5.2 Features of Discussions

  • Post Listing: Displays latest topics with preview text and metadata

  • + Add Post: Create a new thread on any relevant topic

  • Sort By: Organize discussions by recency or category

  • Badges: Label posts with tags like "Treasury", "Democracy", etc.

  • Vote Buttons: Upvote or downvote posts to signal support

  • Reply Support: Engage in threaded discussions beneath each post

5.3 Step-by-Step: How to Create a Post

  1. Click “+ Add Post”

    • You will be redirected to a clean editor interface for writing your new post.

  2. Enter a Title

    • This field is required.

    • Choose a clear, concise name that communicates the subject of your discussion (e.g., “Proposal to Reduce Treasury Burn Rate”).

  3. Compose Your Post

    • Use the rich text editor to type your message.

    • You can apply formatting such as bold, italic, bullet points, inline code, links, and emojis to improve clarity and tone.

  4. (Optional) Add a Tag

    • Select a relevant category such as Treasury, Governance, or Development to help others filter and understand the topic quickly.

  5. (Optional) Create a Poll

    • Click “Create Poll” if you want community members to signal their support or objection.

    • Voting options (e.g., Yes / No) will appear in the thread with real-time results shown as percentage bars.

  6. Click “Submit”

    • Once ready, submit the post to publish it.

    • Your post will immediately appear in the Discussions list, sorted according to recency or upvotes depending on user view preference.

Why Creating Posts Matters?

  • Surface Ideas Early: Avoids gas fees and effort on proposals that would otherwise lack support.

  • Gather Community Sentiment: Use polls or comments to gauge interest before committing code or deposits.

  • Document DAO History: Every post is a searchable record of ReZor’s governance evolution.

  • Enable Collaboration: Turn an individual idea into a shared, community-backed initiative.

2.4 In-Post Features

When viewing a discussion post, you can:

  • React with emojis or vote buttons

  • Comment

  • View a timeline of edits

  • Participate in sentiment polls (Yes/No)

  • Edit your post, report it, or share externally

6. Preimages

The Preimages tab is where users can submit and view proposal drafts before they are formally turned into Proposals/Referenda.

Overview of Preimages Tab

At the top, you’ll find:

  • Search Bar Quickly find preimages by entering part of a hash or proposer address.

  • Add Preimages Button Allows users to initiate a new preimage submission.

6.1 Preimage Table – Detailed Columns

Column

Description

Hash

Unique fingerprint of the preimage. Click the copy icon to copy it.

Proposer

Wallet address of the submitting user

Deposit

Token stake (in RZR) required to create the preimage

Arguments

Action to be executed on chain (e.g. system.setCode, system.remarkWithEvent)

Size

Payload size of the proposal

Status

Indicates if it has been “Requested” or still “Unrequested”

Created At

Exact date & time of submission

6.2 Add Preimages

If you're proposing a runtime upgrade on the ReZor Chain (like updating the chain logic), the first step is to submit a preimage. This is just a way of uploading the full code (WASM) that you want the DAO to vote on.

6.2.1 What You’re Doing Here

You’re submitting a preimage using the setCode(code) call. This is needed when you're planning a runtime upgrade so the proposal can reference the actual code on-chain.

6.2.2 Step-by-Step Instructions

1. Preimage Submission Window

If you're on the DAO interface, at the top, it shows your RZR balance — this confirms you have enough to post the preimage.

2. Select the Action Type

There are two dropdown menus:

  • On the left: select system

  • On the right: select setCode(code) - event. This is the function that updates the chain's runtime

This tells the system you’re submitting a runtime code update.

3. Add the Runtime Code: Preimage Hash

Whatever you type, it automatically converts to a preimage hash.

Also, you can also toggle “file upload” and select it from your computer and it converts the file into preimahe hash

4. System Auto-Fills Hash and Length

After entering or uploading the code:

  • Preimage Hash: Automatically generated based on the content of your code.

  • Preimage Length: Displays the size (in bytes) of your runtime code.

Important: Copy and store the preimage hash somewhere safe — you'll need it when creating a proposal later.

5. Submit the Preimage

Click the “Submit Preimage” button.

This will:

  • Save your runtime code on-chain

  • Allow others to reference this preimage when submitting a proposal

  • Lock a small deposit

What Happens Next?

Once this preimage is on-chain:

  • Anyone can submit a proposal that references the same hash

  • When that proposal is voted on and approved, the runtime upgrade will be applied

This is a required first step for any on-chain upgrade.

6.3 Note: If you wallet is not linked in ReZor DAO, you can not create Preimages

To create proposals or interact with any on-chain governance features, ReZor DAO requires you to connect your wallet.

If your wallet is not yet linked, you’ll see this message when trying to perform a treasury-related action:

"Link your wallet address"

This modal asks you to:

  • Select a wallet (currently supports Talisman)

  • Grant ReZor Assembly access to your wallet

  • Assign a wallet address for proposal creation

You’ll see a blue button:

  • Link Address → triggers wallet access and connection setup

Steps to Link Your Wallet

  1. Open your Talisman Wallet Extension

  2. Navigate to Preimages, Proposals, or Treasury modules

  3. When prompted, click “Link Address”

  4. Confirm the connection in your wallet

  5. ReZor Assembly will now have access to your address

Once linked, your wallet becomes your on-chain signature identity.

Pro Tip: If you change devices or reset your wallet:

  • You may need to relink it for ReZor DAO to recognize it.

7. Proposals

Once a Preimage is created and prepared, it can be submitted as a Referendum using the “Add Referenda” button.

Overview of Proposals:

  • Search Field: Lookup a proposal by its Referendum Index or Proposal Hash

  • Add Referenda: Triggers a form or modal to create a new referendum using a previously submitted preimage

  • Copy Icons: Let you easily grab hash or wallet values for reuse

7.1 What You See in Table:

Column

Description

Referendum Index

Numerical ID for the live proposal

Proposal Hash

Unique hash identifying the code logic submitted

Origins

Authority of submission (e.g., root)

Status Action

Governance command used (e.g., referenda.submit)

Proposed By

Wallet address initiating the proposal

Submitted Time

Exact timestamp of proposal submission

Status

Lifecycle stage (Preparing, Active, Approved)

In your table, all are still in Preparing status — meaning they’ve been submitted but are not yet open for voting.

7.2 How to Use “Add Referenda”

  1. Click the Add Referenda button (top right)

  2. Choose the associated Preimage (usually by Hash)

  3. Submit metadata (optional: title, justification)

  4. Confirm and authorize via wallet

  5. Proposal will enter “Preparing” state before being scheduled

7.3 Step-by-Step: Submitting a Proposal

1. Choose the Submission Track

  • Field: Submission track

  • Select: 0 / Root (This means the proposal requires full administrative rights)

This decides how strict the voting process will be. “Root” is typically used for sensitive actions like runtime upgrades.

2. Select Origin and Call

This section confirms the origin and call:

  • Origin: Should match what’s required for the action (like Root or a collective)

  • Pallet / Module: system

  • Call: setCode (via DispatchRawOrigin)

If you're submitting a proposal to set new runtime code, leave these fields as they are.

3. Enter Preimage Hash

  • Field: preimage hash

  • What to enter: The hash you got after submitting your preimage

You can copy this from the preimage submission window or from your chain explorer if it's stored on-chain.

This connects your proposal to the actual action that should be executed (e.g., the code change).

4. Enter Preimage Length

  • Field: preimage length

  • Enter the number of bytes in the preimage data (your WASM runtime or call payload)

This must match the original preimage you submitted, or the proposal won’t be valid.

5. Set Delay (Optional)

There are two tabs:

  • After delay (default selected)

  • At block (manual block number)

Under After delay, set how many blocks to wait after approval before the proposal is executed.

  • Example: 100 blocks (this gives a delay after the vote passes)

6. Review the Submission Deposit

This field shows the submission deposit in RZR (e.g., 1.0000 RZR). It will be locked while the proposal is active and refunded after the process completes or is canceled.

7. Submit the Proposal

Click “Submit” at the bottom.

This will:

  • Create the proposal and link it to your submitted preimage

  • Start the governance lifecycle (discussion, voting, execution)

What Happens After Submission?

  • The proposal appears in the governance queue

  • Other members can view it and vote

  • If enough votes pass (according to the track’s rules), the action is executed

For example, if you're upgrading the runtime, the chain will schedule and apply the change after the configured delay.

7.3 Behind-the-Scenes Logic

  • Every Referendum is a binding on-chain vote

  • Only proposals with verified Preimages can become Referenda

  • Once moved to “Active”, DAO members can vote on it using their wallet

8. Delegate

ReZor DAO allows you to delegate your voting power to another trusted wallet. This ensures that even if you're inactive or away, your interests can still be represented during referenda.

8.1 What Is Delegation?

Delegation lets you:

  • Assign your voting rights to another account (a delegate)

  • Stay involved without casting votes manually

  • Define how strongly your vote is counted through conviction

8.2 Delegation

Once you visit the Delegate tab, you'll see a table (currently empty in your screenshot) that includes:

Column

Description

#

Serial number

Block Number

Block at which the delegation was made

Delegated To

Address receiving your voting power

Vote Value

Amount of stake/vote weight you've delegated

Conviction

A multiplier that increases the voting impact over time

Track

Proposal category being tracked (e.g., all, root-only)

Deleted At

If revoked, shows when delegation ended

Action

Buttons for editing or removing the delegation

8.3 Step-by-Step: Delegating a Vote

1. Select "Delegate from address"

Use the dropdown to select your own wallet/account that holds the tokens. This is the account you're delegating from.

2. Choose "Apply delegation to all tracks" (Optional)

Toggle this ON if you want your delegation to apply to all governance tracks (not just one specific topic).

3. Submission track

If you leave it OFF, you'll be asked to choose a specific Submission track (like “0 / Root” — used for high-privilege proposals like runtime upgrades).

Note: You cannot delegate using the same Root origin more than once. If you're delegating to someone else and have already used Root for another delegation, you must update the value or choose a different track to proceed.

4. Set the Delegated Vote Value

In the Delegated vote value field, enter the amount of RZR tokens you want to delegate.

This determines the voting weight your delegate will use on your behalf.

Note: You don’t lose ownership of your tokens — they stay in your account. But the delegated voting power is locked based on your conviction.

5. Choose Conviction (Voting Power Multiplier)

The Conviction dropdown lets you decide how much weight your vote should carry and how long it will be locked:

Conviction Option

Meaning

0.1x voting balance, no lockup period

Minimal influence, no locking of funds

1x voting balance, locked for 1x duration

Full voting power, funds locked for fixed time

2x, 4x, 8x, etc.

Higher weight, longer lockup periods

6. Enter Delegate’s Address

Paste the wallet address of the person you’re delegating to in the “Delegate to address” field.

7. Click "Delegate"

After filling all required fields, click the “Delegate” button to confirm.

Once submitted:

  • Your chosen delegate can now vote on your behalf.

  • The vote value and conviction you set will apply.

  • You can revoke or change delegation at any time through the same interface.

Higher conviction = higher vote weight, but longer lock on your tokens

8.4 Managing Your Delegations

Once you've delegated your vote, you can monitor and manage it from the Delegate tab in your dashboard. This section displays all your active and past delegations, including who you’ve delegated to, on which track, and with what conviction.

What You Can See Here:

Each row in the table represents a delegation you’ve made:

Column

Description

Block Number

The block in which the delegation was recorded

Delegated To

The wallet address of the delegatee (truncated for readability)

Vote Value

The amount of RZR delegated

Conviction

Voting power multiplier and lockup condition (e.g., No lockup period)

Track

The governance track this delegation applies to (e.g., Root, Whitelisted)

Deleted At

When the delegation was revoked

Action

Option to Undelegate and reclaim your voting power

8.5 How to Undelegate

If you no longer want to delegate your voting power to someone, you can undelegate it at any time. When you click "Undelegate" from the Delegation table, a confirmation popup like this appears.

Once undelegated:

  • Your voting power is no longer assigned to the delegatee.

  • You can reassign it to someone else or vote directly.

9. DAO Flow For Better Understanding

Phase

Tab Name

Status

Draft

Preimage

Unrequested

Proposed

Proposal

Preparing

Voting

Overview

Active

Outcome

Overview

Approved / Rejected

PreviousReZor Scan (Explorer)

Last updated