Even if the web front end is taken down, the contract is still on-chain so it can be accessed via a web3 browser, a client or even in etherscan in the "read contract" tab.
The smart contract is. It's like https://xkcd.com/932/ . The static JS being served by the site is just a poster that could be hung up anywhere else. Even if that URL is taken down, your money is still safe and sound on the blockchain. You can still sign transactions and interact with the smart contracts, get your liquidity out, etc., so long as you have access to any part of the Ethereum network.
> Interestingly, in the end I was able to withdraw all my funds from AAVE through direct contract calls as illustrated above. So basically the web UI is blocked but people can still use AAVE by sending transactions to the blockchains directly.
Ah thankyou! In that course we did write a web frontend that interacts with the contract ABI to mint the NFTs, but we didn’t do the display side. I’m curious how opensea are doing it, because they can display NFTs from my contract without me ever giving them the ABI. Can you go from decompiled contract (like etherscan can generate) -> ABI maybe?
Presumably the app also has other assets like js and frontend that need to be hosted. These aren't just compiled and stuffed in The Blockchain until the end of time.
I see so this works similar to how blockchain.info site works in the browser, with the server used for encrypted backups and to retrieve blockchain data.
The browser portion of the application does not need to be served from the internet. Dapps (decentralized apps), if they are well designed, do not require anything other than a copy of the HTML/JavaScript and access to a copy of the Ethereum Foundation blockchain (better yet: access to node receiving new transactions - but that's not necessary for historical reads). In fact, this application doesn't even have a website where it is hosted - that's unnecessary from a strictly technical point of view.
If you're okay with high latency (i.e. you are primarily reading from blocks, not writing new transactions, which is probably an accurate profile for the /consumption/ of censored data), then a full copy of the Ethereum Foundation blockchain could be carried on a $40 microSD card and carried (or flown, or dropped), well, anywhere.
Not really because it’s tightly coupled with Ethereum smart contracts. It looks like it was built on top of WebTorrent App (webtorrent.io). Web3Torrent is currently live on the Göerli testnet.
Powered for sure, but I don't know if absolutely everything is stored via web3, like their html or whatever. I know the NFTs and metadata are[1]. Purchases, transfers, bids, offers, etc. are handled using smart contracts. User accounts are just wallet addresses, yes. I don't know how it manages access control, but besides what I assume is some sort of admin access it doesn't really need it.
If OpenSea doesn't qualify as web3, I don't know what would.
What does the chain part provide that's not available right now through any page with an interledger link in meta and maybe an .eth link if you want to be fancy with anticensorship?
Not only open source, also deployed as a smart contact on the Ethereum blockchain.
It’s possible to deploy a smart contract with no way to modify it, meaning it’s literally impossible to shutdown (without shutting down the entire network). This is rare, most dev teams retain admin keys and compose the smart contact components from additional layers of abstraction to allow for updates. But those admin keys typically also allow the possessor to abscond with all funds locked in the contracts (a rugpull).
My understanding is Tornado Cash eventually added a limited form of KYC to the frontend web UI. That’s simply a convenient interface to use the smart contract though, and it’s possible to interact with the smart contact directly (where there’s no KYC).
It's not pointing at a contract. Metamask should let you view the data (and it they're working on it[1]), but ultimately if you want to verify the contents of a contract you're deploying you'll have to compile it yourself. I suppose metamask could take the source and compile it for you, but ultimately verifying what a transaction is going to "actually" do seems like a difficult problem that's unlikely to be solved anytime soon.
well this is built on the Ethereum network, according to a tweet I saw in this thread, and would therefore be a private contract. So the private data is settled on a blockchain that is secured by proof of work now, and proof of stake later.
It is open source and uses Lightning Network (smart-contract sidechains). See https://lightning.network/ . These validate and batch transactions. This is how Strike ( https://strike.me/ ) and other services also can provide very low or no fees as well, however this one is self-hosted.
There's a benefit to building it on the blockchain.
I can look at the USDC contracts and see that privileged users have the ability to freeze the USDC in my account.
I can look at the DAI contracts and see that they do not.
Good luck getting visibility into the back-end processes of web2 applications. Even if they publish the source on github, there's no way to verify what they're running
How does the web3 or whatever js running in your web browser know what gateway to use to interface with the blockchain? What if that gateway goes down? How does it or any ETH or Bittorent node bootstrap in general?
reply