Pre-Proposal: Integrating low-power IoT devices to a dash blockchain

[vazaki3]

This is a pre-proposal. In case we have a positive feedback from the dash community, I may put it as a proposal into the budget.

The idea is to build some miners that will use the Proof_Of_Coverage protocol and store their earnings into the Dash blockcain.

https://dl.acm.org/doi/10.1145/3125503.3125628

Since 2016 I have warned the Dash community about the idea (look here or here or here or here or here)

Some others work on this idea since 2013, and now the idea is already implemented in Helium (HNT), and has a huge success.

https://explorer.helium.com/coverage

In helium they have the validators who are equivalant to the masternodes.

But there is still time for dash to recover and take part in the new upcoming IoT market.
So what do you think? Is this a good idea?

 

[GrandMasterDash]

This will create a mesh network or just a regular hotspot?

 

[vazaki3]

This will create a mesh network or just a regular hotspot?

What I have in my mind is a mesh network, similar to the Helium network.
But of course regular hotspots in crowdy places where bandwidth is needed urgently and could be paid, are also usefull.

Dash could implement payments for the InternetOfThings by using both mesh networks and regular hotspots, and by using different RF technologies like lora, wifi, 5G e.t.c.

All these could be investigated and be implemented, based on the opensource code of Helium, provided of course that the masternodes owners vote in favor of a bandwitdh coin, here in this strawpoll, and most importantly into the budget system in case a proposal is posted there.

 

[GrandMasterDash]

I dunno, not sure I want to see separate coins / tokens. The problem with tokens is that new ones can be issued with new compliance rules, making the old one redundant. Everything should be ground in dash to avoid such situation.

 

[vazaki3]

I dunno, not sure I want to see separate coins / tokens. The problem with tokens is that new ones can be issued with new compliance rules, making the old one redundant. Everything should be ground in dash to avoid such situation.

No separate coins. Only Dash.

My proposal assumes that the RF/IoT nodes are paid directly in dash, and mine directly dash.

The Proof of coverage is an alternative way of mining. You are paid if you can prove that your RF/IoT node covers a certain area. In order to prove that, many nodes must be present in your area, so that the other nodes confirm that your node truly resides where it is supposed to reside. This is how Helium works.

Dash Masternodes could vote and allocate an amount from their Dash budget, and give it to the RF/IoT nodes who offer coverage or bandwidth services in the name of Dash.

The problem with tokens is that new ones can be issued with new compliance rules, making the old one redundant.

Dont forget that an IoT network resides locally, because it covers and serves a specific area. New rules is not necessarily a bad thing. Depends on the rules. Sometimes universal rules cannot be applied locally, and in that sense having rules that are allowed to vary locally is a good thing. For example the 5 dash proposal fee may be ok for US, but not for Nigeria. Thats why the Dash community should allow different rules for the local IoT networks, provided of course that these rules are not against the core values of Dash (as those are defined by the current majority of those who hold Dash voting rights) .

 

[GrandMasterDash]

Okay, understand, but I suspect this is way too radical for MNOs to accept.

This seems very similar to what I've previously suggested, to build a new node class for local content delivery e.g. streaming services that require fast and low latency connections. You need to prove this is a robust algo. From what I understand, one big problem Helium has is requiring centralized registration of the node.

 

[vazaki3]

From what I understand, one big problem Helium has is requiring centralized registration of the node.

Yes...the proof of Coverage protocol of Helium has several flaws.
The registration was free and decentralized from 2013 until the begining of 2021, and the DoItYourself nodes were allowed.

But then a wonderfull hacker discovered a bug in the Helium Proof of Coverage protocol, and stole 1 million HNT.

Instead of fixing the bad design of the Helium proof of Coverage protocol, the incompetent Helium engineers , supported by the well known government's agents whose permanent goal is to control and destroy every crypto, they decided to ban the DIY nodes, turn the Helium registration centralized and transform all Helium nodes into "light Helium nodes", nodes that are prohibited for now on to carry a real blockchain. The Helium blockhain resides now only into the validator nodes, 2500 nodes (similar to the masternodes) who own more than 10000 HNT, govern the Helium network and (similar to Dash) are controled by the agents.

