Regardless of fault, the way Spots has handled this situation is a little too perfectly scripted from the IGotSpots textbook of scammery.
Gorillabucks:
Spots tried to hide the exploited wallets that were raping the blockchain from the community, the minute he realized he couldn't keep it a secret any longer, he locked the thread and abandoned the coin.
Cubes:
Spots denies there is anything wrong with his perfectly written coin and the minute he sees too many questions were being asked about what happened, he locked the thread and abandoned the coin.
oh, and lets not even get started on the admission during his scripted meltdown that he owns 40 million+ that he had been hiding in multiple wallets since day one, or the fact that he hid under a fake account to start the coin. I mean really, what did you guys expect to happen? This was a spots coin, people told you about him hiding behind that digicube account from the start. They are all full of scammery, hidden premines, fake markets, lies and deception.
Have a look at his latest shitcoin, another swap from a 'just a joke coin, dont take it seriously guys'... where he holds nearly all of the supply because he kept the gigantic premine, again hidden in multiple wallets.
Biggest penny chasing one trick pony shitstain in crypto.
Regardless, it's open source code, it's public, anybody that wants to dev this coin that is reputable and wants to, can take over and make it right the way it should be. so bad or good whatever spots did, he made a great coin, we just need ppl to not depend on one person to make such a large system work on its own, we all have to do this together. that's what he lost sight of. |
|
|
|
The trouble about this is it's really hard to figure this out without being a dev or even hobby programmer myself. Bittrex seems to be right that it looks like there was an issue with the checkpoint server restart. The question here I'd like to know is if the checkpoint server was indeed staking? Then checkpoint server are not really compliant with the idea of decentralization, but so are exchanges for that matter.
Now spots has a point too. There are coins using checkpoints and if indeed it's a matter of running a script, and I see no reason why this shouldn't be the case, then someone like an exchange really should run one to put a wallet in maintenance if things look wrong. Checkpoints may be a source for problems but that doesn't change by disregarding them. For an exchange it's either checking them or refusing any coins running them in the first place. Anyway, my question here would be: If checkpoints are a manual thing and the whole mainchain was on the other fork from it, how did it resolve such quickly? Were such few wallets online that the power of 2-3 people actually checking and spots itself pulled everyone else around?
sprout coin has had no checkpoints (dev left the coin a year or so ago) and the coin runs without issue. Here CUBE's checkpoint server stopped (why?, did he turn it off? was it a power failure?, why did it stop?) this question still isn't answered. and i asked him 3 times what exactly did he do during the reboot phase, and his only reply has been just calling me stupid and saying we all just believe trex and he's done with this coin. what kind of answer is that except one that is in denial and hiding something... I don't think it's realistic for an exchange to be able to manage so many checkpoint servers without enough man power to do that, since it's not an automated system. or they would have to develop one that notifies them of any such issues arising like a script that issues a flag saying the coin hasn't had a checkpoint in X amount of time. And let's point out it is very interesting that CUBE is now without a checkpoint in over 24hrs and are no problems. It was only that moment after gregofdoom was the first to post about there being no checkpoint for 500 blocks that shit started to happen.... WHY?! And trex was receiving VALID blocks, they were as valid as the blocks being confirmed RIGHT NOW with no checkpoints. It's when the rollback happened because the server said oh wait none of these 1700 blocks were checked at the restart point, so it has to invalidate ALL THOSE blocks and start all over again..... If there's another explanation to this, god please give one |
|
|
|
I don't know why I find it hard to reason with many DEVs. They ignore simple solutions, probably because they do not struggle in the real world.
It's like for example why in USA, it's required the president has 14 years of living in the usa to understand what the life is like for the regular people so they can make more sound decisions when they are in office. But greed and superiority sometimes get the best of people, and it just takes a good nudge to knock'm off their high pedestal |
|
|
|
My last message to spots (i needed gregofdoom to send this for me) since he blocked my messages. (thank you doom) Re: (No subject) « Sent to: GREEDYJOHN on: Today at 16:22:33 » Reply with quoteQuote ReplyReply Remove this messageDelete he just blocked me on here i need you to send this message to him. just copy paste it for me thank you please! >>> ============================================================== "I don't think that at all. I believe they had invalid blocks as they say, it's in the logs there is no doubt. What I'm saying is that this can easily be prevented for ALL coins by verifying recent checkpoints. Of the 1700 invalid blocks they confirmed, there were 0 checkpoints, while mainnet continued with valid checkpoints. This is what checkpoints are made for. To not use the tools provided to you by the software is just absurd to me.." Quoted from: https://bitcointalk.org/index.php?topic=1211692.msg15155126#msg15155126------ ...verifying recent checkpoints...ok so that's going in the console and typing "getcheckpoint". ''of the 1700 invalid blocks 'they' confirmed " : they=trex, but you mean the wallet (your code). 0 checkpoints = your checkpoint server stopped what valid checkpoints did the mainnet continue with cause gregofdoom posted that his wallet was 500 blocks from the last checkpoint, he was on the mainnet too, and when i saw his first post about this, i checked my wallet and it showed the same thing of no checkpoints from block 7..912. everybody was on the wrong chain after you restarted the server, that's why i had to reload my older backup wallet and resync the chain. duh! trex doesn't run a checkpoint server you do lol. they have some 200+ coins to maintain, they had no idea wat was going on until it was brought to their attention. so where did 'they' cause this? you are fucking insane dude. you don't expect me to believe the exchange has the man power to monitor checkpoints for possibly some 200 coins do you? how many coins has trex had under maintenance "after" the fact something went wrong. it's no different with CUBE. so again how is that when you are the only one running a checkpoint server for this coin, that trex caused the rollback? infact right now the coin is in the exact same situation as it was that day, but now it's over 24 hrs without a single checkpoint and no fucking issues. so it's hardpressed to believe it wasn't until u restarted the checkpoint server that the problems happened! and i bet if you restarted it right now (ofc you'll do it the right way this time) either the same thing will happen or it will continue on normally. am i right?! ================================================= I know there are devs in this community that watch these forums. Seriously if this is wrong in anyway please speak up! |
|
|
|
|
Hey guys, I'm opening up this thread, so we can keep the community together on this Coin and keep a discussion going for DigiCube, everybody needs to stay together on this and just keep supporting CUBE.
I'm not a dev, so let's make that clear, but I'll do what I can as "support" which i have been doing for anyone that needs to know how to use the coin, and any other things we can work on to keep the coin going.
In the meantime SPOTS needs some time to cool off, he's also banned me from sending him messages on the forum but either way let's just do what we can in the meantime and keep spreading the word about this great coin !
|
|
|
|
I've taken down the checkpoint server. If the coin breaks from here on out, you can blame Bittrex for convincing all of you that they are correct when they are not. You're all pretty much on your own now, so verify that you're synced with the explorer before you send coins
I've done my part, now I'm done. I'm going to focus on PRIME and SPOTS more now because Bittrex has all but killed this coin by getting you guys to believe their shills. Call it ego, call it arrogance, I really don't care. It's not worth my time to explain the same basic principle over and over for months. I'm going to keep staking the 40ish million I have (haven't sold, actually been buying), and we'll see what happens long-term. Good luck with your terrible choice here, guys. Really well done and thought out
WE did not ask you to take down your checkpoint server - we only asked you to strike an agreement with BITTREX, so that DIGICUBE can be relisted. Why all this rush and anger? All we want is for this coin to be put back onto BITTREX. there is no need to complicate things any further. read back on the forum prior to that post, then you'll understand. |
|
|
|
Bleutrade Team (Bleutrade) < support@bleutrade.zendesk.com> 10:15 AM (4 minutes ago) to me ##- Please type your reply above this line -## Your request (#3362) has been updated. Reply to this email or click the link below: https://bleutrade.zendesk.com/hc/requests/3362Bleutrade Bleutrade Team (Bleutrade) Jun 11, 11:15 BRT Dear user, Finally start synchronization. This is not a guarantee that we will activate it. Still we will do several tests. Best regards, Bleutrade Team. progress it's progress, fingerscrossed it will be added  Way to go bro... Thanx! Everybody here must be diligent and actively supporting this coin like i do, that's what a community is and does for each other and that's how bitcoin still thrives today and that's how we can make CUBE the next best thing in crypto! I can't do it all for everybody, WE must work together for the same cause, not for personal vendettas and ego wars. |
|
|
|
Bleutrade Team (Bleutrade) < support@bleutrade.zendesk.com> 10:15 AM (4 minutes ago) to me ##- Please type your reply above this line -## Your request (#3362) has been updated. Reply to this email or click the link below: https://bleutrade.zendesk.com/hc/requests/3362Bleutrade Bleutrade Team (Bleutrade) Jun 11, 11:15 BRT Dear user, Finally start synchronization. This is not a guarantee that we will activate it. Still we will do several tests. Best regards, Bleutrade Team. progress it's progress, fingerscrossed it will be added |
|
|
|
@D3m0nKinGx did you receive any reply from bleutrade ?
yes, they were having trouble with syncing the wallet, i gave them list of nodes and link for the bootstrap to download. waiting to hear on an update from them...i'll post here as soon as i hear from them |
|
|
|
{ "synccheckpoint" : "84c24b9b65095a3cb3bcdb5a3b395f0acf302a10daaa03d65ee48efe925c58bb", "height" : 802241, "timestamp" : "2016-06-11 06:33:57 UTC" } last one. let's make history  |
|
|
|
If you really think it's a checkpoint error on my part, the only thing I am willing to do to make all the idiots shut the fuck up is to remove the checkpoint key. If it breaks in the future, though, it's on Bittrex, then
Other than that, I'm not changing shit, and even this is a stupid fucking move to accept. Take it or leave it, but then no new checkpoints will be made, which is perfect for them since they don't check them anyway
fair enough, let's see how it plays out I don't know exactly what the cause is, as i wasn't there physically at your server to see what happened, it's just what everyone is saying and it's what the coin showed that checkpoints stopped happening so that was the alleged culprit that brought suspicion to the cause of the whole thing happening in the first place. i'm not blaming, i'm troubleshooting in a indirect way so we can all just understand what happened, why it happened, and what to do to correct it so it doesn't happen again, that's it, so we can move on , keep using this coin cause it's a good coin and i want to keep using it and see it flourish as many others do too. |
|
|
|
|
there's one way to get this sorted out.
get a hold of anothe reputable dev in the community that has no affiliation to you or any vested /biased interest of the outcome of this coin to look over the code and the situation, report his findings and end of story, no more discussion.
|
|
|
|
I'm done
bravo dude ... trying to help man...everyone was |
|
|
|
Sigh, I give up. None of you guys are listening and already have your minds made up. I've already told you a thousand times the same thing, I'm done with this conversation (All my blocks have checkpoints)
show it i don't speak for others, just me here like richie said, he will apologize if it's proven was in fact on his end. so far it hasn't been proven, i dont' see any evidence yet |
|
|
|
Are you kidding me?
NO! and you don't need to be Socratic either... if whatever happened that day wasn't you, then wtf EXACTLY happened when you restarted the checkpoint server, step by step, one by one what did you do? cause bittrex doesn't run a checkpoint server, only you do. and since we know if a checkpoint server stops working, that in itself DOES NOT CAUSE A FORK, it's what happens upon the method of the re-initiation that determines a fork or not happening... and the consequential rollback... I did nothing lol it fixed itself Ok... and it missed 1700 blocks because? I didn't miss 1700 blocks why were no checkpoints happening for that period of time |
|
|
|
Are you kidding me?
NO! and you don't need to be Socratic either... if whatever happened that day wasn't you, then wtf EXACTLY happened when you restarted the checkpoint server, step by step, one by one what did you do? cause bittrex doesn't run a checkpoint server, only you do. and since we know if a checkpoint server stops working, that in itself DOES NOT CAUSE A FORK, it's what happens upon the method of the re-initiation that determines a fork or not happening... and the consequential rollback... I did nothing lol it fixed itself Ok... and it missed 1700 blocks because? |
|
|
|
Are you kidding me?
NO! and you don't need to be Socratic either... if whatever happened that day wasn't you, then wtf EXACTLY happened when you restarted the checkpoint server, step by step, one by one what did you do? cause bittrex doesn't run a checkpoint server, only you do. and since we know if a checkpoint server stops working, that in itself DOES NOT CAUSE A FORK, it's what happens upon the method of the re-initiation that determines a fork or not happening... and the consequential rollback... |
|
|
|
Right, I made an error with loading a checkpoint server after doing this for four years. When you ask in a room full of long-time Bittrex shills, what other answer do you expect?
Their blocks did not have checkpoints, they have a fundamental misunderstanding of the situation. As of this post.. I'm washing my hands of Bittrex
And SO WHAT MAN, if you made an error big fucking deal, why you gotta fight it ? huh? take ur ego down, look over everything, nobody is fighting with you, just you with yourself on this. you saw richie said he's got nothing against you, he just did his thing cause smth happened with the blockchain after the checkpoint server was restarted, and wanted to make sure his books are in order. wtf you gotta be so belligerent about this. and not only that seems checkpoints aren't even needed anymore according tho that conversation. so you could just change the code and get rid of it all together, end of story. fuck man, this shit's gotta end like today. when gregofdoom https://bitcointalk.org/index.php?topic=1211692.msg14903311#msg14903311 posted that first time when the checkpoint was behind 500 blocks, look at wat you replied to that post dude... ""Yea, I'm resyncing all my nodes to try reproducing the fork right now."" like hello... |
|
|
|
|
d3m0nkings [12:48 AM]
but richie technically speaking conclusion here is the coin actually didn't have a problem with it's code, it's just watever reason the checkpoint server stopped, (power failure, or w.e.)
[12:48]
and spot's method of restarting it
[12:48]
so it wasn't code just human error
[12:48]
possibly
fuzzyhobbit BOT [12:48 AM]
I would call it mismanagement of the checkpointing server
d3m0nkings [12:49 AM]
ya
Wuher BOT [12:49 AM]
well, it's not a coin issue, it's a blockchain issue
d3m0nkings [12:49 AM]
that's all
bittrex-richie [12:49 AM]
wuher: thats crap ;( ... lebron puts up 25-30 pts, 8 boards, 8 assists consistently
Wuher BOT [12:49 AM]
which resulted from mismanagement of the checkpoint server
bittrex-richie [12:49 AM]
agreed with fuzzy/wuher.... what it isn't is the exchanges fault :wink:
Wuher BOT [12:49 AM]
@bittrex-richie: 18 points this game I think? did you see all those missed easy layups/dunks in the 3-4 quarter?
d3m0nkings [12:49 AM]
right but the blockchain issue was the resault of human error
Wuher BOT [12:49 AM]
and missed foul shots in the last 3 minutes..
gritt-n-auld [12:50 AM]
Yes, human error of the one managing the checkpoint server.
|
|
|
|
|
Show Posts
