asynctools
nimbus-eth1
asynctools | nimbus-eth1 | |
---|---|---|
1 | 6 | |
106 | 553 | |
- | 0.4% | |
2.3 | 9.7 | |
6 months ago | 2 days ago | |
Nim | Nim | |
MIT License | Apache License 2.0 |
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.
asynctools
-
Problems installing nimlsp with Mason
Cloning into '.'... From https://github.com/pmunch/nimlsp * tag v0.4.4 -> FETCH_HEAD + nimble build -y --localdeps Warning: Using project local deps mode Verifying dependencies for [email protected] Prompt: No local packages.json found, download it from internet? -> [forced yes] Downloading Official package list Success Package list downloaded. Installing jsonschema@>= 0.2.1 Downloading https://github.com/PMunch/jsonschema using git Verifying dependencies for [email protected] Installing ast_pattern_matching@any version Downloading https://github.com/nim-lang/ast-pattern-matching using git Verifying dependencies for [email protected] Installing [email protected] Success: ast_pattern_matching installed successfully. Installing [email protected] Success: jsonschema installed successfully. Installing asynctools@>= 0.1.1 Downloading https://github.com/cheatfate/asynctools using git Verifying dependencies for [email protected] Installing [email protected] Success: asynctools installed successfully. Building nimlsp/nimlsp_debug using c backend [1m/home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsppkg/suggestlib.nim(3, 18) [0m[31mError: [0mcannot open file: nimsuggest/nimsuggest[36m[0m[0m Tip: 30 messages have been suppressed, use --verbose to show them. Error: Build failed for package: nimlsp ... Execution failed with exit code 1 ... Command: /usr/bin/nim c --colors:on --noNimblePath -d:NimblePkgVersion=0.4.4 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/ast_pattern_matching-1.0.0 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/jsonschema-0.2.1 --path:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimbledeps/pkgs/asynctools-0.1.1 --hints:off -o:/home/terrior/.local/share/nvim/mason/.packages/nimlsp/nimlsp_debug /home/terrior/.local/share/nvim/mason/.packages/nimlsp/src/nimlsp_debug.nim spawn: bash failed with exit code 1 and signal 0.
nimbus-eth1
- Debunking the myth on the "controversial" RPi4 staker
-
Ask HN: Is Ethereum's Merge one of the biggest successes in Open Source?
It certainly seems it will be remembered as a major success story for open p2p protocols on the global Internet of our time.
A great multitude of developers and enthusiasts belonging or contributing to diverse teams spread across the world: developing, debating, and collaborating for years to arrive at the big event.
And it's all been done very much in the public view:
https://weekinethereumnews.com/
https://hackmd.io/@benjaminion/eth2_news
https://github.com/ethereum/pm
https://www.youtube.com/c/EthereumFoundation/videos
Consensus Clients:
https://github.com/sigp/lighthouse#readme
https://github.com/ChainSafe/lodestar#readme
https://github.com/status-im/nimbus-eth2#readme
https://github.com/prysmaticlabs/prysm#readme
https://github.com/ConsenSys/teku#readme
Execution Clients:
https://github.com/akula-bft/akula#readme
https://github.com/hyperledger/besu#readme
https://github.com/ledgerwatch/erigon#readme
https://github.com/ethereum/go-ethereum#readme
https://github.com/NethermindEth/nethermind#readme
https://github.com/status-im/nimbus-eth1#readme
-
Ask HN: Does the Ethereum foundation not develop a post-Merge client?
https://github.com/status-im/nimbus-eth1 (yes, this is also for eth2, see "About" at top right)
-
[AMA] We are the Go Ethereum (Geth) Team (18 August, 2022)
I expect we will see a "merged" client in the future. Nimbus could be the closest of anyone to this vision (nimbus-eth1, nimbus-eth2). Not sure when this will happen though. Anyways, you have to remember -- these are two extremely complicated pieces of software. Just the interface between the two has been developed and tests over the last 18 months. I think there will always need to be serious encapsulation of logic for it to be maintainable.
- How is web3 decentralised?
- Nimbus: An Ethereum 1.0 and 2.0 Client for Resource-Restricted Devices