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

[MalReynolds]

Check at the top right corner. There should be a circle loading with a percentage inside of it.

Nope.  No circle.  See for yourself:

http://104.156.254.157:8040

According to winscp, my blockchain.db is at 95MB and still slowly climbing.

Mal,

that Vultr address is a 512MB account. you need to upgrade to 45.63.6.XX:8040

BTW, that link only leads to the XCR wallet log on screen.  We cant see your node.  Also, you cant enable forging from a remote computer when on Vultr....... you must log on to Vultr and do it there.

I understand it's just a wallet, not my node that you would see.  But if the blockchain isn't loaded, isn't ANY wallet user logging in there supposed to see the spinning circle / percentage loading figure that apparently isn't there?

According to my server management page it is a 768MB server.  That's what I'm paying for.  Where do you see it's 512MB?

I understand that I have to engage forging locally by putting my forging account passcode into the config.json file in quotes and I have done so.  I still think that's not a secure process, which is why I keep my balance very low on this account, but anyway - I still don't see the low balance I know is in there even tho it is the correct forging account number I use.  So it is obviously a blockchain load issue.

SO...how big IS the blockchain right now?  

[1713531565]

1713531565

[1713531565]

1713531565

[1713531565]

1713531565

[Passion_ltc]

Check at the top right corner. There should be a circle loading with a percentage inside of it.

Nope.  No circle.  See for yourself:

http://104.156.254.157:8040

According to winscp, my blockchain.db is at 95MB and still slowly climbing.

Mal,

that Vultr address is a 512MB account. you need to upgrade to 45.63.6.XX:8040

BTW, that link only leads to the XCR wallet log on screen.  We cant see your node.  Also, you cant enable forging from a remote computer when on Vultr....... you must log on to Vultr and do it there.

I understand it's just a wallet, not my node that you would see.  But if the blockchain isn't loaded, isn't ANY wallet user logging in there supposed to see the spinning circle / percentage loading figure that apparently isn't there?

According to my server management page it is a 768MB server.  That's what I'm paying for.  Where do you see it's 512MB?

I understand that I have to engage forging locally by putting my forging account passcode into the config.json file in quotes and I have done so.  I still think that's not a secure process, which is why I keep my balance very low on this account, but anyway - I still don't see the low balance I know is in there even tho it is the correct forging account number I use.  So it is obviously a blockchain load issue.

SO...how big IS the blockchain right now?  

Please tell me the browser you are using. I see the circling image, check:



768MB is good.

The passphrase has to be saved somewhere in order to automatically start the forging. You can always start the node and start the forging by hand in the UI, but you have to do this all the time when you restart the client (which should be never).

But I will also always keep only small amounts on my delegate accounts.


The current blockchain size should be about 160MB.

[MalReynolds]

Please tell me the browser you are using. I see the circling image, check:

The current blockchain size should be about 160MB.

I don't see the spinning circle in Internet Explorer 11, I do see it in Chrome Version 43.  I'm still loading, currently at 153MB.

I seem to be up and running with a complete blockchain if I log in with Chrome.  However, on the forging page I see a floating "red button" in the upper right corner but there is no words near it like "stop forging".

With IE 11, I see nothing.

[Litoshi]

Mal,

have you tried loading the node on to your home computer, DL the blockchain.db and then copy it to your Vultr node?

[Passion_ltc]

Check at the top right corner. There should be a circle loading with a percentage inside of it.

Nope.  No circle.  See for yourself:

http://104.156.254.157:8040

According to winscp, my blockchain.db is at 95MB and still slowly climbing.

Mal,

that Vultr address is a 512MB account. you need to upgrade to 45.63.6.XX:8040

BTW, that link only leads to the XCR wallet log on screen.  We cant see your node.  Also, you cant enable forging from a remote computer when on Vultr....... you must log on to Vultr and do it there.

I understand it's just a wallet, not my node that you would see.  But if the blockchain isn't loaded, isn't ANY wallet user logging in there supposed to see the spinning circle / percentage loading figure that apparently isn't there?

According to my server management page it is a 768MB server.  That's what I'm paying for.  Where do you see it's 512MB?

I understand that I have to engage forging locally by putting my forging account passcode into the config.json file in quotes and I have done so.  I still think that's not a secure process, which is why I keep my balance very low on this account, but anyway - I still don't see the low balance I know is in there even tho it is the correct forging account number I use.  So it is obviously a blockchain load issue.

SO...how big IS the blockchain right now?  

Please tell me the browser you are using. I see the circling image, check:

The current blockchain size should be about 160MB.

I don't see the spinning circle in Internet Explorer 11, I do see it in Chrome Version 43.  I'm still loading, currently at 153MB.

Should be finished soon, just a few more MB and you are 100% synced. Internet Explorer has many issues with our user interface right now, will be fixed in v0.3.2.

Chrome should show it, strange. Can you check if there are JS errors on your page?

[MalReynolds]

Well, I'm definitely running an updated 0.3.0 node now but can't access its wallet with IE 11.    No JS errors that I can see. Chrome 43 works fine.  Just takes a long time to download that blockchain. 

Onward. 

[Passion_ltc]

Well, I'm definitely running an updated 0.3.0 node now but can't access its wallet with IE 11.    No JS errors that I can see. Chrome 43 works fine.  Just takes a long time to download that blockchain.  

Onward.  

Like I said. IE support will come with v0.3.2.

The next time you should copy your old blockchain file over to the new version. This will speed up the process.

[MalReynolds]

When will the blockchain explorer be back online?

http://live.crypti.me/

[Passion_ltc]

When will the blockchain explorer be back online?

http://live.crypti.me/

There was a very small bug, which made it impossible to continue the blockchain explorer. The bugs are fixed now, and Olivier should be able to put the site online tomorrow.

