Summary
SACs are currently unsupported. They have no deployed WASM, so the existing
spec-fetching path in contractSpec.ts has nothing to read. SACs are a large
share of the contracts a user might actually want to inspect (every classic
asset has one), so this is the most visible gap in coverage.
Approach
SAC interfaces are known and fixed rather than discovered from WASM. The likely
fix is to detect a SAC and fall back to a built-in interface definition instead
of fetching a spec.
Acceptance Criteria
Tech Stack
TypeScript, @stellar/stellar-sdk
Summary
SACs are currently unsupported. They have no deployed WASM, so the existing
spec-fetching path in
contractSpec.tshas nothing to read. SACs are a largeshare of the contracts a user might actually want to inspect (every classic
asset has one), so this is the most visible gap in coverage.
Approach
SAC interfaces are known and fixed rather than discovered from WASM. The likely
fix is to detect a SAC and fall back to a built-in interface definition instead
of fetching a spec.
Acceptance Criteria
states SACs are unsupported
Tech Stack
TypeScript, @stellar/stellar-sdk