Topic: Infinex - PoW & Masternode - Lyra2Z (True DEX over MN with Profit Sharing Soon) - page 2. (Read 43306 times)

I'm assuming the latest Bitcoin vulnerability (double spending on blocks, wasting them & crashing nodes) works on Infinex, too. Don't see any commits fixing this. Any comments?

I'm assuming the latest Bitcoin vulnerability (double spending on blocks, wasting them & crashing nodes) works on Infinex, too. Don't see any commits fixing this. Any comments?

More clarification on point 3 about the implementation details & security provided with public private key & password method.

When users first use InfiniDEX app, app would automatically generate unique public private key inside users PC. As it's a newly generated key, users would be prompted to input a password for the account.
The input password would be hash & ONLY THE HASH VALUE would send over to DEX network together with the public key & signing of the message using private key.
With that, nobody would know what your actual password is except for yourselves (as some users would always use the same password for every different platform thus we would like to prevent password leak issue)

Using above method, the verification of users identity would be through the signing of message using private key with password hash value in it & with the public key inside DEX network to verify users.
It added security where anyone who have access to your PC, without your password, won't be able to do anything with your account.
Anyone without your private key won't be anything to hack your account at all.

Ultimately, safekeeping public private key file & your own password is the only thing that you need to do.

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

@everyone

Good day everyone!

I'll be shifting to new Home Office this Thursday (to prepare for new chapter in life end of the year :grinning: )
Initial plan to launch InfiniDEX Beta on Wednesday seems to be very tight as there are quite a number of relocation going on & I don't want to affect the support during release.
Thus I hope for patience & understanding from everyone to wait for few more days as I would push InfiniDEX Beta to release on Monday (01 October 2018) instead.

Hopefully we are the first to release true DEX over MN.

Lastly as per queries in channel about the DEX reward for MN holder, for more clarity:
* The reward is 50% of total trade fee collected & split for MN holder.
* Reward would come in BTC, ETH, DOGE (whatever the subpair is), e.g. IFX/BTC - subpair is BTC; IFX/ETH - subpair is ETH.
* InfiniDEX Beta would start with 0% trade fee (to attract users).
* Kindly wait for official announcement (in 1 month time) for MN holders to update their core Wallet & MN side node.
* After update, users would be provided with new field in core Wallet to input their receiving address for the trade fee (start with BTC, would auto add everytime new subpair added).
* Trade reward would be accumulated & distributed in fix interval automatically.
* Pro-rate distribution are calculated for MN who start late during the month or terminate the MN halfway (fair for everyone).

With this, updated countdown timer as below:
https://www.timeanddate.com/countdown/launch?iso=20181001T08&p0=236&msg=InfiniDEX+Beta+Launch&font=sanserif&csz=1

Once again, thanks everyone for being with Infinex.

1) What exchanges are planned to be? Is there any yet?

2) there's no Infinex listed on BSOD.PW

Latest commits were on April... nothing to improve?