Add public key to manifest to get consistent extension ID

[lukaw3d]

No description provided.

[pro-wh]

oh so that's how you do it

[pro-wh]

oh cool

https://developer.chrome.com/docs/extensions/mv3/manifest/key/

[lukaw3d]

This results in the same ID. If it was different for development, it won't be as easy to test with any dapps.

Are you worried about security?

[pro-wh]

yeah, the security of experimental code having access to the same storage as the real one. actually is that the case? they'll be on the same origin, so I'd guess that they'll have access to the same storage. or does chrome enforce that you fully wipe one before you can install the other?

[lukaw3d]

Just tried:

• if you install Chrome web store first, then you can load development version without removing, and storage is kept
• if you go from development to Chrome web store, then that only shows "Remove" button

[pro-wh]

aw darn that's like the opposite of what I wanted 😆

how about this:

1. we enter a key to get a fixed dev ID here, separate from what the published extension uses
2. we put this public key from the published extension in the documentation
3. dapps should support other wallets anyway 🤞

[lukaw3d]

Is this worth generating different manifest.json with javascript based on env 😖

[pro-wh]

imo no. I'd rather edit a file than set an env var

[lukaw3d]

I mean env just as the difference between dev and build

[pro-wh]

probably not that either, if it were up to me. if someone needed to experiment with new changes and to interact with dapps, they'd perhaps use the real public key in a dev env. or if we need to share around a production build but not clobber the data from people's installation of the published version, we'd do it the other way around.

[pro-wh]

actually what extension ID does this key result in? I feel like we should use a different ID for development

need to ask follow up question