The carbon credits industry became uniquely interesting to me when I realized just how big the opportunity is. Due to existing and impending regulations, there is a multi-trillion dollar opportunity for anyone who can produce carbon credits at scale.
Existing carbon credit solutions struggle across a number of dimensions. It's tough to know if these solutions are triggering actual change, it's tough to measure the exact amount of change that's happening, it's tough to be certain that the change lasts more than a few years.
I joined Bitcoin during the bear of 2011, while the price fell from $30 to $1. I stayed through 2012, when the price fell from $260 to $70. I was there for mt gox, when the price fell from $1200 to $200. And I was there for the fall from $20,000 to $30,000.
This feels like 2014.
2014 was sharply split between bears who left, and bulls who went all-in. The bulls were there for one reason: it was obvious that crypto was rough around the edges and had low hanging fruit that would drive us to the next phase of adoption.
FTX is not a reason to be bearish. Relative to the size of the industry, it is a smaller catastrophe than Mt Gox. To be equal to Mt Gox, we'd have needed either Binance or Coinbase to fail as well. FTX is bad, but we will bounce back. The technology hasn't changed.
Contractors that build houses have little incentive to build more efficient homes because all the savings get passed onto consumers. To fix this, I propose a 'utility rating' for houses that is measured in negative dollars.
You compute the dollars by taking the average annual cost of utilities and dividing it by the average interest rate for a mortgage.
In my area, the average utility rating would be around $-90,000.
This gives contractors an easy way to price homes that have more efficient utilities. Saving 20% on the monthly energy bill could translate to $20,000 of value added to the house, which consumers can now visualize at the moment of sale.
Looks like siasky got completely pulled off of the internet again. I've been waiting for the right moment to publish a blog post on all the troubles we've had keeping a censorship resistant storage network online, but it seems I waited too long.
We'll have more info on Tuesday, as well as an (already deployed) plan for moving forward. We've been working on some fundamental changes to how we're going to be operating portals for several months now.
The key issue comes down to the 4 horsemen of internet censorship: Child Porn, Terrorism, Phishing, and Malware.
If your website hosts or trafficks any of these 4 horsemen, nearly every layer of the Internet is going to collaborate to take your website offline.
Quick update on the Skynet browser extension. Initially the goal was to create a trustless gateway to access Skynet. But as we started poking around, we made some discoveries.
This is the first time in my professional life that I've taken a serious look at web browser development. And I am surprised to be reporting that it is an incredibly powerful toolkit, powerful in ways I've never seen anyone talk about before.
The web browser is a battle hardened app environment. It is a place where a user in the course of a single day can end up running 100 different untrusted, often malicious applications, all running right next to each other, trying to steal data, add tracking, and inject malware.
We are excited today to announce official support for 100 GB files on Skynet. This was a surprisingly difficult thing to support, and is in fact NOT supported on the vast majority of centralized filesharing services.
Here's why it's hard: 🧵/
Most of the web works using a protocol called "TCP". Beginner network engineers are told "UDP is unreliable, and TCP is reliable", which is only somewhat true.
A more true true statement would be "UDP is highly unreliable, and TCP is mildly unreliable".
When you connect to a server over the internet, you are bouncing through often dozens of different routers, all which are handling tons of connections at once. If at any time (extremely common) a router has more messages incoming than it can handle, it'll just delete some.