Pages:
Author

Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 69. (Read 804672 times)

hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
Is new version again a hard fork and incompatible with current network? Huh

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! Angry
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? Huh
starik, it is also written on the blog post:

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


Mandatory is not incompatible Roll Eyes

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.
hero member
Activity: 714
Merit: 500
Crypti Community Manager
Is new version again a hard fork and incompatible with current network? Huh

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! Angry
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? Huh
starik, it is also written on the blog post:

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


Mandatory is not incompatible Roll Eyes

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. Wink
legendary
Activity: 1367
Merit: 1000
Is new version again a hard fork and incompatible with current network? Huh

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! Angry
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? Huh
starik, it is also written on the blog post:

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


Mandatory is not incompatible Roll Eyes
hero member
Activity: 714
Merit: 500
Crypti Community Manager
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. Smiley
legendary
Activity: 938
Merit: 1000
When will the blockchain explorer be back online?

http://live.crypti.me/
hero member
Activity: 714
Merit: 500
Crypti Community Manager
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. Wink

The next time you should copy your old blockchain file over to the new version. This will speed up the process.
legendary
Activity: 938
Merit: 1000
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. 

hero member
Activity: 714
Merit: 500
Crypti Community Manager
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. Smiley

Chrome should show it, strange. Can you check if there are JS errors on your page?
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
Mal,

have you tried loading the node on to your home computer, DL the blockchain.db and then copy it to your Vultr node?
legendary
Activity: 938
Merit: 1000

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.

hero member
Activity: 714
Merit: 500
Crypti Community Manager
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. Smiley

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.
legendary
Activity: 938
Merit: 1000
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?  
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
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.
hero member
Activity: 700
Merit: 500
Member of the Crypti Foundation Board of Directors
Well, so much for Crypti being serviced by Coinomat.com for now.  There were a bunch of Dash and Doge votes in the last minutes so we ended up 4th place for their current voting cycle.  It would take about 2BTC or around $500 to tie with Doge for 3rd place in the next cycle, ignoring any additional votes.  

https://coinomat.com/coinvoting.php

I'm not convinced we need Coinomat, just like I am one of the people who thinks we should not be part of SuperNet. I am not fully convinced coinomat are supernet are completely legit, yet. I hold some SuperNet, but I hold a lot more XCR and I don't think XCR's success should hinge on the success of another cryptocurrency system.  If XCR delivers what it is supposed to, it can be a great success all on it own.

It would be nice to have been listed on Coinomat after DappStore Release, which is 0.5 version of Crypti. That means we have 3 month to gather necessary votes.

50 cent........ dont waste your money buying votes on Coinomat.  

Facts:  

1) Exchanges are established in order to make money, not as a public service

2) Fast way to make money is to charge for listing a coin, or to charge for vote$.

3) Encouraging competition between alt-coins desiring to be listed produces additional paid vote$

4) Shill voting produces even more additional paid votes by competing coins  (shill voting are votes by the exchange owners or proxies)

5) An alt-coin will be listed with or without votes when the exchange owners see that it is in their best interest.  Notice that heavy hyped coins get listed right away?  WHy?  Because it is profitable for the exchange owners (MaxCoin, Aurora)


Hitching our wagon to another alt-coin is very risky.  I equate it with being a rider on a motorcycle.  You have all the risk of the driver, but zero control.  We have already had experience with a partnership that went bad.  Fortunately, Corona didnt get very far.  We will be even more careful in the future.




legendary
Activity: 938
Merit: 1000
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.

hero member
Activity: 714
Merit: 500
Crypti Community Manager
I'm having some problems setting up my 0.3.0 "MalReynolds" delegate on Vultur.  I've got the 0.3.0 software installed and running on my server.  I can call it up over the internet via http://IP:8040 and log into my correct forging account.  However, it doesn't recognize that I am a delegate.  Next to the "Send" button is a half circle with "3%" inside of it.  THe half circle spun for one revolution and is now frozen.  My block chain seems to stop at 258650 and won't load higher.  When I go to the forging page, there is a button to "Register delegate" and no button to "Stop forging".  When I try to register the user name "MalReynolds01" for the account, the registration window freezes and does nothing for a very long time, until I cancel and log out.

Suggestions?

It seems it isn't syncing to the end. If you have the old blockchain from the old version you can use it. Else try to close the client, delete the blockchain.db and start it again. Then it will sync again from scratch, should be working.

Also, how many MB does your client have? While testing we saw, that 512MB are not enough anymore. This will likely change again in the future, but right now we recommend to have 768MB minimum. Smiley

i got the same problem when i upgrade my node.
and then i forever stop app.js   and then forever start app.js....and it works....start to sync again.
maybe it's just because the internet of your server is unstable

I have deleted blockchain.db and restarted app.js.  No client indication the blockchain is loading.  However, I am monitoring the files with the winscp program while I am running an active Putty session with the server.  I see the block chain size increasing with time - it is currently at 51MB and has taken 20-30 minutes to get there.  When I log into the server using http://IP:8040 I get the Crypti client and can log into my correct forging account.  But there is no indication the blockchain is loading and it shows frozen at block 19347.  I am going to leave it running and see if things change when the entire blockchain is uploaded.  How many MB is that currently? 

