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

[docs]: explain fee-bump and Soroban transactions in the bundle format spec

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

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

Research direction

Read docs/bundle-format.md and trace the relevant behavior in crates/externalize-core/src/inclusion.rs, following the functions that handle fee-bump transaction hashes and invocation op_index values. Confirm how each claim is represented, then document both answers with citations to the relevant functions; if the code differs from the intended behavior, open a follow-up bug. Read CONTRIBUTING.md for the repository's checks.

Written by the indexing model from the issue text.

Description

area/docs complexity:trivial documentation good first issue Stellar Wave
Context

docs/bundle-format.md specifies claims by transaction hash. It should say which hash a fee-bump transaction is claimed under, and how an invocation claim's op_index maps to the operations of the inner transaction.

Scope
  • Verify the behaviour against the code in crates/externalize-core/src/inclusion.rs and document it.
  • If the code and the intended behaviour differ, open a follow-up bug instead of changing code here.
Done when
  • The spec answers both questions, citing the relevant functions.

Comment to be assigned before starting. Read CONTRIBUTING.md for the checks this repository runs.

Dominant language
Rust
Stars
1
Forks
1
Avg merge
3d 13h
Merged PRs (30d)
5

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 Externalize-Labs/externalize

All issues in Externalize-Labs/externalize

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.