mortal-kombat-nfts

byJhovany Beltran

I want too start selling mortal kombat nfts for million and billons of usd or eth or usdc

LandingMarketplaceMy ListingsSign UpCheckoutNew Listing
Landing

Comments (0)

No comments yet. Be the first!

System Requirements

System Requirements Document for Mortal Kombat NFTs

1. Introduction

Mortal Kombat NFTs is a first-party marketplace where a seller lists Mortal Kombat NFTs at premium prices denominated in millions and billions of USD, ETH, or USDC, and buyers browse and pay for those NFTs in any of the three accepted currencies. The product intent is a high-stakes, collectible drop surface: a loud, confident storefront for fighting-game digital collectibles sold at headline-scale prices, with a self-service seller workflow (create a listing, track its status and sales) and a self-service buyer workflow (browse listings, complete a purchase, receive the NFT).

The audience is two accepted human roles: the NFT Seller, who lists Mortal Kombat NFTs and tracks listings and sales toward a target revenue, and the NFT Buyer, who browses listings and pays in USD, ETH, or USDC to complete a purchase and receive the NFT. Both roles are self-service: they enroll without an invitation and verify identity on return to reach protected work.

This document is the System Requirements Document for the product; it specifies the product's features, workflows, pages, and constraints in full.

Page 1 of 22

2. System Overview

Mortal Kombat NFTs is delivered as a first-party web application with three provisioned services:

  • frontend — a React application UI that renders all seven accepted pages.
  • backend — a shared FastAPI process that owns application APIs and domain modules (identity, listings, checkout/payment records, sales status).
  • database — MariaDB holding application-owned persistent data: accounts, listings, prices and currencies, and purchase/sale records.

Application-owned identity is required: sellers must privately own and resume their listings and sales history, and a purchase commitment must remain bound to the correct buyer and the correct listing. Access is therefore split between anonymous entry surfaces (Landing, Marketplace, Sign Up, Login) and protected, role-restricted surfaces (Checkout for buyers; My Listings and New Listing for sellers).

Accepted behavior in scope: seller enrollment and return verification; seller listing creation with title, image, and price in USD, ETH, or USDC at million/billion scale; seller visibility into each listing's status and sales; anonymous browsing of Mortal Kombat NFT listings and their prices; buyer enrollment and return verification; buyer checkout paying in USD, ETH, or USDC; and the buyer receiving the NFT on a completed purchase.

Narrow exclusions: no invitation-based or provisioned onboarding (enrollment is self-service only); no account-management capabilities beyond first-use enrollment and returning verification; no currencies other than USD, ETH, and USDC; no NFT subject matter other than Mortal Kombat NFTs.

Page 2 of 22

Removed from scope

  • None — no concept from the authoritative requirement thread was removed or superseded.

2a. Product Interpretation and Delivery Boundary

The product is a first-party, application-owned storefront and transaction record for Mortal Kombat NFTs. The application owns identity (self-service Sign Up, returning Login), the listing catalog, the checkout and payment record, and the seller's view of listing status and sales. Payment is accepted in USD, ETH, or USDC as recorded by the application; the accepted requirement is that buyers can pay in these currencies and that prices are expressed in them at million/billion scale, and the application records the currency and amount for each listing and purchase.

Current delivery covers all seven accepted pages and both accepted personas. There is no future-horizon requirement in the authoritative thread; nothing is deferred. Anonymous visitors can reach Landing, Marketplace, Sign Up, and Login; protected work (Checkout, My Listings, New Listing) requires an established, verified identity with the appropriate role.

2c. Page Content and Component Coverage

Page 3 of 22

