Token-amount decoder fuzz (overflow, fractional)

[Miracle656]

Background

i128 / u128 amounts can overflow JavaScript Number. A fuzz that confirms BigInt-only handling.

What to build

fast-check generator for i128 values, assert decoded result is BigInt and equals the input.

Key files

• tests/decoder.amount.fuzz.test.ts (new)

Acceptance criteria

• 10k inputs, no precision loss

Drips Wave · Complexity: Easy · 100 points

[Awointa]

@Awointa has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi, I’m interested in this issue. I have experience writing TypeScript fuzz tests using fast-check and handling high-precision numeric decoding safely with BigInt.

I can implement a fuzz test that generates i128 edge cases (including overflow-prone and fractional boundary inputs where applicable), validates that decoded values are always returned as BigInt, and ensures exact equality with the original input across a 10k iteration run. I’ll also make sure the test is deterministic, robust, and clearly structured for future extension.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Awointa to this issue.

[githoboman]

@githoboman has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

hello am ayomide a full-stack blockchain dev

ℹ️ Repo Maintainers: To accept this application, review their application or assign @githoboman to this issue.

[drips-wave]

Congratulations, @githoboman! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @githoboman: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