BalkanBetBox
Newbie
Offline
Activity: 90
Merit: 0
|
|
January 10, 2019, 05:22:03 PM |
|
|
|
|
|
Douche McBAgs
Newbie
Offline
Activity: 1
Merit: 0
|
|
January 11, 2019, 07:01:26 AM |
|
Finally, something new and exciting to mine.
Sorry bro, not really Somewhere around the new year xcg implemented their TSA/xbuffer algorithm which was supposed to prevent 51% attacks... Supposedly it would prevent miners from jumping on the network with high hashrates getting all the blocks. The algorithm was supposed to recognize that such a high hashrate has come onto the network and block the excess hash they provided and only allow them whatever speed the network was allowing at the time. The new algorithm frankly sounded like a good idea in theory and drew some attention from outside community members. Many of them decided to look into the code and read more about it, while a few noticed some major problems. It was sometime around Jan 3rd when several Discord members tried to ask questions and raise concerns in the chat only to be rebuked by the developers and mods. The xcg team was incredibly rude, arrogant, and demeaning to anyone who dared to question anything in their “bulletproof” algorithm. They called people names and gloated at how stupid they were for not understanding the code and what xbuffer really does. Quite a few people were banned for simply raising concerns. Unfortunately for xcg some of the community kept digging through the code and found some critical errors that allowed someone to not just attack the network with high hashrates, but with little to no hashrate at all, you see the math in the code was flawed in a way that when high hashrates hit the network it would drop the diff to 0 which allowed cpu's to mine the coin very easily. A couple of small but simple tricks such as adjusting the time on your cpu would allow in most cases for a cpu or a group of cpus to dominate the network and get ALL of the blocks, essentially a "loop". Many people in the community should be able to remember that when xbuffer came out how many issues they had with pools not being able to get blocks, or only getting orphans. Well the xcg team had every excuse under the sun as to why this was happening and they defended their "xbuffer" algorithm to the death. Anyone who got upset was cussed out and banned from the discord. The team seemed to be very aware that something was happening and was scrambling on the backend trying to patch the exploit even though denying it to the community and reprimanding them should they speak up. There were several Discord members who tried to help but they experienced the same attitudes from the team. There was nothing left to do but to mine the shit out of the chain with cpu's and dominate the chain at any given time. You see the team was convinced that people were throwing a P/H at their network and trying to take it down and again they would gloat as to how amazing their buffer algorithm is and how dumb people are for even attempting when in reality miners were generating thousands of coins with nothing more than a couple cpus. This has been going on for just over a week at the moment. As this type of mess is pretty unacceptable, the chain has been thrown back in time to at a bare minimum verify this post. Several additional actions have also been taken on chain that skilled people will be able to read. Additional details on this will not be shared at the moment provided that the XCG team get their shit straight and in order.
|
|
|
|
Bigpiggy01
|
|
January 11, 2019, 07:08:37 AM |
|
Finally, something new and exciting to mine.
Sorry bro, not really Somewhere around the new year xcg implemented their TSA/xbuffer algorithm which was supposed to prevent 51% attacks... Supposedly it would prevent miners from jumping on the network with high hashrates getting all the blocks. The algorithm was supposed to recognize that such a high hashrate has come onto the network and block the excess hash they provided and only allow them whatever speed the network was allowing at the time. The new algorithm frankly sounded like a good idea in theory and drew some attention from outside community members. Many of them decided to look into the code and read more about it, while a few noticed some major problems. It was sometime around Jan 3rd when several Discord members tried to ask questions and raise concerns in the chat only to be rebuked by the developers and mods. The xcg team was incredibly rude, arrogant, and demeaning to anyone who dared to question anything in their “bulletproof” algorithm. They called people names and gloated at how stupid they were for not understanding the code and what xbuffer really does. Quite a few people were banned for simply raising concerns. Unfortunately for xcg some of the community kept digging through the code and found some critical errors that allowed someone to not just attack the network with high hashrates, but with little to no hashrate at all, you see the math in the code was flawed in a way that when high hashrates hit the network it would drop the diff to 0 which allowed cpu's to mine the coin very easily. A couple of small but simple tricks such as adjusting the time on your cpu would allow in most cases for a cpu or a group of cpus to dominate the network and get ALL of the blocks, essentially a "loop". Many people in the community should be able to remember that when xbuffer came out how many issues they had with pools not being able to get blocks, or only getting orphans. Well the xcg team had every excuse under the sun as to why this was happening and they defended their "xbuffer" algorithm to the death. Anyone who got upset was cussed out and banned from the discord. The team seemed to be very aware that something was happening and was scrambling on the backend trying to patch the exploit even though denying it to the community and reprimanding them should they speak up. There were several Discord members who tried to help but they experienced the same attitudes from the team. There was nothing left to do but to mine the shit out of the chain with cpu's and dominate the chain at any given time. You see the team was convinced that people were throwing a P/H at their network and trying to take it down and again they would gloat as to how amazing their buffer algorithm is and how dumb people are for even attempting when in reality miners were generating thousands of coins with nothing more than a couple cpus. This has been going on for just over a week at the moment. As this type of mess is pretty unacceptable, the chain has been thrown back in time to at a bare minimum verify this post. Several additional actions have also been taken on chain that skilled people will be able to read. Additional details on this will not be shared at the moment provided that the XCG team get their shit straight and in order. I can readily confirm all of the above except for the final part on the chain attack as I'm not running the junk atm. There are holes wide enough for me to stick my massive aging head through in the code. Even with some sections commented out that would alleviate at least some of the problems. FFS...
|
|
|
|
gearshiftjb
Jr. Member
Offline
Activity: 45
Merit: 1
|
|
January 11, 2019, 01:40:17 PM |
|
Finally, something new and exciting to mine.
Sorry bro, not really Somewhere around the new year xcg implemented their TSA/xbuffer algorithm which was supposed to prevent 51% attacks... (It does) Supposedly it would prevent miners from jumping on the network with high hashrates getting all the blocks. The algorithm was supposed to recognize that such a high hashrate has come onto the network and block the excess hash they provided and only allow them whatever speed the network was allowing at the time. (That's how it works yes) The new algorithm frankly sounded like a good idea in theory and drew some attention from outside community members. Many of them decided to look into the code and read more about it, while a few noticed some major problems. It was sometime around Jan 3rd when several Discord members tried to ask questions and raise concerns in the chat only to be rebuked by the developers and mods. The xcg team was incredibly rude, arrogant, and demeaning to anyone who dared to question anything in their “bulletproof” algorithm. They called people names and gloated at how stupid they were for not understanding the code and what xbuffer really does. Quite a few people were banned for simply raising concerns. (people were banned for being insulting, racist or frankly rude about it all. So yes there's more to this.) Unfortunately for xcg some of the community kept digging through the code and found some critical errors that allowed someone to not just attack the network with high hashrates, but with little to no hashrate at all, you see the math in the code was flawed in a way that when high hashrates hit the network it would drop the diff to 0 which allowed cpu's to mine the coin very easily. A couple of small but simple tricks such as adjusting the time on your cpu would allow in most cases for a cpu or a group of cpus to dominate the network and get ALL of the blocks, essentially a "loop". Many people in the community should be able to remember that when xbuffer came out how many issues they had with pools not being able to get blocks, or only getting orphans. Well the xcg team had every excuse under the sun as to why this was happening and they defended their "xbuffer" algorithm to the death. (time error patched with 24.1 and reasons why it's happening shared as they come, same with reasons why it shouldn't happening if you'd care to share that part too) Anyone who got upset was cussed out and banned from the discord. The team seemed to be very aware that something was happening and was scrambling on the backend trying to patch the exploit even though denying it to the community and reprimanding them should they speak up. (anyone who was cussing or demeaning the team was banned yes. When a problem arises it gets patched, no? We weren't denying the incoming patch to the community. Good go though) There were several Discord members who tried to help but they experienced the same attitudes from the team. (if you meant the team of trolls, yes, very helpful) There was nothing left to do but to mine the shit out of the chain with cpu's and dominate the chain at any given time. You see the team was convinced that people were throwing a P/H at their network and trying to take it down and again they would gloat as to how amazing their buffer algorithm is and how dumb people are for even attempting when in reality miners were generating thousands of coins with nothing more than a couple cpus. This has been going on for just over a week at the moment. As this type of mess is pretty unacceptable, the chain has been thrown back in time to at a bare minimum verify this post. Several additional actions have also been taken on chain that skilled people will be able to read. Additional details on this will not be shared at the moment provided that the XCG team get their shit straight and in order. Please share those additional details. Man you're really twisting this.. Username checks out.
|
|
|
|
Matchveil
Newbie
Offline
Activity: 20
Merit: 0
|
|
January 11, 2019, 02:03:58 PM Last edit: January 11, 2019, 02:16:48 PM by Matchveil |
|
The masternode count keeps growing, seems like a lot of people are accumulating through this dip. Which is the exact opposite of what happens when most masternode coins see a ROI drop.
|
|
|
|
Bigpiggy01
|
|
January 11, 2019, 03:31:25 PM |
|
Finally, something new and exciting to mine.
Sorry bro, not really Somewhere around the new year xcg implemented their TSA/xbuffer algorithm which was supposed to prevent 51% attacks... Supposedly it would prevent miners from jumping on the network with high hashrates getting all the blocks. The algorithm was supposed to recognize that such a high hashrate has come onto the network and block the excess hash they provided and only allow them whatever speed the network was allowing at the time. The new algorithm frankly sounded like a good idea in theory and drew some attention from outside community members. Many of them decided to look into the code and read more about it, while a few noticed some major problems. It was sometime around Jan 3rd when several Discord members tried to ask questions and raise concerns in the chat only to be rebuked by the developers and mods. The xcg team was incredibly rude, arrogant, and demeaning to anyone who dared to question anything in their “bulletproof” algorithm. They called people names and gloated at how stupid they were for not understanding the code and what xbuffer really does. Quite a few people were banned for simply raising concerns. Unfortunately for xcg some of the community kept digging through the code and found some critical errors that allowed someone to not just attack the network with high hashrates, but with little to no hashrate at all, you see the math in the code was flawed in a way that when high hashrates hit the network it would drop the diff to 0 which allowed cpu's to mine the coin very easily. A couple of small but simple tricks such as adjusting the time on your cpu would allow in most cases for a cpu or a group of cpus to dominate the network and get ALL of the blocks, essentially a "loop". Many people in the community should be able to remember that when xbuffer came out how many issues they had with pools not being able to get blocks, or only getting orphans. Well the xcg team had every excuse under the sun as to why this was happening and they defended their "xbuffer" algorithm to the death. Anyone who got upset was cussed out and banned from the discord. The team seemed to be very aware that something was happening and was scrambling on the backend trying to patch the exploit even though denying it to the community and reprimanding them should they speak up. There were several Discord members who tried to help but they experienced the same attitudes from the team. There was nothing left to do but to mine the shit out of the chain with cpu's and dominate the chain at any given time. You see the team was convinced that people were throwing a P/H at their network and trying to take it down and again they would gloat as to how amazing their buffer algorithm is and how dumb people are for even attempting when in reality miners were generating thousands of coins with nothing more than a couple cpus. This has been going on for just over a week at the moment. As this type of mess is pretty unacceptable, the chain has been thrown back in time to at a bare minimum verify this post. Several additional actions have also been taken on chain that skilled people will be able to read. Additional details on this will not be shared at the moment provided that the XCG team get their shit straight and in order. I can readily confirm all of the above except for the final part on the chain attack as I'm not running the junk atm. There are holes wide enough for me to stick my massive aging head through in the code. Even with some sections commented out that would alleviate at least some of the problems. FFS... Didn't you admit openly about using botnets.......... i'm sure, you would be the last person anyone asks for an opinion. Why trust someone that openly states they exploit. I came on your discord and asked about a miner for a bot net. Instead of a "fuck off" which I should have gotten. Your lovely team gave several suggestions all of which happen to work. As to running botnets nah man, not my style. I get sick and tired of scammy, clammy fucks who know zip about what they are doing misleading the bitcointalk/crypto community. You guys are the team who claim petahashes of x16r repeatedly hit your joke of a network. Renting that kind of power, if it were available in the first place (and no, there are not that many x16r ASICS even on RVN atm), would surpass the cost of your market cap. Get real and check your absurdly broken calculation mechanism. Do you have a decent concept for a project yes which was what caused my initial interest. You have however managed to tear that up quite nicely. Do you know the first fucking thing about blockchain tech and consensus, nope! You have a network that consistently overwrites itself so you removed orphans from showing in wallets etc. Apparently you feel that keeping a chain running is more important than keeping it accurate. Hell, you might even have caused double spends with the level or retardation I see ongoing. As to your request for help earlier on a patch, I'm fairly certain that was offered by several people but you chose to ignore it. This is turning into a mess on the same scale as reef. Oh and asshat, as to proof, anyone who can read a chain just needs to grab it and look at the tips to see the level of suffering I'm talking about.
|
|
|
|
gearshiftjb
Jr. Member
Offline
Activity: 45
Merit: 1
|
|
January 11, 2019, 05:04:28 PM |
|
Looking into getting a professional copy editor for your team here.
|
|
|
|
Bigpiggy01
|
|
January 11, 2019, 05:08:21 PM |
|
Looking into getting a professional copy editor for your team here.
:w00t: feel the need to go hide in a new ANN where you can moderate your own shit if you're still dumb enough to believe an iota of it :w00t:
|
|
|
|
gearshiftjb
Jr. Member
Offline
Activity: 45
Merit: 1
|
|
January 11, 2019, 06:36:23 PM |
|
Looking into getting a professional copy editor for your team here.
:w00t: feel the need to go hide in a new ANN where you can moderate your own shit if you're still dumb enough to believe an iota of it :w00t: what?
|
|
|
|
MDSTUD
Newbie
Offline
Activity: 3
Merit: 0
|
|
January 11, 2019, 07:20:18 PM |
|
Looking into getting a professional copy editor for your team here.
:w00t: feel the need to go hide in a new ANN where you can moderate your own shit if you're still dumb enough to believe an iota of it :w00t: what? The pools probably not going to get to many blocks, I think
|
|
|
|
gearshiftjb
Jr. Member
Offline
Activity: 45
Merit: 1
|
|
January 11, 2019, 09:25:50 PM |
|
Looking into getting a professional copy editor for your team here.
:w00t: feel the need to go hide in a new ANN where you can moderate your own shit if you're still dumb enough to believe an iota of it :w00t: what? The pools probably not going to get to many blocks, I think Okay but I'm not sure what that has to do with a copy editor lol
|
|
|
|
AltcoinCash
Member
Offline
Activity: 502
Merit: 15
Building Altcoinchain
|
|
January 11, 2019, 10:48:40 PM |
|
I am one of those banned for asking questions. My pool never found a block after the update, and there was no words about being CPU only upfront the update. I questioned old transactions coming up within the last blocks, so I was stamped retard and whatnot before I finally got banned. I hear they also is going after me in real life to sue me, thinking I wasted even more time on mining them secretly. This coin got something worse than a 51% attack, and that is its team. Community takeover and rollback to old code, anyone?
|
|
|
|
Bigpiggy01
|
|
January 12, 2019, 04:50:52 AM |
|
I can't believe you fell for that! haha, racism never wins. Eventually people realize the other is just as human as you are. So short story to all, they tried attacking me and making rude remarks, because i said no they are wrong and gave an explanation. Now that i know it was you in another discord name..... its up to me now, if I want to proceed with the law. Never knew sticking up for yourself against trolls or arrogant people meant a bad thing. i think you should all stop now banning is the least anyone would do . I personally wouldn't go near these guy's services, if they think this is okay. Dude, you're dumb enough to think those two are the same people good god.
|
|
|
|
Bigpiggy01
|
|
January 12, 2019, 05:29:34 AM |
|
I can't believe you fell for that! haha, racism never wins. Eventually people realize the other is just as human as you are. So short story to all, they tried attacking me and making rude remarks, because i said no they are wrong and gave an explanation. Now that i know it was you in another discord name..... its up to me now, if I want to proceed with the law. Never knew sticking up for yourself against trolls or arrogant people meant a bad thing. i think you should all stop now banning is the least anyone would do . I personally wouldn't go near these guy's services, if they think this is okay. Dude, you're dumb enough to think those two are the same people good god. omg its a private pm! DOH Reported Please, do report me, the moderators on here really like to get bothered by people whining and going snowflake. We can always kick it up a notch and ask a distinguished community member to come in and verify that your junk code works or that you aren't currently trying to scam the community who invest with hash etc. Any suggestions as to who that should be?
|
|
|
|
AltcoinCash
Member
Offline
Activity: 502
Merit: 15
Building Altcoinchain
|
|
January 12, 2019, 05:37:48 AM Last edit: January 12, 2019, 05:48:30 AM by AltcoinCash |
|
Xchange.Kal, please bring here the racist comments, would you? Why don't you just stop lying?You are the douchebag here, nobody else.Here is our whole PM conversation, whats racist? I offered my help as testpool, but could not since I lost internet.
|
|
|
|
AltcoinCash
Member
Offline
Activity: 502
Merit: 15
Building Altcoinchain
|
|
January 12, 2019, 06:22:12 AM |
|
Whenever you proove the racist comments, or publicly excuse your lying to put me in a bad light.
|
|
|
|
AltcoinCash
Member
Offline
Activity: 502
Merit: 15
Building Altcoinchain
|
|
January 12, 2019, 06:36:15 AM |
|
you posted something, and i posted that you took it out context.... again stop
you started this, don't cry now. Like i said move ON.
I think investors need to know who they deal with, as you are playing with other peoples investments. Lot of time and hash wasted on what turned out you could loop mine with few cpu's. This is what I posted, after this I got banned.. Turned out much more than explorer was flawed though... Is this you posting I took it out of context? Being called imbecile, racist and threatened by you, do you think I will fix your flawed code?
|
|
|
|
AltcoinCash
Member
Offline
Activity: 502
Merit: 15
Building Altcoinchain
|
|
January 12, 2019, 06:51:34 AM |
|
The Canadian Human Rights Act[1] (the Act) is a statute passed by the Parliament of Canada in 1977 with the express goal of extending the law to ensure equal opportunity to individuals who may be victims of discriminatory practices based on a set of prohibited grounds such as sex, sexual orientation, race, marital status, gender identity or expression, creed, age, colour, disability, political or religious belief.
Where i come from, those statements i made are correct in the eyes of the law.
PLEASE BACK OFF NOW
Well then I once again ask you to proove those "racist comments". I feel like a discriminated victim of your false accusations. It is not nice to hurt people. Put yourself in others shoes. All i do is defend my self when you clearly attack. Proof, or apologize.
|
|
|
|
AltcoinCash
Member
Offline
Activity: 502
Merit: 15
Building Altcoinchain
|
|
January 12, 2019, 07:34:15 AM |
|
I do not see what that has to do with me?
No I won't stop until your wrongs are corrected.
|
|
|
|
Bigpiggy01
|
|
January 12, 2019, 08:00:32 AM |
|
do you want to stop now? Isn't the fact that you're so unwell something that should have been in the ANN from the start as it would be an important factor in determining if investor's can have any confidence whatsoever in what's going on? Then again you never felt the need to let miners know that your buffer would wreck their earnings and create chain fractures, a chain attackable with a couple of CPUs etc etc etc. Plus you have repeatedly mentioned on discord how unwell you are and how you feel it entitles you to scam/mislead people as to what is going on or in the most snowflaky possible interpretation excuses doing so. Man, keep this up and someone will at some point request that the forum tag you.
|
|
|
|
|