Can I have some wishes for the callisto hub?
Now it takes a very long time to load assets and even longer NFT. If there is a lot of NFT on the wallet, then the wait is measured in minutes.
This all happens because the hub tries to read everything it knows about from the node and sends thousands of requests to the node. If only a thousand people go to the hub page (we plan to grow?), Then it will be millions of requests. I don't know how many requests the node can process without delay, but it looks like a waste of resources.
Most users do not need to display all known coins and NFTs immediately upon entering the wallet.
I would like to suggest implementing a slightly different approach that will speed up the operation of the hub and reduce the number of requests to the node many times over.
Load only a few main network tokens when opening the hub page page. Also place a drop-down list (which will contain all the other tokens) in which the user himself will choose which balances to load additionally. The same is true for the NFT. Only a list of projects that will be loaded at the user's choice. It will also help to avoid "mess" on the NFT page, when all possible NFTs are displayed out of order.
Also, with this approach, it would be good practice to remember the settings of each wallet connected to the hub so that the user does not load tokens every time, and they are displayed immediately upon entry. Ideally, this list could be edited. For example, the "-" sign at the end of the line with the token will remove it from "loaded by default".
Can I have some wishes for the callisto hub?
Now it takes a very long time to load assets and even longer NFT. If there is a lot of NFT on the wallet, then the wait is measured in minutes.
This all happens because the hub tries to read everything it knows about from the node and sends thousands of requests to the node. If only a thousand people go to the hub page (we plan to grow?), Then it will be millions of requests. I don't know how many requests the node can process without delay, but it looks like a waste of resources.
Most users do not need to display all known coins and NFTs immediately upon entering the wallet.
I would like to suggest implementing a slightly different approach that will speed up the operation of the hub and reduce the number of requests to the node many times over.
Load only a few main network tokens when opening the hub page page. Also place a drop-down list (which will contain all the other tokens) in which the user himself will choose which balances to load additionally. The same is true for the NFT. Only a list of projects that will be loaded at the user's choice. It will also help to avoid "mess" on the NFT page, when all possible NFTs are displayed out of order.
Also, with this approach, it would be good practice to remember the settings of each wallet connected to the hub so that the user does not load tokens every time, and they are displayed immediately upon entry. Ideally, this list could be edited. For example, the "-" sign at the end of the line with the token will remove it from "loaded by default".