raiden VS EIPs

Raiden sees v0.6.0 "Metamorphosis" with an updated database format and changes to the REST API.

Raiden v0.3 is released.

The Raiden client looks almost completely ready for the Coruscant milestone. The development team created a couple more release candidates in the last 7 days, the latest one being Coruscant - mansard. All packages in the Raiden Client were updated to the latest versions and a few more optimizations were also successfully completed. Open issues section of github looks clean of any reported bugs and we can see an open task for the Release 3.0.0.

Referencing this latest release: https://github.com/raiden-network/raiden/releases/tag/v3.0.0rc3

Development progress is looking great in the past week. Release candidate for Coruscant milestone was introduced in the Raiden Client. This release candidate will help the development team in testing and debugging. For now, the open issue section looks clean of any bugs discovered.

The Raiden Testnet is launched.

Coruscant - Songpa adds support for the cooperative settlement. Furthermore it also introduces performance improvements to payments and the WebRTC transport layer. Backward compatibility with version 2.x is broken which means channels opened with older versions need to be closed, settled and re-opened.

The Raiden Client has also seen some nice progress. Progress in the Raiden Client repository can be followed here.

In the Raiden Client repository they successfully completed WebRTC integration. Also, the work in progress version of cooperative settlement feature was introduced. Cooperative settlement was also successfully completed in the Raiden smart contracts. Other work includes minor codebase cleanup and fixes.

Raiden v0.100.4 "thehighfiveghost" is out on testnet, bundled with Raiden Services, and including channel withdrawals, permissive source routing and the handling of pruned blocks.

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