Skip to content

Commit 109747a

Browse files
committed
Remove unnecessary notes
1 parent cee2460 commit 109747a

2 files changed

Lines changed: 0 additions & 6 deletions

File tree

docs/api/xcmP.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,6 @@ The following guide guides you through the XCM SDK functionality implemented in
44
This functionality allows you to send XCM messages across the Paraverse.
55

66
### Package-less implementation of XCM API XCM features into your application
7-
```
8-
NOTES:
9-
- We recently introduced a new, much simpler way to implement XCM API! You can now request a hashed response to the built call, which will offlift you from parsing and work right away!
10-
- XCM API is now migrated to Polkadot API (PAPI), so PolkadotJS signers are no longer compatible!
11-
```
127

138
```ts
149
//Chain WS API instance that will send generated XCM Call

docs/api/xcmRouter.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,6 @@ Following section covers XCM Router implementation in LightSpell XCM API. Users
55
For list of supported chains/assets/dexes head over to [List of supported chains](https://paraspell.github.io/docs/supported.html#xcm-router%E2%98%84)
66

77
### Package-less implementation of XCM API Router features into your application
8-
```NOTE:``` We recently introduced new much simpler way to implement XCM API! You can now request hashed response of built call which offlifts you from parsing and works right away!
98

109
```ts
1110
export const submitTransaction = async (

0 commit comments

Comments
 (0)