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
  • Story collection 1
  • NFT Artwork Collector
  • Story collection2
  • NFT Artist
  • Story collection3
  • NFT Investor / Trader
  • Story collection4
  • NFT Lottery User
  • Story collection5
  • Concert Goer
  • Story collection6
  • Event Manager
  • Story collection7
  • Mobile/Tablet User
  • Story collection8
  • Desktop User

Was this helpful?

Export as PDF
  1. Supporting & Reference Docs
  2. TradeHands Explorer

User stories

General explanation of the feature from the end user perspective.

Story collection 1

NFT Artwork Collector

As an NFT Artwork Collector, I'd like to know that there is a place where I can view and show off my collected artwork that is independent of whatever site or application I used to purchase my collected artworks. Perhaps, I purchased the artwork from a small marketplace specializing in a very niche category of artwork, and perhaps this site doesn't provide the best embedding for sharing to social media, or perhaps it doesn't publicly expose a URL for non-logged-in users to view artworks, making sharing difficult. In this circumstance, an independent explorer providing an objective view of NFT objects and activity on chain would be of use. Thus an NFT Artwork Collector might use TradeHands Explorer for the following reasons:

As an NFT Artwork Collector...

Story #
I want...
So that...

1.1

to show off collected art

  1. I can show a pride of ownership

  2. I can encourage secondary market resale

1.2

to inspect details of art

the authenticity of the artwork can be verified

1.3

to see the artworks

I can compare and see what I have vs. what I need

1.4

to verify the authenticity

I can confirm what kind of artwork I possess like rarest, souvenir value, etc.,

1.5

to view "traits"

I can distinguish the difference among the artworks.

1.6

to have semantic interpretation

any user can understand the concepts, value of any artwork.

1.7

to link with social media eg: Facebook

I can easily share my collections with my social followers.

Story collection2

NFT Artist

As an NFT Artist, I may be using specialized tools to create my NFTs and selling them on specialized or niche marketplaces with a focused audience that provide a particular "view" of the artworks. To get a sense of how my NFTs look to the "rest of the world," or to get access to activity information and statistics perhaps not tracked by the marketplace I am selling on, an independent explorer providing an objective view of NFT objects and activity on chain could be useful. Thus an NFT Artist might use TradeHands Explorer for the following reasons,

As an NFT Artist...

Story #
I want...
So that..

1.1

to see all my own artwork as a gallery

I can display all my artwork as a collection.

1.2

to see owner of his art

I can have the details of who has purchase my arts.

1.3

to see the transaction

I can monitor the selling price of my artworks.

1.4

to verify correct formatting of NFTs

It can be assured that the NFT is aligned with standards.

Story collection3

NFT Investor / Trader

As an NFT investor / trader, I may be using a different application than TradeHands Explorer for actual trading or market activity, but still benefit from an Explorer as it allows an objective, neutral view of objects and activity on chain.

As an NFT Investor / Trader...

Story #
I want...
So that...

1.1

to see recent transaction

I can have a check on which artworks are being sold.

1.2

to see the high value of transaction

I can monitor which artwork is popular so that I can invest in future.

1.3

to see popular artists/artwork

I can learn in which artwork I can invest.

1.4

to view my own collection in a portfolio

I can asses the value of my collection

1.5

to see active buyers

I can see the artworks that are being purchased and able to invest in future.

1.6

to look at the popular categories using filters

I can make an investment based on the profits/needs.

1.7

to see data on the price/bids/asks over time

I can trade artworks

Story collection4

NFT Lottery User

The NFT Lottery system has a separate application that allows users to inspect lotteries, purchase tickets, and enjoy winnings. However, the lottery application is meant to be deployed by lottery hosts. Thus, there may be a multiplicity of deployments, each showing lotteries relevant only to the deployment owners. It may not provide a broad view of all lottery activity on chain, or perhaps a complete view of the individual lotteries in detail. An independent explorer allows users to have an objective view into the activities they are participating in. A lottery participant may use TradeHands Explorer for the following reasons,

