How to prevent sock puppets claiming multiple plugin bounties? \ stacker news ~openagents

pull down to refresh

How to prevent sock puppets claiming multiple plugin bounties?

437 sats \ 6 comments \ @AtlantisPleb 21 May openagents

We have plugin bounties to incentivize devs to build their first agent plugin.

In the rules we say "For a limited time we are paying bitcoin bounties of ₿1M each (~$600 USD as of 5/13) to plugin developers for their first agent plugin."

Of course this creates an incentive for someone to create plugins from multiple accounts.

We're happy for people to create as many plugins as they want for the backend rev-share, but claiming multiple bounties by one person is cheating.

Unfortunately it looks like that happened in this case - and I didn't notice until after awarding both bounties.

Both plugins are in Go, use the same license, have completely new GitHub accounts, and similar writing & coding styles.

And it seems likely, though can't be certain, that this recent submission is from the same person:

#546030

Maybe it is time to suspend the bounty program, or add additional rules?

I'd appreciate any feedback or ideas on this.

view all related items

221 sats \ 1 reply \ @nullcount 21 May

Is the goal of the program to introduce new plugins? Or to introduce new devs that introduce new plugins?

Sounds like you may have a mytical 10x developer writing plugins for you. So why not pay them 10x the value-for-value?

By the way, socks are everywhere. There's only 25 ppl using SN daily, we each have dozens of accounts.

110 sats \ 0 replies \ @nullcount 21 May

Maybe you should lower the bounty after each successful payout. After all, the marginal value-add of an additional plugin should probably also decrease.

The 11th plugin should add more marginal value to the ecosystem than the 111th plugin.

258 sats \ 0 replies \ @k00b 21 May

If you pay for what a plugin is worth and not what their first plugin is worth, then this isn't a problem. There's no way to reliably determine if it's someone's first plugin, so don't rely on it.

Set the bounty to what a plugin is worth and save the sats for other incentive games.

384 sats \ 2 replies \ @BrianisNice 21 May

I am the creator of plugin #56030, and I want to clarify that I am not the same person as the previously mentioned plugin creator. While I did reference their Go code for inspiration, I have developed an entirely independent plugin with a distinct utility.

My plugin serves a different purpose and leverages a unique API. In fact, I have personally invested in accessing a specialized API to provide my plugin's unique functionality.

Although there might be some structural similarities due to referencing open-source code available here, my plugin is fundamentally different in terms of purpose, functionality, and the API it utilizes.

184 sats \ 1 reply \ @AtlantisPleb OP 21 May

Okay thank you Brian for clarifying

I did note that your GitHub account was way older than theirs which were created in the last few days

I'll review your plugin shortly and we'll rework this process moving forward

0 sats \ 0 replies \ @BrianisNice 21 May

Thank you so much! I look forward to it.

"Brian is Nice, Brian won't do such a shameless act"

😂😂😂