Repository navigation
Description
Priority
Medium
User story / Problem statement
Currently, the testnet deployment dates from 2026-10-22, before Tranche 3. Since then the vault, the oracle and the compliance contract have changed (#458–#461), and open work changes them again: the verifier event (#441), the 14-decimal price scale (#431) and the identity registry and compliance that replace the stubs (#238). Stored reports and epoch prices on the current deployment are in WAD, so it cannot be upgraded in place. A redeploy after each change would mean several rounds of new addresses for the app and the docs.
Expected outcome
One testnet deployment built from tranche-3 once this work lands, with the README, the app and the SEP-1 example pointing at it, and nothing left that names the old one.
Acceptance criteria
- Deployed from
tranche-3after Store the share price with 14 decimals instead of WAD #431, Publish an event when the identity verifier lists or delists an address #441 and Choose what replaces the compliance and identity stubs on mainnet #238 merge, and after Generate an asset list for the share token #466 if it lands first - The vault set and the SEP-40 feed are deployed with kept keys
-
environments.tomland the README name the new addresses, and the app builds against them -
docs/sep1/stellar.testnet.tomlis regenerated from the new deployment, with the asset list if Generate an asset list for the share token #466 landed - The happy-path harness scenario passes against the new deployment
- No doc or config still names an address from the 2026-10-22 deployment
- Store the share price with 14 decimals instead of WAD #431's last acceptance criterion is checked
Technical notes
The previous redeploy changed environments.toml and the README in one commit (4e41533). The app reads contract ids from environments.toml at build time, so its build follows that file.
Activity