Skip to content
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

Document ppf deployment on rinkeby and mainnet #55

Closed
sohkai opened this issue Mar 13, 2019 · 4 comments · Fixed by #76
Closed

Document ppf deployment on rinkeby and mainnet #55

sohkai opened this issue Mar 13, 2019 · 4 comments · Fixed by #76
Assignees

Comments

@sohkai
Copy link
Contributor

sohkai commented Mar 13, 2019

No description provided.

@sohkai sohkai mentioned this issue Mar 13, 2019
21 tasks
@izqui
Copy link
Contributor

izqui commented Mar 25, 2019

Will redeploy it with a newer compiler version to both networks. Thinking about whether it would make sense to deploy it to APM as well so we have an immutable reference to the default PPF.

@sohkai
Copy link
Contributor Author

sohkai commented Mar 25, 2019

Maybe if we meant to use proxies on top of it (which may make sense), otherwise the "default" one would be A1's?

@izqui
Copy link
Contributor

izqui commented Mar 25, 2019

I was thinking ppf-factory.aragonpm.eth for factory and then ppf-a1.aragonpm.eth (it would be even better if we got an a1.aragonpm.eth registry for us actually!)

@sohkai
Copy link
Contributor Author

sohkai commented Mar 26, 2019

I like both of those (ppf-factory.aragonpm.eth and a1.aragonpm.eth) ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants