bts-cm / beet_api Goto Github PK

At the moment, the data fetching scripts are run once before compiling the beet_api, however it's entirely possible for new blockchain data to be created after compilation and we'd be missing out on this info.

We should perhaps move away from solely pre-compilation data fetching, to during runtime scheduled data fetching.

We can use the following elysiajs package to schedule regularly fetching the data, if being run on a server for example.

https://github.com/elysiajs/elysia-cron

If an asset/offer/account which is associated with a blocked scam account is requested from the BEET API, we should consider responding either with a blank response, an error, or inject a field indicating the object is associated with a blocked account.

This way we can either avoid showing blocked user content entirely, or the UI can warn the user that they're interacting with a suspicious blockchain account.

Add optional (default enabled) compression to every endpoint to reduce total page request payload size