Hi , may i upload this SEP to snapshot or need Daniel only ?
Let’s hold each other accountable to ensure that the dates proposed are met. This should be uploaded to snapshot as promised on Wednesday, Nov 2nd. If there are continued delays from the minority that have the ability to bring this to a vote, that is concerning. Regardless of the motivation, it has already made the majority DAO participants below the proposal threshold feel that their participation does not have any consequence. If a minority has the exclusive ability to pick the candidates, then the outcome of the election will always favor the interests of that minority. See “Tweedism” in American politics.
To be clear, the governance process says it can be uploaded from today — not that it must necessarily be uploaded today. Although you’re right of course that it’s expected to happen anytime now. Is anyone already on it?
Anyone with at least 20k SAFE in their wallet can upload the proposal to Snapshot. This is not limited to the proposal author, @Daniel, but asking if he’s already on it would make sense of course. In principle, you can certainly upload it!
Why team will not upload it
I’m not home at the moment, but if no one else posts it to Snapshot, I will do it personally in a few hours.
So please don’t mind me, if you want you can post it directly to Snapshot. That would actually be convenient for me, but I can do it later of course.
For various reasons, mainly because SafeDAO should empower all stakeholders of its DAO, not just the team behind Safe. Since the team has been working on Safe as a product for many years already, the team has an unfair advantage in terms of know-how on the product and its ecosystem, if you will. SafeDAO’s governance process puts a counter-weight to that and prioritises decentralised governance from the start.
Also, @Daniel as the proposal author has a say (and did just comment as I’m writing this ).
Okay, seems to me like the team are not interested in this proposal!
Because they want to make the proposal more like a community decision, I guess they will not vote on this proposal either.
For Daniel’s convenience and for the rest of our DAO, I have decided to upload this proposal to Snapshot. I pointed out that the author of the proposal was Daniel, and only just speeded up the process.
I ask all DAO members to vote! Together - we are force !
Good Work Bruce, but you forgot to add SafeSnap, please delete it and let’s make a new one.
Also there are some typos when copied in, need to fix them.
+1 to deleting and reuploading with SafeSnap instructions.
And while we’re on it, let’s also fix the formatting and missing links. That’s easiest done by the proposal author who can edit the proposal, copy the formatting (as below) and – crucially – not change and save anything.
* **Title:** Community Initiative To Unpause Token Contract (Enabling Transferability) * **Author:** [Daniel](https://twitter.com/danftz), Co-founder @ Decentra * **Created:** 2022-09-28 ## Abstract This is a proposal to call the unpause method of the token contract (using the SafeSnap module), which would result in the SAFE token becoming transferable. Unvested tokens would still remain in the vesting contract, and thus would not become transferable. ## Proposal details ### Purpose and Background If we go with the definition of Adam Levi, Co-founder @ DAOStack, a token needs to hold two distinct properties to be actually called a token: * A token cannot be taken away from its owner. * The owner can transfer the token to anyone else, without requesting permission. While the first point is satisfied with the current design, the same is not true for the second. Since SAFE does not have the two properties mentioned above, we cannot consider it a token (yet) per the definition of Adam Levi. I'm not sure if I completely agree with him on this definition, but I do think that those two properties are fundamentally important to a token that is intended to govern a DAO. While non-transferability has its advantages (e.g., the governance process is more resilient against malicious vote-buying at all participation rates), it also has some disadvantages: - Without transferability enabled, those who want to participate in governance, but don't have any tokens allocated to them, can't acquire tokens (=voting power), nor can they bring in proposals on Snapshot themselves, which requires at least 20K SAFE. That basically makes this DAO a static, closed organisation as of now, without any new participants being able to come in. - It limits the scope of activities to be made by SafeDAO (it won't attract contributors who want to be paid in a liquid token, no feasible way to conduct OTC trades, etc.) ### Effects and Impact Analysis Having a transferable token also makes it tradeable, this is inevitable. In an adverse market environment such as the one we're currently finding ourselves in, this might lead to a suppressed valuation compared to what it could have been a year ago. However, I'm not sure if that's actually something we should care about, as price fluctuations are simply part of how a market-based economy works. I don't think SafeDAO should structure its roadmap around how to maximize token value. The current macro environment is outside our sphere of influence, and honestly I believe that a "hockey-stick" price chart is more favorable than a down-only chart with the peak being the token launch, resulting in disillusioned market participants as we've seen in the past with tokens like DYDX, PSP and countless others. **It is beyond SafeDAO's control if and how individuals/institutions choose to price SAFE. Therefore, we should not let the adverse market environment influence our decision on whether to make this token transferable or not.** ### Alternative Solutions - We could keep the token non-transferable indefinitely, this would be a radical experiment in DAO governance. As mentioned above, the advantage here is obviously the increased resilience against malicious vote-buying. The big down side is the fact, that the ownership structure, voting power held by individuals and institutions, would remain static. I reject this on this basis that I'd rather have (new) players who genuinely want to participate in governing SafeDAO accumulate tokens and thus increasing their voting power, than maintaining the status quo indefinitely. And with a high voter turnout, there would also be sufficient resilience against malicious vote buying - even with a transferable token. - We could wait until SafeDAO has matured to enable transferability of the SAFE token. This is the alternative solution that appeals to me almost as much as the immediate unpausing of the token contract. Simply because this would give us time to think about what SafeDAO wants to accomplish and how to structure everything (there's for example the ["Outcomes-based resource allocation (‘OBRA’)"](https://forum.safe.global/t/discussion-safe-dao-resource-allocation-model-obra/1001) model proposed by @pet3rpan-1kx which could be interesting to adopt). However, despite all of this, I believe we should not wait until SafeDAO has matured (although that would not be a disaster either). We should start attracting contributors now, for which a liquid token is necessary and we should not voluntarily limit the scope of our activities, which is a result of this non-transferability. And what if SafeDAO can never mature without having a transferable, liquid token to attract contributors, etc. in the first place? I can't give a definitive answer to this, but this is a realistic scenario in my opinion that should not be overlooked. ### Technical Implementation To make the token transferable no significant additional code is required, however the owner of the token has to call the unpause method of the token contract. This can be accomplished without an intermediary or gatekeeper by ensuring that the "unpause()" function is called by the SafeSnap module. Once the token contract is unpaused (and therefore the token is transferable), it is not possible to pause the token contract again (e.g. once transferable forever transferable). (Thanks to @Arseny for his suggestion regarding the use of the SafeSnap module) Source: https://github.com/safe-global/safe-token/blob/6a1a4a99a7f3166b525cbd5469eaf0aea1c88e54/docs/token.md ## Copyright Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
I ask all DAO members to vote! Together - we are force !
Looks fine to me. Do others agree?
If it stays like that, voting will start in a bit less than 24h on Nov 3, 2022 at 12:14 PM UTC.
It looks good now for me too.
Please post this in the safegov Twitter in a few hours, thanks to all community members, we finally reach here.
Once the Snapshot proposal has been reviewed by a few more people and voting starts in about 23h, it will be announced on the Safe Governance Twitter like every other SEP, of course.
On that note, everyone: If you haven’t yet, consider following and enabling notifications there so that you’ll always be in the known about SEPs in phase 1 (forum discussion) and phase 2 (Snapshot).
It’s okay let’s see the outcome by the community
First it was only 24 hrs after the waiting period now we have to wait til tomorrow to vote, they seriously dragging it.
They act as if everything will be perfect first time around.
No , all okey , its standart
Who exactly set the standards?