diff --git a/.github/workflows/docs.yml b/.github/workflows/docs.yml index 196c00b558..62196820a7 100644 --- a/.github/workflows/docs.yml +++ b/.github/workflows/docs.yml @@ -13,6 +13,6 @@ concurrency: jobs: docs-validation: - uses: stellar/stellar-docs/.github/workflows/build.yml@main + uses: stellar/stellar-docs/.github/workflows/cli-build.yml@main with: stellar-cli-ref: ${{ github.sha }} diff --git a/FULL_HELP_DOCS.md b/FULL_HELP_DOCS.md index 4e9b6d67da..bf5d23c502 100644 --- a/FULL_HELP_DOCS.md +++ b/FULL_HELP_DOCS.md @@ -5020,6 +5020,8 @@ Generate arbitrary XDR values Default value: `20000` +- `--entropy ` — Drive generation with the bytes in this file, or stdin if '-', instead of with fresh randomness. Bytes are consumed the same way the fuzz targets consume them, so a fuzz corpus entry piped in here produces the value that entry stands for + ## `stellar xdr xfile` Preprocess XDR .x files @@ -5094,7 +5096,7 @@ Generate the zero strkey - `` — Strkey type to generate the zero value for - Possible values: `public_key_ed25519`, `pre_auth_tx`, `hash_x`, `muxed_account_ed25519`, `signed_payload_ed25519`, `contract`, `liquidity_pool`, `claimable_balance_v0` + Possible values: `public_key_ed25519`, `pre_auth_tx`, `hash_x`, `muxed_account_ed25519`, `signed_payload_ed25519`, `contract`, `liquidity_pool`, `claimable_balance_v0`, `muxed_contract` ###### **Options:** diff --git a/cookbook/asset-management.mdx b/cookbook/asset-management.mdx index ad7d0f08b1..3bc396da6d 100644 --- a/cookbook/asset-management.mdx +++ b/cookbook/asset-management.mdx @@ -1,8 +1,6 @@ --- title: Asset Management -hide_table_of_contents: false description: Issue a Stellar Asset, deploy it's contract, and mint, burn, freeze, and clawback. -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/asset-management.mdx --- The [stellar-cli] can be used to issue and administer assets on the Stellar network. @@ -263,7 +261,7 @@ Using the user account, invoke the asset contract's `transfer` function. The inv stellar keys use user ``` -```bash cookbooktest.fail cookbooktest.stderr="balance is deauthorized" +```bash cookbooktest.fail="" cookbooktest.stderr="balance is deauthorized" stellar contract invoke --id mycontract -- transfer --from user --to user2 --amount 3 ``` diff --git a/cookbook/contract-build-meta.mdx b/cookbook/contract-build-meta.mdx index 057c76a231..dda20b58ae 100644 --- a/cookbook/contract-build-meta.mdx +++ b/cookbook/contract-build-meta.mdx @@ -1,13 +1,11 @@ --- title: Add meta data to contract WASM on build -hide_table_of_contents: true description: Include meta data in the contract WASM byte code on build -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/contract-build-meta.mdx --- To build a smart contract, use the `stellar contract build` command. The `--meta` option will allow you to add additional meta data entries to the `contractmetav0` custom section of the resulting WASM file at build time. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" export SHA=$(git rev-parse HEAD) ``` @@ -25,7 +23,7 @@ stellar contract info meta \ --wasm target/wasm32v1-none/release/test_hello_world.wasm ``` -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" Contract meta: • rsver: 1.91.0 (Rust version) • rssdkver: 23.0.1#510d3feb724c2b01d7e7ab7652f03b9f8efc3f35 (Soroban SDK version and its commit hash) diff --git a/cookbook/contract-invoke-arguments.mdx b/cookbook/contract-invoke-arguments.mdx index b6b2673011..2fb1e3dd41 100644 --- a/cookbook/contract-invoke-arguments.mdx +++ b/cookbook/contract-invoke-arguments.mdx @@ -1,8 +1,6 @@ --- title: "Contract Invoke: Argument Types" -hide_table_of_contents: true description: How to pass each argument type when invoking a Stellar smart contract using the CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/contract-invoke-arguments.mdx --- When using `stellar contract invoke`, each `--arg-name ` flag is parsed according to the contract's type spec. This guide shows the correct format for each supported type. @@ -11,7 +9,7 @@ When using `stellar contract invoke`, each `--arg-name ` flag is parsed a Pass bare numeric literals directly on the command line. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --count 42 \ --offset -7 @@ -21,7 +19,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass bare numeric literals, just like small integers. The CLI reads the raw value as a string internally, bypassing JSON number precision limits entirely. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --amount 340282366920938463463374607431768211455 ``` @@ -30,7 +28,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass `true` or `false` as unquoted literals. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --is_active true \ --is_paused false @@ -40,7 +38,7 @@ stellar contract invoke --id mycontract -- my_function \ Bare words work for simple strings. Numbers and booleans are also accepted and are automatically converted to their string representation, so you do not need to add extra quoting. Explicit JSON quoting is also accepted. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" # Bare word stellar contract invoke --id mycontract -- my_function \ --label hello @@ -62,7 +60,7 @@ stellar contract invoke --id mycontract -- my_function \ Symbols follow the same rules as `String`: bare words, numbers, and booleans are all accepted, and non-string JSON values are auto-converted. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --status active ``` @@ -71,7 +69,7 @@ stellar contract invoke --id mycontract -- my_function \ You can pass either a locally known identity name (e.g. `alice`) or a raw Stellar strkey (`G…` for accounts, `C…` for contracts). -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" # Using an identity alias stellar contract invoke --id mycontract -- my_function \ --owner alice @@ -85,7 +83,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass a hex-encoded string representing the byte sequence. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --hash "deadbeef01020304" ``` @@ -94,7 +92,7 @@ stellar contract invoke --id mycontract -- my_function \ Simply omit the flag. The CLI will supply a `void` / null value for any `Option` parameter that is not provided. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" # If `--memo` is optional, leaving it out passes None stellar contract invoke --id mycontract -- my_function \ --amount 100 @@ -104,7 +102,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass a JSON array, quoting the whole value so the shell does not split it. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --recipients '["alice", "bob", "carol"]' ``` @@ -113,7 +111,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass a JSON object with string keys. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --metadata '{"key": "value", "version": "1"}' ``` @@ -122,7 +120,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass a JSON array whose elements match the tuple's field order. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --point '[10, 20]' ``` @@ -131,7 +129,7 @@ stellar contract invoke --id mycontract -- my_function \ Pass a JSON object with the struct's named fields. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --config '{"max_supply": "1000000", "decimals": 7}' ``` @@ -140,7 +138,7 @@ stellar contract invoke --id mycontract -- my_function \ For unit variants, pass the variant name as a plain string. For variants that carry a value, pass a JSON object with the variant name as the key. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" # Unit variant stellar contract invoke --id mycontract -- my_function \ --status "Active" @@ -154,7 +152,7 @@ stellar contract invoke --id mycontract -- my_function \ For long or complex JSON values, use the `--arg-file-path` flag variant to load the value from a file instead of inlining it on the command line. The flag name is derived from the argument name by appending `-file-path`. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" # Write the JSON to a file first echo '{"max_supply": "1000000", "decimals": 7}' > config.json @@ -165,7 +163,7 @@ stellar contract invoke --id mycontract -- my_function \ For `Bytes` and `BytesN` parameters, the file's raw binary content is read directly — no hex encoding is required. -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract invoke --id mycontract -- my_function \ --hash-file-path /path/to/binary.bin ``` diff --git a/cookbook/contract-lifecycle.mdx b/cookbook/contract-lifecycle.mdx index 76cbfb7e7d..b352d1bb9c 100644 --- a/cookbook/contract-lifecycle.mdx +++ b/cookbook/contract-lifecycle.mdx @@ -1,13 +1,11 @@ --- title: Contract Lifecycle -hide_table_of_contents: true description: Manage the lifecycle of a Stellar smart contract using the CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/contract-lifecycle.mdx --- To manage the lifecycle of a Stellar smart contract using the CLI, follow these steps: -1. Set your preferred network. For this guide, we will use `testnet`. A list of available networks can be found [here](../../../networks/README.mdx) +1. Set your preferred network. For this guide, we will use `testnet`. A list of available networks can be found [here](/docs/networks) ```bash stellar network use testnet @@ -41,7 +39,7 @@ This will display the resulting contract ID, e.g.: CBB65ZLBQBZL5IYHDHEEPCVUUMFOQUZSQKAJFV36R7TZETCLWGFTRLOQ ``` -To learn more about how to build contract `.wasm` files, take a look at our [getting started tutorial](../../../build/smart-contracts/getting-started/setup.mdx). +To learn more about how to build contract `.wasm` files, take a look at our [getting started tutorial](/docs/build/smart-contracts/getting-started/setup). 5. Invoke a contract function: diff --git a/cookbook/deploy-contract.mdx b/cookbook/deploy-contract.mdx index 5556292cc0..ddb9918f70 100644 --- a/cookbook/deploy-contract.mdx +++ b/cookbook/deploy-contract.mdx @@ -1,8 +1,6 @@ --- title: Deploy a contract from uploaded Wasm bytecode -hide_table_of_contents: true description: Deploy an instance of a compiled contract that has already been uploaded on the network -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/deploy-contract.mdx --- To deploy an instance of a compiled smart contract that has already been uploaded onto the Stellar network, use the `stellar contract deploy` command: @@ -15,8 +13,8 @@ stellar contract deploy \ --alias ``` -:::tip + Optionally assign an alias by replacing `` with your desired alias name for the contract. The alias is a locally stored mapping to the contract address, and can be used in other stellar-cli commands in place of the address. -::: + diff --git a/cookbook/deploy-stellar-asset-contract.mdx b/cookbook/deploy-stellar-asset-contract.mdx index 754ed491e6..e3750584c9 100644 --- a/cookbook/deploy-stellar-asset-contract.mdx +++ b/cookbook/deploy-stellar-asset-contract.mdx @@ -1,8 +1,6 @@ --- title: Deploy the Stellar Asset Contract for a Stellar asset -hide_table_of_contents: true description: Deploy an SAC for a Stellar asset so that it can interact with smart contracts -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/deploy-stellar-asset-contract.mdx --- The Stellar CLI can deploy a [Stellar Asset Contract] for a Stellar asset so that any Stellar smart contract can interact with the asset. @@ -15,7 +13,7 @@ The Stellar Asset Contract can be deployed for any possible Stellar asset, eithe To perform the deploy, use the following command: -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar contract asset deploy \ --source S... \ --network testnet \ @@ -26,18 +24,18 @@ The `asset` argument corresponds to the symbol and it's issuer address, which is The same can be done for the native [Lumens] asset: -```bash cookbooktest.fail cookbooktest.stderr="contract already exists" +```bash cookbooktest.fail="" cookbooktest.stderr="contract already exists" stellar contract asset deploy \ --source S... \ --network testnet \ --asset native ``` -:::note + Deploying the native asset will fail on testnet or mainnet as a Stellar Asset Contract already exists. -::: + For any asset, the contract address can be fetched with: diff --git a/cookbook/extend-contract-instance.mdx b/cookbook/extend-contract-instance.mdx index 37a1829767..935243f13e 100644 --- a/cookbook/extend-contract-instance.mdx +++ b/cookbook/extend-contract-instance.mdx @@ -1,8 +1,6 @@ --- title: Extend a deployed contract instance's TTL -hide_table_of_contents: true description: Use the CLI to extend the time to live (TTL) of a contract instance -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-instance.mdx --- You can use the Stellar CLI to extend the TTL of a contract instance like so: diff --git a/cookbook/extend-contract-storage.mdx b/cookbook/extend-contract-storage.mdx index 897cee0910..75d46f0f31 100644 --- a/cookbook/extend-contract-storage.mdx +++ b/cookbook/extend-contract-storage.mdx @@ -1,8 +1,6 @@ --- title: Extend a deployed contract's storage entry TTL -hide_table_of_contents: true description: Use the CLI to extend the time to live (TTL) of a contract's persistent storage entry -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-storage.mdx --- You can use the Stellar CLI to extend the TTL of a contract's persistent storage entry. For a storage entry that uses a simple `Symbol` as its storage key, you can run a command like so: @@ -31,8 +29,8 @@ stellar contract extend \ --durability persistent ``` -:::info + -Be sure to check out our [guide on creating XDR ledger keys](../../../build/guides/rpc/generate-ledger-keys-python.mdx) for help generating them. +Be sure to check out our [guide on creating XDR ledger keys](/docs/build/guides/rpc/generate-ledger-keys-python) for help generating them. -::: + diff --git a/cookbook/extend-contract-wasm.mdx b/cookbook/extend-contract-wasm.mdx index 80cc3def1e..d46f3a364c 100644 --- a/cookbook/extend-contract-wasm.mdx +++ b/cookbook/extend-contract-wasm.mdx @@ -1,8 +1,6 @@ --- title: Extend a deployed contract's Wasm code TTL -hide_table_of_contents: true description: Use Stellar CLI to extend contract's Wasm bytecode TTL, with or without local binary -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/extend-contract-wasm.mdx --- You can use the Stellar CLI to extend the TTL of a contract's Wasm bytecode. This can be done in two forms: if you do or do not have the compiled contract locally. If you do have the compiled binary on your local machine: @@ -29,8 +27,8 @@ stellar contract extend \ --durability persistent ``` -:::info + -You can learn more about finding the correct Wasm hash for a contract instance [here (JavaScript)](../../../build/guides/rpc/retrieve-contract-code-js.mdx) and [here (Python)](../../../build/guides/rpc/retrieve-contract-code-python.mdx). +You can learn more about finding the correct Wasm hash for a contract instance [here (JavaScript)](/docs/build/guides/rpc/retrieve-contract-code-js) and [here (Python)](/docs/build/guides/rpc/retrieve-contract-code-python). -::: + diff --git a/cookbook/payments-and-assets.mdx b/cookbook/payments-and-assets.mdx index 87aa3bf338..14004aef16 100644 --- a/cookbook/payments-and-assets.mdx +++ b/cookbook/payments-and-assets.mdx @@ -1,13 +1,11 @@ --- title: Payments and Assets -hide_table_of_contents: true description: Send XLM, stellar classic, or a soroban asset using the Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/payments-and-assets.mdx --- To send payments and work with assets using the Stellar CLI, follow these steps: -1. Set your preferred network. For this guide, we will use `testnet`. A list of available networks can be found [here](../../../networks/README.mdx) +1. Set your preferred network. For this guide, we will use `testnet`. A list of available networks can be found [here](/docs/networks) ```bash stellar network use testnet @@ -59,4 +57,4 @@ stellar contract invoke --id -- transfer --to bob --from ali stellar contract invoke --id -- balance --id bob ``` -For more information on the functions available to the stellar asset contract, see the [token interface code](../../../tokens/token-interface.mdx#code) +For more information on the functions available to the stellar asset contract, see the [token interface code](/docs/tokens/token-interface#code) diff --git a/cookbook/restore-contract-instance.mdx b/cookbook/restore-contract-instance.mdx index 28b3fd64a4..172e642177 100644 --- a/cookbook/restore-contract-instance.mdx +++ b/cookbook/restore-contract-instance.mdx @@ -1,8 +1,6 @@ --- title: Restore an archived contract using the Stellar CLI -hide_table_of_contents: true description: Restore an archived contract instance using the Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/restore-contract-instance.mdx --- If your contract instance has been archived, it can easily be restored using the Stellar CLI. diff --git a/cookbook/restore-contract-storage.mdx b/cookbook/restore-contract-storage.mdx index 0fea166b25..fa97a64928 100644 --- a/cookbook/restore-contract-storage.mdx +++ b/cookbook/restore-contract-storage.mdx @@ -1,8 +1,6 @@ --- title: Restore archived contract data using the Stellar CLI -hide_table_of_contents: true description: Restore archived contract storage entries using Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/restore-contract-storage.mdx --- If a contract's persistent storage entry has been archived, you can restore it using the Stellar CLI. For a storage entry that uses a simple `Symbol` as its storage key, you can run a command like so: @@ -27,8 +25,8 @@ stellar contract restore \ --durability persistent ``` -:::info + -Be sure to check out our [guide on creating XDR ledger keys](../../../build/guides/rpc/generate-ledger-keys-python.mdx) for help generating them. +Be sure to check out our [guide on creating XDR ledger keys](/docs/build/guides/rpc/generate-ledger-keys-python) for help generating them. -::: + diff --git a/cookbook/stellar-keys.mdx b/cookbook/stellar-keys.mdx index 1356f12c4c..a072cce3c2 100644 --- a/cookbook/stellar-keys.mdx +++ b/cookbook/stellar-keys.mdx @@ -1,8 +1,6 @@ --- title: Stellar Keys -hide_table_of_contents: true description: Manage stellar keys -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/stellar-keys.mdx --- This guide walks you through generating, inspecting, and removing a Stellar identity using the CLI. @@ -27,7 +25,7 @@ The CLI stores this identity in a TOML file. Navigate to the configuration directory and list the contents: -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" cd .config/soroban/identity && ls ``` @@ -41,7 +39,7 @@ The file carol.toml contains the seed phrase for your identity. ### 3. View the Seed Phrase -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" cat carol.toml ``` @@ -51,11 +49,11 @@ Output: seed_phrase = "patrol clean public grocery roof aim have valve cherry dismiss lunar tail duty license capable little version banana amount often cover dice couple party" ``` -:::danger + Note: The seed phrase is sensitive information. Handle it with care and never expose it publicly. -::: + ### 4. Derive the Secret Key @@ -71,11 +69,11 @@ Output: SCJP663VYFZPYN75H2DYJA3FYUBP5UR23HZ4ZDHDMDY6TXVYUYMWNKTI ``` -:::danger + Note: The secret key is sensitive information. Handle it with care and never expose it publicly. -::: + ### 5. Derive the Public Key diff --git a/cookbook/tx-new-create-claimable-balance.mdx b/cookbook/tx-new-create-claimable-balance.mdx index 1e088caae2..ff1111cd3a 100644 --- a/cookbook/tx-new-create-claimable-balance.mdx +++ b/cookbook/tx-new-create-claimable-balance.mdx @@ -1,8 +1,6 @@ --- title: Create Claimable Balance -hide_table_of_contents: true description: Create claimable balances with various claim predicates using the Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-new-create-claimable-balance.mdx --- Claimable balances allow you to send payments that can be claimed by the recipient based on specific conditions. This is useful for escrow-like functionality, conditional payments, or time-locked transfers. @@ -176,7 +174,7 @@ This means: Create a claimable balance for a custom asset: -```bash cookbooktest.ignore +```bash cookbooktest.ignore="" stellar tx new create-claimable-balance \ --source alice \ --amount 1000_000_000 \ diff --git a/cookbook/tx-new.mdx b/cookbook/tx-new.mdx index 680321b896..8cc59aba9a 100644 --- a/cookbook/tx-new.mdx +++ b/cookbook/tx-new.mdx @@ -1,8 +1,6 @@ --- title: tx Commands -hide_table_of_contents: true description: Create stellar transactions using the Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-new.mdx --- So far the examples of the CLI interacting with the blockchain have been through the `contract` command. Uploading contracts, deploying contracts, and invoking them. Each of these are different types of transactions, which must be signed and submitted to the network (and in the case of contract related transactions simulated first). @@ -31,7 +29,7 @@ stellar network use testnet ### Create Account -Creates and funds a new Stellar account. Above `alice` was funded by [friendbot](../../../networks/README.mdx#friendbot). However, `bob` and `charlie` were not. So we can use the `create-account` command to fund them. +Creates and funds a new Stellar account. Above `alice` was funded by [friendbot](/docs/networks#friendbot). However, `bob` and `charlie` were not. So we can use the `create-account` command to fund them. `bob` will receive 10 XLM and `charlie` will get 1 XLM. diff --git a/cookbook/tx-op-add.mdx b/cookbook/tx-op-add.mdx index 1d4652ca3b..15c7eee206 100644 --- a/cookbook/tx-op-add.mdx +++ b/cookbook/tx-op-add.mdx @@ -1,8 +1,6 @@ --- title: tx op add -hide_table_of_contents: true description: Create stellar transactions using the Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-op-add.mdx --- As seen before you can use pipes to pass a transaction envelope between commands. Before we have only been looking at transactions with one operation, however, as mentioned there can be up to 100 operations in a single transaction. diff --git a/cookbook/tx-sign.mdx b/cookbook/tx-sign.mdx index 615e92967f..d47032261a 100644 --- a/cookbook/tx-sign.mdx +++ b/cookbook/tx-sign.mdx @@ -1,8 +1,6 @@ --- title: tx sign and tx send -hide_table_of_contents: true description: Create stellar transactions using the Stellar CLI -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/tx-sign.mdx --- The previous examples of using `tx new` showed how to create transactions. However, these transactions were immediately ready to be signed and submitted to the network. @@ -48,7 +46,7 @@ AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAA You can again [view it in lab and see that there is now a signature attached to the transaction envelope](https://lab.stellar.org/xdr/view?$=network$id=testnet&label=Testnet&horizonUrl=https:////horizon-testnet.stellar.org&rpcUrl=https:////soroban-testnet.stellar.org&passphrase=Test%20SDF%20Network%20/;%20September%202015;&xdr$blob=AAAAAgAAAAAebE8Ewg9uzvHRAl+UmvP0kixsyp238kkz0zOy+91FeQAAAGQAFJk4AAAAAQAAAAAAAAAAAAAAAQAAAAAAAAAAAAAAAPpiy8qfSw4pLYG//Bav78FfrFWlte7YQfiHX41DQ+nGWAAAAAAX14QAAAAAAAAAAAfvdRXkAAABA4kjz9Yeub//IrzogjMr57U4nYwCmSJAXxIW+7Xyjan//UweIByF7uEhVS4gEl1N138uq07njVxZwRMtugWyMleCg==;;). -:::tip + Or sign with lab! Though currently you must send it from lab and cannot return to the CLI (a work in progress!). @@ -61,7 +59,7 @@ stellar tx new create-account \ | stellar tx sign --sign-with-lab ``` -::: + ## `tx send` diff --git a/cookbook/upload-deploy.mdx b/cookbook/upload-deploy.mdx index 04a597ae99..e0558c4caa 100644 --- a/cookbook/upload-deploy.mdx +++ b/cookbook/upload-deploy.mdx @@ -1,8 +1,6 @@ --- title: Upload and deploy a smart contract -hide_table_of_contents: true description: Combine the upload and deploy commands in the Stellar CLI to accomplish both tasks -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/upload-deploy.mdx --- You can combine the `upload` and `deploy` commands of the Stellar CLI to accomplish both tasks: diff --git a/cookbook/upload-wasm.mdx b/cookbook/upload-wasm.mdx index 973fea5938..87cb78a76e 100644 --- a/cookbook/upload-wasm.mdx +++ b/cookbook/upload-wasm.mdx @@ -1,8 +1,6 @@ --- title: Upload Wasm bytecode -hide_table_of_contents: true description: Use the Stellar CLI to upload a compiled smart contract on the ledger -custom_edit_url: https://github.com/stellar/stellar-cli/edit/main/cookbook/upload-wasm.mdx --- To use the Stellar CLI to upload a compiled smart contract on the ledger, use the `stellar contract upload` command: @@ -14,8 +12,8 @@ stellar contract upload \ --wasm ../relative/path/to/soroban_contract.wasm ``` -:::note + Note this command will return the hash ID of the Wasm bytecode, rather than an address for a contract instance. -::: +