How to use Chopsticks to have a mainnet fork of Polkadot/Kusama locally for OpenGov experiments. The developer docs can be found at https://acalanetwork.github.io/chopsticks/docs/ Requirements Basic understanding of how to use command line tools Know how to encode and decode extrinsics Prerequisites Install nodejs https://nodejs.org/en

Network: acala Error Mint aUSD On Account: min(Current Balance, Total Claim) Current Balance: Balance when running this script Before Balance: Balance before the incident #1638215 After Balance: Balance after the pause #1639493 Before Diff: Current Balance - Before Balance After Diff: Current Balance - After Balance Address: 23zjkju8pxHtm8b26ntsZHjWUaV3LNRc5YDoYAz6ZfVKHUmn

Acala supports EVM that allow people to deploy Solidity smart contracts. Please write a tutorial targeting existing Ethereum Solidity smart contract developers on how to deploy a smart contract to Acala using Remix. The tutorial should provide clear instructions for people to follow to Remix to build a smart contract and use Acala Contract UI to deploy and invoke the contract on Acala testnet. We do not have much documents yet so part of the challenge is figuring out the exact steps. Some useful information: Acala repo: https://github.com/AcalaNetwork/Acala Contract UI: https://acala-evm.vercel.app

Please create a set of steps to manage private keys with different criticalness, including steps to create, store (backup) and use them. Please include steps for low critical keys (insignificant damage if leaked or lost), medium level (significant damage if leaked or lost), and highly critical keys (should NEVER be leaked or lost). Please make the right balances between convenience and security. In the steps, also list the roles will be involved. e.g. DevOps can create and rotate low critical keys and Developer can access it. Multiple Executives will be involoved when creating highly critical keys. Example:

Last updated: 28/01/2020 Breaking changes: Enable CORS checks: #2248 #2291 Constify storage values and type parameter: #2565 #2883 #2975 #3112 #3093 #3191 Light client friendly events: #2491 New sessions module & remove consensus module: #2802 Transaction Dispatch Info / Weight: #2799 #4124 Implement a proper generic resolution in decl_storage!: #2913

--- tags: substrate --- # Fungible Token ## Abstract A cross-chain token standard is required for blockchains to transfer assets across the ecosystem and for clients (e.g. wallet, browser extension) to offer unified support of the token that provided by different chains. ## References - https://hackmd.io/gQKQGf42TeOODid3hM4_1w - https://eips.ethereum.org/EIPS/eip-20 - https://eips.ethereum.org/EIPS/eip-777 - https://eips.ethereum.org/EIPS/eip-1155 ## Description A fungible token is mainly

--- tags: substrate-course --- # Substrate 快速入门与实战 第六课 作业提示 ## 作业 - 重构 OwnedKitties 和 KittyLinkedItem - 支持泛型 - 单独的可重复使用的模块 ## 提示 - 作为一个可重用的模块，可以是一个单独的package，可以用 `cargo new package-name` 创建 - 但是这边简化下，一个单独的Rust module也是可以的。直接建立一个新的文件在src目录下就好，然后lib.rs文件里加上 `mod module_name;` 就可以引用了 - 优化的方向有两个，一个是这个LinkedItem目前只是针对于 `T::KittyIndex` 的，最好可以改成一个泛型，就可以支持不同的数据结构 - `struct LinkedItem<Item>` - 还有一个方向是现在的实现都是针对于 `OwnedKitties` 的，并不能重用。 - 这就需要有一个抽象支持不同的 `Storage` - 这个有几种方法，我这边提供个最通用的的方法的思路