dm3
dm3 copied to clipboard
The dm3 protocol | New standard of web3 messaging | Decentralized ENS-based registry | Secure end-to-end encryption | Easy dApp integration
see #778 and #827 and #909
### TESTED VERSION: STAGING 2024-05-08T10:20:55 a0ddf4 > **PRIO1** ... critical bug, blocks release > **PRIO2** ... bug, but doesn't block release > **PRIO3** ... not nice, not critical for release...
- [x] Would it be a good idea to use asymmetric keys in our jwt? Are they available both in backend and delivery service? Then do it. - [x] issue...
The user has to be able to delete their DM3 name. This requires a button that would trigger the according smart contract call. - [ ] Add the delete feature...
## Tasks - [x] #542 - [x] #543 - [x] #544 - [x] #545 - [x] #547 - [x] #548 - [x] #554 - [x] #555 - [x] #556 -...
### TESTED VERSION: STAGING 2024-05-08T10:20:55 a0ddf4 > **PRIO1** ... critical bug, blocks release > **PRIO2** ... bug, but doesn't block release > **PRIO3** ... not nice, not critical for release...
Since the problem with libsodium is fixed we can finally test the FE business logic. Test - [ ] useAuth - [ ] useConversation - [x] useTld - [ ]...
# Background Currently, both backend and delivery service store the user's "profile" in their database. Since the profile should ideally be managed on-chain, only one source of truth should ever...