Landing

  • Information/state: Anonymous public entry. Explains Mortal Kombat NFT sales and the three accepted currencies (USD, ETH, USDC). Hero headline "Own the fight. Pay in ETH."; subline "Mortal Kombat NFTs with prices in USD, ETH or USDC."; call to action "See the drop".
  • Primary actions: "See the drop" → Marketplace. Supporting: links to Sign Up and Login.
  • Domain entities: none owned; presents product framing and currency set.
  • Component responsibilities: full-bleed charcoal hero field; oversized circular badge on the right carrying the drop name; stacked slab headline in the left columns; orange price ticker along the bottom edge; CTA pinned beneath the headline over a kraft block.
  • States: loading (static content, no data fetch required); empty/success not applicable; error not applicable; recovery — all navigation controls remain reachable at every viewport.
Page 4 of 22

Marketplace

  • Information/state: Anonymous browsing of Mortal Kombat NFT listings, each showing title, image, and price with its currency (USD, ETH, or USDC) at million/billion scale. Strict three-column grid that stacks at 375px.
  • Primary actions: Select a listing to proceed toward purchase (Checkout). Supporting: Sign Up / Login entry for purchase continuation.
  • Domain entities: Listing (title, image, price amount, currency, status).
  • Component responsibilities: listing cards with 2px black border and hard offset shadow; tabular mustard price numerals with an orange currency chip; grid container.
  • States: loading (listing fetch in progress); empty (no listings yet — message with seller entry point); success (grid of listings); error (fetch failure with retry); recovery (retry reloads the grid).
Page 5 of 22

Checkout

  • Information/state: Protected, buyer role. Shows the selected listing's title, image, and price with currency; buyer selects payment currency among USD, ETH, and USDC; shows purchase confirmation state.
  • Primary actions: Confirm payment in the selected currency. Supporting: return to Marketplace.
  • Domain entities: Listing, Purchase (buyer, listing, amount, currency, status).
  • Component responsibilities: order summary panel; currency selector (USD / ETH / USDC); confirm control; confirmation receipt showing the NFT is received.
  • States: loading (order summary fetch); empty (no listing selected — return to Marketplace); success (purchase recorded, NFT received, receipt shown); error (payment not completed — message and retry); recovery (retry preserves the selected listing and currency).

My Listings

  • Information/state: Protected, seller role. Shows each listing's status and its sales.
  • Primary actions: Open New Listing. Supporting: view a listing's status and sales detail.
  • Domain entities: Listing, Sale (listing, buyer, amount, currency, status).
  • Component responsibilities: listings table/list with status column and sales column; entry control to New Listing.
  • States: loading (listings fetch); empty (no listings yet — prompt to create one); success (list with statuses and sales); error (fetch failure with retry); recovery (retry reloads the list).
Page 6 of 22

New Listing

  • Information/state: Protected, seller role. Form with title, image, and price in USD, ETH, or USDC at million/billion scale.
  • Primary actions: Create listing. Supporting: cancel and return to My Listings.
  • Domain entities: Listing (title, image, price amount, currency, status).
  • Component responsibilities: title field; image field; price amount field accepting million/billion-scale values; currency selector (USD / ETH / USDC); submit control.
  • States: loading (submission in progress); empty (blank form); success (listing created, appears in My Listings and Marketplace); error (validation or submission failure with field-level message); recovery (form retains entered values for correction and resubmission).

