U. Diamond UI User Guide and Wallet Compatibility

This guide covers Diamond UI staking, pool management, governance access, and DMD name workflows, followed by wallet compatibility reports. For an overview of the application, see Diamond UI.

On this page

• Connect and Access the Interface
• Review Your Profile and Validator Pools
• Create and Manage a Pool
  • Create a Pool
  • Configure a Node Operator Share
  • Remove a Pool
• Delegate DMD
• Withdraw Stake
• Understand Automatically Restaked Rewards
• Manage DMD Names
  • Find a Name
  • Register a Name
  • Review and Manage Owned Names
  • Change the Active Name
  • Renew a Name
  • Transfer a Name
  • Report a Name
  • Configure Website and Email Settings
• Wallet Compatibility
  • Test Results and Community Reports
  • Maintaining the Test Record

U.1 Connect and Access the Interface

1. Open Diamond UI Mainnet or the separate Diamond UI Testnet.
2. Select Connect and choose your wallet or its supported connection method.
3. Confirm that the wallet is connected to the intended DMD network and account. Keep DMD available in the account for transaction gas fees in addition to the amount being staked.
4. Review requested transactions in the wallet before confirming them. The interface updates after the transaction is processed.

Wallet support varies by platform and operation. See Wallet Compatibility below. WalletConnect connects the interface to a compatible wallet; it is not a wallet itself.

The application can also run locally with a configured DMD RPC endpoint, including a user's own node. This requires access to the network and a working endpoint. Hosted statistics and other external services may remain unavailable independently of core contract interactions.

U.2 Review Your Profile and Validator Pools

Your profile provides account and pool information, including your name where available, stake, delegations to other pools, delegates to your pool, Bonus Score, governance voting weight, and any configured node operator share. Network views provide epoch and network statistics and access to DAO information.

Open Validators to review pools. A pool's detailed view includes its address or name, validator node address, public key, stake and delegation information, status, score, connectivity reports, and available histories. Governance history is available through the DAO module.

The DAO module provides proposal submission, voting, history, finalization, and execution. See DAO Governance for the rules and the DAO Proposal and Voting Guide for the workflow.

Connectivity Report (CR) indicates how many other active validators have reported connectivity problems with the validator.

Status	Meaning
Active	In the current active validator set.
Standby	Eligible for selection but not in the current active set.
Invalid	Does not meet the required availability or staking conditions.

Use the available filters to review candidates and pools you have staked on. Eligible Candidates groups Active and Standby pools. Selection uses stake, Bonus Score, and randomness; registration or eligibility alone does not guarantee selection or rewards.

U.3 Create and Manage a Pool

U.3.1 Create a Pool

1. Prepare a synchronized validator node and its required configuration. See Validators for the prerequisites.
2. Connect the wallet that will own the pool and open your profile.
3. Select Create a pool.
4. Enter the owner stake and the requested node public key. The minimum owner stake described in the Whitepaper is 10,000 DMD; the contract and interface determine the applicable requirement.
5. If using a separate node operator, configure the operator address and reward share.
6. Review the details and confirm the transaction in your wallet. Check the resulting pool information after processing.

Pool registration and selection for the active set are separate steps. The node must also meet the availability and validator-preparation requirements.

U.3.2 Configure a Node Operator Share

The pool owner can configure an operator address during pool creation or later through the profile. One recipient is active at a time; changing it replaces the previous recipient. Changes are limited to once per epoch.

The share is expressed as a percentage of the pool's allocated reward and is paid from the upfront owner portion. See Node Operator Share for the range and allocation examples. An operator payment does not transfer pool ownership or governance voting rights.

U.3.3 Remove a Pool

1. Open the pool owner's profile and review whether removal is available. An active validator pool cannot be removed while it remains in the active set.
2. Select Remove pool when permitted and follow the withdrawal information shown by the interface.
3. Review and confirm the transaction, then check the updated pool and withdrawal state.

The required minimum owner stake cannot be partially withdrawn in a way that leaves a registered pool below its minimum; removing the remaining owner stake follows the pool-removal process. The pool owner's staking address (the wallet account used to manage the pool in Diamond UI) and the validator's mining address are fixed for that pool and cannot be replaced. After the pool is removed, neither address can be reused to register a new pool.

U.4 Delegate DMD

1. Choose an eligible pool from the validator list or open its detailed page.
2. Select Stake and enter the amount to delegate.
3. Review the pool, amount, and transaction fee, then confirm in your wallet.
4. Check your updated delegation after the transaction is processed.

The minimum initial delegation described in the Whitepaper is 100 DMD and is configurable through governance. Top-ups to an existing delegation can be smaller. The 50,000 DMD pool limit restricts additional deposits; accumulated rewards can take a pool's balance above that amount.

A new delegation to an active pool becomes effective for reward participation from the next epoch under the staking rules. Receiving rewards still depends on the pool's selection and eligibility. Use the effective timing shown by the interface.

Moving a delegation must follow the available withdrawal and staking operations.

U.5 Withdraw Stake

Open the relevant delegation or pool and select Unstake. The Unstake DMD dialog shows the actions available for your balance: claiming a previous order, withdrawing immediately available stake, or placing a new unstake order. Where supported by the current balance, claiming a previous order can be combined with an additional withdrawal or a new order in the same flow.

Available action	What to do	Result
Claim	Review the amount marked Ready to withdraw now, then select Claim.	Receives funds from a previous unstake order that has become claimable.
Unstake	Enter an amount within Available to unstake now, then select Unstake.	Withdraws that amount immediately without creating an order.
Place unstake order	Enter an amount within Available to order, then select Place unstake order.	Creates a new order. These funds can be claimed after the required epoch transition; placing the order does not transfer them to your wallet immediately.
Claim & Unstake	Select Also unstake additional funds now, enter the additional amount, and select Claim & Unstake.	Claims the previous order and withdraws the additional available stake. Receive now shows their combined amount before network fees.
Claim & Place order	Select Also place an unstake order, enter the order amount, and select Claim & Place order.	Claims the previous order and places a new order. Receive now includes only the claimable funds; the new order must be claimed later.
Pending unstake	If an existing order is not yet claimable and no other withdrawal action is available, close the dialog and return when the funds are ready.	The order remains pending until it becomes claimable.

Review Receive now, any New order, and the remaining stake where shown before submitting the selected action. Confirm the transaction requests presented by your wallet. Amounts shown as receivable are before network fees.

Available actions depend on your balance and the pool's state. Owner withdrawals must respect the pool's minimum owner stake and removal conditions. An ordered withdrawal requires a later claim once eligible.

U.6 Understand Automatically Restaked Rewards

Allocated rewards are added directly to staked balances. They follow the staking withdrawal rules rather than being held in a separate reward account.

For example, if your stake is 500 DMD and your allocated reward is 10 DMD, the resulting staked balance is 510 DMD. This is an arithmetic illustration, not a promised reward or rate of return. See Validator Reward for allocation and eligibility.

U.7 Manage DMD Names

Diamond UI provides registration and management of human-readable DMD names. For ownership rules, name format, fees, validity, and moderation, see DMD Naming System. A displayed name identifies an associated address in supported views; review the address and transaction details before confirming an operation.

U.7.1 Find a Name

Use the name-search field on Home, open DMD Ecosystem → DMD Names from the header, or open My DMD Names from your profile.

1. Enter the desired name in the search field; the interface displays the .dmd suffix separately.
2. Select Search to check the name.
3. Review its availability. For a registered name, open its name page to inspect ownership and history. For an available name, proceed to registration.

The DMD Names catalogue also supports searching the list by name or owner address, filtering, and sorting. This catalogue search is separate from the availability search used to register a new name.

U.7.2 Register a Name

1. Connect the wallet that will own the name and check its network and account.
2. Search for an available name and select Register name.
3. In the Create dialog, review the name, minting fee, estimated gas fee, and total estimated cost.
4. Review the information about activation. If the address has no active name, the new name is activated automatically. If it already has an active name, the new name is created but remains inactive until you activate it; the current active name is unchanged.
5. Select Confirm & Create, then review and confirm the transaction in your wallet.
6. After confirmation, open My DMD Names to review the registered name.

Keep enough unstaked DMD in the wallet for the minting fee and gas. Use the current fee shown by the interface rather than assuming the initial minting-fee value still applies.

U.7.3 Review and Manage Owned Names

Open your profile and select My DMD Names. The page shows the active name, the number of owned names, names nearing expiration, and an Owned names table with status, expiration, and last-action information.

Use Manage for the actions available to a name. Select the name or History to open its history page. The history view includes the creator, creation time, current owner, activation timeline, ownership transfers, and links to transactions in the explorer.

U.7.4 Change the Active Name

An address can own multiple names, but only one can be its public active name at a time.

1. Open My DMD Names and locate the owned name you want to use.
2. Open its Manage menu and choose the available activation action.
3. Review the selected name and the applicable activation fee and gas before confirming in your wallet.
4. After confirmation, check the active-name information.

See Activation Fee for the fee schedule when changing the active name.

U.7.5 Renew a Name

1. In My DMD Names, open Manage → Renew for the name.
2. Review the current expiration date, the keep-alive action, and estimated gas cost.
3. Select Confirm & Renew, then review and confirm the transaction in your wallet.
4. Check the updated expiration after confirmation.

Renewal sends a keep-alive transaction and resets the 10-year validity window from the time of confirmation. It can be performed before the final year; there is no need to wait for an expiration reminder.

U.7.6 Transfer a Name

1. In My DMD Names, open Manage → Transfer for the name.
2. Enter and verify the recipient's wallet address.
3. Review the transfer fee, estimated gas fee, and total estimated cost.
4. Select Confirm & Transfer, then review and confirm the transaction in your wallet.
5. After confirmation, check the updated ownership and transfer history. The transferred name is removed from your owned-name list.

Diamond UI includes the mandatory transfer fee. A standard NFT transfer through another wallet or marketplace fails unless that application implements the required fee mechanism. See Transfer Fee and Application Compatibility.

U.7.7 Report a Name

1. Open the name's history page and select Report Username. A report action is also available in the name catalogue.
2. Enter a description of the issue. Add supporting links or transaction references in Evidence if relevant.
3. Select Submit report to open a prepared email to the moderation team.
4. Review and send the email through your email application.

Submitting a report requests team review; it does not immediately hide the name or initiate a DAO vote. See Moderation and Display Filtering for the distinction between hosted UI filtering and DAO-governed blacklisting.

U.7.8 Configure Website and Email Settings

DNS integration is in the final stages of implementation. The following describes the agreed workflow once the feature is available; it is not an instruction to use controls already present in every release.

From the owned name's management area, the owner will be able to configure a website target and an email forwarding destination. The website target can be an IP address (A record) or a domain/hostname (CNAME), with only one website target active at a time. Email forwarding sends messages to an existing email address and does not create a mailbox.

Creating, updating, or removing settings requires a wallet-confirmed on-chain transaction and gas. The DNS synchronization service then applies the change through the external provider, so the blockchain confirmation and the visible DNS update do not necessarily occur at the same time.

After an ownership transfer, previous DNS and email settings are cleared and the new owner can configure their own. See DNS and Email Integration for synchronization, moderation, and service details.

U.8 Wallet Compatibility

U.8.1 Test Results and Community Reports

The records below preserve the wallet tests and community experience previously collected in the Whitepaper. They are historical observations, not new tests performed for this guide. A successful connection does not by itself confirm staking, withdrawal, or transfer support.

