Topic: NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs - page 1269. (Read 2985503 times)

Did the 6 hour stuff to be able to do start delegated harvesting and when I click I get error 700 need 1000 xem.
I have more than 20 000 xem

Any idea ??

Thanks! I sort of figured, but was a bit unsure..

But I have another issue that might turn out as an embarrassement for me:

When using the testNEM account, I genertaed a real  NEM account and tooke great care to store the privkey and the pubkey.

Now the privkey opens another account, but the original account (I have listed right above my privkey) does exist and have the XEM in it.

Can this have gone wrong somehow?
 [I am not quite panicking yet, but would really like to find out]

what I have as privkey is a 64digit hex string with the e-f in small letters- this doesnt look like a passphrase to me.. 

was there any step involved that yields a 64 digit hex string with small letters?

wallet file stores your private keys encrypted. if you use a strong enough password for your wallet, like you would for nxt, no one will be able to hack it and take your coins. alternatively you can just import your private key each time you use the wallet but that wouldnt be as secure as just using a strong password for the wallet file imo. you cant use the private key with out creating a wallet file unless you use the API i guess.

When you replace "PASTE_YOUR_ACCOUNT_ADDRESS_HERE" with your account's address make sure to remove the dashes "-" from the address. No dashes No spaces.

Restarted NIS, now I get: the timestamp is too far in to the future. 

EDIT: retried, everything the same, now it "succeeded" and is waiting for a confirmation.

EDIT 2: **SUCCES** the transaction is in the blockchain.

Thank you very much, very helpful answer

sorry- I miss a few basic mechanics in a prominent place.

like- when I enter my passphrase for the first time, I have to enter a wallet name.

when I return, that name is listed in wallets on that computer. Elsewhere, I read s.t. about a wallet file.

Is that wallet file encrypted with the same passphrase as my account passphrase?

Can I disregard the wallet file and only use my passphrase? When the computer is lost/stolen, can anyone access my XEM somehow on the hard drvie?

I would prefer to operate with ONE passphrase onlly, so having two is  confusing- a bit like that annoying Bitcoin feature where the real privKey is carefully hidden, and only a passphrase to

an off-blockchain DB is supposed to be used....

And sry that I don't feel like browsing tutorials and forums for this info

Ah I see- when I 'export wallet' I get  a small zip file...

I had same problem earlier today. It seems one of the accounts are set to "unlocked" which means "harvesting" and now the GUI is not showing you any option to stop the account from harvesting "as you probably started harvesting with this account as LOCAL harvesting".

Now once your account turned active for delegate harvesting, you now have the option to start delicate harvesting but you don't have the option to stop local harvesting "as the GUI harvesting button been replace/switched to delegate".

If you wanna confirm that you indeed have one of your accounts unlocked/harvesting locally where you can't see that in the GUI, you can simply confirm that by performing the following steps:

- Open your browser
- Open this url: http://127.0.0.1:7890/account/status?address=PASTE_YOUR_ACCOUNT_ADDRESS_HERE
- Replace "PASTE_YOUR_ACCOUNT_ADDRESS_HERE" above with your account address
- You should receive a text/json response. Check the Status field. If it is set to locked the account is not harvesting, and if the status is set to unlocked so the account is harvesting.
- Do the same with all your accounts, you should find at least one account set to unlocked.

In my case I found one of my accounts status set to unlocked "though the GUI/client is not informing me about that nor allowing me an option to lock/stop local harvesting". So I wrote a python script around the lock api call, to lock the account. I can send you the script if you need it.

On the other hand an easy fast solution would be setting the maximum allowed number of harvesting accounts. You can set that in the configuration file: /nis/config.properties  the default value is 1, change it to 2 and restart NIS. That should fix your problem.

Feel free to PM me if you need more help.

enter one of the IP addresses in this post into "host" instead of localhost. then start delegated harvesting. its throwing the error cos you are already harvesting on your local nis and the limit is set to one. you may need to try more than one IP if the ones in the list already have the max harvestors.
https://forum.ournem.com/vps-nodes/list-of-dedicated-vps-nodes-to-conect-nem/msg15100/#msg15100

current block 3704
Try to restart NIS, maybe that helps.

Oh okay I see, thanks!

What does the "block difficulty" really mean? Does it depend on "how much importance" that is currently harvesting?

System time is correct and NIS says: "NIS is synchronized! (at block 3691)" at 21:13

Start =/= boot

If you let NCC open and stay logged into your wallet and then restart NIS, you have to boot it manually. Take a look in the menu on the top right (arrow down symbol) -> "Boot Local Node".

You are probably already harvesting locally on that node. Since 1 harvester is the default maximum you can't also delegate harvest on that node.

You don't necessarily need a remote hose to use delegated harvesting so localhost is fine.

I still cannot figure out delegated harvesting. I have followed the guide, but I don't know what to enter as "host" in the remote server menu. I have localhost by default but that brings up the error 699 maximum number of harvesters reached.

I have waited the 6 hours.

Is your NIS synced ?
Please check your system time and see if it's way off.

Yes, I do. The transaction never gets picked up by the blockchain.


The transaction never leaves my wallet, so there isn't anything Poloniex can do about that.

yes please show of some more of your great photoshop skillz

thanks ...

Did you do the Generate Message that is asked of you prior to the deposit? Its needed to identify your account so they know who is depositing.