Browse Source

Hush Foundation Proposal (#2)

* Hush Foundation

Aim is to help scale the Hush ecosystem by supporting software developers financially and creating a structure to give the non-dev community a voice into the future of Hush.

* Add files via upload

* Update README.md

* Delete HIP- Hush Foundation.txt

* HIP - Hush Foundation

Aim of foundation is to support HUSH ecosystem by creating a sustainable, community-driven funding mechanism and create a structure so non-dev community can have a voice for the future of HUSH.

* Rename hush foundation to hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update hush-foundation.md

* Update README.md

* Update README.md

Renamed Hush Foundation file name, added type.

* Added HIP Data Section
master
Eddy-O 6 years ago
committed by Matthew Reichardt
parent
commit
fd1c662af3
  1. 7
      README.md
  2. 56
      hush-foundation.md

7
README.md

@ -8,6 +8,9 @@ Having a HIP here does not make it a formally accepted standard until its status
Those proposing changes should consider that ultimately consent may rest with the consensus of the Hush users.
Number | Title | Owner | Type | Status |
------------- | -------------------------------------------| ------------------------------------- | ------------- | ------------- |
Number | Title | Owner | Type | Status
----------------- | ------------------------------------------ | ------------------------------------- | ------------- | --------
[1](hip-0001.md) | HIP Purpose and Guidelines | Matthew Reichardt | Process | Planning |
[2](hip-0002.md) | Hush Foundation | Eddy O | Process | Draft |

56
hush-foundation.md

@ -0,0 +1,56 @@
<pre>
CIP: 2
Title: Hush Foundation
Author: Eddy O. <ejdolivares@gmail.com>
Status: Draft
Type: Process
Created: 2017-12-27
</pre>
**AIM: To create a sustainable, community-driven funding mechanism to support software development and to create a structure to ensure the non-dev HUSH community has a voice.**
I've been listening to the public chatter and talking privately with a bunch of community members to get an idea of the HUSH community sentitment and how to improve the current situation. My conclusion is we:
1. Need to create a sustainable funding mechanism
2. Need to attract more developers
3. Need to make non-dev community feel more involved
A few community members and I brainstormed how to tackle these issues. The implementation could be a "foundation" made up of non-core community members (+ one or two core devs to oversee things). I see the issues stated above being tackled via two phases:
*First Phase*
Set up dev fee mining pool + website for bounties + allow community members to contribute ideas and vote for bounties (need someone on core team to review code and approve disbursement of bounty)
During this phase, Hush foundation's role is to collect weekly/bi-monthy updates from those working on bounties. An example of how a similar organization (CoZ) reports is here - https://medium.com/proof-of-working/weekly-report-19-2017-11-22-ee02be1b33b3. As you can see, there is no core dev update. Same would apply for this foundation- it is not about core development updates.
Notes:
I can start a business to run the mining pool to ensure we have decent hashrate when we start (if no one else is willing, i want to start a mining farm in China anyway).
I want to "kick off" the foundation by rewarding some past contributions (duke, kent, iceyballz, trunk, etc. --- sorry if i missed anyone, a bit new here)
I will lend a substantial amount of HUSH to fund the initial bounties (I have a list of a bunch and I want to get others to give ideas, too). The dev fee mining pool can re-pay me/others over time. This should attract devs faster.
We can stop this program at anytime (if the fund gets bloated and there's plenty of cash to fund dev)
*Second Phase*
Set up a dev competition. Devs would submit dApps, smart contracts, etc.... a good example of a similar competition here - https://cityofzion.io/dapps/1
Leading up to the competition, the foundation should/could be reaching out to organizations and setting up the framework for the competition. We can get some VIPs (influential people in blockchain?) + core devs + community to vote on the winner. After the competition, we may consider setting up some infrastructure to support the projects that were developed for the Hush platform (marketing help, a bit of funding, guidance, etc.). For the CoZ competition, some of the projects will go on to ICO- it ended up being very impactful for their ecosystem.
Notes:
I'm willing to donate some of my HUSH for this cause. maybe others would be willing to do it, too. if not, can rely on me to fund first one entirely)
We can wait to do this as the HUSH price increases, to leverage our impact and attract the most people
We can time also time this with an important release to the core (like smart contracts ability). This will help gain awareness for the cool tech core is working on! We may be able to get a corporation (which meshes with the ideology of Hush) to sponsor the competition with us (Microsoft did it with NEO).
____
There are a lot of details not discussed here- this is a rough draft. I have spoken with multiple members of the community and the feedback was positive, so I'm presenting the idea publicly. All work going forward should/will be done transparently on the #marketing-sync channel.
Lastly, I have a concern. I feel it's important that if something like this is implemented, the foundation be "officially" connected to the core team. The foundation should be run by the community, but at least one core dev should be a member at all times (and thus the "connecting link"). If it's not "officially" connected, then it will be hard to achieve the goals of the foundation.
Loading…
Cancel
Save