BLURT of course...😅 There you go, it happened... thanks heaps for the ones voting and making me quickly see how this happens here.

As expected, version 0.8.2, and I am not yet sure about the operation flat and bandwidth fees votes, but that can be adjusted later. Although these should depend on the prices of BLURT and how many transactions happen on a daily basis. Not something to worry about much for now.

Produced a block on BLURT

In this case, block #23276513, that carried out 1 transaction from the user @whaaat in regards to an upvote for the post of @spinbunny (about toy cars). I used to love cars like this when I was a kid. Never had many though.

Note to this block explorer - it would be nice if one could "manually" add their own RPC node to be contacted by the explorer - creating defaults is nice for stability, but one should also allow experimentation (maybe for security measures, add some limits to the number of requests, in order to avoid overflows of the website - Nginx can do that easy on a particular redirection).

Right, that's all for now, but if you missed the witness introduction (👈 check here).

Will leave you with these peculiar specimen guys that might have something to say... but are mostly very fun to collaborate with too: @stickupboys (yes I "infested" BLURT too 🤣, gonna drive the entire world to be decentralized!!! 😅)

Vote for witnesses at https://blurtwallet.com/~witnesses
Forky, 🎤💨over and out!