Dracula Improvement Proposal (DIP) 02:

Tokenizing Staked DRC has been submitted on Snapshot. Voting will require unstaking DRC, which is an issue that this proposal addresses. NOTE: This proposal only affects single-staking DRC, and not liquidity providers.

Vote here: https://snapshot.org/#/dracula/proposal/QmRvMuZzuhjN34VoN2HTsdS5et2kgmV1uHoVVL6daXVzid

5/17: In case you missed it, DIP-02 voting is still live!

Make sure you vote here: https://snapshot.org/#/dracula/proposal/QmRvMuZzuhjN34VoN2HTsdS5et2kgmV1uHoVVL6daXVzid.

We are also working on a few more proposals to improve Dracula Protocol and will release them shortly after DIP-02 has concluded. We are still waiting to hear from RARI about the ETH vault, but are also exploring other options, such as their stablecoin vault, or using Yearn, in case the incident is not resolved soon.

We will most likely introduce this change in a DIP. We are also working on a script that will distribute DRC as an airdrop to all users of V2 to compensate for gas costs. Finally, Dracula Protocol is moving towards a less centralized organization by introducing our official DAO through a Gnosis Safe, which can be found here:

https://gnosis-safe.io/app/#/safes/0x823Bf40F0FbCeB9832fB4f51eFc9aC19570b099a/transactions.

We will release more details on the airdrop and the DAO in a later post!

Dracula Improvement Proposal (DIP) 02:

Tokenizing Staked DRC has been submitted on Snapshot. Voting will require unstaking DRC, which is an issue that this proposal addresses. NOTE: This proposal only affects single-staking DRC, and not liquidity providers.

Vote here: https://snapshot.org/#/dracula/proposal/QmRvMuZzuhjN34VoN2HTsdS5et2kgmV1uHoVVL6daXVzid

Dracula Protocol has transitioned to a DAO via Gnosis Safe. Funds are now secured via a multisig wallet and all future revenue will be directed to the DAO. Full details here:

https://draculaprotocol.medium.com/dracula-protocol-transitions-to-a-dao-c6880d6f7b65

Dracula Improvement Proposal (DIP) 03: Migrate from Uniswap to Sushi is now live!

Vote here: https://snapshot.org/#/dracula/proposal/QmRVKSFjxTEdyn9bZim6WizH7X5Biqnkwe2RdWyR6Yi58E

Also please check:

https://forum.sushi.com/t/sushinomics-introducing-osushi/4055

5/24: Developers are currently working on implementing xDRC, which is a tokenized receipt for staked DRC that will auto-compound yields. Developers are also working on the oSUSHI integration, which will continue $SUSHI rewards for the $DRC / $ETH pool. That’s all for now!

5/31: We have finished the xDRC contract to be able to include the changes proposed in DIP-02. In order to optimize the purchasing of DRC with the ETH collected from the drain, we have decided to implement ArcherDAO to help prevent frontrunning.

This integration is still underway. We have also completed the Sushi integration mentioned in DIP-03, but will have to wait until Sushi goes live with oSUSHI to actually implement it. As for the RARI Vault, we have yet to receive a timeline for when it will be active. So we have decided to integrate Yearn's ETH Vault for our compounding strategy for V2.1.

More details on this to follow, but we are a few weeks of testing away from our relaunch.

6/7: The ArcherDAO integration is nearing completion, which will help prevent frontrunning attacks when purchasing DRC off the open market. We have also been working to ensure that our contracts can manage tokenized receipts for the Yearn integration, which will generate a constant revenue stream to DRC stakers via the affiliate fee from Yearn's Partnership Program. Once we finalize our integration with Yearn, we will begin full-scale testing of V2.1 on mainnet.

6/14: Contracts for the Yearn integration, as a victim and for our compounding strategy, have been completed. Sushi integration has been completed. ArcherDAO integration is almost complete. We will begin testing on testnet shortly, which will be followed by mainnet testing. Timeline right now is unknown, but testing will most likely take a few weeks if no major errors are discovered.

6/21: Internal testing is underway by our devs, mostly focused on the drain mechanism and the new compounding strategy to make sure that everything is running smoothly. We have also been reviewing the current list of victim pools to make sure we have an updated list for our relaunch. We will be asking community members for closed beta-testing in the coming weeks, so stay tuned for that!