In this very moment, it is the perfect time for the Dash community to intervene, and in the name of decentralization, offer to the crypto community a real wireless/IoT decentralized bank.

The community of Dash should fix the design bug of the proof of coverage protocol, and make the IoT decentralization and the wireless decentralized bank possible, for the future generations to thank us and not blame us.

 

[vazaki3]

You can read the Helium whitepaper here.

http://whitepaper.helium.com/

This is how the proof of coverage works: a challenger constructs a multi-layer data packet (a multi-layer challenge ) which is broadcasted wirelessly to several targets. Each target signs the receipt, delivers it to the challenger, then removes their layer and broadcasts it for the next target. Then there is the transport fee. Devices using the network in order to send and receive data to and from the Internet must pay the Miners a transport fee. This fee compensates the Miner for delivering data packets between the Device and the intended router on the Internet.

I think that the important thing is the transport layer and that the proof of coverage and the challenge layer is not really needed. If someone gives you a packet, and the packet is finally delivered to its destination by the network, then you prove at the same time the coverage too, and the challenge is completed! So a multi-layer data packet , signed by the router that first serves the Device's data packet, then removes his layer and broadcasts it for the next router, until the final destination is reached, could be used as both a proof of transport and a proof of coverage, in order to mine coins.

 

[GrandMasterDash]

I think maybe you could ignore / bypass any need for changes to mining / treasury funds.

1. I think you could start with a working node that leverages dash quorums and registers to a masternode. You do this initially to demonstrate that this actually works as intended.

2. You split end user payments, 20% to the node operator and 80% to whoever delivers the data.

3. Once this proof of concept is complete and MNOs realize they can make more money, you then submit a proposal and code change to multiply the number of nodes by making these nodes independent of the masternode network. The masternode network will manage the Proof of Service to randomly verify and enforce data delivery, speed and latency requirements. This new node will have a collateral requirement to fit your desired coverage area e.g. 10 dash collateral to produce 462900 nodes.

4. If you ever get this far then the final step is a proposal to change treasury allocation, creating a 25% fund exclusively to fund content creation / streaming opportunities.

 

[vazaki3]

I think maybe you could ignore / bypass any need for changes to mining / treasury funds.

1. I think you could start with a working node that leverages dash quorums and registers to a masternode. You do this initially to demonstrate that this actually works as intended.

2. You split end user payments, 20% to the node operator and 80% to whoever delivers the data.

3. Once this proof of concept is complete and MNOs realize they can make more money, you then submit a proposal and code change to multiply the number of nodes by making these nodes independent of the masternode network. The masternode network will manage the Proof of Service to randomly verify and enforce data delivery, speed and latency requirements. This new node will have a collateral requirement to fit your desired coverage area e.g. 10 dash collateral to produce 462900 nodes.

4. If you ever get this far then the final step is a proposal to change treasury allocation, creating a 25% fund exclusively to fund content creation / streaming opportunities.

No.
I am not going to create any working prototype for dash.

I will ask for a decentralized-wireless-bank-developer-incentives-fund (similar to the protocol-developer-incentives-fund ). In case the wireless bank incentives fund is accepted by the masternodes, I will start compete with other developers who want the fund, create a prototype tied to dash and follow the steps you proposed.

The market is huge and very fast growing, as shown in the below map.

Why start working for the dash community in case they dont want it? No incentives for developers, no development. Developers are paid 10000$ per month for coding, they do not start working without incentives.

In case nobody cares here in dash (I am afraid this is the case, when I look at the voting participation in my strawpoll), I will propose the same to another crypto, until a developer incentives fund for a wireless decentralized bank is finally accepted somewhere.

 

[vazaki3]

<vote history>
Integrating low-power IoT devices to a dash blockchain. Is this a good idea?
yes
Votes: 2 66.7%
no
Votes: 1 33.3%
other
Votes: 0 0.0%

Total voters 3

</vote history>

 

[vazaki3]

No.
I am not going to create any working prototype for dash.

