bstry
nimbus-eth1
Our great sponsors
bstry | nimbus-eth1 | |
---|---|---|
5 | 6 | |
17 | 551 | |
- | 0.2% | |
0.0 | 9.7 | |
over 3 years ago | 5 days ago | |
Nim | Nim | |
- | 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.
bstry
-
Abusing Monday.com's Project Manager As A Command & Control Server
I'm removing this post, just because it doesn't reach the quality standards of this subreddit. Anything can be a C&C, it's not new or novel nor interesting research. Sorry, we do welcome your posts though. I looked through the GitHub and something like https://github.com/1d8/bstry may be more appropriate.
- Tutorial On Coding Ransomware
- (Tutorial) Coding Ransomware
- Tutorial On Coding Ransomware In Nimlang
- Coding Ransomware In Nimlang - A Tutorial
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