Before I get to Fork in the road #3 I provide links to the previous 2 forks.
| Fork | Decision Point |
|---|---|
| #1 | Exploring trust on Hive |
| #2 | Building a Service Desk for PEPT |
Background
For the past week or so I have been reading and learning a lot about Hive reward distribution. A lot of my understanding has come about from analyzing what is unfolding as a result of a community reward system being challenged by some Hivers.
I extracted some valuable information from the following blog.
The user @Acidyo is insistent on destroying our Community - Important Announcement for the FreeCompliments Community!
Thank you @acidyo for your informative contribution in helping make Hive a better community. It is not an easy role to play when challenging weakness in a systems. Today I have a much better understanding of the concerns you identified.
Also, there was a Discord audio chat yesterday related to the about blog. After listening and reading a very active chat log I decided to ask a question to one of the Subject Matter Experts. I was seeking some sort of documented standard as guidance to use in my PEPT project journey. Something that would help me avoid future risk and ensure a fair, equitable and trusted distribution of rewards, be it Hive or some of my layer 2 tokens. The following is the Discord snippet to my question.
Thank You @pharesim Your response triggered me to take a closer look at something I already knew but needed to review. The following snippet is the start of my trustless expoloration.
Once I complete some more reading I will be looking at learning more about implementing decentralized autonomous organization tools in my project journey.
You can see from the following chart I have several layer 2 tokens created. At the top is my PEPT project and community token.
@fjworld/project-epaytraffic-pept-tokens
There is only 12,000 PEPT tokens in circulation at this time. Half is held off chain by myself, family and ePayTraffic.com members. The other six thousands are held on chain.
On ePayTraffic I have a Terms of Service for members and I created a Member Quality Scorecard point system to help me assess the activity and trustworthiness of my members. I have done some work in creating a Know Your Customer process that can help me onboard my traffic exchange members and visitors to my site. Any money owed and paid to traffic exchange members is done via ePay tokens on Hive. Some process improvement is underway to facilitate the web2/web3 integration.
The pepEntropy token I created is currently the only token on Hive where I return Hive rewards to token holders. It is a manual process at this time.
So far, all my offerings has been based on trust, best practices, loyalty and proven business relationship management skills.
Now I am ready to implement a governance process and tools to bring trustless DAO's into our PEPT ecosystem and economy. This will likely start with our TooFuckeh problem solving token.
I have started to make some funding changes with several accounts supporting PEPT and I am accumulating Hive and BEE for the project development that needs to be completed. I am thinking that adding staking to our problem solving token is a good start. I know what I want from a business flow logic but I do not have the coding skills required to make it so.
I am willing to exchange TooFuckeh tokens and/or Hive for some coding and ongoing support. If you are reading this and you are interested in some project collaboration or you know a coder that can convert my business logic to some kind of DAO it would be much appreciated.
Fork in the road #3
The path I was on has been guided on building trust. The new path taken will be about implementing a trustless protocol. Going forward will be about avoiding single points of failure.
All feedback, comments and questions are welcomed.
May Positive pepEntropy be with you.