dOrgJelli
dOrgJelli
These sounds like nice changes! Making medium the new slow makes me worry though, since slow is used for SchemeRegistrar. This would mean that a boosted proposal could potentially sneak...
Hey @Phinneas, yes it is. Sounds like a plan! Please feel free to DM me and we can discuss the issue over a call.
@sogasg thoughts on where this should fall in the roadmap/milestones?
This would make use of the `arcVersion` option shown here: https://github.com/daostack/migration/blob/29b7da1dfa2090098c8672b562a3eadc74acba90/migrate-dao.js#L4
I do not want to do this without Arc Hives / Factories being fully integrated into the stack and in production. If we add this to DAOcreator now, new users...
No I'm referring to the Scheme Configuration UI in the DAOcreator. I think Alchemy actually supports this by default, not sure.
There's a feature that exists in the migration script + params where you can include a custom contract address + ABI to be called after the deployment of the DAO....
I'm good with merging this, but the CI is still red for the templates, looks like some of them aren't properly building: https://github.com/polywrap/cli/actions/runs/6706112620/job/18221943589?pr=1924
I think the proposed solutions you laid out are very interesting, especially making the URI resolution system "semantic versioning aware". I think it'd help if we clearly label each possible...
After running through this, personally I'm in becoming favorable of `A` & `D`, but curious what others think / feel.