Bottom line, I seem to be running, the blockchain seems to be loading, but there is no indication of that in the client.  I'll let you know what happens.

Check at the top right corner. There should be a circle loading with a percentage inside of it.
legendary
Activity: 938
Merit: 1000
I'm having some problems setting up my 0.3.0 "MalReynolds" delegate on Vultur.  I've got the 0.3.0 software installed and running on my server.  I can call it up over the internet via http://IP:8040 and log into my correct forging account.  However, it doesn't recognize that I am a delegate.  Next to the "Send" button is a half circle with "3%" inside of it.  THe half circle spun for one revolution and is now frozen.  My block chain seems to stop at 258650 and won't load higher.  When I go to the forging page, there is a button to "Register delegate" and no button to "Stop forging".  When I try to register the user name "MalReynolds01" for the account, the registration window freezes and does nothing for a very long time, until I cancel and log out.

Suggestions?

It seems it isn't syncing to the end. If you have the old blockchain from the old version you can use it. Else try to close the client, delete the blockchain.db and start it again. Then it will sync again from scratch, should be working.

Also, how many MB does your client have? While testing we saw, that 512MB are not enough anymore. This will likely change again in the future, but right now we recommend to have 768MB minimum. Smiley

i got the same problem when i upgrade my node.
and then i forever stop app.js   and then forever start app.js....and it works....start to sync again.
maybe it's just because the internet of your server is unstable

I have deleted blockchain.db and restarted app.js.  No client indication the blockchain is loading.  However, I am monitoring the files with the winscp program while I am running an active Putty session with the server.  I see the block chain size increasing with time - it is currently at 51MB and has taken 20-30 minutes to get there.  When I log into the server using http://IP:8040 I get the Crypti client and can log into my correct forging account.  But there is no indication the blockchain is loading and it shows frozen at block 19347.  I am going to leave it running and see if things change when the entire blockchain is uploaded.  How many MB is that currently?  

Bottom line, I seem to be running, the blockchain seems to be loading, but there is no indication of that in the client.  I'll let you know what happens.
legendary
Activity: 1344
Merit: 1000
Well, so much for Crypti being serviced by Coinomat.com for now.  There were a bunch of Dash and Doge votes in the last minutes so we ended up 4th place for their current voting cycle.  It would take about 2BTC or around $500 to tie with Doge for 3rd place in the next cycle, ignoring any additional votes.  

https://coinomat.com/coinvoting.php

I'm not convinced we need Coinomat, just like I am one of the people who thinks we should not be part of SuperNet. I am not fully convinced coinomat are supernet are completely legit, yet. I hold some SuperNet, but I hold a lot more XCR and I don't think XCR's success should hinge on the success of another cryptocurrency system.  If XCR delivers what it is supposed to, it can be a great success all on it own.

It would be nice to have been listed on Coinomat after DappStore Release, which is 0.5 version of Crypti. That means we have 3 month to gather necessary votes.
hero member
Activity: 868
Merit: 1000
Well, so much for Crypti being serviced by Coinomat.com for now.  There were a bunch of Dash and Doge votes in the last minutes so we ended up 4th place for their current voting cycle.  It would take about 2BTC or around $500 to tie with Doge for 3rd place in the next cycle, ignoring any additional votes.  

https://coinomat.com/coinvoting.php

I'm not convinced we need Coinomat, just like I am one of the people who thinks we should not be part of SuperNet. I am not fully convinced coinomat are supernet are completely legit, yet. I hold some SuperNet, but I hold a lot more XCR and I don't think XCR's success should hinge on the success of another cryptocurrency system.  If XCR delivers what it is supposed to, it can be a great success all on it own.
full member
Activity: 157
Merit: 100
I'm having some problems setting up my 0.3.0 "MalReynolds" delegate on Vultur.  I've got the 0.3.0 software installed and running on my server.  I can call it up over the internet via http://IP:8040 and log into my correct forging account.  However, it doesn't recognize that I am a delegate.  Next to the "Send" button is a half circle with "3%" inside of it.  THe half circle spun for one revolution and is now frozen.  My block chain seems to stop at 258650 and won't load higher.  When I go to the forging page, there is a button to "Register delegate" and no button to "Stop forging".  When I try to register the user name "MalReynolds01" for the account, the registration window freezes and does nothing for a very long time, until I cancel and log out.

Suggestions?

It seems it isn't syncing to the end. If you have the old blockchain from the old version you can use it. Else try to close the client, delete the blockchain.db and start it again. Then it will sync again from scratch, should be working.

Also, how many MB does your client have? While testing we saw, that 512MB are not enough anymore. This will likely change again in the future, but right now we recommend to have 768MB minimum. Smiley

i got the same problem when i upgrade my node.
and then i forever stop app.js   and then forever start app.js....and it works....start to sync again.
maybe it's just because the internet of your server is unstable
Pages:
Jump to: