Cowrie Research

astria-company-primary-sources-2026-08-11

3 min read

Astria company primary-source snapshot

Fetched: 2026-08-11 UTC

1) Mainnet Alpha network page

Source: https://docs.astria.org/networks/mainnet-alpha

Selected excerpts from the official docs:

Sequencer RPC https://rpc.astria.org/

Sequencer gRPC https://grpc.astria.org/

Sequencer Block Explorer https://astrotrek.io/

Celestia Signer celestia1ldf3mhs0z5h5effkkyvc5scpy0xah00t98xfml

Additional signals from the source:

  • The mainnet page is useful company-layer evidence because it publishes the canonical public entrypoints, signer address, bridge-channel map, and explorer path users are expected to trust first.
  • The same page also lists current mainnet service versions and links directly to Astria-owned source repositories for the Conductor, Composer, Sequencer-relayer, Sequencer, and Flame components.

2) Bridging overview

Source: https://docs.astria.org/bridging/cli-bridging-overview

Selected excerpts from the official docs:

IMPORTANT The Astria Bridge UI is the recommended method for bridging to Astria.

Visit the Astria Bridging UI here (https://bridge.astria.org).

Additional signals from the source:

  • This is strong first-party evidence that the easiest production path into Astria is not only protocol-level IBC mechanics but also an operator-packaged bridge surface.
  • The page also centralizes the official IBC channel map and tells users which CLI dependencies and endpoints to use, reinforcing Astria as the documentation and workflow authority around the live network.

3) Mainnet bridging guide

Source: https://docs.astria.org/bridging/mainnet-alpha/bridge-to-astria-mainnet-alpha

Selected excerpts from the official docs:

astria-cli sequencer balance get $ASTRIA_ADDRESS —sequencer-url https://rpc.astria.org/

Additional signals from the source:

  • The mainnet bridging guide routes users back through the same official RPC endpoint and channel configuration published on the network page.
  • That matters because the practical onboarding surface is company-shaped even when the underlying transport is IBC.

4) Transaction flow

Source: https://docs.astria.org/overview/transaction-flow

Selected excerpts from the official docs:

In the current architecture, an instance of the Composer is run alongside each individual rollup.

Our hope is that the Composer serves as a starting point for searchers and block builders interested in collecting end user order flow for one or more rollups and submitting it to the shared sequencer as bundles or blocks.

Additional signals from the source:

  • This is useful company-layer evidence because it shows Astria not only defining protocol mechanics but also publishing the default orderflow-collection component it expects rollups, searchers, and builders to start from.
  • Composer / Conductor packaging is part of the operator boundary even before asking who eventually runs more decentralized versions of the network.

5) Monorepo README

Source: https://raw.githubusercontent.com/astriaorg/astria/main/README.md

Selected excerpts from the official repo:

This repository contains the custom Astria components that make up the Astria network.

To run locally, we utilize a dev-cluster which can be found at astriaorg/astria/tree/main/charts.

To learn more about Astria, please visit astria.org.

Additional signals from the source:

  • The README makes the implementation boundary explicit: Astria controls the main monorepo, component layout, and recommended dev-cluster path for anyone trying to run or extend the stack.
  • The protocol may be about shared sequencing, but the implementation and release surface still lives under one named organization.

Notes

  • Astria clears the bar for a company/entity note because the practical dependency is not only lazy shared sequencing; it is the named operator that publishes the canonical RPC / gRPC / explorer / bridge path, curates current mainnet component versions, stewards the implementation repos, and packages the default Composer / Conductor rollout shell.
  • The project note should stay on sequencing, DA publication, namespace verification, and soft-versus-firm commitments. The company note should stay on endpoint truth, bridge workflow, release authority, and the default production path users inherit first.

Graph View