Yes mate, when you look at a block you can see all the transactions that are included in that block. How many there are, which addys made the transactions plus the amount in coins.

I think cloning + maintaining + adding new feature for POC coin is not as easy as normal PoW , PoS coin. I suspect if there is ever a clone of burst it would be just copy and paste. No new feature and it would probably be a scam coin because it's not an easy coin to maintain.

Also , it's not a good time for alt coin in general for this period of time.

If burst were to be release last year, i bet it would reach 5,000 - 10,000 sat.

If alt coin pick p next year , we will probably see some cloning but by then burst could probably be the market leader in PoC coin.

the pool situation is a direct result of the java backend.
java is not designed to scale quite well by simply adding memory to centralized hosts.
the solution is to port (start from scratch) the required burst protocol parts to a solid c++ backend and run the pools with that.
every single effort which is put into the java code base to stabilize the pool situation is in my eyes not worth it cause the next limit is already set.

what burst needs is a core functionality c++ api to host professional services.
this includes to act as full network peer (aquire and distribute the blockchain),
submit blocks to the network,
extract reward receipients from the chaindata,
send burst,
extract messages,
send messages
and to create addresses from private keys.

if this works the whole api functioniality for the asset exchange and marketplace may get added.
a intermediate solution may be to create a mysql backed partial blockchain with php access to take the pool load away from the java components on the pools. however, as far as i know is the core pool servercode still based on java.
another option to stay with java may be to add autonomous proxies to the pools which submit the round reward assignments to a hidden internal pool server which distributes the rewards. keeping them in sync may be much harder to code than starting to design the c based api from scratch.

a simple pool design may be this:
wallet (current or c based) --> distribute current block information and stats to the miner connect nodes
connect nodes --> provide block data to the miner, accept and verify shares, provide cached stats --> submit miner results to central hidden node
hidden node --> distribute rewards, provide stats
load balancer --> knows throughput of shares for each node and assigns miners to nodes

I think this has more to do with the approach used by uray's pool software. Every single nonce sent is http posted to the wallet, which apparently doesn't handle that much load that well, and the wallet ends up also doing a lot of redundant calculations, as it doesn't save the mining related information between calls. If the pool checked results and only passed on the best ones, I don't think the situation would be as bad.

Under more sane conditions the built in api should be able to handle requests without issue, but if not the h2 database can be directly accessed by another program if the h2 AUTO_SERVER option is set.

sorry i've been off for couple of days, currently focusing on upgrading pool, i am sorry if there are a lot of problem before, its because vps provider is pushing me that i made too huge tcp connection, too many cpu time, too much traffic, so i ended up moving all of those pool to new dedicated server, with new software which should be more efficient and has better reward distribution, currently SG and EU already using new code and under testing, and also the front-end is still buggy but i believe back-end is working as intended right know

no, my pools does not post every single nonce received to wallet, its processed first in native C++, and only best nonce for current round is sent to wallet, and also mining info related APIs are cached, its not directly from wallet

but i believe another pool that use my source code doing direct send to wallet for every single nonce, its my guess anyway, because it is how it work in the very basic source code i made public

anyway q327K091, what do you mean pools are in major disarray ?

Maybe it would've been better to send them encrypted blockchain messages?

You might want to adjust the range it accepts guesses. The miner who mines block 4 will be able to include his own transaction in block 4 while knowing what scoop block 5 will require. I don't think anyone would bother doing that at this stakes, but just wanted to point out that the person who mines block 4 is able to cheat.

Hey uray,

did you read my post a few pages back: https://bt.irlbtc.com/view/731923.msg9652448#msg9652448 ? Are these issues solved so I can return to SG?

Haaaa.... 800 sat for each??!  Go back to your pot,ganja,maryj,dank coins!
Lol