Public endorsements from trusted experts in relevant domains, such as crypto, econ, impact certificates, EA-style prioritization. Yes, that’d be great! I’m closest to knowledgeable on the last one, and I’m very concerned about Ofer’s concern above. So I want to come up with a promising solution to that before I move forward at all.
A series of blog posts detailing how different actors can use the system. Yes, very good. I’d also explain the reasoning behind various design decisions in these posts. Something that irks me about a lot of crypto projects is that they have a very specific fine-tuned byzantine architecture that they explain in detail but never mention why they made all these design decisions.
A software that abstracts away all the unnecessary complexity. That is probably something that I’ll need to build gradually as I see signs of adoption. It’d be too easy to waste a year on building a software that no one uses. (I’ve worked for a startup that did that.) So I hope I can do it in a way where the complexity doesn’t itself impede the adoption too much…
On the flip side, I think there’s a lot of potential for such a system, so I’d see this work as quite plausibly very high impact and thus hopefully a mini-cause around which folks can coordinate. Personally, I can try to rally support once a system exists (see above), but I’m not currently in a position to rally community leaders nor get crypto experts to scrutinize the plan.
Awesome, thank you!
Public endorsements from trusted experts in relevant domains, such as crypto, econ, impact certificates, EA-style prioritization. Yes, that’d be great! I’m closest to knowledgeable on the last one, and I’m very concerned about Ofer’s concern above. So I want to come up with a promising solution to that before I move forward at all.
A series of blog posts detailing how different actors can use the system. Yes, very good. I’d also explain the reasoning behind various design decisions in these posts. Something that irks me about a lot of crypto projects is that they have a very specific fine-tuned byzantine architecture that they explain in detail but never mention why they made all these design decisions.
A software that abstracts away all the unnecessary complexity. That is probably something that I’ll need to build gradually as I see signs of adoption. It’d be too easy to waste a year on building a software that no one uses. (I’ve worked for a startup that did that.) So I hope I can do it in a way where the complexity doesn’t itself impede the adoption too much…
Thank you! 😊