Skip to content

Stellar Registry: 2026 Q4 deliverables - #5

Draft
pselle wants to merge 10 commits into
mainfrom
deliverables/stellar-registry-2026q4
Draft

Stellar Registry: 2026 Q4 deliverables#5
pselle wants to merge 10 commits into
mainfrom
deliverables/stellar-registry-2026q4

Conversation

@pselle

@pselle pselle commented Nov 2, 2026 •
edited by github-actions Bot
Loading

Copy link
Copy Markdown

Stellar Registry

Stellar Registry is an on-chain smart contract registry for Soroban that lets developers publish,
version, discover, and deploy Wasm binaries and contract instances, making contracts reusable across
the ecosystem like packages.
Category Developer Experience
Website https://rgstry.xyz
CLI & Rust Macros https://github.com/stellar-registry/cli
UI https://github.com/stellar-registry/ui
Indexer & API https://github.com/stellar-registry/indexer
Contract(s) https://github.com/stellar-registry/contracts
OZ Wasms https://github.com/stellar-registry/oz-combined-wasms
GH Actions https://github.com/stellar-registry/actions
First Released March 2026
Intake SCF-Public-Goods-Maintenance#23
Budget Requested $50,000
Maintenance Reserve $12,500
Other $37,500

Project Description

Registry is the missing infrastructure layer between "I wrote a smart contract" and "the ecosystem
can safely use my smart contract."

Registry tracks two things:

  1. Contracts: Registry gives contracts human-friendly names, rather than gobbledigook IDs, as
    well as tracking a contract's owner and its Wasm.
  2. Wasms: Stellar separates a contract instance, if you will (see item 1), from the WebAssembly
    (Wasm) binary that defines its behavior. Many contracts can use the same Wasm binary, but today
    that's impractical because Wasms are identified only by a gobbledigook ID.

Registry makes these usable. It gives them both names and versions, making the development
experience feel like familiar package management—like crates.io or NPM.

Team & Experience

Stellar Registry is built and maintained by The Aha Company, a team of 10+ senior engineers
deeply embedded in the Stellar ecosystem.

Early Soroban origin:

In 2022 (before Soroban had a name) SDF already had a clear ambition: launch their upcoming smart
contract platform with a “batteries-included” developer experience. The gap was execution capacity:
there was no in-house team available to design and implement the developer workflows needed to make
that promise real. Tyler van der Hoeven went to major blockchain conferences to find the right team,
and identified The Aha Company as the team with the right combination of product mindset and deep
technical ability to “install the batteries.”

Foundational Stellar developer workflows we designed and shipped:

We envisioned, architected, and implemented several of the workflows that have become core to Soroban
development on Stellar, including:

  • Stellar CLI smart contract workflows, such as the contract invoke behavior and associated
    developer ergonomics that leapfrog, rather than ape, other blockchain ecosystems, simplifying
    testing, deployment, and interaction.
  • JavaScript developer experience patterns, including the Contract Client behavior in
    stellar-sdk-js, which helps application developers interact with contracts more safely and
    predictably.
  • Stellar Scaffold, helping newcomers, experts, and AI agents ship quickly, reduce bugs, and
    focus on app logic not nuts-and-bolts wiring and boilerplate.

Deep community participation and ecosystem leadership:

Our team includes well-known ecosystem contributors. Several members hold key community roles (e.g.,
SCF Pilot, category delegates) and actively build their own SCF projects (e.g., Moonlight,
Tansu, Stellar Merch Store, PG Atlas, Turbolong). We contribute to protocol and tooling
discussions, provide developer support at hackathons and conferences, and invest heavily in community
outreach and education. We show up consistently at major events and actively communicate about
Stellar, both its strengths and the practical realities builders need to know.

Cross-ecosystem perspective (DevX benchmarking):

Beyond Stellar, The Aha Company is also an integration partner in other ecosystems (e.g., Filecoin,
XRPL, Cardano, Canton, Starknet). This gives us a unique ability to benchmark developer experience
across chains and bring proven patterns back to Stellar—while keeping Stellar Registry aligned with
what developers expect from modern, full-stack tooling.

Specific teammates assigned to Stellar Registry:

In the latter half of 2026, the Stellar Registry team consists primarily of the following
individuals, in order of involvement:

  • Pam Selle — @pselle • LinkedIn • Registry Lead
  • Willem Wyndham — @willemneal • LinkedIn • PR
    review; co-architect; key research (such as on continued stellar-registry/actions maturation
    (D9), Secure Store upstream contributions (D8), and named accounts for both G- and C-addresses
    (D5))
  • Chad Ostrowski — @chadoh • LinkedIn • PR review;
    co-architect; dev outreach & education (D3)
  • Zach Fedor — @zachfedor • LinkedIn • UI Lead

Retroactive Impact

In Q3 2026 the Registry finished its mainnet launch and grew from infrastructure you can query into a
toolkit developers can build with: import_contract! shipped in a released crate, rgstry.xyz became
a full discovery and deployment platform, and the governance machinery we built for Registry was
adopted upstream by Tansu for every project that uses it.

The mainnet launch is complete. Mainnet data is fully indexed in Goldsky
(stellar-registry/indexer#25) and served from https://stellar-registry-mainnet.fly.dev/.
stellar.rgstry.xyz is now the primary subdomain (with rgstry.xyz
redirecting to it), the registry contract is visible on Stellar Expert, and every stellar registry
command works across both testnet and mainnet.

Registry is now composable from Rust. import_contract! is released, documented on
crates.io and
docs.rs, and covered by unit tests that run on every commit.
Shipping it took two large re-architectures, the consolidation of the related
import_contract_client! and import_asset! macros into the Registry repo, and a new
stellar-registry-name crate. With that release,
all Stellar Registry crates reached official beta at version 0.1.0. Compile-time safety came with it:
flagged contracts fail to resolve by default, proven by an integration test
(stellar-registry/cli#60). The macro also now handles Stellar Asset Contracts, so
import_contract!(xlm) and import_contract!("circle/usdc") work for any SAC registered in Registry
(stellar-registry/cli#64).

rgstry.xyz became a real discovery platform. Server-side fuzzy search now covers contracts as
well as Wasms (stellar-registry/indexer#24), e.g. every mainnet contract matching
kal. Wasm pages gained a "deploy this Wasm" form
(stellar-registry/ui#23) and contract pages an embedded Contract Explorer (stellar-registry/ui#24).
Verified-build (SEP-55) badges from Stellar Expert data now appear on contracts
(stellar-registry/ui#57), and SEP-58 source-verification fields are surfaced on Wasm and contract
pages (stellar-registry/indexer#49, stellar-registry/ui#82, stellar-registry/ui#83).

Governance became shared infrastructure. A new Governance section on rgstry.xyz provides forms to
propose adding a contract to the root registry (stellar-registry/ui#67), adding a Wasm
(stellar-registry/ui#71), or creating a subregistry (stellar-registry/ui#81). Meanwhile, the
workaround we built last quarter to act on Tansu proposals was merged into Tansu itself (merged to
Tansu main 2026-09-02), builds against the real Tansu contract, and is documented in Tansu's
governance docs, so any ecosystem project can now use it. We deleted our duplicate
registry-tansu-manager and tansu-stub (stellar-registry/contracts#55).

Secure CI publishing, and a new product. The Registry contract now auto-publishes its Wasm on
commits to main (stellar-registry/contracts#53). Keeping keys on GitHub safe led us to design and
ship Perch, a composable policy layer for Soroban smart
accounts.

Also shipped. Foundational support for named G-addresses in the registry contract
(stellar-registry/contracts#37, stellar-registry/contracts#38); full contract version history on
contract detail pages (stellar-registry/ui#40); a
Stellar Registry Full Walk-Through video on The Aha
Company's YouTube channel; and a new logo and consolidated documentation.

Past Deliverables

2026 Q2

Every deliverable below has merged, verifiable work behind it this quarter; where release mechanics
remain, the item states exactly what is left. We also shipped substantial infrastructure beyond the
proposed scope — see "Beyond the proposal" at the end of this section.

D1. Mainnet Deploy of Stellar Registry

Description from last quarter:

Deploy the Registry smart contract to Stellar mainnet and confirm it is publicly accessible via
stellar registry CLI and rgstry.xyz.

Measure: the contract is deployed & the CLI points to it.

Proof of completion:

Deployed to mainnet. The phased deploy pipeline merged and executed at the close of the quarter:
the registry contract is live on mainnet at its deterministic ID, seeded with verified ecosystem
contracts, and resolvable via the stellar registry CLI (the mainnet ID ships baked into the CLI).
Remaining for full public accessibility: the mainnet indexer pipeline and pointing
rgstry.xyz at mainnet — rolling out this week — plus secure-store/Ledger
signing for admin operations (stellar-registry/cli#14).

D2. import_contract! Macro

Description from last quarter:

Publish a working import_contract! macro in the stellar-registry crate that allows
cross-contract client instantiation with a single line of Rust.

Measure: the macro is available in a released crate version, documented with at least one working
example, and covered by integration tests.

Proof of completion:

Shipped — release mechanics left. The macro is implemented, tested (13 unit tests,
pedantic-clippy clean), and in final review, and rgstry.xyz already teaches developers how to use the
import macros on every contract page. The crates.io publish lands days into Q3.

D3. Flagged Contract Enforcement at Build Time

Description from last quarter:

Extend import_contract! and import_contract_client! to emit a compile-time error when the
referenced Wasm or Contract is flagged in the Registry.

Measure: a test exists that demonstrates a flagged contract causes a build failure, and the
behavior is documented.

Proof of progress:

D4. Server-Side Search, Pagination & Sorting on rgstry.xyz

Description from last quarter:

Replace the current client-side full-data-fetch approach with API-backed search, pagination, and
sorting on rgstry.xyz.

Measure: the explorer handles at least 1,000 published Wasms/Contracts without degraded load time,
search returns results server-side, and pages load incrementally.

Proof of completion:

Shipped for Wasms — live in production. Server-side fuzzy search is merged and answering queries
on rgstry.xyz today, and the API already supports limit/cursor pagination. Remaining: the same
treatment for contracts (stellar-registry/indexer#24, open), the explorer's pagination/sorting UX,
and validation against a 1,000+ entry dataset.

D5. rgstry.xyz UI Enhancements

Description from last quarter:

Ship three specific improvements to the Registry web explorer:

  1. Contract Explorer embedded on contract detail pages
  2. stellar contract info meta metadata surfaced on Wasm and Contract detail pages
  3. A "deploy this Wasm" button that initiates a Registry deploy from the UI

Measure: all three features are live on the production rgstry.xyz site and manually verified
against at least one mainnet contract.

Proof of completion:

Backend and page richness shipped. The metadata API (item 2's backend) is live and serving the
full contract info meta fields, and contract pages gained README/LICENSE rendering beyond the
proposed scope. Remaining: surfacing the rest of the metadata fields in the UI, the embedded Contract
Explorer (item 1), and the deploy button (item 3).

D6. Verified Build Integration with Stellar Expert

Description from last quarter:

Display verified build status from Stellar Expert's API on Registry Wasm and Contract detail pages.

Measure: the verified build badge or indicator is visible on at least one Wasm detail page with a
known verified contract, and the integration is live in production on rgstry.xyz.

Proof of completion:

Shipped — Registry releases are themselves verified builds. Every registry contract release is
now built by the stellar.expert workflow with OIDC build-provenance attestation, and the first
attested release is public. Remaining: displaying the badge on rgstry.xyz detail pages — targeting
contract pages, since we established Stellar Expert has no Wasm-level pages (stellar-registry/ui#17).

D7. Registry Documentation & Education

Description from last quarter:

Publish complete Registry documentation and videos covering:

  • publishing a Wasm
  • deploying a named contract
  • using import_contract!
  • deploying an unnamed contract
  • publishing/releasing using CI workflow
  • more!

Measure: documentation is live on Registry's own docs site & The Aha Company's YouTube channel.

Proof of completion:

Docs shipped in the product; the guide is live. The Registry Guide is live and linked from the
rgstry.xyz nav, every contract and wasm page carries usage guides, and all four standalone repos got
rewritten documentation. Remaining: moving the guide to Registry's own docs site, import_contract!
coverage (follows the D2 release), and the video series.

Beyond the proposal

Infrastructure we shipped this quarter that was not in the Q2 deliverables:

2026 Q3

✅ D1: Complete the Mainnet Launch (carried from Q2)

Description from last quarter:

With the registry contract live on mainnet, finish the public rollout: run the mainnet indexer
pipeline, point rgstry.xyz at the mainnet API and remove the "Coming Soon" banner, and land
secure-store/Ledger signing in the CLI (stellar-registry/cli#14) so admin operations never expose a
raw secret key.

Proof: mainnet data live and browsable at rgstry.xyz, the contract visible on Stellar Expert, and
named contracts resolvable via stellar registry CLI.

✅ Complete:

✅ D2: Release import_contract! (carried from Q2)

Description from last quarter:

Merge stellar-registry/cli#17 and publish the macro in released crates, documented with at least
one working example and covered by integration tests.

Proof: a crates.io release containing import_contract!, linked docs and example, CI running the
integration tests.

✅ Complete:

The macro has landed! This was a hefty engineering task that entailed two large-scale
re-architectures, code consolidation from other repositories (stellar-scaffold/cli repo is no
longer the home of related macros import_contract_client! and import_asset!), and the creation of
a new stellar-registry-name crate. With this
release, we declared all Stellar Registry crates to have reached official beta, marking them all as
version 0.1.0.

✅ D3: Flagged Contract Enforcement at Build Time (carried from Q2)

Description from last quarter:

Extend import_contract! / import_contract_client! to fail compilation when the referenced Wasm
or Contract is flagged in the Registry, building on the on-chain flagging that shipped in April.

Proof: a test demonstrating a flagged contract causes a build failure, and documented behavior.

✅ Complete:

✅ D4: Finish Search, Pagination & Sorting on rgstry.xyz (carried from Q2)

Description from last quarter:

Extend server-side search to contracts (stellar-registry/indexer#24), fix search-result updating
(stellar-registry/ui#22), and ship pagination and sorting so the explorer handles 1,000+ entries
without degraded load time.

Proof: live on rgstry.xyz; search, pagination, and sorting demonstrated against a 1,000+ entry
dataset.

✅ Complete:

✅ D5: Contract Explorer, Deploy Button & Verified-Build Badges (carried from Q2)

Description from last quarter:

Ship the remaining explorer features: the embedded Contract Explorer on contract detail pages, a
"deploy this Wasm" button, the remaining stellar contract info meta fields surfaced on detail
pages, and verified-build status from Stellar Expert on contract detail pages.

Proof: all features live on production rgstry.xyz, manually verified against at least one mainnet
contract.

✅ Complete:

✅ D6: Governance Operations UI

Description from last quarter:

Ship the governance proposal forms (stellar-registry/ui#51): propose adding a Wasm or contract to
the root registry, creating a subregistry, or changing owners — executed through the
Tansu-DAO-gated registry manager contract that merged in Q2.

Proof: a governance proposal created from rgstry.xyz, voted on in Tansu, and executed on-chain via
trigger, with the transaction linked.

✅ Complete:

Tracking issue: stellar-registry/ui#51 (context; closed October 7 once
every sub-issue was complete; the delivery is the merged PRs below). A new Governance section on
rgstry.xyz hosts one form per operation. On testnet, a form builds the on-chain outcome transaction,
pins proposal.md to IPFS, and creates a Tansu proposal signed with the user's wallet. On mainnet,
the form opens a prefilled issue in https://github.com/stellar-registry/gov.

🟩 D7: Registry Documentation & Education (carried from Q2)

Description from last quarter:

Publish the Registry docs site and video series covering publishing a Wasm, deploying named and
unnamed contracts, using import_contract!, and publishing/releasing via the verified-build CI
workflow.

Proof: documentation live on the Registry docs site and videos on The Aha Company's YouTube
channel.

✅ Complete:

⚠️ Pending:

✅ D8: Support named G-addresses

Description from last quarter:

Just as Registry today allows giving names to Wasms and Contracts, expand it to also allow giving
names to G-addresses. These will be displayed in the rgstry.xyz UI, so that the "Deployer" and
"Admin" fields become human-friendly names.

Value to ecosystem: a central, open, and collaborative system to add human-friendly names to
G-addresses will allow other Stellar tools such as Stellar.Expert to also show friendly names,
making the entire ecosystem more usable by existing participants and more welcoming to newcomers.

Proof: code shipped; address system available, documented, and advertised to the community; more
than just Aha addresses added and available.

✅ Complete:

Scope was narrowed during Q3 to foundational contract-level support; see tracking issue
stellar-registry/cli#51 (context; closed after the quarter, with remaining
G-address work moving to new Q4 issues; the delivery is the merged PRs below).

Displaying names in the rgstry.xyz UI (e.g. "Deployer" and "Admin" fields), CLI support,
documentation and community outreach, and onboarding non-Aha addresses will be proposed as Q4 work.

✅ D9: Surface emerging Source Verification information

Description from last quarter:

The Registry team submitted a
proposal for the Source Verification system RFP.
Whether or not our team is awarded this contract, Q3 will see the finalization of underlying SEP-58
and the launch of independent Source Verification services. Registry is a natural place to surface
and organize this information and make it useful to the ecosystem.

Value to ecosystem: As the hub that makes Wasms on Stellar discoverable and reusable, Registry is a
natural place to surface the Wasm metadata added by SEP-58. Registry is also not a source
verification service, but a neutral third party that hosts the information provided by many source
verification services. A lot of information is being added to the blockchain by this new standard,
and Registry gives everyone a way to view and make sense of this information.

Proof: all SEP-58 fields viewable on rgstry.xyz; verification status of those fields by independent
Source Verification services also shown in a way that exposes, rather than flattens, disagreement.

✅ Complete:

⚠️ Pending:

  • Registry could do more! New 3rd-party, off-chain Build Verification Services never got in touch to
    update Registry with their build-verification information.

✅ D10: guide Tansu evolution to support Registry needs

Description from last quarter:

Harnessing Tansu for Registry's governance required significant effort and an unsatisfying
technical workaround (see above discussion of Tansu-DAO-gated registry manager). We will
collaborate with the Tansu team to guide Tansu's evolution, either obsolescing this workaround or
sculpting it into a more general and generally-usable shape.

Value to ecosystem: whether for security guarantees as in the case of Registry, or just for open &
participatory governance of open-source projects, on-chain governance provides a crucial role to
any blockchain ecosystem. Registry's partnership with Tansu ensures the maturity of this solution
for all community projects.

Proof:
Registry Tansu Manager contract
either migrates out of the stellar-registry repository to Tansu, becoming easier to use for all
ecosystem projects, or becomes altogether unnecessary.

✅ Complete:

✅ D11: Registry GH Workflow to publish Wasms and upgrade contracts

Description from last quarter:

Wrap the
stellar-expert/soroban-build-workflow
and add Registry-specific things:

  • build with stellar scaffold build instead of stellar contract build to ensure inter-contract
    dependency build order correctness
  • when already-published Wasms are updated with new versions, publish these new versions to
    Registry

We are intentionally leaving contract upgrades as future work, as this gets into the thorny issue
of migrations. It is best to leave contract upgrades as a manual task until tooling around
migrations has matured.

This task requires research into how to securely provision keys which only have permission to
invoke publish on the registry and can be stored in a GitHub workflow and which do not have risky
privilege levels.

Proof: new repository available at, say, stellar-registry/gh-build-workflow. Documented and
tested in production with the Registry wasm itself.

✅ Complete:

✅ D12: UI: Expose full contract version history

Description from last quarter:

The Registry API
now exposes full version history,
which notably extends into the full history of the blockchain, beyond the launch of the Registry
contract itself. This information is not yet exposed
in the rgstry.xyz UI. This deliverable addresses
that mismatch.

Value to ecosystem: making contract upgrades easy to find and analyze aids in troubleshooting and
full-blockchain comprehensibility.

Proof: Contract detail pages on rgstry.xyz/contracts
display information about full contract history.

✅ Complete:

🟩 D13: Documentation consolidation & redesign; potential migration of rgstry.xyz

Description from last quarter:

Implement new logo and design elements, secured in Q2, across rgstry.xyz site and other Registry
properties such as GitHub. Organize videos created as part of D7 into landing page and other
relevant locations throughout rgstry.xyz.

Discuss with ecosystem partners and SDF potential for a new domain for Registry: rgstry.xyz was
never intended to be permanent. Registry could live under an SDF-owned domain, such as
registry.stellar.org. This, in turn, may require frontend redesign, swapping current
subdomain-based network specification (testnet.rgstry.xyz / stellar.rgstry.xyz) for URL-based
specification. Depending on scope, the actual implementation of any such plan may be a Q4 concern.

Value to ecosystem: consolidates Registry documentation to a single, searchable place, making it
simple to onboard and make the most of Registry.

Proof: redesigned site live, videos highlighted throughout, and question of domain's permanent home
settled with decision documented and justified.

✅ Complete:

⚠️ Pending:

  • domain move discussion: no public link. History of discussion:

    • @chadoh raised the issue in a thread within
      SDF Slack;
      no one responded
    • @chadoh to raise again in Stellar Community Call when presenting Registry (see
      D7)

✅ D14: Extend import_contract! macro to support SAC and XLM

Description from last quarter:

Currently it is difficult to work with Stellar Asset Contracts, you need to know the asset encoding
or provide the contract Id. Furthermore, writing unit tests which use SACs, particularly the native
xlm asset, are difficult. We have previous work which helped this and is our
guess the number contract.
The other big improvement is for testing on a standalone network. Currently the xlm SAC isn't
deployed by default on standalone quickstart image, this work would make this happen lazily on a
contract's deployment.

Value to ecosystem: make it fun and easy for new developers to use and test SAC assets, especially
the native.

Proof: published macro which can detect if a contract is a stellar asset contract and generate the
required code to make using and testing the asset easy.

Note that import_asset! was already available and reasonable as an alternative at the end of Q2.
The goal here is to ensure that import_contract!(xlm) and similar (such as
import_contract!("circle/usdc")) work as-expected, so that users have a choice between
import_asset! and import_contract!, where import_contract! alternative works for any SAC
registered in stellar.rgstry.xyz.

✅ Complete:

✅ D15: Verified Build Integration with Stellar Expert

This is copied from D6 in Q2, as outlined in the
Q3 Proposal discussion.
It was not hard-committed in the Tansu vote, but was soft-committed in the linked discussion.

Description from Q2:

Display verified build status from Stellar Expert's API on Registry Wasm and Contract detail pages.

Measure: the verified build badge or indicator is visible on at least one Wasm detail page with a
known verified contract, and the integration is live in production on rgstry.xyz.

Extra details from
Q3 Proposal discussion:

There was some real confusion amongst our team about the goal here. The initial Q2 D6 milestone was
about helping our users implement the Verified Build workflow from Stellar Expert. In our write-up
of what we did in the quarter, we instead referenced our own use of the Stellar Expert verified
build workflow.

While this served as useful research for how to help our users, it did not satisfy the original
task. D6 should have also been marked as a carry-over for Q3.

In addition, in our "completion notes" for D6, we stated that we were targeting contract pages,
"since we established Stellar Expert has no Wasm-level pages." We've changed our thinking on this,
as documented in a new issue, stellar-registry/ui#38. This is a sub-issue of our original tracking
issue stellar-registry/cli#35, which we will continue to use as our tracking issue for Q3.

✅ Complete:

2026 Q4

⏳ D1: Help Community Projects Use Registry Internally

Description:

Work intensively with at least two key partners to onboard their projects to Registry, specifically
focusing on improvements to their toolchains and processes. This deliverable is about getting
partners to use Registry in their own workflows. Along the way, we will discover Registry gotchas,
improving the product to accelerate further rollout.

Possible partners & projects: XOXNO, Reflector (Orbitlens), Stellar Broker (Orbitlens), Crossmint
(Overcat), Rozo (Shawn), LiFi, Soroswap (Palta Labs / Esteblock).

Value to ecosystem: more teams are saving time by using Registry and their contracts and Wasms are
easier to find & use for the rest of the ecosystem.

Issue:

Proof:

  • Merged PRs to integrate Registry into their codebases/workflows
  • Partner teams' contracts & Wasms exist on Registry and are owned by their teams' accounts

⚠️ Pending:

⏳ D2: Help Community Projects Show Registry Info

Description:

Starting with Stellar.Expert, we'll help community partners display Registry info, turning opaque
hashes and IDs into human-friendly names.

Value to ecosystem: in the systems that people are already relying on, contracts and Wasms are
identified by human-friendly names and versions, rather than opaque hashes and IDs.

Issues:

Proof:

  • Linked issue closed with implementing PR
  • Registry info displays on Stellar.Expert when available

✅ Complete:

⚠️ Pending:

⏳ D3: Developer outreach & education

Description:

We will continue to present and teach about Registry at Stellar community events and support other
teams who do the same.

Value to ecosystem: help people learn about and onboard to Registry.

Issues:

Proof: links to recorded videos or event links

✅ Complete:

⚠️ Pending:

⏳ D4: Smart account support in the account namespace

Description:

The account namespace shipped in Q3 only accepts classic G-addresses: register_account rejects
contract addresses with NotAccountAddress. Smart wallets such as
Nido (passkey-based) are contract accounts (C-addresses), so their
users can't get a name today.

Issues:

Value to ecosystem: one naming system for every kind of Stellar account, so passkey and other
smart-wallet users get the same human-readable names as classic accounts.

Proof: registry contract released with smart-account support; at least one Nido wallet registered
under a name and resolvable on rgstry.xyz and from the CLI.

✅ Complete:

⚠️ Pending:

⏳ D5: Named G-addresses, from contract to ecosystem (follow-on from Q3 D8)

Description:

Q3 shipped named G-address support in the registry contract (stellar-registry/contracts#37,
stellar-registry/contracts#38). Make it usable and adopted.

This follows D4 intentionally: either style of named account (whether backed by a G-address or a
smart account C-address) must be supported in all situations.

Issues:

Value to ecosystem: human-readable names for accounts, not only contracts & Wasms; reduce
copy-paste mistakes and make on-chain activity legible.

Proof: names shown on rgstry.xyz and resolvable from the CLI; docs published and announced; named
addresses registered by at least one team other than Aha; SEP draft or discussion linked.

✅ Complete:

⚠️ Pending:

✅ D6: Simplify import_contract! testing

Description:

import_contract! works well on testnet and mainnet, but local development and unit tests need a
registry with the depended-on contracts already registered, which each team has to set up
themselves. Build the workaround from stellar-registry/cli#64 into the library

Issue:

Value to ecosystem: teams adopting import_contract! get a working dev and test setup without
retracing our steps.

Proof: linked issue address with a PR using a newly-cut release of stellar-registry crate

✅ Complete:

Tracking issue stellar-registry/cli#65 closed November 11 once its
component PRs merged.

⏳ D7: Contract Details UI Revamp

Description:

The amount of information shown on Contract Details pages has grown, and it's starting to feel
cluttered. Let's clean it up and prioritize what's important.

Issue:

⚠️ Pending:

⏳ D8: Fix core deploy workflow when using Secure Store

Description:

When following security best practices, keeping secret keys and seed phrases off the file system
and instead using macOS Secure Store or a hardware wallet like Ledger, the Registry CLI falls
victim to an upstream Stellar CLI bug.

Issue:

Value to ecosystem: No longer force users into clumsy and potentially insecure workarounds for core
Registry CLI workflows.

Proof: Issues and PRs created in https://github.com/stellar/stellar-cli, and communications sent
to Stellar CLI via our shared Slack channel to attempt to secure a review of these issues & PRs.

⚠️ Pending:

⏳ D9: stellar-registry/actions maturation & adoption

Description:

Q3's D11 saw us add automatic Wasm publishing to Registry via GitHub Workflow, added to Registry's
own Wasm in stellar-registry/contracts#53. In Q4 we add contract upgrades to the core actions
workflow, add more discerning Mainnet publish pathway, and adopt these workflows in all
Aha-maintained projects. Along the way, we turn any rough edges or tooling/documentation gaps into
new issues or PRs.

Issues:

Value to ecosystem: maturation of stellar-registry/actions ahead of Q1 rollout to partner teams
and broader ecosystem; simplified & automatic best-practices publishing of Wasms with associated
contract upgrades for all projects that adopt the workflow.

Proof:

  • Issues closed with implementing PRs
  • Successful workflow runs on linked Aha repos

✅ Complete:

⚠️ Pending:

Proposed Impact

Overarching Q4 story: Registry is ready, now drive adoption.

Q3 saw Registry become a sophisticated product offering huge productivity gains to any team that
adopts it. And: the more everyone adopts it, the more everyone benefits. In Q4 we accelerate those
gains.

We'll also ship the stuff early adopters have already asked for.

Proposed Deliverables

D1: Help Community Projects Use Registry Internally

Work intensively with at least two key partners to onboard their projects to Registry, specifically
focusing on improvements to their toolchains and processes. This deliverable is about getting
partners to use Registry in their own workflows. Along the way, we will discover Registry gotchas,
improving the product to accelerate further rollout.

Possible partners & projects: XOXNO, Reflector (Orbitlens), Stellar Broker (Orbitlens), Crossmint
(Overcat), Rozo (Shawn), LiFi, Soroswap (Palta Labs / Esteblock).

Value to ecosystem: more teams are saving time by using Registry and their contracts and Wasms are
easier to find & use for the rest of the ecosystem.

Issue:

Proof:

  • Merged PRs to integrate Registry into their codebases/workflows
  • Partner teams' contracts & Wasms exist on Registry and are owned by their teams' accounts

D2: Help Community Projects Show Registry Info

Starting with Stellar.Expert, we'll help community partners display Registry info, turning opaque
hashes and IDs into human-friendly names.

Value to ecosystem: in the systems that people are already relying on, contracts and Wasms are
identified by human-friendly names and versions, rather than opaque hashes and IDs.

Issues:

Proof:

  • Linked issue closed with implementing PR
  • Registry info displays on Stellar.Expert when available

D3: Developer outreach & education

We will continue to present and teach about Registry at Stellar community events and support other
teams who do the same.

Value to ecosystem: help people learn about and onboard to Registry.

Issues:

Proof: links to recorded videos or event links

D4: Smart account support in the account namespace

The account namespace shipped in Q3 only accepts classic G-addresses: register_account rejects
contract addresses with NotAccountAddress. Smart wallets such as Nido
(passkey-based) are contract accounts (C-addresses), so their users can't get a name today.

Issues:

Value to ecosystem: one naming system for every kind of Stellar account, so passkey and other
smart-wallet users get the same human-readable names as classic accounts.

Proof: registry contract released with smart-account support; at least one Nido wallet registered
under a name and resolvable on rgstry.xyz and from the CLI.

D5: Named G-addresses, from contract to ecosystem (follow-on from Q3 D8)

Q3 shipped named G-address support in the registry contract (stellar-registry/contracts#37,
stellar-registry/contracts#38). Make it usable and adopted.

This follows D4 intentionally: either style of named account (whether backed by a G-address or a
smart account C-address) must be supported in all situations.

Issues:

Value to ecosystem: human-readable names for accounts, not only contracts & Wasms; reduce copy-paste
mistakes and make on-chain activity legible.

Proof: names shown on rgstry.xyz and resolvable from the CLI; docs published and announced; named
addresses registered by at least one team other than Aha; SEP draft or discussion linked.

D6: Simplify import_contract! testing

import_contract! works well on testnet and mainnet, but local development and unit tests need a
registry with the depended-on contracts already registered, which each team has to set up themselves.
Build the workaround from stellar-registry/cli#64 into the library

Issue:

Value to ecosystem: teams adopting import_contract! get a working dev and test setup without
retracing our steps.

Proof: linked issue address with a PR using a newly-cut release of stellar-registry crate

D7: Contract Details UI Revamp

The amount of information shown on Contract Details pages has grown, and it's starting to feel
cluttered. Let's clean it up and prioritize what's important.

Issue:

D8: Fix core deploy workflow when using Secure Store

When following security best practices, keeping secret keys and seed phrases off the file system and
instead using macOS Secure Store or a hardware wallet like Ledger, the Registry CLI falls victim to
an upstream Stellar CLI bug.

Issue:

Value to ecosystem: No longer force users into clumsy and potentially insecure workarounds for core
Registry CLI workflows.

Proof: Issues and PRs created in https://github.com/stellar/stellar-cli, and communications sent to
Stellar CLI via our shared Slack channel to attempt to secure a review of these issues & PRs.

D9: stellar-registry/actions maturation & adoption

Q3's D11 saw us add automatic Wasm publishing to Registry via GitHub Workflow, added to Registry's
own Wasm in stellar-registry/contracts#53. In Q4 we add contract upgrades to the core actions
workflow, add more discerning Mainnet publish pathway, and adopt these workflows in all
Aha-maintained projects. Along the way, we turn any rough edges or tooling/documentation gaps into
new issues or PRs.

Issues:

Value to ecosystem: maturation of stellar-registry/actions ahead of Q1 rollout to partner teams and
broader ecosystem; simplified & automatic best-practices publishing of Wasms with associated contract
upgrades for all projects that adopt the workflow.

Proof:

  • Issues closed with implementing PRs
  • Successful workflow runs on linked Aha repos

pselle and others added 10 commits November 2, 2026 14:06
@pselle @claude
registry: 2026 Q4 deliverables status (in progress)
5a50722 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: drop Q4 work-in-progress note
873e8a4 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: label Q4 descriptions plainly
b47f2bf 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: correct Q4 status after self-review
e670b70 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: update Q4 D4/D5 status (indexer#56 merged, testnet upgrades)
55a64b6 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: Q4 D5 status, indexer#60 live on testnet
5b44df2 
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pselle @claude
registry: Q4 D3 HackMeridian talk recording
cd36e8f 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: Q4 D6 status, cli#77 merged
a10d54c 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: mark partially complete Q4 deliverables pending
83013db 
Co-Authored-By: Claude <noreply@anthropic.com>
@pselle @claude
registry: Q4 D6 complete
7854e50 
Co-Authored-By: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@pselle