KIP-41: New Sophon Nomination: Nathan

This is an apparent consensus vote, open to ROOK and xROOK token holders.

• Vote 'No objection' if you agree with the proposal.
• Vote 'Object' if you disagree with the proposal. If voting ‘Object’ to the proposal, you are encouraged to voice your reasoning on the Rook Forum. Objections that are backed by a strong argument may potentially hold more weight than a simple objection vote.

Sophon Recommendation

The Sophons reached a consensus of "no objection", with all four recommending in favor of this proposal (one abstained due to other commitments). Given the urgency of this proposal, the Sophons reviewed it concurrently with the community.

Results

KIPs that receive > 50% ‘No Objection’ votes do not automatically pass. On completion of the vote, ‘Object’ votes will be analyzed and discussed by the Rook team and community. If a significant number of objections occur, the vote will either be marked as ‘Failed’ or enter a reconciliation phase. For more information, see the Rook Governance Beigepaper.

Proposal Full Text Links

LINK Forum post LINK Github post of record

kip: 41
title: new sophon nomination: Nathan
category: other
author:  @jasonw
status: voting
created: 2023-02-23
replaces: KIP-1
dependencies: 

Proposal

Onboard @Nathan_ as a Sophon to replace @Doge.

References

[1] KIP-1: Initial Sophon Onboarding
[2] Forum post: Our first trial of Sophon onboarding
[3] Forum post: Hearing from the Sophons: poll results

Background

The first batch of Sophons were nominated and elected via KIP-1 [1] in October 2021, and have served continuously in that role for 16 months. @Doge, one of the current Sophons, began to indicate their desire to offboard from that role in late 2022, leading us to workshop several possibilities for how to address his replacement as a DAO. Key among these was the idea to use this changeover to trial a revised election process that spans three stages [2]:

1. Nomination of the candidate, including information about the candidate’s background and contributions to the DAO.
2. Evaluation of the candidate by the community, including public sessions with the community and the candidate.
3. Voting on Snapshot for 5 days.

Rationale

The Sophon to be offboarded and replaced in this proposal is @Doge, who was described in the initial proposal as a community member as well as a researcher and token strategist [1].

Nathan’s nomination is based on the results of a poll of the Sophons last year about what makes for an effective Sophon [3]. In that poll, the two strongest requirements were detailed knowledge of the Rook Protocol as well as of the Rook DAO and community. As a prominent MEV searcher, Nathan has a high level of knowledge of the Rook Protocol and where it sits in the modern MEV landscape, and has even advised on the design of several aspects of the system in the past. As a longtime DAO member, Nathan has always championed Rook inside the industry, and has participated in DAO-led podcasts, interviews, and other events to help Rook’s message reach a wider audience.

Nathan has provided the following information to the community in support of his nomination:

• ENS address
  • nathanw.eth
• Discord and forum handles
  • @Nathan_
• Twitter handle
  • @NathanWorsley
• Background and Web3 expertise, and how this will benefit Rook DAO.
  • Nathan runs an MEV firm as well as a crypto exchange, and also works as an advisor to several projects. His unique perspective as both a user of the protocol (as a searcher) and an expert within this market segment, will ensure that Rook is able to tackle new challenges using its governance.
• Knowledge of Rook and prior contributions to the DAO
  • Nathan was an early DAO community member and served as an advisor to Rook on MEV and protocol development. He sat for podcasts with the DAO and has also shipped code across a few early Rook products.
• Current ROOK/xROOK holdings
  • Nathan has received 1000 ROOK for prior advisory work.
• Potential conflicts of interest
  • None
• Intent to abide by the Sophon KIP evaluation criteria (link)
  • Yes.

Specification

• Once posted as a KIP Draft to the forum, set at least one date for community interaction with Nathan, ideally at a governance workshop
• After reaching soft consensus per our usual governance process, set up a 5-day election on Snapshot