Pages:
Author

Topic: Open Discussion: DigiCube - page 3. (Read 3002 times)

hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 13, 2016, 07:31:56 AM
#16
I'm syncing a new wallet without having downloaded the bootstrap. this is syncing from 0 right now and look at the checkpoint:


hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 13, 2016, 07:16:27 AM
#15
you folks are either extremely blind or extremely tricky,
the dev of cubes is a talented crypto con artist,
you don't need to dig the code, it's quite clear from his behavior pattern.
imho he's done with cube for now

I didn't say he's coming back. don't care either. coin works without him. maybe after some time, someone will jump on board and take over
full member
Activity: 231
Merit: 100
June 13, 2016, 02:02:05 AM
#14
Well. We just hope spots well be back ..  he said himself that he will focus from now on spots and prime. I regret not having sold my cube with the total value of it was 1 btc when it was on 330 satoshi.  Shocked
legendary
Activity: 1778
Merit: 1000
June 13, 2016, 01:26:33 AM
#13
Why would anyone want to rework a coin where that chimp owns half of the supply?
We should be happy that he still owns the coin - it shows that he will be back soon
hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 13, 2016, 01:10:05 AM
#12
Hi All
So whats happening with Bittrex  is the coin Getting back on or not.


it's still on there till the 15th for sure. but if you really want the answer to that ask them on slack.bittrex.com

or email their support.

I'm waiting to see also what will happen.
full member
Activity: 213
Merit: 100
June 13, 2016, 01:05:34 AM
#11
Hi All
So whats happening with Bittrex  is the coin Getting back on or not.
hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 13, 2016, 12:45:07 AM
#10
Why would anyone want to rework a coin where that chimp owns half of the supply?

Fork it and if i knew code find a way to make it so he just can't access the new chain to carry over his coins. or make some kind of verification system to allow access by verified individuals only.

It's code surely someone knows something that's possible.
sr. member
Activity: 365
Merit: 300
June 13, 2016, 12:35:57 AM
#9
Why would anyone want to rework a coin where that chimp owns half of the supply?
hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 13, 2016, 12:32:26 AM
#8
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.
sr. member
Activity: 365
Merit: 300
June 13, 2016, 12:28:10 AM
#7
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.
hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 13, 2016, 12:12:06 AM
#6
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

sr. member
Activity: 346
Merit: 250
June 12, 2016, 11:54:34 PM
#5
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?
hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 12, 2016, 11:00:01 PM
#4
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
legendary
Activity: 1778
Merit: 1000
June 12, 2016, 10:57:11 PM
#3
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.
hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 12, 2016, 09:01:27 PM
#2
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://bitcointalksearch.org/topic/m.15155126
------

...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!

hero member
Activity: 1638
Merit: 507
The snake which cannot cast its skin has to die
June 12, 2016, 08:57:18 PM
#1
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 !

Pages:
Jump to: