Topic: 💸  DigiCube  🔷  NOW ON RAWX (NEW MCXNOW)  💸  EARN 50K CUBE/WEEK WITH TWITTER! - page 122. (Read 460478 times)

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

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.

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

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.

bravo dude ... trying to help man...everyone was

I'm done

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

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 up until the reset to try replicating their fork, which was after they were already back on the main chain.. I could not do aka it was not broken)

why were no checkpoints happening for that period of time

I didn't miss 1700 blocks

Ok... and it missed 1700 blocks because?

I did nothing lol their node fixed itself

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

Are you kidding me?

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://bitcointalksearch.org/topic/m.14903311  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...

 

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

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.

d3m0nkings [12:38 AM] 
but it's possible to say it's not his fault for watever reason the server stopped doing checkpoints that could've machine error not human, it's just wat happened afterwards

[12:38] 
that's possible to be blamed on him

[12:38] 
but either way , this blaming thing doesn't get anywhere

bittrex-richie [12:38 AM] 
i got no blame for anyone

[12:38] 
i just can't afford to lose funds


Wuher BOT [12:38 AM] 
@d3m0nkings: it isn't that it stopped that is the issue

d3m0nkings [12:39 AM] 
it's the restart


Wuher BOT [12:39 AM] 
Well, it's how it was brought back onto the network afterwards

[12:39] 
which ​*is*​ human error

d3m0nkings [12:40 AM] 
ok then, so he just needs to say what really happened after that realization the server stopped

[12:40] 
admit to whatever occurred there and just move on

[12:40] 
and not do it again

bittrex-richie [12:40 AM] 
this isn't a punishment .. nor am i looking for an apology

[12:41] 
its a simple economics thing.. if i dont trust the coin, i'm removing it


fuzzyhobbit BOT [12:41 AM] 
none of that is really necessary, he just needs to help richie balance his spreadsheet

bittrex-richie [12:41 AM] 
it was .2 btc.. i didnt' care about it

bittrex-richie [12:20 AM] 
as was ccex

[12:20] 
so both your exchanges were on the same fork... and then it rolls back 1700 blocks


Wuher BOT [12:20 AM] 
fuzzyhobbit: yeah you can't do stuff like that.. you have to stop the checkpointing server, resync the chain separately, then bring it back up with a synced version

bittrex-richie [12:21 AM] 
d3m0nkings: just so you know.. fuzzy runs one of the most stable coins out there ... and wuher runs a major pool and deals with almost as many wallets as us

[12:21] 
if you really want to get it sorted out.. go find a dev.. any dev.. one that gets paid to code review coins

[12:21] 
and have them assess the situation


Wuher BOT [12:22 AM] 
Also, the reality is also that the checkpointing server, being that far behind, can't sync with the other fork either

[12:22] 
(it can't regain those blocks it 'missed')

bittrex-richie [12:22 AM] 
i'm sure we are right here... i dont know if spots is incompetant or just too proud to admit he made a mistake...

[12:22] 
before this i counted him as a very capable dev and i would go to for advice and sanity checks.

[12:22] 
and even now i have nothing against him... the coin itself has an issue.  i want it addrsesed.

[12:23] 
oh and one last point

[12:23] 
if his theory that checkpointing is so important

[12:23] 
and everyone is suppose to be checking it


fuzzyhobbit BOT [12:23 AM] 
ruby and blackcoin don't use it at all anymore

bittrex-richie [12:23 AM] 
```query primecoin getcheckpoint
{
    "synccheckpoint" : "86909ab2eaa81655d91176e51688ec93abe8bd63616a17143b818b789f778c78",
    "height" : 116389,
    "timestamp" : "2016-03-28 23:39:41 UTC"
}

```


fuzzyhobbit BOT [12:24 AM] 
and we are pure pos without the protection of pow

bittrex-richie [12:24 AM] 
the other spots coin i have on here hasn't been check pointed in 3 months?

[12:24] 
the checkpoint argument is stupid.

d3m0nkings [12:24 AM] 
ya and look at sprout coin nothing since last year

bittrex-richie [12:24 AM] 
if the wallet has an issue with it, go into safe mode.

[12:24] 
there is no reason i'm checking when the last block checkpointed.

[12:24] 
fuzzy, you stopped using a checkpoint server?


fuzzyhobbit BOT [12:25 AM] 
yep

bittrex-richie [12:25 AM] 
didn't know that..


Wuher BOT [12:25 AM] 
it's just an attach vector


fuzzyhobbit BOT [12:25 AM] 
it's not necessary anymore if you change a few other things


Wuher BOT [12:25 AM] 
*attack

bittrex-richie [12:25 AM] 
yeah.. i hate cp servers...


fuzzyhobbit BOT [12:25 AM] 
and have proper distribution

bittrex-richie [12:25 AM] 
might as well run a DB

d3m0nkings [12:26 AM] 
ok well , richie, point is if SPOTS gets this corrected, then the exchange will consider keeping the on board?

[12:26] 
coin*


fuzzyhobbit BOT [12:27 AM] 
https://github.com/rubycoinorg/rubycoin/commit/dfe3595991364593b1f069bf7916fff591369d28

bittrex-richie [12:27 AM] 
doubtful... i tried to be civil about it


fuzzyhobbit BOT [12:27 AM] 
https://github.com/rubycoinorg/rubycoin/commit/7a35f1d6b60d4b05540597c3b807ca2dbf1e13fb

bittrex-richie [12:27 AM] 
if it wasn't for privacy reasons, i'd show you the thread we had.

d3m0nkings [12:27 AM] 
ya it's alright

bittrex-richie [12:27 AM] 
fuzzy, nod.. didn't realize you did that.

[12:28] 
d3m0nkings: if we are at fault here, i woudl haveno problem owning up to it

[12:28] 
if you can find me a credible dev that said we did somethin gwrong, i'm happy to apologize....

[12:28] 
but i've checked this with numerous devs and other individuals.. i dont see how a chain rolling back is our fault

d3m0nkings [12:28 AM] 
lol if i could i'd get gavin to assess it lol


Wuher BOT [12:28 AM] 
gavin would likely be a poor source for verification of that

d3m0nkings [12:29 AM] 
why

bittrex-richie [12:29 AM] 
there are a lot of credible devs in here.. .


fuzzyhobbit BOT [12:29 AM] 
a large part of being able to remove the checkpointing server is to remove coin-age(https://github.com/rubycoinorg/rubycoin/commit/2aa720c58eedc7d06ad3bd93184d1b4e06a1a735) so that the staking closer resembles a random lottery


Wuher BOT [12:29 AM] 
He has more limited experience with non-bitcoin coins than many other people.

d3m0nkings [12:29 AM] 
so have them check it then


Wuher BOT [12:29 AM] 
Checkpointing servers aren't used in bitcoin.

bittrex-richie [12:29 AM] 
earlz does code reviews and writes excellent shit.. fuzzy runs a successful coin... gritt-n-auld ran blackcoin... syntaks runs more coins than i cna count....

d3m0nkings [12:29 AM] 
show the result f of their analysis


Wuher BOT [12:29 AM] 
@d3m0nkings: I haven't heard a single person supporting the other side of your argument

bittrex-richie [12:29 AM] 
infernoman runs tx and some other stuf..  jyap runs jbs..

[12:30] 
the list goes on and on

pulseproject [12:30 AM] 
Hello

bittrex-richie [12:30 AM] 
go do your own research.

[12:30] 
and then theres pulse :wink:

gritt-n-auld [12:30 AM] 
I heard my phone bing

bittrex-richie [12:30 AM] 
grin..

[12:30] 
go back to bed dude

pulseproject [12:30 AM] 
Everyone has a healthy Pulse here ?

[12:30] 
we hope so!

gritt-n-auld [12:30 AM] 
I just got out of bed


Wuher BOT [12:31 AM] 
man, look at the juice @bittrex-richie has

bittrex-richie [12:31 AM] 
hhe you should read the thread we talked about the other day... it went super sideways hehe

bittrex-bill [12:31 AM] 
haha. we appreciate you showing up.  you're on richie's list of credible devs

bittrex-richie [12:31 AM] 
omg

[12:31] 
did anyone see the blocktalk thing with the cabbage devs?


Wuher BOT [12:31 AM] 
waking people up in the middle of the night with a single message.. with great power comes great responsibility richie

bittrex-richie [12:31 AM] 
its pure entertainment

[12:31] 
i didn't even @ tag him!

d3m0nkings [12:31 AM] 
ya the thing that doesn't line up, is if checkpoint server failed, then sprout coin should've forked after it stopped doing checkpoints

bittrex-richie [12:31 AM] 
thats not what happens


Wuher BOT [12:32 AM] 
@d3m0nkings: the fork occurs when you bring the checkpoint server back up afterwards

bittrex-richie [12:32 AM] 
if its on the wrong chain

[12:32] 
liek if it was staking


Wuher BOT [12:32 AM] 
(and/or in between, forks can occur if there's no checkpointing server, but that's not guaranteed to happen)

bittrex-richie [12:32 AM] 
it chooses its own staked block instead of what the network was doing the entire time it was offline.

[12:32] 
its all messy when it comes to checkpoint servers


Wuher BOT [12:32 AM] 
and yes, it's only most likely to happen when the checkpointing server is staking

bittrex-richie [12:32 AM] 
https://www.youtube.com/watch?v=CBaaOyI1hhE&feature=youtu.be&t=2170
 YouTube #Blocktalk
#Blocktalk - Cabbage Tech Team
 


fuzzyhobbit BOT [12:32 AM] 
if a staking node also had the checkpoint private key, it could have rolled back to virtually anywhere it wanted (maybe a hard-coded checkpoint would stop it)
=================================================


So SPOTS.....

make it happen....