Deploy QSTN Survey Funding & Claim Contracts to Mainnet (Agoric SDK)

Governance CoreEval
1

Summary

QSTN proposes deploying its Agoric-powered multichain survey funding and reward-distribution contracts to mainnet.

Using Agoric Orchestration, businesses can fund survey reward pools on Osmosis and Neutron via Avalanche in a single transaction, and users can claim their rewards from all chains at once through a unified “Claim All” action.

The system integrates Keplr Wallet for business and user signing.

Application Overview

QSTN is a Web3 survey platform where businesses fund incentivized surveys and users earn token rewards. Our Agoric integration introduces:

1. Single-Transaction Multichain Funding

  • Business signs one Keplr transaction

  • Agoric routes funds to reward contracts deployed on Osmosis, Neutron, and Avalanche testnet.

  • No more manual chain-by-chain setup

  • Lower gas, faster onboarding

2. Single-Transaction Multichain Reward Claiming

  • User clicks Claim All

  • Agoric Orchestration aggregates rewards

  • Claims execute across Osmosis + Neutron contracts via Avalanche

  • Keplr signs once

  • Cleaner UX across Cosmos & EVM

3. Full Keplr Wallet Support

  • Both business and user flows use Keplr

  • Agoric smart wallet → orchestrated cross-chain actions

  • No additional extensions required

Delivered Testnet Implementation

Frontend (Testnet):

Demo Videos

GitHub Repositories

Testnet Reward Contracts

Testnet functionality is fully complete.

Deployment Checklist Status

QSTN has completed the Mainnet-2 checklist items with Agoric OpCo:

  • Linting + CI coverage: We ran linting with Agoric’s recommended configuration across the contract bundle and frontend. No blocking lint issues remain. Link: mainnet-checklist by JoE11-y · Pull Request #1 · QSTN-US/qstn-agoric-dapp-evm · GitHub

  • Pause mechanism: The contract-level pause mechanism is being finalized and will be committed by November 28. We will demonstrate the pause/resume flow during our December 4 meeting with Agoric OpCo. Link: mainnet-checklist by JoE11-y · Pull Request #1 · QSTN-US/qstn-agoric-dapp-evm · GitHub

  • Null-upgrade test: We executed a null-upgrade scenario to ensure durable state survives contract restart. Contract state persisted correctly and all subsequent calls executed normally.

  • Core-eval deployment test: We prepared and executed a full deployment test using the core-eval script intended for mainnet.This verified: bundle installation, contract deployment, offer handler behavior, claim and funding flows under real execution. Link: mainnet-checklist by JoE11-y · Pull Request #1 · QSTN-US/qstn-agoric-dapp-evm · GitHub

  • Public testnet deployment: We deployed fully to public testnets and demonstrated functionality across: Neutron Testnet, Osmosis Testnet, Avalanche Fuji Testnet. All funding and claiming actions execute as designed. Link: mainnet-checklist by JoE11-y · Pull Request #1 · QSTN-US/qstn-agoric-dapp-evm · GitHub

  • RPC rate limiting: During testnet deployment, we observed that the frontend was making more frequent RPC calls than necessary due to its default polling behavior. Although we did not hit rate limits during testing, we adjusted the frontend to reduce polling frequency and ensure it remains within the recommended ≤2 RPC requests per second guideline. Further fine-tuning will be done during the Emerynet phase using the @agoricagoricagoricagoricagoricagoricagoricagoric/rpc batching and chainStorageWatcher tools to guarantee compliance under higher usage.

  • Stress testing: We simulated repeated calls for: Business funding (Agoric → Avalanche → Osmosis/Neutron), User claiming @agoricagoricagoricagoricagoricagoricagoricagoricClaim All), Batch orchestration tasks.

    • Observations: No CPU/memory abnormalities on the Agoric side, No abnormal durable state growth, Cross-chain routing executed deterministically. We are prepared to repeat on Emerynet.

  • Security review: With guidance from Agoric OpCo during office hours, we reviewed all new transaction flows — business funding, orchestration routing (Agoric → Avalanche → Osmosis/Neutron), and the unified “Claim All” action. We validated input handling, offer shapes, and state transitions. No blocking issues were identified, and recommended adjustments (offer-shape tightening + parameter validation) were implemented before testnet deployment.

  • Resource usage observation: During stress testing, we monitored CPU, memory, and durable-state usage while running repeated funding, routing, and Claim All flows. No abnormal spikes, leaks, or storage growth were observed. We are prepared to repeat this observation during the Emerynet phase with validator support.

  • Full end-to-end demos: Business Funding: https://drive.google.com/file/d/1udk0BywYhBEJjzqH4RSxZkx303ACQB54/view User Claiming: https://drive.google.com/file/d/14R2MxY9Oa9DR30cLCJ8ETKo9851vU6uj/view

We are ready for Emerynet deployment.

Milestones for Emerynet → Mainnet

0 — Publish QSTN bundle to Emerynet

After OpCo confirmation.

1 — Publish core-eval proposal on Emerynet

2 — Validate full functionality on Emerynet

  • Funding (Keplr → Agoric → Osmosis/Neutron/Avalanche)

  • Reward aggregation and Claim All

  • Orchestration routing stability

3 — Joint monitoring with validators + OpCo

4 — Share progress updates in this thread

5 — Publish mainnet bundles

6 — Submit mainnet core-eval proposal

Only configuration (addresses) will change from testnet version.

Feedback

If you’re a validator, DAO, or ecosystem contributor interested in participating or supporting this beta, please reply in this t@realorrinnread or re@realorrinch@realorrinno@realorrinnt directly @realorrinn Discord (@realorrin) or Telegram.

Resources

Website: https://qstn.us
Twitter: https://twitter.com/qstnus
GitHub: https://github.com/QSTN-US

QSTN is excited to introduce a practical, user-friendly multichain orchestr@realorrinntion examp@realorrine on Agoric. We welcome validator feedback and are ready for the Emerynet phase.

— QSTN Team

2 Likes
2

Thank you, QSTN team for thoroughly completing and submitting all of the items in the Deployment Checklist!

The Agoric Systems team has been reviewing the submissions and we’ll be in touch about next steps!

Happy orchestrating :saluting_face: