From 0ea769b5b3dcd64b35d5b1ae37281118ff4e4c30 Mon Sep 17 00:00:00 2001 From: Willem Wyndham Date: Mon, 6 Jul 2026 13:16:48 -0400 Subject: [PATCH 01/26] PG Award Proposal: Stellar Registry (2026Q3) Q3 renewal: Q2 retroactive impact and deliverable evidence, Q3 goals. Co-Authored-By: Claude Fable 5 --- docs/projects/stellar-registry.md | 355 +++++++++++++++++++++++------- 1 file changed, 274 insertions(+), 81 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 5398a15..8c90c5c 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -21,7 +21,7 @@ the ecosystem like packages._ | -------------------- | -------------------------------------------------------------------------------------------------- | | **Category** | Developer Experience | | **Website** | | -| **Repository** | | +| **Repository** | | | **First Released** | March 2026 | | **Intake** | | | **Budget Requested** | 50000 | @@ -120,14 +120,50 @@ what developers expect from modern, full-stack tooling. -Stellar Registry launched within the last three months on Testnet, and has already garnered -significant interest from ecosystem partners/projects such as PG Atlas and the SDF DevRel team for -multiple hackathons. These users provided valuable insight to the scope and workflow of the initial -prototype deployed to testnet. - -We also held discussion with ecosystem partners and SDF team members on the formation and governance -structure of the Security Council, providing a roadmap of requirements for further improvements of -Registry. +In Q2 2026 the Registry grew from a testnet prototype into a production-shaped system with its own +organization, on-chain governance, verified builds, and a real data platform behind rgstry.xyz. + +**Registry became standalone infrastructure.** The Registry was split out of the +theahaco/scaffold-stellar monorepo into its own GitHub organization, +[github.com/stellar-registry](https://github.com/stellar-registry), with four repos — `cli`, +`contracts`, `ui`, and `indexer` — each with full history preserved, scoped CI, dependabot, and +rewritten documentation. The Registry now stands on its own, as promised in our Q2 proposal ("the +Registry stands independently and is designed to serve the entire Soroban developer community"). + +**Five on-chain registry releases.** Registry contract versions v0.5.0 through v0.6.2 shipped in +April, adding contract flagging with a gas-optimized storage encoding (unflagged entries pay zero +overhead on the hot invocation path), `SubRegistry` events, cross-registry deploys +(`deploy_with_subregistry`) that record provenance on Deploy events, deterministic salt-derived +contract IDs, and dry-run deploy options. + +**On-chain governance shipped.** The Tansu-DAO-gated registry manager contract merged +(stellar-registry/contracts#5): a manager whose `trigger(proposal_id)` entry point executes an +approved Tansu DAO proposal (e.g. `registry.publish_hash` / `registry.deploy`) in a single +transaction. Verified live end-to-end on testnet: proposal → vote → trigger → publish, with +replay-guard rejection confirmed. + +**Verified builds are live.** We adopted the stellar-expert/soroban-build-workflow for releases +(stellar-registry/contracts#10), replacing 243 lines of bespoke CI with environment-gated, OIDC +build-provenance-attested releases, and published the first verified build of the registry contract. +We also submitted a Contract Source Verification Service RFP to the SCF Build Award RFP track and +collaborated with Ethan Frey (Confio) on its technical architecture. + +**The indexer went v1.** The first mainnet-ready pipeline & API (stellar-registry/indexer#5) moved +data into a versioned schema, added auto-discovery of named subregistries (oz, blend, soroswap, +defindex), and grew an archive pipeline exposing full per-contract version history +(stellar-registry/indexer#14). June added structured logging with request-id tracing and a trigram +index enabling fuzzy server-side search (stellar-registry/indexer#23). + +**rgstry.xyz matured.** The UI gained a testnet/mainnet network switch with per-environment +Cloudflare Worker deploys, in-UI usage guides for the import macros, README/LICENSE rendering from a +contract's GitHub repo, contract metadata on detail pages, server-side search, and request-id-traced +error reporting — 18 merged PRs in the quarter. + +**Releases and toolchain.** Crates published: `stellar-registry` v0.0.8–v0.0.10, +`stellar-registry-cli` v0.0.20/v0.0.21, `stellar-registry-build` v0.0.8. The contracts moved to +soroban-sdk v27 / stellar-cli v27 (stellar-registry/contracts#11); the CLI's v27 migration is in +review (stellar-registry/cli#13). Registry intake forms are now CI-validated with strkey, sha256, and +semver validators and IssueOps labeling. @@ -135,16 +171,181 @@ Registry. -### D1. Registry UI (beta) shipped and publicly deployed +### 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 progress: + +- https://github.com/stellar-registry/contracts/pull/14 — phased, dry-run-by-default + `deploy_mainnet.sh` plus verified mainnet seed data (circle, soroswap, blend, defindex, xlm), with + every contract ID resolved from authoritative sources and confirmed live on Pubnet +- https://github.com/stellar-registry/indexer/pull/5 — "the first mainnet-ready pipeline & API" +- https://github.com/stellar-registry/ui/pull/1 — testnet/mainnet network switch and per-environment + Cloudflare Worker deploys; Mainnet UI scaffolding at stellar.rgstry.xyz + +**Not completed.** The mainnet deploy machinery (deploy script, verified seed data, mainnet-ready +indexer, multi-network UI) was built this quarter, but the contract is not yet deployed to mainnet. +One blocker is being fixed first: `stellar registry deploy` cannot yet sign with secure-store or +Ledger keys (stellar-registry/cli#14), and we will not deploy permanent mainnet infrastructure from a +raw secret key. This deliverable carries into Q3 as our top priority. + +### 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 progress: -> - Deliver a frontend for exploring and consuming contracts (search/browse, contract pages, -> provenance/metadata, usage instructions). -> - Measure: UI deployed to a public URL + documented usage flows. -> - Issue: https://github.com/theahaco/scaffold-stellar/issues/169 -> - Ecosystem value: makes contract discovery and reuse real for app developers; reduces repeated -> reinventing of standard components. +- https://github.com/stellar-registry/cli/pull/17 — full implementation: a proc-macro crate where + `stellar_registry::import_contract!(env, name)` returns a soroban Client pre-bound to the named + contract's deployed address, resolved at build time, with 13 unit tests +- https://github.com/stellar-registry/ui/pull/6 — in-UI usage guides for the import macros +- https://github.com/stellar-registry/ui/pull/10 — real contract IDs in the macro examples shown on + every contract page -Testnet Registry frontend is live at https://testnet.rgstry.xyz/ +**Mostly complete.** The macro is implemented, tested, and in review, and rgstry.xyz already teaches +developers how to use the import macros on every contract page. The crates.io release lands early 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: + +- https://github.com/stellar-registry/contracts/commit/de06277 — on-chain contract flagging with a + gas-optimized storage encoding (flag encoded in vec length, so unflagged entries pay zero overhead + on the hot path), `FlagContract` events, and error types +- https://github.com/stellar-registry/cli/commit/1413f7f — registry intake CI validation (strkey, + sha256, semver validators with IssueOps labeling), the curation pipeline enforcement sits on + +**Partially complete.** The on-chain half (flag storage, events, errors) shipped in April. The +build-time half — making the import macros fail compilation for flagged entries — was deliberately +sequenced behind the `import_contract!` implementation (D2) and carries into Q3. + +### 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 progress: + +- https://github.com/stellar-registry/indexer/pull/23 — trigram index enabling fuzzy server-side + search +- https://github.com/stellar-registry/ui/pull/21 — wasm list wired to the backend search API with a + debounced search hook +- https://github.com/stellar-registry/indexer/pull/24 — (open) extends trigram/full-text search to + the contracts table + +**Partially complete.** Server-side fuzzy search is merged and live in production for Wasms, and the +API already supports limit/cursor pagination; contract search (stellar-registry/indexer#24), the +pagination/sorting UX in the explorer, and validation against a 1,000+ entry dataset carry into Q3. + +### 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 progress: + +- https://github.com/stellar-registry/indexer/pull/15 — `stellar contract info meta` metadata parsed + and exposed in the wasm-detail API (item 2, backend half — the API serves rsver, SDK, CLI, and + build versions plus source repo) +- https://github.com/stellar-registry/ui/pull/13 — README.md and LICENSE fetched and rendered from a + contract's GitHub repo +- https://github.com/stellar-registry/ui/pull/18 — request-id-traced error reporting + +**Partially complete.** The backend half of metadata surfacing (item 2) shipped — the UI currently +renders the source-repo link, with the remaining metadata fields still to surface — plus unplanned +page-richness work (README/LICENSE rendering). The embedded Contract Explorer (item 1) and the +"deploy this Wasm" button (item 3) carry into Q3; the deploy button now has a clearer path via the +governance proposal forms in stellar-registry/ui#16. + +### 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 progress: + +- https://github.com/stellar-registry/contracts/pull/10 — releases now use the + stellar-expert/soroban-build-workflow: environment-gated, with OIDC build-provenance attestation +- https://github.com/stellar-registry/contracts/releases — first verified build of the registry + contract published +- https://github.com/stellar-registry/cli/pull/9 — Contract Source Verification Service RFP submitted + to the SCF Build Award RFP track, with architecture collaboration from Ethan Frey (Confio) + (stellar-registry/cli#11, #12) + +**Partially complete.** The produce side is done — Registry releases are themselves verified builds +attested to Stellar Expert. The display side (badge on rgstry.xyz detail pages) carries into Q3; we +learned along the way that Stellar Expert has no Wasm-level pages (stellar-registry/ui#17), so the +badge work targets contract pages. + +### 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 progress: + +- https://scaffoldstellar.org/docs/registry — the Registry Guide is live (overview, + verified/unverified registries, name resolution, publish/deploy CLI usage) and linked as "Guide" + from the rgstry.xyz nav +- https://github.com/stellar-registry/ui/pull/6 — in-UI usage guides for the import macros, shown on + every contract and wasm page +- https://github.com/stellar-registry/cli — README and contributor docs rewritten for the standalone + repo (likewise for contracts, ui, and indexer) +- https://github.com/stellar-registry/cli/pull/17 — design spec and implementation plan documents for + `import_contract!` + +**Partially complete.** Documentation moved into the product (usage guides on every registry page, +the Registry Guide linked from the site) and into the four standalone repos. The measure specified +Registry's own docs site and videos: the guide currently lives on the Scaffold Stellar docs site, +`import_contract!` coverage awaits the D2 release, and the video series did not ship — these carry +into Q3. @@ -152,33 +353,27 @@ Testnet Registry frontend is live at https://testnet.rgstry.xyz/ -**Make the Registry production-ready.** Deploying to mainnet (theahaco/scaffold-stellar#433) -transforms the Registry from a testnet experiment into permanent Stellar infrastructure — a shared, -on-chain contract store that any Soroban developer or dApp can publish to and consume from. Provide a -migration path from beta users to production-ready service. - -**Make contract composability ergonomic.** The `import_contract!` macro -(theahaco/scaffold-stellar#419) and its build-time safety enforcement (theahaco/scaffold-stellar#452) -mean that any Soroban developer can depend on Registry contracts the way they depend on Rust crates — -with a clean API and compile-time guarantees that flagged or compromised contracts won't ship. +**Launch on mainnet.** Q2 built every piece of the mainnet machinery: a phased deploy script with +verified seed data (stellar-registry/contracts#14), a mainnet-ready indexer pipeline, a multi-network +UI, and — critically — the security posture to do it right: DAO-gated registry governance via Tansu +and secure-store/Ledger signing (stellar-registry/cli#14) so permanent ecosystem infrastructure is +never operated from a raw secret key. Q3 turns the key: the Registry contract live on Pubnet, +governed on-chain, indexed, and browsable at rgstry.xyz. -**Make the Registry discoverable and usable without the CLI.** Through search, pagination, UI -enhancements, verified build integration, and human-readable addresses -(theahaco/scaffold-stellar#454, theahaco/scaffold-stellar#453, theahaco/scaffold-stellar#455, -theahaco/scaffold-stellar#421), `rgstry.xyz` becomes a real contract discovery platform — not just a -read-only dashboard — so developers can find, evaluate, and deploy contracts directly from the -browser. +**Complete the composability story.** Releasing `import_contract!` (stellar-registry/cli#17) lets any +Soroban developer depend on Registry contracts the way they depend on Rust crates, and the +flagged-contract build-time enforcement extends that with compile-time guarantees that compromised +contracts won't ship. -**Lower the barrier to entry.** Targeted Registry documentation (theahaco/scaffold-stellar#426), -cross-linked with Scaffold Stellar's docs, ensures developers arriving from any direction — the CLI, -the web explorer, or Scaffold Stellar — can get productive with the Registry quickly. +**Make rgstry.xyz a real discovery platform.** Finish server-side search across contracts and Wasms, +pagination and sorting, verified-build badges from Stellar Expert, and governance proposal forms that +let anyone propose adding a Wasm or contract to the root registry directly from the browser — closing +the loop from "found a contract" to "deployed it" without leaving the site. **Benefit to the Stellar ecosystem:** The Registry is ecosystem infrastructure, not a product -feature. Every Soroban project benefits from a trustworthy, searchable, mainnet-deployed contract -store. It enables contract reuse, reduces duplicated effort across teams, and raises the baseline -security and auditability of the ecosystem. Scaffold Stellar remains the recommended starting point -for building on top of the Registry, but the Registry stands independently and is designed to serve -the entire Soroban developer community. +feature. A mainnet Registry with DAO governance, verified builds, and compile-time safety raises the +baseline security and auditability of every Soroban project that consumes shared contracts, and gives +the ecosystem its first crates.io-style package experience for on-chain code. @@ -186,67 +381,65 @@ the entire Soroban developer community. -## D1: Mainnet Deploy of Stellar Registry (theahaco/scaffold-stellar#433) - -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. +### D1: Mainnet Launch of Stellar Registry (carried from Q2) -## D2: `import_contract!` Macro (theahaco/scaffold-stellar#419) +Deploy the Registry contract and seed data to mainnet via the phased deploy pipeline +(stellar-registry/contracts#14), with secure-store/Ledger signing support in the CLI +(stellar-registry/cli#14) so the deploy and admin operations never expose a raw secret key. Point the +CLI and rgstry.xyz at the mainnet contract and remove the "Coming Soon" banner. -Publish a working `import_contract!` macro in the `stellar-registry` crate that allows cross-contract -client instantiation with a single line of Rust. +Proof: the mainnet contract ID published in the docs, visible on Stellar Expert, resolvable via +`stellar registry` CLI, and browsable at rgstry.xyz. -Measure: the macro is available in a released crate version, documented with at least one working -example, and covered by integration tests. +### D2: Release `import_contract!` (carried from Q2) -## D3: Flagged Contract Enforcement at Build Time (theahaco/scaffold-stellar#452) +Merge stellar-registry/cli#17 and publish the macro in released crates, documented with at least one +working example and covered by integration tests. -Extend `import_contract!` and `import_contract_client!` to emit a compile-time error when the -referenced Wasm or Contract is flagged in the Registry. +Proof: a crates.io release containing `import_contract!`, linked docs and example, CI running the +integration tests. -Measure: a test exists that demonstrates a flagged contract causes a build failure, and the behavior -is documented. +### D3: Flagged Contract Enforcement at Build Time (carried from Q2) -## D4: Server-Side Search, Pagination & Sorting on rgstry.xyz (theahaco/scaffold-stellar#454) +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. -Replace the current client-side full-data-fetch approach with API-backed search, pagination, and -sorting on `rgstry.xyz`. +Proof: a test demonstrating a flagged contract causes a build failure, and documented behavior. -Measure: the explorer handles at least 1,000 published Wasms/Contracts without degraded load time, -search returns results server-side, and pages load incrementally. +### D4: Finish Search, Pagination & Sorting on rgstry.xyz (carried from Q2) -## D5: rgstry.xyz UI Enhancements (theahaco/scaffold-stellar#453) +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. -Ship three specific improvements to the Registry web explorer: +Proof: live on rgstry.xyz; search, pagination, and sorting demonstrated against a 1,000+ entry +dataset. -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 +### D5: Contract Explorer, Deploy Button & Verified-Build Badges (carried from Q2) -Measure: all three features are live on the production `rgstry.xyz` site and manually verified -against at least one mainnet contract. +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. -## D6: Verified Build Integration with Stellar Expert (theahaco/scaffold-stellar#455) +Proof: all features live on production rgstry.xyz, manually verified against at least one mainnet +contract. -Display verified build status from Stellar Expert's API on Registry Wasm and Contract detail pages. +### D6: Governance Operations UI -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`. +Ship the governance proposal forms (stellar-registry/ui#16): 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. -## D7: Registry Documentation & Education (theahaco/scaffold-stellar#426) +Proof: a governance proposal created from rgstry.xyz, voted on in Tansu, and executed on-chain via +`trigger`, with the transaction linked. -Publish complete Registry documentation and videos covering: +### D7: Registry Documentation & Education (carried from Q2) -- publishing a Wasm -- deploying a named contract -- using `import_contract!` -- deploying an unnamed contract -- publishing/releasing using CI workflow -- more! +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. -Measure: documentation is live on Registry's own docs site & The Aha Company's YouTube channel. +Proof: documentation live on the Registry docs site and videos on The Aha Company's YouTube channel. From c9c180920164938b72f4508b06a5682bbdf4725f Mon Sep 17 00:00:00 2001 From: Willem Wyndham Date: Mon, 6 Jul 2026 14:31:26 -0400 Subject: [PATCH 02/26] Reframe past deliverables: lead with shipped work Per team feedback: each deliverable now opens with what shipped and names exactly what remains; adds "Beyond the proposal" section for unproposed infrastructure wins. Co-Authored-By: Claude Fable 5 --- docs/projects/stellar-registry.md | 88 ++++++++++++++++++++----------- 1 file changed, 56 insertions(+), 32 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 8c90c5c..da6e655 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -171,6 +171,10 @@ semver validators and IssueOps labeling. +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: @@ -189,11 +193,11 @@ Proof of progress: - https://github.com/stellar-registry/ui/pull/1 — testnet/mainnet network switch and per-environment Cloudflare Worker deploys; Mainnet UI scaffolding at stellar.rgstry.xyz -**Not completed.** The mainnet deploy machinery (deploy script, verified seed data, mainnet-ready -indexer, multi-network UI) was built this quarter, but the contract is not yet deployed to mainnet. -One blocker is being fixed first: `stellar registry deploy` cannot yet sign with secure-store or -Ledger keys (stellar-registry/cli#14), and we will not deploy permanent mainnet infrastructure from a -raw secret key. This deliverable carries into Q3 as our top priority. +**All launch machinery built and verified.** The phased deploy script with mainnet seed data (every +contract ID resolved from authoritative sources and confirmed live on Pubnet), the mainnet-ready +indexer pipeline, and the multi-network UI are all in place. The deploy itself is intentionally gated +on secure-store/Ledger signing (stellar-registry/cli#14): we will not operate permanent ecosystem +infrastructure from a raw secret key. Flipping the switch is the first Q3 deliverable. ### D2. `import_contract!` Macro @@ -205,7 +209,7 @@ Description from last quarter: > Measure: the macro is available in a released crate version, documented with at least one working > example, and covered by integration tests. -Proof of progress: +Proof of completion: - https://github.com/stellar-registry/cli/pull/17 — full implementation: a proc-macro crate where `stellar_registry::import_contract!(env, name)` returns a soroban Client pre-bound to the named @@ -214,8 +218,9 @@ Proof of progress: - https://github.com/stellar-registry/ui/pull/10 — real contract IDs in the macro examples shown on every contract page -**Mostly complete.** The macro is implemented, tested, and in review, and rgstry.xyz already teaches -developers how to use the import macros on every contract page. The crates.io release lands early Q3. +**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 @@ -235,9 +240,9 @@ Proof of progress: - https://github.com/stellar-registry/cli/commit/1413f7f — registry intake CI validation (strkey, sha256, semver validators with IssueOps labeling), the curation pipeline enforcement sits on -**Partially complete.** The on-chain half (flag storage, events, errors) shipped in April. The -build-time half — making the import macros fail compilation for flagged entries — was deliberately -sequenced behind the `import_contract!` implementation (D2) and carries into Q3. +**On-chain half shipped; compile-time half sequenced by design.** Flag storage, `FlagContract` +events, and error types shipped in April. The build-time check extends `import_contract!` (D2), so it +was deliberately sequenced behind that macro's implementation and follows it in early Q3. ### D4. Server-Side Search, Pagination & Sorting on rgstry.xyz @@ -249,7 +254,7 @@ Description from last quarter: > 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 progress: +Proof of completion: - https://github.com/stellar-registry/indexer/pull/23 — trigram index enabling fuzzy server-side search @@ -258,9 +263,10 @@ Proof of progress: - https://github.com/stellar-registry/indexer/pull/24 — (open) extends trigram/full-text search to the contracts table -**Partially complete.** Server-side fuzzy search is merged and live in production for Wasms, and the -API already supports limit/cursor pagination; contract search (stellar-registry/indexer#24), the -pagination/sorting UX in the explorer, and validation against a 1,000+ entry dataset carry into Q3. +**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 @@ -275,7 +281,7 @@ Description from last quarter: > Measure: all three features are live on the production `rgstry.xyz` site and manually verified > against at least one mainnet contract. -Proof of progress: +Proof of completion: - https://github.com/stellar-registry/indexer/pull/15 — `stellar contract info meta` metadata parsed and exposed in the wasm-detail API (item 2, backend half — the API serves rsver, SDK, CLI, and @@ -284,11 +290,11 @@ Proof of progress: contract's GitHub repo - https://github.com/stellar-registry/ui/pull/18 — request-id-traced error reporting -**Partially complete.** The backend half of metadata surfacing (item 2) shipped — the UI currently -renders the source-repo link, with the remaining metadata fields still to surface — plus unplanned -page-richness work (README/LICENSE rendering). The embedded Contract Explorer (item 1) and the -"deploy this Wasm" button (item 3) carry into Q3; the deploy button now has a clearer path via the -governance proposal forms in stellar-registry/ui#16. +**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 and traceable +error reporting 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) — the latter now has +a clearer path via the governance proposal forms in stellar-registry/ui#16. ### D6. Verified Build Integration with Stellar Expert @@ -299,7 +305,7 @@ Description from last quarter: > 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 progress: +Proof of completion: - https://github.com/stellar-registry/contracts/pull/10 — releases now use the stellar-expert/soroban-build-workflow: environment-gated, with OIDC build-provenance attestation @@ -309,10 +315,10 @@ Proof of progress: to the SCF Build Award RFP track, with architecture collaboration from Ethan Frey (Confio) (stellar-registry/cli#11, #12) -**Partially complete.** The produce side is done — Registry releases are themselves verified builds -attested to Stellar Expert. The display side (badge on rgstry.xyz detail pages) carries into Q3; we -learned along the way that Stellar Expert has no Wasm-level pages (stellar-registry/ui#17), so the -badge work targets contract pages. +**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 @@ -329,7 +335,7 @@ Description from last quarter: > > Measure: documentation is live on Registry's own docs site & The Aha Company's YouTube channel. -Proof of progress: +Proof of completion: - https://scaffoldstellar.org/docs/registry — the Registry Guide is live (overview, verified/unverified registries, name resolution, publish/deploy CLI usage) and linked as "Guide" @@ -341,11 +347,29 @@ Proof of progress: - https://github.com/stellar-registry/cli/pull/17 — design spec and implementation plan documents for `import_contract!` -**Partially complete.** Documentation moved into the product (usage guides on every registry page, -the Registry Guide linked from the site) and into the four standalone repos. The measure specified -Registry's own docs site and videos: the guide currently lives on the Scaffold Stellar docs site, -`import_contract!` coverage awaits the D2 release, and the video series did not ship — these carry -into Q3. +**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: + +- **Standalone organization**: the Registry split out of the scaffold-stellar monorepo into + https://github.com/stellar-registry — four repos (cli, contracts, ui, indexer) with full history + preserved, scoped CI, and dependabot. +- **On-chain governance**: the Tansu-DAO-gated registry manager contract + (stellar-registry/contracts#5), merged and verified live on testnet end-to-end (proposal → vote → + trigger → publish, replay-guard confirmed). +- **Protocol currency**: contracts migrated to soroban-sdk v27 / stellar-cli v27 + (stellar-registry/contracts#11); the CLI's v27 migration is in review (stellar-registry/cli#13). +- **Registry intake pipeline**: CI-validated intake forms with strkey, sha256, and semver validators + and IssueOps labeling. +- **Contract version history**: an archive indexer pipeline capturing factory-pattern deploys and + exposing full per-contract version history (stellar-registry/indexer#14). +- **Source verification RFP**: a Contract Source Verification Service RFP submitted to the SCF Build + Award track, with architecture collaboration from Ethan Frey (Confio). From 922fd9cd5dac2c21607dab7362c9d0f9783403c3 Mon Sep 17 00:00:00 2001 From: Willem Wyndham Date: Mon, 6 Jul 2026 15:06:34 -0400 Subject: [PATCH 03/26] Update D1: Registry deployed to mainnet contracts#14 merged and executed; retroactive impact, past D1, and Q3 D1 now reflect the live mainnet contract, with indexer + UI cutover as the remaining rollout. Co-Authored-By: Claude Fable 5 --- docs/projects/stellar-registry.md | 58 ++++++++++++++++++------------- 1 file changed, 34 insertions(+), 24 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index da6e655..d90bf94 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -120,8 +120,15 @@ what developers expect from modern, full-stack tooling. -In Q2 2026 the Registry grew from a testnet prototype into a production-shaped system with its own -organization, on-chain governance, verified builds, and a real data platform behind rgstry.xyz. +In Q2 2026 the Registry grew from a testnet prototype into production infrastructure — deployed to +mainnet at the close of the quarter — with its own organization, on-chain governance, verified +builds, and a real data platform behind rgstry.xyz. + +**The Registry is live on mainnet.** The registry contract is deployed to Stellar mainnet at its +deterministic, salt-derived ID `CDU4M3LDIOUJJ5F3YXKJ4EJEP5VPRPG6N2LJ5HOQIMN7MNGL3NS3EGUY` (baked into +the CLI) via the phased deploy pipeline (stellar-registry/contracts#14, merged 2026-07-06), seeded +with verified ecosystem contracts (circle, soroswap, blend, defindex, xlm). The mainnet indexer +pipeline and the rgstry.xyz mainnet cutover are rolling out this week. **Registry became standalone infrastructure.** The Registry was split out of the theahaco/scaffold-stellar monorepo into its own GitHub organization, @@ -184,20 +191,24 @@ Description from last quarter: > > Measure: the contract is deployed & the CLI points to it. -Proof of progress: +Proof of completion: -- https://github.com/stellar-registry/contracts/pull/14 — phased, dry-run-by-default - `deploy_mainnet.sh` plus verified mainnet seed data (circle, soroswap, blend, defindex, xlm), with - every contract ID resolved from authoritative sources and confirmed live on Pubnet +- https://stellar.expert/explorer/public/contract/CDU4M3LDIOUJJ5F3YXKJ4EJEP5VPRPG6N2LJ5HOQIMN7MNGL3NS3EGUY + — the registry contract live on mainnet at its deterministic, salt-derived ID +- https://github.com/stellar-registry/contracts/pull/14 — merged 2026-07-06: phased, + dry-run-by-default `deploy_mainnet.sh` plus verified mainnet seed data (circle, soroswap, blend, + defindex, xlm), with every contract ID resolved from authoritative sources and confirmed live on + Pubnet - https://github.com/stellar-registry/indexer/pull/5 — "the first mainnet-ready pipeline & API" - https://github.com/stellar-registry/ui/pull/1 — testnet/mainnet network switch and per-environment Cloudflare Worker deploys; Mainnet UI scaffolding at stellar.rgstry.xyz -**All launch machinery built and verified.** The phased deploy script with mainnet seed data (every -contract ID resolved from authoritative sources and confirmed live on Pubnet), the mainnet-ready -indexer pipeline, and the multi-network UI are all in place. The deploy itself is intentionally gated -on secure-store/Ledger signing (stellar-registry/cli#14): we will not operate permanent ecosystem -infrastructure from a raw secret key. Flipping the switch is the first Q3 deliverable. +**Deployed to mainnet.** The phased deploy pipeline merged and executed at the close of the quarter: +the registry contract is live on Pubnet 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 @@ -377,12 +388,11 @@ Infrastructure we shipped this quarter that was not in the Q2 deliverables: -**Launch on mainnet.** Q2 built every piece of the mainnet machinery: a phased deploy script with -verified seed data (stellar-registry/contracts#14), a mainnet-ready indexer pipeline, a multi-network -UI, and — critically — the security posture to do it right: DAO-gated registry governance via Tansu -and secure-store/Ledger signing (stellar-registry/cli#14) so permanent ecosystem infrastructure is -never operated from a raw secret key. Q3 turns the key: the Registry contract live on Pubnet, -governed on-chain, indexed, and browsable at rgstry.xyz. +**Complete the mainnet launch.** The Registry contract is live on mainnet as of this proposal. Q3 +finishes the public rollout: the mainnet indexer pipeline, rgstry.xyz serving mainnet data with the +"Coming Soon" banner removed, and secure-store/Ledger signing for admin operations +(stellar-registry/cli#14) so permanent ecosystem infrastructure is never administered from a raw +secret key — alongside the Tansu DAO-gated governance already in place. **Complete the composability story.** Releasing `import_contract!` (stellar-registry/cli#17) lets any Soroban developer depend on Registry contracts the way they depend on Rust crates, and the @@ -405,15 +415,15 @@ the ecosystem its first crates.io-style package experience for on-chain code. -### D1: Mainnet Launch of Stellar Registry (carried from Q2) +### D1: Complete the Mainnet Launch (carried from Q2) -Deploy the Registry contract and seed data to mainnet via the phased deploy pipeline -(stellar-registry/contracts#14), with secure-store/Ledger signing support in the CLI -(stellar-registry/cli#14) so the deploy and admin operations never expose a raw secret key. Point the -CLI and rgstry.xyz at the mainnet contract and remove the "Coming Soon" banner. +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: the mainnet contract ID published in the docs, visible on Stellar Expert, resolvable via -`stellar registry` CLI, and browsable at rgstry.xyz. +Proof: mainnet data live and browsable at rgstry.xyz, the contract visible on Stellar Expert, and +named contracts resolvable via `stellar registry` CLI. ### D2: Release `import_contract!` (carried from Q2) From acc32afa3e1764989cf1c7d3910940b68caca1d2 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Mon, 6 Jul 2026 17:52:32 -0400 Subject: [PATCH 04/26] s/Pubnet/mainnet/ Co-authored-by: Willem Wyndham Signed-off-by: Chad Ostrowski <221614+chadoh@users.noreply.github.com> --- docs/projects/stellar-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index d90bf94..e394f8f 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -204,7 +204,7 @@ Proof of completion: Cloudflare Worker deploys; Mainnet UI scaffolding at stellar.rgstry.xyz **Deployed to mainnet.** The phased deploy pipeline merged and executed at the close of the quarter: -the registry contract is live on Pubnet at its deterministic ID, seeded with verified ecosystem +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 From ab7d08a4f61b3189611d5f005828208c358d3aa2 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Mon, 6 Jul 2026 17:52:57 -0400 Subject: [PATCH 05/26] rgstry.xyz hyperlink Co-authored-by: Willem Wyndham Signed-off-by: Chad Ostrowski <221614+chadoh@users.noreply.github.com> --- docs/projects/stellar-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index e394f8f..830b282 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -206,7 +206,7 @@ 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 +Remaining for full public accessibility: the mainnet indexer pipeline and pointing [rgstry.xyz](https://rgstry.xyz) at mainnet — rolling out this week — plus secure-store/Ledger signing for admin operations (stellar-registry/cli#14). From d7f7ae0f382b4e1496e7b3a08dddd645caf5f999 Mon Sep 17 00:00:00 2001 From: Willem Wyndham Date: Mon, 6 Jul 2026 18:39:21 -0400 Subject: [PATCH 06/26] Apply suggestions from code review Co-authored-by: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Co-authored-by: Willem Wyndham Signed-off-by: Willem Wyndham --- docs/projects/stellar-registry.md | 36 ++++++++++++------------------- 1 file changed, 14 insertions(+), 22 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 830b282..b857c4a 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -152,14 +152,16 @@ replay-guard rejection confirmed. **Verified builds are live.** We adopted the stellar-expert/soroban-build-workflow for releases (stellar-registry/contracts#10), replacing 243 lines of bespoke CI with environment-gated, OIDC build-provenance-attested releases, and published the first verified build of the registry contract. -We also submitted a Contract Source Verification Service RFP to the SCF Build Award RFP track and +We also submitted a Contract Source Verification RFP to the SCF Build Award RFP track and collaborated with Ethan Frey (Confio) on its technical architecture. **The indexer went v1.** The first mainnet-ready pipeline & API (stellar-registry/indexer#5) moved data into a versioned schema, added auto-discovery of named subregistries (oz, blend, soroswap, defindex), and grew an archive pipeline exposing full per-contract version history -(stellar-registry/indexer#14). June added structured logging with request-id tracing and a trigram -index enabling fuzzy server-side search (stellar-registry/indexer#23). +(stellar-registry/indexer#14), including versions that predate contract's +addition to Stellar Registry. June added structured logging with request-id +tracing and a trigram index enabling fuzzy server-side search +(stellar-registry/indexer#23). **rgstry.xyz matured.** The UI gained a testnet/mainnet network switch with per-environment Cloudflare Worker deploys, in-UI usage guides for the import macros, README/LICENSE rendering from a @@ -167,10 +169,8 @@ contract's GitHub repo, contract metadata on detail pages, server-side search, a error reporting — 18 merged PRs in the quarter. **Releases and toolchain.** Crates published: `stellar-registry` v0.0.8–v0.0.10, -`stellar-registry-cli` v0.0.20/v0.0.21, `stellar-registry-build` v0.0.8. The contracts moved to -soroban-sdk v27 / stellar-cli v27 (stellar-registry/contracts#11); the CLI's v27 migration is in -review (stellar-registry/cli#13). Registry intake forms are now CI-validated with strkey, sha256, and -semver validators and IssueOps labeling. +`stellar-registry-cli` v0.0.20/v0.0.21, `stellar-registry-build` v0.0.8. The contracts and CLI both moved to +soroban-sdk v27 / stellar-cli v27 (stellar-registry/contracts#11, stellar-registry/cli#13). @@ -248,12 +248,8 @@ Proof of progress: - https://github.com/stellar-registry/contracts/commit/de06277 — on-chain contract flagging with a gas-optimized storage encoding (flag encoded in vec length, so unflagged entries pay zero overhead on the hot path), `FlagContract` events, and error types -- https://github.com/stellar-registry/cli/commit/1413f7f — registry intake CI validation (strkey, - sha256, semver validators with IssueOps labeling), the curation pipeline enforcement sits on - -**On-chain half shipped; compile-time half sequenced by design.** Flag storage, `FlagContract` -events, and error types shipped in April. The build-time check extends `import_contract!` (D2), so it -was deliberately sequenced behind that macro's implementation and follows it in early Q3. +- https://github.com/stellar-registry/cli/pull/17 – PR for D2 implements compile-time error mechanics, + preventing contracts from building when their source contracts have been flagged. ### D4. Server-Side Search, Pagination & Sorting on rgstry.xyz @@ -299,13 +295,11 @@ Proof of completion: build versions plus source repo) - https://github.com/stellar-registry/ui/pull/13 — README.md and LICENSE fetched and rendered from a contract's GitHub repo -- https://github.com/stellar-registry/ui/pull/18 — request-id-traced error reporting +- https://github.com/stellar-registry/ui/pull/23 — (open) form for deploying unnamed (unregistered) contract from a Wasm detail page, shipping days into Q3 +- https://github.com/stellar-registry/ui/pull/24 — (open) form for interacting with a deployed contract from its rgstry.xyz detail page, shipping days into Q3 **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 and traceable -error reporting 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) — the latter now has -a clearer path via the governance proposal forms in stellar-registry/ui#16. +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 @@ -374,11 +368,9 @@ Infrastructure we shipped this quarter that was not in the Q2 deliverables: (stellar-registry/contracts#5), merged and verified live on testnet end-to-end (proposal → vote → trigger → publish, replay-guard confirmed). - **Protocol currency**: contracts migrated to soroban-sdk v27 / stellar-cli v27 - (stellar-registry/contracts#11); the CLI's v27 migration is in review (stellar-registry/cli#13). -- **Registry intake pipeline**: CI-validated intake forms with strkey, sha256, and semver validators - and IssueOps labeling. + (stellar-registry/contracts#11; stellar-registry/cli#13). - **Contract version history**: an archive indexer pipeline capturing factory-pattern deploys and - exposing full per-contract version history (stellar-registry/indexer#14). + exposing full per-contract version history beyond Registry's existence (stellar-registry/indexer#14). - **Source verification RFP**: a Contract Source Verification Service RFP submitted to the SCF Build Award track, with architecture collaboration from Ethan Frey (Confio). From 8c2c2be87adcf9141b939dff085b91edc33c86b7 Mon Sep 17 00:00:00 2001 From: Willem Wyndham Date: Mon, 6 Jul 2026 18:43:21 -0400 Subject: [PATCH 07/26] Fix pre-commit failures: trailing whitespace + prettier wrap Reflows the web-UI review-suggestion commits to the repo's 101-column prettier format; no content changes. Co-Authored-By: Claude Fable 5 --- docs/projects/stellar-registry.md | 34 +++++++++++++++++-------------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index b857c4a..9cb853e 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -158,10 +158,9 @@ collaborated with Ethan Frey (Confio) on its technical architecture. **The indexer went v1.** The first mainnet-ready pipeline & API (stellar-registry/indexer#5) moved data into a versioned schema, added auto-discovery of named subregistries (oz, blend, soroswap, defindex), and grew an archive pipeline exposing full per-contract version history -(stellar-registry/indexer#14), including versions that predate contract's -addition to Stellar Registry. June added structured logging with request-id -tracing and a trigram index enabling fuzzy server-side search -(stellar-registry/indexer#23). +(stellar-registry/indexer#14), including versions that predate contract's addition to Stellar +Registry. June added structured logging with request-id tracing and a trigram index enabling fuzzy +server-side search (stellar-registry/indexer#23). **rgstry.xyz matured.** The UI gained a testnet/mainnet network switch with per-environment Cloudflare Worker deploys, in-UI usage guides for the import macros, README/LICENSE rendering from a @@ -169,8 +168,8 @@ contract's GitHub repo, contract metadata on detail pages, server-side search, a error reporting — 18 merged PRs in the quarter. **Releases and toolchain.** Crates published: `stellar-registry` v0.0.8–v0.0.10, -`stellar-registry-cli` v0.0.20/v0.0.21, `stellar-registry-build` v0.0.8. The contracts and CLI both moved to -soroban-sdk v27 / stellar-cli v27 (stellar-registry/contracts#11, stellar-registry/cli#13). +`stellar-registry-cli` v0.0.20/v0.0.21, `stellar-registry-build` v0.0.8. The contracts and CLI both +moved to soroban-sdk v27 / stellar-cli v27 (stellar-registry/contracts#11, stellar-registry/cli#13). @@ -206,9 +205,9 @@ 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](https://rgstry.xyz) at -mainnet — rolling out this week — plus secure-store/Ledger signing for admin operations -(stellar-registry/cli#14). +Remaining for full public accessibility: the mainnet indexer pipeline and pointing +[rgstry.xyz](https://rgstry.xyz) at mainnet — rolling out this week — plus secure-store/Ledger +signing for admin operations (stellar-registry/cli#14). ### D2. `import_contract!` Macro @@ -248,8 +247,8 @@ Proof of progress: - https://github.com/stellar-registry/contracts/commit/de06277 — on-chain contract flagging with a gas-optimized storage encoding (flag encoded in vec length, so unflagged entries pay zero overhead on the hot path), `FlagContract` events, and error types -- https://github.com/stellar-registry/cli/pull/17 – PR for D2 implements compile-time error mechanics, - preventing contracts from building when their source contracts have been flagged. +- https://github.com/stellar-registry/cli/pull/17 – PR for D2 implements compile-time error + mechanics, preventing contracts from building when their source contracts have been flagged. ### D4. Server-Side Search, Pagination & Sorting on rgstry.xyz @@ -295,11 +294,15 @@ Proof of completion: build versions plus source repo) - https://github.com/stellar-registry/ui/pull/13 — README.md and LICENSE fetched and rendered from a contract's GitHub repo -- https://github.com/stellar-registry/ui/pull/23 — (open) form for deploying unnamed (unregistered) contract from a Wasm detail page, shipping days into Q3 -- https://github.com/stellar-registry/ui/pull/24 — (open) form for interacting with a deployed contract from its rgstry.xyz detail page, shipping days into Q3 +- https://github.com/stellar-registry/ui/pull/23 — (open) form for deploying unnamed (unregistered) + contract from a Wasm detail page, shipping days into Q3 +- https://github.com/stellar-registry/ui/pull/24 — (open) form for interacting with a deployed + contract from its rgstry.xyz detail page, shipping days into Q3 **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). +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 @@ -370,7 +373,8 @@ Infrastructure we shipped this quarter that was not in the Q2 deliverables: - **Protocol currency**: contracts migrated to soroban-sdk v27 / stellar-cli v27 (stellar-registry/contracts#11; stellar-registry/cli#13). - **Contract version history**: an archive indexer pipeline capturing factory-pattern deploys and - exposing full per-contract version history beyond Registry's existence (stellar-registry/indexer#14). + exposing full per-contract version history beyond Registry's existence + (stellar-registry/indexer#14). - **Source verification RFP**: a Contract Source Verification Service RFP submitted to the SCF Build Award track, with architecture collaboration from Ethan Frey (Confio). From 38086d99993814d57345f5c2560151413269b802 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 10:05:24 -0400 Subject: [PATCH 08/26] add milestone for named g-addresses --- docs/projects/stellar-registry.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 9cb853e..418714b 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -471,6 +471,21 @@ workflow. Proof: documentation live on the Registry docs site and videos on The Aha Company's YouTube channel. +### D8: Support named G-addresses + +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. + +Issue: https://github.com/stellar-scaffold/cli/issues/421 + +Proof: code shipped; address system available, documented, and advertised to the community; more +than just Aha addresses added and available. + ## Legal Acknowledgements From e3f6c982e3ed53e5d5e1babbad84cfb1751b2b99 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 14:06:48 +0000 Subject: [PATCH 09/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 418714b..8c4add2 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -478,13 +478,13 @@ names to G-addresses. These will be displayed in the rgstry.xyz UI, so that the "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. +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. Issue: https://github.com/stellar-scaffold/cli/issues/421 -Proof: code shipped; address system available, documented, and advertised to the community; more -than just Aha addresses added and available. +Proof: code shipped; address system available, documented, and advertised to the community; more than +just Aha addresses added and available. From bcb2ccf6da6c96dc2d1fb50a9b3f98d88f2d29d3 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 10:17:59 -0400 Subject: [PATCH 10/26] add D9: Source Verification --- docs/projects/stellar-registry.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 8c4add2..f67dc0e 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -486,6 +486,23 @@ Issue: https://github.com/stellar-scaffold/cli/issues/421 Proof: code shipped; address system available, documented, and advertised to the community; more than just Aha addresses added and available. +### D9: Surface emerging Source Verification information + +The Registry team submitted a [proposal for the Source Verification +system RFP](https://communityfund.stellar.org/dashboard/submissions/receWOpMjj7FxAydj). 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. + ## Legal Acknowledgements From f1b27b6ba55b5ded5b6b63c23b90c29220e897c1 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 14:18:22 +0000 Subject: [PATCH 11/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index f67dc0e..f1972cc 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -488,11 +488,11 @@ just Aha addresses added and available. ### D9: Surface emerging Source Verification information -The Registry team submitted a [proposal for the Source Verification -system RFP](https://communityfund.stellar.org/dashboard/submissions/receWOpMjj7FxAydj). 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. +The Registry team submitted a +[proposal for the Source Verification system RFP](https://communityfund.stellar.org/dashboard/submissions/receWOpMjj7FxAydj). +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 From c785336017ccbe308a93831fc86da253b9294197 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 10:30:17 -0400 Subject: [PATCH 12/26] add D10: tansu evolution --- docs/projects/stellar-registry.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index f1972cc..688e66c 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -503,6 +503,25 @@ 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. +### D10: guide Tansu evolution to support Registry needs + +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. + +Issue: https://github.com/stellar-scaffold/cli/issues/527 + +Proof: [Registry Tansu Manager +contract](https://github.com/stellar-registry/contracts/tree/main/contracts/registry-tansu-manager) +either migrates out of the stellar-registry repository to Tansu, becoming easier to use for all +ecosystem projects, or becomes altogether unnecessary. + ## Legal Acknowledgements From c948326db7f4bee266a987b3dbf9ac981b641bbd Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 14:30:33 +0000 Subject: [PATCH 13/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 688e66c..c4ee34d 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -505,20 +505,20 @@ Source Verification services also shown in a way that exposes, rather than flatt ### D10: guide Tansu evolution to support Registry needs -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. +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. +blockchain ecosystem. Registry's partnership with Tansu ensures the maturity of this solution for all +community projects. Issue: https://github.com/stellar-scaffold/cli/issues/527 -Proof: [Registry Tansu Manager -contract](https://github.com/stellar-registry/contracts/tree/main/contracts/registry-tansu-manager) +Proof: +[Registry Tansu Manager contract](https://github.com/stellar-registry/contracts/tree/main/contracts/registry-tansu-manager) either migrates out of the stellar-registry repository to Tansu, becoming easier to use for all ecosystem projects, or becomes altogether unnecessary. From 14842c2117e191560d0f22c04eb8f5215fbf52c3 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 11:49:19 -0400 Subject: [PATCH 14/26] d11: gh workflow --- docs/projects/stellar-registry.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index c4ee34d..8b65f79 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -522,6 +522,25 @@ Proof: either migrates out of the stellar-registry repository to Tansu, becoming easier to use for all ecosystem projects, or becomes altogether unnecessary. +### D11: Registry GH Workflow to publish Wasms and upgrade contracts + +Wrap the [stellar-expert/soroban-build-workflow](https://github.com/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 that 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. + + ## Legal Acknowledgements From faaba21a1da0db6eb4aac79dbfe722c9a72ba3dd Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 15:49:35 +0000 Subject: [PATCH 15/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 8b65f79..f44c1cc 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -524,7 +524,9 @@ ecosystem projects, or becomes altogether unnecessary. ### D11: Registry GH Workflow to publish Wasms and upgrade contracts -Wrap the [stellar-expert/soroban-build-workflow](https://github.com/stellar-expert/soroban-build-workflow) and add Registry-specific things: +Wrap the +[stellar-expert/soroban-build-workflow](https://github.com/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 @@ -540,7 +542,6 @@ 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. - ## Legal Acknowledgements From 82ecc0c03bce2b2e2b71cce6488f171c0fc224a6 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 12:00:01 -0400 Subject: [PATCH 16/26] d12: full contract version history --- docs/projects/stellar-registry.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index f44c1cc..dbfb037 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -542,6 +542,20 @@ 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. +### D12: UI: Expose full contract version history + +The Registry API [now exposes full version +history](https://stellar-registry-testnet.fly.dev/v1/contracts/registry), 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](https://testnet.rgstry.xyz/contracts/registry). 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](https://testnet.rgstry.xyz/contracts) display +information about full contract history. + ## Legal Acknowledgements From 19d0bf189c2cc42d54751174df27bb10db64f4d1 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 16:00:44 +0000 Subject: [PATCH 17/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index dbfb037..65c7c3c 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -544,11 +544,12 @@ in production with the Registry wasm itself. ### D12: UI: Expose full contract version history -The Registry API [now exposes full version -history](https://stellar-registry-testnet.fly.dev/v1/contracts/registry), 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](https://testnet.rgstry.xyz/contracts/registry). This deliverable addresses that mismatch. +The Registry API +[now exposes full version history](https://stellar-registry-testnet.fly.dev/v1/contracts/registry), +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](https://testnet.rgstry.xyz/contracts/registry). This deliverable addresses +that mismatch. Value to ecosystem: making contract upgrades easy to find and analyze aids in troubleshooting and full-blockchain comprehensibility. From 8c532d2cdab9fc845300e3f26deea581fe570d89 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 12:14:14 -0400 Subject: [PATCH 18/26] d13: documentation and redesign --- docs/projects/stellar-registry.md | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 65c7c3c..914e889 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -557,6 +557,24 @@ full-blockchain comprehensibility. Proof: Contract detail pages on [rgstry.xyz/contracts](https://testnet.rgstry.xyz/contracts) display information about full contract history. +### D13: Documentation consolidation & redesign; potential migration of rgstry.xyz + +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. + ## Legal Acknowledgements From 063446239420ca059ff8a4db6defa67e156e29c7 Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 16:14:34 +0000 Subject: [PATCH 19/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 914e889..e784023 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -560,11 +560,11 @@ information about full contract history. ### D13: Documentation consolidation & redesign; potential migration of rgstry.xyz 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. +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 +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. From b6443bbacc992170b272bdcc778fb986820c1b8a Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Tue, 7 Jul 2026 16:20:42 -0400 Subject: [PATCH 20/26] wording about needed research from @willemneal Co-authored-by: Willem Wyndham Signed-off-by: Chad Ostrowski <221614+chadoh@users.noreply.github.com> --- docs/projects/stellar-registry.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index e784023..07b67c0 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -536,8 +536,7 @@ We are intentionally leaving contract upgrades as future work, as this gets into 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 that can be stored in a GitHub -workflow and which do not have risky privilege levels. +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. From 06e9d93aa8d3b745c19b6fd6cad7c133ca02e95f Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Tue, 7 Jul 2026 20:20:52 +0000 Subject: [PATCH 21/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 07b67c0..b67d2f3 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -536,7 +536,9 @@ We are intentionally leaving contract upgrades as future work, as this gets into 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. +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. From d2fe607b03e9eb27640951f30af4a6e574988008 Mon Sep 17 00:00:00 2001 From: Pamphile Roy <23188539+tupui@users.noreply.github.com> Date: Wed, 8 Jul 2026 10:42:26 +0200 Subject: [PATCH 22/26] Update docs/projects/stellar-registry.md Co-authored-by: Willem Wyndham Signed-off-by: Pamphile Roy <23188539+tupui@users.noreply.github.com> --- docs/projects/stellar-registry.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index b67d2f3..774a45f 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -576,6 +576,16 @@ 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. +### D14: Extend `import_contract!` macro to support SAC and XLM. + + + 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](https://github.com/stellar-scaffold/ui/blob/main/contracts/guess-the-number/src/xlm.rs). 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. + + ## Legal Acknowledgements From dd163fdb84ca955ec5c58ea9b56e904d27a4724f Mon Sep 17 00:00:00 2001 From: "pre-commit-ci[bot]" <66853113+pre-commit-ci[bot]@users.noreply.github.com> Date: Wed, 8 Jul 2026 08:42:37 +0000 Subject: [PATCH 23/26] [pre-commit.ci] auto fixes from pre-commit.com hooks for more information, see https://pre-commit.ci --- docs/projects/stellar-registry.md | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 774a45f..24b1e0c 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -578,13 +578,19 @@ settled with decision documented and justified. ### D14: Extend `import_contract!` macro to support SAC and XLM. - - 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](https://github.com/stellar-scaffold/ui/blob/main/contracts/guess-the-number/src/xlm.rs). 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. - +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](https://github.com/stellar-scaffold/ui/blob/main/contracts/guess-the-number/src/xlm.rs). +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. From 1538d0f5f994f1321c645ca9bcb0f74ba6770146 Mon Sep 17 00:00:00 2001 From: Chad Ostrowski <221614+chadoh@users.noreply.github.com> Date: Mon, 13 Jul 2026 09:59:15 -0400 Subject: [PATCH 24/26] fucking linter Signed-off-by: Chad Ostrowski <221614+chadoh@users.noreply.github.com> --- docs/projects/stellar-registry.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 24b1e0c..1a8a858 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -576,7 +576,7 @@ 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. -### D14: Extend `import_contract!` macro to support SAC and XLM. +### D14: Extend `import_contract!` macro to support SAC and XLM 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 From 711f8ba8db0c81f972912339d164d1ead5e69a56 Mon Sep 17 00:00:00 2001 From: Alex Olieman Date: Thu, 30 Jul 2026 21:59:00 +0200 Subject: [PATCH 25/26] add pg atlas metric badges --- docs/projects/stellar-registry.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index 1a8a858..af6895f 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -594,6 +594,14 @@ required code to make using and testing the asset easy. +## Metrics loaded from PG Atlas + +[![PG Atlas](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.activity_status&label=PG+Atlas&color=914CFF)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) +[![90d Contributors](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.active_contributors_90d&label=90d+Contributors&color=00B578)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) +[![Criticality](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.criticality_score&label=Criticality&color=E5484D)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) +[![Pony Factor](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.pony_factor&label=Pony+Factor&color=0090FF)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) +[![Adoption](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.adoption_score&label=Adoption&color=FF9900)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) + ## Legal Acknowledgements - [x] As the project representative, I agree to the Legal Acknowledgements. From b1b549d337eb1ea26388b6cff3ffc664903e6e8f Mon Sep 17 00:00:00 2001 From: Alex Olieman Date: Sun, 2 Aug 2026 12:56:04 +0200 Subject: [PATCH 26/26] remove criticality badge --- docs/projects/stellar-registry.md | 1 - 1 file changed, 1 deletion(-) diff --git a/docs/projects/stellar-registry.md b/docs/projects/stellar-registry.md index af6895f..8e1a5f5 100644 --- a/docs/projects/stellar-registry.md +++ b/docs/projects/stellar-registry.md @@ -598,7 +598,6 @@ required code to make using and testing the asset easy. [![PG Atlas](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.activity_status&label=PG+Atlas&color=914CFF)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) [![90d Contributors](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.active_contributors_90d&label=90d+Contributors&color=00B578)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) -[![Criticality](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.criticality_score&label=Criticality&color=E5484D)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) [![Pony Factor](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.pony_factor&label=Pony+Factor&color=0090FF)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry) [![Adoption](https://img.shields.io/badge/dynamic/json?url=https%3A%2F%2Fapi.pgatlas.xyz%2Fprojects%2Fdaoip-5%3Ascf%3Aproject%3Astellar_registry&query=%24.adoption_score&label=Adoption&color=FF9900)](https://www.pgatlas.xyz/projects/daoip-5%3Ascf%3Aproject%3Astellar_registry)