uint64 for lamports or token input amount will overflow

[0xZex]

I found that in the instruction packages for computebudget, token, and system, the type for amounts is uint64. We know that the maximum value for uint64 is 2**64-1， which is 18446744073709551615. According to Solana's precision of 9, it supports a maximum of 18.4 billion.

In Go, if a value exceeds the range, it won't throw an error; instead, it automatically truncates the high bits and retains only the low 64 bits.

Is there any plan to introduce the math/big package?

[sonicfromnewyoke]

The u64 here is the protocol type, not a computation - if a caller passes a value > 2^64-1, Go's compiler/runtime is the gatekeeper (untyped-constant literals are a compile error; typed casts like uint64(x) from a wider type silently wrap, but that's the caller's side of the boundary, not ours).
Introducing math/big here wouldn't help - the wire value is still u64.

safe to close @HealthyBuilder because it works as intended