beigepaper VS EIPs

An unofficial simplified re-write of the Yellow Paper: https://github.com/chronaeon/beigepaper/

Micah Dameron writes the Ethereum Beige paper, a readable rewrite of Ethereum's yellow paper.

Ethereum actually also released a beige paper, a rewrite of their yellow paper formatted for readability.

What I am looking for is something like an updated version of the Ethereum yellow paper or - even better - a beige paper.

https://github.com/chronaeon/beigepaper/ is pretty much just as good as the yellow paper but much better written

For details on Ethereum, you could go with the beige paper or just Solidity documentation.

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.

For ethereum we have the ABI defined https://github.com/chronaeon/beigepaper/blob/master/beigepaper.pdf

Micah Dameron writes the Ethereum Beige paper, a readable rewrite of Ethereum's yellow paper.

Even more relevant would be the Ethereum Improvement Proposal repo (where people submit proposals to change the spec):

https://github.com/ethereum/EIPs

Or the go-ethereum execution client (the most popular execution client):

https://github.com/ethereum/go-ethereum

It’s early in the life of the xERC20 standard, but progress is quickly being made. The standard has been audited and is already live with a few projects. The EIP to adopt the standard has been created, and implementation has begun. Alchemix recently announced support for the xERC20 standard. And Defi Wonderland has published a suggested implementation on their GitHub. This implementation has an interface for the xERC20 contract with eight core functions that the token issuer must implement. These are functions related to setting the Lockbox contract (setLockbox), issuance limits for bridges (setLimits, mintingMaxLimitOf, burningMaxLimitOf, etc.), and the core mint and burn functions.

Check out EIP-7517: Giving Consent for AI Data Mining on the Blockchain

ERC223 is not widely implemented, and there is some debate in the ERC discussion thread about backward compatibility and trade-offs between implementing changes at the contract interface level versus the user interface.

Ethereum Improvement Proposals (EIPs): These are proposals to change various aspects of Ethereum. They often contain detailed technical discussion and can be a good resource for understanding the finer points of how Ethereum works. EIPs can be found here: https://eips.ethereum.org/

Worth looking at: EIP6968: Contract Secured Revenue on an EVM based L2 https://github.com/ethereum/EIPs/pull/6969/files

Additionally, I have made an EIP that can help standardise and maintain official contract registry of each DApp. This can help identify official contracts of a protocol vs scammers using fraud contracts but presenting like official protocol. https://github.com/ethereum/EIPs/pull/6807