Currently, we are supporting the filtering the UTXO in local db based on the public key of interest.
basically, we are filtering only UTXO belonging to the keys that are installed in cli-wallet during the time block syncing.
As of now, I am not sure to achieve this in UTXO model if I want to get the kitties from the user whose keys are not installed in my wallet, which is the real-time scenario.
Since UTXO are scattered, difficult to search for kitties that are for sale based on owner.
One idea is
Maintain an off-chain database that stores each kitty irrespective of any user, as we are doing now.
In real time situation. the size of locadb increases.
https://github.com/mlabs-haskell/TuxedoDapp/issues/4 https://github.com/Off-Narrative-Labs/Tuxedo/issues/184
This is difficult to implement:
Currently, we are supporting the filtering the UTXO in local db based on the public key of interest. basically, we are filtering only UTXO belonging to the keys that are installed in cli-wallet during the time block syncing.
As of now, I am not sure to achieve this in UTXO model if I want to get the kitties from the user whose keys are not installed in my wallet, which is the real-time scenario.
I will investigate on this or ask Joshy.
Withen the same wallet, I can do search based on the public key : https://github.com/mlabs-haskell/Tuxedo/blob/4caa90a2cc88b70973427c55c154f5af224118b8/wallet/src/sync.rs#L639-L644
Since UTXO are scattered, difficult to search for kitties that are for sale based on owner. One idea is Maintain an off-chain database that stores each kitty irrespective of any user, as we are doing now. In real time situation. the size of locadb increases.