@subsquid/pipes v1.0.0-beta.1
·
7 commits
to main
since this release
TRON: tolerate the full int64 range on transaction fields
Synchronizes the TRON portal client validation (portal-client/query/tron.ts) with the Rust query API and the java-tron wire types. Two decoders were stricter than what the portal actually serves, so valid blocks halted the stream mid-batch:
| Fields | Codec (Rust) | Proto type | Before | After |
|---|---|---|---|---|
tx expiration, tx timestamp, block timestamp |
TimestampMillisecond (JSON number) |
int64 |
NAT (safe-int only) |
TIMESTAMP_MS (any integer number) |
fee, withdrawAmount, unfreezeAmount, withdrawExpireAmount, energyFee, energyUsage, energyUsageTotal, netUsage, netFee, originEnergyUsage, energyPenaltyTotal |
BigNum (decimal string) |
int64 |
BIG_NAT (unsigned) |
BIG_INT (signed) |
feeLimit was already signed (#137); this generalizes that fix to every int64 amount field, since they share the same BigNum codec and can all be negative. No public types change: timestamp fields stay number, amount fields stay bigint.
Full Changelog: pipes-v1.0.0-alpha.21...pipes-v1.0.0-beta.1