Skip to content
EAPES product / case study

EAPES dApp

Modernizing a live Web3 Marketplace without disrupting its wallet-connected ecosystem.

EAPES STUDIO combined targeted dependency hardening with a measured Marketplace redesign, keeping wallet login, NFT visibility, language switching and transaction journeys inside the validation boundary.

app.eapes.com
EAPES DAPP / MULTIVERSXSecure.
Scale.

WALLET / MARKETPLACE / UTILITY

24 Listings per page4 Scale scenarios1 Direct fallback path
NetworkMultiversX
ProductWallet-connected dApp
Marketplace page24 listings
Scale checks3 / 50 / 200 / 800
Public statusLive

Repository evidence, automated pagination checks and public HTTP availability verified August 10, 2026.

The challenge

Improve security and scale without breaking active product flows.

  • Move security-sensitive dependencies to supported releases.
  • Reduce the cost of loading Marketplace history as sales accumulate.
  • Preserve wallet login, NFT visibility, languages, listings, offers and utility routes.
  • Keep Browse usable if the optimized listing endpoint becomes unavailable.
  • Avoid performance claims that were not backed by controlled analytics.
The solution

A targeted modernization with explicit fallbacks and scale checks.

  • Upgraded Next.js, Swiper and protobufjs through separately reviewed changes.
  • Derived a focused snapshot of active listings and recent Marketplace volume.
  • Paginated Browse at 24 listings and limited default metadata work to the visible page.
  • Retained the direct-chain path as a functional fallback.
  • Automated ordering, uniqueness and metadata checks at 3, 50, 200 and 800 listings.
Verified outcomes

What the work established.

  1. 01

    Security-sensitive dependency families moved to reviewed, supported releases.

  2. 02

    Browse now limits default metadata loading to the visible 24-listing page.

  3. 03

    Automated scale scenarios preserved listing order and uniqueness from 3 through 800 items.

  4. 04

    Functional validation covered wallet access, NFT visibility, languages and a test listing.

Evidence boundary. This was a targeted security and performance modernization—not a penetration test, formal smart-contract audit or complete file-by-file security review. No percentage speed improvement is claimed without controlled production analytics.

Your product / The next case study

Modernize a live Web3 product
without losing what already works.

Discuss your product