Sign Up

  • Information/state: Anonymous, self-service enrollment for a new seller or buyer; no invitation required. Establishes the account and its role (seller or buyer).
  • Primary actions: Create account. Supporting: go to Login.
  • Domain entities: Account (identity, role).
  • Component responsibilities: enrollment form; role selection (seller or buyer); submit control.
  • States: loading (submission in progress); empty (blank form); success (account created, routed to the role's protected work); error (validation or duplicate identity with message); recovery (form retains values for correction).
Page 7 of 22

Login

  • Information/state: Anonymous, returning seller or buyer verification to reach protected work.
  • Primary actions: Verify identity and continue. Supporting: go to Sign Up.
  • Domain entities: Account.
  • Component responsibilities: verification form; submit control.
  • States: loading (verification in progress); empty (blank form); success (routed to the role's protected work); error (verification failure with message); recovery (retry without losing entered identity).
Page 8 of 22

3. Functional Requirements

FR-1 — Sell Mortal Kombat NFTs (explicit) As an NFT Seller I should list Mortal Kombat NFTs for sale so that I can sell them at premium prices.

  • Trigger/input: seller submits a listing with title, image, and price.
  • Observable result: the listing exists with status and appears in My Listings and on Marketplace.
  • Access: seller role, authenticated.
  • Failure/recovery: submission failure shows an error and retains entered values for resubmission.
  • Continuation: seller returns to My Listings to track status and sales.

FR-2 — Price in millions and billions of USD, ETH, or USDC (explicit) As an NFT Seller I should set each listing's price in USD, ETH, or USDC at million/billion scale so that prices reflect the accepted high-value range.

  • Trigger/input: price amount and currency selection (USD, ETH, or USDC) on New Listing.
  • Observable result: the listing stores and displays the amount with its currency at million/billion scale.
  • Access: seller role, authenticated.
  • Failure/recovery: invalid amount or missing currency shows a field-level error and retains values.
  • Continuation: the priced listing is visible in My Listings and Marketplace.
Page 9 of 22

FR-3 — Pay in USD, ETH, or USDC (explicit) As an NFT Buyer I should pay for an NFT in USD, ETH, or USDC so that I can complete a purchase in my chosen accepted currency.

  • Trigger/input: buyer selects a listing, chooses USD, ETH, or USDC on Checkout, and confirms.
  • Observable result: a purchase is recorded with the listing, buyer, amount, and currency; the buyer receives the NFT and sees a receipt.
  • Access: buyer role, authenticated.
  • Failure/recovery: an incomplete payment shows an error and allows retry with the selected listing and currency preserved.
  • Continuation: buyer returns to Marketplace to browse further listings.

FR-4 — Self-service enrollment (required_inference) As a new NFT Seller or NFT Buyer I should create an account without an invitation so that I can reach protected work.

  • Trigger/input: enrollment form on Sign Up with role selection (seller or buyer).
  • Observable result: an account is created and the user is routed to the role's protected work.
  • Access: anonymous.
  • Failure/recovery: validation or duplicate-identity error with message; form retains values.
  • Continuation: the user proceeds to New Listing (seller) or Marketplace/Checkout (buyer).
Page 10 of 22

FR-5 — Returning verification (required_inference) As a returning NFT Seller or NFT Buyer I should verify my identity on Login so that I can resume protected work.

  • Trigger/input: verification form on Login.
  • Observable result: the user is routed to the role's protected work (My Listings for sellers; Checkout/Marketplace for buyers).
  • Access: anonymous entry; protected destinations remain unavailable until verified.
  • Failure/recovery: verification failure shows a message and allows retry without losing entered identity.
  • Continuation: the user resumes the role's protected work.

FR-6 — Seller role for My Listings and New Listing (required_inference) As an NFT Seller I should hold the seller role so that I can use My Listings and New Listing.

  • Trigger/input: role established at Sign Up or verified at Login.
  • Observable result: seller-role users can reach My Listings and New Listing; non-sellers cannot.
  • Access: role-restricted.
  • Failure/recovery: a user without the seller role is denied access to these surfaces.
  • Continuation: the seller creates or tracks listings.
Page 11 of 22

FR-7 — Track listing status and sales (required_inference) As an NFT Seller I should see the status of each listing and its sales so that I can track progress toward my target revenue.

  • Trigger/input: opening My Listings.
  • Observable result: each listing shows its status and its sales.
  • Access: seller role, authenticated.
  • Failure/recovery: fetch failure shows an error with retry.
  • Continuation: seller opens New Listing or reviews another listing.

FR-8 — Browse listings and prices (required_inference) As an NFT Buyer I should browse Mortal Kombat NFT listings and their prices so that I can choose one to purchase.

  • Trigger/input: opening Marketplace.
  • Observable result: a grid of listings with title, image, and price with currency.
  • Access: anonymous.
  • Failure/recovery: fetch failure shows an error with retry.
  • Continuation: buyer selects a listing to proceed to Checkout.

FR-9 — Receive the NFT on purchase (required_inference) As an NFT Buyer I should receive the NFT after paying so that the purchase is complete.

  • Trigger/input: confirmed payment on Checkout.
  • Observable result: the purchase is recorded and the buyer sees a receipt confirming receipt of the NFT.
  • Access: buyer role, authenticated.
  • Failure/recovery: incomplete payment shows an error and allows retry.
  • Continuation: buyer returns to Marketplace.

4. User Personas

Page 12 of 22

NFT Seller

  • Product context: A seller of Mortal Kombat NFTs who wants to move collectibles at premium, headline-scale prices denominated in millions and billions of USD, ETH, or USDC.
  • Primary goal: List Mortal Kombat NFTs and track listings and sales toward a target revenue.
  • Distinct accepted responsibilities: Enrolls self-service (Sign Up) or verifies on return (Login); holds the seller role; creates listings on New Listing with title, image, and price in USD, ETH, or USDC; reviews each listing's status and sales on My Listings.
  • Relevant inputs/decisions: Title, image, price amount at million/billion scale, and currency choice (USD, ETH, or USDC).
  • Interactions with other participants: The seller's listings are what the NFT Buyer browses and purchases; each completed purchase appears as a sale in My Listings.
  • Observable success: A created listing appears in My Listings and Marketplace with its price and currency, and completed purchases are visible as sales against that listing.
Page 13 of 22

NFT Buyer

  • Product context: A buyer of Mortal Kombat NFTs who browses the drop and pays in USD, ETH, or USDC.
  • Primary goal: Browse Mortal Kombat NFT listings and complete a purchase in an accepted currency, receiving the NFT.
  • Distinct accepted responsibilities: Browses Marketplace anonymously; enrolls (Sign Up) or verifies on return (Login); holds the buyer role; selects a listing and a payment currency on Checkout; confirms payment; receives the NFT.
  • Relevant inputs/decisions: Which listing to purchase and which of USD, ETH, or USDC to pay in.
  • Interactions with other participants: Purchases the NFT Seller's listings; the purchase is recorded as a sale visible to the seller.
  • Observable success: A recorded purchase with a receipt confirming the NFT is received, and the ability to return to Marketplace.

5. Core User Flows

Page 14 of 22

Flow A — Seller enrolls and creates a listing

  1. New seller opens Landing (anonymous) and selects Sign Up.
  2. On Sign Up, the seller enters enrollment details and selects the seller role, then submits.
  3. The account is created; the seller is routed to seller-protected work.
  4. The seller opens New Listing and enters a title, an image, and a price amount at million/billion scale, then selects USD, ETH, or USDC.
  5. The seller submits; the listing is created with a status.
  6. Result: the listing appears in My Listings and on Marketplace with its price and currency.
  7. Failure/recovery: a validation or submission error shows a field-level message and retains entered values for correction and resubmission.
  8. Continuation: the seller returns to My Listings to track status and sales.

Flow B — Seller tracks listing status and sales

  1. Returning seller opens Login (anonymous) and verifies identity.
  2. On success, the seller is routed to My Listings.
  3. The seller reviews each listing's status and its sales.
  4. Result: the seller sees which listings have sold and their recorded sales.
  5. Failure/recovery: a fetch failure shows an error with retry; retry reloads the list.
  6. Continuation: the seller opens New Listing to add another listing.
Page 15 of 22

Flow C — Buyer browses and purchases

  1. Buyer opens Marketplace (anonymous) and browses Mortal Kombat NFT listings in the three-column grid, each showing title, image, and price with currency.
  2. The buyer selects a listing to purchase.
  3. Because Checkout is buyer-protected, the buyer enrolls on Sign Up (selecting the buyer role) or verifies on Login.
  4. On Checkout, the buyer reviews the listing's title, image, and price, selects USD, ETH, or USDC, and confirms payment.
  5. Result: the purchase is recorded and the buyer sees a receipt confirming the NFT is received.
  6. Failure/recovery: an incomplete payment shows an error; retry preserves the selected listing and currency.
  7. Continuation: the buyer returns to Marketplace to browse further listings.

Flow D — Buyer returns to complete a purchase

  1. Returning buyer opens Login and verifies identity.
  2. On success, the buyer is routed to buyer-protected work.
  3. The buyer opens Marketplace, selects a listing, and proceeds to Checkout.
  4. The buyer selects a currency and confirms; the purchase is recorded and the NFT is received.
  5. Failure/recovery: verification failure shows a message and allows retry without losing entered identity.
Page 16 of 22

6. Visuals Colors and Theme

Muse: Aaron Draplin. Headline register: bold field-note badges for a high-stakes fight card — loud, competitive, confident.

Mode: dark.

RoleHex
Background#141210
Surface#211D18
Text#F3EADA
Primary (hot action)#E8552B
Accent (prices, labels)#F2B01E
Muted#8C8375

Charcoal ground holds ~70% of each page; kraft surface blocks carry cards; orange is the hot action colour; mustard marks prices and labels.

Typography: Headings — Alfa Slab One, heavy slab display, all caps, tight tracking, hard edges. Body — Oswald, condensed gothic with wide caps labels. Modular scale 1.333: 64/48/36/24/18/16. Display clamp 48px mobile to 128px desktop.

Shape language: Chunky 2px borders, badge circles, stamp corners, hard rectangles. No soft radii above 4px.

Layout: Poster grid with ruled panels. A full-width badge headline sits over a kraft block. Listings sit in a strict three-column grid that stacks at 375px.

Page 17 of 22

Imagery: Thick-line vector emblems, halftone fighter silhouettes, gear-style stamps. No stock photos.

Motion: Snap-in stamp reveals on scroll; hover lifts a card by 2px with a hard shadow; no bounce.

Avoid: gradient blobs, glass panels, blue or indigo accents, rounded pill buttons, identical hover-lift card grids, thin hairline borders.

Readability rule: headlines, wordmarks, labels, numbers, and card text/controls stay entirely inside the viewport and their container at 375px, 768px, and 1280px, wrapping or scaling (e.g. clamp(...)) to fit; decoration may crop or bleed, readable text and controls may not.

7. Signature Design Concept

The public entry (Landing) is a full-bleed charcoal field (#141210) holding one oversized circular badge on the right — a thick-line vector emblem carrying the drop name, stamped with a 2px border and hard offset shadow. The left nine columns carry a stacked Alfa Slab One headline at up to 128px, all caps, tight tracking, sitting over a kraft block (#211D18) with the "See the drop" CTA pinned beneath it in orange (#E8552B). An orange price ticker runs along the bottom edge, its numerals in tabular mustard (#F2B01E) with orange currency chips for USD, ETH, and USDC. The badge overlaps the hero image corner as a stamp. Every readable element stays whole at 375px, 768px, and 1280px; the badge and ticker carry the bleed and crop gestures.

Page 18 of 22

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

  • Focal subject: the oversized circular badge stamp on the right, with the stacked slab headline on the left and the orange price ticker along the bottom edge.
  • Thesis: on load, the badge snaps into place like a stamp pressed onto the field (input: page load; transformation: snap-in stamp reveal with hard edges, no bounce; outcome: the badge, headline, and CTA settle into their composed positions and the ticker begins its continuous scroll).
  • Motion vocabulary: snap-in stamp reveals, 2px hover lift with hard shadow, no bounce, no easing overshoot.
  • Composed first frame: charcoal field, kraft block behind the headline, badge at right, CTA pinned beneath the headline, ticker at the bottom edge.
  • Reduced-motion state: all elements appear in their final positions with no snap or scroll animation; the ticker wraps into static rows so every price and currency chip is fully readable.
Page 19 of 22

9. Non-Functional Requirements

  • NFR-1 — Persistent application state (required_inference): accounts, listings, prices/currencies, and purchase/sale records persist in MariaDB so sellers can resume listings and buyers' purchases remain bound to the correct listing and buyer.
  • NFR-2 — Identity continuity (required_inference): protected surfaces (Checkout, My Listings, New Listing) are reachable only after Sign Up or Login; anonymous entry surfaces (Landing, Marketplace, Sign Up, Login) remain reachable without identity.
  • NFR-3 — Role restriction (required_inference): My Listings and New Listing are restricted to the seller role; Checkout is restricted to the buyer role.
  • NFR-4 — Currency integrity (explicit): only USD, ETH, and USDC are accepted as price and payment currencies; amounts support million/billion scale.
  • NFR-5 — Readability at all viewports (explicit, from creative direction): readable text and controls stay whole at 375px, 768px, and 1280px; decoration may crop or bleed.
  • NFR-6 — Reduced motion (explicit, from creative direction): with prefers-reduced-motion, a usable static arrangement is provided (ticker wraps or scrolls so each item is fully readable).
Page 20 of 22

10. Tech Stack

  • frontend: React application UI (all seven pages).
  • backend: shared FastAPI process for application APIs and domain modules (identity, listings, checkout/payment records, sales status).
  • database: MariaDB for application-owned persistent data.
  • Deployment: docker-compose with the three provisioned services (frontend, backend, database); no additional infrastructure is required for the accepted workflows.

11. Assumptions and Constraints

  • A-1 (required_inference): Identity is application-owned and self-service; no invitation or provisioning path exists.
  • A-2 (required_inference): A user holds one role (seller or buyer) established at Sign Up and verified at Login.
  • A-3 (explicit): All NFTs sold are Mortal Kombat NFTs.
  • A-4 (explicit): All prices are in millions and billions of USD, ETH, or USDC.
  • A-5 (required_inference): Payment is recorded by the application as a purchase with amount and currency; the accepted requirement is that buyers can pay in USD, ETH, or USDC and receive the NFT.
  • A-6 (explicit, from creative direction): Dark mode only; palette, fonts, and shape language as specified in Section 6.
Page 21 of 22

12. Glossary

  • Mortal Kombat NFT — a digital collectible in the Mortal Kombat franchise, the only subject matter sold on the platform.
  • Listing — a seller-created entry with title, image, price amount, currency, and status.
  • Sale — a recorded completed purchase of a listing by a buyer.
  • USD / ETH / USDC — the three accepted price and payment currencies.
  • Seller role — the role required to use My Listings and New Listing.
  • Buyer role — the role required to use Checkout.
  • Protected surface — a page reachable only after Sign Up or Login (Checkout, My Listings, New Listing).
  • Anonymous entry surface — a page reachable without identity (Landing, Marketplace, Sign Up, Login).
Page 22 of 22
Live
Landing design preview
Landing: See the drop
Marketplace: 1. Browse listings and prices
Marketplace: 2. Retry listings fetch
Marketplace: 3. Select listing to purchase
Sign Up: 1. Enroll with buyer role
Sign Up: 2. Correct enrollment errors
Login: 4. Verify returning identity
Login: 5. Retry verification
Checkout: Review order summary
Checkout: Select payment currency
Checkout: 1. Confirm payment
Checkout: 2. Retry preserved payment
Checkout: View NFT receipt
Marketplace: Browse further listings
Live
Landing design preview
Landing: See the drop
Marketplace: 1. Browse listings and prices
Marketplace: 2. Retry listings fetch
Marketplace: 3. Select listing to purchase
Sign Up: 1. Enroll with buyer role
Sign Up: 2. Correct enrollment errors
Login: 4. Verify returning identity
Login: 5. Retry verification
Checkout: Review order summary
Checkout: Select payment currency
Checkout: 1. Confirm payment
Checkout: 2. Retry preserved payment
Checkout: View NFT receipt
Marketplace: Browse further listings