soroban-cli: The transaction fails when using a Stellar multisig account
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- rust
- Domain
- blockchain, cli
Research direction
Start by reproducing the documented soroban contract invoke command with the multisig account and additional signer. Trace the CLI's transaction submission and authorization handling; the issue is complete when this invocation succeeds and the contract call returns normally.
Written by the indexing model from the issue text.
Description
What version are you using?
soroban 0.6.0 (7421c1383beae274d41e503fa44e248b1dbe9b05)
soroban-env 0.0.14 (d06aaddca61f011cc64ec098b464233423197c3a)
soroban-env interface version 29
stellar-xdr 0.0.14 (55f47d302a3bbcd34cf32bfcd28abccfaeffc5e0)
xdr next (df18148747e807618acf4639db41c4fd6f0be9fc)
What did you do?
soroban contract invoke \
--secret-key SBG...API \
--id 10e14c1aa5b4a320068bc05e3406d9bec6f8060f1ea33c1b11621746867e5e16 \
--rpc-url https://horizon-futurenet.stellar.cash:443/soroban/rpc \
--network-passphrase 'Test SDF Future Network ; October 2022' \
--fn increment \
-- \
--user GB3...7LB \
--value 1
The secret key SBG...API belongs to the additional signer of the GB3...7LB account, and has sufficient weight to invoke the contract.
The contract:
pub enum DataKey {
Counter(Address),
}
pub struct IncrementContract;
#[contractimpl]
impl IncrementContract {
pub fn increment(env: Env, user: Address, value: u32) -> u32 {
user.require_auth();
let key = DataKey::Counter(user.clone());
let mut count: u32 = env
.storage()
.get(&key)
.unwrap_or(Ok(0))
.unwrap();
count += value;
env.storage().set(&key, &count);
count
}
}
What did you expect to see?
A successful contract invocation.
What did you see instead?
error: transaction submission failed
- Dominant language
- Rust
- Stars
- 123
- Forks
- 141
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stellar/stellar-cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
stellar/stellar-cli#2384 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
stellar/stellar-cli#2347 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
stellar/stellar-cli#2723 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
stellar/stellar-cli#2722 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
stellar/stellar-cli#2703 ·
All issues in stellar/stellar-cli
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
kwakseongjae/auto-hwp#319 ·
-
area:cli bug filter-quality good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
bevyengine/bevy#25861 ·
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
enhancement remote
Difficulty 2/5 1-3 hours Newbie friendliness 68/100