I have 20,000 NEM in the account and have been harvesting for several hours now. It still shows 0% chance to hit the next block.
The NIS message says: "WARNING your balance haven't vested yet, foraging does not make sense (org.nem.core.model.AccountImportance d)"
When will the account be vested?
Someone on irc said it is 24 hours Thanks. I will keep it running all the time. it doesn't need to be running all the time, after the NEM have been in your wallet for 24hrs you can start harvesting |
|
|
|
im only getting "no suitable peers found to sync with" ?
just got it too, someone else had this earlier tonight |
|
|
|
Taking a close look at transacions, I noticed something "strange". Can I receive 1 nem and who sent me the money pay 10 k nem?  TRansaction details:  Thanks You can set your own transaction fee, someone must have been testing the system. |
|
|
|
send me some pls. hook it up I wanna try sending and receiving
I sent you some awhile ago, did you get them? |
|
|
|
I love the client! Very nice design and great landing page.  Transactions work, 3 incoming and 3 outgoing.
When I click the Client Info, I get: "ERROR 306 Unexpected error occurred, sorry for this"
I installed jdk-8u5-windows-x64.exe, is that the right package?
Same here. From terminal: Jun 26, 2014 2:01:01 AM org.nem.ncc.controller.g cF
INFORMATION:
Jun 26, 2014 2:01:01 AM org.nem.ncc.connector.a isConnected
INFORMATION: Requesting NIS <http://localhost:7890/heartbeat>
Jun 26, 2014 2:01:01 AM org.nem.ncc.connector.a a
INFORMATION: Requesting NIS <http://localhost:7890/node/extended-info>
Jun 26, 2014 2:01:01 AM org.nem.ncc.controller.e a
INFORMATION: java.lang.ClassCastException: org.nem.ncc.view.NodeIdentity cannot be cast to org.nem.ncc.connector.Node
The only issue with the UI is the visibility of the account menu in the upper right, which stays out of scope on window dimensions < 1200px. However, this is just a minor thing and I'm so excited such a thing is the only one I can complain for now.  Did you start NIS and let it load before starting NCC? |
|
|
|
Is this a TEST-NET BlockChain, or is this the real NEM BlockChain ?
Test, these are play nem's And when comes the Real NEM I am not sure if they decided it |
|
|
|
Transactions work, 3 incoming and 3 outgoing.
When I click the Client Info, I get: "ERROR 306 Unexpected error occurred, sorry for this"
I installed jdk-8u5-windows-x64.exe, is that the right package?
come to our irc channel and we can help you #ournem |
|
|
|
Is this a TEST-NET BlockChain, or is this the real NEM BlockChain ?
Test, these are play nem's |
|
|
|
Its all good thanks, do i have to perform a "boot local node" every time i start the client?
I wasnt sure if the nodename was one i had to connect to or create myself! lol
if you mean after you shut everything down, then yes, but if you only shutdown NCC and leave NIS running then no |
|
|
|
|
From Jaguar0625:
"Guys, this is a slightly older version. Please wait a few hours for the official closed alpha version. Thanks!"
|
|
|
|
|
From Jaguar0625:
"Guys, this is a slightly older version. Please wait a few hours for the official closed alpha version. Thanks!"
|
|
|
|
Hello Nemsters! Just a quick update concerning the open alpha. We’re still on track for the 25th June 2014. However, the code is unlikely to be signed until at least next week (more information about code signing here: http://www.symantec.com/code-signing/java). Don’t panic; this only means the open alpha will not be one-click install immediately and will start with packages similar to the closed alpha. A small amount of manual work will be required to get up and running - but do not fear! Quite a few of us involved in the closed alpha have had no problems whatsoever and we are all happy to help out. A new thread will probably be opened on the NEM Forum for convenience, along with details of how to get involved. - The NEM Teammeans another wait? no, the open alpha will run tomorrow but it won't be a one click install, it will take a few simple steps to get it going. |
|
|
|
except my block count is not increasing in my getinfo... im getting headers, but not processing blocks.
[edit] and ffs have I done anything but embarrass myself in this thread? lol
you call it embarrassment i call it opportunity to poke fun at you  |
|
|
|
|
ok Billo is right, there is something wrong:
getmininginfo:
"blocks" : 13957,
"currentblocksize" : 143520,
"currentblocktx" : 999,
"difficulty" : 1.00000000,
"errors" : "This is a pre-release test build - use at your own risk - do not use for mining or merchant applications",
"genproclimit" : 1,
"networkhashps" : 59634,
"pooledtx" : 1002,
"testnet" : true,
"generate" : true,
"hashespersec" : 30957
then i am also seeing this:
Accept block header
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 14086 16725 16725 17725 0
OS 13958 NS 13958
Update: 13958 17725 16725 17725 1
Accepted block 13958
Accept block header
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 17725 17725 16725 17725 1
Update: 16725 16725 16725 17725 0
Update: 13958 17725 16725 17725 1
Update: 14086 16725 16725 17725 0
OS 13958 NS 13958
Update: 13958 17725 16725 17725 1
Accepted block 13958
Accept block header
Update: 17726 16726 16726 17726 0
Update: 16726 16726 16726 17726 0
Update: 17726 16726 16726 17726 0
Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Accept block header
Update: 17726 16726 16726 17726 0
Update: 16726 16726 16726 17726 0
Update: 13958 17726 16726 17726 1
Update: 14086 16726 16726 17726 0
OS 13958 NS 13958
Update: 17726 17726 16726 17726 1
Accepted block 17726
Accept block header
Update: 17727 16727 16727 17727 0
Update: 16727 16727 16727 17727 0
Update: 17727 16727 16727 17727 0
Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Accept block header
Update: 17727 16727 16727 17727 0
Update: 16727 16727 16727 17727 0
Update: 13958 17727 16727 17727 1
Update: 14086 16727 16727 17727 0
OS 13958 NS 13958
Update: 17727 17727 16727 17727 1
Accepted block 17727
|
|
|
|
my client seems stuck @ block 14022. Log looks clean but I noticed this in the console output: Warning: saved state too old. Fast forward sync may not be possible. Run Resync!!!
Does this mean I need to delete the blockchain and start over? Billo, look above and you will find the answer (to life the universe and everything). Peace my brother |
|
|
|
Output error:Warning: saved state too old. Fast forward sync may not be possible. Run Resync! log file https://mega.co.nz/#!Vpc21baJ!JO71UzypRkpNf2ikAgqk_ejWyVisNnoy4s6yttdlHLk |
|
|
|
I noticed that too today, I will see if i can fix that when i am able to get back to my computer |
|
|
|
|
Show Posts
