
Ethereum represents the gateway to a worldwide, decentralized computing paradigm. This platform enables you to run decentralized applications (DApps) and smart contracts that have no central points of failure or control, integrate with a payment network, and operate on an open blockchain. With this practical guide, Andreas M. Antonopoulos and Gavin Wood provide everything you need to know about building smart contracts and DApps on Ethereum and other virtual-machine blockchains.

Discover why IBM, Microsoft, NASDAQ, and hundreds of other organizations are experimenting with Ethereum. This essential guide shows you how to develop the skills necessary to be an innovator in this growing and exciting new industry.

A guide to the operation and use of Ethereum and other EVM-compatible blockchains.

Mastering Ethereum


The story of the idealists, technologists, and opportunists fighting to bring cryptocurrency to the masses.

In their short history, Bitcoin and other cryptocurrencies have gone through booms, busts, and internecine wars, recently reaching a market valuation of more than $2 trillion. The central promise of crypto endures—vast fortunes made from decentralized networks not controlled by any single entity and not yet regulated by many governments.

The recent growth of crypto would have been all but impossible if not for a brilliant young man named Vitalik Buterin and his creation: Ethereum. In this book, Laura Shin takes readers inside the founding of this novel cryptocurrency network, which enabled users to launch their own new coins, thus creating a new crypto fever. She introduces readers to larger-than-life characters like Buterin, the Web3 wunderkind; his short-lived CEO, Charles Hoskinson; and Joe Lubin, a former Goldman Sachs VP who became one of crypto’s most well-known billionaires. Sparks fly as these outsized personalities fight for their piece of a seemingly limitless new business opportunity.

This fascinating book shows the crypto market for what it really is: a deeply personal struggle to influence the coming revolution in money, culture, and power.

Idealism, Greed, Lies, and the Making of the First Big Cryptocurrency Craze

The Cryptopians


Tokens - often referred to as cryptocurrencies - can represent anything from an asset to an access right, such as gold, diamonds, a fraction of a Picasso painting or an entry ticket to a concert. Tokens could also be used to reward social media contributions, incentivize the reduction of CO2 emissions, or even ones attention for watching an ad. While it has become easy to create a token, which is collectively managed by a public Web3 infrastructure like a blockchain network, the understanding of how to apply these tokens is still vague.

The industry keeps referring to “Blockchain” as different from “Bitcoin,” creating an artificial divide that is often misleading. There seems to be too little understanding about the fact that Bitcoin is a blockchain network, which is (a) globally managed by people who mostly do not know each other, and (b) enabled by the consensus protocol that (c) incentivizes all network actors for their contributions with a native token. The governance rules are tied to the minting of a native blockchain token. The Bitcoin token can, therefore, be seen as the currency of a distributed Internet tribe, called the Bitcoin network, where network actors are rewarded with Bitcoins, just as the Ether is the currency of the distributed Internet tribe Ethereum network, or Sia is the native currency of the Sia network. The Bitcoin network and other distributed ledgers all represent a collectively maintained public infrastructure and are the backbone of the next generation Internet, what the crypto community refers to as the Web3.

This book attempts to summarize existing knowledge about blockchain networks and other distributed ledgers as the backbone of the Web3, and contextualize the socio-economic implications of the Web3 applications such as smart contracts, tokens, and DAOs to the concepts of money, economics, governance and decentralized finance (DeFi).

Token Economy


Learn to Code Blockchain DApps By Building Simple Games

CryptoZombies is an interactive school that teaches you all things technical about blockchains. Learn to make smart contracts in Solidity or Libra by making your own crypto-collectibles game.

#1 Solidity Tutorial & Ethereum Blockchain Programming Course

CryptoZombies


More and more DeFi projects on Ethereum are getting hacked. This is your chance to join the party.

Each challenge can be considered standalone. Depending on the challenge, you should either stop the system from working, steal as much funds as you can, or do some other unexpected things.

Put your black hat on, and break some DeFi projects on Ethereum!

Damn Vulnerable DeFi


This is an interactive tutorial website for learning Vyper while building games using smart contracts, similar to Cryptozombies.

VyperFun


Blockchain is an exciting new discipline in Computer Science. It combines a wide array of skills from math and cryptography to social sciences and understanding organizations. Understanding blockchain decentralization and how/where to apply it is a brand new skill that very few have mastered.

