NeblioTeam / Neblio-Improvement-Proposals

Neblio Improvement Proposals
1 stars 1 forks source link

[New NIP]: NIP Create an Avado and DAppNode Package #9

Open Cesnili-Kanka opened 2 years ago

Cesnili-Kanka commented 2 years ago

Proposal Description

Brief: The Neblio Blockchain has slow moving organic growth and is relatively unheard of in the ecosphere of cryptocurrencies, unfortunately that means businesses and developers are unlikely to choose Neblio over competitors when launching their applications. To increase Neblio's public awareness among staking individuals with no direct out-of-pocket cost to the development team, a Neblio package can be deployed for hosting the blockchain and wallet DApp through Dappnode's and Avado's github repositories, see: [https://github.com/dappnode/dappnode] , and [https://github.com/AvadoDServer] .

Summary of DAppNode and Avado: DAppNode [https://dappnode.io/] is an open Debian based cryptocurrency centric Operating System catering to Dapps, stakers and P2P networks. Avado [ https://ava.do/ ] is a forked Operating System of DAppNode that is proprietary but can fetch and use DAppNode packages. DAppNode and Avado make staking more accessible to a broader market of less technology savvy individuals. With DAppNode, the OS is free to download and a computer purchase is optional but packages may have poor support, whereas Avado supplies customers with the OS + computer as a package deal and incentivizes community members to provide support. Combined, these two blockchain staking sources account for over 2,500 active nodes, with multiple different nodes running on a given host computer; and anytime a package is on boarded for use, all node operators will be able to pull and launch the Dapp's package. Avado also has a guide for implementing a DApp in the Avado DAppstore, [https://wiki.ava.do/en/developers/building-an-avado-package] .

Impact of Package Manifest: Operators of the DAppNode and Avado OSs are more likely to stake Neblio coins due to no minimum entry and competitive staking APY versus other operators of non-blockchain purposed host computers. This in turn creates demand for Neblio and awareness to Neblio's existence, opening the prospect for more partnerships and development. The tangible target is an increase in Neblio nodes.

Long Term Requirements: Lifecycle support will be needed throughout the course of the package's existence to ensure Neblio Dapp functions meet end user expectations with all necessary updates and fixes as Neblio blockchain further matures.

Avado Target Community Considerations: No Command Line Interface among users--any CLI has to be integrated into the user interface. Minimal user input is the goal, for example a public address, needs to be part of the onboarding procedure when the user opts to host Neblio from the DAppstore. Since the AVADO computer can run other DApps like Nodes it is possible to make the blockchain and wallet separate application packages should Neblio Team desire to go that route and treat it like a remote procedure call endpoint. Information from other packages like a Node ID should be automatically inserted without action needed from the user.

S.M.A.R.T. Tool: Specific--Create and launch a Neblio Dapp for Avado and DAppNode with lifecycle support Measurable--Active nodes launched can be tracked to quantify success Attainable--Neblio Team has the skills and knowledge necessary for onboarding a host package Relevant--On par with Neblio's organic growth and a decentralised chain hosted infrastructure Timely--Doable within 3 months if approved from the voting Neblio community, following vote closure

Proposal Voting Details

No particular block voting range is desired at this time, Neblio Team can decide the time duration and point which voting happens if they believe this proposal is beneficial to Neblio blockchain.

Other Information

For author contact pertaining to this initiative, reach out to @Cesnili_Kanka publicly within the Neblio Blockchain - Official Channel on Telegram. Unsolicited direct messages will be treated as malicious by intention.

nebliodev commented 2 years ago

Thank you for submitting a complete and well-written proposal.

I personally had never heard of DAppNode or Avado before, but this looks simple enough and doable and would expand easy access to running a Neblio node (even though we have already made it super easy).

My only hesitation around this proposal is that, in my limited research, it looks like anyone could do this work. It does not appear to need to be done by our team. It appears to just be nebliod in a docker container with a handy web interface for checking balance, stake management, and backups. It would likely be fairly simple to fork the Qtum DApp and modify it for Neblio.

So I believe we have 2 options for this proposal:

  1. We schedule this for a vote. If the vote is successful, this will get added to the roadmap and prioritized, the Neblio Team will spend development time researching and building this package for DAppNode and Avado. After release we will of course support and maintain the package with new versions of Neblio Core.
  2. Or someone else picks up the initial package creation. No vote required, no dev time from the Neblio Team needed. Then the Neblio Team will commit to taking over the maintenance and support of the package after the initial release.

Opening this proposal for feedback and discussion.