hashgraph / hashgraph/asset-tokenization-studio
SDK README's Hedera testnet Resolver/Factory addresses are stale (point at a dead BLR deployment)
- Dominant language
- TypeScript
- Stars
- 33
- Forks
- 28
- Avg merge
- 15h 36m
- Merged PRs (30d)
- 8
Description
### Summary
`packages/ats/sdk/README.md`'s "Initialise the SDK" section lists these
testnet coordinates:
- Resolver: `0.0.6797832`
- Factory: `0.0.6797955`
Both addresses have deployed bytecode, but **every call to them reverts**,
including simple view functions like `getLatestVersion` on the resolver.
### Root cause
`packages/ats/contracts/deployments/hedera-testnet/` in this same repo
shows the BusinessLogicResolver has been redeployed multiple times since:
```
newBlr-2026-01-29T16-49-02.json
newBlr-2026-02-05T12-21-16.json
newBlr-2026-04-16T14-20-25-080.json
newBlr-2026-05-19T16-49-31-449.json
newBlr-2026-06-12T11-19-42-198.json <- current, as of this issue
```
The README's addresses point at an earlier, now-dead deployment — they
were never updated to track the redeployments recorded in the same repo's
`deployments/` directory.
### Suggested fix
The two sources of truth (README's example addresses, and
`deployments/hedera-testnet/*.json`) have drifted apart with no
mechanism keeping them in sync. Either:
1. Generate the README's testnet address snippet from the latest
`deployments/hedera-testnet/` file at release/doc-build time, or
2. Replace the hardcoded addresses in the README with a short pointer —
"see the latest file in `packages/ats/contracts/deployments/hedera-testnet/`
for current testnet coordinates" — so it can't silently go stale again.
### Current live addresses (for reference, from the June 12 file)
- BLR proxy: `0xBA2D5FC2083A0b8f164c50e65d782087fBA18E0a`
- Factory proxy: `0xd1F118A40f3b02883D35909eF2517e7EDd78379d`
### What we did instead
Read `newBlr-2026-06-12T11-19-42-198.json` directly for the live
addresses. Full writeup: https://github.com/fabian4819/Stratus-Finance/blob/main/docs/phase-0-findings.md
### Environment
- Checked 2026-09-07/08, no newer `newBlr-*.json` exists as of this issue.
Contributor guide
Research direction
Start with packages/ats/sdk/README.md and compare its Initialise the SDK addresses with the newest file in packages/ats/contracts/deployments/hedera-testnet/, currently newBlr-2026-06-12T11-19-42-198.json. Decide whether the README should point to the deployment source or be generated from it, then verify that it no longer presents dead testnet coordinates as current.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- blockchain, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100