User Experience (assumptions)
//
| Environment | RPC Endpoint |
|---|---|
| Turing Staging (Rococo) | rpc.turing-staging.oak.tech |
| Turing (Kusama) | rpc.turing.oak.tech |
| OAK (Polkadot) | Crowdloan launching soon! |
Parachain Requirements
The following requirements apply for any Kusama parachain that wishes to support cross-chain automation (including recurring payments, auto-compounding liquidity / staking rewards, automatic swaps, and more):
- Open bi-directional HRMP channels - HRMP Channels and You
-
Enable users to authorize future transactions powered by OAK using a proxy pallet and XCM origin converter.
2a. Proxy pallet implementation
2b. XCM converter implementation
2c. Get proxy accountId:
curl --location --request POST 'http:*//rpc.turing-staging.oak.tech' \* --header 'Content-Type: application/json' \ --data-raw '{"id":1, "jsonrpc":"2.0", "method": "xcmpHandler_crossChainAccount", "params": [""]}' \
Application Requirements [Extrinsics]
Fees
Up front payment is collected from the user’s account to schedule future task(s), including fees for a defined number of future occurrences. Fees for indefinitely recurring transactions may be paid at each occurrence. An RPC endpoint to retrieve the following Turing Network Fees will be delivered in October:
- The Turing inclusion fee to store the future extrinsic(s).
- The Turing execution fee when the future extrinsic(s) are triggered.
- The XCM fee to communicate future extrinsic(s) to a foreign chain (if applicable).