almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
October 17, 2016, 08:46:19 AM |
|
Very possible I am just not understanding some basic thing about mining or am otherwise generally confused. Every PoW coin I've ever mined assigns a brand new address for every block it creates (following the broad "new transaction, new address" rule). It's very unusual to see two or more different PoW block rewards being credited to the same address. It does show that apparently the one miner created hundreds of blocks in a row, which in a fair and normal running network seems unlikely.
|
|
|
|
KindHearted
Newbie
Offline
Activity: 61
Merit: 0
|
|
October 17, 2016, 02:41:36 PM |
|
Somebody over here knowing until approx. when the 1CR blockchain is still stuck ?? When will the 1CR blockchain resume again?
A good estimate, even based on past occurences would be greatly appreciated.
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
October 17, 2016, 02:49:09 PM |
|
Somebody over here knowing until approx. when the 1CR blockchain is still stuck ?? When will the 1CR blockchain resume again?
A good estimate, even based on past occurences would be greatly appreciated.
It's been about 4 days so probably fairly soon, but see recent messages about some serious blockchain manipulation. If you're sending or receiving 1CR then it should still get through - the sending wallet will retry if the chain reorganises and the transaction disappears - but trying to mine will probably be a waste of time.
|
|
|
|
KindHearted
Newbie
Offline
Activity: 61
Merit: 0
|
|
October 17, 2016, 04:31:43 PM |
|
Hello almightyruler,
Is somebody even working on fixing the 1CR blockchain stuck issue, so that it won't happen in future anymore?
Somebody needs to remove the difficulty algo which is utter CRAP and completely REWRITE it from scratch. Perferably a team of devs with enough knowledge and experience, who know what they are actually doing.
Any chances this will happen ?? At least the new group supporting 1CR should publish some info about the steps and measures taken, to fix the blockchain, rather than ignoring the topic as if there was no problem at all. The users have a right to know. Otherwise people will lose confidence in the coin at some point, but maybe that's too difficult to understand for them.
|
|
|
|
dnaleor
Legendary
Offline
Activity: 1470
Merit: 1000
Want privacy? Use Monero!
|
|
October 17, 2016, 06:07:01 PM |
|
Hello almightyruler,
Is somebody even working on fixing the 1CR blockchain stuck issue, so that it won't happen in future anymore?
Somebody needs to remove the difficulty algo which is utter CRAP and completely REWRITE it from scratch. Perferably a team of devs with enough knowledge and experience, who know what they are actually doing.
Any chances this will happen ?? At least the new group supporting 1CR should publish some info about the steps and measures taken, to fix the blockchain, rather than ignoring the topic as if there was no problem at all. The users have a right to know. Otherwise people will lose confidence in the coin at some point, but maybe that's too difficult to understand for them.
I am looking into it. Could take weeks or months. I am not an experienced coin dev. If anyone who has experience with this knows a "quick fix", please contact me. But the only long term solution I see is adopting a CPU friendly algo. And maybe change the difficulty algo as well.
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
October 18, 2016, 12:14:40 AM |
|
Blockchain moved again (briefly) 13-Oct-2016 16:05:42 UTC+0 height: 60710 difficulty: 4189.79652439 tx: 1 17-Oct-2016 18:19:11 UTC+0 height: 60711 difficulty: 5407.41186158 tx: 6 17-Oct-2016 18:19:43 UTC+0 height: 60712 difficulty: 5.03686162 tx: 1 17-Oct-2016 18:19:45 UTC+0 height: 60713 difficulty: 0.33615277 tx: 1 17-Oct-2016 18:19:46 UTC+0 height: 60714 difficulty: 0.02229077 tx: 1 17-Oct-2016 18:19:47 UTC+0 height: 60715 difficulty: 0.00147649 tx: 1 17-Oct-2016 18:19:49 UTC+0 height: 60716 difficulty: 0.00024414 tx: 1 17-Oct-2016 18:19:49 UTC+0 height: 60717 difficulty: 0.00024414 tx: 1 17-Oct-2016 18:19:50 UTC+0 height: 60718 difficulty: 0.07403596 tx: 1 17-Oct-2016 18:19:50 UTC+0 height: 60719 difficulty: 0.40130185 tx: 1 17-Oct-2016 18:19:51 UTC+0 height: 60720 difficulty: 0.56167882 tx: 1 17-Oct-2016 18:19:52 UTC+0 height: 60721 difficulty: 0.56175586 tx: 1 17-Oct-2016 18:19:53 UTC+0 height: 60722 difficulty: 0.56448001 tx: 1 17-Oct-2016 18:19:54 UTC+0 height: 60723 difficulty: 0.76363319 tx: 1 17-Oct-2016 18:19:54 UTC+0 height: 60724 difficulty: 1.21825854 tx: 1 17-Oct-2016 18:19:55 UTC+0 height: 60725 difficulty: 267.33635031 tx: 1 17-Oct-2016 18:20:00 UTC+0 height: 60726 difficulty: 503.88827151 tx: 1 17-Oct-2016 18:20:47 UTC+0 height: 60727 difficulty: 373.26095179 tx: 1 17-Oct-2016 18:20:57 UTC+0 height: 60728 difficulty: 80.16015825 tx: 1 17-Oct-2016 18:21:09 UTC+0 height: 60729 difficulty: 99.92888158 tx: 1 17-Oct-2016 18:21:11 UTC+0 height: 60730 difficulty: 154.77471493 tx: 1 17-Oct-2016 18:21:35 UTC+0 height: 60731 difficulty: 379.66371721 tx: 1 17-Oct-2016 18:30:55 UTC+0 height: 60732 difficulty: 6274.93120064 tx: 2 17-Oct-2016 18:31:01 UTC+0 height: 60733 difficulty: 1052.25857586 tx: 1 17-Oct-2016 18:33:27 UTC+0 height: 60734 difficulty: 1155.35036566 tx: 1 17-Oct-2016 18:33:40 UTC+0 height: 60735 difficulty: 1190.01224674 tx: 1 17-Oct-2016 18:36:05 UTC+0 height: 60736 difficulty: 1248.70598538 tx: 1 17-Oct-2016 18:44:01 UTC+0 height: 60737 difficulty: 1609.7699944 tx: 1 17-Oct-2016 18:44:38 UTC+0 height: 60738 difficulty: 1032.9353399 tx: 1 17-Oct-2016 18:45:17 UTC+0 height: 60739 difficulty: 1494.90736931 tx: 1 17-Oct-2016 18:46:11 UTC+0 height: 60740 difficulty: 6470.83726564 tx: 1
Flurry of low diff blocks for 44 seconds after the "stalled" block was solved, then the diff rapidly rose again. Note that block 60732 (diff 6274.93120064) was solved in about 9 minutes.
|
|
|
|
almightyruler
Legendary
Offline
Activity: 2268
Merit: 1092
|
|
October 18, 2016, 12:19:57 AM |
|
I am looking into it. Could take weeks or months. I am not an experienced coin dev. If anyone who has experience with this knows a "quick fix", please contact me.
A quick fix would be to change the difficulty algo to something besides KGW, but if there really is significant hash power working on this coin (even briefly, if a pool switches in) it would probably still be susceptible to massive difficulty swings. The price rising on polo probably hasn't helped, since a lot more people are suddenly interested in mining this coin.
|
|
|
|
dnaleor
Legendary
Offline
Activity: 1470
Merit: 1000
Want privacy? Use Monero!
|
|
October 18, 2016, 10:21:06 AM |
|
|
|
|
|
s4w3d0ff
Sr. Member
Offline
Activity: 322
Merit: 250
Spray and Pray
|
|
October 19, 2016, 10:52:26 PM |
|
Assuming that the 'KimotoGravityWellTW' function is doing what it is supposed to (1 hour min, about 6 days max(or 1 day max? I'm not really sure, either way, the diff is going to be hell)): https://github.com/s4w3d0ff/1credit/blob/master/src/main.cpp#L1334unsigned int static GetNextWorkRequired(const CBlockIndex* pindexLast, const CBlockHeader *pblock) { static const int64 BlocksTargetSpacing = TargetSpacing; static const unsigned int TimeDaySeconds = 60 * 60 * 24; int64 PastSecondsMin = TimeDaySeconds * 0.01; int64 PastSecondsMax = TimeDaySeconds * 0.14; uint64 PastBlocksMin = PastSecondsMin / BlocksTargetSpacing; uint64 PastBlocksMax = PastSecondsMax / BlocksTargetSpacing;
if (pindexLast->nHeight <= FIRST_KGW_BLOCK) { return OldGetNextWorkRequired(pindexLast, pblock); } if (pindexLast->nHeight <= FIRST_KGWTW_BLOCK) { return KimotoGravityWell(pindexLast, pblock, BlocksTargetSpacing, PastBlocksMin, PastBlocksMax); } if (pindexLast->nHeight < FIRST_KGWMB_BLOCK) { return KimotoGravityWellTW(pindexLast, pblock, BlocksTargetSpacing, 7, 168); // 1 hour min, 1 day max } return KimotoGravityWellTW(pindexLast, pblock, BlocksTargetSpacing, 7, 1024); // 1 hour min, about 6 days max } if (pindexLast->nHeight < FIRST_KGWMB_BLOCK) { return KimotoGravityWellTW(pindexLast, pblock, BlocksTargetSpacing, 7, 168); // 1 hour min, 1 day max } return KimotoGravityWellTW(pindexLast, pblock, BlocksTargetSpacing, 7, 1024); // 1 hour min, about 6 days max
Then one can assume that a large miner could jump in at a low diff, starting with a small amount of hashing power then exponentially (and quickly) increase the power until the difficulty goes through the roof. Then the miner exits the network (or lowers the hash power to a minimal) until the high diff block gets solved and the diff goes super low, repeat. Not sure if this is malicious, probably just a profit switching pool (or a troll, but is there a difference?), but the miner with massive power could double spend if they wanted (if they haven't already). You could try a simple fix and adjust the parameters above and try to reduce the damage from profit pools, but if it is a troll, adjusting the above would probably do nothing. You would have have to do a major rewrite or push out a new coin. IMO, to 'quick fix', maybe start with adjusting the "1 hour min" to something higher or the max to something closer to 1 hour. Good luck! BTC:15D8VaZco22GTLVrFMAehXyif6EGf8GMYV
|
|
|
|
iHaveNoClue
Member
Offline
Activity: 85
Merit: 10
|
|
October 20, 2016, 01:07:55 AM |
|
Any ETA on the withdrawal/deposit issue on Poloniex? This might hurt 1CR's growth after the launch tomorrow.
|
|
|
|
bolivarcoin
|
|
October 20, 2016, 02:13:26 AM |
|
Any ETA on the withdrawal/deposit issue on Poloniex? This might hurt 1CR's growth after the launch tomorrow.
This is the answer i got from polo a couple of days ago Thank you for getting in touch.
The 1CR wallet is undergoing maintenance and unfortunately we do not have an ETA as for when it will be back up and running. Rest assured that we will attempt to resolve all wallet related issues as soon as possible.
We appreciate your patience regarding this matter.
Best regards,
Jerichk Poloniex Support
|
|
|
|
iHaveNoClue
Member
Offline
Activity: 85
Merit: 10
|
|
October 20, 2016, 03:02:12 AM |
|
Any ETA on the withdrawal/deposit issue on Poloniex? This might hurt 1CR's growth after the launch tomorrow.
This is the answer i got from polo a couple of days ago Thank you for getting in touch.
The 1CR wallet is undergoing maintenance and unfortunately we do not have an ETA as for when it will be back up and running. Rest assured that we will attempt to resolve all wallet related issues as soon as possible.
We appreciate your patience regarding this matter.
Best regards,
Jerichk Poloniex SupportThat's too bad. I wanted to play some games on the arcade tomorrow but looks like that isn't going to happen. Hope they fix it soon.
|
|
|
|
trannamtan
|
|
October 20, 2016, 06:07:54 AM |
|
yes,I think it takes one week wait
|
|
|
|
yaooke
Sr. Member
Offline
Activity: 280
Merit: 250
Vincit qui se vincit.
|
|
October 20, 2016, 01:14:11 PM |
|
Should be very interesting..
|
|
|
|
olkah
|
|
October 20, 2016, 01:15:51 PM |
|
mining at the start?
|
|
|
|
|
|
yaooke
Sr. Member
Offline
Activity: 280
Merit: 250
Vincit qui se vincit.
|
|
October 20, 2016, 05:19:27 PM |
|
Looks like a big flop coin, classic PND.
|
|
|
|
|
caffeine93
Newbie
Offline
Activity: 41
Merit: 0
|
|
October 20, 2016, 07:08:36 PM |
|
yeah, this is becoming sad already...especially if they're saying they're the ones who developed the games?
|
|
|
|
|