It's still using resources from "Web 2" websites, and doesn't work without them...
Most importantly, among these are requests for resources from `ipfs.originprotocol.com`, which bypasses my local IPFS node. I'd argue that's the wrong way to use IPFS.
From the article:- ""We're excited that Cloudflare is bringing their infrastructure expertise to the Ethereum ecosystem. Infura has always believed in the importance of standardized, open APIs and compatibility between gateway providers, so we look forward to collaborating with their team to build a better distributed web." - E.G. Galano, [Infura](https://infura.io/) co-founder."
Not exactly sure what that means, but it looks like the goal is for them to perform a similar function?
Due to the nature of Cloudflares services, some of their clients operate in ethical/legal gray areas. They enable this, for better or worse. Would this service allow those clients to easily receive funds, with the entire network being behind Cloudflare?
CryptoOnlyPlatinum | QC: ETH 55, CC 34, BCH 214 weeks ago
Crypto is open for everyone to use, that’s the beauty of it!
All I know about CloudFlare is that they're a huge internet infrastructure company.
After reading that blog post I have to say, I love CloudFlare.
That was an amazing explanation of Ethereum, and their attitude, understanding, and helpfulness are all 10/10.
I love how they're throwing the 'eth is centralized bc Infura' line and flushing it down the toilet.
Being the 2nd major gateway provider to build on Eth and the 1st outside major corporation is huge.
It reminds me of a video I saw at a music festival about dancing. It was about how groupthink works and how to start a trend.
The video starts with 1 guy just going full on dancing solo all alone on a hillside. Then, after 1 minute, another person joins in, then another minute and 1 more. This starts a bunch of other more shy people to jump in and start dancing and within a minute there are hundreds of people all dancing together starting from one guy and the key early adopters that signalled to everyone else you don't need to feel embarrassed about joining in.
I feel like Cloudflare and all these great announcements are like the 2nd 3rd 4th and 5th dancers.
For sure. Can you imagine all the board rooms out there where people have no idea about blockchain and will suddenly want to get involved, or they'll get fired? It's going to be good for anyone who knows what they're talking about.
I liken it to the switch from analog to digital. Sure, at first digital looked like shit compared to its mature analog cousin (later analog video is really really good quality), but it didn't matter, the advantages digital gave were so far beyond what analog could muster that it eventually gave way completely to digital.
Decentralization will be the same way. Sure at first it might be slow compared to its centralized cousins, but given enough time its benefits will clearly surpass anything that centralization can offer.
I'm assuming this is the same issue that you experience when using Infura. Cloudflare is just running a bunch of Ethereum nodes behind a load balancer, so depending on which node the balancer sends your request to, the node might be a few blocks behind the rest.
This is 126 blocks behind though...Probably has to do with caching on the edge—either the Cloudflare workers aren't correctly issuing invalidations, or the invalidations aren't propagating for some time.
Cloudflare, one of the largest and most important networks on the internet, will now be providing high-performance access to Ethereum.
When taken together with announcements from Microsoft, EY, and Google, a very clear picture of critical infrastructure needed to develop for the Ethereum public chain is coming together. And of course, many L2 and privacy experiments are now in operation, Eth 1.x continues to evolve, and Eth 2.0 Phase 0 is just around the corner.
2019 will be remembered as the year when Ethereum infrastructure truly started to become a reality, and will fuel massive growth and adoption from 2020 to 2022.
The most important line from this article:
By providing a gateway to the Ethereum network, we help users make the jump from general web-user to cryptocurrency native, and eventually make the distributed web a fundamental part of the Internet.
I cannot imagine a more bullish line than this coming from a firm like Cloudflare.
And hopefully this also kills the continual and popular FUD from Bitcoin Maxis that "Ethereum is centralized because of Infura"...well, we now have one of the largest internet networks in the world also providing access to Ethereum. I seriously doubt they'll be the last.
I would not be surprised if Azure, AWS and GCS are working on similar offerings.
I still think light client development is important to furthering the decentralized web, but I see this as a big boost for adoption!
Mekswoll4 - 5 years account age. 250 - 500 comment karma.4 weeks ago
Genuine question: when you say Eth1.x continues to evolve, can you expand on this? According to multiple articles the tentative date for ETH2.0 Phase 0 is 3rd of january 2020, but we know that that's just the beacon chain and a fully operational ETH2.0 will likely only be available somewhere in 2022. What improvements do you expect to see on Eth1.x while we're waiting for a fully operational ETH2.0?
Here is a good description of 1.x [https://docs.ethhub.io/ethereum-roadmap/ethereum-1.x/](https://docs.ethhub.io/ethereum-roadmap/ethereum-1.x/)
Major changes are state rent, ewasm and storage pruning. Basically reduce resource requirements for running a node while increasing max gas/s by about 10 times.
If tx/s can be increased 10 times and sharding gives another 1000 times and 15 can be done on chain now that would be 150k tx/s on L1 one day without sacrificing decentralisation. Lets hope.
Not entirely sure about Eth1.x, but a lot of great work being done on the layer 2 side (e.g Loom), which should greatly alleviate scalability concerns for Eth1.x
Loom for example recently had a day where they did the equivalent of 10% of the Ethereum transaction volume of that day. Small, but important step to scaling Eth.
Cloudflare is ran by really bad people to be real. The CEO has a horrible reputation in the valley and their sales people are the worst. I’d avoid anything this place touches to be honest. Very questionable ethics.
"But Jonathan," I hear you say, "by providing a gateway aren't you just making Cloudflare a centralizing institution?"
The problem is the market share of these institutions. Google could argue that they aren't the sole gatekeeper to search since services like DuckDuckGo exist. This isn't really valid when you control a huge amount of the market share. I'm worried about how the internet is becoming super homogeneous, it really hurts startups. I'm not saying what Cloudflare is doing is bad, but the amount of control Cloudflare has is increasingly worrying based of all the services they are launching. Look at what it did to The Daily Stormer (I think they are disgusting and have zero support for them), it's clear that they aren't unbiased. If Cloudflare blocks your service on their VPN, DNS, DDoS protection, IPFS site, Ethereum, etc you are majorly screwed. Most people aren't willing to change their setup just to visit your one service. I still think what Cloudflare does is awesome, not trying to be too negative, just a little worried.
From what i know about cryptocurrencies, Ethereum has so many more use cases and functionalities built in than Bitcoin. It seems like this is what blockchain tech is all about, not just transacting money. Is there some real reason why Ethereum coin market cap is so much lower? Is it just the hype and Bitcoin being first?
So as someone who is working in this space (on distributed applications using Ethereum), I want to call everyone's attention to a very important API that Cloudflare thankfully did implement: eth_getProof. As far as I am concerned, this is the most important API offered (and if anything, it is mostly sad no one has built out a few more APIs designed to make getting to the point where this is useful).
For those who don't know much about the inner workings of Ethereum, every account has state associated with it: not just its balance, but in the case of a contract its memory and its code; the memory of a contract is pretty much a sparse 256-bit addressable hash table, with everything from a single contract hashed into the same address space. This makes directly working with the memory of a contract really trivial; and, if/once you know of a specific storage slot you want, you can get it using eth_getStorageAt.
Now, what most people know is that each block contains a hash of the previous block, and "the contents of the block"; but, the setup is actually way more useful than that: each block "contains" (by hash reference) the entire current state. So, given a block header you trust, you can work off of a merkle tree of the entire Ethereum state that is rooted at that block and obtain a proof that some specific account state value is valid.
This means that light clients can opt to sync only block headers and then request proofs of the specific tiny bits of information they need from other nodes. Instead of using eth_getStorageAt to pull a storage slot from the memory of a contract, or eth_getBalance to find out how much money the account is storing, you can use eth_getProof to get a merkle path demonstration that "given the block headers you trust, you can now trust this random value you wanted to pull".
A really light client might alternatively sync some subset of block headers to some total amount of difficulty into the past (similar to people who wait for "confirmations" on Bitcoin blocks), to say "someone who is trying to fool me about this event having happened would have had to spend a million dollars of electricity to target me with fake information here, which wouldn't be worth it given the relatively small amount of my transaction I am verifying".
Another way of doing this is to correlate the current block hash from multiple providers to make sure that it is the same, and then use that opaque agreement as the root of trust for calls to eth_getProof. (An important detail: doing it like this, as opposed to correlating the thing you wanted to check, happens before any of the providers know what you are looking for, so if they are colluding they wouldn't be able to target you and the information you want to read with corrupt data.)
Essentially, since Cloudflare has implemented this specific key API (which is notable as it is a newer one that has greater resource usage on their end than other APIs, and so I have seen providers decide not to bother as they just don't get it), you don't actually have to trust them all that much when you are using this API: it feels more like working with IPFS, where "well, I asked for the file with this hash and they gave me a file that in fact does have this hash... I guess I would be shocked if it weren't the right file".