I would like to address some ideas that may be relevant in the future for Ethereum requests for commons:
Public & Private Blockchain
Public and Private blockchain have multiple approaches for enterprise adoption it is necessary to have both possibility’s for inter corporate transactions on public blockchains and internal transaction for private blockchains to make this possible there is a need for public private interoperability there you have multiple approaches instead of a private version of Ethereum some sort of public private transaction instead of public private blockchains this is also possible on layer 2 or on hybride blockchains.
Public & private Smart Contract
There are multiple approaches to realize public private smart contracts one possible solution is an enterprise soft fork where the chain is able to merge smart contract and transaction data to mainnet if needed to migrate from private to public.
Public & private Smart Contracts
Corporate internal off chain computation is also a possible approach to outsource computation not only to private blockchains where the internal consensus & voting could be different if necessary to the public source of truth that could still be used for inter corporate transactions.
Public & private multichain transaction
There are as always multiple approaches a similar approach to the hybride transactions would be to use public blockchains as source of truth and execute private transactions or private smart contracts internally to ensure immutable data and transparency it is possible to send multiple transactions at once to a public and private blockchain. There are multiple use cases interacting from a public smart contract with a private smart contract using a public transaction or private transaction and so on.
Multichain contract execution
Furthermore to enable Multichain contract execution there is a need for a new standard that allows multiple contracts to be executed at once and performing multiple transactions on different chains and protocols regardless of private or public blockchains.
Private Identity zkNFTs
Encrypted KYC data on chain and off chain.
The identity data validation can be on chain and off chain. For zero knowledge allow data access using approval function and private key signing. Enable conditional checks without showing the data for the identity contract allow contract access to read the information from the NFT and identity information for conditional checks to proof your age.
Key exchange between contracts
Double check and compare your contract and NFT data enabled through key exchange between identity NFT and identity validation contract.
Smart Contract interaction with NFT data
Allow smart contracts to interact with NFTs properties. Enable more functionality for NFTs integrate NFTs into smart contracts with functions and properties to make them more usable.
There are multiple use cases for example car dealership and insurances with a smart contracts that has multiple cars or insurances as NFTs inside his contract a car can have an insurance and an insurance company has insurance NFTs that can be linked to cars.
Stonks as NFT
Possible solution could be a Plattform that issues tokenized stonks utilizing NFTs issued by a Smart Contract. An ERC for tokenized stonks to represent the balance sheet & investor relations of a company as a Smart Contract to enable autonomous tokenized stonk exchange. Minting and burning should be disabled for tokenized stonks the standard must be with all the regulatory needs for legal systems & governments. There is a need for NFT stonks to represent all the market data of a public traded company share utilizing NFT property’s. A fundamental difference between stonks and crypto, the value of a protocol or product is the token not the balance sheet of a company or the product revenue this means crypto doesn’t sell anything it provides value in a decentralized manner.
Event NFTs
Event NFTs enable more usability for NFTs also for digital products and allow product exchange. This is possible trough an integration between payment provider and e-commerce utilizing the event data a better approach would be to create a smart contract and product standard where the smart contract holds the products in the form of NFTs similar to tokenized stonks.
Stablecoin CBDC & Bankaccount ERC
Wallets are basically bank accounts the difference you need multiple wallets for one bank and multiple accounts with multiple wallets for central banks. Stablecoin CBDCs & Bankaccount ERC for Centralbanks and Banks in any country solves any banking issue.
Multi wallet Smart Contract with embedded KYC
Multiple wallets inside one smart contract for example a dropdown where the contract address resides. To mitigate admin key risk every user has his own private key and to enable wallet recovery and reoccurring payments for banks there are multiple approaches to realize this for example banks could reissue a new wallet and migrate funds from to new wallet using KYC and user accounts.
Recover Accounts using KYC
The other approach would be to allow the user reset the account using KYC what basically means reissue a new wallet and migrate funds to new wallet so there is a need to save KYC data on chain to prevent fraud. This also enables upgradable smart contracts without admin key risk put the twice encrypted private key inside the smart contract and allow only updated contract to migrate funds to new contract.
Multiple wallets in one account
Enable multiple user wallets inside multiple bank accounts and multiple bank accounts inside central bank accounts to ensure privacy on both sides Zero Knowledge could be used for block confirmation.
Privacy encrypted hashing
Another privacy approach would be to encrypt payment data after block hashing.
Multiple transactions
One approach to lower transaction cost for dezentralized applications would be to enable bunch transactions for enterprises or Banks. Comparing transaction amount sender and receiver balance from previous block to ensure block validity.
Autonomous transactions
Enable smart contracts with tax function to allow governments and enterprises to switch from regular finance to Blockchain FinOps and to bridge the gap between fiat and crypto allow payment gateways to pay with crypto or fiat and the receiver can choose what to receive. Therefore Smart Contract need some payment functionality to call fiat gateways or other Payment provider APIs and exchange tokens for instant fiat crypto payment and vice versa.
APYieldFarmer
commented
1 day ago
Hello there,
I would like to address some ideas that may be relevant in the future for Ethereum requests for commons:
Public & Private Blockchain Public and Private blockchain have multiple approaches for enterprise adoption it is necessary to have both possibility’s for inter corporate transactions on public blockchains and internal transaction for private blockchains to make this possible there is a need for public private interoperability there you have multiple approaches instead of a private version of Ethereum some sort of public private transaction instead of public private blockchains this is also possible on layer 2 or on hybride blockchains.
Public & private Smart Contract
There are multiple approaches to realize public private smart contracts one possible solution is an enterprise soft fork where the chain is able to merge smart contract and transaction data to mainnet if needed to migrate from private to public.
Public & private Smart Contracts Corporate internal off chain computation is also a possible approach to outsource computation not only to private blockchains where the internal consensus & voting could be different if necessary to the public source of truth that could still be used for inter corporate transactions.
Public & private multichain transaction There are as always multiple approaches a similar approach to the hybride transactions would be to use public blockchains as source of truth and execute private transactions or private smart contracts internally to ensure immutable data and transparency it is possible to send multiple transactions at once to a public and private blockchain. There are multiple use cases interacting from a public smart contract with a private smart contract using a public transaction or private transaction and so on.
Multichain contract execution Furthermore to enable Multichain contract execution there is a need for a new standard that allows multiple contracts to be executed at once and performing multiple transactions on different chains and protocols regardless of private or public blockchains.
Private Identity zkNFTs Encrypted KYC data on chain and off chain. The identity data validation can be on chain and off chain. For zero knowledge allow data access using approval function and private key signing. Enable conditional checks without showing the data for the identity contract allow contract access to read the information from the NFT and identity information for conditional checks to proof your age.
Key exchange between contracts Double check and compare your contract and NFT data enabled through key exchange between identity NFT and identity validation contract.
Smart Contract interaction with NFT data Allow smart contracts to interact with NFTs properties. Enable more functionality for NFTs integrate NFTs into smart contracts with functions and properties to make them more usable.
There are multiple use cases for example car dealership and insurances with a smart contracts that has multiple cars or insurances as NFTs inside his contract a car can have an insurance and an insurance company has insurance NFTs that can be linked to cars.
Stonks as NFT Possible solution could be a Plattform that issues tokenized stonks utilizing NFTs issued by a Smart Contract. An ERC for tokenized stonks to represent the balance sheet & investor relations of a company as a Smart Contract to enable autonomous tokenized stonk exchange. Minting and burning should be disabled for tokenized stonks the standard must be with all the regulatory needs for legal systems & governments. There is a need for NFT stonks to represent all the market data of a public traded company share utilizing NFT property’s. A fundamental difference between stonks and crypto, the value of a protocol or product is the token not the balance sheet of a company or the product revenue this means crypto doesn’t sell anything it provides value in a decentralized manner.
Event NFTs Event NFTs enable more usability for NFTs also for digital products and allow product exchange. This is possible trough an integration between payment provider and e-commerce utilizing the event data a better approach would be to create a smart contract and product standard where the smart contract holds the products in the form of NFTs similar to tokenized stonks.
Stablecoin CBDC & Bankaccount ERC Wallets are basically bank accounts the difference you need multiple wallets for one bank and multiple accounts with multiple wallets for central banks. Stablecoin CBDCs & Bankaccount ERC for Centralbanks and Banks in any country solves any banking issue.
Multi wallet Smart Contract with embedded KYC Multiple wallets inside one smart contract for example a dropdown where the contract address resides. To mitigate admin key risk every user has his own private key and to enable wallet recovery and reoccurring payments for banks there are multiple approaches to realize this for example banks could reissue a new wallet and migrate funds from to new wallet using KYC and user accounts.
Recover Accounts using KYC The other approach would be to allow the user reset the account using KYC what basically means reissue a new wallet and migrate funds to new wallet so there is a need to save KYC data on chain to prevent fraud. This also enables upgradable smart contracts without admin key risk put the twice encrypted private key inside the smart contract and allow only updated contract to migrate funds to new contract.
Multiple wallets in one account Enable multiple user wallets inside multiple bank accounts and multiple bank accounts inside central bank accounts to ensure privacy on both sides Zero Knowledge could be used for block confirmation.
Privacy encrypted hashing Another privacy approach would be to encrypt payment data after block hashing.
Multiple transactions One approach to lower transaction cost for dezentralized applications would be to enable bunch transactions for enterprises or Banks. Comparing transaction amount sender and receiver balance from previous block to ensure block validity.
Autonomous transactions Enable smart contracts with tax function to allow governments and enterprises to switch from regular finance to Blockchain FinOps and to bridge the gap between fiat and crypto allow payment gateways to pay with crypto or fiat and the receiver can choose what to receive. Therefore Smart Contract need some payment functionality to call fiat gateways or other Payment provider APIs and exchange tokens for instant fiat crypto payment and vice versa.
Kind regards J.W.