Vapor – Decentralized Web over Bitcoinized HTTP(vapor.network)

15 pointsby vapormachevor 6 Jahren6 comments

Vapor – Decentralized Web over Bitcoinized HTTP

https://vapor.network

7 comments

Provenvor 6 Jahren

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...

dsun180vor 6 Jahren

From the docs it does not look like that every http tx is stored onchain. It is more like an ssl-alternative where you sign stuff with bitcoin crypto and therefore not need to trust the sender.

Provenvor 6 Jahren

giancarlostorovor 6 Jahren

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.

zellyvor 6 Jahren

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.

isthisrealityvor 6 Jahren

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).

isthisrealityvor 6 Jahren

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