deso-protocol / deso-protocol/frontend
Error when private message sent through deso.py
- Dominant language
- TypeScript
- Stars
- 271
- Forks
- 128
- PR merge metrics
- No merged PRs in 30d
Description
When a private message is sent though [deso.py](https://github.com/AdityaChaudhary0005/DeSo.py) library, the sender is shown the below message in the inbox from bitclout.com and diamondapp.com
``
The receiver receives the correct message though. But the sender has issues in seeing the message sent.
Issue mentioned in https://github.com/AdityaChaudhary0005/DeSo.py/issues/20
Is it because of mistake in [deso.py](https://github.com/AdityaChaudhary0005/DeSo.py) or in deso frontends?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing a private message sent through the linked deso.py issue and compare what the sender sees in bitclout.com and diamondapp.com with what the receiver sees. Review the linked DeSo.py issue for the reported behavior; done means the sender can view the sent message without the non-decryptable error, with the responsible component identified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, typescript
- Domain
- frontend, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100