- [ ] duplicate images (or detect similarity to a certain degree) - [ ] referencing images outside of a chains package is a no-no — require image sync if those properties exist - [ ] another thing is to parse existing images that don't have sync and determine where they exist, and sync them - [ ] allow uri data images — for npm modules — only do for images.isPrimary - [ ] for images, potentially create a new catetegory,e.g. ibc_info, assetlists, chains, images - [ ] allow for uploading images to a FE, and updating a basePath - [ ] composite images — circle in circle — ask Jeremy - [ ] chainreg2.0 — `ibcInfo`, `assetLists`, `chains`, `images`
ibcInfo,assetLists,chains,images