---
title: Swingby Issue
tags:
---
# Swingby Issue
## What happened
When engaged to do the Swingby governance setup, I communicated clearly that:
1. February will be a month of travelling
2. I will not be able to monitor and execute on things
3. Someone needs to take over governance in some capacity
All deliverables were completed by early February and the process was handed over and briefed to the Swingby team & community.
At this point, the first proposal was in the first phase, but unfortunately did not go onto the second phase without anyone monitoring. Community did not agree with the specifics because
Despite this, another proposal was tabled on Snapshot jumping from the first to third phase immediately. This proposal actually passed, making it look like we shortcut our own process.
## Implications
This looks bad on 2 fronts:
1. Lack of momentum on the first proposal: Unfortunately, it makes the governance effort looks insincere.
2. Second proposal jumping to the third phase immediately: This makes it worse as we have went against our own process that we set up.
## How we can salvage it
I think that my question to the team is that - is this a soft-rug? Or do you want to continue doing things with the community? If it is the latter, the community goodwill is something that's required to continue this project. Someone needs to own this then.
I think it's alright to not like the process - you can change it, make it easier/better/faster/clearer. But somehow has to own it, if this project wants to move forward.
As my last suggestion out of pure goodwill, I will suggest we do this:
1. I can work on the cleanup, but I need someone to own this process moving forward.
2. 0xTester will say that:
- He has fallen sick due to Covid & hence the lack of response
- Proposal D-01 will be moving forward to Phase 2 Discord Temperature Check
- The Snapshot proposal will not be considered at all because it is a rogue proposal that has not followed the governance process
- <Someone> will be also overseeing governance to have more decentralization and less dependency
I will do the above out of pure goodwill, but after that, everything governance should be undertaken by someone on the Swingby team
## Messaging
Hi there Swingby community, 0xtester here - sincere apologies for the radio silence over the last couple of weeks wrt governance. I was down with Covid-19 and have been nursing myself back to health.
Picking up from where we left off, here are some updates for the community.
1. New governance lead: We take community governance very seriously and would like to avoid governance being neglected due to any mishaps (as we did over the last few weeks). As such, I'd like to introduce you to <>, who will be overseeing governance and make sure we're on task for community governance moving forward.
2. Proposal D-01: The proposal to rebalance incentives between Skybridge liquidity providers & Metanode operators have been thoroughly discussed on Discord and Github (https://github.com/SwingbyProtocol/swips/issues/11). The next step would be to hold the Discord Temperature Check for the next 48 hours. Please react and vote in this thread on Proposal D-01.
3. Proposal on Snapshot: There has been a rogue proposal that was proposed and voted on in Snapshot <link>. As this proposal did not follow the governance framework laid out in the community call, we will ignore this proposal. If any community member wishes to propose this proposal, please follow the governance framework laid out in the docs here.
---
## Discord Temp Check
After 48 hours of discussion, this is the Final Proposal for SWIP-D01: https://github.com/SwingbyProtocol/swips/issues/11. For the next 48 hours, we will be doing a temperature check. Please react with 👍 or 👎 if you are FOR or AGAINST this proposal respectively.