You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/build/guides/tokens/stellar-asset-contract.mdx
+7-2
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ client.mint(...);
57
57
58
58
## Testing
59
59
60
-
Soroban Rust SDK provides an easy way to instantiate a Stellar Asset Contract tokens using `register_stellar_asset_contract`. This function can be seen as the deployment of a generic token. In the following example, we are following the best practices outlined in the [Issuing and Distribution Accounts section](../../../tokens/control-asset-access.mdx#issuing-and-distribution-accounts):
60
+
Soroban Rust SDK provides an easy way to instantiate a Stellar Asset Contract tokens using `register_stellar_asset_contract_v2`. This function can be seen as the deployment of a generic token. It also allows you to manipulate flags on the issuer account like `AUTH_REVOCABLE` and `AUTH_REQUIRED`. In the following example, we are following the best practices outlined in the [Issuing and Distribution Accounts section](../../../tokens/control-asset-access.mdx#issuing-and-distribution-accounts):
The contract, `ClaimableBalanceContract`, allows one party to deposit an arbitrary quantity of a token to the contract, specifying additionally: the `claimants`, addresses that may withdraw from the contract; and the `time_bound`, a specification of when those claimants may withdraw from the account.
118
118
@@ -182,8 +182,8 @@ Our `soroban-examples/fuzzing` directory looks like
182
182
183
183
There are special considerations to note in the configuration of both the [contract's manifest] and the [fuzzing crate's manifest].
This fuzz test takes a much more complex input, where some of the values are user-defined types exported from the contract under test. This test is structured as a simple interpreter, where the fuzzing harness provides arbitrarily-generated "steps", where each step is either a `deposit` command or a `claim` command. The test then treats each of these steps as a separate transaction: it maintains a snapshot of the blockchain state, and for each step creates a fresh environment in which to execute the contract call, simulating the advancement of time between each step. As in the previous example, assertions are made after each step.
668
668
@@ -795,4 +795,4 @@ The great benefit of property tests though is that they can be included in stand
795
795
796
796
The [`proptest.rs`] file is a translation of `fuzz_target_1.rs` to a property test.
Copy file name to clipboardexpand all lines: docs/build/smart-contracts/example-contracts/logging.mdx
+5-5
Original file line number
Diff line number
Diff line change
@@ -24,8 +24,8 @@ The [logging example] demonstrates how to log for the purpose of debugging.
24
24
25
25
Logs in contracts are only visible in tests, or when executing contracts using [`stellar-cli`]. Logs are only compiled into the contract if the `debug-assertions` Rust compiler option is enabled.
Copy file name to clipboardexpand all lines: docs/build/smart-contracts/getting-started/storing-data.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -21,7 +21,7 @@ import TabItem from "@theme/TabItem";
21
21
22
22
Now that we've built a basic Hello World example contract, we'll write a simple contract that stores and retrieves data. This will help you see the basics of Soroban's storage system.
23
23
24
-
This is going to follow along with the [increment example](https://github.com/stellar/soroban-examples/tree/v21.4.1/increment), which has a single function that increments an internal counter and returns the value. If you want to see a working example, [try it in GitPod](https://gitpod.io/#https://github.com/stellar/soroban-examples/tree/v21.4.1).
24
+
This is going to follow along with the [increment example](https://github.com/stellar/soroban-examples/tree/v21.6.0/increment), which has a single function that increments an internal counter and returns the value. If you want to see a working example, [try it in GitPod](https://gitpod.io/#https://github.com/stellar/soroban-examples/tree/v21.6.0).
25
25
26
26
This tutorial assumes that you've already completed the previous steps in Getting Started: [Setup](./setup.mdx), [Hello World](./hello-world.mdx), and [Deploy to Testnet](./deploy-to-testnet.mdx).
Copy file name to clipboardexpand all lines: src/pages/docs/learn/interactive/dapps/challenges/challenge-1-payment.mdx
+1-1
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ yarn
61
61
62
62
## Checkpoint 2: 🎬 Deploy Smart Contracts
63
63
64
-
For this step you will need to clone and deploy the Soroban token smart contract from the [Soroban Examples repository](https://github.com/stellar/soroban-examples/tree/v21.4.1/token). This Soroban token smart contract, broken into several smaller modules (as is the custom for complex smart contracts like this one), enables you to create and manage tokens on Soroban.
64
+
For this step you will need to clone and deploy the Soroban token smart contract from the [Soroban Examples repository](https://github.com/stellar/soroban-examples/tree/v21.6.0/token). This Soroban token smart contract, broken into several smaller modules (as is the custom for complex smart contracts like this one), enables you to create and manage tokens on Soroban.
65
65
66
66
The Soroban token is a custom token that will be used to facilitate payments in the Payment Dapp. Tokens are essentially programmable assets on a blockchain, and smart contracts provide the automation and rules for these tokens. They allow for predefined conditions and actions related to the tokens, such as issuance, transfer, and more complex functions, ensuring the execution of these operations without the need for intermediaries. In the case of this Payment Dapp, you will use the Soroban token to initialize and mint "Demo Token" assets, or DT, that you can then use to make payments via the Payment Dapp.
0 commit comments