[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS

[MalReynolds]

For what it's worth, it looks like there are at least 12 Top Delegates in the "101 Club" that are not currently forging:

UPTIME     DELEGATE

72.78%   Altocumulus
72.78%   Altostratus
84.69%   Stratocumulus
84.47%   Stratus
56.18%   foundation10
56.60%   foundation9
85.38%   MatthewDC_D1
85.07%   MatthewDC_D8
12.79%   stasDelegate1
12.63%   stasDelegate4
75.38%   landgraf.paul
53.15%   Wulfcastle

This list may be longer, but if so, it's among members whose total uptime is over 85%.

[Litoshi]

For what it's worth, it looks like there are at least 12 Top Delegates in the "101 Club" that are not currently forging:

UPTIME     DELEGATE

72.78%   Altocumulus
72.78%   Altostratus
84.69%   Stratocumulus
84.47%   Stratus
56.18%   foundation10
56.60%   foundation9
85.38%   MatthewDC_D1
85.07%   MatthewDC_D8
12.79%   stasDelegate1
12.63%   stasDelegate4
75.38%   landgraf.paul
53.15%   Wulfcastle

This list may be longer, but if so, it's among members whose total uptime is over 85%.

For what it is worth, I noticed that my delegate, hosted on Vultr, is only hitting about 75% since the 030 update.  My uptime has gone down slowly, as I hit an average of 3 forgings per hour and miss one.

[MalReynolds]

For what it is worth, I noticed that my delegate, hosted on Vultr, is only hitting about 75% since the 030 update.  My uptime has gone down slowly, as I hit an average of 3 forgings per hour and miss one.

That's interesting, because the list I posted above is based on servers that I see have their uptime going down slowly too.   Maybe they ARE online forging but are occasionally missing their turn too.  I'll let it percolate for a day or so and recheck.

In any event, it looks like it's worth verifying 0.3.0 isn't causing an upswing in missed forgings because of tighter timings.

[starik69]

New POT fail?

Death Note fan?

Again false assumptions? 
Never saw it

[imd1]

On my 0.2.0 delegate node when I click on 'Stop Forging' button it asks for a password, entering my delegate passphrase there gives me 'Access denied' error ? I'm not able to stop my delegate and update it to 0.3.0 version.

Please help.

[Passion_ltc]

On my 0.2.0 delegate node when I click on 'Stop Forging' button it asks for a password, entering my delegate passphrase there gives me 'Access denied' error ? I'm not able to stop my delegate and update it to 0.3.0 version.

Please help.

Just close the client, install v0.3.0 and start forging there.

For what it's worth, it looks like there are at least 12 Top Delegates in the "101 Club" that are not currently forging:

UPTIME     DELEGATE

72.78%   Altocumulus
72.78%   Altostratus
84.69%   Stratocumulus
84.47%   Stratus
56.18%   foundation10
56.60%   foundation9
85.38%   MatthewDC_D1
85.07%   MatthewDC_D8
12.79%   stasDelegate1
12.63%   stasDelegate4
75.38%   landgraf.paul
53.15%   Wulfcastle

This list may be longer, but if so, it's among members whose total uptime is over 85%.

For what it is worth, I noticed that my delegate, hosted on Vultr, is only hitting about 75% since the 030 update.  My uptime has gone down slowly, as I hit an average of 3 forgings per hour and miss one.

Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.

[MalReynolds]

On my 0.2.0 delegate node when I click on 'Stop Forging' button it asks for a password, entering my delegate passphrase there gives me 'Access denied' error ? I'm not able to stop my delegate and update it to 0.3.0 version.

Please help.

Go to your server, stop the 0.2.0a program / process, copy the blockchain over to the 0.3.0 folder, go to the 0.3.0 folder, mod the config.json text file with your forging account password, and start the 0.3.0 program/process.

Don't worry about gracefully doing a controlled transfer between the two versions.  Just kill the old job and start the new job.

[MalReynolds]

Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.

Your uptime SHOULD go up "a bit" over a period of a few days, right?  And asymptotically approach 99.99%.

My question is, how do you know if you've missed a forge you were supposed to do in a cycle of 101 blocks?

[Passion_ltc]

Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.

Your uptime SHOULD go up "a bit" over a period of a few days, right?  And asymptotically approach 99.99%.

My question is, how do you know if you've missed a forge you were supposed to do in a cycle of 101 blocks?

Yes. You can check in the forging center if you forged the block or missed it. The interval of your forged blocks should always be between 0 and 101 (1 and 100).

[MalReynolds]

Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.

Your uptime SHOULD go up "a bit" over a period of a few days, right?  And asymptotically approach 99.99%.

My question is, how do you know if you've missed a forge you were supposed to do in a cycle of 101 blocks?

Yes. You can check in the forging center if you forged the block or missed it. The interval of your forged blocks should always be between 0 and 101 (1 and 100).

I've checked my data for the last eight hours and looks like I'm hitting 100%.  However, I think the actual "good" interval is not between 1 and 100 but instead between 1 and 200.  You could theoretically be the first forger in cycle A and the last forger in cycle B and there could be 200 blocks between those two turns.  A long stretch like this could also account for your "uptime" going down slightly during a two cycle period.  I will need to re-evaluate  my list of 12 printed above tomorrow when there is a longer period of time to examine.

[Passion_ltc]

Very strange, my uptime went a bit up in the last days. So I encountered the exact contrary phenomenon.

Your uptime SHOULD go up "a bit" over a period of a few days, right?  And asymptotically approach 99.99%.

My question is, how do you know if you've missed a forge you were supposed to do in a cycle of 101 blocks?

Yes. You can check in the forging center if you forged the block or missed it. The interval of your forged blocks should always be between 0 and 101 (1 and 100).

I've checked my data for the last eight hours and looks like I'm hitting 100%.  However, I think the actual "good" interval is not between 1 and 100 but instead between 1 and 200.  You could theoretically be the first forger in cycle A and the last forger in cycle B and there could be 200 blocks between those two turns.  A long stretch like this could also account for your "uptime" going down slightly during a two cycle period.  I will need to re-evaluate  my list of 12 printed above tomorrow when there is a longer period of time to examine.

You are right, sorry. Yesterday it was pretty late already.

[Azkhabar]

Hello community! I just went into Crypti and applied as a delegate, but I'd like to know what a delegate is expected to be (or to do) exactly?
In the meantime, I'm a native French speaker with a very good command of Italian too so if I can ever help for some translations just tell me!

[Karen98]

Does anyone know how much blocks does it take to transfer XCR to Poloniex? Transferred a test amount 15 minutes ago, so 90 blocks ago, and it still has not arrived.

[MalReynolds]

Does anyone know how much blocks does it take to transfer XCR to Poloniex? Transferred a test amount 15 minutes ago, so 90 blocks ago, and it still has not arrived.

Did your Crypti account balance actually go down by the amount you expected?

Look here: http://cryptichain.me/

Do you see your transaction?  If yes, then apparently Polo has yet to manually credit your account there.  If no, then your test transfer didn't work and you need to try again.  

[Karen98]

Yes, I see the transaction there.

It's a pity that while Crypti is one of the fastest coins with 10 sec block time the exchanges have to basically use pen & paper to complete it so the transaction is slower than BTC on the end. After 1,5 hours still nothing on Poloniex.

[crypti]

Yes, I see the transaction there.

It's a pity that while Crypti is one of the fastest coins with 10 sec block time the exchanges have to basically use pen & paper to complete it so the transaction is slower than BTC on the end. After 1,5 hours still nothing on Poloniex.

It's problem of poloniex, looks like something didn't work on their part.

[Karen98]

Well I have transferred 1000 XCR from my account to my Polo address, and then they have transferred it to another account thereafter. So They have received it, but it was not credired.

[Karen98]

http://cryptichain.me/ appears to be down now. I get "waiting for blocks" message for a long time.

[MalReynolds]

For what it's worth, it looks like there are at least 12 Top Delegates in the "101 Club" that are not currently forging:

UPTIME     DELEGATE

72.78%   Altocumulus
72.78%   Altostratus
84.69%   Stratocumulus
84.47%   Stratus
56.18%   foundation10
56.60%   foundation9
85.38%   MatthewDC_D1
85.07%   MatthewDC_D8
12.79%   stasDelegate1
12.63%   stasDelegate4
75.38%   landgraf.paul
53.15%   Wulfcastle

This list may be longer, but if so, it's among members whose total uptime is over 85%.

I was wrong, all of these are apparently forging OK.   I checked today and uptime on all of these are higher today that when I made the post above, even tho their uptimes declined over a short period of time (obviously less than two cycles) when I made my initial check yesterday.  Sorry for the confusion.

[Passion_ltc]

Well I have transferred 1000 XCR from my account to my Polo address, and then they have transferred it to another account thereafter. So They have received it, but it was not credired.

Once we have a higher market cap and steady volume I hope that more serious exchanges will accept XCR.

http://cryptichain.me/ appears to be down now. I get "waiting for blocks" message for a long time.

Olivier is moving cryptichain.me to a more powerful server. The move is done now and the explorer should work now.