Skip to content

Comments

fix: accept base58-encoded transaction_message in vault_transaction_create CLI#176

Open
kukaklaudio wants to merge 1 commit intoSquads-Protocol:mainfrom
kukaklaudio:fix/cli-transaction-message-parsing
Open

fix: accept base58-encoded transaction_message in vault_transaction_create CLI#176
kukaklaudio wants to merge 1 commit intoSquads-Protocol:mainfrom
kukaklaudio:fix/cli-transaction-message-parsing

Conversation

@kukaklaudio
Copy link

Bug

The vault_transaction_create CLI command declares transaction_message as Vec<u8>:

#[arg(long)]
transaction_message: Vec<u8>,

Clap parses Vec<u8> by expecting space-separated individual byte values on the command line (e.g., --transaction_message 1 2 3 4), which is completely impractical for transaction messages that are hundreds of bytes long.

Fix

Changed the argument type to String and decode from base58 at runtime:

/// Base58-encoded transaction message bytes
#[arg(long)]
transaction_message: String,

This is consistent with how Solana CLI tools handle binary data and allows users to pass transaction messages as a single base58 string.

Fixes #159

The vault_transaction_create CLI command declared transaction_message as
Vec<u8>, which clap cannot properly parse from command-line arguments
(it expects space-separated individual byte values, which is impractical
for transaction messages).

Changed the argument to accept a base58-encoded string, which is decoded
to Vec<u8> at runtime. This is consistent with how Solana CLI tools
typically handle binary data.

Fixes Squads-Protocol#159
@vercel
Copy link

vercel bot commented Feb 20, 2026

Someone is attempting to deploy a commit to the squads Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Incorrect setup for clap in transaction_create

1 participant