Migrate wrappers published to ENS
Move wrappers from web3 ETH domain to polywrap ETH domain
@Niraj-Kamdar @cbrzn I created this document to aggregate a backlog of ENS domains that need to be migrated.
Can you please add all domains that need to be migrated to polywrap.eth on mainnet? Also LMK if you have a better idea on how we can do this tracking.
https://hackmd.io/@polywrap-dao/r1Wyt-I65
Niraj Idea
- dev release, prod release
- dev released to any test network + dev domain (/rinkeby/dev.polywrap.eth)
- prod release -> take dev domain -> set production domain hash
- create a new "CD" multi-sig
-
- give ownership of a subdomain to this multi-sig
-
- one account is the github action bot, which posts new transactions
-
- dev team has other signer keys, signs off on CD actions
This is blocked by ENS Text Record Support: https://github.com/polywrap/monorepo/issues/1113
Reasoning: When going through the migration backlog here I found myself needing to create many subdomains, which is expensive and requires a new transaction.
Instead, I want to just create a simple text record. Cheaper, faster, don't have to do multiple if the namespace is nested. For example /demos/rs/simple-storage.