For developers building on Circle products, post Q&A, best practices & SDK/API insights. Use Tags

Circle Products & Developer Toolings

Closing off the week, the ArcShop webinar with Elton — 

Unified Balance Kit for Crosschain USDC Flows

 — and with HJ — Building Chain Agnostic Apps with Circle Gateway and Circle Wallets —  landed on something most builders haven't fully internalized yet: 

the Circle stack is converging on a pattern where the asset is the primitive, and custody is a configuration.

That's the unlock. Gateway is an amazing primitive. AppKit is making integrating these primitives super straightforward 🫡

If you weren't able to attend - look for recordings of these events here: 

https://community.arc.network/home/content

Today, if you want to ship a stablecoin product, you pick your custody model up front and live with the consequences. Dev-controlled? Fast UX, but you carry the keys and the liability [use a managed KMS/HSM — don't handle raw secrets]. User-controlled? Real self-custody, but onboarding bleeds users at every signature prompt. Multisig / modular? Powerful, but you're stitching it together yourself.

 doesn't care which adapter you pass — the spend semantics are the same whether the underlying wallet is dev-controlled, user-controlled SCA, or a modular MSCA. Unified USD balance in, single-chain spend out. The custody layer becomes a parameter, not a fork in the architecture 🔥

Gateway today only accepts ECDSA on burn intents, which means every smart contract wallet — every SCA, every MSCA, every modular setup — is locked out of the unified balance flow at the signature layer. Dev-controlled EOAs work. Nothing else does.

This isn't a hypothetical concern — it's already an active thread in the ecosystem. The 

 on the x402-foundation repo has surfaced exactly this gap, and the community feedback has been pretty pointed:

 flagged that nearly every x402 facilitator on the market today rejects valid EIP-1271 signatures because they validate off-chain instead of doing a 

"the design space for UI/UX really opens up in the x402 space if facilitators work with EIP-1271."

 left a longer note on the same thread arguing that ERC-1271 support on the facilitator side is the unlock for a full agentic wallet hierarchy: a root treasury controlled by a multisig, operator-level wallets with scoped permissions, and ephemeral agent session keys with bounded spending — all enforced at the contract level rather than trusting an off-chain policy.

 layered failure hierarchies on top of authorization hierarchies — failure budgets, circuit breakers, human-in-the-loop thresholds — and landed on the same prerequisite: ERC-1271 first.

Circle's own response on the thread (@harshalbhangale-circle): 

"Our current model is EOA-based, and we haven't started designing for smart contract wallet signers yet."

So the gap is acknowledged. The question is sequencing. And it is something that requires care and attention. The whole ecosystem depends on it.

 call can adapt to work across the entire wallet spectrum natively. No adapters bridging gaps. No EOA-shaped workarounds inside multisig contracts. The Gateway contract just verifies whatever the wallet says is a valid signature, and the asset moves.

This is the moment stablecoins get web2 UX without web2 custody.

A consumer app can ship a "tap to pay" flow backed by a user-controlled SCA. A treasury product can ship the same flow backed by an MSCA multisig with policy controls. A payroll tool can dev-control the operating account but route everything through the same primitives. An agent can transact continuously within cryptographically enforced spending limits, with a human off-switch at every level of the hierarchy. The UI doesn't change. The trust model does.

Asset-first, custody-last. That's the design space ERC-1271 + AppKit + Gateway opens up — and it's the first time non-custodial actually competes with custodial on UX rather than apologizing for it.

Hoping it ships beyond dev-controlled 🚬🥃

Asset-first, custody-last: where Circle Wallets + AppKit should be headed

Home

Forum

Events

Content

Courses

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

Profession

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 noreply@arc.network 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 noreply@arc.network 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