Topic: [ANN][1CR] 1CRedit Coin Relaunch - page 5. (Read 290039 times)
Guys where mining????Mining there will not be????Not that there Pogozheva there are some children's games
This was a big let down. Stay away guys.
also, since you claim you've been working hard on the coin, why is there no development since years ago?
https://github.com/s4w3d0ff/1credit
take a look at commit dates, the last commit was to change 3 lines of code of constants, lol?
https://github.com/s4w3d0ff/1credit
take a look at commit dates, the last commit was to change 3 lines of code of constants, lol?
I reached out to the OP of this thread whom I believe to be Kevin N. Carpenter. (as according to his domain register info for http://www.1creditcoin.org/) Of course, I won't assume he owns or is responsible just because the domain info has his name on it, but it's a great place to start. It seems Mr Carpenter also owns http://www.carpenter-farms.us/ and a few other domains. Perhaps he is a small time crypto trader who tried to bring it back for legit reasons? Who knows. It seems he has long since abandoned 1cr however.
also, since you claim you've been working hard on the coin, why is there no development since years ago?
https://github.com/s4w3d0ff/1credit
take a look at commit dates, the last commit was to change 3 lines of code of constants, lol?
https://github.com/s4w3d0ff/1credit
take a look at commit dates, the last commit was to change 3 lines of code of constants, lol?
And now 1cr's 4th game they just posted a screenshot of:
https://twitter.com/LunyAndrew/status/789160260443312128
This is slightly amusing.
https://twitter.com/LunyAndrew/status/789160260443312128
This is slightly amusing.
yeah, this is becoming sad already...especially if they're saying they're the ones who developed the games?
Yea, it looks like their other attempt to make $$ failed. They also own 1stto.com which is a scam click tracking service. The signup link just redirects to a paypal checkout screen for $37.
There is a way to make free campaigns however, as I have found. http://1stto.com/fuckurscam1cr/
Thanks 1cr for my free campaign
And now 1cr's 4th game they just posted a screenshot of:
https://twitter.com/LunyAndrew/status/789160260443312128
This is slightly amusing.
https://twitter.com/LunyAndrew/status/789160260443312128
This is slightly amusing.
yeah, this is becoming sad already...especially if they're saying they're the ones who developed the games?
And now 1cr's 4th game they just posted a screenshot of:
https://twitter.com/LunyAndrew/status/789160260443312128
This is slightly amusing.
https://twitter.com/LunyAndrew/status/789160260443312128
This is slightly amusing.
Care to explain this 1cr?
The 2nd game you plan to release https://twitter.com/LunyAndrew/status/789128297607106560
and here's your 3rd game.
https://twitter.com/LunyAndrew/status/789132902537699328
So I guess you just buy all of your games from code canyon eh? So much for game devs.
The 2nd game you plan to release https://twitter.com/LunyAndrew/status/789128297607106560
and here's your 3rd game.
https://twitter.com/LunyAndrew/status/789132902537699328
So I guess you just buy all of your games from code canyon eh? So much for game devs.
Looks like a big flop coin, classic PND.
Care to explain this 1cr?
The 2nd game you plan to release https://twitter.com/LunyAndrew/status/789128297607106560
and here's your 3rd game.
https://twitter.com/LunyAndrew/status/789132902537699328
So I guess you just buy all of your games from code canyon eh? So much for game devs.
The 2nd game you plan to release https://twitter.com/LunyAndrew/status/789128297607106560
and here's your 3rd game.
https://twitter.com/LunyAndrew/status/789132902537699328
So I guess you just buy all of your games from code canyon eh? So much for game devs.
someone has just posted this on Poloniex trollbox, seems way too similar to the apparent 1CR game?
https://codecanyon.net/item/bionic-race-html5-running-game/18042591
and this twitter background image: https://twitter.com/1CreditOfficial
https://codecanyon.net/item/bionic-race-html5-running-game/18042591
and this twitter background image: https://twitter.com/1CreditOfficial
mining at the start?
Should be very interesting..
yes,I think it takes one week wait 
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
That'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.
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
Any ETA on the withdrawal/deposit issue on Poloniex? This might hurt 1CR's growth after the launch tomorrow.
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#L1334
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
https://github.com/s4w3d0ff/1credit/blob/master/src/main.cpp#L1334
Code:
unsigned 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
}
{
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
}
Code:
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
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
If anyone has problems with their wallet (node), you can follow this guide:
http://1cred.it/2016/10/18/possible-solutions-for-your-1cr-wallet-being-stuck/
http://1cred.it/2016/10/18/possible-solutions-for-your-1cr-wallet-being-stuck/
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.
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.
Blockchain moved again (briefly)
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.
Code:
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
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.
Jump to: