The software contains inconsistencies in how it handles MPT magnitudes. The `ParseMPTAmountBinary()` function in `internal/ledger/state/ripple state.go` uses `num.Int64()` to convert eight-byte MPT magnitudes without verifying if they fit within 63 bits, which allows positive magnitudes of 2^63 or greater to wrap into negative amounts without triggering an error. This affects the `ParseEscrow()` function, which processes 33-byte `sfAmount` fields and stores `MPTRaw()` in `EscrowData.MPTAmount`, leading to incorrect calculations and divergence from rippled interpretations. Additionally, the `readMPTAmount()` function in `internal/tx/ledgerfields/decode stream.go` accepts magnitudes that exceed limits and produces large decimal strings because it does not enforce the maximum signed 64-bit value, creating a discrepancy with the safer public codec in `codec/binarycodec/types/amount.go`.