-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solving the issue #150
Comments
I'm not sure that this is actually the case. The original Vitae chain is still running, this fork doesn't even provide any source code. |
In fact, the Vitae fork chain was fixed by him. Just go to your Stex account - open your Vitae transaction ID from day first one |
There are 2 chains, you tell me which one is the real one? The original chain is still running, but is not the one at your link. @iqmojo is not a developer. He didn't fix anything. I'd also like references to said malicious behavior. The blockchain doesn't lie, so it should be easy to bring up examples of it, were it actually happening. |
Okie you right: Are you on Stex Exchange ? |
Blockchain is not voted on by the community, by the decision of an individual or company. It's not decentralization - it's not democracy. It is a form of dictatorship. |
When you can make multiple wallets and then use multi-send with split-transaction, you can make tracing very difficult. Along with the ability to delete a masternode and make a new one, giving even more obscurity to the exploit, it is very difficult to trace wallets and rewards. Sending false headers to nodes to eliminate them from the the reward and limiting communication with DNS, you can then gain selection. Due to the conflict resulting from Supernodes and Masternodes agreeing on the winner, having an increased time sequence for wallet verification, you can then gain first place. When other nodes are not able to communicate through the DNS and are just milliseconds behind, the ledger forks when other nodes declare the winner and print to the ledger. Once a node is on a different chain, they are no longer eligible for the "original" chain, making it easier and easier to exploit and gain rewards. When the chain has nearly 20 different chains, because other nodes begin to rely on those headers, the only thing you need to keep doing is splitting the rewards, multi-send to multiple wallets, programmed for additional multi-send and mixing the "tokens" from timed sequencing in the wallet for the transactions, it is difficult to verify what wallets are used for the exploit. Since we don't know who has the wallet address in their possession, it would be near impossible to track a reward, even if we were to follow a hash from beginning to end. But when you attack the new chain, it is easier, since there is less wallets and there are no Supernodes to create conflict. By implementing checks and other measures, we were able to keep that exploit from happening. But when you try to exploit the Supernode rewards, you should know that, I, Michael Bradley, the Founder of Vitae, kept a record of every supernode address and the owners name, in case issues with those nodes occurred in the early months. SMD. |
Can you show any on-chain record to backup your statements? Perhaps some links to transactions or blocks on a block explorer? |
Got any math proofs to back this up? Sounds like you are conflating things.
Point to me where the Nash Algorithm is implemented in Vitae's Blockchain. Or explain how it has anything to do with vitae.
Well this is awkward. I'm sorry you feel this way. What have you done recently to contribute to Humanity, or are you just a taker? ...
@Cantrieudo1981 Please stop flooding these tickets with irrelevant spam posts and images. You are not a developer, what are you doing? |
I am nothing |
It was important to solve the issue of the fork and find out that there was malicious activity on the part of a a known person associated with Vitae. Without solving this the likely hood of continued listing on STEX and HITBTC would have been unlikely. It would have also been more difficult to keep the fork from happening over and over.
https://github.com/vitae-labs/Vitae/releases Is already trading on STEX and HitBTC.
The text was updated successfully, but these errors were encountered: