nanocrawler VS nano

This touches on payment ids which is historically a sore spot with Nano. Without running a full node and using unique receiving addresses, verifying payments is hard to do. That said, there are work arounds. You can leverage the NanoCrawler apis and check pending blocks for unique transaction amounts (add tx id at end of raw transaction amount). In fact thats how Nano.to is verifying payments in the backend (unless he started up his own node).

https://nanocrawler.cc/ no transactions is occurring.

Ok, then, look at the network. Transactions don’t match market-cap price. If XNO was truly $2.82 you would see much bigger transactions on the network. Recent transactions are almost always x10-3 https://nanocrawler.cc/

Look up the public address you have on 2miners on nanocrawler.cc or a similar site. It most probably it says the transactions are ready to be received.

I personally think the best project in crypto for money use( ideology ) is Nano but the used of nano right now is so small (https://nanocrawler.cc ) we average less than 1 tx/s of use . So we are a big community but nobody use the network.

You can find the tx hash on https://nanolooker.com/ or https://nanocrawler.cc/.

That being said please remember to give credit to NanoCrawler and the wonderful APIs they made

Receiving funds while your seed is safe and offline is easy: You can just generate some addresses from your seed while on the offline machine and hand them out as usual. You can see what people are sending to these addresses by watching them at services like https://nanocrawler.cc. It starts to become more difficult once you want to pocket your funds, set your representative or withdraw funds. This is where offline signing comes into play.

Couldn't you use just a vanilla Golang (or any other language) microservice for all of this? If you know what you are doing you can have a bulletproof basic service with all of the above up and running in no time, just add your game logic. Most of your requirements are part and parcel of any modern commercial Docker microservice. Never mind that such frameworks already exist, e.g. nano [0] specifically designed for games.

Scalability is also not an issue. Number of simultaneous players and objects is limited by bandwidth and latency only. There are certainly no barriers to handling multi-million entity databases on any modern server. You're really only limited by how much data you can push out to your users within an update tick. And of course by how much money you're willing to pay for back end compute capacity on an ongoing basis. But those costs are very low these days, especially if you have dedicated servers rather then AWS/Google/Azure.

I think perhaps the issue is not so much that frameworks don't exist, but rather that no single framework has achieved popularity in the game design community. The indie crowd is not likely to want to, or afford to, run servers for years and years, so the demand is not there. The triple-A studios roll their own.

[0] https://github.com/lonng/nano