---
# System prepended metadata

title: Untitled

---

## Remaining Items (in order of priority)
- [x] chrome local key storage
- [x] messaging
- [x] firebase push notification integration
- [x] xmtp production API issues
- [ ] layout bugs / issues (detailed below)
- [x] merge conflict resolution
- [ ] readme for chrome extension
- [ ] faster local state restoration
- [x] push: subscribe to convo topics like in readme: https://github.com/xmtp/example-notification-server-go/blob/34b6fcdd514a66da768015c64f26ca637071a0ed/docs/notifications-client-guide.md
- [ ] send message from background script to frontend

## UI bugs

- [ ] Hook up existing connect wallet button to new web3modal stuff
- [ ] dual scroll bar issues (think this is due to the fixed height popup)
- [ ] ENS address substitution: messages list, message thread (in progress, almost done)
- [ ] fix inconsistent additional wallet signature request
- [ ] clicking new message button should go to new thread screen
      ![](https://i.imgur.com/f3tHXpz.png)
      
## Outstanding questions?
- [ ] How do messages get queued in the push server? Does XMTP Api do that?

## Notes

### 12/22/22

#### Firebase push server

Running into some weird chrome extension-specific issues. Firebase requires you create service-worker with a specific name in a specific location 🙄, so I need to change how some of the esbuild bundling stuff works to package up the background script into that file.

~~#### XMTP Production API Issues~~

~~I'm getting decryption errors when I connect to the production XMTP API, but not against the dev api.~~