Cubist

High-performance infrastructure for managing digital assets. Powering digital asset operations with the rigor and accountability of modern finance.

[Cubist @cubistdev]

We built CubeSigner for workloads where milliseconds change what's possible.

One of our customers, a high-frequency trading firm, is using Cubist to process 17 million transactions/day with 99.999% uptime while maintaining 24 ms p50 signing latency.

To our knowledge, that's significantly faster than the published benchmarks of any competing wallet infrastructure (and these are production metrics measured through real market volatility, not under controlled test conditions).

We recently published a case study describing how we helped this trading firm achieve industry-leading performance without hot wallets. Link in comments.

[Range @range_org]

Range now supports @Cubistdev.

View your Cubist-secured balances alongside every wallet, bank account, exchange and custodian you hold, in a single real-time view, with continuous monitoring across all of them.

Cubist's hardware-backed signing infrastructure now orchestrates institutional asset flows across regulated finance and DeFi. Its accounts sit in the same view.

Add your Cubist-secured accounts 👇 Builders can integrate via the Range API.

[Range @range_org]

Range now supports @Anchorage, @FireblocksHQ, @BitGo, @Turnkeyhq, @CopperHQ, @Utila_io, @DfnsHQ, @FordefiHQ, @Cubistdev, and @Privy_io.

Your custody and wallet balances now sit in a single real-time view with every wallet, bank account and exchange you hold, continuously monitored for sanctions, fraud and exposure.

No console to log into per provider. Data flows directly to QuickBooks or Xero.

Connecting your accounts is completely free. Builders can integrate via the Range API.

Add your accounts 👇

https://t.co/q059jxUZvb

[Lacey @laceywisdom]

@MetaMask just shipped agent wallet powered by @cubistdev 🤯 great to see two @plcapital portfolio companies collaborating on something so important

[Kostas Ferles @KFerles]

Even though the concept of an agent wallet terrifies me, I feel safer when knowing that @cubistdev is involved!

[Cubist @cubistdev]

One of the most rewarding parts of being an infrastructure provider is watching customers ship products that move the industry forward. Congratulations to the @MetaMask team on today's launch of 🦊 MetaMask Agent Wallet.

In order to handle real assets, AI agents need clear guardrails outlining what they can and can’t do. MetaMask Agent Wallet lets users define spend limits, allowlisted protocols, and risk profiles while staying in control of their own keys.

We're delighted to have CubeSigner and Confidential Cloud Functions (C2F) powering the self-custody key management, transaction signing, and policy enforcement behind MetaMask Agent Wallet. Something we’ve always been proud of is the customizability of the Cubist platform and it’s exciting to see MetaMask Agent Wallet put that customizability directly in their users’ hands to let them shape their own agentic experiences.

[Cubist @cubistdev]

Excited to see 🦊 @MetaMask Agent Wallet reach everyone today with @cubistdev powering the key management that makes autonomous signing safe to run unattended. One of the best parts of building infrastructure is seeing it disappear into products people love.

Cubist 🤝 MetaMask

[MetaMask 🦊 @MetaMask]

Your agent finally gets its own wallet.

MetaMask Agent Wallet is now live for everyone.

[Francesco Andreoli ᵍᵐ @francescoswiss]

We shipped it, the 🦊 Agent Wallet is live for everyone today, a huge milestone for the team

Agents can research, plan and decide (24/7). The moment they need to move money onchain, everything has historically gotten fragile.

A self-custodial wallet built for autonomous execution: you set the spend limits, protocols and risk profile, the agent stays inside them. Gasless, batched, security checks on every transaction.

I've spent most of this year close to this product, and the reason it matters to me isn't the agent — it's the rails. Autonomous finance doesn't work until the execution layer is boring and safe. Today it got a lot closer.

If you build anywhere near trading, agents and crypto, take a look and come say HI.

none of this ships alone. built with:

@HyperliquidX — perps execution, the venue agents actually want
@Polymarket — prediction markets, because agents are good at pricing beliefs
@aave — idle capital doesn't have to sit idle
@CoWSwap — mev-protected, intent-based swaps. agents get filled, not sandwiched
@lifiprotocol — cross-chain routing so the agent doesn't care what chain the opportunity is on
@blockaid_ — every transaction screened before it signs
@cubistdev — the key management that makes autonomous signing safe to run unattended
@awscloud — the infra underneath all of it

🧡

[MetaMask 🦊 @MetaMask]

👉️ Start using MetaMask Agent Wallet: https://t.co/faosgwUZS8

Built with @HyperliquidX @Polymarket @aave @CoWSwap @lifiprotocol @blockaid_ @cubistdev @awscloud 🧡

[Cubist @cubistdev]

See the case study here: https://t.co/IzkWrdgMEN

[Cubist @cubistdev]

We built CubeSigner for workloads where milliseconds change what's possible.

One of our customers, a high-frequency trading firm, is using Cubist to process 17 million transactions/day with 99.999% uptime while maintaining 24 ms p50 signing latency.

To our knowledge, that's significantly faster than the published benchmarks of any competing wallet infrastructure (and these are production metrics measured through real market volatility, not under controlled test conditions).

We recently published a case study describing how we helped this trading firm achieve industry-leading performance without hot wallets. Link in comments.

[Cubist @cubistdev]

