Stackup primary-source snapshot

Last reviewed: 2026-04-27 UTC

Project status snapshot

What the official materials say

1) Homepage

  • URL: https://www.stackup.fi/
  • Key takeaways:
    • Stackup positions itself as crypto finance infrastructure for companies rather than as a consumer wallet or only a developer SDK vendor
    • The homepage emphasizes getting paid onchain, automating bill payments, and unifying onchain and offchain treasury operations
    • It also explicitly leans on security-and-safety language, which matters because the product is selling operational control, not only transaction execution

2) Security overview

  • URL: https://docs.stackup.fi/docs/security-overview
  • Key takeaways:
    • Stackup’s security docs emphasize self-custodial control, audited smart-account infrastructure, passkey-based authentication, and SOC2-oriented platform design
    • The docs say account configuration is stored offchain in a Merkle-tree structure while only a root hash is committed onchain, which is a high-signal clue about the actual architecture
    • The page also distinguishes wallet-level access configuration from platform-level admin/member/application roles, showing that Stackup is combining wallet infrastructure with enterprise operations software

3) Smart-account explainer

  • URL: https://docs.stackup.fi/docs/understanding-smart-accounts
  • Key takeaways:
    • Stackup explicitly ties its product to ERC-4337 and account abstraction, but frames that as a means to better business operations rather than as the end product itself
    • The docs say Stackup’s keystore smart accounts are purpose-built for shared multi-chain treasuries and emphasize adaptable access control, privacy by default, and sync across EVM chains
    • This page also makes the project’s lineage visible: the team presents itself as a former large-scale ERC-4337 infrastructure provider that has moved up the stack into business finance workflows

4) Keystore technical article

  • URL: https://www.stackup.fi/resources/stackup-keystore
  • Key takeaways:
    • This is the strongest single technical categorization page in the Stackup corpus
    • The article argues that current smart accounts struggle with key rotations, cross-chain sync, gas cost, and privacy, then proposes a Keystore contract plus Merkle-tree-backed configuration model as the fix
    • The architecture decouples account code from account configuration via an immutable reference hash pointing to a mutable root, which is the key insight behind Stackup’s current wallet design

5) Keystore repo and specification

6) Essentials / operations guide

  • URL: https://docs.stackup.fi/docs/stackup-essentials-guide
  • Key takeaways:
    • The guide shows the practical product surface: organization setup, team invites, wallet funding, bank connectivity, permissions, and transaction workflows
    • This is useful because it reveals Stackup’s real operating target user: founders, CFOs, and finance teams managing crypto operations, not only protocol developers
    • It also confirms that Stackup should be cataloged as a treasury / finance control plane rather than only as smart-account middleware

Whitepaper / technical-doc status

  • No standalone Stackup company whitepaper or litepaper surfaced in this pass.
  • The strongest technical source is the keystore article plus the open-source keystore specification.
  • A public Spearbit audit PDF for the keystore implementation was saved locally as stackup-keystore-spearbit-july2025.pdf.

Research notes

  • Best current category for the library: onchain finance operations / treasury control plane / self-custodial smart-account infrastructure.
  • The key insight is that Stackup is not just selling business wallets; it is bundling smart-account architecture, team access controls, audit trails, invoicing/payment workflows, and bank-linked treasury operations into one control plane.
  • This makes Stackup a good example of a crypto-adjacent firm whose official materials are richer than the homepage suggests once the docs and repo are read together.