ndavd

The idea is to have a singleton HTML registry where protocols could set minimalistic versions of their dapps. Users can fetch and run it locally in one command. It provides some safety when domains get hijacked and users don't know which urls are safe. github.com/ndavd/html-reg…

@PatrickAlphaC would love to get your feedback on this context: x.com/z0r0zzz/status… also related (and needs support :) ): ethereum-magicians.org/t/erc-8244-con…

The idea is to have a singleton HTML registry where protocols could set minimalistic versions of their dapps. Users can fetch and run it locally in one command. It provides some safety when domains get hijacked and users don't know which urls are safe. github.com/ndavd/html-reg…

New ERC: Contract-Hosted Application HTML Contract serves own dapp via html(). Wallet fetches via same call it already trusts, so UI lives in same channel as the bytecode. Live demo: …888741B254d37e1b27128AfEAaBC.w4eth.io < Make Apps Decentralized Again >

Some of my latest contributions to Foundry which are already available on the latest nightly version: - expectAndMockCall — helper for expectation and mocking - console.table — print tabular output in console - ignored_error_codes_from — ignore error codes from matching paths

@0xngmi DeFi United

Looks like this will be the final tally, with just 3% left to cover the entire hole from the rsETH hack

publishing and running a website on ethereum is much cheaper and more secure than using vercel

@z0r0zzz And uploading the whole dapp to the HTML registry on mainnet costed just 3.25 USD

zSwap can be fetched via the standalone onchain UI, 0x000000000A4A4F895734cF70700b6F84AadbcA6C by calling html() or request() via ERC-5219 It can also be fetched through the HTML registry deployed by @0xndavd, and is keyed to the same router used by the UI, html(ROUTER)

@z0r0zzz Thaanks, yours too, not sure how you were able to mine those many zeroes haha

@0xndavd on it :~) nice choice of vanity address btw

@z0r0zzz Niice

@0xndavd done. I was able to actually call into the registry through the same router that plugs into the onchain UI. Cool stuff.

@z0r0zzz can you try out your zSwap?

It's on mainnet 0xFa11bacCdc38022dbf8795cC94333304C9f22722

@z0r0zzz HTMLRegistry has been deployed BTW checkout the README

@0xndavd it just works. I think there is whole new kind of programming around 'perma dapps' - especially since in almost all cases, dapps are just an input form for swap or deposit, and can have their fallback versions as single file html source that can be served by users on own machines

@tritlo 34Hz actually sounds pretty decent

@0xndavd 34hz but yeah, mouse movement can be a bit jarring if you are coming from a 144hz display

e-ink is so good for being able to enjoy the sun without sacrificing your eyes

Great write-up. Now more than ever, there's a real need for minimal, tamper-proof, immutable solutions that we can all fall-back to.

@0xngmi It's going to come back stronger

I see ppl calling for the death of defi They're wrong DeFi is gonna take a hit but it will not die, current situation is completely recoverable with protocol treasuries and loans I believe in DeFi and I'm gonna keep working to make it succeed🦙

@z0r0zzz 🎯

Listen for HTMLRegistry__HtmlSet events to track updates. If in doubt that the frontend might be compromised, one can call latestVersion(author,target) at a past block to get the trusted past version and use it in html(author,target,version).

If the contract is not ownable (or uses another interface, such as role-based ownership) and has no way to call the registry, then it's recommended to use a trusted author and target and mention that in the protocol's documentation, calling html(author,target).