Skip to content

fix: bump rosetta-filecoin-lib to v1.3600.0-rc1 (close NV28 actor CID gap)#546

Merged
emmanuelm41 merged 1 commit intodevfrom
fix/rosetta-lib-v1.3600.0-rc1
May 7, 2026
Merged

fix: bump rosetta-filecoin-lib to v1.3600.0-rc1 (close NV28 actor CID gap)#546
emmanuelm41 merged 1 commit intodevfrom
fix/rosetta-lib-v1.3600.0-rc1

Conversation

@emmanuelm41
Copy link
Copy Markdown
Member

Summary

`v4.3600.0-rc1` (NV28 / FireHorse) shipped with `rosetta-filecoin-lib` pinned at `v1.3401.0`, which has `LatestVersion = network.Version27`. The actor CID loader (`actors/actors.go`) iterates `V0..LatestVersion` and queries `StateActorCodeCIDs` per version — so NV28 actor code CIDs are never loaded into the registry.

`rosetta-filecoin-lib v1.3600.0-rc1` (published 2026-05-05, ~15h before `fil-parser v4.3600.0-rc1`) raises `LatestVersion` to `network.Version28` and pins `lotus v1.36.0-rc1`. The dep just needs to be bumped here.

Observed symptom on calibration-blue (pro-zur1, v9.0.2-rc1 + parser v4.3600.0-rc1)

```
ERROR helper/helpers.go:212 — could not get actor cid and name from address.
Err: invalid actor code CID: bafk2bzaceb63lj5qyx6hrtagl4mlqla6rb2ligpeglurhfvn2avubim62oyxc
```

Metric counters ticking:

  • `fil_parser_helper_actor_name_error{code="3844450837"}` — that's FRC-42 of `InvokeContract`
  • `fil_parser_parser_parse_tx_metadata_error{txType="Constructor", mainSuccess="true", subcallSuccess="true"}`

`txType=Constructor` here is the catch-all label assigned when the parser can't classify the actor — the underlying cause is the unknown CID, not Constructor decoding per se.

Change

  • `go.mod`: `zondax/rosetta-filecoin-lib v1.3401.0` → `v1.3600.0-rc1`
  • `go mod tidy` lifted `go.uber.org/zap v1.27.1` → `v1.28.0` (indirect)

Test plan

  • `GOTOOLCHAIN=go1.25.7 go build ./...` clean
  • `go test -short ./...` — same outcome as v4.3600.0-rc1 baseline (one pre-existing test failure `TestParser_ParseTransactions` "Rosetta lib should not be nil" present on both, unrelated to this bump)
  • CI green
  • After merge: tag `v4.3600.1-rc1` (pre-release), bump in fil-indexing, deploy to indexing-calibration-blue, verify both `fil_parser_helper_actor_name_error` and `fil_parser_parser_parse_tx_metadata_error` stop ticking on the unrecognized CIDs

Notes for the release

This is a single-line dep bump. After merge → tag from the merge commit on `dev` as `v4.3600.1-rc1` (pre-release, between rc1 and the next rc).

v4.3600.0-rc1 (NV28 / FireHorse) shipped with rosetta-filecoin-lib
pinned at v1.3401.0, which has LatestVersion = network.Version27. Its
actor CID loader iterates V0..LatestVersion, so V28 actor code CIDs
were never queried from the node. This produced "invalid actor code
CID" errors on calibration once NV28 activated:

  helper/helpers.go:212 - could not get actor cid and name from address
  fil_parser_helper_actor_name_error{code=3844450837} (InvokeContract)
  fil_parser_parser_parse_tx_metadata_error{txType="Constructor"}

rosetta-filecoin-lib v1.3600.0-rc1 (already published) raises
LatestVersion to network.Version28 and pins lotus v1.36.0-rc1. Bumping
the dep fills the registry gap.

go.uber.org/zap also moved 1.27.1 -> 1.28.0 transitively.
@emmanuelm41 emmanuelm41 merged commit ba431fe into dev May 7, 2026
4 of 5 checks passed
@emmanuelm41 emmanuelm41 deleted the fix/rosetta-lib-v1.3600.0-rc1 branch May 7, 2026 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant