Fluxpayai

The problem

Creator–brand deals run on trust and manual ops: brands worry about paying for low-quality work; creators worry about getting paid at all. Escrow helps, but someone still has to manually judge "is this deliverable good?" and click release. That human bottleneck doesn't scale, and on-chain payments traditionally require creators and brands to hold native gas tokens on every chain.

The solution

FluxPay turns the entire deal lifecycle into an autonomous on-chain workflow:

1. Brand posts a deal → defines milestones, budget, and content requirements.

2. Brand grants a spending permission once → via useGrantMilestonePermission, an ERC-7715 spending permission is signed on their MetaMask Smart Account and stored server-side (POST /api/permissions).

3. Creators apply → browse open deals, submit a cover note; brands review on-chain reputation and select.

4. Creator submits a deliverable → a single submit call auto-kicks the settlement loop.

5. Venice AI verifies & scores → the score is mapped to a payout amount (quality-weighted payment).

6. The agent releases USDC autonomously → it redeems the brand's permission via ERC-7710 and pays the creator — 1Shot relays on mainnets so gas is paid in USDC; Base Sepolia uses a direct-redeem path. Reputation scores update on both sides.

Why it's novel

• AI is in the money path, not just an advisor. Venice's score literally determines how much USDC is released — quality-weighted, autonomous settlement.

• Permission-based payments, not pre-funded escrow vaults. The brand signs once; the agent draws against that permission per milestone using MetaMask's delegation toolkit.

• Gasless for everyone. All gas is paid in USDC via 1Shot's paymaster path — creators and brands never touch a native token.

• Truly multi-chain. A single source-of-truth chain config spans 8 mainnets (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Linea, Scroll) plus Base Sepolia for testing — with per-chain USDC addresses and correct decimals (USDC is 18 decimals on BNB Chain, 6 elsewhere)

Core autonomous settlement loop (the heart of the project)

• ✅ Venice AI verification service (veniceService.ts, verificationService.ts) — scores deliverables against the brief; POST /api/verify.

• ✅ Score-to-payout settlement (settlementService.ts) — POST /api/settle runs verify → score → release with no human approval. Milestone submit auto-kicks the loop.

• ✅ 1Shot relayer path (relayerService.ts, oneshot.ts) — mainnet payouts with gas paid in USDC; USDC addresses sourced from 1Shot's getCapabilities.

• ✅ ERC-7715/7710 permission flow (permissionService.ts, redeemService.ts, redelegationService.ts) — brand grants a spending permission on the frontend; agent redeems it server-side to release funds. Direct-redeem path for Base Sepolia (1Shot doesn't support testnets).

Multi-chain infrastructure

• ✅ Single source-of-truth chain config for 8 mainnets + Base Sepolia (chains.ts) — per-chain USDC addresses, correct decimals (18 on BNB Chain), and NETWORK_MODE / ACTIVE_CHAIN_ID resolution.

• ✅ On-chain balance reads (wagmi useBalance + USDC balanceOf) with a GoldRush/Alchemy proxy for the full token list.

Full marketplace product

• ✅ Auth — Web3Auth (MetaMask Embedded Wallets) with server-side JWT verification (JWKS/PEM).

• ✅ Jobs → milestones lifecycle — post, quote, apply, select, fund, submit, approve, dispute (job.ts, deal.ts).

• ✅ Multi-creator applications with an approvals inbox (/api/applications/incoming).

• ✅ Unified reputation system (0–100 for creators and brands, everyone starts at +5) wired everywhere — replaced all mock data with real scores (reputation.ts).

• ✅ One-time $2 testnet USDC faucet on signup, idempotent per address (faucetService.ts).

• ✅ Social OAuth for creator profiles (socialOAuthService.ts).

• ✅ Neon Postgres persistence — JSONB repository pattern (no migrations for new fields), graceful in-memory fallback.

Engineering quality

• ✅ Strict frontend↔backend contract through a single typed api-client.ts; canonical API.md endpoint list; consistent { error: { code, message } } shape.

• ✅ Migrated all creator & organization pages to TanStack Query hooks; reconciled on-chain vs. ledger balance sources.

• ✅ Deployed to production (Vercel + Render) with full .env.example parity.

Sponsor integration scorecard

none