moinen: thanks for your previous summary, it helped get me started!
At this point, I'm the most intrigued as well as perplexed by the transactions, however I think the order of likelihood of meaningfulness is 1. rest of the text in the image, 2. dots, 3. transactions.
I suspect dots to be the next step. We already have a plaintext message in the characters, so I am wondering if the dots will inform us how to decode the rest of the characters in some meaningful way. Or are in fact some sort of binary message. Or something.
Has anyone considered reading the dots from top to bottom, right to left or even diagonally?
I've done quite a bit with them right to left, but not top to bottom or diagonally. Top to bottom or bottom to top may be very promising. I also think there's possible rainbow-shaped traversals given the shape of the data set.
Also I was thinking, could the blue dot be a starting point and the yellow dots signify some sort of change in reading direction?
I've thought about that as well, and whether there's an embedded maze. Also, I've been thinking about traffic lights, i.e., red=stop, yellow=slow, green=go. I haven't really gotten anywhere on either of those fronts - there don't seem to be any clear uninterrupted paths..
Why that triangle is downward? Is that a indication to start from the bottom to top?
That is a possibility. However, it also happens to be the dark wallet logo. IMO the upper left corner of the triangle points directly at the blue dot as a clue, others here think it doesn't point exactly at that.
As a side note, I spent a bit of time refreshing on morse code and I suspect it's a nonstarter. Morse isn't binary - pauses are an important component to know when a letter ends. Normal letters can be anywhere between 1-4 dots and dashes, numbers, symbols, and special characters can be up to 6.
Given that we see sequences of multiple red, green, and yellow dots in a row, none of them seems like a good candidate to be a delimiter for morse. If we look at just reds and greens, for example, we wouldn't be able to tell the difference between ETE (./-/.) and R (.-.). This quickly wanders into inelegant brute force territory.