Skip to content

Update smart-contract CLI examples for wasm32v1-none and --source-account #44

Description

@kalepail

The smart-contracts skill still shows pre-current Stellar CLI examples in the build/deploy/invoke flow and related docs.

Current stale examples include:

  • target/wasm32-unknown-unknown/release/*.wasm
  • stellar keys generate --global alice --network testnet --fund
  • stellar contract deploy ... --source alice
  • stellar contract invoke ... --source alice

Current canonical forms should be:

  • target/wasm32v1-none/release/*.wasm
  • stellar keys generate alice --network testnet --fund
  • stellar contract deploy ... --source-account alice
  • stellar contract invoke ... --source-account alice

Evidence checked 2026-07-07:

  • Stellar Docs Hello World says stellar contract build wraps cargo with target wasm32v1-none and emits target/wasm32v1-none/release/....
  • Stellar Docs Contract Rust Dialect says new contracts should use Rust 1.84+ and wasm32v1-none; wasm32-unknown-unknown is unsupported on Rust 1.82+.
  • Local stellar 27.0.0 CLI help uses --source-account <SOURCE_ACCOUNT> for deploy/invoke. --source remains accepted as an alias, so this is a canonical-docs fix rather than a command-removal claim.
  • Local stellar keys generate --help uses stellar keys generate [OPTIONS] <NAME> and includes --network and --fund, with no --global option.

Suggested files to update:

  • skills/smart-contracts/SKILL.md
  • skills/smart-contracts/development.md
  • skills/smart-contracts/testing.md
  • skills/assets/SKILL.md for the SAC deploy example using --source

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions