From 4e7e3b5062836c0683bc05b72a104255f1d0636a Mon Sep 17 00:00:00 2001 From: Bri <92327786+briwylde08@users.noreply.github.com> Date: Mon, 19 Aug 2024 10:43:06 -0600 Subject: [PATCH 1/3] move deploying an SAC guide to Tokens --- docs/build/guides/{conventions => tokens}/deploying-a-sac.mdx | 1 + 1 file changed, 1 insertion(+) rename docs/build/guides/{conventions => tokens}/deploying-a-sac.mdx (99%) diff --git a/docs/build/guides/conventions/deploying-a-sac.mdx b/docs/build/guides/tokens/deploying-a-sac.mdx similarity index 99% rename from docs/build/guides/conventions/deploying-a-sac.mdx rename to docs/build/guides/tokens/deploying-a-sac.mdx index a36d3e626..feb15e9e2 100644 --- a/docs/build/guides/conventions/deploying-a-sac.mdx +++ b/docs/build/guides/tokens/deploying-a-sac.mdx @@ -1,5 +1,6 @@ --- title: Deploy a Stellar Asset Contract (SAC) from within a contract +hide_table_of_contents: true description: Deploy a SAC from another smart contract using the Rust SDK --- From 37060936fa512df03d9f0e0435d0cd967dcbdfa4 Mon Sep 17 00:00:00 2001 From: Bri <92327786+briwylde08@users.noreply.github.com> Date: Mon, 19 Aug 2024 11:57:51 -0600 Subject: [PATCH 2/3] move storage guide --- .../guides/{archival => storage}/choosing-the-right-storage.mdx | 0 docs/learn/encyclopedia/storage/state-archival.mdx | 2 +- 2 files changed, 1 insertion(+), 1 deletion(-) rename docs/build/guides/{archival => storage}/choosing-the-right-storage.mdx (100%) diff --git a/docs/build/guides/archival/choosing-the-right-storage.mdx b/docs/build/guides/storage/choosing-the-right-storage.mdx similarity index 100% rename from docs/build/guides/archival/choosing-the-right-storage.mdx rename to docs/build/guides/storage/choosing-the-right-storage.mdx diff --git a/docs/learn/encyclopedia/storage/state-archival.mdx b/docs/learn/encyclopedia/storage/state-archival.mdx index ff101fb7b..fd90abae6 100644 --- a/docs/learn/encyclopedia/storage/state-archival.mdx +++ b/docs/learn/encyclopedia/storage/state-archival.mdx @@ -16,7 +16,7 @@ description: Smart contract state archival. Contract data is made up of three different types: `Persistent`, `Temporary`, and `Instance`. In a contract, these are accessed with `env.storage().persistent()`, `env.storage().temporary()`, and `env.storage().instance()` respectively; see the [`storage()` docs](https://docs.rs/soroban-sdk/latest/soroban_sdk/storage/struct.Storage.html). -Learn about choosing the right storage for your use case in this [How-To Guide](../../../build/guides/archival/choosing-the-right-storage.mdx) and other state archival related guides [here](../../../build/guides/archival). +Learn about choosing the right storage for your use case in this [How-To Guide](../../../build/guides/storage/choosing-the-right-storage.mdx) and other state archival related guides [here](../../../build/guides/archival). All contract data has a Time To Live (TTL) that must be periodically extended. If an entry's TTL is not periodically extended, the entry's TTL will eventually go to 0 and either become "archived" or permanently deleted depending on the storage type. Each type of storage functions similarly, but has different fees and archival behavior: From 6e163d7cf5c663a14c93c6b9287b843a3cf2b8ef Mon Sep 17 00:00:00 2001 From: Bri <92327786+briwylde08@users.noreply.github.com> Date: Wed, 21 Aug 2024 14:25:53 -0600 Subject: [PATCH 3/3] adding a couple of links --- docs/build/guides/tokens/stellar-asset-contract.mdx | 2 +- docs/learn/fundamentals/fees-resource-limits-metering.mdx | 2 ++ docs/tokens/stellar-asset-contract.mdx | 4 +++- 3 files changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/build/guides/tokens/stellar-asset-contract.mdx b/docs/build/guides/tokens/stellar-asset-contract.mdx index cad4cea73..4e8f0a055 100644 --- a/docs/build/guides/tokens/stellar-asset-contract.mdx +++ b/docs/build/guides/tokens/stellar-asset-contract.mdx @@ -4,7 +4,7 @@ hide_table_of_contents: true description: Test and use Stellar assets in a Stellar smart contract --- -When interacting with assets in a smart contract, the Stellar Asset Contract is not different from any other token that implements the Stellar [SEP-41 Token Interface]. +When interacting with assets in a smart contract, the [Stellar Asset Contract](../../../tokens/stellar-asset-contract.mdx) is not different from any other token that implements the Stellar [SEP-41 Token Interface]. ## Contract Code diff --git a/docs/learn/fundamentals/fees-resource-limits-metering.mdx b/docs/learn/fundamentals/fees-resource-limits-metering.mdx index 9e8eea830..961485df3 100644 --- a/docs/learn/fundamentals/fees-resource-limits-metering.mdx +++ b/docs/learn/fundamentals/fees-resource-limits-metering.mdx @@ -48,6 +48,8 @@ The implementation details for fee computation are provided by the following [li Find current resource fees in the [Resource Limits & Fees](../../networks/resource-limits-fees.mdx) page in the Networks section. +For help in analyzing smart contract cost and efficiency, see this [How-To Guide](../../build/guides/fees/analyzing-smart-contract-cost.mdx). + ### Refundable and non-refundable resource fees The resource fee is calculated with a non-refundable fees portion and a refundable fees portion: `ResourceFee(sorobanData.resourceFee) = Non-refundable resource fee + Refundable resource fees`. diff --git a/docs/tokens/stellar-asset-contract.mdx b/docs/tokens/stellar-asset-contract.mdx index c85e254c8..45fc8d3d9 100644 --- a/docs/tokens/stellar-asset-contract.mdx +++ b/docs/tokens/stellar-asset-contract.mdx @@ -1,7 +1,7 @@ --- sidebar_position: 50 title: Stellar Asset Contract -description: Use Stellar assets on Soroban. +description: Use Stellar assets in smart contracts --- @@ -16,6 +16,8 @@ description: Use Stellar assets on Soroban. The Stellar Asset Contract (SAC) is an implementation of [CAP-46-6 Smart Contract Standardized Asset] and [SEP-41 Token Interface] for Stellar [assets]. +See examples of how to use the SAC in the [Tokens How-To Guides](../build/guides/tokens/). + ## Overview :::note