Skunkworks Project Suggestion: Integrate a secondary wallet into the dashboard to prepare for upcoming events.

[krisstege]

Name of the project

Users should have the option to connect a secondary wallet in the Scroll dashboard for future use.

Project abstract

We all anticipate that every Layer 2 (L2) solution will eventually have its own coin, but it's essential to remember that the token is not the sole factor determining success. However, it does play a significant role in attracting both the project and the community.

A supportive community is paramount for the success of any project, and achieving that is undoubtedly a win.

Considering the community aspect, in the Web3 world, having your wallet hacked is possibly the most disheartening experience one can imagine. All the hard work and funds stored in that wallet are at risk of being lost.

Moreover, any interactions associated with that wallet would also disappear. If someone were to reward the compromised wallet, it would feel like salt in the wound.

So, what Scroll can do is consider implementing a feature for any future community airdrops. This feature would allow users to connect a different wallet that has not been hacked and disconnect the compromised wallet to receive rewards in the future, if such an opportunity arises.

Specification

Recently, I've noticed more projects implementing a feature where users can connect another wallet and disconnect a compromised one to claim rewards, with $JUP and $PIXEL being the latest examples.

This move shows that these projects truly consider their community's needs, offering hope and fostering trust among users.

While not impossible, this change has the potential to create a significant positive impact on the community.