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

`tx update sequence-number next` fails when the transaction source is a muxed account

Open Beginner friendly
  • Is something wrong?
#2,774 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

@neimasilk-arch is already working on this.

Since Oct 3, 2026.

  • #2793 by @neimasilk-arch — open

Assessment

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

Research direction

Start with the stellar tx update sequence-number next command and reproduce the failure using the muxed-account transaction shown in the issue. Trace how the transaction source is decoded and how the underlying account's sequence number is fetched, then verify that the command succeeds for both muxed and regular sources and preserves the expected transaction output.

Written by the indexing model from the issue text.

Description

bug
What version are you using?

stellar-cli 28.1.0 (d0b26d9, built from main).

What did you do?

I built a payment with a muxed (M…) source account and asked the CLI to fill in the next sequence number:

Setup transaction:

$ stellar network use testnet
$ stellar keys generate alice --fund
$ stellar keys generate bob --fund
$ stellar keys address alice
GD2B52NO66LDB7V745JLNTTWNHBSQJDY3GODG36E6JLUX4F5MMVPSB4H
$ alice_m123=$(stellar keys address alice | stellar-strkey decode | jq '{muxed_account_ed25519: {ed25519: .public_key_ed25519, id: 123}}' | stellar-strkey encode)
$ echo $alice_m123
MD2B52NO66LDB7V745JLNTTWNHBSQJDY3GODG36E6JLUX4F5MMVPSAAAAAAAAAAAPPTC4
$ tx=$(stellar tx new payment --source $alice_m123 --destination bob --amount 1 --build-only)
$ echo $tx
AAAAAgAAAQAAAAAAAAAAe/Qe6a73ljD+v+dSts52acMoJHjZnDNvxPJXS/C9Yyr5AAAAZABLt2UAAAABAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAAzzHaMX7aCe5rN/dBo5nmtZm9AZNqta0rENosve8iCk8AAAAAAAAAAAAAAAEAAAAAAAAAAA==

Attempt to update its sequence number:

$ echo $tx | stellar tx update sequence-number next
What did you expect to see?

The transaction updated with the next sequence number of the underlying G… account, the same as when the source is alice. For example:

$ stellar tx new payment --source alice --destination bob --amount 1 --build-only \
  | stellar tx update sequence-number next
AAAAAgAAAAD0Humu95Yw/r/nUrbOdmnDKCR42Zwzb8TyV0vwvWMq+QAAAGQAS7dlAAAAAQAAAAAAAAAAAAAAAQAAAAAAAAABAAAAAM8x2jF+2gnuazf3QaOZ5rWZvQGTarWtKxDaLL3vIgpPAAAAAAAAAAAAAAABAAAAAAAAAAA=
What did you see instead?

Fails when the tx source is a muxed:

$ stellar tx new payment --source $alice_m123 --destination bob --amount 1 --build-only \
  | stellar tx update sequence-number next
❌ error: the strkey decodes to more bytes than allowed
Dominant language
Rust
Stars
123
Forks
147
Avg merge
3d 11h
Merged PRs (30d)
39

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 stellar/stellar-cli

All issues in stellar/stellar-cli

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.