shc261392

  A corrupted image can be created by using the above script with this image and this thumbnail 

Found another case of corrupted image from production site. Here are 4 related images: downtown-koto-ku.jpg (original image, has CAI info): https://drive.google.com/file/d/1Yz-jPigYHW5AlqRD24ChC8qfzlVnVHvC/view?usp=sharing downtown-koto-ku-thumbnail.jpg (original thumbnail, has no CAI): https://drive.google.com/file/d/1xIQnrPNvABdcQi7jAX8j8FOJORWKxbLt/view?usp=sharing downtown-koto-ku_cai__3__.jpg (CAI...

Another corrupted image: https://drive.google.com/file/d/1U8XhsSFdrSFLLrio1AuLA4wXJvHoQ95k/view?usp=sharing It might be easier to find the the common trait of these images and find the root cause if we could find more cases like this

That makes sense to me. Also it would be nice to keep the `nftRecord` as array structure and allow multiple NFTs in a one-time commit to support the case that...

> Hi @shc261392, thank you for opening the PR. > > At the moment we do not merge new blockchains into WalletCore without a positive decision from our Business Development...

@Cryptocool1 Sorry for pinging again, we just want to know if the ticket submitted are getting viewed because we hadn't receive any response for weeks.

There is only `Internal Server Error` message, no additional info. After setting the cmds subsystem log to debug level, here's what I've found that could be relevant: ``` 2022-03-18T04:24:18.494Z DEBUG...

Here's what I get for running the above command: ``` $ ss -at | tail -n +2 | awk '{print $1}' | sort | uniq -c | sort -n 16...

I have read the CLA Document and I hereby sign the CLA