https://ipfs.busy.org/ipfs/QmbrG1RU61Qe9Ch9ZPckv6w8xf7y9yhwVoebZy35qVzNA9

1. Introduction

To further elevate engagement in the community, @steemph.cebu community leader launched a delegation system wherein a new voting model was in place. The new community voting model set an equivalent vote percentage for the amount delegated by each members. Thus, it scrapped the old community voting model where verified members was entitled to a vote.

How does the new voting model and delegation system works?

In the old voting model, only Cebuano and verified trail follower was entitled with a vote from @steemph.cebu bot. Usually, the vote is preset to a vote weight around 5% to 10%. To make lesser rooms for abuse, each members are only given a vote every after 12 hours. In addition, core leaders are given a luxury to vote its post without limitation. In all fairness, I have not seen one who abused this privilege. In the new voting model, everyone who delegates to @steemph.cebu receives a vote with a substantial weight as to the amount delegated. First, user delegates a steem power to @steemph.cebu. Then, a community moderator verifies the use's delegation through the community discord server by giving the user a role in the discord server, typically the amount delegated. Once verified, the user can now have a vote from the @steemph.cebu bot. For users and previously verified members whom steem power is less than 35 SP, they are given a vote with a vote weight similar to the old system. In addition, each user's post can only receives a vote every after 12 hours.

Read more about the @steemph.cebu's delegation system in the post: What's the hidden motive with steemph.cebu delegation system? authored by @jassennessaj.

Why perform this analysis?

When the steemph.cebu introduces the new delegation and voting system, members initially have responded very well. In my previous analysis, I compared the previous and current system. I was able to find out, last time, that lesser and lesser delegation is coming to @steemph.cebu bot. In addition, I have drawn out a conclusion that the launching was a success despite of the the decreasing trends. Today, I decide to perform this analysis to take a look and draw some conclusion in the current state of the delegation system of @steemph.cebu bot. I would also include to take a look into the bot's voting performance.

2. Scope of the Analysis

The analysis was performed using the data gathered from SteemSQL on 10 AM (PHI), August 5, 2018. The data where between May 26 and July 31, 2018. The time frame was considered based on the commits history on bot's Github repository: TeamMalaysia/Steemph.cebu. The last recorded update was on May 26 where the current voting and delegation system was released. The voting mechanism is depended on the amount of SP delegated as stated earlier. By which, vote weight percentage is between 5% to 60%. Two sets of query were run to obtain the required data from the steem blockchain. Each query run through TxDelegateVestingShares, Comments and TxVotes table from the steemsql. Data extracted from the database are averages and sums under a specific column in the tables mentioned earlier. Lastly, all data were subjected to statistical measure and plotting using Microsoft Excel.

3. Data Presentation and Results

What happen in the first month after launching?

https://ipfs.busy.org/ipfs/QmRNVDrqdpdHhx7N2E8zjKGRW7f6ZnGZYDo34A969TXUok

https://ipfs.busy.org/ipfs/QmNtQSkZxpDZi9WVWdXdZ7fxDDrogquH4ZmcSjq8yDMQWk

Undoubtedly, the launching has initially gained interest in the members of the community. As a proof, a 39 members have delegated to @steemph.cebu in the first week after its announcement. It has receives about 931,304 Vests or 2,969 SP. Over a month, @steemph.cebu has successfully receives 11,033,197 Vests or 5,445 SP of delegations from 63 users. However, the success was short-lived. Based on the trends, lesser and lesser of users had been delegating since the first two weeks after launching the delegation system. This shows how poorly the members of the community response on this initiative. From steemauto, there are total of 632 trail followers. Sadly, only about 10% have supported the initiative by delegating steem power to @steemph.cebu. The response is underwhelming as compared to the initial launching of the old voting system way back earlier this year.

You can read previous analysis about steemph.cebu in the post: Steemph.cebu bot-shifting to delegation system.

How about the SP delegation to @steemph.cebu in the recent month?

https://ipfs.busy.org/ipfs/QmWrYMK2WJ1s2MuKVfGfhSJdV16aYpqrma2Ntpej2gvqU8

https://ipfs.busy.org/ipfs/QmdATuGJa1vo8mbVda4QZQFczYTvzZAGYznyDdF1WAHaTm

Relatively, the number of delegation is too low after the first month of launching. I can only take into account 16 users delegating a total of about 1, 632,660 Vests or 990 SP. The amount of delegation recieves by @steemph.cebu has dropped by 56.50% as compared to the first month after launching. Over the last two months, 12,311,239 Vests or 6,075.7274 SP had been accumulated through delegation from 79 users. Even with underwhelming response to the delegation system, the community still able to reach a substantial amount of delegation from those who have trusted and supported such great initiative for the @steemph.cebu community.

https://ipfs.busy.org/ipfs/QmajTYiAUC3ZQ6fsoGt2NqK2VxFw7rDoByBRYijXLHgkMV
https://ipfs.busy.org/ipfs/QmUhTgyiRNmcL37cGrSySwQ5MkuDmaSb6YKjVYmHSo7JpH

In the discord server, there are 64 out of 79 delegator had been activated in the community discord server who are eligible for a vote from @steemph.cebu bot. About 55% are minnow trail follower who could not delegate any amount of steem power hence it only has 35 SP and below. From the steemsql, i have accounted 8 users (10%) who have less than 20 SP in delegation. However, among these 8 users, only 2 have at least 1 SP in delegation. So, among the 55%, only 2 users have delegate at least 1 SP to @steemph.cebu.
Since majority of the users activated has been verified as minnow trail follower (55%), the fewer amount and no. of delegation going to @steemph.cebu could be attributed to it. If we project all of 55% (77) users have a delegation of at least 20 SP, I could project an additional of 3,120,500 Vests or 1,540 SP. So, the community account will have at least around 18,805,530 Vests or 9,280 SP. The vote value per percentage designation will substantially be higher. Moreover, a substantial decrease in the delegation from 6,075.7274 SP to the current 5,203.564 SP delegation. This is a proof that the delegation was not fully supported by the community. I have observed un-delegation in the data, resulting the current value of delegation.

Steemph.cebu bot voting performance after launching delegation system

https://ipfs.busy.org/ipfs/QmNijzx3J3Fs5tJvnRJ2AReMwpG5DdppEHukFD4HZWP8fQ
https://ipfs.busy.org/ipfs/QmeURcKxwqbsr24uSNK2k7XUoLzVpYMfLboCxUt9gVo2Hh

On average, a total of 60 post per day were voted by @steemph.cebu. These posts receive 147 votes per day on average.
The 60 post per day is relatively good indication that the bot is performing well. If we take into account the 69 members whom eligible for a vote, the number of post is relatively lower than the number of members. This also suggests that the 12 hour voting cool down is finely working.
In addition, the number of post voted by @steemph.cebu bot was declining. While, the number of votes from the trail is increasing. The opposite trend suggest that, as lesser post to be voted by @steemph.cebu bot and its trail, more votes are voted to each post. This also tells that more members of the trail could vote in a post before reaching the predetermine voting percentage limit. The current trends is projected to be sustained in the coming month.

3. Conclusion

Initially, the new delegation system has gained interests from a handful of community members. However, this was short-lived as lesser members and users delegated to @steemph.cebu community. In the first month of implementation, 11,033,197 Vests or 5,445 SP of delegations from 63 users were received by @steemph.cebu. A substantial amount of delegation about 12,311,239 Vests or 6,075.7274 SP had been received in the last two months after launching. However, the current delegation in the @steemph.cebu account only amounts to 5,203.564 SP. This shows that, even after the designated time frame of the analysis, withdrawal of delegation was observed. Currently, I can say that there is a limited and a lesser chance that more delegation is coming to @steemph.cebu account. Is the new delegation system a success? Right now, it is 50/50. The delegation coming to @steemph.cebu is going to be in the decreasing end for the coming months. A positive take away from the new system is that there are a large number of minnow-trail-follower members till earning and growing their SP.