As an NFT Lottery User...

Story #
I want...
So that...

1.1

to identify the winners

I will be aware of who has won lottery.

1.2

alternate ways to see/verify the lottery

I can have a check on the winning numbers.

1.3

to see who else is participating

I can check the number of participants.

1.4

to check on the end date and conditions

I am fully aware of the ticket details.

1.5

to see the tickets that has souvenir value with sematic interpretation

I can save the ticket/sell for a profitable price.

Story collection5

Concert Goer

The Concert Goer will have a separate application for purchasing and using NFT-powered concert tickets. However, such an application will likely have a streamlined, simplified user interface that obscures the details of the underlying NFT objects and blockchain activity. More technically-oriented users may gain comfort and confidence in the event tickets and their relevant apps usage by inspecting the objects on chain using an objective, independent explorer. An explorer can allow users to have a broader view of NFT-powered event ticket activity, perhaps revealing events of interest to them that are not highlighted in the ticket app they are using. Thus a Concert Goer might use TradeHands Explorer for the following reasons:

As a Concert Goer...

Story #
I want...
So that...

1.1

to quickly find the ticket for the event

It can be blocked to purchase.

1.2

to verify the ticket authenticity

the Ticket issuer and event information can be viewed.

1.3

to see all the issuer details

so that the website, information, details about other events can be checked.

1.4

to see the tickets that have Souvenir value

I can save the ticket/sell for a profitable price.

Story collection6

Event Manager

The Event Manager may be using expensive licensed event-management software that provides a full-featured but controlled view of the NFT-powered events they are managing. For verification and validation, an Event Manager may benefit from an independent explorer that provides an objective view of the objects and activity occurring on chain, including their own event ticket NFTs. Thus, the Event Manager might use TradeHands Explore for the following reasons:

As an Event Manager...

Story #
I want...
So that...

1.1

to see all tickets created per events

I can be aware of how much tickets are being sold.

1.2

to see all the events details in wide view

I have all information about the events in a detailed view.

1.3

to see the events that are created by me using a sort and filter

I can find the events hosted by me at ease.

1.4

to see the sold ticket details

I can monitor the number of people attending the event.

1.5

to see the unsold ticket details

I can find other alternate ways to sell the tickets.

1.6

to check on the secondary market activity

I can monitor various platforms through which tickets are being sold and also find the selling/buying cost.

Story collection7

Mobile/Tablet User

The Mobile/Tablet user can be any of the above persona who expects to have a pleasant experience while browsing the TradeHands Explorer.

As a Mobile/Tablet User...

Story#
I want...
As a/an/any...

1.1

to have a simple page layout

  1. NFT Collector/investor/Trader to easily navigate for gathering details of any artwork.

  2. NFT Artist to showcase my artwork, value for buyers.

  3. Lottery user to check the winners and souvenir value of my ticket at ease.

  4. Concert goer to purchase tickets.

  5. Event Manager to check the activity of any events like time, tickets sold, etc.,

1.2

to have an easy share control (no right click)

Persona, will be easily able to share details of artworks/tickets over social media as required.

Story collection8

Desktop User

The Desktop User can be any of the above Personas who expect the TradeHands Explorer to showcase the artwork in detail. Desktop user has the following advantages,

  1. Much larger screen for viewing content

  2. Full access to website content

  3. Much easier to navigate content

  4. Often have the stability and greater bandwidth

As a Desktop User...

Story#
I want...
As a/an/any..

1.1

a detailed representation of artworks which should contain owner, asset value, highest transaction

  1. NFT Collector to showcase my artwork collection that helps buyers to invest

  2. Desktop User, I can monitor my own artwork collection, owner of my artwork, transaction details in a single large screen layout.

  3. NFT Investor/Trader, I can showcase my portfolio in a single page layout.

1.2

to have easy navigation control

Persona can check relevant details of any artworks/tickets for selling/buying/monitoring.

PreviousUser PersonasNextAPP-FS01 Detailed View

Last updated 2 years ago

Was this helpful?