LogoLogo
PAO DocsCommunity DocsInfrastructure DocsPeerplays.com
  • Developer Documentation
  • API Reference
    • Peerplays Core API
      • Popular API Calls
      • Account History
      • Asset API
      • Block API
      • Crypto API
      • Database API
      • Network Broadcast API
      • Network Nodes API
      • Orders API
    • Wallet API
      • Account Calls
      • Asset Calls
      • Blockchain Inspection
      • General Calls
      • Governance
      • Privacy Mode
      • Trading Calls
      • Transaction Builder
      • Wallet Calls
    • Bookie API
      • General Calls
      • Listeners
      • Tournaments
  • Peerplays API Libraries
    • Python Peerplays
      • Installation
      • Creating an Account
      • Creating a Peerplays Wallet
      • NFT API
      • Marketplace API
      • Role Based Permissions API
  • Development Guides
    • Creating User Issued Assets
    • Introduction to Permissions
    • NFT Minting
    • Calculating Costs
  • The Cookbook
    • NFTs for Staking Creator Tokens
  • Tools and Integrations
    • PeerID
      • 1.0.0
        • Infrastructure
          • Deployment on a Linux Serve
          • Deployment to AWS ECS
            • Building the Docker Images
            • Storing Secrets in Amazon Parameter Store to use in ECS
            • Creating the Task Definition
            • Creating the Cluster
            • Creating the Service
        • Development
          • How does PeerID work without storing the keys ?
          • Authentication with PeerID
          • Brain Storming
          • Software Requirements
      • Authentication with PeerID
      • Requirements Specification
    • Random Number Generator
      • RNG Technical Summary
      • RNG API
  • Supporting & Reference Docs
    • Peerplays Development FAQs
    • Sidechain Operator Node (SON) Development
      • Generic Sidechain Docs
        • Quick joining GLADIATOR
        • Changes to Peerplaysjs-lib
        • Requirements Specification
        • Low Level Designs
          • bitcoin-deposit-handling-lld
          • bitcoin-operations-draft
          • bitcoin-sidechain-handler-lld
          • bitcoin-sidechain-multisig-bitcoin-wallet-and-bitcoin-addresses-pw
          • bitcoin-withdrawal-handling-lld
          • btc-address-scripting-mechanism
          • comparison-between-scenarios-for-handling-deposits-and-withdrawals
          • exchange-rate-list
          • generic-sidechain-deposit-hld
          • generic-sidechain-high-level-design
          • generic-sidechain-listener-hld
          • generic-sidechain-withdrawal-hld
          • refund-btc-mechanism
          • son-configuration
          • son-consensus-communication-and-transaction-signing-on-chain-lld
          • son-de-register-proposals-lld
          • son-objects-and-operators
          • son-rewards-lld
          • son-voting-lld
          • son-wallet-list_sons-lld
          • creation of a multi-sig bitcoin address lld
          • claiming initial son vesting lld
          • changeover and SON maintenance scenarios lld
          • user-sidechain-addresses-mapping
          • wallet-commands-for-son
        • Functional Specs
          • SON Configuration
          • SON rewards
          • SON Voting and Consensus
          • SONs switchover scenarios
          • SON Status Operations & Monitoring
          • Proposals
          • SON Smart Contracts
      • Bitcoin Sidechain Docs
        • Functional Specs
          • btc-refunds
          • voting-and-consensus
          • son-switchover
          • son-rewards
          • son-proposals
          • son-configuration
          • heartbeat-monitoring
          • BTC Transaction Processing & Signing
          • Bitcoin Withdrawal Handling
          • Bitcoin Deposit Handling
          • SON Multisig Bitcoin Wallet
      • Hive Sidechain Docs
        • Functional Specs
          • HIVE Deposit Handling
          • HIVE Withdrawal Handling
    • Peerplays DEX Development
      • Peerplays NEX
        • Functional Specifications
          • NEX-FS01 Dashboard Page
            • NEX-FS12 ETH-SONs Deposit/Withdraw Functionality
          • NEX-FS02 Login and Account Creation
          • NEX-FS03 Menus and Nav
          • NEX-FS04 Notifications
          • NEX-FS05a Market Page (alpha)
          • NEX-FS05 Market Page
          • NEX-FS06 Profile Page
          • NEX-FS07 Wallet Functions
          • NEX-FS08 App Settings
          • NEX-FS09 Blockchain Page
          • NEX-FS10 GPOS Page
          • NEX-FS11 WhaleVault Integration
      • Requirements Specification
      • Functional Specs
        • Asset Info Page and Asset Lists
        • Dashboard
        • Exchange Page
        • Login and Account Creation
        • User Account Page
        • Voting Page
    • SPK Network
      • Functional Specs
        • Claimdrop Snapshot Functional Specification
        • Initial Claimdrop Functional Specification
    • NFT Development
      • NFT Store
        • NFT Store User Stories
        • NFT Store UI HLD
        • NFT Store Requirements Specification
        • Functional Specifications
          • APP-FS01 App Header
          • APP-FS02 App Body
          • APP-FS03 App Footer
          • APP-FS04 App Navigation
          • APP-FS05 Wallet Functions
          • APP-FS06 App Home Page
          • APP-FS07 Account Page
          • APP-FS08 Browse View
        • App Page List
        • Requirement Traceability Matrix
    • Operation IDs List
    • Sidechain Flow Diagram (HIVE coin)
    • Sidechain Flow Diagram (Bitcoin)
    • Sidechain Flow Diagram (Ethereum coin)
    • TradeHands Explorer
      • User Personas
      • User stories
      • APP-FS01 Detailed View
      • Draft: APP-FS02 Front Page
      • APP-FS03 Collection Details Page
    • Grafana
      • Grafana Installation
      • Install Grafana Behind reverse proxy
      • Loki Installation
      • Promtail agent Installation
      • Grafana Explorer
    • NEX Deployment & Configuration
      • NEX Deployment
      • NEX - Blockchain API configuration
      • Deploying NEX in a HA scenario
    • API Node
      • MarketCap API
    • TOTO Application
      • FS-Subscription Plan
      • FS-Achievements
  • Development Workflow Docs
    • Development Workflow
  • Other Documentation
    • Peerplays Home
    • Community Docs
    • Infrastructure Docs
    • Site Reliability Engineering