5. Tools and Query

The data used in the analysis is extracted from Comments, TxVotes, and TxDelegationVestingShares table on SteemSQL, and imported on Microsoft Excel. All data statistics and visualization were performed using Microsoft Excel. Core Query. (1.) The core query used to import the post and vote count is stated below:

SELECT
MONTH(Comments.created) AS [MONTH],
DAY(Comments.created) AS [DAY],
COUNT(Comments.permlink) AS [NO_OF_POST],
AVG(Comments.net_votes) AS [AVERAGE_NET_VOTES],
AVG(Comments.total_payout_value) AS [AVERAGE_PAYOUT],
AVG(TxVotes.weight) AS [AVERAGE_VOTE_WEIGHT]
FROM Comments (NOLOCK)
INNER JOIN TxVotes (NOLOCK)
ON TxVotes.permlink = Comments.permlink AND
TxVotes.author = Comments.author
WHERE
YEAR(Comments.created) = 2018 AND
TxVotes.timestamp >= '2018/05/26' AND
TxVotes.timestamp < '2018/08/01' AND
TxVotes.voter = 'steemph.cebu' AND
TxVotes.author != 'steemph.cebu'
GROUP BY
MONTH(Comments.created),
DAY(Comments.created)

(2.) The query used to obtain the data for the SP delegation to @steemph.cebu as follows:

SELECT
MONTH(TxDelegateVestingShares.timestamp) AS [MONTH],
DAY(TxDelegateVestingShares.timestamp) AS [DAY],
TxDelegateVestingShares.delegator,
TxDelegateVestingShares.vesting_shares
FROM TxDelegateVestingShares(NOLOCK)
WHERE
YEAR(TxDelegateVestingShares.timestamp) = 2018 AND
TxDelegateVestingShares.timestamp >= '2018/05/26' AND
TxDelegateVestingShares.timestamp < '2018/08/01' AND
TxDelegateVestingShares.delegatee = 'steemph.cebu'
GROUP BY
MONTH(TxDelegateVestingShares.timestamp),
DAY(TxDelegateVestingShares.timestamp),
TxDelegateVestingShares.delegator,
TxDelegateVestingShares.vesting_shares

SELECT
MONTH(TxDelegateVestingShares.timestamp) AS [MONTH],
DAY(TxDelegateVestingShares.timestamp) AS [DAY],
COUNT(TxDelegateVestingShares.delegator) AS [DELEGATOR],
AVG(TxDelegateVestingShares.vesting_shares) AS [AVERAGE_DELEAGTION]
FROM TxDelegateVestingShares(NOLOCK)
WHERE
YEAR(TxDelegateVestingShares.timestamp) = 2018 AND
TxDelegateVestingShares.timestamp >= '2018/05/26' AND
TxDelegateVestingShares.timestamp < '2018/08/01' AND
TxDelegateVestingShares.delegatee = 'steemph.cebu'
GROUP BY
MONTH(TxDelegateVestingShares.timestamp),
DAY(TxDelegateVestingShares.timestamp),
TxDelegateVestingShares.delegator,
TxDelegateVestingShares.vesting_shares

In addition, the data for the members eligible for @steemph.cebu bot vote is taken from the community discord server. For the bot updates mentioned in the text, the historical commits were based from TeamMalaysia/Steemph.cebu

Github Repository: TeamMalaysia/Steemph.cebu

Proof of Work: juecoree/Steemph.cebu

Posted from my blog with SteemPress : https://engrjueco.000webhostapp.com/2018/08/is-steem-power-delegation-still-coming-to-steemph-cebu

RE: Don't Chase the Low-Hanging Cheese