This post aims to revise & renew the Delegates Incentives Program from May to December 2024, Previous budget was allocated here: PGM-46: Renew delegate incentives program
Context
Reminder of incentivization eligibility criteria:
Governance participation: Initially 80%, update to minimum 90%
Obligation of transparency: Explain voting rationale
Delegation Threshold: Minimum 10 000 hPAL delegated from 2 stakeholders
Recognised Delegates have to self-report on a monthly basis in this thread in order to get their incentives
Rationale
This proposal aims to evaluate the Paladin delegates status & spending over the past months, as well as propose to revise & renew this program for an additional 6 months.
And since 0xTekGrinder was elected as a councilor (which has a higher allocation), I assume you meant that there are only 3 eligible delegates, correct ?
That’s up to him to chose, but yes it would make sense. You can perfectly do both roles, you just get paid for one as the goal is to favour diversification of active contributors.
This rule only targeted 2 of the most active contributors including 0xTekGrinder who was a delegate + signer + building products on top of Paladin & myself as I was active contributor + delegate + signer since 2y+
The main goal was preventing us to earn from $1K to $1,5K as councilor/signer (new compensation up from below $50/month for years) + the delegate compensation (voting power based) so not a fixed amount but below $1K/month for every delegates, and which you can significantly influence since the core team is delegating a lot of voting power.
Pretending you want to diversify contributors is not true as you added this rule in a previous post saying that “anyone can create proposals but only councilors or paid service providers can be compensated to do so” (ignoring the main suggestion of an onboarding program to bring new contributors), and also asked current active contributors to choose between delegate or signer role unless if they did one for free.
Disappointing & concerning to see you decided to censor the forum by deleting an important comment, go against your own recommandation of not changing the majority of signers at once to reduce risks, validate the proposal mostly with team voting power & prevent active contributors from getting involved in several ways, just to avoid rewarding up to $2.5K/month in PAL tokens to 2 very active contributors and to re-centralize treasury day to day decisions/operations (with multisigs related discord channels supposed to be opened to public for a while as agreed on the forum but still private despite many requests)
Anyway I guess 0xTekgrinder is doing councilor since the vote has been pushed so voted for & I’ll post the quorum below.
No the main goal was to incentivise active stakeholder diversity.
You’re the only person I ever met who expects to be paid by proposal.
It’s not ignored, write an actual proposal and we’ll be able to discuss it seriously.
We litterally asked you to simply move it to another post, send you the actual text, you refused because you like to play the victim.
We’re in the process of opening them, the Council has been up for barely a week, this is its first edition, we’re finding our marks. You also fail to mention that we shared a file with all transactions done by the Council since inception (found here).
Hey I’m reporting for May and June 2024
I apologize, I have been slightly less involved in the governance conversations, a lot of work IRL
My ENS is tradercameraman.eth
Voting Power: 132.74.k
Delegators: 5 addresses (including mine)
That’s not what I said, just saying I’m not a councilor nor service provider so no incentives in spending time working on more proposals (your behavior with me clearly showed you wouldn’t support SP proposal so didn’t even proposed, but you know very well that’s what I wanted to do)
The fact that you actually think it’s acceptable to abuse of your admin power to delete informations from a delegate before the vote ends (with vague moderation pretext), and still trying to put the fault on me is the kind of actions that really speaks for itself.
If you really wanted this text to be reposted elsewhere, you would just have done it directly (faster & better to make sure to one misses it) but that’s not what you did.
This is also surprising tbh. There has been various requests asking you to make public the multisigs channels, and you accepted. There was 2 channels: One to discuss with the signers, and one fully setup with Den notifications it was only requiring to change settings.
However instead of doing that, you litterally deleted or hidden both channels, and started a new one for council notifications, which required you to redo all the Den settings for all multisigs. Btw the configuration is incomplete meaning that no one is able to quickly see what’s happening (unlike on the previous channel).
Anyway, doing all of this just to avoid making multisigs channels publics is suspicious/weird behavior too.
And yet I supported paying you retro-actively, I’m sorry but we both know this is wrong, stop playing the victim, if you want something put up a proposal, this has been the process since launch.
Except you forget that I have dozens of any other tasks at hand at any time of the day, so no, I couldn’t, which is why I asked you nicely to repost it.
The fact that you think I have time do such petty things like changing channels is beyond me (hint, we have someone managing this for us internally and he probably just screwed up, I will ask him to fix the transaction channel, the conversation channel will remain private for obvious operational needs of confidentiality).
We simply try to operate both development and growth of the project the best we can, if it’s not sufficient and you feel you can do a better job, please by all means, apply to replace us on some tasks, Paladin is earning enough revenue to cover its ops given reasonable asks for funding.
It’s my fault, I thought I had made the council (multisig) public, and for Den, I unintentionally deleted the entire channel and so I had to put the channel back and configure the bot, I enabled notifications for current signers, if something is missing, let me know and I’ll add it, in any case it was not in order to “hide” anything, it’s really a human error.
Thanks for the feedback. The only one currently visible is for msigs notifications but missing the safes verification with Den bot so most informations are not visible. To enable it click on the Bell sign in Den, Select Add to Discord, scroll down to get the code & type the /verify code command in the channel:
The 2nd one is for signers discussions but seems it’s not public on purpose.
You argued against the proposal for weeks, then forced to reduce amount & partially vest over 6 months, to finally abstain from the vote so we have different views on that.
Doesn’t make sense as there shouldn’t be anything confidential in this channel which is just supposed to execute DAO decisions. Moreover you accepted several times in the past to make it public, not understanding why you’re now saying it must remains private.
I might consider applying once my availability is back to normal & after knowing what’s included in Mithras scope as a SP to avoid overlaps.
Delegate Self Reporting for July 2024
ENS: dydymoon.sismo.eth
Voting Power: 350 888 votes
Delegators: 11 addresses (including mine)
Fyi: KarmaHQ stopped tracking the Paladin DAO as they were doing it for free, asked the cost but they said $12k/year so not sure if the DAO is interested. Delegators amount can also be found on boardroom.io but not the breakdown.
We both know this isn’t true. A lot of voted decisions’ execution has to remain private in order to avoid front-running and other manipulations. If we are recommending to avoid making it public it is because we have seen abuses in other DAOs.
I think we can simply add these info on the delegate landing page.