Built for
Game studios, app developers, affiliate operations teams and contractor or community reward platforms
← All productsLocal Mock · no live payout
INFRASTRUCTURE · PRODUCT BRIEF
JayBounty
Design non-custodial campaign vaults, webhooks and automated USDC rewards for game and app companies.
JayBounty is a B2B reward engine where a company fixes the campaign name, gross deposit and per-user payout, then uses explicit approval from its own wallet to prepare a non-custodial smart vault or bounded spending permission. The target flow authorizes a 500 USDC gross deposit, routes the 10%, 50 USDC platform fee first, and fixes the remaining 450 USDC as the reward pool. A verified company webhook can then release the policy-fixed 5 USDC for up to 90 rewards. The current implementation is a local Mock; no live vault, funded deposit, signed webhook, sweep transaction or JGas sponsorship is verified.
BaseUSDCSmart vaultERC-4337Signed webhookJGas adapter
SAMPLE UI · NO LIVE TRANSACTION
LOCAL REWARD ENGINE
10% FEEA safe payout policy for a 500 USDC gross deposit
GROSS CAMPAIGN DEPOSIT500.00 USDC50 FEE → 450 REWARD POOL
01Gross deposit · 500 USDC
02Platform fee · 50 USDC
03Reward pool · 450 USDC
04Per mission · 5 USDC × 90
POST /v1/rewardsMOCK 200Local Mock; only gross deposit, 10% upfront fee, replay guard and reward ledger are simulated.
B2B INFRASTRUCTURE · LOCAL MOCK
See what can be reviewed—and what stays locked—first.
The product flow and economics can be reviewed on this Mac. Real assets, wallet approval and onchain transfer are never executed.- EXECUTION MODE
- LOCAL MOCK ONLY
- CUSTODY BOUNDARY
- NO CUSTOMER ASSET CUSTODY
- LIVE ADAPTER
- LOCKED · NO BROADCAST
Intended outcome
Connect a company-approved gross deposit, 10% upfront fee, verified mission events and bounded USDC payouts through one auditable campaign policy
PRODUCT FLOW
Four steps users can understand
01 · Create campaign
Fix campaign name, 500 USDC gross deposit, 5 USDC per reward and payout conditions.
02 · Deposit and deduct
A 500 USDC gross approval deducts the 50 USDC fee upfront and fixes a 450 USDC reward pool.
03 · Mission webhook
The company server sends a completion event with signature, timestamp, event ID and campaign-bound user.
04 · Bounded payout
Only a 5 USDC reward passing verification, replay and balance policy can sweep to the recipient wallet.
INTERFACE TEMPLATE
Sample product interface
A code-native sample for reviewing the product structure without real keys, transactions or customer data.SAMPLE UI · NO LIVE TRANSACTION
LOCAL REWARD ENGINE
10% FEEA safe payout policy for a 500 USDC gross deposit
GROSS CAMPAIGN DEPOSIT500.00 USDC50 FEE → 450 REWARD POOL
01Gross deposit · 500 USDC
02Platform fee · 50 USDC
03Reward pool · 450 USDC
04Per mission · 5 USDC × 90
POST /v1/rewardsMOCK 200Local Mock; only gross deposit, 10% upfront fee, replay guard and reward ledger are simulated.
CAPABILITIES
Designed capabilities
Fixed campaign policy
Bind budget, per-user amount, allowed missions and expiry to an immutable version.
10% upfront fee
Route a 50 USDC fee first from the 500 USDC gross deposit and fix the spendable reward pool at 450.
Signed webhook inbox
Process only events with verified timestamp, signature, event ID and idempotency.
Bounded per-user payouts
The campaign policy, not webhook payload, supplies the allowed amount and destination binding.
Reward audit ledger
Record deposit intent, fee, event, payout decision and Mock receipt separately.
INTEGRATION SEQUENCE
Implementation sequence
- Configure policyFix tenant, campaign, mission, reward amount and limits on the server.
- Company funding approvalOutside Mock, the company wallet must review and approve the 500 gross amount, 50 upfront fee and remaining 450 pool.
- Verify webhookKeep secrets server-side and fail closed on signature, age, tenant and replay checks.
- Evaluate payout policyRecheck mission, user, campaign balance, count limits and stop state immediately before payout.
- Reward sweepSend the exact 5 USDC call and record a final receipt only when a live adapter is ready.
SERVER-SIDE PSEUDOCODE · NO CREDENTIALS
Server integration sketch
Secrets never enter the browser. Every external response is verified by the server before product state advances.
const campaign = await server.campaigns.createPolicy(input);
const funding = server.campaigns.previewFunding(campaign); // 500 gross → 50 fee + 450 pool
const event = await server.webhooks.verifyMock(signedFixture);
const decision = await server.rewards.evaluate({ campaign, event });
await server.rewards.recordMockSweep(decision); // NO BROADCASTSECURITY
Security and responsibility
No server-managed omnibus wallet
The design prioritizes a smart vault over automated payouts from a server-controlled customer-funds hot wallet.
Webhook is not payout authority
A webhook supplies only a mission event; server policy decides amount, token, destination and campaign.
Replay and duplicate protection
Tenant-bound event IDs, a timestamp window and idempotent ledger allow one payout only.
Budget and stop guards
No sweep occurs on insufficient balance, expiry, campaign stop or ambiguous state.
READINESS
Current limitations
Local Mock
Current deposit, webhook and payout receipts are asset-free fixtures.
Vault undeployed and unaudited
No live escrow contract, smart-account module or external security audit is complete.
Live signed webhook unverified
The current CEO flow uses a local secret fixture, not an integrated company server.
No funded sweep or JGas
Live USDC deposit, wallet approval, broadcast, mined receipt and gas sponsorship are unverified.
Market and operating boundary