You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, some fields are using data types that are insufficient to hold the expected design values. As an example, memo.id = 18446744073709551615, and in this SDK, memo id is stored using Long. If this SDK is used to parse this transaction, the correct result cannot be obtained. We should modify it to be stored using BigInteger.
The following fields should be corrected.
field
before
after
LedgerBounds.minLedger
int
long
LedgerBounds.maxLedger
int
long
MemoId.id
long
BigInteger
TimeBounds.minTime
long
BigInteger
TimeBounds.maxTime
long
BigInteger
TransactionBuilder.baseFee
int
long
TransactionPreconditions.TIMEOUT_INFINITE
long
BigInteger
TransactionPreconditions.minSeqAge
Long
BigInteger
TransactionPreconditions.minSeqLedgerGap
int
long
What did you expect to see?
These field types have been corrected.
What did you see instead?
N/A
The text was updated successfully, but these errors were encountered:
What version are you using?
latest code.
What did you do?
Check #494 first.
Currently, some fields are using data types that are insufficient to hold the expected design values. As an example, memo.id = 18446744073709551615, and in this SDK, memo id is stored using
Long
. If this SDK is used to parse this transaction, the correct result cannot be obtained. We should modify it to be stored usingBigInteger
.The following fields should be corrected.
What did you expect to see?
These field types have been corrected.
What did you see instead?
N/A
The text was updated successfully, but these errors were encountered: