Bitcoin Forum
September 19, 2019, 11:35:06 AM *
News: Latest Bitcoin Core release: 0.18.1 [Torrent]
   Home   Help Search Login Register More  
Pages: [1]
Author Topic: Decentralized Wireless Internet Connectivity Provider  (Read 823 times)
Offline Offline

Activity: 5
Merit: 0

View Profile WWW
September 24, 2014, 04:35:14 PM

I had this idea to stimulate real demand (as opposed to speculative) for bitcoin so i wrote about it (see below):

This jist of it is: To provide hardware, firmware images, and payment infrastructure to allow individuals to sell their connectivity over wireless for instantaneous payment in BTC with plan for further decentralization of the payment infrastructure.
Users can select their gateway based on price and speed ( number of hops and link quality)

I'm putting this out to bounce ideas off Your heads.
I'm specifically interested to know if there is anything like this out there now.

---- Pasted from ----
1 Intro

For now I'll refer to it as Wisp-imagined. To create a Decentralized Wireless Internet Connectivity Provider (DWICP) that accepts bitcoin micro-payments for internet connectivity and provides free access to an *intra*net. The level of decentralization is as much as possible with current technology, but that is designed to grow as new technologies move from concept to application (Ethereum). As possible i will explain how this structure allows movement to a more decentralized model.

2 What advantages does new techbology give this DWISP over traditional ISPs?

2.1 Routing
The new BATMAN routing protocol is more "intelligent" and adaptable than previous protocols. Thus, where extensive and expensive planning, configuration, and reliability requirements were necessary for effective networking, now BATMAN will automatically select the best route from the viable links. This reduces both the cost associated with planning and administering because links can be set up willy-nilly by individuals, and will get paid according to the usefulness (in MB) of their link. Additionally, the requirement of reliable commercial grade equipment is also eliminated because the network can recuperate seemlessly from node failure; creating and using redundancy as necessary. This network can be run on consumer hardware.

2.2 Payment
Bitcoin payment network means those operating AP nodes, P-2-P nodes, and Internet gateways can be paid on an instantaneous basis for the connectivity they provide. That, in conjunction with BATMAN routing protocol opens the possibility for a highly dynamic network environment. Additionally, end users may register and pay for Internet Connectivity with out giving superfluous payment details.

3 Network Components

Role   | Defintion | Payment
Users |   May register to join the network and pay to access the internet. |    Pays varible rate calulated by gatways cost + hops
Nodes |   Wireless Access Points and P-2-P links |    Operators receive BTC payment by the MB
Gateways |   Give users access to the internet |    Select a rate at which they offer connectivty
Authentication, Authorization, Payment |   Maintains user access list and payment db. Polls Nodes and Gateways for usage and them payment |    Collect a % of users fees

4 How it works:

4.1 Access Point Nodes
Host three wireless networks ( it is possible to do with with a single antenna and wireless device )

    Unencrypted network
    Used as a captive portal to require authentication

    WPA2 Encrypted network
    Used to access the intra and inter nets

    Ad-Hoc Mesh Network
    Bridged to the Encrypted network to give users network access

4.2 P-2-P Nodes
Proxy/Bridge connections from users to gateways and are paid according to ther use in MB by users. Every node that a user crosses to reach an internet gateway is considered a P-2-P Node

5 Payment model

Those operating gateways may specify how much they will charge for internet access. Access Points and P-2-P nodes are paid a flat fee per MB. Of course, a single entity can act as both a gateway and AP. Thus everyone is rewared for their participation on the network and competion to build a more utilized network is emphasized.

5.1 Why this model?
This will encourage price competition and growth of a robust network, giving remote users an opportunity to compete with far-away gateways because of the price incurred from hops across P-2-P nodes. I consider having the option to pay out at different rates to AP and P-2-P nodes so that if it is necessary to emphasize speed over access to new users it would be possible to pay out more to the P-2-P nodes, thus speeding up the network1 by increasing the reward for construction of high-speed links.

Additionally, this structure abstracts the cost of planning, managing, and operating the network arithmetically as a function of the cost willing to be paid by the end users. Thus enabling competition with traditional ISPs such as Comcast by eliminating a large amount of overheard. Comast might be available in your area for ~$70 USD a month, but if for whatever reason you can offer connectivity for less, then "bobs your uncle."

6 Walk Thru

6.1 New User Experience
User connects to unsecured access point and is prompted to deposit money to access the internet (HTTPS is used to protect payment details). After deposit, user registers a name and password then may connect to WPA2 password protected network with their new info. The password protected network provides access to the DWICP's network. From there the user may shop for a gateway to the internet. The DWICP's AAP will host an application that displays available gateways and routes. A price is assocated per MB for each gateway and path. Hopefully there will be many options to the user as Gateways may compete in price. Also, speed and price will be affected by hops thu P-2-P nodes. So for example, the cheapest ISP may be in the city, but your neighbor may decide to sell access for a little less.

User selects a local gateway at a given rate and starts browsing. When all the money in his account is depleted, access to the gateway is closed. Micro-payments are made from the AAP to nodes and gateways during the users session.

7 Potential for further decentralization

7.1 Auth token market
Rather than pay out to nodes with BTC, they are awarded with DWICP-auth tokens they can use to access the internet or sell. Traffic in MBs is used as "proof of work" to allocate tokens in a similar fashion to bitcoin mining. ( Proof of work used to compete for block reward ) It may also be possible to keep auth information in a distributed hash table. For now, the plan is for a centralized server (APP) to log traffic and make payments accordingly.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Hero Member
Offline Offline

Activity: 924
Merit: 511

View Profile
September 24, 2014, 06:28:51 PM

You could also use a voucher system, allowing the user to pay upfront for a voucher for X amount of data.

This also enables you to give your customers (if you run a shop) the ability to get free vouchers for doing X, Y and Z Smiley

I would also suggest offering multiple hotspots on different frequencies, this way you can distribute the load!

AC network would be great in an open environment :O
Hero Member
Offline Offline

Activity: 868
Merit: 501


View Profile WWW
September 25, 2014, 02:56:18 AM

ubiquiti access points would make this real easy to incorporate. The problem is that most people aren't going to have BTC to use.

Offline Offline

Activity: 5
Merit: 0

View Profile WWW
September 25, 2014, 01:34:07 PM
Last edit: September 25, 2014, 02:32:59 PM by BaltimoreJoe

To clarify: End users can pay with whatever. BTC payments are made to operator(s) of the network. A bitcoin address associated with each node receives micro-payments as it is used by paying customers to access the internet.

Ubiquity? I was thinking about a MikroTik or

To support most hardware with firmware images may create demand for pre-flashed nodes/specialty network hardware.
Pages: [1]
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!