ssv VS EIPs

Are you strapped in and ready to make history? We're in the heart of the mission control room, preparing for the Limited Launch of the ssv.network mainnet.

After seeing this post about ssv.network, I became curious about what the rest of reddit thought about it.

It's pretty much an alternative to https://ssv.network/ (DVT)

Solo stakers and other community stakers are invited to participate in the next round of DVT testing with Obol Network and SSV Network. Deteails in the original Twitter thread.

I would start here - https://ssv.network/

Currently we are supporting Staking on testnet as well as creating a testnet Node Operator for the SSV network (https://ssv.network/) As you can see from the video, there is still a ton left to do, a lot of components/features we are planning to implement missing and polish to apply before we can think of a full release.

What you're describing already exists! It was on the top of Vitalik's roadmap (https://twitter.com/VitalikButerin/status/1466411377107558402), funded through a grant from the Ethereum Foundation, and has a working public testnet that is close to mainnet launch. Check out ssv.network. And here's a good video that gives a decent overview: https://www.youtube.com/watch?v=TV70EgAKkrI

I thing ssv.network did present something in AMS this week which shares portions of the validation keys accross a network of operators who need to aggregate a signature to validate. It's still not your keys, not your validator, but at least you are dilluting the risk by splitting the trust into several parties which would need to collude to slash you, which they also have no incentive to. Now do you trade the key split for the convenience of delegating the infra is another topic :)

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