Skip to main content

​
Overview

ArtStar’s architecture is designed around a single goal: enabling a stable closed loop across the frontend, backend, and on-chain layers for issuance, subscription, compliance, synchronization, and subsequent circulation of art RWAs. This is neither a pure DApp nor a traditional Web2 platform. It is a hybrid architecture where the frontend owns the user experience, the backend provides aggregation and orchestration, and the blockchain provides settlement and trust.

​
Layered Architecture

Three-layer collaborative architecture

ArtStar can be abstracted into the following three core layers:

Frontend Interaction Layer

Organizes complex on-chain and backend states into user-understandable product flows * Present projects, assets, and market information * Handle wallet connection and signature-based login * Guide KYC processes and status * Initiate on-chain approvals and subscription transactions * Display user assets and activity data

Backend Service Layer

Responsible for “state aggregation” and “business orchestration,” complementing on-chain capabilities * Manage user profiles and sessions * Handle asynchronous KYC callbacks * Aggregate referrals, commissions, and points ledgers * Sync and index on-chain events * Provide query APIs for the frontend

On-Chain Execution Layer

Executes the platform’s most critical trust logic and asset settlement * Stablecoin approvals and debits * Minting fractionalized ownership tokens
  • Sale status and whitelist control * Liquidity pool initialization * Serve as the final source of truth for asset state

​
Data Flow

A typical subscription flow goes through the following full interaction chain:
1

Wallet connection

The user connects a wallet in the frontend
2

Authentication

The frontend initiates signature-based login and obtains a backend session
3

State aggregation

The frontend reads KYC status, whitelist status, and sale status
4

Approval

The user completes stablecoin approval (Approve)
5

Purchase execution

The user submits a subscription (Mint / Purchase) transaction
6

On-chain sync

After confirmation, events are asynchronously synced to the backend for parsing and recording
7

UI refresh

The frontend refreshes the UI based on on-chain results and backend aggregated data

​
Architecture Principles

The frontend may cache and display state, but the source of truth must come from smart contracts and the backend database, not local memory
The backend can enhance queries and validation, but it must not replace on-chain finality for asset behaviors
KYC, whitelisting, and network checks should be completed before the user submits a transaction to reduce failed transactions and wasted effort
Whether it is purchase records, KYC status, commission outcomes, or points changes, everything must be queryable, reconcilable, and explainable
At its core, ArtStar’s architecture balances three things: trustworthy on-chain execution, backend state aggregation, and low-friction frontend experience. Only with all three layers collaborating can art RWAs become a usable product.