[starik69]

Is new version again a hard fork and incompatible with current network?

Litoshi mixed something up. The old v0.2.0er release is not compatible with the current version, as we introduced new features.

Oh, this always misleading me Litoshi!

I think it still syncs, but at some point you will probably land on a fork.

Can you tell what are exact conditions when 0.2 go fork with 0.3?

starik, it is also written on the blog post:

To all delegates: This update is mandatory! You have to update your nodes as soon as possible! Thank you.

So you have to update your nodes. 

Mandatory is not incompatible

[Passion_ltc]

Is new version again a hard fork and incompatible with current network?

Litoshi mixed something up. The old v0.2.0er release is not compatible with the current version, as we introduced new features.

Oh, this always misleading me Litoshi!

I think it still syncs, but at some point you will probably land on a fork.

Can you tell what are exact conditions when 0.2 go fork with 0.3?

starik, it is also written on the blog post:

To all delegates: This update is mandatory! You have to update your nodes as soon as possible! Thank you.

So you have to update your nodes. 

Mandatory is not incompatible

As soon as some user on the network made a v0.3.0 transaction, like registering a username or adding a contact. I did both already, so it should go on a fork. Mabye you are lucky and it doesn't happen, but better use v0.3.0.

[Litoshi]

Is new version again a hard fork and incompatible with current network?

Litoshi mixed something up. The old v0.2.0er release is not compatible with the current version, as we introduced new features.

Oh, this always misleading me Litoshi!

I think it still syncs, but at some point you will probably land on a fork.

Can you tell what are exact conditions when 0.2 go fork with 0.3?

starik, it is also written on the blog post:

To all delegates: This update is mandatory! You have to update your nodes as soon as possible! Thank you.

So you have to update your nodes. 

Mandatory is not incompatible

Eventually 020 will have to forge or confirm one of the new 030 functions, such as username registration, or adding a contact.  Once this happens, an 020 delegate will likely produce its own fork.

So, as long as you are not an active delegate, and dont make any transactions, your 020 full wallet will show the block chain and your balance.  

You be the judge of if this can be called compatable or not.

[starik69]

You be the judge of if this can be called compatable or not.

Going fork is incompatible
BTW, yesterday i successfully upgraded my delegate so don't vote for it
Oh, missed the moment i became L

[Passion_ltc]

You be the judge of if this can be called compatable or not.

Going fork is incompatible
BTW, yesterday i successfully upgraded my delegate so don't vote for it
Oh, missed the moment i became L

Death Note fan?

[Passion_ltc]

Cryptichain.me Online again

Great news, Olivier just fixed the blockchain explorer and therefore cryptichain.me is now online again. Have fun using it, I see many username registrations!

[jari76]

Hello, just a little complaint about the client, the Forging indicator that is also a button is not a clear way to make a button to start forging, it looks like  just a decorative indicator, not an actual button, it took me 2 days to realize i wasnt actually forging and that was in fact a button. Not exactly saying it is bad, just not very clear to simple guys like me

This is the button i'm talking about:

[jari76]

Cryptichain.me Online again

Great news, Olivier just fixed the blockchain explorer and therefore cryptichain.me is now online again. Have fun using it, I see many username registrations!

Awesome, nice to see it working again!

[Passion_ltc]

Hello, just a little complaint about the client, the Forging indicator that is also a button is not a clear way to make a button to start forging, it looks like  just a decorative indicator, not an actual button, it took me 2 days to realize i wasnt actually forging and that was in fact a button. Not exactly saying it is bad, just not very clear to simple guys like me

This is the button i'm talking about:

Hey Jari, thanks for your feedback. We encountered the problem ourselves. Therefore we will change it to a switch. We changed the design, however Vera still need to code it. It will come in a later version in the v0.3.0er branch.




As an advice from one delegate to another, you should set your passphrase in the config.json. If you client restarts, you will still forge this way. But to do this you should transfer nearly all XCR out of your delegate account for security reasons.

[jari76]

Hello, just a little complaint about the client, the Forging indicator that is also a button is not a clear way to make a button to start forging, it looks like  just a decorative indicator, not an actual button, it took me 2 days to realize i wasnt actually forging and that was in fact a button. Not exactly saying it is bad, just not very clear to simple guys like me

This is the button i'm talking about:

Hey Jari, thanks for your feedback. We encountered the problem ourselves. Therefore we will change it to a switch. We changed the design, however Vera still need to code it. It will come in a later version in the v0.3.0er branch.

http://i.cubeupload.com/bjlkkR.png


As an advice from one delegate to another, you should set your passphrase in the config.json. If you client restarts, you will still forge this way. But to do this you should transfer nearly all XCR out of your delegate account for security reasons.

Yes, it is configured that way, that's why i didnt check for a button, i expected it to automatically forge
New design for it is looking very good 

[Passion_ltc]

Hello, just a little complaint about the client, the Forging indicator that is also a button is not a clear way to make a button to start forging, it looks like  just a decorative indicator, not an actual button, it took me 2 days to realize i wasnt actually forging and that was in fact a button. Not exactly saying it is bad, just not very clear to simple guys like me

This is the button i'm talking about:

Hey Jari, thanks for your feedback. We encountered the problem ourselves. Therefore we will change it to a switch. We changed the design, however Vera still need to code it. It will come in a later version in the v0.3.0er branch.

http://i.cubeupload.com/bjlkkR.png


As an advice from one delegate to another, you should set your passphrase in the config.json. If you client restarts, you will still forge this way. But to do this you should transfer nearly all XCR out of your delegate account for security reasons.

Yes, it is configured that way, that's why i didnt check for a button, i expected it to automatically forge
New design for it is looking very good 

Strange, it should automatically start forge. Please try it again at a later version. Glad you like the switch, this will make things more clear.