
← Work archiveCASE / 001
Economic / NFT Trading Platform
POPPOP NFT Platform
Solo-built NFT trading/exchange platform on the Beatoz chain using batch-oriented smart contracts and a batch execution server.
- Role
- Solo builder · architecture, implementation, and operational tooling
- Period
- 2024.03 - 2025.08
- Context
- Beatoz Labs
01 / Executive summary
Solo-built NFT trading/exchange platform on the Beatoz chain using batch-oriented smart contracts and a batch execution server.
DECISION / ASystem challenge
What made the system difficult.
Required a reliable batch execution flow across multiple transaction types while keeping on-chain operations safe and observable.
DECISION / BEngineering response
How boundaries and flows answered it.
Implemented batch functions in Solidity (trade/cancel/refund/settlement/gift/barcode) and a gRPC-based batch server with queueing, retries, and operational safeguards.
02 / System path
The path of responsibility through the system.
TM-Contract-V2
Smart Contract Layer
Responsibilities
- — Batch trade functions
- — Fee tracking
- — Rollback support
TM-BatchServer
Backend API Layer
Responsibilities
- — gRPC batch endpoints
- — Queue-based execution
- — Retry & monitoring
03 / Technology field
01Solidity02Node.js03gRPC04Hardhat05OpenZeppelin06Bull07Redis
04 / Detailed record
Overview
- Solo-built NFT trading/exchange platform on the Beatoz chain.
- Designed around on-chain batch execution + an off-chain batch execution server.
Key Components
TM-Contract-V2 (Smart Contracts)
- Transaction-type state transitions (purchase/exchange/refund/settlement/gift, etc.)
- Batch execution inputs/validation flows
- Fee tracking structure (
FeeTracker) + event-based auditability - Operational recovery paths (rollback flows)
TM-BatchServer (Batch Execution Server)
- gRPC-based batch API
- Queue/polling based execution per transaction type
- Gas/nonce awareness + failure classification + retry policy, with logs for observability
05 / Factual evidence

ACTUAL PROJECT ASSET / NOT GENERATED