echo-server
echo-server copied to clipboard
WalletConnect
WalletConnect Push Server Implementation
We are using the `notifications` table just for the idempotency, so the table can be pruned once a week to clean the database space. Full context: https://walletconnect.slack.com/archives/C03SPNLG39P/p1706209564977319
GeoIP lookup errors like ``` ERROR geoip lookup error.. ``` should not be considered as 5xx.
Export metrics on client registrations that enable `always_raw` so we know % of clients that upgraded to use this new feature https://github.com/WalletConnect/echo-server/blob/ea1401e818aae6cf7ab0b0819cf4358f2469608b/src/handlers/register_client.rs#L124
At the moment when the `create_client` is called all the related to the supplied client.id [notifications are deleted](https://github.com/WalletConnect/echo-server/blob/3dde225228178c6198c89d674113c05ad4eb700b/src/stores/client.rs#L36) from the `notifications` table. We can preserve the notification records in this...
We shouldn't reject if we already stored a notification, we should check if the notification exists and if it does see if this notification has been processed before, if so:...
### Is there an existing issue for this? - [X] I have searched the existing issues ### Current Behavior Assumption: when `/internal` API calls HTTP5XX/HTTP401/HTTP403/HTTP400 then echo server is down...
Look at relay tests to ensure that Echo Server has tests implemented for the analytics feature
The analytics export have zero test, c.f. [relay](https://github.com/WalletConnect/rs-relay/tree/master/tests/analytics) for examples
geo-data columns for this data are always null. Determine: * does it make sense to have geo-data ? ( push_messages don't origin on user interactions) * do we have IP...
