Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Invalid gindex calculation

Open
  • Is something wrong?
#311 2 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript
Domain
backend

Research direction

Start by running the TypeScript reproduction with ssz.phase0.BeaconState.getPathInfo for the validators/0/activationEpoch and validators/0/pubkey paths. Trace getPathInfo and the gindex calculation, then verify that these paths produce different gindexes and the reported comparison is false.

Written by the indexing model from the issue text.

Description

meta-bug prio-medium

Describe the bug

import {ssz} from "@lodestar/types";

const {BeaconState} = ssz.phase0;
console.log(
  BeaconState.getPathInfo(["validators", 0, "activationEpoch"]).gindex === BeaconState.getPathInfo(["validators", 0, "pubkey"]).gindex
);
// true

Expected behavior

false

Dominant language
TypeScript
Stars
62
Forks
27
Avg merge
19h 2m
Merged PRs (30d)
6

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ChainSafe/ssz

All issues in ChainSafe/ssz

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.