Skip to content
WildanNiamStart a conversation

Navigate

Software systems, documentary proof, and the decisions behind the build.

Back to work
Full-Stack Product Builder2026-06-08 to present

Quorum

Making collaborative event settlement inspectable on Stellar testnet.

State
prototype
Context
hackathon / collaboration
Validation
live-deployment / testnet / tests / transaction
Quorum discovery page showing event search, four seeded events, remaining seats, categories, and a visible Stellar testnet status.
Quorum's deployed discovery surface makes event access, remaining capacity, format, and the testnet proof layer visible before checkout. Seeded event content demonstrates the product flow; it is not presented as market traction.

Outcome

Six signed Quorum flows recorded by the repository were independently confirmed successful on Stellar testnet on 2026-07-11.

Testnet network execution for the recorded flows; not evidence of mainnet, production event usage, revenue, partnership, or an independent contract audit.

Quorum live testnet evidence recordPaid-event publish transaction

Problem

The product question.

Collaborative events often collect ticket revenue through one organizer and reconcile speaker, venue, community, and partner shares through spreadsheets, screenshots, and follow-up transfers. Access, check-in, contract accounting, evidence, withdrawal, and off-ramp state can easily drift across trust boundaries.

Intended users

  • Web3 community organizers creating paid or free events and gated resources.
  • Attendees purchasing or claiming a wallet-bound pass and checking in.
  • Collaborators who need a visible share, balance, withdrawal proof, and optional cash-out continuation.

Contribution

Full-Stack Product Builder

Wildan owned the product and full-stack build. ArgaAAL made substantive infrastructure and evidence contributions across database migration, indexing, proof surfaces, ledger work, live-flow evidence, and deployment fixes.

  • Product specification and interaction design.
  • Next.js application, server routes, sessions, and Postgres persistence.
  • Soroban contracts, wallet transaction boundaries, and deployment tooling.
  • Evidence indexing, settlement correction, MoneyGram-compatible continuation, and QA.

Decisions

Choices that shaped the build.

01

Split product data from on-chain invariants

Postgres makes event content and product iteration practical, while the contracts enforce the values that control payment, access, balances, withdrawal, and check-in.

The system gains a clear source-of-truth map but must reconcile indexed chain events and application records carefully.

02

Make wallet intent narrow and inspectable

Prepared and signed XDR are checked for signer, network, source, contract, function, and arguments before submission and persistence.

Local or mocked proof cannot silently impersonate a live transaction, while users retain explicit Freighter approval.

03

Separate contract withdrawal from cash-out

An on-chain event debit and a later wallet-to-MoneyGram transfer are two money movements. Treating them as one created a double-accounting and proof risk.

Cash-out now references eligible settled withdrawals, keeps the two hashes distinct, prevents over-allocation, and reuses failed or cancelled records for safe retry.

System flow

From intent to visible evidence.

  1. 01

    An organizer signs a Freighter challenge and creates an event with capacity, access mode, resources, and a 100 percent split.

  2. 02

    Publishing prepares, validates, signs, submits, and confirms a QuorumCore create-event transaction.

  3. 03

    An attendee pays exact testnet USDC or claims a free pass.

  4. 04

    QuorumCore enforces capacity and uniqueness, credits balances, and invokes QuorumPassNFT.

  5. 05

    The non-transferable pass unlocks resources and can be checked in by an authorized organizer.

  6. 06

    An indexer stores contract events and cursor state for proof, pass, event, and collaborator views.

  7. 07

    A collaborator withdraws the credited contract balance to a wallet.

  8. 08

    Only that settled withdrawal can continue into a separate MoneyGram-compatible SEP-24 cash-out record.

Reflection

What remains, and what comes next.

Current boundary

  • Quorum is a Stellar testnet hackathon build with no independent smart-contract or security audit.
  • The public evidence route showed a hosted database connection failure on 2026-07-11.
  • MoneyGram-compatible sandbox initiation is not a partnership or a completed cash-out and pickup.

Next improvements

  • Repair and re-verify the hosted evidence path, then preserve a stable deployed replay.
  • Complete and document the remaining manual MoneyGram transfer and pickup flow.
  • Harden contracts, QR/check-in behavior, refund and cancellation policy, wallet coverage, and observability.
  • Gather authentic organizer, collaborator, and real-event validation.

Technology

Next.js 16 / React 19 / TypeScript / Node.js / PostgreSQL / Supabase / Zod / Vercel / Stellar SDK / Freighter / Rust / Soroban / Stellar RPC / Horizon / SEP-1 / SEP-10 / SEP-24 / Playwright

Next projectPayGate