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

Add a fee-sponsorship decision guide linking fee-bumps, sponsored reserves and the Relayer page

Open Beginner friendly
#2,871 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
75/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Domain
documentation

Research direction

Look at the existing docs for fee-bump transactions, sponsored reserves, and the OpenZeppelin Relayer page. Find the passkey and smart-account tutorials to see where services are named inline. Create a new guide that compares the three options and update the tutorials to link to it. Verify links work in the built documentation.

Written by the indexing model from the issue text.

Description

documentation

Every passkey and smart-account onboarding flow needs someone to pay the user's fees and reserves. The docs cover the pieces separately: fee-bump transactions, sponsored reserves, and the OpenZeppelin Relayer page (which now carries the Launchtube replacement). Nothing tells a builder which to reach for, and the passkey tutorials still name a service inline, which breaks each time the recommended service changes.

Please add:

  • a short decision guide: fee-bumps vs sponsored reserves vs a relayer, when each fits, and the cost and trust tradeoffs;
  • a dated "current recommendation" pointer to the Relayer page;
  • cross-links from the passkey and smart-account tutorials to the guide instead of naming a service.

Surfaced by Frontier Lab's ecosystem crawl.

Dominant language
MDX
Stars
138
Forks
313
Avg merge
2d 22h
Merged PRs (30d)
39

Contributor guide

Open the 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 stellar/stellar-docs

All issues in stellar/stellar-docs

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.