period participation 7/7:
period communication 7/7:
newPeriod Count = 2
newPeriod Participation = 9/9 = 100%
cumulative Communication = 9/9 = 100%
lowest for the period: 90812.06175390587
hey guys I donât understand what you expect me to do here. I read the OP post but I donât get what exactly I need to do.
I voted for all votes since the start of governance except for Snapshot which was due to travelling and not having access to the key.
My addresss is 0x2b888954421b424c5d3d9ce9bb67c9bd47537d12 and I always expain the vote in the corresponding topic post (even the one I missed and why) and also in a tweet.
period participation 7/7:
period communication 7/7:
newPeriod Count = 2
newPeriod Participation = 9/9 = 100%
cumulative Communication = 9/9 = 100%
lowest for the period: I could not get Dune Query to run⌠I will update after I figured out why
formula incentives: 0
TOTAL COMP for newPeriods 1 and 2: 0
bobrossi.eth - 0xb29A655f3D67B2B6724Fb22B2C2303cB660c946B
Hi mate, you need to draft a brief report like the ones other delegates have posted. The report muse include your participation rate (votes) and your communication rates (explanations of the votes) with individual links to the votes and to the posts communicating.
After that, use the new formula in the first post
I = ((log(h) - 4.55) * 3500) * M
M = 1 + (0.1 * P)
=>
I = ((log(h) - 4.55) * 3500) * 1 + (0.1 * P)
To calculate your HOP âformula incentivesâ, and include that number in your report.
âhâ for your specific wallet address can be found here, change the dates to reflect the periods.
Lowest for the period: 3519310.404120717
Formula incentives: 6987.60150695
2023-04-11 - 2023-05-10
Here I missed to vote on HIP-27 but wrote in discord that I could not make it due to travelling and having no access to my voting key as the voting period is only 5 days and I landed back hours after vote closed.
Hey thanks a lot. I did that according to your suggestions. But oh boy thatâs quite manual for something that can be checked easily by following the forum and/or snapshot. Plus without having this automated we run the risk of someone cheating.
Someone from hop should run these numbers, double check everything and then tell each delegate what their payout is according to the rules. Otherwise we can end up with someone cheating, or even making a mistake without their knowledge.
And since the process is so manual and error-prone, and takes time out of each delegateâs day if someone from Hop does end up running the numbers we should not be doing that ourselves manually.
I agree, generally, that this information shouldnât be manually and individually collated, because thereâs so much information to parse and itâs too to game. I know Shane goes through these threads each period to confirm various parameters but donât know how far that goes. Ultimately, automation of such a process should be the goalâI just donât know what that looks like.
I believe things could be automated, but not on its current form. For a bot to check communication automatically (minimum delegated amount and participation are easier) then it would probably be better that delegates estandarize communications in some way.
Right now some people post to Twitter, others comment in the specific forum post, and others have a dedicated forum thread with comments on their decisions. Some of those comments are standalone (for example one comment per HIP) and some others bundle communications from multiple HIPs in the same comment.
For a bot to consider all of this and not fail there would probably be some kind of technical development need, or a single place where delegates post their feedback that something automated can easily tap into (Google sheets?)
BTW, I also think it would be a great idea to automate or even partially automate some of this process. Participation and minimum HOP delegated per user should not be that difficult.
Our intentions are then more easily viewable and readily available to other voters at vote time. Could possibly automate cross posting to the forum too. Though that might be a bit more tricky.
The Dune query has been updated to Duneâs new v2 SQL engine (thanks for calling that out @francom).
The posts in this thread will be verified on Monday June 19 at 12:00:00 UTC so that they can be included in the next HOP incentive distribution. Complete your reporting on this thread by that time.
With regards to verification, in its current form it is quite trivial, assuming everyone provides all required information. I would be happy to discuss automating it the process in an open way, but wanted to add context by calling out that verification generally takes <30 minutes thanks to the detailed posts.
Hey @shanefontaine the table in my post above has a communication column which is somewhat cropped in the standard browser. Did you see those? Some of the rationales admittedly were fairly brief.
Lol clearly youâre right itâs just busywork in some scenarios. I think we can add more nuance to the requirement but I do think it adds value when people are incentivized to contribute to forum discussions though.
