Welcome to the next crypto level
← Nexorena

Altcoins

Sui revises transaction pagination in test release 1.84.0

The test release published on November 10 includes protocol version 142 and changes the cursors used to page through transactions and events. Integrators who save these cursors need to distinguish the gRPC changes from the GraphQL changes.

Nexorena Editorial Team

Sui revises transaction pagination in test release 1.84.0

Some older cursors cannot carry over after the update

Mysten Labs published Sui’s testnet-v1.84.0 release on November 10 at 19:01 UTC. It includes version 142 of the protocol. QuickNode scheduled an update to its own test infrastructure for November 11. That window applies to the provider and its service. The release notes already give Sui integrators a way to identify the changes that will affect how they read transactions, events, and checkpoints.

A cursor tells the server where to resume reading. In gRPC, transaction and event lists now reject cursors issued by servers older than version 1.83. List methods also reject the original cursor format. The client can resume from a position in the ledger. In GraphQL, the change affects, among others, transaction and event cursors from pages that started in the pre-1.84 format. The notes say to restart pagination without a cursor in that case.

An explicit resume position for indexers

gRPC list streams and some subscription streams now carry a resume position in their progress marker. This ledger position gives consumers a reference for ordering results and removing duplicates. Transaction and event lists also accept boundaries expressed as indexes within a checkpoint. An event list can specify the starting or ending event index. These boundaries give indexers a more precise way to resume than using a checkpoint number alone.

On full nodes with the embedded RPC store, a checkpoint becomes readable as soon as it is indexed. The release notes estimate that the relevant subscriptions deliver these checkpoints about 180 milliseconds sooner on average. That figure applies to this particular read path. Another change affects GraphQL clients that get stuck requesting an empty page beyond a boundary. The response now indicates that there are no further pages in that direction.

Accumulator writes count toward transaction effects size

The software release also bundles changes to the protocol. The notes attribute to protocol version 141 the inclusion of accumulator writes, ID-only changes, and unchanged consensus objects in the calculation of transaction effects size. They also specify a limit of 1,024 accumulator events per transaction. Changes previously planned for protocol 141 move to protocol 142 in this test release.

A separate change affects Move contracts that verify Groth16 proofs. When the prepared verifying key contains a number of elements other than the number of public inputs plus one, the verification function now raises an explicit error where it previously returned false. Applications that handled those outcomes differently therefore have a case to test, as do clients that resume streams using saved cursors.

Written with love byOlivia ParkerMeet this editorial pen name ↗

Explorer Nexorena