This blog post captures the research I've done in building an uncensorable API, leveraging IPFS. This could replace REST APIs or gRPC. What do you think?
Keep an eye on this GitHub repository. This will be an npm JS library for the peer-discovery protocol I'm working on. I've come to the conclusion that it will be easier for me to just
Sorry to interrupt and go off topic, but the first one of you coding aficionados to make a wrapped BCH token for Matic, well, you can write your own ticket at that point.
Personally, I am morally opposed to PoS coins. If whoever has the most coin gets to make the rules, how is that different than today's corrupt banking system? Fuck that noise
A wise investor spends most of his time & energy trying to find reasons why investments *suck*, and only puts in money when the arguments against just don't add up. Skepticism FTW
PoS mostly intends to achieve scalability & speed. But that can also be achieved with simple validator nodes, like XRP and XLM (which both have the same basic design)
Interesting! I grok IPFS content-address. Ultimately a computer has to open a socket to a network address; P2P systems say, "find a node (somehow), they can tell you about other nodes"
The next bit of research I'm going to do will focus on the *peer discovery* and *request/response* messages. That will help differentiate this idea from other p2p systems and protocols
Excellent. Peer discovery strikes me as the most-centralized part of most ostensibly-decentralized systems. Generally there has to be a hardcoded seed (or set of seed nodes) somewhere.
You're right. This is where IPFS pubsub rooms are a game changer. They allow nodes to find one another, discover the things they have in common, and route to the services they want to