An on-chain proposal vote for Shutter DAO 0x36 has been created at Fractal by a community member nhan.eth.
#0 Make treasury contract ERC 721/ERC 1155 compatible
https://app.fractalframework.xyz/daos/0x36bD3044ab68f600f6d3e081056F34f2a58432c4/proposals/0
Start Date: Jan 22, 2024, 11:35 AM CET [See your local time at Fractal]
End Date: Jan 25, 2024, 12:05 PM CET [See your local time at Fractal]
See details at Fractal:
It seems that there is a bug in the Fractal frontend that you can also vote even if you have 0 voting power for this proposal.
Please note that you have only voting power if you have delegated your tokens before the proposal was created today at 9:35 am UTC.
All individuals who delegated after that time will have the voting power enabled for the next votes in the future.
The 3% Quorum, is that currently calculated as 3% of the 1,000,000,000?
If so, do we know that we have that many tokens delegated before the proposal’s block?
More than that has been claimed, hopefully also delegated.
The site on the link isn’t working for me anymore. Anyone else experiencing problems loading the site?
The first on-chain proposal for Shutter DAO 0x36 has been approved after passing the voting process.
The proposal met the necessary 3% quorum and received 100% support in the Yes votes.
As a result, the proposal can now be executed on-chain by anyone.
You can find further details about the proposal and the Execute Transaction button at Fractal.
The proposal has been executed.
Details can be found at https://app.safe.global/settings/modules?safe=eth:0x36bD3044ab68f600f6d3e081056F34f2a58432c4.
Confirmed. I was able to send shutterdao.eth to the treasury address successfully.
tx hash: 0xf55f604202ba3e2ffa76509b78ed4c13965f008d27ce9749c30acecf8334d680
Now proceeding to send:
shutter0x36.eth (*edit - completed @ Tx 0x1488f6d17eb44a268f16fd79fd40d8ad943e3d4fd886e2bd2febc3efa3949366)
shutterDAO0x36.eth ( *edit - completed @ Tx 0xce9fadeadc73ee7349d8ad4ddcafdaa7a777ea0ce534cecce62870ebfb2e58d3)
The Treasury now owns and controls all three of these names. Future edits can be performed through executable proposals.
Thanks Spence! How about using shutterdao.eth? Or is it reserved for something non-treasury related?
Certainly a possibility. Perhaps it’s something that could be voted on.
Any number of names can point to the treasury for what’s called “forward resolution”. So all three of those names could resolve to the treasury’s address, and all three do currently. (Meaning you type the name into etherscan or a wallet and it resolves to the treasury’s address.)
However, there is a 1 to 1 relationship with what’s called “reverse resolution”. The name that reverse resolves from the address is called the primary name. A wallet hash can only have one primary name.
That means when typing the treasury’s address (hash) into etherscan for instance, you’ll see the single chosen name, the primary name. This is also the name that’s shown when that wallet hash connects via wallet connect or similar.
There currently isn’t a primary name set for the treasury’s address. The primary name can mostly only be set by the wallet hash itself, so it will require an executable from the treasury.
TL;DR - none of those three names is the “primary name” for the treasury, and once one is selected an executable will be needed to perform the transaction.
Some details around setting the primary name for contracts are here in the ENS Docs.
https://support.ens.domains/en/articles/7902626-set-primary-name-for-contract
(*edit for additional clarity - I personally don’t have any control over any part of any of those three names anymore. They are all 100% owned and controlled by the treasury address. They look different in that screenshot because one is an ERC-1155 and two are the older ENS style ERC-721. Functionality is mostly the same for our purposes)