Powered by GitBook
On this page
  • 1. Purpose
  • 2. Scope
  • 2.1. Components
  • 3. Document Conventions
  • 4. Process Overview
  • 4.1. User Navigation
  • 5. Context
  • 6. Design Wireframes
  • 7. Requirements
  • 7.1. My Asset List layout (Wallet Dashboard)
  • 7.2. My Asset List layout (Exchange Dashboard)
  • 7.3. Asset List layout (Exchange Page)
  • 7.4. The Asset Information Page
  • 7.4. The system
  • 8. Glossary
  • 9. Related documents

Was this helpful?

Export as PDF
  1. Supporting & Reference Docs
  2. Peerplays DEX Development
  3. Functional Specs

Asset Info Page and Asset Lists

The Peerplays Decentralized Exchange (DEX) platform functional requirements specification for the asset info related functions.

1. Purpose

The purpose of this document is to outline functional specifications for the Peerplays Decentralized Exchange (DEX) relating to asset information functions from the user's perspective.

2. Scope

The "my assets" list, asset info page, and asset explorer are part of the wallet functionality built into the DEX. This functional spec covers listing a user's owned assets in various locations throughout the DEX app.

Peerplays assets in the context of this functional spec are any on-chain asset. This includes native Peerplays assets like the PPY coin, Peerplays NFTs, and CATs. This also includes assets that have originated off-chain that have been transferred onto the Peerplays chain through the services of Peerplays SONs. These external (sidechain) assets include Peerplays versions of BTC, HIVE, or ETH and even Peerplays versions of NFTs living on the Ethereum chain. The external assets are backed by their counterparts, locked in a Peerplays controlled account on their native chains.

2.1. Components

Specific components and features covered include:

  • the My Assets list layouts in the following contexts:

    • wallet dashboard

    • exchange dashboard

    • exchange page

  • the Asset Info page layout

    • Asset Info display

    • Asset Explorer (advanced search and list)

3. Document Conventions

For the purpose of traceability, the following code(s) will be used in this functional specification:

Code

Meaning

AL-#

Asset Listing Requirement

The keyword shall indicates a requirement statement.

4. Process Overview

The processes which will be described here:

  • user navigation among asset related lists and pages

4.1. User Navigation

Assumptions: The user has an account and owns some assets.

FIG 1. User navigation among asset lists / pages

The arrows in FIG 1 above correspond to the steps in the process flow that follows.

User navigation:

  1. User logs in and initially lands on the wallet dashboard page. The user clicks on an asset in their "My Assets" list to view its details.

  2. User lands on the Asset Info page for the selected asset. The user reviews the available exchange markets for this asset and clicks a trading pair to view the exchange page.

  3. User lands in the exchange page for the selected trading pair. After some trades, the user decides to look up an asset. User navigates to the Asset Info Page.

  4. User searches and finds an asset. User clicks to view the asset details.

5. Context

Various pages in the DEX require a list of assets the user owns. Asset lists throughout the DEX can add to the user friendliness of the app by providing quick access to detailed asset information and links to the most important DEX features.

6. Design Wireframes

FIG 2. Asset List on Dashboard Design Wireframe

FIG 3. Asset Links on Exchange Page Trading Pairs

FIG 4. Asset Information Page Design Wireframe

7. Requirements

Requirements specific to the items outlined in this functional specification are as follows.

7.1. My Asset List layout (Wallet Dashboard)

the My Assets List layout:

  • AL-1 shall be available to authenticated users on the wallet dashboard.

  • AL-2 shall allow users to search the list of their assets and display the results.

  • AL-3 shall allow users to sort the assets by the following (ascending and descending):

    • favorite

    • available balance

    • total balance

    • last transaction (time)

    • alphabetically

  • AL-4 shall, for each asset the user owns, display the following information:

    • the asset symbol

    • the asset name

    • the user's available balance

    • the user's total balance

    • an actions dropdown button

  • AL-5 shall allow the user to take the following actions within the actions options:

    • send asset

    • view the asset's info page

    • view the asset's vesting page

    • view the asset's exchange page (default trading pair)

  • AL-6 shall allow the user to mark the asset as a favorite.

7.2. My Asset List layout (Exchange Dashboard)

the My Assets List layout:

  • AL-7 shall be available to authenticated users on the exchange dashboard.

  • AL-8 shall allow users to search the list of their assets and display the results.

  • AL-9 shall allow users to sort the assets by the following (ascending and descending):

    • favorite

    • available balance

    • total balance

    • last transaction (time)

    • alphabetically

  • AL-10 shall, for each asset the user owns, display the following information:

    • the asset symbol

    • the asset name

    • the user's available balance

    • the user's total balance

    • an actions dropdown button

  • AL-11 shall allow the user to take the following actions within the actions options:

    • view the asset's available trading pairs in the exchange

    • view the asset's info page

    • view the asset's vesting page

    • send asset

  • AL-12 shall allow the user to mark the asset as a favorite.

7.3. Asset List layout (Exchange Page)

the market selector assets list:

  • AL-13 shall be available to users on the exchange page (market selector).

  • AL-14 shall allow users to search the list of available and display the results.

  • AL-15 shall allow users to sort the assets by the following (ascending and descending):

    • favorite

    • available balance

    • 24h trade volume

    • alphabetically

  • AL-16 shall, for each available market, display the following information:

    • the asset symbols in the market trade pair

    • the user's available balance (if user is authenticated)

    • the 24h trade volume

    • links to the asset info page for each asset

  • AL-17 shall allow the user to select a trading pair to view its market on the exchange page.

  • AL-18 shall allow the user to mark the asset as a favorite.

7.4. The Asset Information Page

Asset Info Display

the Asset Info Page:

  • AL-19 shall be available for each Peerplays Asset (except for NFTs which will be covered by the NFT Express-Cart project).

  • AL-20 shall display the following information for the selected asset:

    • asset name

    • asset symbol

    • asset description (See note below)

    • asset url (See note below)

    • asset community social links

  • may display informative tags. (See note below)

    • examples:

    • Core token, CAT, or Sidechain token

    • allows PowerUp

    • provides rewards

    • allows trading, sending

    • etc...

  • AL-21 shall display a buy button for quick link to the exchange.

  • AL-22 shall display rewards info.

  • AL-23 shall display supply info:

    • circulating supply

    • max supply

    • inflation rate

NOTE on Asset Info Display: Some information should be provided by PBSA, CAT creator, or Advisor / SMEC.

Asset Explorer (advanced search and list)

the Search functions on the Asset Info Page:

  • AL-24 shall allow searching for assets by the following methods:

    • search by:

    • asset name

    • asset symbol

    • informative tags (if available)

  • AL-25 shall display the information page for the selected asset.

Asset Exchange Info

the Asset Info Page exchange info section:

  • AL-26 shall display the following information:

    • all exchange trading pairs for the given asset:

      • the current price

      • the 24h volume

      • a button to show more details about the pair

    • given the selected trading pair:

      • the price chart

      • the current price

      • 24h change

      • 24h low & high

      • 24h volume

      • yesterday's low & high

      • yesterday's open & close

      • yesterday's change

      • yesterday's volume

      • 7 day low & high

      • 30 day low & high

      • 90 day low & high

      • 1 year low & high

      • All time high with date and price

      • All time low with date and price

  • AL-27 shall allow the user to select a trading pair to go to its exchange page.

Asset Holders Info

the Asset Info Page holders info section:

  • AL-28 shall display the following information:

    • a ranked list of all users which own the selected asset, including:

      • their username

      • their asset balance

      • their asset powerup balance (if relevant to the asset)

  • AL-29 shall allow the user to sort the list by the following:

    • username

    • balance

    • powerup balance

  • AL-30 shall allow the user to click a username in the list to visit the user's profile page.

Asset Community Info

  • AL-31 shall display the following information about the selected asset:

    • community discussion

    • CAT governance (if applicable)

    • CAT information (if applicable)

    • links to community resources

NOTE on Asset Community Info: Some information should be provided by PBSA, CAT creator, Advisor / SMEC, or community members.

Asset Recent Transactions Info

  • AL-32 shall display the following information about the selected asset:

    • a list of recent transactions which used the asset, including:

      • block number

      • date and time

      • transaction data

7.4. The system

  • AL-33 if an error occurs at any point, the system shall display meaningful error information to the user and provide them with actions they can take to attempt to resolve the error.

8. Glossary

CAT: Community Asset Token - A token created by a community for the purpose of forming a community which takes advantage of the Peerplays ecosystem to manage governance, payments, and other transactions. The community can enact its own role based security to manage its tokens and community parameters. CATs are native to the Peerplays blockchain.

SMEC: Subject Matter Expert Committee - A group of delegates which act as the experts for a given topic. They are given the power of decision-making within the area of their expertise.

9. Related documents

PreviousFunctional SpecsNextDashboard

Last updated 3 years ago

Was this helpful?

Peerplays DEX Requirements Specification