Read the case study here: https://t.co/IzkWrdgMEN

[Cubist @cubistdev]

One of DeFi's highest-volume trading firms reduced signing latency from 600 ms to 24 ms by switching to Cubist wallet infrastructure.

They deployed the Cubist platform in their own cloud environment to hit their latency targets and safely bring profitable new trading strategies into production.

For firms trading on DEXes, security at speed is a difficult balance to strike. Wallets handling millions of dollars need institutional-grade protection, while trading systems need to execute in milliseconds. This firm's existing MPC infrastructure met their security requirements, but every signing request added enough latency to make some strategies infeasible.

Rather than resorting to hot wallets to achieve the performance they needed, the firm integrated CubeSigner and Confidential Cloud Functions (C2F) to securely manage their keys and signing.

Signing latency is 25x faster, while every signing request continues to pass through a policy engine that restricts the types of transactions traders and systems can sign. Using C2F, policies even incorporate real-time market data into automated signing decisions.

Separate governance policies control who can modify those rules, ensuring no individual has unilateral control over the system.

Results at a glance:
🔵 24 ms p50 / 28 ms p90 / 32 ms p95 signing latency
🔵 500 million signing operations per month
🔵 99.999% measured uptime
🔵 No performance degradation during periods of extreme market volatility

As the firm's Head of Trading put it: "Signing latency is no longer the constraint that's driving decisions about which strategies we can and can't deploy."

If your trading desk is wrestling with similar tradeoffs between security and performance, check out the full case study linked in the comments.

[Cubist @cubistdev]

Cubist is glad to be working alongside an impressive group of partners as momentum builds towards @SuiNetwork's Hashi testnet launch. We're excited by efforts to make Bitcoin a more productive asset for institutions and bring new participants into the ecosystem.

[Sui @SuiNetwork]

Hashi is a native Sui primitive turning ~$1T of idle $BTC into productive financial collateral.

Ahead of its global testnet launch this July, @CumberlandSays, @swissborg, and @0xfluid are the latest to join 20+ partners in the Hashi ecosystem.

[Cubist @cubistdev]

The industry is converging on an important idea: agents need guardrails, not just capabilities.

We’re thrilled to have the Cubist platform contributing to the infrastructure behind @MetaMask Agent Wallet.

As @zenzhenyu put it:
"If the first generation of trading agents normalizes giving away your keys, we'll be rebuilding the custodial mistakes crypto spent a decade escaping.”

That's why we believe the most important question in agentic trading is no longer whether agents can transact onchain, but how users stay in control when they do.

[Cubist @cubistdev]

Congrats to the @MetaMask team! Cubist is proud to contribute to the infrastructure behind MetaMask Agent Wallet and excited to see it reach one of the largest communities in crypto.

The era of agentic trading is here and so are the myriad risks that come with giving AI agents access to real assets. We believe the future of agentic trading will be defined by how confidently users can delegate to agents.

MetaMask Agent Wallet gives an agent an agent-specific wallet, connects through a command-line interface (CLI), and lets the user set operating rules before the agent starts transacting. We're eager to see these workflows become a familiar part of the onchain experience.

[MetaMask 🦊 @MetaMask]

The MetaMask Agent Wallet is here. 🦊

Early Access is now live - 200 spots available.

👇

[Cubist @cubistdev]

@squidrouter We believe in Squid

[Cubist @cubistdev]

We believe better applications don't just scale across chains—they work everywhere by design.

🤝@squidrouter x @cubistdev making this real

[squid @squidrouter]

What do you believe in?

[Cubist @cubistdev]

Manifest your beliefs below

https://t.co/dZ2gbaUZ14

[Cubist @cubistdev]

We believe that systems can have your back. Security isn't just a checklist for us: strong signing operations are built for real life and can say "no" when people can't.

What do you believe in?

[Cubist @cubistdev]

Our customers kept wanting to restrict key usage based on core application logic: needing to check state on a different chain before signing, compute over sensitive data, or tie approvals to an external system.

Those kinds of rules don’t fit neatly into a predefined menu—especially when handling keys programmatically—because they’re unique to every product.

That’s what led us to develop Cubist Confidential Cloud Functions (C2F): instead of prescribing a narrow set of rules to govern signing logic, it gives developers the freedom to write their own.

🔍 On-chain verification — check blockchain state before signing (e.g., confirm a burn or liquidity event).

🛡 Cross-chain enforcement — “watch here, act there” logic (e.g., Bitcoin event authorizing action on Ethereum).

🔗 Integrations with external systems — tie approvals to KYC/AML services, fraud monitoring, oracles, LLMs, etc.

🧪 Transaction simulation — run simulations and gate signatures based on the result.

🚦 Smart contract upgrades — require that upgrades are signed by CI pipeline builds and/or approved by auditors.

🔒 Privacy-preserving policies — enforce sensitive approval logic off-chain without exposing it publicly.

🔑 Secret-handling policies — run logic over sensitive data (e.g., trading strategy, cross-chain order book, API keys, etc.) that is dangerous to include in an onchain smart contract.

🧩 Composable attestations — accept or reject transactions based on attestation evidence from trusted enclaves or validators.

The takeaway: for most Web3 use cases, infrastructure security needs to be programmable. Confidential Cloud Functions make key management as expressive as application code.