Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/build/guides/dapps/frontend-guide.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -367,7 +367,7 @@ Calculating these fees can be cumbersome but the Stellar SDK provides a way to c

The ABI or spec is a json file that contains the contract's interface. It defines the functions that can be called on the contract, their parameters, and return types. The ABI is used by clients to interact with the contract and execute its functions. The ABI is generated from the contract's source code and is used to compile the contract into XDR for execution on the Stellar network.

ABI can be generated for a contract using the [`stellar contract bindings`](/docs/tools/cli/stellar-cli#stellar-contract-bindings) command and can be used to interact with the contract.
You can output a contract's ABI as JSON with the [`stellar contract info interface`](/docs/tools/cli/stellar-cli#stellar-contract-info-interface) command and `--output json`, then use it to interact with the contract.

This ABI can also be generated as a typescript library to ease development in your DApp and we'll be looking it later in this guide

Expand Down
2 changes: 1 addition & 1 deletion docs/learn/fundamentals/contract-development/overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ Stellar’s Contract Spec shares many similarities with Ethereum’s ABI but als

Sometimes, you may not have access to the contract's source code or the ability to compile it. In such cases, you must use the [`stellar contract fetch`](../../../tools/cli/stellar-cli#stellar-contract-fetch) command to download the contract's Wasm binary and generate the spec.

Finally, we use the [`stellar bindings`](/docs/tools/cli/stellar-cli#stellar-contract-bindings) command to generate the contract spec from the Wasm binary.
Finally, we use the [`stellar contract info interface`](/docs/tools/cli/stellar-cli#stellar-contract-info-interface) command to output the contract spec from the Wasm binary.

The Stellar Lab has a [Contract Explorer](https://lab.stellar.org/smart-contracts/contract-explorer) also provides the ability to view and to download a contract's contract spec.

Expand Down
2 changes: 1 addition & 1 deletion docs/tools/lab/smart-contracts/contract-explorer.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ In this section, you can find the Wasm history of changes.

## Bindings

Bindings are a feature of the [Stellar CLI](../../cli) that generate fully typed client libraries for your smart contracts, tailored to your chosen programming language, including TypeScript, JSON, Rust, Python, and Java. This makes it easy to integrate Stellar contracts into your application as if they were native modules. Each binding provides type-safe functions corresponding to your contract’s methods. To learn more about generating bindings, please see the [Stellar CLI’s bindings command](../../cli/stellar-cli#stellar-contract-bindings).
Bindings are fully typed client libraries for your smart contracts. They make it easy to integrate Stellar contracts into your application as if they were native modules. Each binding provides type-safe functions corresponding to your contract’s methods. The [Stellar CLI](/docs/tools/cli) generates Rust bindings. For TypeScript, use the [JavaScript Stellar SDK generator](https://github.com/stellar/js-stellar-sdk#cli), since the CLI’s TypeScript command is deprecated. Python, Java, and other languages need an [external plugin](/docs/tools/cli/plugins-list). To learn more about generating bindings, please see the [Stellar CLI’s bindings command](/docs/tools/cli/stellar-cli#stellar-contract-bindings).

## Invoke Contract

Expand Down