Pulsechain.box
130 posts

Pulsechain.box
@pulsechainbox
Pulsechain Scanner - powered by Gypsy Labs 🧪 and more…










This is how expired limit orders will look in your personal order book. @SwitchDotWin #PulseChain 🪄 0xcurv.win


So hey @RichardHeartWin remember when you said if we want something done on Pulsechain we should use the pulsechain gitlab to open an issue and we should get a response from the team? Well I did just that yesterday but @bretep decided it's better to close the issue and make it confidential before providing an answer. Yo #pulsechain how do you feel about this? Please see photos below. Back-story: Postgres 13, the DB engine running the explorer has been EoL ( not getting any patches or security updates ) since Nov 2025. I have made an issue outlining exactly this fact and asking if there is a mitigation plan to not be in a position where the scanner is prone to a vulnerability on the scale of the MongoBleed cve from a few weeks ago. Bretep saw the issue I have opened and decided to make it confidential and close it without offering a response on the question.. how is this making you feel? Pulsechain, I'd appreciate if you'd share this post! Maybe we'll get an answer on the question. Thanks, Ave.


scan.pulsechain.box/address/0x00c5… kekxplorer.pls.fyi Thank you for the time!

@HWYPEWPEW We would rather accept donations or just stop the project than look to scheme people for a little bit of room to move. It is not in our ethos to act in such a way. But appreciate you for the thoughts!



Hello PulseChain! As an update on this matter, the migration is still on-going. At the moment we can but wait until the process is finished to see the outcome. Thank you!

1/3 Hey PulseChain community, Quick update on the Pulsechain Box Explorer: As covered in detail in my pinned thread (the post-mortem from the recent DB server crash), we've been running on a temporary single-machine setup after losing the original 16TB database