6/28: Internal testing is still on-going, so all beta-testers hold on tight while we wrap things up! On the other side of development, our new UI and landing page are nearing the final stages of development. This improved UI will focus on improving the user-experience for our platform, including information about Dracula Protocol and how to use it. We will be testing out our new front end during the beta-testing, but in the meantime, check out our new landing page:

https://cdn.discordapp.com/attachments/791006308169285662/859211428330209300/Screen_Shot_2021-06-28_at_7.17.08_PM.png

7/5: We have been working on our APIs in order to ensure that our APRs are as accurate as possible for our V2.1 launch. Contracts are still being tested and the UI is nearing completion. In the meantime, we would like to invite all interested users to signup for our beta testing here:

https://forms.gle/6hhYaXtunrjvGPY96

Those that sign up will get exclusive access to the platform before official launch. More details on this will follow as we get closer to launch!

7/12: Thank you to the over 150 people who have signed up for the beta test of Dracula V2.1!

We appreciate the overwhelming interest and are working to ensure a smooth launch. Our UI is finished and we are currently integrating it with the contracts for testing. Most of the beta will be focused around ensuring our frontend and contracts work seamlessly on mainnet.

We also appreciate some of the community members stepping up to help us with aspects such as copywriting and marketing. Be on the lookout for the announcement regarding beta-testing in the coming weeks.

Please vote!

https://t.me/DraculaProtocol/156627

7/19: Mainnet testing is ongoing with a few different pools, including several 2x and Kashi Sushi pools. We are waiting for rewards to accrue in the drain to complete our internal testing, which will be followed by our closed beta-launch. We hope to test out our other victims, such as Dodo and Pickle, during this phase. We will also be looking for feedback on our improved frontend, which will also be live upon V2.1 launch. Things are coming along and we expect to launch our beta within the next three weeks.

7/26: We are putting the finishing touches on our new landing page, which will be live within the next day or so! Be on the lookout for an official announcement regarding the changes we are making on our UI in anticipation for V2.1. We have been successfully testing the drain mechanism with a few community members and are going to reach out to more beta-users for testing of the Sushi contract, which will also be added in the next several days.

8/2: We have soft-launched our new landing page at dracula.sucks, but have some final copywriting and alignment with our documentation to finish before posting an announcement. We've been deploying and testing different adapters, mostly testing UI compatibility along with functionality. These tests have been going well and we hope to open up the beta-testing once we get a few more adapters hooked up and working. Be on standby beta-testers, your time is coming!

8/9: Welcome to the first day of beta-testing! We are currently looking for all users with SLP (Liquidity Providers for Sushi on mainnet) to help test! We are only allowing a select number of users, so if you are interested, please fill out this form and someone on the Dracula team will reach out to you: https://forms.gle/9qZ7k4Woy5iMbuJ77. We will most likely have several further rounds of beta-testing with different victims, but for now are only accepting Sushi LPs.

8/16: We have been successfully testing several victim contracts, including Sushi, as well as our overall drain on mainnet thanks to our beta testers! We are adding additional victim adapters and will be reaching out to more users during this upcoming week. We are also finalizing details for the 530 users who will receive a DRC airdrop. More details on that soon!

8/23: Victim adapters and drain have been running smoothly. Thanks to everyone who accepted the call to beta-test! We are now working on implementing the Yearn auto-compounding mechanism, along with claiming from the contract. Once those are implemented and properly tested, we will then be working on front-end fixes before moving into our official launch. We are starting talks with other platforms to add utility to xDRC so that we can hit the ground running once the platform is live.

8/30: Currently we are working on front-end fixes that we encountered during beta-testing and internal testing. These fixes are mostly small bugs and opportunities to improve user-experience. Once these are completed, we will be doing a final run-through of the platform before we release the app to all beta-users. V2.1 launch is nearing, stay tuned for more updates!

9/6: Our Dev team has deployed Yearn adapter and updated our front-end.

We also moving forward to deeper integration with Yearn finance. With it we will essentially get an affiliate fee for all user deposits that goes to DRC stakers!

9/13: We have finished up the integration for the Yearn contracts! If you have any Yearn tokens and are interested in helping us test, please reach out! This is the last piece of our architecture, so if all goes well we will be launching after testing concludes! We are also thrilled to announce that we are onboarding a new front-end developer to help ease the workload and increase our agility for future developments. We will have a separate post once we finalize details, but be on the lookout for a governance proposal to bring on a new dev!