Vapor – Decentralized Web over Bitcoinized HTTP(vapor.network)
vapor.network
Vapor – Decentralized Web over Bitcoinized HTTP
https://vapor.network
7 comments
1) Slow RTT
2) Misuse of bitcoin with crazy amounts of blockchain spam (could end up blocked by miners too)
3) Expensive
4) Loss of access to a Bitcoin API means app downtime
5) etc...
Maybe it's adequately named 'vapor' as in vaporware? But I agree, surprised it didn't implement its own token or cryptocurrency instead of polluting BitCoin.
I like the research idea but please do this on a separate blockchain not on the Bitcoin network. Not only would it be so expensive to be unfeasible, it'd also be an egregious waste of a vital resource (block space). The Bitcoin network is virtually the only way to transfer money uncensorably and it's supported by volunteers like me. If I have to buy more hard drives, I'm less likely to keep my node online.
IIUC, Vapor only uses the Bitcoin network for micropayments and immutable timestamps (block hash/height). Both are optional.
It's called "Bitcoinized HTTP" because they wrap requests and responses in Bitcoin transactions (as the packet format).
It's called "Bitcoinized HTTP" because they wrap requests and responses in Bitcoin transactions (as the packet format).
The most intriguing parts of Vapor in my opinion (in order of intrigue):
- monetizable requests/routing
- proof of request/response
- data portability
- wallet as universal identity
- monetizable requests/routing
- proof of request/response
- data portability
- wallet as universal identity