Our customers are running digital assets at serious scale. They’re processing payouts across dozens of chains, issuing embedded wallets to millions of end users, and closing audited books under new legislation. Our job is to keep shipping the infrastructure that makes that possible, and help our customers make the most of everything we’ve built.
That’s why we ran our recent Pulse Masterclass webinar, a deep dive session with live demos on scaling digital asset operations with speed, security, and compliance. If you’re running digital assets at scale, or planning to, what we covered applies to you too.
The market context is quickly evolving. Digital assets are becoming core financial rails, and the line between traditional finance and crypto keeps getting thinner. The businesses that offer the best financial experience, regardless of the underlying technology, are the ones who will lead.
For those businesses, nearly every infrastructure question rolls up to one of two themes: how do I protect my business, and how do I grow it? We built the session around these needs.
Operating at Scale Means Protecting and Proving
Once key management is solved, the operational risk moves to configuration: the policies, permissions, and access controls that govern how assets move. The reality is that these configurations drift over time as the business evolves and operations become more complex, increasing the surface area for risk.
Fireblocks Security Posture Management (FSPM), the first SPM tool purpose-built for digital assets, catches that drift. It runs continuously against your workspace, flagging risks like stale policies, inactive users, and weak approval thresholds. Every finding explains what the issue is, why it matters, and how to fix it, and every fix or accepted risk is logged with a timestamp.
That trail matters because auditors want evidence that controls held across the entire audit period, not a folder of screenshots assembled the week before the review. Additional recent releases like Policy Export, Policy Inspector, and Protected Tags make policy configuration portable, explainable, and maintainable, so your audit trail becomes a byproduct of normal operations, not something your team produces under pressure.
Finance teams face the same problem from a different angle: blockchain data isn’t audit-ready, and traditional finance systems weren’t built for onchain activity. With regulators now demanding financial clarity, that gap is no longer deferrable, which is why we acquired TRES Finance. TRES pulls data from more than 280 sources, reconciles it, applies your cost basis methodology, and syncs with any ERP. It carries SOC 1 and SOC 2 Type II certifications and complies with GAAP and IFRS, so the numbers coming out of it hold up in an audit.
The Product Experience Has to Abstract the Complexity
Growth introduces a different set of infrastructure demands on top of the security and compliance foundation. The focus for growth-stage digital asset businesses is what comes next: building product experiences that abstract the underlying complexity entirely, so neither the end user nor the team behind the product ever has to think about it.
One path is embedded wallets through Dynamic, a non-custodial model where users hold their own assets and the business owns the product experience around them. Another is direct custody infrastructure, where the business takes custody and runs the full operational stack on behalf of its customers.
On the embedded wallet side, the goal is a product experience that feels native, with none of the blockchain complexity surfacing to the user. Users can log into an application with familiar login methods, get an embedded wallet created without a separate login, and send gasless transactions on both Solana and EVM chains with no signing pop-ups unless the business wants them.
We also introduced Fireblocks Flow, where a user funds an application in whatever asset they already hold while the business receives the stablecoin it actually wants. The swap, and any necessary bridging, happens out of view. The user sees a transaction that cleared. The business receives the asset it needs. The conversion and any bridging across chains happened in between, without either side having to think about it.
These two architectures are not entirely separate. The magic spend flow connects them directly. This flow moves assets from a Fireblocks Vault into a user’s embedded wallet and onchain in a single coordinated sequence, without requiring separate integrations at each step. Building this flow natively, without stitching together separate systems across custody, embedded wallets, and onchain execution, is what makes it viable to offer at scale.
High-Volume Infrastructure Has to Be Governed, Not Just Scaled
Every operation should happen inside a governed and auditable environment. The features built for high-volume direct custody operations are designed around exactly that. The businesses processing a high frequency of transactions cannot afford for governance to slow them down.
We introduced batch approvals for exactly this reason. Rather than completing a PIN code and biometric for each request, approvers can now bundle up to ten transfers into a single action. The security model stays intact, with the Policy Engine still determining who approves what and under which conditions. What changes is the number of times an approver has to go through the process to get through their queue.
The same logic runs through the rest of the set:
- Solana multi-destination transactions let a business pay out to many destinations atomically as a single transaction.
- The UTXO Manager gives granular control over UTXO statuses for fee estimation and balance handling.
- Broadcasting sub-statuses and Account Traffic Control give operators visibility into what happens to a transaction after it leaves Fireblocks, with the latter using AI tooling to detect transactions stuck in the mempool and troubleshoot them in real time.
The governed environment requirement extends to every operation a team executes, including ones that have historically required reaching outside the platform. Native swapping is the clearest example. Teams can now execute swaps and cross-chain bridging directly in the console, without connecting out to a third party DEX or bridge. A native order policy type governs who can trade, where, and under what limits.
Additionally, access to DeFi yield from blue-chip protocols Aave and Morpho is now available as a native experience inside Fireblocks, governed by policy. Staking follows the same logic, with expanded support now including ETH validator connectivity through ETH Link, letting businesses connect their own validators to their Fireblocks workspace while retaining the validator keys. Every staking operation, from creating a stake to a full unwind, runs through policy.
That is the common thread. The work of mature infrastructure is to pull those operations back inside, wrap them in policy, and make the secure path the convenient one. Running digital assets at scale looks exactly like this, built into every release we ship.
Want to see these capabilities in action? Watch the recording to go deeper on any of the topics above.
