@shawmakesmagic@NEARProtocol at one point had react components on chain that were then fetched and composed via a vm. But outside of censorship resistance not sure what problem it really solved and the vm itself had to be hosted somewhere but it could've been run locally as well.
@HouseofChimera With client side proving, what are the hardware requirements of clients? Bandwidth constraints? How can this impact battery life, compute resources, etc?
vitalik introduced Kohaku—ethereum’s native and compliant privacy framework.
it's the biggest privacy upgrade path ethereum has ever outlined.
i try to explain the flow in the most intuitive way possible.
so let's say alice wants to send $1k to bob.
1. say bob has a normal wallet. (0xABC...)
2. bob creates a stealth keypair linked to his real wallet.
3. alice derives a one-time stealth address from bob's stealth key.
4. alice sends money to the stealth address.
5. bob scans the network to see if his stealth key's addresses received funds.
6. the stealth address alice sent the funds to expires.
in essence, Kohaku creates an ephemeral stealth address with your public key, which lets you execute a private action without revealing the link to your main wallet.
this is a game changer, but why is it compliant?
you can publicly reveal the linkage if required (for regulation, audits, institutions).
but the blockchain does NOT automatically expose it.
believe in somETHing.
@TezberryPie@Cameron_Dennis_@KamBenbrik@ChorusOne@NEARGovernance Reality is token price action gets attention and NEAR needs a bigger catalyst to get attention which is to rethink sustainable redistribution of fees and foster a ecosystem addressing use cases.