Feedback has been received for various areas of the project and some changes are to follow. As stated in the announcement post, we're in a trial phase until April 22nd 2022 to allow for flexibility and adjustments to the curation model and the project overall.

_^[1]

---

Distribution/Curation Data Post

The current format for the data post has multiple issues which restrict comprehension of the curators efforts.

Problem

1. Post & comment votes are combined
2. Total vote weight used for each curator is provided (below the tables) but the vote weight used towards each individual author is not
3. The beneficiary attached to the data post isn't a reliable way to reward the efforts for those collating the data (previously set at 80%)

Solution

1. Comment votes will be dropped from the outgoing vote totals as the curation trail does not follow behind comment votes Comment and post votes can't be separated using HIVE SQL, so we're going to include comment voting with the trail and link this change with point 2 below
2. The rank column will be dropped from tables and the total vote weight used per author will be added instead. This will be in descending order, so the account with the highest total vote weight received will be at the top of the table
3. The beneficiary will change to 100% and an upvote using vyb.pob (and possibly vyb.fund) account will be applied to the data post to provide the data collator with a consistent reward (while also removing the ability for @vyb.curation to receive upvote rewards from these accounts)

_^[2]

Communication & Curator Opportunity

Heavy reliance on third-party applications like Discord, Telegram, Slack, etc. for communication with curators is an issue when we're looking to boost engagement and decentralisation on the platform.

Problem

1. Limited interaction with the overall community which is reducing the opportunities for curation expanding outward
2. The use of Discord as the main method for interaction with curators is creating an 'echo chamber' while also adding to point 1.
3. Curator selection is limited due to the sphere of influence held by the VCP Admin(s)

Solution

1. Communication post to be published on @vyb.hub* (then reblogged by @vyb.vyb) on the day of curator swap-over. This will include details about the curation trail and delegation allocation for the curators during the previous week, as well as a method for people to request curatorship (outside-in) and for previous/current curators to provide feedback (inside-out)
2. As above.
3. An application process will be shared within the communication post which will provide an avenue for interested persons to get involved with the curation efforts (specifically @vyb.curation curation blocks to begin with as VYB Check is still largely in development with the initial core group)

_^[2]

VYB Curation

is the main funnel for the VCP distribution/curation model. Curators are followed by the @vyb.curation account and its voting trail on a weekly basis and the data for outgoing votes are published on the vyb.curation account for the community to review. There are no guidelines set for the curators so they can vote how they like with the understanding that their upvotes will be publicly shared and acknowledged by the community.

Requesting community feedback for below. This isn't to say that problems and solutions aren't identified and being discussed or implemented already.

Problem

Solution

_{The above points will be updated with feedback received from the comments and credit will be assigned.}

_^[2]

VYB Check

is a method for rewarding excellent content through a submission and approval process. This process is backed with reason and transparency to ensure that some level of accountability is maintained for the curation votes received.

Problem

1. VYB Check workflow has primarily been off-chain during the initial stages to provide room for improvements and flexibility
2. Checkers have no incentivisation, except through their own intrinsic motivation, to approve/deny submitted posts by curators
3. Posts outside of the VYB/POB tags cannot be rewarded by the VYB Check VYB/POB upvotes
4. No method for VYB Check accountability has been set up like the VCP Distribution Data posts
5. Limited potential for !vybcheck submissions if restricted to VCP curators only

Solution

1. All VYB Checks will be moved on-chain with Discord being used to post the initial comment submission for Checkers to respond to (this will move to be fully on-chain once automation is set up for the @vyb.check comment response)
2. Sponsorships for Checkers are being offered by @proofofbrainio to assist with the VYB Check testing phase during the 3-month trial. This will be in the form of a POB delegation and curation trail follow from the @proofofbrainio account
   _{2.5. A method for rewarding liquid/staked POB/VYB to curators (submissions) and checkers (approvals/denials) is being developed. This will come from the curation rewards earned by the main trail generator (vyb.pob), after the initial 50% of the rewards have been sent to support the development of Proof of Brain via the @pob-fund account.}
3. A post called "VYB Check Approval Notifier" has been published to act as a bridge for rewarding these posts.
4. Approvals and denials by the Checkers will be posted on the @vyb.curation account in a data post.
5. We're going to test grounds with the !vybcheck submission process as a platform-wide solution, initially starting with a one-week trial phase.

_^[2]

---

_{**@vyb.hub is being created as an on-chain method of communication for specific areas of the VYB tribe. This will include, but is not limited to: tech-support/issues, moderation, governance, curation, distribution. Further details of this layer of communication will be posted in an announcement post via @vyb.hub.}

---

@vyb.curation trail support

CLICK to visit the @vyb.curation curation trail page

---