Afristore

Decentralized marketplace for African art, built on Stellar + Soroban smart contracts.

Architecture

Freighter Wallet ──► Next.js Frontend ──► Soroban Contract (Stellar)
                          │                       │
                          ▼                       ▼
                     Pinata IPFS             On-chain Storage
                  (Images + Metadata)     (Listings + Ownership)

Monorepo Structure

afristore/git checkout -b feature/admin-dashboard-ui
├── contracts/
│   └── soroban-marketplace/          # Rust Soroban smart contract
│       ├── src/
│       │   ├── lib.rs                # Contract entry point
│       │   ├── types.rs              # Listing, Status, Error types
│       │   ├── storage.rs            # Storage key helpers
│       │   └── contract.rs           # Contract implementation
│       ├── Cargo.toml
│       └── Makefile
├── frontend/
│   └── afristore-app/                # Next.js 14 App Router frontend
│       ├── src/
│       │   ├── app/                  # App Router pages
│       │   ├── components/           # Reusable UI components
│       │   ├── lib/                  # Stellar SDK, IPFS, contract helpers
│       │   └── hooks/                # React hooks
│       ├── public/
│       ├── package.json
│       └── next.config.js
└── scripts/
    └── deploy/                       # Deployment scripts
        ├── deploy_contract.sh
        └── fund_account.sh

Quick Start

1. Deploy the Soroban contract (Testnet)

cd scripts/deploy
./fund_account.sh          # fund a new keypair on testnet
./deploy_contract.sh       # build + deploy the contract

2. Start the frontend

cd frontend/afristore-app
cp .env.example .env.local   # fill in contract ID + Pinata keys
npm install
npm run dev

Open http://localhost:3000

Current Testnet Deployment (2026-04-09)

Use these live addresses to avoid redeploying contracts during testing.

Item	Address / ID	Notes
Deployer / Admin Wallet	`GBFUNHEQOVN35LFEKP7SZXFYJPMJ3WLXLX4PQZGBK737NTLRHOKVES3F`	Testnet account used for the deployments below
Marketplace (active)	`CD3FSSR667WES5YVVUZZ22LFRQ2RB5NGJGGQEGSPP4OXWLJJV5EFHIIR`	Frontend is configured to this contract
Launchpad Factory	`CCLHHJXSDPXGBXA672FHHYROFH7AEL2TV5CTD3OESI2DYVAKYHNLG2ZU`	Initialised and configured with collection WASM hashes
Normal 1155 Collection (via launchpad)	`CAQBWUKVLOR5W43QBQDFJAHSE2LUGCALRDCM7EVEO36FTWOP5P2O36ML`	Deployed through `deploy_normal_1155`
Marketplace (older)	`CBKY6WYCJI5U7RAD6Z32DQK45BVP7PMKF7G7ZF7HTJDY46M5NNAS24GP`	Older deployment, not used by frontend

Uploaded Collection WASM Hashes (used by launchpad)

Collection WASM	Hash
Normal ERC-721 (`collection_nft_erc721.wasm`)	`6fe018f8d43f85a4b3c7b4430552a134240e87b2a2835b6c001b3ac8f6019013`
Normal ERC-1155 (`collection_nft_erc1155.wasm`)	`b5d6299353e7e9b2e17a355eb61e9af0b87fa515b91a65bbe58828ffde921de0`
LazyMint ERC-721 (`lazy_mint_erc721.wasm`)	`59f803c1be39c679603c4875bed7f6c88c89c8abbf65375922b3f4e6199cb3f9`
LazyMint ERC-1155 (`lazy_mint_erc1155.wasm`)	`1cf995455b89bda48002efdc5f0df90ac8f7e78a1f52fea3b3d6fc7d9e53344f`

WASM Hash Verification

Canonical on-chain proof that these four hashes were set on launchpad:

Launchpad set_wasm_hashes tx: https://stellar.expert/explorer/testnet/tx/da048a970f9390dda5ac5da45090cb9e563310527c2220e4bbbb98bdb477b12b

You can also verify current launchpad configuration directly from CLI:

LAUNCHPAD=CCLHHJXSDPXGBXA672FHHYROFH7AEL2TV5CTD3OESI2DYVAKYHNLG2ZU
SOURCE="<your testnet secret key or identity>"

stellar contract invoke --id $LAUNCHPAD \
  --source-account "$SOURCE" \
  --rpc-url https://soroban-testnet.stellar.org \
  --network-passphrase "Test SDF Network ; September 2015" \
  --send no -- all_collections

Note: these hashes may map to WASM code uploaded in an earlier session/account. The launchpad set_wasm_hashes transaction above is the source of truth for what is active.

Related Testnet Transactions

Launchpad initialize: https://stellar.expert/explorer/testnet/tx/8e68976a8bbdbf0a2787f0ebee1c84c6015751b97d2c8d80eec76a2bf4954960
Launchpad set_wasm_hashes: https://stellar.expert/explorer/testnet/tx/da048a970f9390dda5ac5da45090cb9e563310527c2220e4bbbb98bdb477b12b
Launchpad deploy_normal_1155: https://stellar.expert/explorer/testnet/tx/d65cac3675f9efbe407b31f46b90ffb5d73c34f79409ae5dac8eaeed95ab6004

Environment Variables

Variable	Description
`NEXT_PUBLIC_CONTRACT_ID`	Deployed Soroban contract address
`NEXT_PUBLIC_STELLAR_NETWORK`	`testnet` or `mainnet`
`NEXT_PUBLIC_STELLAR_RPC_URL`	Soroban RPC endpoint
`NEXT_PUBLIC_STELLAR_HORIZON_URL`	Horizon API endpoint
`PINATA_JWT`	Pinata JWT for server-side uploads (private)
`NEXT_PUBLIC_PINATA_GATEWAY`	Pinata IPFS gateway URL

Which env vars are for Vercel frontend

Only the frontend app in frontend/afristore-app needs these in Vercel:

Public vars (NEXT_PUBLIC_*):
- NEXT_PUBLIC_CONTRACT_ID
- NEXT_PUBLIC_STELLAR_NETWORK
- NEXT_PUBLIC_STELLAR_RPC_URL
- NEXT_PUBLIC_STELLAR_HORIZON_URL
- NEXT_PUBLIC_STELLAR_NETWORK_PASSPHRASE
- NEXT_PUBLIC_PINATA_GATEWAY
- NEXT_PUBLIC_INDEXER_URL (if using indexer endpoints)
Private server vars:
- PINATA_JWT

The indexer and deploy scripts use their own env files and do not need to be set in Vercel for frontend preview deployments.

Tech Stack

Layer	Technology
Frontend	Next.js 14 (App Router)
Blockchain	Stellar / Soroban
Smart Contracts	Rust (soroban-sdk)
Wallet	Freighter
Storage	IPFS via Pinata
Blockchain SDK	@stellar/stellar-sdk

Future Improvements

PostgreSQL event indexer for fast queries + search
On-chain royalties (EIP-2981 equivalent for Soroban)
Secondary resale market with royalty split
Search + category filtering via indexed metadata
Auction / bidding contract
Analytics dashboard
Mobile wallet support (LOBSTR, xBull)

Future Plan (V2)

1) Split into dedicated repositories

To scale development and deployment, this monorepo will be split into focused repos:

afristore-frontend
- Next.js app, wallet UX, listing/discovery pages, creator dashboard
afristore-backend
- Indexer, API, search, analytics, notifications, admin services
afristore-contracts
- Soroban marketplace, auction, royalty, and protocol-level smart contracts

2) Marketplace evolution

Move from “create NFT in marketplace” to “list existing NFT for sale”
Enable clean primary and secondary sales flow
Preserve original_creator + royalty rules across all resales
Keep protocol fee and payout splitting fully on-chain

3) Launchpad creation

The launchpad will support creator-first primary drops:

Collection/project setup for artists and brands
Configurable drop mechanics (fixed price, timed drop, allowlist)
Primary mint + instant listing pipeline
Launch metrics dashboard (mints, volume, conversion)
Shared royalty and treasury configuration with marketplace

4) Supporting improvements

PostgreSQL event indexer for fast queries and search
Auction / bidding contracts and offer workflows

Deploy Workflow

1 — Deploy Launchpad factory and collection WASMs

cd scripts/deploy
./fund_account.sh                  # create + fund a testnet keypair
./deploy_contract.sh               # deploy marketplace contract