You will build your skills from the ground up with strong fundamentals that will provide you with the ability to adapt in this rapidly evolving ecosystem.

Choose From Multiple Paths to Begin Your Ethereum Coding Journey.

Fast-track your Ethereum Developer career in an instructor-led and challenging bootcamp focused on discussion and application!

ChainShot


This is an initiative for the early solidity developers by those who were early developers sometime.

In this approach, we are looking to categorize the smart contract according to the difficulty level in multiple standards. For now, we are keeping the standard 0 to 5(can be discussed).

This initiative needs great support from Blockchain enthusiast, developer and researchers to build this school in a way which can attract learners and provide them ease for development.

First place for early developers to learn Solidity 

solidity-school


## Introductory Modules

- What is a SNARK?
- Building a SNARK (part 1)
- Building a SNARK (part 2)

## Whiteboard Sessions with ZK Projects​

- SNARKs vs. STARKS with Brendan and Bobbin
- PLONK and Custom Gates with Adrian Hamelink
- Lookup Arguments for Performance Optimisation with Mary Maller
- Zero Knowledge Virtual Machine (zkVM) with grjte
- Achieving Decentralised Private Computation with Pratyush Mishra
- Introduction to zkRollups with Barry Whitehat
- zkEVM with Jordi Baylina
- ZK Swaps with Henry de Valence
- zkID with Oleksandr Brezhniev
- Fast Recursion with Plonky2 with William Borgeaud

ZK Whiteboard Sessions is an educational series on all things zero knowledge

ZK Whiteboard Sessions


## What is a smart contract?

Smart contracts are the backbone of decentralized applications (DApps) and Web3. A smart contract is a simple program that lives on a blockchain network (such as Ethereum). They're actually not that smart. And nothing like a (legal) contract. They’re more like an executable piece of code that requires input or an trigger from an external source. They can validate those input conditions and if correct, execute their own logic to update the state on a blockchain.

## Benefits

They often serve the following purposes:
- Store and maintain data
- Manage relationships with users, or other contracts

Benefits of smart contracts are
- Immutable - once deployed none can change them
- Composable - they’re public and anyone can interact with them, or build on top of them. Much like public APIs

## Resources

The following resources have been the most popular resources on the site for a long time. These are all highly recommend to start learning about Solidity


### 1. Official Solidity website
The most obvious resources is ofcourse the official website and documentation of the Solidity team itself. The Solidity team covers all the core concepts and fundamentals of Solidity and smart contracts in general. Highly recommended

https://soliditylang.org/


### 2. Solidity by Example
The second one on the list is Solidity by Example. A great collection of more pratical examples, incl. source code and supporting videos.

https://solidity-by-example.org/


### 3. CryptoZombies 
CryptoZombies is an interactive school that teaches you all things technical about blockchains. A fun and interactive way to write smart contracts in Solidity by making your own crypto-collectibles game.

https://cryptozombies.io/


### 4. Speedrun Ethereum

