Some update for everyone on changes that is being worked on for InfiniDEX

1) First one is more of low level changes that need to be done & can't be changed once DEX goes LIVE.
It's about categories of messages that are being sent & received between nodes.
Current Bitcoin core have around 30 types of messages, so every time a node receive a message, it would loop through every single possible category before deciding where it belongs to.
Looping through 30 categories (although can be considered quite a lot) but as number of messages between nodes is not so much so its working fine.

For our DEX, currently we have around 100 categories of messages just for DEX alone (which is still growing).
Moving forward, as more traffic move up between nodes for DEX live processing (something like number of processes per second), looping through hundres of categories for every message would sooner or later cause performance hit in the speed of processing.
With that, we have implemented direct routing for messages categorisation so it should help with performance in the long run

---------------------------------------------
2) This is more of a value (limiter) setup with value changes could be done from network. Its something like max number of messages of same category could be in single transfer, number of histories to display for users & others.
Previously we hardcoded the limit for those but we think moving it to changeable value should be better.

3) Currently CB implement login using something like username & password in private key form (which seriously I don't think anyone can remember the private key thus most of the people stored the key somewhere & copy paste it).
We don't think that its safe, thus the way we plan to implement is by using password defined by you (first usage of DEX), along with private key inside your computer to verify your identity. Your password won't be saved in the network (as we would only get the hash value generated from password & verify it). With that, for multi devices access, you would only need to copy the private key file to all your devices that you want to access.

4) Something that we plan but haven't really think of how to implement yet (need to read Bitcoin source code first to find the function). It's more of continuity for point 3. Transferring private key file is a hassle & could prove to be difficult to transfer it from PC to possibly mobile device app (which we haven't develop yet but definitely needed in the future). With that, we are looking to apply HD key (seed key, where users input 12 unique letters to generate key, something like hardware wallet). By using HD key, it would be easier for users to have access to their account on multiple devices.


This conclude the update for today & more frequent update will be coming.
Have a good day @everyone