SIP-274-Initiated Dismissal of 0x6a6d127afF67436D08fe4a295e7ac4D20508b26A from Spartan Council

The passing of SIP-274 created an inactivity threshold for the maximum number of protocol-issued votes that can be sequentially missed by a Spartan Councillor before a dismissal process is automatically begun. In the case of Spartan Councillor 0x6a6d127afF67436D08fe4a295e7ac4D20508b26A (known the aliases poilk, pollick, etc.), this threshold has now been reached. As a result, this vote is being carried out as a part of the formal dismissal process.

The dismissal process entails those members of the Spartan Council who have not been found to be inactive, unanimously voting for dismissal using a Snapshot vote and then submitting the request to the council owner (currently the pDAO). This is that vote. The council owner will then be required to revoke the governance NFT from 0x6a6d127afF67436D08fe4a295e7ac4D20508b26A.

The missed votes to which SIP-274 is being applied are as follows: