Skip to content

Commit 4f5ca32

Browse files
committed
fix: minor fixes
1 parent 0c38cf0 commit 4f5ca32

File tree

1 file changed

+2
-2
lines changed
  • smart-contracts/precompiles

1 file changed

+2
-2
lines changed

smart-contracts/precompiles/xcm.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ categories: Smart Contracts
88

99
## Introduction
1010

11-
The [XCM (Cross-Consensus Message)](/develop/interoperability/intro-to-xcm){target=\_blank} precompile enables Polkadot Hub developers to access XCM functionality directly from their smart contracts using a Solidity interface.
11+
The [XCM (Cross-Consensus Message)](/parachains/interoperability/get-started/){target=\_blank} precompile enables Polkadot Hub developers to access XCM functionality directly from their smart contracts using a Solidity interface.
1212

1313
Located at the fixed address `0x00000000000000000000000000000000000a0000`, the XCM precompile offers three primary functions:
1414

@@ -140,6 +140,6 @@ By building and executing XCM programs, developers can build cross-chain applica
140140

141141
## Next steps
142142

143-
Head to the Polkadot Hub TestNet and start playing around with the precompile using Hardhat or Foundry.
143+
Head to the Polkadot Hub TestNet and start playing around with the precompile using [Hardhat](/smart-contracts/dev-environments/hardhat/get-started/){target=\_blank} or [Foundry](/smart-contracts/dev-environments/foundry/get-started/){target=\_blank}.
144144

145145
You can use PAPI to build XCM programs and test them with Chopsticks.

0 commit comments

Comments
 (0)