User:
RockBitNBlockAdditional information (optional):
* Some of his posts on technical board also got deleted by moderator. See
https://ninjastic.space/post/65559184 and
https://ninjastic.space/post/65559284.
List of post:
This looks like a classic case where Node.js hits its memory limits during long runtimes without a restart.Maybe it would be worth considering moving part of the explorer to a different runtime like handling the backend in Python and letting the frontend pull JSON from a cache instead.
Yes, I suggested moving only the backend part the part doing repeated RPC calls into Python not rewriting the entire explorer.
The idea is:
Keep the existing frontend
Replace or supplement the backend with a Python script that periodically fetches RPC data and stores it in a local cache.
Let the frontend pull from that lightweight cache instead of making live RPC calls every time
This could eliminate the memory bloat in Node.js from repeated RPC calls and long runtimes.
If you don’t want to do that, at least make sure to run Node.js with an increased memory limit
node max-old-space-size=8192 ./bin/www
1. Suggesting to rewrite BTC-RPC explorer isn't realistic suggestion, especially when the one who asked question doens't mention he's a programmer.
2. Even if he only suggest to rewrite the backend, i expect the frontend need to changed as well since it'll communicate with different backend.
FYI, the btc m4 14 label is most likely an old blockchain.com userdefined tag added through verified message signing nothing to do with Satoshi. These addresses show classic exchange transactional volume. Use tools like walletexplorer to check clustering and ownership patterns.
Source image: https://www.blockchain.com/explorer/addresses/btc/3MqUP6G1daVS5YTD8fz3QgwjZortWwxXFd1. "M4 14" label is unlikely to be user defined tag, since it has verified icon.