A transfer-history export should resume from its last saved page after a timeout. It should not start over, and it should not advance past a page it never received.

The useful unit of progress is the response and its next cursor, saved together . A cursor on its own tells you where to continue, but not whether you kept the data that came before it.

This BlockVectra example reads ERC-20 transfers for one address in a fixed block window. It makes at most one request per invocation, saves the original response envelope, and resumes when you run it again.

Install the packaged example

The example is included in the 0.1.5 GitHub release archive:

npm install https://github.com/blockvectra/data-api-js/releases/download/v0.1.5/blockvectra-data-api-0.1.5.tgz umask 077 mkdir -p .checkpoints chmod 700 .checkpoints

Enter fullscreen mode

Exit fullscreen mode

Use this archive for the example.…