beigepaper
annotated-spec
beigepaper | annotated-spec | |
---|---|---|
11 | 44 | |
763 | 312 | |
- | 0.0% | |
0.0 | 0.0 | |
over 4 years ago | 2 months ago | |
TeX | ||
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.
beigepaper
-
Did you know that when transferring on Ethereum, it costs ~40% more gas to send tokens to a zero-balance account, and also 10% less gas to empty out an existing account's balance.
An unofficial simplified re-write of the Yellow Paper: https://github.com/chronaeon/beigepaper/
- Beigepaper.pdf
-
Daily General Discussion - February 24, 2022
Micah Dameron writes the Ethereum Beige paper, a readable rewrite of Ethereum's yellow paper.
-
Why are white papers so unprofessional?
Ethereum actually also released a beige paper, a rewrite of their yellow paper formatted for readability.
-
ETH2 technical deep dive yellow paper / beige paper
What I am looking for is something like an updated version of the Ethereum yellow paper or - even better - a beige paper.
-
Deep diving on the whitepapers. I want to understand this at its depths.
https://github.com/chronaeon/beigepaper/ is pretty much just as good as the yellow paper but much better written
-
Why 15s for block production? What happens if a contract code runs for more than 15s?
For details on Ethereum, you could go with the beige paper or just Solidity documentation.
-
Question concerning Ethereum smart contracts
No, so the way bytecode works is that there are a bunch of instructions in a string that the computer reads and executes. Some of those instructions are to set memory registers, or add values in registers, or write to persistent storage, or to branch execution path to a different part of the bytecode string based on the values of registers etc. Ack I might have linked you the yellow paper before. I meant to link the beige paper, which is a little easier to read, at the end there is a list of instructions as they exist in the EVM: https://github.com/chronaeon/beigepaper . The code commited to the blockchain is executed deterministically in the EVM based on the bytecode and the parameters sent in later transactions that a user makes to run that code, as well as the data in on chain persistent storage. e.g. I commit code like this: if you send me a 1 as a parameter, I send back the number 0, else I send you the number 1.
-
How easy it will be for developers to develop on the Cardano blockchain?
For ethereum we have the ABI defined https://github.com/chronaeon/beigepaper/blob/master/beigepaper.pdf
-
Daily General Discussion - February 24, 2021
Micah Dameron writes the Ethereum Beige paper, a readable rewrite of Ethereum's yellow paper.
annotated-spec
- Daily General Discussion - February 17, 2023
-
Can't the Sync Committee be cheaply bribed, and therefor serves no real purpose for security?
My current understanding: The Sync Committee selects 512 validators to continually sign off on block header. Any block headers that get >2/3 are "valid"1, such that Light Clients using this header for verification can trust it.
-
Ethereum Mainnet Merge Announcement
https://github.com/ethereum/annotated-spec/blob/master/phase...
Here we have slashing fields in the block body where you insert your proofs of slashable offense. There are functions with a “slash” in the name that describes precise state transition.
The hard part of slashing is finding these proofs because you have to do more work than necessary to detect slashing and produce proofs - that’s what this software does. It’s more expensive to run a slasher but you need only one and it does not matter who runs it, anyone can run it. The link that you sent says that this slasher broadcasts proofs by default - that way anyone can include it.
-
Explaining Ethereum's consensus mechanism after The Merge
According to Eth docs:
> One validator is randomly selected to be a block proposer in every slot. This validator is responsible for creating a new block and sending it out to other nodes on the network. Also in every slot, a committee of validators is randomly chosen, whose votes are used to determine the validity of the block being proposed.
The annotated code for this can be found in [2].
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://notes.ethereum.org/@vbuterin/Sys3GLJbD#Misc
-
Daily staking income was irregularly high, anyone knows why?
Here's some more info on Sync committees if you are interested. https://github.com/ethereum/annotated-spec/blob/master/altair/sync-protocol.md
- Daily General Discussion - February 20, 2022
-
My First Impressions of Web3
The crux of the article is that the front-ends are all routing calls through centralized APIs to get their message included on the blockchain. Infura and Alchemy don't do much. They just pass a JSON-RPC message to an Ethereum node running on their servers. There is some additional indexing services they provide, but there are many open, decentralized alternatives for that such as TheGraph Protocol. And it's not unfeasible for an application to run its own Postgres instance to index data from the ETH blockchain.
As for full-fat clients on normal mobile devices, the main issue is the data requirements. Running a full node can take hundreds of gigabytes. It is possible on light hardware. People are running Beacon chain nodes on Raspberry Pis. But you do need the storage and that tends to be scarce on mobile.
Meanwhile, the Ethereum core devs are aware of this issue and are actively working towards it. They shipped the Altair hard fork this year that has adds sync committees which make it possible to do without needing the whole chain history (using merkle trees): https://github.com/ethereum/annotated-spec/blob/master/altai...
The light client to follow from those improvements is forthcoming:
-
ETH2.0 withdrawal roadmap post merge
It's not about validators going offline, it's about the validator set changing. To quote the annotated specs
-
Proof of stake is a scam and the people promoting it are scammers
Even a relatively light reading of the Annotated Spec[1] for Eth2 and/or the Eth Org's Proof of Stake FAQs[2] suggests the designers (and independent implementer-teams who gave feedback to designers... lather, rinse, repeat) understand it's important to consider the overall system "outside of the comfort zone".
[1] https://github.com/ethereum/annotated-spec/blob/master/phase...
[2] https://eth.wiki/en/concepts/proof-of-stake-faqs
-
Help understanding staking factors
Alpha leak: I am currently finishing up a full revision of my annotated specification for Altair, and plan to get it published in a couple of weeks. Meanwhile Vitalik's annotated spec has some info on how base rewards work under Altair.
What are some alternatives?
yearn-finance - 🏦 yearn v2 web interface
ethmerge.com-content - Markdown formatted content for the ethmerge.com website.
EIPs - The Ethereum Improvement Proposal repository
consensus-specs - Ethereum Proof-of-Stake Consensus Specifications
pm - Project Management: Meeting notes and agenda items
ens - Implementations for ENS core functionality: The registry, registrars, and public resolvers.
1559-outreach - Outreach related to EIP-1559
crypto-fees - Website for comparing total daily fees of various blockchain protocols.
ethereum-org-website - Ethereum.org is a primary online resource for the Ethereum community.