Stackup
- Name: Stackup
- URL: https://www.stackup.fi/
- Category: treasury control plane / crypto finance-operations platform / self-custodial smart-account infrastructure
- Tags: ethereum-ecosystem
- Summary: Stackup is treasury software built on smart-account rails. The useful point is not
AA infrastructurein the abstract; it is that Stackup turns shared accounts, passkeys, approvals, invoice flow, and bank hookups into one operator surface for crypto-native finance teams. Good note for treasury-control comparisons, not for treating every ERC-4337 vendor as a finance platform. - What it does:
- Provides a web platform and APIs for businesses to pay vendors, receive crypto payments, manage team permissions, and operate shared wallets with full audit trails
- Uses self-custodial ERC-4337-style smart accounts with passkeys, role-based access, and configurable wallet-level permissions rather than relying on shared EOAs or hardware-wallet-heavy workflows
- Connects onchain treasury activity with offchain banking rails, including US bank connectivity and fiat conversion through partner flows
- Publishes a keystore architecture designed to keep account configuration gas-efficient, privacy-preserving, and easier to synchronize across multiple EVM chains
- Maintains open-source keystore contracts, specification docs, deployment addresses, and audit artifacts that expose the underlying account model more clearly than the marketing site alone
- Key claims:
- The homepage positions Stackup as crypto finance infrastructure for businesses that want to get paid onchain, automate bill payments, and unify onchain and offchain treasury operations
- The security docs say the platform is built around self-custodial control, passkey authentication, audited smart-account contracts, and SOC2-oriented platform controls
- The smart-account docs describe Stackup’s keystore accounts as purpose-built for shared multi-chain treasuries, emphasizing gas efficiency, privacy by default, and flexible access-control updates across chains
- The keystore technical article argues that decoupling account configuration into a Merkle-tree-backed singleton contract helps solve key-rotation, cross-chain sync, gas-cost, and privacy problems that affect current smart-account designs
- The docs and product guides show Stackup has expanded beyond its earlier ERC-4337 infrastructure identity into a broader finance-ops platform with invoicing, team workflows, bank connectivity, and transaction operations for crypto businesses
- Whitepaper: No classic standalone Stackup company whitepaper or litepaper was found in this pass. The strongest technical primary sources were the official docs, the keystore technical article, the open-source keystore specification, and the public audit artifact saved locally; see
../whitepapers/stackup-primary-sources-2026-04-27.mdand../whitepapers/stackup-keystore-spearbit-july2025.pdf. - Sources:
- https://www.stackup.fi/
- https://docs.stackup.fi/docs/security-overview
- https://docs.stackup.fi/docs/understanding-smart-accounts
- https://docs.stackup.fi/docs/stackup-essentials-guide
- https://www.stackup.fi/resources/stackup-keystore
- https://github.com/stackup-wallet/keystore
- https://raw.githubusercontent.com/stackup-wallet/keystore/main/README.md
- https://raw.githubusercontent.com/stackup-wallet/keystore/main/doc/spec.md
Internal linkages
-
Keep this note tight.
-
Best anchors: safe, fireblocks, and aera.
-
Reusable lens: Stackup is where
self-custodial treasury toolingcashes out as role design, signer recovery, payment approvals, audit visibility, and cross-rail operating defaults. -
Useful contrast: bundler vendors stay closer to ERC-4337 traffic plumbing, while Stackup is the finance-ops layer built on top.
-
Last reviewed: 2026-05-31 UTC