General

Let's chat all things AI and Agentic Economy on Arc


Agentic Economy

We 💙 AI Agents at Arc.  If you're building with Autonomous Agents, tell us about it here in a post.

: A technical deep-dive into how we run an 8-agent autonomous AI swarm 24/7 on Arc Testnet for Puls—covering continuous web research, onchain USDC bonding, the concurrency bottleneck we hit with Circle Gas Station, and how we resolve agent-vs-agent duels.

: Developers orchestrating multi-agent systems on Arc, builders managing concurrent transactions through Circle Developer-Controlled Wallets, and teams designing economic accountability for AI agents.

, or run the MCP server with Claude / Cursor (

1. The Reality of Running a Live Swarm 24/7 on Arc

Most Web3 agent demos run single-turn scripts. In Puls, we operate eight autonomous AI agents running continuously on a Debian VPS managed by PM2:

 (high-level macro sentiment & breaking news) and 

: Specialized forecasters competing on specific market sectors (macro, tech, crypto, policy).

: Ingests real-world news using Gemini 2.5 Flash with live Google Search grounding.

: Generates a structured mathematical forecast (probability distribution + reasoning thesis).

: Unlocks predictive alpha from peer agents via x402 nanopayments in USDC.

: Submits trades and posts capital bonds directly on Arc Testnet (Chain ID 

2. The Concurrency Trap: Nonce Collisions on Circle Gas Station

When you scale from a single bot to an 8-agent swarm trading across 100+ active prediction markets, parallel execution immediately breaks naive RPC pipelines

Each agent holds its own Circle Developer-Controlled Wallet. When a major news event breaks, multiple agents attempt to publish trades or unlock x402 signals simultaneously. Firing concurrent transaction requests through Circle Gas Station caused:

: Transactions submitted in the same millisecond collided before the previous transaction was mined.

: Firing raw bursts overwhelmed the backend wallet signing endpoints

The Solution: Atomic FIFO Nonce Serialization Queue

We engineered an in-memory queue inside our Express backend (

) that isolates transaction streams per agent wallet address:// Conceptual FIFO Queue Pattern implemented in puls_backend

  private queues: Map<string, Promise<any>> = new Map();

  async enqueue<T>(agentWallet: string, task: () => Promise<T>): Promise<T> {

    const currentQueue = this.queues.get(agentWallet) || Promise.resolve();

      .catch(() => {}) // Prevent previous error from blocking the queue

        const result = await task();

    this.queues.set(agentWallet, nextTask);

Because Arc’s Malachite consensus delivers 

 (1-block inclusion without reorgs), each transaction settles in ~400–800ms. The queue drains almost instantaneously without creating UI lag or mempool stalls.

3. Skin in the Game: Agent Bonds & The Colosseum (AgentDuels)

AI predictions without economic consequences generate low-signal noise. In Puls, agents are required to put capital behind their convictions:

: When an agent publishes a high-conviction forecast thesis, it locks a testnet USDC bond into the protocol. If the market resolves in its favor, the bond is returned with a yield share. If wrong, the bond is slashed.

: When two agents take opposing sides on a binary market (e.g., Agent Alpha forecasts 80% YES vs Agent Beta forecasting 25% YES), the protocol matches them in an onchain duel. Both agents lock matching USDC stakes. Upon market resolution via our optimistic oracle layer, 100% of the purse settles automatically to the winning agent's wallet.

All duels, bond states, and agent PnL are publicly auditable in real time at 

4. Developer Integration: Querying Swarm Intelligence with @pulsmarket/sdk

External applications and AI agents can query the live swarm's consensus and inspect agent health using 

import { PulsClient } from '@pulsmarket/sdk';

  // 1. Query the AI Oracle: Crowd vs. Agent Swarm

  const targetMarket = 'fed-rate-cut-september';

  const consensus = await puls.oracle.consensus(targetMarket);

  console.log(`Market: ${targetMarket}`);

  console.log(`Crowd Odds: ${consensus.crowdYes}% YES`);

  console.log(`AI Swarm Consensus: ${consensus.aiYes}% YES (${consensus.agentCount} active agents)`);

  // 2. Fetch the active Agent Roster & bond stats

  const { agents } = await puls.agents.roster();

    console.log(`Agent [${agent.name}] | Win Rate: ${agent.winRate}% | Active Bonds: $${agent.activeBonds} USDC`);

5. Honest Limitations & What We Are Building Next

: Agent wallets are currently orchestrated through Circle Developer-Controlled Wallets on our VPS backend. While all trades and bonds settle onchain on Arc Testnet, the signing keys live in our managed infrastructure.

: We are working on migrating individual swarm agents to sovereign modular smart accounts, allowing third-party developers to sponsor and deploy their own independent agents into the Puls Colosseum.

https://www.npmjs.com/package/@pulsmarket/sdk

https://www.npmjs.com/package/@pulsmarket/mcp

How are other teams structuring nonce synchronization and gas sponsorship when running multiple concurrent agent wallets through Circle Developer-Controlled Wallets?

If you are building autonomous agents, what bonding and slashing ratios have you found most effective for aligning AI incentives onchain?

Under the Hood of Puls: Running an 8-Agent Autonomous Swarm on Arc Testnet (Nonce Queues, Circle Gas Station & Onchain Duels)

Home

Forum

Events

Content

Courses

Collections

People

Contributors

Albums

Groups

Chat

Channels

Not being used

Help

Join the global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make the economy work for everyone.

Arc House

What do you do professionally (be specific especially if you are self employed)

Join a global network of builders developing the Economic OS for the internet. We’re reimagining how value moves, creating the tools that make that economy work for everyone. 

Arc House | Build the economic OS for the internet with us

Copyright

Terms of Service

Privacy

Code of Conduct

Your Privacy Choices

It looks like there is no account associated with the email you provided. The event is for members only. Please complete the application to join our community first.

Thank you for your interest in joining us

Thanks for your interest in joining the event. However, your account is still pending. Once it's approved, you'll be able to register for the event. Please contact us via dev@arc.io if you need support.

Pending Approval

Login to the The Arc Community Hub community to connect with others, attend community events, and more!

Login or Sign Up for even more

To unlock all parts of the community complete your profile using verifiable and real information.

Hey, complete your profile

It looks like there is no account associated with the email you provided. Please complete the application to join our community.

Thank you for your interest in joining Arc House.

Thanks for your interest in joining Arc House. We will review your request shortly and email you once it's approved. Meanwhile, please feel free to contact us via dev@arc.io for any questions.

Accounts are unapproved when profile information cannot be verified or when activity patterns indicate spam, inorganic participation, or behavior that undermines trust in the program.

To strengthen your profile for future consideration, sign in with a verified LinkedIn account, use real and current profile information, and participate constructively in other community spaces.

Commercial customers should raise concerns through their support channel.

https://www.arc.network/community-guidelines