# Upload collection WASMs and deploy launchpad (see contracts/launchpad/README.md)
HASH_N721=$(stellar contract upload --wasm target/.../normal_721.wasm --network testnet --source deployer)
HASH_N1155=$(stellar contract upload --wasm target/.../normal_1155.wasm --network testnet --source deployer)
HASH_L721=$(stellar contract upload  --wasm target/.../lazy_721.wasm   --network testnet --source deployer)
HASH_L1155=$(stellar contract upload --wasm target/.../lazy_1155.wasm  --network testnet --source deployer)

LAUNCHPAD=$(stellar contract deploy --wasm target/.../launchpad.wasm --network testnet --source deployer)

stellar contract invoke --id $LAUNCHPAD --network testnet --source deployer \
  --fn initialize -- --admin $ADMIN_ADDRESS \
  --platform_fee_receiver $ADMIN_ADDRESS --platform_fee_bps 0

stellar contract invoke --id $LAUNCHPAD --network testnet --source deployer \
  --fn set_wasm_hashes -- \
  --wasm_normal_721 $HASH_N721 --wasm_normal_1155 $HASH_N1155 \
  --wasm_lazy_721 $HASH_L721   --wasm_lazy_1155 $HASH_L1155

2 — Create a collection (user flow)

stellar contract invoke --id $LAUNCHPAD --network testnet --source creator \
  --fn deploy_normal_721 -- \
  --creator $CREATOR_ADDRESS --name "My Collection" --symbol "MYC" \
  --max_supply 10000 --royalty_bps 500 --royalty_receiver $CREATOR_ADDRESS \
  --salt $(openssl rand -hex 32)
# Returns: collection contract address — indexed automatically by the indexer

3 — Marketplace deployment

# Start the indexer (picks up deploy + marketplace events)
cd indexer
cp .env.example .env
# Set MARKETPLACE_CONTRACT_ID, LAUNCHPAD_CONTRACT_ID, DATABASE_URL
npm install && npm run build && npm start

Admin Dashboard

The admin dashboard (/admin) provides platform operators with:

Feature	Description
Fee management	View and update platform fee BPS and receiver address
Collection registry	Browse all deployed collections with creator and kind
Listing oversight	View all active, sold, and cancelled listings
Event log	Full on-chain event timeline per listing
Creator profiles	Collections and activity per creator address

Access the dashboard at http://localhost:3000/admin — wallet must match the admin address set during launchpad initialisation.

Name		Name	Last commit message	Last commit date
Latest commit History 254 Commits
.github		.github
contracts		contracts
frontend		frontend
indexer		indexer
scripts/deploy		scripts/deploy
.codex		.codex
.gitignore		.gitignore
Cargo.toml		Cargo.toml
PAUSE_IMPLEMENTATION_GUIDE.md		PAUSE_IMPLEMENTATION_GUIDE.md
README.md		README.md
package-lock.json		package-lock.json

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Repository files navigation

Afristore

Architecture

Monorepo Structure

Quick Start

1. Deploy the Soroban contract (Testnet)

2. Start the frontend

Current Testnet Deployment (2026-04-09)

Uploaded Collection WASM Hashes (used by launchpad)

WASM Hash Verification

Related Testnet Transactions

Environment Variables

Which env vars are for Vercel frontend

Tech Stack

Future Improvements

Future Plan (V2)

1) Split into dedicated repositories

2) Marketplace evolution

3) Launchpad creation

4) Supporting improvements

Deploy Workflow

1 — Deploy Launchpad factory and collection WASMs

2 — Create a collection (user flow)

3 — Marketplace deployment

Admin Dashboard

About

Uh oh!

Releases

Packages

Uh oh!

Uh oh!

Contributors

Uh oh!

Languages

Folders and files

Latest commit

History

Repository files navigation

Afristore

Architecture

Monorepo Structure

Quick Start

1. Deploy the Soroban contract (Testnet)

2. Start the frontend

Current Testnet Deployment (2026-04-09)

Uploaded Collection WASM Hashes (used by launchpad)

WASM Hash Verification

Related Testnet Transactions

Environment Variables

Which env vars are for Vercel frontend

Tech Stack

Future Improvements

Future Plan (V2)

1) Split into dedicated repositories

2) Marketplace evolution

3) Launchpad creation

4) Supporting improvements

Deploy Workflow

1 — Deploy Launchpad factory and collection WASMs

2 — Create a collection (user flow)

3 — Marketplace deployment

Admin Dashboard

About

Resources

Uh oh!

Stars

Watchers

Forks

Releases

Packages 0

Uh oh!

Uh oh!

Contributors

Uh oh!

Languages

Packages