Reports with unspecified operations remain general-use reports. Different networks, platforms, and connection methods are kept separate.

Wallet	Connection / Platform	Network	Operations tested or reported	Known issues / Scope
Brave Wallet	Brave browser; Windows 11	Mainnet	General use reported successful; individual operations not recorded.	No direct issue reported with Brave Wallet on this setup
MetaMask app	Mobile app; Android	Mainnet	General use reported successful; individual operations not recorded.	Larger screens reported easier to use; no specific transaction failure recorded.
MetaMask	Apple devices; Apple devices	Mainnet	Platform-dependent behavior reported; individual operations not recorded.	Differences reported without a specific reproducible issue.
MetaMask	Edge browser; Windows	Mainnet	Sending previously failed after a wallet update.	At one MetaMask update, sending was blocked due to a cross-chain support check, even for DMD-to-DMD transactions; GitHub issue was opened
MetaMask	Firefox extension; Various OS	Mainnet	Partial compatibility reported.	UI sometimes requires account switching in MetaMask to refresh properly; MetaMask becomes unresponsive in less than a day, suspected memory leaks; requires Firefox restart
MetaMask	Chrome extension; Not specified	Mainnet	General use reported successful; exchange transfers not tested.	No issues reported; exchange transfers not tested.
MetaMask	Built-in wallet browser; iPhone; exact iOS version not recorded	Mainnet	General use reported successful; individual operations not recorded.	No issues reported
MetaMask	Chrome browser connected to MetaMask; iPhone	Mainnet	General use reported mostly successful; individual operations not recorded.	Small visual bugs
MetaMask	Brave and Edge browsers; Windows 11; sometimes Windows 10 and Linux	Mainnet	General use reported mostly successful; occasional deposit/withdrawal failures.	One or two failed deposit/withdraw attempts, possibly caused by the external platform rather than MetaMask/DMD
MetaMask plugin	Supremium portable browser; Windows 7	Mainnet	General use reported successful; individual operations not recorded.	No issues reported with this setup
SafePal	WalletConnect; Chrome; macOS	Mainnet	Validator workflows reported successful; individual operations not recorded.	No issues with validator experience
Rabby Wallet	Chrome extension; Windows 11 laptop	Mainnet	Network setup, staking, and unstaking succeeded.	No issues reported
Coinbase Wallet	Chrome extension; Windows 11 laptop	Mainnet	Network setup, staking, and unstaking succeeded.	No issues
OKX Wallet	Chrome extension; Windows 11 laptop	Mainnet	Network setup succeeded; staking could not be confirmed.	At the staking stage, the transaction could not be confirmed because the confirmation button was grayed out and not clickable
Enkrypt Wallet	Chrome extension; Windows 11 laptop	Mainnet	Network setup, staking, and unstaking succeeded.	No issues
TokenPocket	Chrome extension; Windows 11 laptop	Mainnet	Network setup succeeded; staking failed.	Diamond UI returned a transaction receipt error with invalid params / expected 0x-prefixed hex string
Zerion	Chrome extension; Windows 11 laptop	Testnet (tDMD)	Network setup, staking, and unstaking succeeded; sending tDMD failed.	Sending tDMD back to MetaMask failed due to invalid params / unknown chainId field
OneKey	Chrome extension; Windows 11 laptop	Testnet (tDMD)	Network setup and receiving tDMD succeeded; staking failed.	Staking failed with JSON RPC execution exception
Trust Wallet	Chrome extension; Windows 11 laptop	Testnet (tDMD)	Network setup, receiving, staking, unstaking, and sending tDMD succeeded.	No issues reported

U.8.2 Maintaining the Test Record

For each new test, record wallet and browser versions, operating system, network, connection method, and results for the operations actually attempted: connection, receiving, sending, staking, unstaking, and claiming an ordered withdrawal. Mark operations that were not attempted as Not tested. Preserve the error message and context for a failed operation so a later retest can distinguish resolved issues from ongoing limitations.