XCM format: https://github.com/paritytech/polkadot/blob/master/xcm/src/v2/mod.rs
WASM_TARGET_DIRECTORY="$(pwd)" make build-full
https://github.com/substrate-developer-hub/substrate-pallet-template
https://www.shawntabrizi.com/substrate-js-utilities/codec/
https://szulborski.eu/wymiana-kluczy-ssh-na-ed25519/
Book: https://w3f.github.io/parachain-implementers-guide/whence-parachains.html
https://w3f.github.io/parachain-implementers-guide/protocol-overview.html
https://github.com/substrate-developer-hub/awesome-substrate
https://github.com/open-web3-stack/open-runtime-module-library
!! https://decoded.polkadot.network/2021submission
https://en.wikipedia.org/wiki/Diffie%E2%80%93Hellman_key_exchange
Parachain's logic is encoded by wasm blob. Compiling and executing it can be time consuming. There is an interest in sandboxing the execution pipeline. Specifically, in the number of physical memory consumed. There is RLIMIT_RSS but that was retired long time ago. A mechanism like cgroups can help with this. cgroups can be v1 and v2. We would like to know, should we focus on one of those or do we need both. v2 adoption speed in general is quite slow.
That's not the primary reason why I am asking though. The question of what kernel versions are in the wild is already popped up a few times before. This is because it is generally useful to know what kind of Linux features we can or cannot target.
https://man7.org/linux/man-pages/man2/userfaultfd.2.html
https://www.redhat.com/sysadmin/cgroups-part-one
- open-web3-stack/open-runtime-module-library#8
- open-web3-stack/open-runtime-module-library#73
- open-web3-stack/open-runtime-module-library#98
- open-web3-stack/open-runtime-module-library#194
- open-web3-stack/open-runtime-module-library#265
https://doc.rust-lang.org/stable/rust-by-example/
https://github.com/rust-lang/rustlings
https://github.com/SubstrateDevAcademy
https://rust-analyzer.github.io/ (The Matklad)
https://github.com/SubstrateCourse/
https://substrate.dev/recipes/runtime-printing.html#printing-from-the-runtime