Cowrie Research

anza-primary-sources-2026-08-13

3 min read

Anza company-boundary primary sources — 2026-08-13

Why this source capture exists

  • Earlier corpus work already had a useful product-layer note for solana-wallet-adapter.
  • This pass was about whether the surrounding operator boundary also deserves a separate companies/ note.
  • The answer is yes, because the same named organization now appears across Solana’s majority validator client, official Agave docs, SDK/tooling packaging, and app-side wallet-integration middleware.

Primary-source snapshots

1) Official homepage

  • URL: https://www.anza.xyz/
  • Key excerpt:
    • The homepage calls Anza the leading Solana-focused software development firm and a Solana R&D lab pushing the boundaries of blockchain performance and scalability.
    • It presents Agave as Solana's gold standard client and says it is the majority validator client built by the engineers closest to the protocol.
    • The same page groups validator software, consensus research, SDK work, and program/tooling work under one company boundary instead of presenting a single narrow product.

2) Agave documentation home

  • URL: https://docs.anza.xyz/
  • Key excerpt:
    • The docs say Agave is a fork of the original Solana validator previously maintained by the Solana Labs team and is now under active development by the core engineering team at Anza.
    • That is the cleanest first-party statement that Anza is not only a website brand; it is a live software-maintenance and release boundary for validator infrastructure.
    • The same docs package CLI, validator operations, architecture, and runtime documentation inside the Anza-run docs shell.

3) Wallet Adapter repository

  • URL: https://raw.githubusercontent.com/anza-xyz/wallet-adapter/master/README.md
  • Key excerpt:
    • The README describes Wallet Adapter as Modular TypeScript wallet adapters and components for Solana applications.
    • The repo path itself matters for taxonomy: this widely inherited wallet-integration layer now sits inside the anza-xyz GitHub organization rather than under a neutral standards body.
    • That makes the company boundary analytically useful even though the adapter remains a real project-layer note.
  • URLs:
  • Key excerpt:
    • The public GitHub organization shows Anza stewarding multiple important Solana-adjacent repositories, including agave, kit, and solana-sdk, alongside the wallet-adapter repository.
    • The privacy policy and terms identify the legal entity as Anza Technology, Inc. and describe Anza as the company providing the website and services.
    • Together these pages establish both the practical software-maintenance boundary and the formal legal-entity boundary.

Working conclusion

Anza should not replace product notes like solana-wallet-adapter. The adapter note is still the right place for app-side wallet selection, modal packaging, capability handling, and migration away from wallet-specific adapters. But a separate company note is warranted because one named operator now packages validator-client stewardship, official docs, SDK/tooling work, and wallet-integration middleware under the same company shell. That boundary materially improves control-surface analysis for the Solana stack.

Graph View