memoscan

0x6853…eeb0

All memos sent from and to 0x6853…eeb0.
0xab339ae6…dda6sent to0x6853f886…eeb0·#24,741,818·0xeed85c79…d58189
# Fund a ragequit contract and to burn the governance module’s mint function This proposal claims the approximately 400 ETH in sudoAMM fees accumulated by the protocol currently sitting in pair factory smart contracts, and sends them to a ragequit smart contract that lets SUDO holders exchange their tokens for a fixed ETH rate. The proposal also burns the governance’s module power to mint SUDO tokens, by transfering ownership to the burn address, in order to remove any potential governance attack risk with regards to the mint function. The fixed rate is of 0.00001563744154ETH per SUDO and was determined by dividing the circulating supply of SUDO by the total sudoAMM fees collected by the protocol, and the circulating supply of SUDO was determined by subtracting the SUDO in the governance treasury and in SudoRandom’s multisig from the total supply.    The ragequit smart contract has no time limit, and is opt-in. SUDO may be exchanged for ETH at the fixed rate as long as sufficient ETH remains in the smart contract. Once exchanged, SUDO tokens will be sitting in the ragequit contract and cannot be exchanged back.
0x75d4bdbf…346fsent to0x6853f886…eeb0·#21,369,031·0x934ab1af…aeafed
# Claim Fees to DAO, Add Delegate / Claim to allow target 1\) Claims all fees earned on v2 factory to the DAO, a prerequisite for any further proposals for spending. 2\) Adds delegate v2 (https://etherscan.io/address/0x000000f534caa75bd1a3950ab32d6bd24d2e6b76) to the v2 factory call targets 3\) Adds cult claim (https://etherscan.io/address/0x000000f534caa75bd1a3950ab32d6bd24d2e6b76) to the v2 factory call targets.
0x98e1c4e3…3c4bsent to0x6853f886…eeb0·#16,842,114·0x7d97ad49…5fff6d
# Wonderland’s Proposal for Sudoswap Shared Pooling I'm posting this on behalf of the Wonderland team. The entire proposal can be viewed here (https://defi-wonderland.notion.site/Sudoswap-Wonderland-s-Proposal-for-Sudoswap-Shared-Pooling-5b633b7830f44d0faebfe3b8cb1f4e27). # Introduction We at Wonderland are big supporters of Sudoswap and believe it can become a crucial pillar of DeFi. We plan to contribute to ensuring its success and are thrilled to be introducing the concept of shared pooling to Sudoswap. Shared pooling will allow users to provide liquidity into already existing pools. This should solve many existing pain points, allowing Sudoswap users to dramatically simplify the pool setup process and be free of activity tinkering to achieve the best returns. Shared pooling will also solve major liquidity fragmentation issues and will unlock pool tokenization, which will be helpful in composability, NFT fractionalization, and on-chain NFT pricing oracles. Our shared pooling innovation should lead to more liquidity being provided to Sudoswap as barriers to entry will be dramatically reduced. Users will be able to target the best-performing pools and the highest returns at reduced costs while their liquidity is actively managed for them. # Who is Wonderland? We are a team of top Web3 researchers, developers, and operators who believe that the future must be open-source, permissionless, and decentralized. We partner with some of the most successful and promising protocols in Web3 – including Yearn, Connext, and Keep3r Network – to find solutions to complex engineering challenges and help them reach their full potential. We focus on building deep, mutually beneficial partnerships with protocols. We do not clock out to simply “get the job done”. We are an extension of our partners’ teams, delivering unparalleled guidance and support over the long-term, and standing by partners as they navigate the exciting (and sometimes challenging) world of Web3 and decentralized finance. The experienced Wonderland team has seen it all – the good and the bad – and believes being in it together is the way forward in Web3. ## What is Shared pooling? When discussing AMMs, people often envision pools of money where multiple users can provide liquidity. Sudoswap is the most popular NFT AMM, but currently, it only supports single-user pools. In the NFT context, shared pooling allows users to participate in an NFT-ETH pool together. When NFTs are deposited, users no longer own the NFT itself but instead possess a position represented by an LP token. **But why do we care so much about shared pooling?** Shared pooling is not only a powerful solution to reduce liquidity fragmentation, but also unlocks other benefits that will take NFTs and DeFi to the next level. For instance, shared pooling enables the ability to **tokenize pools**, allowing users to invest in an entire collection or gain exposure to multiple NFTs with a single LP token. Additionally, **fractionalization** of NFTs would be possible, enabling investors to gain exposure to the price of an NFT without paying the whole amount. Shared pooling could also enable the creation of an on-chain NFT pricing oracle that could be used for lending, derivatives markets, and other DeFi applications. **Which NFTs can be shared pooled?** When considering shared pooling for NFTs, it is essential to remember that it only makes sense for NFTs with similar pricing. This is because all NFTs in the pool are offered at the same selling price, and the pool can only buy any NFT at that same price. Although using an off-chain rarity oracle to determine the price is possible, a trustless and permissionless shared pool would only work for price floor NFTs. By voting "FOR" this proposal, the DAO agrees to set aside 200,000 SUDO via LlamaPay to be distributed to Wonderland upon completion of the task. The tokens will be vested linearly over the course of four months. By voting "AGAINST," you do not support this proposal.
0x8f031ee2…024dsent to0x6853f886…eeb0·#16,829,588·0x7895ac9e…fadc1b
# Allow pairs (LP pools) to call eternal proxy (EPS) This proposal allows the pairs to call the eternal proxy ESAPI. If passed, this would allow LPs to use EPS to designate a delegate address. This is useful for cases like Webaverse where the LP address was whitelisted. LPs would be able to designate an address to mint the NFTs.
0x8f031ee2…024dsent to0x6853f886…eeb0·#16,828,327·0x060b5c17…633f86
# Allow pairs (LP pools) to call eternal proxy (EPS) This proposal allows the pairs to call the eternal proxy [ESAPI](https://www.eternalproxy.com/setting-up-a-proxy/). If passed, this would allow LPs to use EPS to designate a delegate address. This is useful for cases like [Webaverse](https://twitter.com/webaverse/status/1633143502388228096?s=20) where the LP address was whitelisted. LPs would be able to designate an address to mint the NFTs.
0x98e1c4e3…3c4bsent to0x6853f886…eeb0·#16,673,524·0x638c140a…d2b726
# Burn Unclaimed SUDO From Lockdrop & Airdrop Make sure to delegate your SUDO to yourself or someone **BEFORE** voting starts (at https://www.tally.xyz/gov/sudoswap) since your voting power will not count if not done in time. As we approach the end of the lockdrop, there are a few things the DAO needs to discuss. According to the blog posted by the team on September 1 (https://blog.sudoswap.xyz/sudo-distribution.html), “The SUDO that is not distributed during the lockdrop will go back to the treasury.” At the time of writing, roughly 80% of XMON has been locked for SUDO (https://etherscan.io/address/0xada31f59e70ad18665380f21ce49d4c43f9865c2). I am proposing to burn the unclaimed SUDO from the lockdrop and airdrop. This will lower the circulating and total supply depending on final lockdrop participation rates. The amount of SUDO in the treasury, if this proposal passes, will not deviate from the original intended distribution (https://blog.sudoswap.xyz/sudo-distribution.html). This is more of a “temperature check” vote as any execution, if necessary, will need to be determined after the lockdrop ends on 3/1 and airdrop claim ends around 5/1. By voting “For” on this proposal, you support burning the unclaimed SUDO from the lockdrop and airdrop. By voting “Against,” you do not support this proposal.
0x98e1c4e3…3c4bsent to0x6853f886…eeb0·#16,622,992·0x73a9adfc…429aa0
# Make $SUDO Transferable The first proposal did not pass as we did not hit quorum. Make sure to delegate your SUDO to yourself or someone **BEFORE** voting starts (at https://www.tally.xyz/gov/sudoswap) since your voting power will not count. The past vote was rejected, mainly due to concerns around SUDO/ETH liquidity. As mentioned by recizk.eth: “I have some doubts about using the treasury as buy side in the LP. If the people that got the airdrop dump into it we would buy back a token we gave out for free. In general, for DAOs it’s better to spend token equity (that they have a lot and can print more if needed) than hard money (ETH in treasury).” Therefore, I believe that it’s better to establish POL after price stabilizes. If we establish POL at launch, the DAO risks providing exit liquidity for large holders & airdroppers. Incentivizing LPs will externalize this risk. There will also be natural demand to LP on UniV3 for SUDO given it’s likely to attract volume. We all know Sudoswap is an amazing product that just needs more eyeballs, education, and incentivization. Once there is more interest around the protocol, we should expect more NFT volume data, which we can then use to determine what type of NFT liquidity we should incentivize in the coming months. Given the above points, I propose a 3 month liquidity mining program for a UNIv2 SUDO-ETH LP. Targeting 30% APR at $5M TVL, we’d need to emit $375,000 worth of $SUDO over 3 months. If we estimate a price of $2 per SUDO, that is 187,500 SUDO tokens to be distributed to LPs over the 3 month period (1.25% of treasury). $LOOKS has ~$7M liquidity on Uniswap, so targeting $5M seems reasonable. The DAO can then agree on a longer-term solution for POL. By voting “For” on this proposal, SUDO holders are voting to make $SUDO transferable and support a 3 month liquidity mining program for UniV2. By voting “Against,” you do not support this proposal.
0x98e1c4e3…3c4bsent to0x6853f886…eeb0·#16,536,403·0x040785db…4122ad
# Make $SUDO Transferable Will keep this short and sweet - the goal of this proposal is to make $SUDO transferable. Proposals around incentivizing liquidity for $SUDO can come at a later date. First priority is to release $SUDO into circulation as that is table stakes. As per the $SUDO announcement blog (https://blog.sudoswap.xyz/sudo-distribution.html): “SUDO will initially be non-transferable. A governance proposal to initiate transferability may be put forward through the standard governance process for the sudoAMM protocol, which will be addressed at a later time. This is done as a measure to ensure SUDO does not go into circulation unless and until there can be assurance that there will be sufficient participation from SUDO holders in governance.” By voting “For” on this proposal, tokenholders are voting to make $SUDO transferable. By voting “Against,” you do not want your $SUDO tokens to be transferable.
0x98e1c4e3…3c4bsent to0x6853f886…eeb0·#16,528,557·0x1311f5c5…b063e9
# Make $SUDO Transferrable Will keep this short and sweet - the goal of this proposal is to make $SUDO transferable. Proposals around incentivizing liquidity for $SUDO can come at a later date. First priority is to release $SUDO into circulation as that is table stakes. **As per the $SUDO announcement blog (https://blog.sudoswap.xyz/sudo-distribution.html): ** “SUDO will initially be non-transferable. A governance proposal to initiate transferability may be put forward through the standard governance process for the sudoAMM protocol, which will be addressed at a later time. This is done as a measure to ensure SUDO does not go into circulation unless and until there can be assurance that there will be sufficient participation from SUDO holders in governance.” By voting “yes” on this proposal, tokenholders are voting to make $SUDO transferable. By voting “no,” you do not want your $SUDO tokens to be transferable.