Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix broken links xcm pages #5389

Merged
merged 2 commits into from
Nov 29, 2023
Merged

Fix broken links xcm pages #5389

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7f1d7d3
minor edit test
filippoweb3 Nov 29, 2023
526ed89
fixed broken links
filippoweb3 Nov 29, 2023
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
4 changes: 2 additions & 2 deletions docs/learn/xcm/fundamentals/weight_and_fees.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,12 +35,12 @@ instructions. We'll talk more about `BuyExecution` in the
XCM is agnostic, which means it doesn't assume fees need to be paid. It's entirely possible to not
pay for the effects of an XCM on the destination system. Even in systems where fees have to be paid,
special cases of free execution can be made. There are security measures systems can put in place
(see [barrier](../executor_config/index.html#barrier)) to not execute XCMs that do not pay for their
(see [barrier](../executor_config/config.md#barrier)) to not execute XCMs that do not pay for their
fees.

## Executor config

The executor has a `Weigher` [configuration item](../executor_config/index.html#weigher) that
The executor has a `Weigher` [configuration item](../executor_config/config.md#weigher) that
specifies the weight of each instruction. It weighs the whole message by adding the weight of each
instruction. A simple way of weighing instructions is to assign them a base weight value to all of
them. This works, but it is not very accurate, as different instructions use more resources when
Expand Down
6 changes: 3 additions & 3 deletions docs/learn/xcm/journey/transact.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ The Transact instruction has three fields. The `origin_kind` is of type
[OriginKind](https://paritytech.github.io/polkadot/doc/xcm/v2/enum.OriginKind.html) and specifies
how the origin of the call should be interpreted. In the xcm-executor, the `origin_kind` is used to
determine how to convert a `MultiLocation` origin into a `RuntimeOrigin`. For more information,
check out the [xcm-executor config docs](../executor_config/index.html).
check out the [xcm-executor config docs](../executor_config/config.md).

The `require_weight_at_most` field tells the XCVM executing the call how much
[weight](../fundamentals/weight_and_fees.md) it can use. If the call uses more weight than the
Expand Down Expand Up @@ -75,9 +75,9 @@ In this section, we quickly look at how the XCM executor executes the `Transact`
It executes, among other things, the following steps:

1. Decode the call field into the actual call that we want to dispatch.
2. Check with the [SafeCallFilter](../executor_config/index.html#safecallfilter) on whether the
2. Check with the [SafeCallFilter](../executor_config/config.md#safecallfilter) on whether the
execution of this call is allowed.
3. Use the [OriginConverter](../executor_config/index.html#originconverter) to convert the
3. Use the [OriginConverter](../executor_config/config.md#originconverter) to convert the
`MultiLocation` origin into a `RuntimeOrigin`.
4. Check whether the call weight does not exceed `require_weight_at_most`.
5. Dispatch the call with the converted origin and set the `transact_status` register to be the
Expand Down
Loading