substrate
tokio
substrate | tokio | |
---|---|---|
83 | 196 | |
8,348 | 24,677 | |
- | 1.5% | |
8.1 | 9.5 | |
8 months ago | 7 days ago | |
Rust | Rust | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
substrate
-
On Implementation of Distributed Protocols
Substrate — a framework for building application-specific blockchains (written in Rust);
-
build error because found duplicate lang item `panic_impl`
frame-benchmarking = { version = "4.0.0-dev", default-features = false, optional = true, git = "https://github.com/paritytech/substrate.git", branch = "polkadot-v1.0.0" }
-
What to do next... Web 3, Rust, Solidity?
To offer some perspective outside of the typical "all crypto is a scam", Parity is doing some cool stuff with a rust modular blockchain library called Substrate https://github.com/paritytech/substrate.
-
What application will make Rust its prime ?
Rust takes the cake in the blockchain space: Substrate, Cosmos (CosmWasm), and Solana. All of the zero knowledge cryptography libraries used for layer 2 solutions are written in Rust, compiling to Wasm (see arkworks, Risc0). Ethereum's next version of smart contracts will even use a restricted subset of Wasm ("Ewasm") instead of EVM.
-
Why am I not receiving staking rewards?
Verifying NPoS election solution graph and its score is a memory-intensive operation that needs to be performed within a single block time. Under the current runtime constraints, a solution graph with 22,500 nominators can be verified well within the block production time on Polkadot. There are plans to improve on this and implement multi-block election solution verification, after which, the NPoS system can scale to incorporate more nominators.
- Fast-unstake is now available on Kusama. This allows instant unstaking if you have not participated in staking in the last 28 eras.
-
Polkadot Digest 17 Jan 2023
Fast-unstake is now available on Kusama. This allows instant unstaking if you have not participated in staking in the last 28 eras. https://github.com/paritytech/substrate/pull/12129
-
Polkadot Digest 11 Jan 2023
First, any outstanding multisig calls (ones where one signatory has signed, but not the threshold) will not be able to execute. Please either finish your multisig calls before this upgrade, or wait until after it is completed. https://github.com/paritytech/substrate/pull/12072
- pallet dev mode added to make dev easier
-
Substrate Rresources
Github: https://github.com/paritytech/substrate
tokio
-
On Implementation of Distributed Protocols
Being able to control nondeterminism is particularly useful for testing and debugging. This allows creating reproducible test environments, as well as discrete-event simulation for faster-than-real-time simulation of time delays. For example, Cardano uses a simulation environment for the IO monad that closely follows core Haskell packages; Sui has a simulator based on madsim that provides an API-compatible replacement for the Tokio runtime and intercepts various POSIX API calls in order to enforce determinism. Both allow running the same code in production as in the simulator for testing.
-
I pre-released my project "json-responder" written in Rust
tokio / hyper / toml / serde / serde_json / json5 / console
-
Cryptoflow: Building a secure and scalable system with Axum and SvelteKit - Part 0
tokio - An asynchronous runtime for Rust
-
Top 10 Rusty Repositories for you to start your Open Source Journey
3. Tokio
-
API Gateway, Lambda, DynamoDB and Rust
The AWS SDK makes use of the async capabilities in the Tokio library. So when you see async in front of a fn that function is capable of executing asynchronously.
-
The More You Gno: Gno.land Monthly Updates - 6
Petar is also looking at implementing concurrency the way it is in Go to have a fully functional virtual machine as it is in the spec. This would likely attract more external contributors to developing the VM. One advantage of Rust is that, with the concurrency model, there is already an extensive library called Tokio which he can use. Petar stresses that this isn’t easy, but he believes it’s achievable, at least as a research topic around determinism and concurrency.
-
Consuming an SQS Event with Lambda and Rust
Another thing to point out is that async is a thing in Rust. I'm not going to begin to dive into this paradigm in this article, but know it's handled by the awesome Tokio framework.
-
netcrab: a networking tool
So I started by using Tokio, a popular async runtime. The docs and samples helped me get a simple outbound TCP connection working. The Rust async book also had a lot of good explanations, both practical and digging into the details of what a runtime does.
-
Thread-per-Core
Regarding the quote:
> The Original Sin of Rust async programming is making it multi-threaded by default. If premature optimization is the root of all evil, this is the mother of all premature optimizations, and it curses all your code with the unholy Send + 'static, or worse yet Send + Sync + 'static, which just kills all the joy of actually writing Rust.
Agree about the melodramatic tone. I also don't think removing the Send + Sync really makes that big a difference. It's the 'static that bothers me the most. I want scoped concurrency. Something like <https://github.com/tokio-rs/tokio/issues/2596>.
Another thing I really hate about Rust async right now is the poor instrumentation. I'm having a production problem at work right now in which some tasks just get stuck. I wish I could do the equivalent of `gdb; thread apply all bt`. Looking forward to <https://github.com/tokio-rs/tokio/issues/5638> landing at least. It exists right now but is experimental and in my experience sometimes panics. I'm actually writing a PR today to at least use the experimental version on SIGTERM to see what's going on, on the theory that if it crashes oh well, we're shutting down anyway.
Neither of these complaints would be addressed by taking away work stealing. In fact, I could keep doing down my list, and taking away work stealing wouldn't really help with much of anything.
-
PHP-Tokio – Use any async Rust library from PHP
The PHP <-> Rust bindings are provided by https://github.com/Nicelocal/ext-php-rs/ (our fork of https://github.com/davidcole1340/ext-php-rs with a bunch of UX improvements :).
php-tokio's integrates the https://revolt.run event loop with the https://tokio.rs event loop; async functionality is provided by the two event loops, in combination with PHP fibers through revolt's suspension API (I could've directly used the PHP Fiber API to provide coroutine suspension, but it was a tad easier with revolt's suspension API (https://revolt.run/fibers), since it also handles the base case of suspension in the main fiber).
What are some alternatives?
cosmos-sdk - :chains: A Framework for Building High Value Public Blockchains :sparkles:
async-std - Async version of the Rust standard library
developer-roadmap - Interactive roadmaps, guides and other educational content to help developers grow in their careers.
Rocket - A web framework for Rust.
polygon-edge - A Framework for Building Ethereum-compatible Blockchain Networks
hyper - An HTTP library for Rust
manim - Animation engine for explanatory math videos
futures-rs - Zero-cost asynchronous programming in Rust
polkadot - Polkadot Node Implementation
smol - A small and fast async runtime for Rust
rust-analyzer - A Rust compiler front-end for IDEs
rayon - Rayon: A data parallelism library for Rust