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
Philosophically, it feels most correct to change fields from number to bigint everywhere that go-algorand defines a uint64 data type. In practice, it causes a backwards incompatibility and adds some friction to developer ergonomics (can't perform arithmetic with numberandbigint).
Given that changing field types feels out of reach, we agreed it'd be reasonable to expand function types to accept number | bigint + perform safe coercion to number.
We confirmed via visual inspection that Transaction construction defends against unsafe conversions to number using Number.isSafeInteger. Here's an example check:
I am modifying Reach to always use bigint int decoding, but there are some problems...
makeAssetTransferTxnWithSuggestedParams
-- specifically theassetIndex
could be a bigintmakeApplicationXYZ
--- specifically the app id, foreign, and asset idsindexer.lookupApplications
indexer.searchForTransactions().minRound()
The text was updated successfully, but these errors were encountered: