[1IP-10] 1inch DAO SAFE Airdrop Claim

2.0 1inch DAO
1
  • (Yes) In favor of this proposal.
  • (No) Against this proposal.

0 voters

Simple Summary

The purpose of this proposal is to create the transaction needed to claim the SAFE airdrop that has been allocated to the 1inch DAO Treasury as well as delegate this voting power to StableNode.

Abstract

Gnosis Safe DAO is airdropping SAFE tokens to historical users of the platform. The 1inch DAO Treasury Gnosis Safe is eligible for an airdrop of 10,128.65 SAFE (5,103.86 of which is immediately available, and 5,034.79 vests over the next 4 years). If passed, this proposal will execute the on-chain claim transaction and delegate this voting power.

Motivation

There are no financial costs associated with claiming the SAFE airdrop other than the small amount of required gas. There is no reason not to claim the tokens, and doing so will add additional assets to the 1inch DAO Treausury.

This proposal also allows for the 1inch DAO’s interests to be represented in SafeDAO via vote delegation.

Specification

Delegate Address: Stablelab.eth – 0xea172676E4105e92Cc52DBf45fD93b274eC96676

Safesnap Transaction Data 
[
	{
		"to": "0x469788fE6E9E9681C6ebF3bF78e7Fd26Fc015446",
		"operation": "0",
		"value": "0.0",
		"data": "0xbd86e508736166652e657468000000000000000000000000000000000000000000000000000000000000000000000000ea172676e4105e92cc52dbf45fd93b274ec96676"
	},
	{
		"to": "0xA0b937D5c8E32a80E3a8ed4227CD020221544ee6",
		"operation": "0",
		"value": "0.0",
		"data": "0xbf6213e4000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000005bacaa2000000000000000000000000000000000000000000000022513418138e440000000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000010e358ae256a8fefd36e9ea5c48c369f6ada89aab98d9a7692313e9247bb83d30ddecf3ea81c773522a38338c9bc56f21752504e403b97b00a846c8b74ccb49095a681610ddbc4326d6a0883e680a5e575decb20dbc04dba79d0566d4c61792652834ef7366c9bf27b485842a651ae1c71f145f3fe74f1ea02aeb820663104b32139cf5231a6701804386f97d122712147638764a90f876e3fdfeb45fb344566c74c1c73600eed0dd3c3322898d790a2548480212593e5c5a6fc7f532d6f3a661854e6b4dd55e41545752eb8222ee96d8a67d9e24982cc8dc60f3f84d60151c498fc1d9cd25b7080ca24b66d64f6f3ceaa2442a69e2cff6cf17c7cf45cd02fed378e40073295ba99431257f051cb6822b21b6e5b8ecb19b45aaa55235e6ff5f58a1b155cc48a3f983883777daaecca51e89b90443bc3390494b68fbecae3928f1462f72c711f41ce5faf101ddc3a938d581cdc746950cb7c93762f5cf4a3d88efca0870e463abf45cb18f85a835919099f45c6c56581232b3be9c06448420b35c94f4f3628f31b808b09ced67b073ab97919ba14e9389e154be4fe2b10fcdd327302fdc9a0b8cea5373715d2fce8d9ddd244f4259aafb0a21305edfdda956dd84359d69bacd790ff82f7310dd382bf3f53e885e74f5dad9b3aeb7fe96ce926ff47f8e2791b9d07b3e620189a36bf17e30c874e66b205c79492a16cd5a9c5bb65b7"
	},
	{
		"to": "0xA0b937D5c8E32a80E3a8ed4227CD020221544ee6",
		"operation": "0",
		"value": "0.0",
		"data": "0x0087b83fcdcd74dcca41c772a2d1bfb8ba75e9c5f44ee4ca1f062385a31b0db14ab55ceb0000000000000000000000007951c7ef839e26f63da87a42c9a87986507f1c0700000000000000000000000000000000ffffffffffffffffffffffffffffffff"
	}
]

Rationale

As part of the stage-2 governance launch, the powers of the 1inch DAO treasury multisig owners are limited to emergency cases only. In order for the 1inch DAO Treasury to make any transaction, a vote needs to occur.

SafeSnap will be used to execute this off-chain SnapShot vote in a trust-minimized fashion. A full description of this process can be seen in the governance documentation: Gnosis Safe + Snapshot + SafeSnap.

Delegation

During the phase-1 discussion, StableNode and DAOplomats agreed that the team with the least amount of SAFE delegation on Monday October, 10th should be set as the delegate. There were no objections to this suggestion.

StableNode currently has 0 SAFE delegated to their address, so they have been selected as delegate.

Considerations

There are no costs associated with this proposal. If passed, the proposal will add 10,128.65 SAFE to the 1inch DAO Treasury.

This proposal does not call for spending these SAFE tokens, only the claiming of them and the delegation of the voting power. Any use of these funds will require an additional proposal.

6 Likes
2

I added in the Safesnap transaction data that @Belac developed. Here is his explanation of each step:

STEPS:

  1. Create a transaction to reality.eth module, this adds the proposal id and transaction hash so it can be executed later
    to: 0xa62D2a75eb39C12e908e9F6BF50f189641692F2E
    data: 0x8dcd2661000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000c00000000000000000000000000000000000000000000000000000000000000042307839663435343438386562653332326138653934663534356634613438626362643331313538323931656630343833336563643237636137363533613732373266000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000134b51e4b654ddb9016adfaca1282f3a734dd8d40a241577fe0dac080071a299c
    THE QUESTION ID SHOULD BE 0x474bc2884aad71a3c1fbc2b2624dbc8b09ae786b7a37f80a7c1f8d4cb6374180
  2. next, submit the answer on reality.eths webiste
    PASSING:
    to: 0x5b7dD1E86623548AF054A4985F7fc8Ccbb554E2c
    data: 0x77f325df474bc2884aad71a3c1fbc2b2624dbc8b09ae786b7a37f80a7c1f8d4cb637418000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000000
    value: 100000000000000000 wei (0.1 ETH)
    FAILING
    to: 0x5b7dD1E86623548AF054A4985F7fc8Ccbb554E2c
    data: 0x77f325df474bc2884aad71a3c1fbc2b2624dbc8b09ae786b7a37f80a7c1f8d4cb637418000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    value: 100000000000000000 wei (0.1 ETH)
  3. next, execute the proposal if PASSING !! warning, must wait a whole week for it to finalize !!
    to: 0xa62D2a75eb39C12e908e9F6BF50f189641692F2E
    data: 0x2351a87700000000000000000000000000000000000000000000000000000000000000c000000000000000000000000000000000000000000000000000000000000001400000000000000000000000008d29be29923b68abfdd21e541b9374737b49cdad0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000018000000000000000000000000000000000000000000000000000000000000000010000000000000000000000000000000000000000000000000000000000000042307839663435343438386562653332326138653934663534356634613438626362643331313538323931656630343833336563643237636137363533613732373266000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000134b51e4b654ddb9016adfaca1282f3a734dd8d40a241577fe0dac080071a299c00000000000000000000000000000000000000000000000000000000000004c48d80ff0a0000000000000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000046b00469788fe6e9e9681c6ebf3bf78e7fd26fc01544600000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000044bd86e508736166652e657468000000000000000000000000000000000000000000000000000000000000000000000000ea172676e4105e92cc52dbf45fd93b274ec9667600a0b937d5c8e32a80e3a8ed4227cd020221544ee6000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002c4bf6213e4000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001a0000000000000000000000000000000000000000000000000000000005bacaa2000000000000000000000000000000000000000000000022513418138e440000000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000010e358ae256a8fefd36e9ea5c48c369f6ada89aab98d9a7692313e9247bb83d30ddecf3ea81c773522a38338c9bc56f21752504e403b97b00a846c8b74ccb49095a681610ddbc4326d6a0883e680a5e575decb20dbc04dba79d0566d4c61792652834ef7366c9bf27b485842a651ae1c71f145f3fe74f1ea02aeb820663104b32139cf5231a6701804386f97d122712147638764a90f876e3fdfeb45fb344566c74c1c73600eed0dd3c3322898d790a2548480212593e5c5a6fc7f532d6f3a661854e6b4dd55e41545752eb8222ee96d8a67d9e24982cc8dc60f3f84d60151c498fc1d9cd25b7080ca24b66d64f6f3ceaa2442a69e2cff6cf17c7cf45cd02fed378e40073295ba99431257f051cb6822b21b6e5b8ecb19b45aaa55235e6ff5f58a1b155cc48a3f983883777daaecca51e89b90443bc3390494b68fbecae3928f1462f72c711f41ce5faf101ddc3a938d581cdc746950cb7c93762f5cf4a3d88efca0870e463abf45cb18f85a835919099f45c6c56581232b3be9c06448420b35c94f4f3628f31b808b09ced67b073ab97919ba14e9389e154be4fe2b10fcdd327302fdc9a0b8cea5373715d2fce8d9ddd244f4259aafb0a21305edfdda956dd84359d69bacd790ff82f7310dd382bf3f53e885e74f5dad9b3aeb7fe96ce926ff47f8e2791b9d07b3e620189a36bf17e30c874e66b205c79492a16cd5a9c5bb65b700a0b937d5c8e32a80e3a8ed4227cd020221544ee6000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000640087b83fcdcd74dcca41c772a2d1bfb8ba75e9c5f44ee4ca1f062385a31b0db14ab55ceb0000000000000000000000007951c7ef839e26f63da87a42c9a87986507f1c0700000000000000000000000000000000ffffffffffffffffffffffffffffffff00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    timestamp: 1666709851
2 Likes
3

Seeing as there were no additional comments, the phase-3 temperature check vote is now live and will close in 5 days.

1 Like
4

Temperature-check vote was a success.

1IP-10 Phase-4 snapshot vote has been created and voting will open up within the hour!

Please hop over there and give this proposal a vote!

This is the first time we’re using SafeSnap to execute the vote, so let’s see how our trust-minimized governance infrastructure performs!

1 Like
5

Unfortunately this proposal failed to meet the 10M vote quorum by a few hundred thousand votes (9.6M voted in favor).

There were some issues we experienced with the voting process – one of the Snapshot plugins we were using, Shutter, initially made it impossible for some wallets to vote. Also, since that plugin was enabled, Snapshot obfuscated the total vote tally so users could not see what % of the quorum we had reached until the vote concluded.

The proposal has no financial drawbacks and seems totally uncontroversial. I suggest we re-run the 1IP-10 vote with that Shutter plugin turned-off (unless there are any objections to this).

On that note, we are having consistent trouble in reaching the quorum. I am making a push to encourage large v1INCH and st1INCH holders to delegate voting power to the recognized delegates so that we can overcome these quorum woes.

2 Likes
6

I don’t think this is a great idea to rerun the same proposal as it has failed. From my understanding and following the discussions on the Snapshot discord, the Bugs were fixed before the vote ended. I’m not sure who is responsible if some of the delegates of @DAOplomats.eth decide to vote alone instead of delegating them to DAOplomats. They have claimed to have 3 M voting power, but after the poll ended, many token holders didn’t trust DAOplomats’ ability to vote!

IMO if someone is interested in claiming the SAFE tokens, they have to follow the already established governance process. since DAO doesn’t want to delegate to stable nodes, why not try the other group or go with the safe Guardians in a new proposal?

7

From my understanding and following the discussions on the Snapshot discord, the Bugs were fixed before the vote ended.

The bug that prevented smart contract wallets from voting was fixed before the vote ended, however, it was still extremely difficult to get a gauge of how the vote was doing in terms of quorum.

For some context: about 12 hours before the vote ended I downloaded the vote history CSV from Snapshot and it looked as though the proposal had 12M+ votes. It turns out that CSV was logging the vote from DAOplomats as well as the votes from individuals who had delegated to DAOplomats. The only way for an observer to figure out that the vote had not actually hit the quorum was to run a Graph query to see what addresses had delegated to DAOplomats and cross-reference it against the list of addresses that had already voted in this proposal – this would show that some of the delegators voted “Yes” themselves and that their voting power would be subsequently subtracted from DAOplomats for this vote.

No one I talked to knew that this was the case during the vote, it was only after the vote concluded that we realized the quorum wasn’t hit.

They have claimed to have 3 M voting power, but after the poll ended, many token holders didn’t trust DAOplomats’ ability to vote!

Delegators still voting doesn’t necessarily have anything to do with trust. People could have the intention to vote in most proposals but still delegate to ensure that their voting power is still represented if they ever miss a vote. Snapshot delegation was designed with this in mind and allows for this.

IMO if someone is interested in claiming the SAFE tokens, they have to follow the already established governance process. since DAO doesn’t want to delegate to stable nodes, why not try the other group or go with the safe Guardians in a new proposal?

Regarding your first point: I don’t see why anyone in the DAO would not want to claim the SAFE airdrop. It is a piece of another protocol that we are being gifted, there seems to be no drawbacks. Can you point me to some arguments being made by members who do not want the DAO to claim the SAFE drop?

In response to your second point: I don’t think this has anything to do with the DAO not wanting to delegate the SAFE drop to StableNode as I didn’t see a single comment/message that took issue with that. I think it stems from a bigger problem of the quorum being extremely difficult to hit in these votes. I personally believe that we should lower the quorum but that in and of itself would require a vote so it’s sort of a catch-22.

8

Hi @RoundElephant

I think it would be great to vote again because of mentioned reasons and this seems to be nobrainer to me.

This maybe needs it’s own topic, but can we do something about the voting process?
I think it is too hard to do. Mainly because off it was hard to find where the actual voting happens, had to go thru pile of documents. Maybe this is very clear for more experienced users, but for new ones just pain in the a@@ when trying to do it first time. So can we simplify it, by adding link to voting page into header? I think by doing this it will generate greater voting activity → easier to pass quorum.

1 Like
9

All great ideas! I think there are a lot of things that can be bettered with the voting process:

  • Lower the quorum
  • Shortening to proposal lifecycle (5-day temp-check + 7-day vote is prohibitively long imo)

I’ll start a new thread where we can mull over those ideas.

1 Like
10

I’ve re-created the Snapshot proposal. Full justification can be seen in this thread but the TL;DR is the first vote experienced some bugs that complicated the voting process.

Since the SAFE airdrop claim deadline is December 27th, and the Snapshot + Safesnap process takes at least 13 days, we needed to act today or risk leaving all of those SAFE tokens on the table.

Please take the time to vote! [1IP-10] 1inch DAO SAFE Airdrop Claim (re-vote)

1 Like
11

Is it really so that I can’t vote because my tokens are in Binance Smart Chain?

12

This is bullshit you keep not including people holding tokens based on geographic location. im selling every 1inch token i have you guys are a walled dumpster fire. if you hate united states citizens because they have 0 control over their shitty government then you are that government! spineless jellyfish

13

1INCH tokens need to be staked to vote, and that is only supported on Ethereum mainnet (full breakdown).

Since the DAO treasury is on Ethereum mainnet, it reduces the security risks if all governance functions take place on Ethereum mainnet.

Hopefully the staking pods 1IP passes and we’ll have a direct incentive to stake again.

14

I have staked my 1INCH tokens on BSC and I have st1INCH tokens (staked in app.1inch.io), So I thought if I can vote on Aggregation protocol governance & Liquidity protocol governance then I can also actually take part of proposals too… this is sad, but hopefully this changes over time. :slight_smile:

To be honest you don’t lose much because I have only small bag :smiley: But I will come back if this changes.

15

The 1inch smart contracts are immutable and permissionless. The 1inch API is permissionless. To my knowledge, the only parts of the 1inch stack that are geo-restricted are the parts that are owned and controlled by the 1inch Foundation, namely, the front-end.

The full terms of service for the 1inch interface, hosted by the 1inch Foundation, can be seen here.

16

I have been holding over 250 1inch tokens for almost a year and i cant vote on any snapshot because it says i have no voting power. Can you explain to a simp why that would be? If you have the time my address is rockcocaine.eth

Also why does geographic location matter this is the internet its free and open or at-least that’s how it has been sold to me and everyone i know. can you also tell me who owns the internet?

17

Only 1INCH staked on Ethereum mainnet can vote. For a full breakdown see the governance documentation.

18

Thanks for the reply however when i try to stake i get this:

Screenshot 2022-12-17 at 4.24.13 PM
Screenshot 2022-12-17 at 4.24.13 PM1672Ă—1214 69.1 KB

should i use a vpn and violate laws THAT DO NOT EXIST in order to use my tokens on the free and open internet? or do i get around it by creating my own ui to interact directly with the contract thereby severely limiting 1inch platforms audience which is not so good for the ecosystem?

For a full breakdown please see this: 1INCH BONES UNITED STATES CITIZENS TOO

19

Thanks for sharing this.