Skip to content

Commit

Permalink
fix links
Browse files Browse the repository at this point in the history
  • Loading branch information
eshaben committed Oct 2, 2024
1 parent 056c4c6 commit 7a548b2
Show file tree
Hide file tree
Showing 10 changed files with 10 additions and 10 deletions.
2 changes: 1 addition & 1 deletion builders/build/templates/custom-runtime.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Already existing Substrate runtimes need to at least have both [Cumulus](#adding

Nevertheless, teams might have already implemented certain modules that can collide with some functionalities related to Tanssi, for example, block production, block authority assignment, and consensus.

If the starting point for your project was the [parachain template](https://github.com/substrate-developer-hub/substrate-parachain-template){target=\_blank}, the following modules are included by default and must be removed along with their corresponding configuration:
If the starting point for your project was the [parachain template](https://github.com/paritytech/polkadot-sdk-parachain-template){target=\_blank}, the following modules are included by default and must be removed along with their corresponding configuration:

```rust
Authorship: pallet_authorship = 20,
Expand Down
2 changes: 1 addition & 1 deletion builders/build/templates/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: Tanssi includes templates to kick-start the development of an appch

Appchains deployed through Tanssi are essentially parachains within the Polkadot ecosystem that are capable of interacting with the relay chain and other parachains. They also contain the necessary functionalities to support the Tanssi protocol.

As presented in the [Included Templates](/learn/tanssi/included-templates#baseline-appchain-template){target=\_blank} from the Learn section, Tanssi already provides two templates to jumpstart the development process:
As presented in the [Included Templates](/learn/tanssi/included-templates/#baseline-appchain-template){target=\_blank} from the Learn section, Tanssi already provides two templates to jumpstart the development process:

- **[Baseline Tanssi appchain template](/learn/tanssi/included-templates/#baseline-appchain-template){target=\_blank}** - a template that provides the basic platform to start adding custom logic in a Substrate-based Tanssi appchain
- **[Baseline Tanssi EVM (Ethereum Virtual Machine) appchain template](/learn/tanssi/included-templates/#baseline-evm-template){target=\_blank}** - a template that provides full Ethereum compatibility
Expand Down
2 changes: 1 addition & 1 deletion builders/manage/dapp/services-payment.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: Appchains deployed through Tanssi benefit from block production ser

## Introduction {: #introduction }

As presented in the [Block Production as a Service](/learn/tanssi/technical-features#services-payments){target=_\blank} article, there are two main costs associated that the appchain governor must cover:
As presented in the [Block Production as a Service](/learn/tanssi/technical-features/#services-payments){target=_\blank} article, there are two main costs associated that the appchain governor must cover:

- **Block producers assignment** - for the assignment of block producers by the Tanssi protocol, which happens once per session
- **Block production** - for each block that is produced on the appchain's behalf
Expand Down
2 changes: 1 addition & 1 deletion builders/toolkit/ethereum-api/libraries/viem.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ npx tsc --init

## Set Up a viem Client (Provider) {: #setting-up-a-viem-provider }

Throughout this guide, you'll be creating a bunch of scripts that provide different functionality, such as sending a transaction, deploying a contract, and interacting with a deployed contract. In most of these scripts, you'll need to create a [viem client](https://docs.ethers.org/v6/api/providers){target=\_blank} to interact with the network.
Throughout this guide, you'll be creating a bunch of scripts that provide different functionality, such as sending a transaction, deploying a contract, and interacting with a deployed contract. In most of these scripts, you'll need to create a [viem client](https://docs.ethers.org/v6/api/providers/){target=\_blank} to interact with the network.

You can create a viem client for reading chain data, like balances or contract data, using the `createPublicClient` function, or you can create a viem client for writing chain data, like sending transactions, using the `createWalletClient` function.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ keywords: solidity, ethereum, native, token, moonbeam, precompiled, contracts, a

## Introduction {: #introduction }

As presented in the [Native Cross-Chain Communication](/learn/framework/xcm){target=\_blank} article, appchains deployed through Tanssi can communicate and interoperate with any other appchain in the ecosystem. This multi-chain environment leads to a multi-asset world, where seamless transfer of assets, data, and value across different networks widens the possibilities to build use cases across diverse industries such as finance (DeFi), real-world assets (RWAs), and others.
As presented in the [Native Cross-Chain Communication](/learn/framework/xcm/){target=\_blank} article, appchains deployed through Tanssi can communicate and interoperate with any other appchain in the ecosystem. This multi-chain environment leads to a multi-asset world, where seamless transfer of assets, data, and value across different networks widens the possibilities to build use cases across diverse industries such as finance (DeFi), real-world assets (RWAs), and others.

External assets are tokens native to another blockchain, or, in other words, assets whose reserve chain is not the chain you are interacting with. Tanssi appchains can register external assets to enable their inflow. To do so, it is necessary to [establish an XCM channel](/learn/framework/xcm/#channel-registration){target=\_blank} with the other chain and then register one of its native assets as an external asset. Registered external assets behave, to some extent, the same way as local ones.

Expand Down
2 changes: 1 addition & 1 deletion builders/toolkit/ethereum-api/wallets/talisman.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: This guide walks you through how to connect Talisman, a comprehensi

Developers and users of Tanssi EVM appchains have a variety of options when it comes to wallets. Thanks to their seamless Ethereum compatibility, Tanssi EVM appchains support a great variety of popular wallets, such as Talisman.

Talisman is a Web3 wallet that natively supports Substrate (Polkadot) and Ethereum accounts. This tutorial centers on the Ethereum API, but you can check out a similar [tutorial for interacting with Talisman using the Substrate API](/builders/toolkit/substrate-api/wallets/talisman/){target=\_blank}. The Talisman wallet browser extension is available on [Google Chrome](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank}, [Brave](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank}, and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/talisman-wallet-extension){target=\_blank}, and a corresponding asset dashboard is accessible at [app.talisman.xyz](https://app.talisman.xyz){target=\_blank}
Talisman is a Web3 wallet that natively supports Substrate (Polkadot) and Ethereum accounts. This tutorial centers on the Ethereum API, but you can check out a similar [tutorial for interacting with Talisman using the Substrate API](/builders/toolkit/substrate-api/wallets/talisman/){target=\_blank}. The Talisman wallet browser extension is available on [Google Chrome](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank} and [Brave](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank}, and a corresponding asset dashboard is accessible at [app.talisman.xyz](https://app.talisman.xyz){target=\_blank}

This guide takes you through all the necessary steps, from installing Talisman to setting up a wallet, connecting it to your Tanssi EVM appchain, and sending funds.

Expand Down
2 changes: 1 addition & 1 deletion builders/toolkit/substrate-api/wallets/talisman.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ description: This guide walks you through how to connect Talisman, a Polkadot, S

Developers and users of Tanssi Substrate appchains have a variety of options when it comes to wallets. Talisman is a great option, as it provides full native support for both Substrate and Ethereum accounts. This guide focuses on the Substrate API. You can also check out a [similar guide for configuring Talisman for use with your Tanssi EVM appchain](/builders/toolkit/ethereum-api/wallets/talisman/){target=\_blank}.

Talisman is a Web3 wallet that natively supports Substrate (Polkadot) and Ethereum accounts. The Talisman wallet browser extension is available on [Google Chrome](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank}, [Brave](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank}, and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/talisman-wallet-extension){target=\_blank}, and a corresponding asset dashboard is accessible at [app.talisman.xyz](https://app.talisman.xyz){target=\_blank}
Talisman is a Web3 wallet that natively supports Substrate (Polkadot) and Ethereum accounts. The Talisman wallet browser extension is available on [Google Chrome](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank} and [Brave](https://chrome.google.com/webstore/detail/talisman-polkadot-wallet/fijngjgcjhjmmpcmkeiomlglpeiijkld){target=\_blank}, and a corresponding asset dashboard is accessible at [app.talisman.xyz](https://app.talisman.xyz){target=\_blank}

This guide takes you through all the necessary steps, from installing Talisman to setting up a wallet, connecting it to your Tanssi Substrate appchain, and sending funds.

Expand Down
2 changes: 1 addition & 1 deletion learn/framework/modules.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ In addition to those previously listed, other modules like [identity](https://pa

Developers creating new modules enjoy complete freedom to express any desired behavior in the core logic of the blockchain, like exposing new transactions, storing sensible information, and validating and enforcing business logic.

As explained in the [Architecture](/learn/framework/architecture#client-runtime-communication){target=\_blank} article, a module needs to be able to communicate with the core client by exposing and integrating with a very specific API that allows the runtime to expose transactions, access storage, and code and decode information stored on-chain. It also needs to include many other required wiring codes that make the module work in the node.
As explained in the [Architecture](/learn/framework/architecture/#client-runtime-communication){target=\_blank} article, a module needs to be able to communicate with the core client by exposing and integrating with a very specific API that allows the runtime to expose transactions, access storage, and code and decode information stored on-chain. It also needs to include many other required wiring codes that make the module work in the node.

To improve developer experience when writing modules, Substrate relies heavily on [Rust macros](https://doc.rust-lang.org/book/ch19-06-macros.html){target=\_blank}. Macros are special instructions that automatically expand to Rust code just before compile-time, allowing modules to keep up to seven times the amount of code out of sight of the developers. This allows developers to focus on the specific functional requirements when writing modules instead of dealing with technicalities and the necessary scaffolding code.

Expand Down
2 changes: 1 addition & 1 deletion learn/tanssi/included-templates.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,7 +39,7 @@ As presented in the [Overview](/learn/tanssi/overview/){target=\_blank} article,

As a sibling chain of the other members of the ecosystem (like the Tanssi network itself), they must include the necessary behavior to implement their consensus mechanism and be able to interact and synchronize with Polkadot's relay chain.

The Baseline Tanssi appchain Template is based on the [Substrate Parachain Template](https://github.com/substrate-developer-hub/substrate-parachain-template){target=\_blank} featuring [Cumulus](https://github.com/paritytech/polkadot-sdk/tree/master/cumulus){target=\_blank} SDK, which includes all the required functionality for the block producers logic, p2p, database, and synchronization layers between the appchain and the relay chain, making the integration of a new appchain into the Polkadot ecosystem a breeze.
The Baseline Tanssi appchain Template is based on the [Polkadot SDK Parachain Template](https://github.com/paritytech/polkadot-sdk-parachain-template){target=\_blank} featuring [Cumulus](https://github.com/paritytech/polkadot-sdk/tree/master/cumulus){target=\_blank} SDK, which includes all the required functionality for the block producers logic, p2p, database, and synchronization layers between the appchain and the relay chain, making the integration of a new appchain into the Polkadot ecosystem a breeze.

This template also includes Tanssi's [Author Noting](https://github.com/moondance-labs/tanssi/blob/master/pallets/author-noting/src/lib.rs){target=\_blank} pallet, which implements the logic for retrieving and validating the set of block producers assigned to provide block production services to the appchain. It also includes logic that allows a block producer to sign the block when the consensus mechanism determines that it is the block producer's turn to produce the block (and thus be rewarded accordingly).

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ To follow along with this tutorial, you will need to have:
- Create or have two accounts accessible in Polkadot.js Apps
- Both accounts will need to be funded with `DANCE` tokens, and the block producer account will need at least `{{ networks.dancebox.block_producers.min_self_del.dance }}` `DANCE`

If you need help importing your accounts into Polkadot.js Apps, please check out the [Connecting to Polkadot.js](/builders/toolkit/substrate-api/wallets/talisman#connecting-to-polkadotjs){target=\_blank} guide.
If you need help importing your accounts into Polkadot.js Apps, please check out the [Connecting to Polkadot.js](/builders/toolkit/substrate-api/wallets/talisman/#connecting-to-polkadotjs){target=\_blank} guide.

## Creating a Staking Proxy Account {: #creating-a-staking-proxy-account }

Expand Down

0 comments on commit 7a548b2

Please sign in to comment.