Issues

`StellarTomlResolver` does not support `.well-known/stellar.toml` fallback — fails if TOML is at legacy path

Sorokit/core#862 · opened

on Oct 18, 2026

3

`TransactionBuilder` does not warn when operations exceed typical transaction size — produces oversized transactions

Sorokit/core#858 · opened

on Oct 18, 2026

2

`ContractResultDecoder` does not handle union-type return values — splits results incorrectly

Sorokit/core#857 · opened

on Oct 18, 2026

3

`SorobanSimulation` does not cache simulation results — repeated invocations for the same contract call are re-simulated

Sorokit/core#856 · opened

on Oct 18, 2026

2

`RpcConnectionPool` does not implement circuit breaker pattern — hammers failing endpoints indefinitely

Sorokit/core#855 · opened

on Oct 18, 2026

2

`NetworkPassphrase` is not validated — accepts any string, including invalid passphrases

Sorokit/core#851 · opened

on Oct 18, 2026

10

`FeeEstimate` does not consider transaction complexity — returns the same fee for simple and complex transactions

Sorokit/core#850 · opened

on Oct 18, 2026

5

`ManageOfferBuilder` does not validate price ratio — allows offers with inverted or illogical prices

Sorokit/core#848 · opened

on Oct 18, 2026

3

`buildPaymentWithPath` does not enforce minimum path length — accepts paths with no intermediate hops (ambiguous behavior)

Sorokit/core#847 · opened

on Oct 18, 2026

5

SDK does not provide metrics/observability hooks for production monitoring — blind to runtime behavior

Sorokit/core#845 · opened

on Oct 18, 2026

5

`OfferManager` does not validate that buying and selling assets are different — allows nonsensical offers

Sorokit/core#841 · opened

on Oct 18, 2026

2

`ContractInvocationCache` does not handle Soroban contract upgrades — returns stale contract state after upgrade

Sorokit/core#840 · opened

on Oct 18, 2026

3

Error handling across the SDK is inconsistent — some functions throw, others return `SorokitResult`

Sorokit/core#794 · opened

on Oct 15, 2026

3

`core.ts` does not document which features require opt-in configuration — callers miss required setup steps

Sorokit/core#793 · opened

on Oct 15, 2026

3

`didSupport.ts` does not validate DID document structure — accepts malformed DIDs

Sorokit/core#784 · opened

on Oct 15, 2026

4

Navigation Menu

Repository navigation

Issues

`StellarTomlResolver` does not support `.well-known/stellar.toml` fallback — fails if TOML is at legacy path

`TransactionBuilder` does not warn when operations exceed typical transaction size — produces oversized transactions

`ContractResultDecoder` does not handle union-type return values — splits results incorrectly

`SorobanSimulation` does not cache simulation results — repeated invocations for the same contract call are re-simulated

`RpcConnectionPool` does not implement circuit breaker pattern — hammers failing endpoints indefinitely

`NetworkPassphrase` is not validated — accepts any string, including invalid passphrases

`FeeEstimate` does not consider transaction complexity — returns the same fee for simple and complex transactions

`ManageOfferBuilder` does not validate price ratio — allows offers with inverted or illogical prices

`buildPaymentWithPath` does not enforce minimum path length — accepts paths with no intermediate hops (ambiguous behavior)

SDK does not provide metrics/observability hooks for production monitoring — blind to runtime behavior

`OfferManager` does not validate that buying and selling assets are different — allows nonsensical offers

`ContractInvocationCache` does not handle Soroban contract upgrades — returns stale contract state after upgrade

Error handling across the SDK is inconsistent — some functions throw, others return `SorokitResult`

`core.ts` does not document which features require opt-in configuration — callers miss required setup steps

`didSupport.ts` does not validate DID document structure — accepts malformed DIDs