Skip to content

Comments

Permissionless Fishermen#11

Open
DragonDmoney wants to merge 1 commit intopokt-network:mainfrom
DragonDmoney:permissionless-fishermen
Open

Permissionless Fishermen#11
DragonDmoney wants to merge 1 commit intopokt-network:mainfrom
DragonDmoney:permissionless-fishermen

Conversation

@DragonDmoney
Copy link

This is the official spec PR following ADR 001. Let me know your thoughts and if there is anything you would like me to change!

CC: @luyzdeleon, @Olshansk, @andrewnguyen22

@Olshansk
Copy link
Collaborator

Olshansk commented Sep 3, 2022

@DragonDmoney I printed out section 3.3 and reviewed it by hand since it was a bit easier to do that way. There are some nits, some edits, some questions, etc... PierreFishermanReview.pdf

I think it's a good starting point, and a huge step in the right direction, but still needs a bit of work & discussion. For topics that you're unsure about, can you leave a DISCUSS: <topic> directly in markdown so we can use that as a starting point. In particular, I think it'd be good to have @andrewnguyen22 feedback on it too, so we can figure out what the minimum viable changes are that we can commit and iterate on in future iterations.

Also, two other things there missing are:

  1. I think you should add Permisionless fisherman as a step in Permissionless Fishermen #11 since we likely won't have it straight off the bat.
  2. Consider looking into additional attack vectors or dissenting opinions here: https://github.com/pokt-network/pocket-network-protocol/tree/main/utility#5-attack-vectors.

For example, a madmen could potentially DOS a fisherman causing them to record that a ServiceNode was unavailable, causing more rewards to be distributed amongst the other fisherman. Note that this isn't a very well thought-through attack, but I think there are several others that should be explicitly considered.

Copy link
Collaborator

@Olshansk Olshansk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comment above

@DragonDmoney
Copy link
Author

@Olshansk Here are some questions I had about your review:

V1 Response Questions.pdf

@Olshansk
Copy link
Collaborator

@DragonDmoney just wanted to update: this modification to the spec is not a priority right now, but I do plan to revisit & think about it after the current "revamp" is merged in.

@Olshansk Olshansk added documentation Improvements or additions to documentation utility Utility module related changes labels Jan 26, 2023
@Olshansk Olshansk added this to the M5: IoS (Innovate or Skip) milestone Jan 26, 2023
@Olshansk
Copy link
Collaborator

Olshansk commented May 16, 2023

@DragonDmoney Might ask you to pick up this work later this year ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation utility Utility module related changes

Projects

Status: In Review

Development

Successfully merging this pull request may close these issues.

2 participants