-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy upgraded registration factory contracts on additional chains #128
Comments
Whether registration contracts need an updatable feature? |
The PR was created about the versioning feature. |
The design pattern I discussed with @isaac Patka ***@***.***> is that
we did not want the registration factories to be updatable. We will simply
update our own indexer, and ideally include data from previous registration
factories to the degree that it is possible, when we need to update a
factory.
…On Mon, Aug 28, 2023 at 11:44 PM Kahn ***@***.***> wrote:
The PR <#133> was created about
the versioning feature.
Waiting for a reply to the last comment before I move on to the next
steps. @thelastjosh <https://github.com/thelastjosh> @amanwithwings
<https://github.com/amanwithwings>
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHA5PFK3SMRELIAG33LF2DXXVQTBANCNFSM6AAAAAA33RXCTI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
@crazyyuan will deploy to other chains by weekend; please include verification (i.e. have a registration show up in our frontend!) |
The contracts are all deployed and verified. arbitrum goerli bnb bruno And then, we need to create TheGraph indexer for these. |
TheGraph Indexer has been deployed on the arbitrum-goerli network. TheGraph Indexer has been deployed on the chapel network PR for these: #137 The next step, @Rashmi-278 please update the frontend to support these two networks. |
The document about contracts is updated. |
It's completed with updates, PR is ready to go. Can close this @thelastjosh |
As per my knowledge the updated contracts are deployed on the following chains, MainnetsEthereum
Optimism
TestnetsEthereum-goerli
Optimism-goerli
Arbitrum-goerli
BNB-bruno
|
Do we have plans to deploy our contracts on more chains @thelastjosh @eleventh19 ? |
We had deployed an earlier version of the factory contract to these chains.
No reason not to, but I'd like to develop standard set of actions (e.g.
upgrade the frontend, perhaps the explorer + indexer) to accompany new
deployments.
…On Tue, Sep 26, 2023 at 12:21 PM Rashmi V Abbigeri ***@***.***> wrote:
Do we have plans to deploy our contracts on more chains @thelastjosh
<https://github.com/thelastjosh> @eleventh19
<https://github.com/eleventh19> ?
I think we should also do Polygon, Arbitrum, and BNB mainnets too before
we close this
—
Reply to this email directly, view it on GitHub
<#128 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACHA5PGVVCK4IYBVUQJMB5TX4L6IDANCNFSM6AAAAAA33RXCTI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Yes For sure, I agree. Does this help define the set of actions for the standard? |
These are deployed, Rashmi will deploy some test DAOs to the new chains to make sure they show up in the explorer, otherwise we're good! The big list of contracts now canonically lives at the main README.md for DAOstar. |
Just a matter of (1) adding some basic versioning to our factory contracts, (2) deploying the NEW registration factory contracts (with the new, updated indexer pattern) to chains where it is not already present, (3) tracking that appropriately in documentation, and (4) updating the frontend to reflect the newly-deployed contracts.
For example, prioritize deploying fresh ones to Arbitrum and BNB, as we are applying for grants there.
For now focus on just deploying.
The text was updated successfully, but these errors were encountered: