The problem SuiPact solves

🚀 The Problem It Solves: The Freelance Trust & Payout Dilemma

Freelancing and remote digital commerce represent a $1.5 Trillion global market, yet the infrastructure supporting it is plagued by high fees, slow settlements, payment disputes, and a lack of transparent revenue sharing.

┌───────────────────────────────┐        ┌───────────────────────────────┐
│   Traditional Web2 Platforms  │   VS   │      Raw Web3 Solutions       │
│  (Upwork, Fiverr, Escrow.com) │        │   (Standard Crypto Wallets)   │
├───────────────────────────────┤        ├───────────────────────────────┤
│ ❌ 10% – 20% Predatory Fees   │        │ ❌ Volatile Tokens (BTC/ETH)  │
│ ❌ 5–14 Day Bank Payout Lags  │        │ ❌ Complex Seed Phrases       │
│ ❌ Manual, Opaque Team Splits │        │ ❌ Confusing Network Gas Fees │
│ ❌ Subjective Dispute Rulings │        │ ❌ High Risk of Bad Code Bugs │
└───────────────────────────────┘        └───────────────────────────────┘
                                 ▼
         ╔═══════════════════════════════════════════════════╗
         ║                     SUIPACT                       ║
         ║   Zero-Gas USDC Vaults + Atomic PTBs + Gemini AI  ║
         ╚═══════════════════════════════════════════════════╝

🎯 What Can People Use It For? (Real-World Use Cases)

🛡️ How It Makes Existing Tasks Easier, Safer, and Faster

1. 💰 100% Earnings Retention (Zero Commission vs. 20% Loss)

• Before: On a $3,000 freelance contract, platforms like Upwork pocket $300 to $600 in platform fees.
• With SuiPact: Freelancers and agencies keep 100% of the project budget. Zero platform cuts.

2. ⚡ Atomic Instant Splits via Sui Programmable Transaction Blocks (PTB)

• Before: Payouts take 5–14 business days to clear international banking rails, followed by manual accounting spreadsheets to distribute shares to subcontractors.
• With SuiPact: A single Sui PTB splits and routes USDC to up to 6 different team wallets simultaneously in under 400 milliseconds.

3. 🔒 Safe & Stable Value (USDC vs. Crypto Price Swings)

• Before: Paying in volatile native tokens (like ETH or SUI) meant a 15% market dip during development could wipe out the developer's profit margin.
• With SuiPact: All agreements are pegged to USDC ($1.00 USD), guaranteeing exact price predictability from start to finish.

4. 🤖 AI-Powered Clarity & Neutral Dispute Resolution (Gemini 2.0)

• Before: Scope creep leads to messy disputes where centralized support agents make arbitrary, one-sided refund decisions.
• With SuiPact:
  • AI Scope Generator: Automatically converts plain English prompts into quantifiable deliverables and mathematically balanced basis-point split schedules.
  • AI Deliverable Auditor: Verifies GitHub pull requests, commits, and Figma URLs against contract milestones.
  • AI Dispute Arbitrator: Analyzes deliverables and evidence impartially to propose fair, proportional compromise splits.

5. ⛽ $0.00 Gas & No Seed Phrases (Google zkLogin + Gas Relayer)

• Before: Normal clients give up when told to install browser extensions, buy gas tokens, and write down 24-word seed phrases.
• With SuiPact: Users log in with Google zkLogin and execute transactions with $0.00 gas fees, sponsored automatically by the backend gas relayer.

Challenges we ran into

🛠️ Challenges We Ran Into & How We Overcame Them

Building SuiPact across Sui Track 01 (Payments & Stablecoins) and Sui Track 02 (SUI x AI) pushed us to solve complex challenges across Move smart contract design, dual-signed gas sponsorship, zero-knowledge authentication, and multi-model AI orchestration.

1. 🧩 Sui Move Integer Division & Remainder Truncation in Atomic Splits

• The Hurdle: In Sui Move, Coin<T> balances are strictly typed u64 integers. When dividing a total project budget among multiple team members based on arbitrary basis points (e.g., 3 teammates with 3333 bps, 3333 bps, 3334 bps), integer division rounding errors risked leaving micro-dust amounts locked in the contract or aborting transaction execution due to unspent balances.
• How We Overcame It: We designed an exact remainder reconciliation loop in escrow.move. The loop calculates (total * r.bps) / 10000 for the first n - 1 recipients, and dynamically assigns total - distributed to the final recipient. This guarantees that 100.00% of the locked funds are disbursed with zero dust left behind. We verified this math with 9 automated Move unit tests.

2. ⛽ Dual-Signer Sponsored Gas Relayer Pipeline

• The Hurdle: To achieve a true $0.00 gas experience for Web2 clients, our backend relayer needed to co-sign transactions as the gas payer while the user signed the actual escrow execution. Serializing raw Programmable Transaction Blocks (PTBs), passing transaction kind bytes between client and server, and preventing signature mismatch errors during RPC execution was a major technical hurdle.
• How We Overcame It: We engineered a custom Node.js/Express relayer using @mysten/sui/transactions and Ed25519 keypairs. The frontend builds the PTB, sends the serialized bytes to /api/sponsor, the backend attaches gas payment coins and signs, and the combined dual-signature payload is submitted to Sui Testnet in one atomic RPC call.

3. 🤖 AI Hallucination & Strict Basis-Point Normalization (Gemini 2.0)

• The Hurdle: When converting natural language briefs into Move smart contract parameters using LLMs, models would occasionally produce JSON where recipient basis points summed to 9,990 bps or 10,050 bps instead of the mandatory 10,000 bps (100.00%), causing on-chain Move verification to reject the transaction.
• How We Overcame It: We implemented structured JSON schema enforcement with Gemini 2.0 Flash combined with a deterministic client-side sanitization layer. If the AI output deviates by even 1 basis point, our math normalizer re-proportions the distribution and forces the total to exactly 10,000 bps before locking funds on Sui.

4. ⚡ Next.js 15 SSR Hydration with zkLogin & Local State

• The Hurdle: Combining browser-based Google zkLogin session tokens, Web3 wallet connectors (@mysten/dapp-kit), and demo sandbox personas caused React hydration mismatch warnings during Next.js 15 server-side rendering.
• How We Overcame It: We refactored AuthContext to use a dedicated mounted hydration lifecycle with deterministic SHA-256 address derivation for zkLogin identities, ensuring the server and client render identical initial markup before attaching dynamic wallet state.

5. 🔄 Resolving Currency Discrepancies (SUI vs. USDC)

• The Hurdle: Early prototypes mixed native SUI token amounts with USD prices in the services marketplace, creating price confusion when transferring budgets into escrow creation forms.
• How We Overcame It: We standardized the platform exclusively on USDC ($1.00 USD) across all contracts, splits, balances, and marketplace gig cards. SUI is kept purely under the hood for network gas fees, giving freelancers and clients total price stability.