test(evm-core): Verify derivation behaves safely at the highest valid and first invalid child index

Open Beginner friendly
#697 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
83/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
rust

Research direction

Start in crates/evm-core/src/derive.rs and read the existing child derivation tests and the fallible path builder. Add boundary coverage using only the public test mnemonic: assert success and a stable address at 2^31 - 1, and an error without a panic at 2^31. Run cargo test -p octo-evm-core; done when both boundary cases pass.

Written by the indexing model from the issue text.

Description

area/contract area/testing enhancement good first issue help wanted

Description

Non-hardened child indices must be below 2^31; the behaviour at 2^31 - 1 and 2^31 is not tested.

Requirements and context

  • Where: crates/evm-core/src/derive.rs
  • Security: Use public test vectors only; never real mnemonics.
  • Testing: just fmt-check, just lint and just test must pass; add or update tests for the change.
  • Documentation: Update the nearest doc if behaviour changes; otherwise no doc change is needed.

Suggested execution

  • Comment on this issue to claim it, then fork the repository and branch from main.
  • Branch name: git checkout -b test/evm-core-index-boundary

Implement changes

  • Derive at index = 2^31 - 1 and assert success with a stable address.
  • Derive at index = 2^31 and assert an error rather than a panic (depends on the fallible path-builder issue).
  • Use the public test mnemonic only.

Test and commit

  • cargo test -p octo-evm-core passes.
  • Run just fmt, just lint and just test locally before pushing (see CONTRIBUTING.md).
  • Commit with a conventional message and keep the change small and focused.

Example commit message

test(evm-core): cover child index boundary

Guidelines

  • Open the PR against main and link it with Closes #<this issue>.
  • Keep the diff focused on this issue; no unrelated refactors or formatting churn.
  • One line per comment, no bloated code; follow patterns already used in the crate.
  • Never commit secrets, .env files or real keys; use public test vectors only.
  • CI (fmt, clippy -D warnings, tests) must be green before requesting review.
  • Ask in the issue thread if anything is unclear before starting.
Dominant language
Rust
Stars
0
Forks
91
Avg merge
5h 23m
Merged PRs (30d)
4

Getting set up

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 Octo-Protocol-org/Octo-Protocol

All issues in Octo-Protocol-org/Octo-Protocol

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.