This makes it possible to build decentralized web applications that can trustlessly synchronize API requests with one another as well as natively monetize data through Bitcoin payments. REPLICATE: The Bitcoin transaction packet from step 3 may be replicated to multiple interested parties.īecause every API request is explicitly signed by a Bitcoin wallet and stored as a Bitcoin transaction with immutable bitcoin transaction IDs, it is possible to propagate a single HTTP request to multiple independent parties, complete with authentication information attached.ROUTE: The HTTP request is extracted from the transaction and routed to relevant API endpoints.AUTH: The Vapor endpoint authenticates the request by verifying the signature.POST: The transaction is sent to a Vapor endpoint over HTTP.SIGN: The wrapper Bitcoin transaction is signed by a Bitcoin wallet's private key.WRAP: An HTTP request is wrapped in a Bitcoin transaction as an OP_RETURN output.In essence, it's a protocol for authenticating and wrapping HTTP requests inside Bitcoin transactions, making it possible to replicate HTTP requests across multiple interested parties in a trustless manner. Vapor is an OFFCHAIN Bitcoin protocol for building a decentralized web by "Bitcoinizing" HTTP requests. Request an invite to get notified of the upcoming Vapor node beta release:
To end-users, Vapor apps are indistinguishable from a normal web app because Vapor is literally HTTP. This leads to a superior user experience where all Vapor apps are simply HTTP based web apps, and no one needs to run a "P2P node" and have deep tech knowledge. Instead of rebuilding the networking stack, it focuses on decentralizing data itself, which works across any existing networking stack, most notably HTTP. Most of them have focused on rebuilding the networking layer to facilitate decentralization of trust. There have been many past attempts at building a "decentralized internet".
0 kommentar(er)
