What version are you using?
What did you do?
The VerifyEvents function in the token transfer processor (verify_events.go#L161)
expects the amount field to be int64. However, SAC token balances can exceed the
int64 limit through cumulative mints.
Observed behavior:
A SAC token's balance grew via mints and was then fully burned with an amount
(18446947143889701584) exceeding the int64 max. This caused VerifyEvents to fail.
Evidence:
- Contract: CBMFDIRY5OKI4JJURXC4SMEQPWB4UUADIADJK4NA6CYBNOYK4W4TMLLF
- Key: 98a39d51d4d4be729cb01de4c59d489192ce85bbb412b0ff87d6a73cf215cdf6
- Ledger where balance exceeded int64: 61456768
- Ledger where full balance was burned: 61457010
What did you expect to see?
VerifyEvents should not fail for larger amount and supports amounts larger than int64. Probably we need to find limits.
What did you see instead?
VerifyEvents failed for 18446947143889701584
What version are you using?
What did you do?
The VerifyEvents function in the token transfer processor (verify_events.go#L161)
expects the amount field to be int64. However, SAC token balances can exceed the
int64 limit through cumulative mints.
Observed behavior:
A SAC token's balance grew via mints and was then fully burned with an amount
(18446947143889701584) exceeding the int64 max. This caused VerifyEvents to fail.
Evidence:
What did you expect to see?
VerifyEvents should not fail for larger amount and supports amounts larger than int64. Probably we need to find limits.
What did you see instead?
VerifyEvents failed for
18446947143889701584