search

hicommonwealth / commonwealth

A platform for decentralized communities
https://commonwealth.im
GNU General Public License v3.0
67 stars 42 forks source link

🪣 Deploy Stake + Contests on 3 Chains (Phase 1 of Decoupling) #8695

Open zakhap opened 1 month ago

zakhap commented 1 month ago

Description

For simplicity's sake, we'd like to deploy Stake + Contests on 3 Alchemy supported chains, enabling our Admins for launching Stake+Contests on different chains. The below chains are ordered by impact:

Ultimately, we want to decouple Stake + Contests, however, that is out of scope for this immediate project making available these features to more communities.

Project Owner

Sachin Benny, Zak Hap @zakhap

PRD

The Larger Decoupling Project Overview is here: https://www.notion.so/buildcommon/Decoupling-dbb7fdf225654190b111210b73e60384

This Bucket is a precursor bucket ticket to all of the work described in the document.

Enable Stake + Contests on:

Design Links

No response

Design Screenshots

No response

Additional Context

No response

ianrowan commented 1 month ago

Just want to add a couple points to get the conversation going here.

Do we actually know of people who want to use these features on ETH mainnet? And if so would their use outweigh our costs? For context the contract suite could cost > $1000 to deploy and each piece of content people add would cost around $10-15 for us to sequence on chain as well as votes. ie 100 upvotes on the UI could cost $1500 alone.

And for linea, I think we've checked but will refer to @timolegros. for chain events to work the chain needs to be supported by alchemy webhooks and I believe linea is only supported at the RPC level so there may be significant work on the platform to support

timolegros commented 1 month ago

I have shared this a few times but will add here for context as well: https://github.com/hicommonwealth/commonwealth/blob/master/knowledge_base/Chain-Feature-Matrix.md. This is the current chain feature matrix. If Linea is seriously to be considered we really need to evaluate how critical it is compared to the eng effort lest we fall back to our previous model of 'supporting any chain, anytime, at any cost'. The previous model was very expensive to maintain and should be avoided.

Per @ianrowan's comment, contests on ETH mainnet seem completely unsustainable but that's outside my purview.

dillchen commented 1 month ago

Mark has added context here:

https://www.notion.so/buildcommon/Growth-Chain-Priority-Docs-a4c66f8238a546d8b5e49ecaa67b2c01?pvs=4

The other requested chains is BNB. cc: @timolegros

jnaviask commented 4 weeks ago

Backlogging until we reach a final decision.

dillchen commented 4 weeks ago

What needs final decision?

Who do you need final decision from?

Sent via Superhuman iOS @.***>

On Fri, Aug 16 2024 at 4:06 PM, Jake Naviasky @.***> wrote:

Backlogging until we reach a final decision.

— Reply to this email directly, view it on GitHub https://github.com/hicommonwealth/commonwealth/issues/8695#issuecomment-2294157709, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIWMHIEB554UEPH66IVSSTZRZLUJAVCNFSM6AAAAABLZKA7M6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUGE2TONZQHE . You are receiving this because you commented.Message ID: @.***>

ianrowan commented 3 weeks ago

To begin planning for this, wanted to provide the expected tasks here which can be ticketed upon acceptance.

  1. Security set-up for each network
    • Creation of all 7(?? @egetekiner ) multi-sigs per network. Is safe available on all networks?
    • Funding of all key holder accounts on all networks(35 addresses per network i believe)
  2. Deployment of Contracts per chain
    • Consolidated full deployment script required(ie Namespace + contests)
    • Funding of deployment key per network
    • potential key holder coordination for txs
  3. Protocol updates to CW app
    • add addresses to chainConfig for each new network
  4. Platform configurations
    • Adding alchemy webhooks/CE for each network/contracts CC @timolegros on this
  5. Final configurations
    • Any app deployment plan steps to spin this up
    • Funding and monitoring for Contest sequencer on each network

Additionally post-deployment, each chain's sequencer wallet must be monitored and remain funded to support contests

egetekiner commented 3 weeks ago

We can setup the deployments for Monday Aug 26th and we can use the same keys for the multisig creations. Only thing we need to do is to fund all of the wallets in the networks we would like to deploy.

If that's ok for everyone, I can start to create multisignature wallets and once all of them will be ready we can come together for the deployment (or only @ianrowan and I can take care of it).

dillchen commented 3 weeks ago

This sounds great to me. Please add me to the deployment call, I will also fund during that time as well

Sent via Superhuman iOS @.***>

On Fri, Aug 23 2024 at 2:51 AM, Ege Tekiner @.***> wrote:

We can setup the deployments for Monday Aug 26th and we can use the same keys for the multisig creations. Only thing we need to do is to fund all of the wallets in the networks we would like to deploy.

If that's ok for everyone, I can start to create multisignature wallets and once all of them will be ready we can come together for the deployment (or only @ianrowan https://github.com/ianrowan and I can take care of it).

— Reply to this email directly, view it on GitHub https://github.com/hicommonwealth/commonwealth/issues/8695#issuecomment-2305322239, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIWMHOYH7TLG2QA3B5ZUZDZSYQLJAVCNFSM6AAAAABLZKA7M6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBVGMZDEMRTHE . You are receiving this because you commented.Message ID: @.***>

ianrowan commented 3 weeks ago

I've added tickets to track these tasks to the task section of this bucket. Would say to be accurate the deployment portion of these tickets will start on Aug 26th but may run into the next day or two given the light dev work/testing potentially required.

The platform side tickets may be more involved but pinged team members to weigh in on effort on those.

CC @jnaviask

ianrowan commented 4 days ago

These changes/deployments are ready to go in #9108 When this commit makes it to production the new networks will automatically become active. Are we ready to do this, ie should this go in as a hotfix, the next release, or a release in the future?

CC @zakhap (+growth team) @ilijabojanovic

ianrowan commented 4 days ago

Confirmed #9108 will be added as a hotfix from team

CC @ilijabojanovic