Speedrun Ethereum helps you get to the next level. It teaches you how to build on Ethereum; the superpowers and the gotchas while you build up your Web3 portfolio. If you like this, also make sure to check out the other work of the amazing [Austin Griffith](https://twitter.com/austingriffith) such as [ETH-build](https://eth.build/) and [Scaffold-eth](https://scaffoldeth.io/).

https://speedrunethereum.com/


### 5. Smart Contract Best Practices 

Smart contracts are complex instruments that have the authority to allocate high-value resources between complex systems. Often working autonomously. With huge financial loss at risk. This makes them critical components in these systems. Development of such components requires thoughtful design, solid engineering practices, rigorous testing and a strong security mindset. This document provides a baseline knowledge of security considerations.

https://consensys.github.io/smart-contract-best-practices/


## Other resources

If you'd like to read more, make sure to checkout all the other [Solidity](/tags/smart%20contracts) resources on the site.

Solidity is a programming language designed for developing smart contracts that run on Ethereum. It's the most in demand skill in the Web3 space. These are the best resources to help you learn more about it.

Best resources to learn Solidity


This handbook is for people who are interested in exploring the vision behind “Web3”, and who wish to acquire in-demand skills that are essential to realizing that vision.  

A Handbook for Smart Contract Development

Learn Solidity

Free resources to learn about Zero Knowledge Proofs (ZKPs) and Cryptography

Road to ZK


Create Eth App supports multiple frontend frameworks. It comes with a host of decentralized finance templates pre-filled with contract ABIs, addresses and subgraphs. Everything you need to build a modern Ethereum-powered single-page app.

- Learning how to write Ethereum-powered apps in a comfortable and feature-rich development environment.
- Starting new Ethereum-powered single-page React applications without wasting time on copy-pasting boilerplates
- Creating examples with React for your Ethereum-related libraries and components.

Create Ethereum-powered apps with one command

Create Eth App


**Features**
- Next.js
- Ethereum
- Typescript
- Chakra UI
- Wagmi
- Connectkit
- Ethers.js

An open-source Next.js + Ethereum starter kit to quickly ship Web3 Apps

Nexth Starter kit


Everything you need to build on Ethereum!

Quickly experiment with Solidity using a frontend that adapts to your smart contract

Forkable Ethereum dev stack focused on fast product iterations

Scaffold-ETH


Becoming a blockchain engineer is the most fun, rewarding, and exhilarating choice I’ve and my colleagues have ever made. And we’ve already blazed the trail for you to get started! In this article, we will show you exactly how to learn to become a blockchain engineer, from beginner to professional.

Spoiler alert, here is the exact blueprint we are going to cover to get you to a successful blockchain engineer:

1. Understand why you should become a blockchain engineer
2. Take a Blockchain Course
3. Join a Hackathon, the Community, & Build
4. Start your own protocol, Take a job, Freelance & Contribute

If you make it this far, you’ve done it! Although, I’ll add a bonus step 5 that we will talk about soon.

5. You’ve made it! Keep learning!

That’s it! These are the exact steps you need to take to become a blockchain engineer!

Become a blockchain, solidity, and smart contract engineer by following these steps

Become a Blockchain Engineer


Odds are you’ve heard about the Ethereum blockchain, whether or not you know what it is. It’s been in the news a lot lately, including the cover of some major magazines, but reading those articles can be like gibberish if you don’t have a foundation for what exactly Ethereum is. So what is it? In essence, a public database that keeps a permanent record of digital transactions. Importantly, this database doesn’t require any central authority to maintain and secure it. Instead it operates as a “trustless” transactional system — a framework in which individuals can make peer-to-peer transactions without needing to trust a third party OR one another.

Still confused? That’s where this post comes in. My aim is to explain how Ethereum functions at a technical level, without complex math or scary-looking formulas. Even if you’re not a programmer, I hope you’ll walk away with at least better grasp of the tech. If some parts are too technical and difficult to grok, that’s totally fine! There’s really no need to understand every little detail. I recommend just focusing on understanding things at a broad level.

Many of the topics covered in this post are a breakdown of the concepts discussed in the yellow paper. I’ve added my own explanations and diagrams to make understanding Ethereum easier. Those brave enough to take on the technical challenge can also read the Ethereum yellow paper.

Many of the topics covered in this post are a breakdown of the concepts discussed in the yellow paper. I’ve added my own explanations and diagrams to make it easier.

How does Ethereum work, anyway?


I recently joined Edge & Node as a Developer Relations Engineer and have been diving deeper into smart contract development with Ethereum. I have settled upon what I think is the best stack for building full stack dApps with Solidity:

▶︎ Client Framework - React
▶︎ Ethereum development environment - Hardhat
▶︎ Ethereum Web Client Library - Ethers.js
▶︎ API layer - The Graph Protocol

Building Full Stack dApps with React, Ethers.js, Solidity, and Hardhat

The Complete Guide to Full Stack Ethereum Development


Educational sandbox for building on web3. Visually understand how Ethereum works by doing.

ETH.Build


https://www.youtube.com/watch?v=gyMwXuJrbJQ

This course will give you a full introduction into all of the core concepts in blockchain, smart contracts, solidity, NFTs/ERC721s, ERC20s, Coding Decentralized Finance (DeFi), javascript and solidity, Chainlink, Ethereum, upgradable smart contracts, and full stack blockchain development.   

Some of the technologies covered are:
- The Graph
- Chainlink
- Metamask
- Alchemy
- Remix
- Hardhat
- Solidity
- Openzeppelin
- Trail of Bits
- Ganache
- Ethers
- Etherscan
- Coinmarketcap
- Aave
- IPFS
- Fleek.hq
- Filecoin
- NextJS
- Moralis
- Web3uikit
- Opensea
- Pinata
- Nft.storage

 And more!

Follow along with the videos and you'll be a blockchain wizard in no time!  💻 The repository with helpful links to all code, resources, and support forums is located here: https://github.com/smartcontractkit/full-blockchain-solidity-course-js.

This course will give you a full introduction into all of the core concepts related to blockchain, smart contracts, Solidity, ERC20s, full-stack Web3 dapps, decentralized finance (DeFi), JavaScript, TypeScript, Chainlink, Ethereum, upgradable smart contracts, DAOs, the graph, moralis, aave, IPFS, and more. Follow along with the videos and you'll be a blockchain wizard in no time!

Learn Blockchain, Solidity, and Full Stack Web3 Development with JavaScript – 32-Hour Course


Learning Solidity with a collection of YouTube videos and example code.

Learning Solidity


Here we collect and discuss the best DeFi & Blockchain researches and tools 

DeFi Developer roadmap


Nowadays there are countless well-made resources on how to learn blockchain development of all kinds and with different specializations in mind, however, it is still very hard to get guidance and personalized suggestions based on your interests. I am writing this guide in order to provide an aggregator of all the resources that I’ve found over the years, plus give some opinionated commentary on how to approach them and how to use them in order to maximize learning and practical understanding in order to get building cool things in the space as soon as possible.

This guide will focus on the Ethereum ecosystem as that’s where most developers and applications are. If you are interested in other ecosystems that are non-EVM compatible and are not L2s on Ethereum, then check out their respective documentation or guides written by their developer communities. Examples of other non-EVM compatible blockchains that are popular are Solana (Rust/Anchor), Polkadot (Rust/Substrate), Cosmos, Terra, and others. Most of these blockchains do or will support the EVM stack through various initiatives like Neon EVM (Solana), Moonbeam/Moonriver (Polkadot/Kusama), EVMOS (Cosmos), etc.

I really want this guide to become a community-sourced public good that everyone will be able to take advantage of. I will do my best to present it to the wider blockchain developer community to get constructive feedback, proofreading help, and insight into how to make it the best available guide available.

devpill.me


This document provides a baseline knowledge of security considerations for intermediate Solidity programmers. It is maintained by ConsenSys Diligence, with contributions from our friends in the broader Ethereum community.

A guide to Ethereum smart contract security best practices

Smart Contract Best Practices

Do more with Rust tests and less with Yaml/Bash.

The point is to make more tests [runnable via `cargo test`](https://www.reddit.com/r/rust/comments/prhz1u/comment/hdkbpjl/) (not to use Rust for Rust's sake).

- [x] [Prettier](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L37)
- [ ] [Cargo sort](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L42)
- [ ] [Format](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L47)
- [ ] [Format example READMEs](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L55)
- [ ] [Format util READMEs](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L58)
- [ ] [Check lockfiles](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L63)
- [ ] [Check licenses](https://github.com/trailofbits/dylint/blob/178b740594bc97968adf68f0d8a139c46f807455/.github/workflows/ci.yml#L66)

Necessist uses this approach, e.g., for [checking licenses](https://github.com/trailofbits/necessist/blob/7d46abec83529e449a6b7fbc7bacf73b02e1079c/core/tests/ci.rs#L65-L84) and [checking lockfiles](https://github.com/trailofbits/necessist/blob/7d46abec83529e449a6b7fbc7bacf73b02e1079c/core/tests/ci.rs#L170-L178).

The new tests should probably go in [dylint.rs](https://github.com/trailofbits/dylint/blob/master/cargo-dylint/tests/dylint.rs).

good first issue

A tool for running Rust lints from dynamic libraries

dylint

Rust

Convert GitHub workflow tests to Rust tests

Can we add an estimation for FullPruning? We could add some metadata as we have for StateDB size https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.Blockchain/KnownChainSizes.cs


A robust execution client for Ethereum node operators.

nethermind

UX full pruning progress

**Is your feature request related to a problem? Please describe.**

There are two flags: `--importKeystores` and `--importKeystoresPassword`. Where `--importKeystores` expects a directory with all the keystores while `--importKeystoresPassword` expects just ONE password file to decrypt ALL the keystores. What if we have keystores with different password for each keystore?

**Describe the solution you'd like**

Support multiple password file formats (simple and mapped) or option to provide multiple password files, maybe similar approach to how [teku validator-keys](https://docs.teku.consensys.net/Reference/CLI/CLI-Syntax/#validator-keys) work.

I could imagine a file structure like this

```txt
<keystore filename1>:<password1>
<keystore filename2>:<password2>
<keystore filename3>:<password3>
```


prio-medium

help-wanted

meta-feature-request

🌟 TypeScript Implementation of Ethereum Consensus

lodestar

TypeScript

Support different passwords for each keystore

The function is located [here](https://github.com/NethermindEth/warp/blob/1e513662e886d5d172da8318671d40f756bad5af/src/passes/literalExpressionEvaluator/literalExpressionEvaluator.ts#L253). The function should call `safeGetNodeType` function to differentiate nodes instead of using typestring. The value shouldn't be extracted from type but from the node itself.

Warp - Bringing Solidity to Starknet at warp speed. Warp is a Solidity to Cairo Compiler, this allows teams to write/migrate Solidity to Cairo for easy onboarding into the StarkNet ecosystem.

warp

Refactor createLiteralFromType

As mentioned [here](https://github.com/hyperledger/iroha/pull/3258#discussion_r1118758863) it looks like we have a redundant duplication of some errors in `queue.rs` and `transaction.rs (data_model)`, i.e. `Expired` and `SignatureCondition`.

We should try to remove this duplication

iroha2

Refactor

Iroha - A simple, enterprise-grade decentralized ledger

iroha

[refactor] Remove redundant errors from `Queue` and `Transaction`

### Component

Cast

### Describe the feature you would like

I'm using `cast send` extensively in some scripts. Sometimes they fail with `replacement transaction underpriced`. I suggest having a flag that allows bumping the gas price automatically so that the script can replace the stuck transaction.

- Option A: `--bump-fee`. If the transaction encounters the above error, we try resending it with iteratively increasing gas price (e.g. +10%) until we succeed.
- Option B: `--bump-fee <MAX_GAS_PRICE>`. Same as above but provide an upper limit.

I can take a go at implementing this if you think this would be a useful feature.

### Additional context

_No response_

T-feature

Foundry is a blazing fast, portable and modular toolkit for Ethereum application development written in Rust.

foundry

cast send: add --bump-fee flag

low priority

Prototype & implement EIP4444

# 🚀 Feature Request

### Description

Several Beacon API endpoints include a `{state_id}` parameter, which can be substituted with a state root. This is limited to the last `SLOTS_PER_HISTORICAL_ROOT` state roots (8192 on Mainnet). This is because there is no easy way to fetch an arbitrary state by root from the database, and we keep the latest `SLOTS_PER_HISTORICAL_ROOT` state and block roots in memory, which allows us to do this:
```
for i, root := range headState.StateRoots() {
	if bytes.Equal(root, stateRoot) { // stateRoot is the requested root
		blockRoot := headState.BlockRoots()[i]
		return p.StateGenService.StateByRoot(ctx, bytesutil.ToBytes32(blockRoot))
	}
}
```

 

### Describe the solution you'd like

It would be desirable to be able to use an arbitrary state root for the `{state_id}` parameter. One possible solution is to create a `state_root -> block_root` mapping in the database. This way we could get the block root efficiently and then use `StateGenService` to fetch the entire state.

Help Wanted

Go implementation of Ethereum proof of stake

prysm

Support more than `SLOTS_PER_HISTORICAL_ROOT` states when fetching state by root

**Issue summary**

[`prometheus-client`](https://crates.io/crates/prometheus-client) has been used by `libp2p-metrics` and it's maintained by the official, we should consider migrating from the [`prometheus`](https://crates.io/crates/prometheus) crate.


**Other information and links**


https://github.com/tikv/rust-prometheus/issues/392#issuecomment-968072946

Priority: 4 - Low

Ready

forest

Switch to official `prometheus-client` crate

**Issue summary**

A `completion` subcommand that setup shell completion could be helpful for `forest` and `forest-cli`.  It is already supported by `clap` and an example can be found [here](https://github.com/clap-rs/clap/tree/master/clap_complete).


**Other information and links**

https://docs.rs/clap/latest/clap/
https://github.com/clap-rs/clap/tree/master/clap_complete

shell completion for `forest` and `forest-cli`

## Description

There's a new HTTP API on the block for builders: https://github.com/ethereum/beacon-APIs/issues/301

I think @realbigsean might already have an implementation to support `mock-relay`, so we should probably base the standard impl on that. I'm happy to go hunting for the branch and porting it across next week, as Sean is on leave.


enhancement

HTTP-API

capella

lighthouse

Implement expected_withdrawals HTTP API

LibFuzzer has nice HTML coverage reports, we can borrow the styling.

echidna

Solidity

Use LibFuzzer styling for HTML coverage reports

Plenums 3rd parties dependencies use a build of rocksdb from evernym. (https://github.com/evernym/rocksdb) 

The built of rocksdb from evernym is not declaring its dependencies such as:
libgflags-dev \
libsnappy-dev \
zlib1g-dev \
libbz2-dev \
liblz4-dev \
libgflags-dev 

References:
https://github.com/hyperledger/indy-plenum/blob/1fa69a1ae04c8be1aef53816249192bad0f863b2/build-scripts/ubuntu-1604/build-3rd-parties.sh#L8-L23


help wanted

CI/CD

indy-plenum

Python

Problems with Rocksdb

Currently `yarn run tsc` catch errors from `node_modules` folder:
```
❯ yarn run tsc
yarn run v1.22.19
$ /home/.../.bin/tsc
node_modules/@wagmi/core/dist/contracts-3880ee54.d.ts:144:91 - error TS1005: '?' expected.

144 }, TOptions extends Options = DefaultOptions> = TFunction['inputs'] extends infer TInputs extends readonly AbiParameter[] ? Or<IsNever<TInputs>, NotEqual<TAbi, Abi>> extends true ? {
                                                                                              ~~~~~~~

node_modules/@wagmi/core/dist/contracts-3880ee54.d.ts:144:99 - error TS1005: ':' expected.

144 }, TOptions extends Options = DefaultOptions> = TFunction['inputs'] extends infer TInputs extends readonly AbiParameter[] ? Or<IsNever<TInputs>, NotEqual<TAbi, Abi>> extends true ? {
                                                                                                      ~~~~~~~~
```

It should only catch errors from our own files

Type: Tools

retryable-tx-panel

Fix tsc not catching typescript errors 

We have a redundant configuration.  
1. Network.Bootnodes
https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.Network/Config/NetworkConfig.cs#L32
2. Discovery.Bootnodes
https://github.com/NethermindEth/nethermind/blob/master/src/Nethermind/Nethermind.Network.Discovery/DiscoveryConfig.cs#L42

We should analyze the usage. One of the configs should be probably removed.  

Heads up, if we remove/change Discovery.Bootnodes we should coordinate it with EF DevOps because it is used in all EF setups. Example:
https://github.com/ethpandaops/withdrawals-testnet/blob/master/zhejiang-testnet/inventory/group_vars/nethermind.yml#L46
We know for sure that `Discovery.Bootnodes` is working as expected. 

configuration

network

Network.Bootnodes vs Discovery.Bootnodes

Analyze & prototype eth_multicall https://github.com/ethereum/execution-apis/pull/383

Before implementing, it would be great if someone from the Nethermind team analyze this endpoint and provide our input if needed. 

Analyze & prototype eth_multicall RPC endpoint

@gozala wrote on a merged PR: 

> Ideally we'd even have visuals like ssb and dat protocols have

- https://ssbc.github.io/scuttlebutt-protocol-guide/#rpc-protocol
- https://dat-ecosystem-archive.github.io/how-dat-works/#mdns-response

> And I was hoping we could generate such things from the extended schema

multidid

Diagrams or illustrations warmly welcome

Possibly overlap with #16, but if not, please could you add methods for reading the owner and group SIDs out of an ACL?

Rust crate to simplify Windows ACL operations

windows-acl

Methods to return SID Owner & Group

Make use of the [secrecy](https://docs.rs/secrecy/latest/secrecy/) crate to prevent the secrets like `PrivateKey`(are there any other?) from being leaked accidentally by being printed in logs or serialized. `Secret` wrapper also makes sure that upon dropping the field is [zeroize](https://docs.rs/zeroize/latest/zeroize/index.html)d in memory

Chore

Guard against secrets leakage

Same for `iroha_wasm_validator_derive` if it will be created at this point

Contribute to open-source Web3 projects

✨ Ethereum.org

✨ Privacy & Scaling Explorations

✨ Solidity