stellar-protocol VS EIPs

Although Stellar provides recommendations, there is no NFT standard on Stellar. This brings to mind the question posed by Mara Bos, Rust team lead, about the necessity of a Rust standard—…Do we need one?.

From Justin Rice: " Time for a protocol discussion! The main topic: CAP 46-06: Smart Contract Standardized Asset. This is the proposal that describes how smart contracts will interoperate with Stellar assets, so it should be interesting. As per usual, it's a technical discussion, so you probably want to read the CAP in advance: https://github.com/stellar/stellar-protocol/blob/master/core/cap-0046-06.md "

Every year scammers steal hundreds of thousands of dollars from credulous users. So our top priority is to make Stellar Network a safer place. If you develop an application on Stellar, you can utilize our API to protect your users and improve the general UX of your app. Check our API and SEP draft.

CAP-47: Smart Contract Life Cycle

CAP-46: WebAssembly Smart Contract Runtime Environment

May 26th - Mainnet Upgrade to Protocol 19

Be very afraid of Stellar and Ripple because they are designed for CBDC. They allow for the control and manual approval of individual transactions. Check out SEP-8, issuance of regulated assets. https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md

Proposal

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