I will ask for a decentralized-wireless-bank-developer-incentives-fund (similar to the protocol-developer-incentives-fund ). In case the wireless bank incentives fund is accepted by the masternodes, I will start compete with other developers who want the fund, create a prototype tied to dash and follow the steps you proposed.

Anyway.
I may spend 1 dash to propose for a decentralized-wireless-back-developer-incentives-fund, in case of course the proposal fee falls to 1 dash.
I would like to propose it, and let it being rejected, just to be 100% sure that the Dash masternodes are stupid indeed.

So, in case I will propose it, I would like someone to help me propose in proper english, because I do not speak or write english very well.

 

[Sven]

How can the network be sure that you'd actually be able to deliver such a significant project? And why should we trust you that you will, even if you're able?

 

[AgnewPickens]

How can the network be sure that you'd actually be able to deliver such a significant project? And why should we trust you that you will, even if you're able?

He helped code MNOWatch website, you may remember him as Demo, Tungfa used to ban him for his posts, but he comes up with a lot of good ideas.

 

[vazaki3]

How can the network be sure that you'd actually be able to deliver such a significant project? And why should we trust you that you will, even if you're able?

This is #13

I am asking for a decentralized-wireless-bank-developer-incentives-fund (similar to the protocol-developer-incentives-fund ).
In case the wireless bank incentives fund is accepted by the masternodes, I will start competiting with other developers who also want the fund. And let the best win.

After approving an incentives fund, many developers may present many solutions. So the important question is, who you gonna trust to judge which solution is the best. Shall the network decide by vote?

But lets do the first step, and solve the problems one by one.

1. Will the network approve an incentives fund regarding a wireless bank, so that the developers start working and competing on it?
2. How much money this incentives fund may be? Will you vote the numbers on that?
3. Shall the network or the core team decide which, among the many developers who may provide many solutions, is the best solution?

You have to answer the above questions. Competitive developers are a scarce resource, and they will not join and help your network unless you become serious.

 

[vazaki3]

When I posted this thread, the coinmarketcap snapshot was:

Historical Snapshot - 05 September 2021 | CoinMarketCap
Dash 56th coin (market cap 2,7 billion $) and HNT 64th coin ( market cap 2,3 billion $ )

2 months passed, nothing has been done, and here you are the new shapshot:

Historical Snapshot - 07 November 2021 | CoinMarketCap
Dash number 75 ( fallen at 2 billion $ market cap), HNT number 44 ( skyrocketed at 4.5 billion $ market cap).

Well done masternodes voters, once again you proved how much lazy and stupid you are. Keep up making bad decisions, keep up trusting bad actors, keep up preserving voting rights only for the stupid rich people, and dash will certainly perish.

Vote the numbers !

 

[vazaki3]

<vote history>
Integrating low-power IoT devices to a dash blockchain. Is this a good idea?

• yes
  Votes: 4 -- 80.0%
• no
  Votes: 1 -- 20.0%
  
  
• other
  Votes: 0 -- 0.0%
  </vote history>

 

[vazaki3]

In the meantime, the HNT blockchain engineers are complete amateurs.
They reversed their blockchain! Yet, after doing such big mistakes, they still managed to double their marketcap in two months!
2.5 billion dollars more for them in two months, amazing isnt it!

I really wonder why Dash does not enter into this so profitable market of IoT devices.
Is Dash blockchain not as fast as it is supposed to be, in order to support IoT ?
What the Dash stress tests are saying?
Can Dash blockchain support transactions of 300.000 nodes, as HNT does?

 

[Sven]

...
Well done masternodes voters, once again you proved how much lazy and stupid you are. Keep up making bad decisions, keep up trusting bad actors, keep up preserving voting rights only for the stupid rich people, and dash will certainly perish.

As for "making bad decisions", assuming this refers to your idea, there was nothing for MNOs to decide on. Put a proposaal out and promote it! But I can already tell you, calling people lazy and stupid won't win you much support.

 

[GrandMasterDash]

To get this to pass you need to gather a team / crew / rabble of people you can put names to, list their their qualifications for the job and tell us that your collection of pirates are going on this journey. Not asking you to build this yourself, only to gather the enthusiasts you need to give it a try.