ether1project / ecps Goto Github PK

https://staking.ethofs.com is an amazing platform that allows people with extra ETHO to lend to those whom want to run nodes but do not have the capital to invest.

As ETHO grows in price the money required to stake a node increase making more and more difficult for people to come up with the required funds. Yet, to lower the staking deposits would require a retooling of the entire node setup. It would require development time to update the code and people restaking the nodes which could jeopardize the network stability.

Thus a simple solution would be to allow Community Members to pool funds and create staking wallets. Using some concepts that are very popular in the DeFi space here is the basic ouline:

1. Anyone could create a Community Wallet. The wallet could be named to make it fun. For example "Jimmy's ETHO Rocket Gateway Wallet" etc.
2. The creator of the wallet could set a minimum deposit amount to participate. Do to transaction fees, you would not want too many people in the wallet, but at the same time setting a minimum deposit/contribution too high might limit participation. 500 ETHO seem like a good number for a GN, 250 ETHO for MN, and 100 ETHO for SN. Just suggestions.
3. The wallet creator would determine the split (like wallet owners do now) for the ETHO lender -- in this case the Pooled Wallet and the Node Operator. Splits range from 1/99 to 50/50. Same goes for the ETHO penalty if a node operator does not deploy the node after claiming the stake. If a node operator defaults the penalty would be refunded prorata to the wallet members.
4. Wallets will be placed into a "wallet marketplace" where others can review and decide what wallet to join.
5. Then when the wallet reaches the 5000/15000/30000 level (set during setup) it can/will be placed into staking.ethofs.com for a node operator to pick up.
6. Unlike the current setup a very important difference is each pooled wallet would have an expiration date/time period. 90/120/180/360 days. When a Community Member joins the wallet you are locked in for that period of time. Upon expiration the initial funds would automatically be return.
7. Same would go for wallet creation. There needs to be a set time period for something to happen. 10 days to fund and 10 days to deploy for example. If a pooled wallet does not reach its funding limit for the desired node for if a Node Operator does not borrow the funds would be refunded. The wallet cannot tie up people ETHO in limbo forever.
8. To avoid Wallet Spamming (creating dozens of useless wallet combinations that do not get community backing) there should be a "wallet setup fee" that will be refunded + interest at the end. For example there is a 100 ETHO wallet setup fee. If the wallet does not get funded or deployed the fee is refunded. If the wallet gets funded and deployed there is a 10% bonus paid back to the creator at the end of the contract, 110 ETHO. The extra 10 ETHO would be accumulated out of the rewards paid to the community wallet. The idea here is to keep too many spam wallets from being created, not to make money as a full time wallet creator.

This setup allows for interesting dynamics. You could have 360 day SN or 30 day GN wallets, any combination you like. Like short term and long term bonds. People can chose how long they want their ETHO in the wallet. Node operators know exactly how long they need to run the node with that wallet before it expires, providing them a known timeframe.

Post your comments/ideas/improvements.

ECP-2: Council should have Moderator Powers on Ether-1 Discord
ECP Discussion End: 05 Feb 2020 0:00 UTC
ECP Vote Date Start | End: 06 Feb 2020 0:01 UTC to 07 Feb 2020 0:01 UTC

ECP Originator: Pistol22Cal
ECP Sponsor: Pistol22Cal
ECP Motivation: Give Council Moderator Powers in order to work within chat channels more easily.
ECP Summary: Council Members should have moderator powers

Details

Council members should have moderator powers. Further experienced Council should have rights to create and manage channels in Ether-1 discord. Council members that have higher than moderator powers should be discussed and voted on within the council.

If an ECP is approved by the Community it should be accomplished by something similar to the Staking Dashboard. It would be nice to have a list of ECPs and that status of the funding level, if the ECP is "Open" it has not reached the funding required, if it is "Closed" then it is 100% funded. It would be very nice to also be able to click on the ECP to "drill down" and see those Community members that have contributed to the ECP funding -- a live list with the Members who contributed the most in order top down. When the Community Member clicks contribute they have the ability to provide a screen name with the donation. People can contribute in anonymity or for fun in the name of someone/cause/charity even.

In this case the SC would be a simple list of contributors, names, and amounts. Not sure about the release of funds etc, I think it should be tied to the multi-sig wallet controlled by the PC. So each ECP SC would be birthed by the PC multi-sig wallet. Did I get that correct? Devs? LOL.

In accordance with my other proposal, this ECP Funding Dashboard Budget is $100* and I will fund it since there is no dashboard yet for others to contribute.

*Dev-Team I can contribute the ETHO to the Dev Fund etc, let me know if this is OK? Please advise on the time/cost for the SC Template and Dashboard, just wanted to get started somewhere... Thanks!

The development of the Ether1 Project has fallen heavily on DevJames, Fallen, Treehouse, Primate and others in the past two years (sorry if I forgot to mention your name). Going forward in the spirit of Decentralization the project needs to migrate to a more bottom-up approach. The Community must propose ideas, direction, and improvements.

Therefore if a Community Member wishes to submit an ECP they must do some research on the improvement. Which means submitting a budget for the item (if there is a cost associated with the improvement). For example, a new "Android Wallet" that looks like "XYZ Coin" because that wallet just rocks. Ok, well maybe XYZ wallet was developed using the ABC Development Kit, and that cost $500. In addition, the cost of developers needs to be also included because no one at Ether1 knows how to use the ABC kit. In this case the Community Member got a bid for the developer's time and that is also $500.

In summary, the Community Member would submit an ECP that says something like this:

I, BigKillerDude, propose a new Ether1 Andriod Wallet, I have found the tool kit and developers, the kit is $500 and the developers have given me a bid for $500 and it will take 2 weeks.  Total is $1000.

We need this wallet because.....

Submitting an ECP with a budget brings a reality check to the process and also provides discipline to the process.

Summary

A provisional leadership council to work along side the existing Ether-1 team to decide on some immediate project needs, direction and to test and then finalize the rules/protocols needed in order to implement a fully functional decentralized governance system.

Details

1. The provisional leadership council should consist of 7 community members, contributors and team members and will be mainly responsible for refining and voting on proposals put forth by the existing Ether-1 leadership team.

2. A secondary responsibility will be to determine where any funds should be spent/used.

3. Any community member, contributor or team member should be eligible to run for a provisional council seat simply by nominating themselves and publishing their ideas/directions they want the project to head in.

4. The provisional council would be elected by the overall Ether-1 community.

5. Once elected/organized, a simple council voting majority should be used to pass/fail any proposal put forth for consideration.

6. The Ether-1 leadership team should have the ability to check/balance any delegated responsibilities during this provisional period.

7. Provisional council will remain in place until a permanent governance constitution is voted in and a permanent council is elected.

8. The Ether-1 leadership team will not be eligible to run for this provisional council.

The cryptocurrency space, with the advent of DeFi and new solutions has exploded in the last year and a clear and unique name is critical. While "Ether-1" has serviced us well, often it has been confused with Ethereum or other "Eth_____" spin-offs projects.

Rebranding has been discussed openly for several years but the cost has always been an issue. Recently a proposal was suggested to rebrand as "ETHO Protocol" which is unique and more importantly lets the project keep the ETHO ticket symbol for Wallets & Exchanges.

The cost of rebranding would be minimal as the greatest expense would be with wallets and exchanges and this is avoided.

The project would keep the Red Diamond Logo as well.

Finally the word "Protocol" itself is very descriptive and indeed represents more of what Ether-1 is all about: a set of rules to conducted business in the digital world.

The Ether-1 Council has discussed the name change and is in agreement for the rebranding. We post this here for input from our community. Let us know what you think!

Ether1 allows for immutable data to be hosted in the blockchain in total anonymity. This is a noble and just cause in the era of centralized control from both governments and corporations. The definition of free speech and expression can vary greatly and it is almost impossible to define, nor should it be defined.

However, with that said, Ether1 cannot be without limits. Community Standards must be created and enforced for objectional content such as Child Pornography. It is simply indefensible as any right to free speech or expression.

If Ether1 does not create and enforce Community Standards it will quickly become a dumping ground for the worst possible content and people on the Internet which would destroy any value or usefulness for legitimate commerce.

The example of Child Pornography is every simple--everyone gets it. The bigger problem is what comes next? How is it dealt with? Whom decides? Where does it end? These are not easy questions to answer. Even the world's largest tech company--Google has issues with acceptable standards, I reference this recent expose' on YouTube as a great example of the challenge.

http://progressvideo.tv/videos/is-youtube-doing-enough-to-fight-hate-speech-and-conspiracy-theories

The Ether1 has the unique ability with its technology and decentralized approach to not let any person or persons (The "Content Committee" for example) police the network but the network operators, users and community members themselves can decide what is objectionable and not. And furthermore, the ability to let the "network" operate a Content Kill Switch (CKS*) to remove reprehensible data.

This ECP Proposes a Formal Discussion of Community Standards and to gather ideas for the CKS which will be a future ECP with an implementation budget.

Budget $0.

*CKS -- Community Kill Switch or Content Kill Switch, both seem to ring nicely.

In the past a few of the Founders have born the brunt of not just development time but money. All future ECPs should be funded by the Community. As per my ECP suggest #2.

As we transition from the Ether1 Management Team to the New Provisional Council (PC) there needs to be a transitory framework by which things can get done and the Community can provide bottom-up direction.

Our Discord Server is the primary property for project collaboration thus it should be used as a simple method for Community Contribution.

There should be a standard protocol for ECPs and voting.

When a new ECP is created on GithHub a notice should also be posted in the Governance Channel in Discord for Community awareness.

The clock starts with the time date/stamp of GH creation:

1. Each ECP has a 14 day life-span for comments before voting. While live banter can take place on Discord, serious amendments pros/cons to the ECP should be posted under it on GitHub.
2. At the end of the 14 days, the ECP comment period has ended. The ECP will be updated by the author within 72 hours for Final Draft.
3. The final draft will be locked on Github and will go to vote on Discord under the Voting Channel, there is a 7 day voting window on the ECP.
4. If the ECP is passed and requires funding the ECP will be posted on the ECP Funding Dashboard.

So in summary
Days 1-14: Comments
Days 15-17: Amendments
Days 18-25: Voting

There is no cost to this ECP.

This is a test

Based on some of the discussion earlier with Hashratez on decision making cycles, I feel it is important for us to offer additional streams of communication such as an emailing list that can help ensure that people do not miss votes and other upcoming community events without at least being informed of them.

There are few things as bad as coming back and finding changes you knew nothing about being in place. That feeling of "Hey! W**?" is not the nicest one around. A mailing list could go a long way towards alleviating that. Particularly as members willing to sign up for such are more likely to be actively contributing constructively.

In this case, setting up an emailing list cost should be none or minimal.
If we want to get fancy and integrate FB/TWITTER/ETC hootsuite is something to look at for the longer term. However, a mailinglist is a good starting point.

I think one of the first things the council should get to work on is developing or financing the development of an opensourced gateway for selling eth0fs hosting for fiat.

Cryptomarket independent fiat pricing for the service provided will help set a fairer market value for Ether1 as long as pricing remains competitive with standard hosting options.

There are multiple ways or making this happen, a wordpress template, bootstrap etc Most of the payment providers like Paypal/Alipay/Wepay etc all have fairly similar apis and ought to integrate fairly smoothly.

ECP-3: Ad Campaign on Twitter 60 days then reevaluate
ECP Discussion End: 14 Feb 2020 0:00 UTC
ECP Vote Date Start | End: 15 Feb 2020 0:01 UTC to 18 Feb 2020 0:01 UTC
ECP Originator: Pistol22Cal
ECP Sponsor: Pistol22Cal
ECP Motivation: Ether-1 Awareness - Bring in people to the platform
ECP Summary: Budget for Twitter Ads

Details
https://business.twitter.com/en/help/campaign-setup/create-an-awareness-campaign.html

1. $1 per day -- Daily Maximum: this is the amount you want your campaign to spend per day. We’ll automatically stop showing your ads when this number is reached each day, and daily budgets reset each day at midnight. Daily Maximum is a required field for every campaign.
2. https://business.twitter.com/en/help/campaign-editing-and-optimization/ad-groups.html
3. Access to Ether-1 Twitter by a council member that knows how to run and setup ad’s
4. Payment Method - https://privacy.com/pricing - Suggest we use this or if someone would like to be reimbursed and pay for this with a personal account that would be fine too.
5. Allotment from Dev. Fund of 5100 ETHO per month for this expense or Equivalent $30 USD per month in ETHO
6. Who does what task can be discussed within the council and development team

It is important for any efforts, projects, solutions, to have a consistent and unified message. This avoids confusion to the greater world at large. People need to relate to people. Thus far Ether1 has not had any central point of contact in official capacity as such. I believe that this has been detrimental to the project. Having a "face behind Ether1" would be good.

With that said, soon the Provisional Council (PC) will be announced. I propose the new PC elects an Official Spokesperson to the project that can be used in all official messaging: Press Releases, Tweets, Social Network engagements, Announcements, Interviews etc.

Cost/Budget to this ECP is zero.

Please note I am not interested in being this person.

PLEASE ALL COUNCIL MEMBERS LIST A WALLET YOU WANT TO USE FOR COUNCIL BUSINESS.

THIS IS ALSO THE WALLET WE WILL USE FOR THE MULTISIG WALLET.

Pistol: 0x31e2d1e5711f90e549b6809bDCedB44af8854B2b

ECP-1: Distribution of Development Funds
ECP Discussion End: 04 Feb 2020 0:00 UTC
ECP Vote Date Start | End: 05 Feb 2020 0:01 UTC to 06 Feb 2020 0:01 UTC

ECP Originator: Provisional Council
ECP Sponsor: Provisional Council
ECP Motivation: Pay the Bills
ECP Summary: How to spend Dev Funds

Details

-PROVISIONAL BUDGET – REVIST IN 60 DAYS – IF THIS BUDGET WORKS WE VOTE TO MAKE IT PERMANENT FOR THIS COUNCIL.

-Total Budget $ETHO - 172,800.00 Per 30 Days

-This ECP to be activated 15 Feb 2020

-Allocation of Funds

· Council Fund - 100% of Dev Fund goes to this wallet.*

*Funds are to be spent on Approved ECP's only.

**Costs are to be paid via single ongoing ECP updated each month, this ECP has Pre-Approval to avoid costs not being paid. Costs are to communicated to the council no later than the last day of the month. Funds shall be sent to Dev-James no later than 3 days after council knows the amount needed.

Anyone who needs funding must create an ECP for that funding to be covered. Standard 4 to 7 vote needed for approval. ECP's can be vetoed by Dev-James and a veto can be overruled by a 6/7 vote from the council.

Section 2. Creation
--- CableGod to create 1 smart contract / multisig wallet for the council 4 out of 7 votes needed to send funds ---

1. Council Fund

Section 3. Execution

Dev-James - Project founder of Ether-1 - Is to distribute funds every 30 day period starting, as outlined in this ECP if approved via 4/7 vote by Provisional Council - 15 Feb 2020

ALL WALLETS THAT COLLECT ANY FUNDS FROM THE DEVELOPMENT FEE SHALL BE PUBLICLY KNOWN.

Issue: You host multiple files/websites on ethoFS, BUT you see that out of the sudden you can't visit your site/files anymore because OOPS... you forgot to extend your contract.

Fix: Automated e-mail towards user e-mail address, first e-mail 20 days before expiring; a warning that 'some' of his/her ethoFS hosted contracts are about to expire. Next, 7 days upon expiring, same message. Last warning 1 day before the expire date of the contract. (If this all can be done over a #Decentralized mail system it would be even cooler).

By doing this people will not forget about ending contracts, it also keeps the ethoFS user satisfied by our services.

Dylan