NEM (XEM) Official Thread - 100% New Code - Easy To Use APIs

[x13]

Well, I personally think that the real breakthrough will happen in 2017. 2016 is the year when more and more institutions and companies are getting to know about blockchain. 2017 and 2018 will be the years when they are going to work with the blockchain technology.

So Xem is mid/long term investment ?

YES, expect price to have several more runs this year as well ...

2016 is the year of Blockchain Tech!

[4emily]

I notice that harvesting starts automatically before the wallet is fully synced - I assume that's supposed to happen and isn't some sort of anomaly with my wallet. With other coins of course the usual rule is don't 'stake' etc before the wallet is fully synced, otherwise it'll 'gum up the works' - for want of the appropriate technical term 

[Sjacmur]

I read about supernode but I dont know why somebody want have one ?
I dont know difference with delegated harvested. And only some % fee from transaction ? nothing more profit than delegated harvested ? so what different what node somebody have ? I no have yet its theoritical ask because i dont read what difference is.
Its dont matter how many coins supernode have minimal is 3 000 000 coins but if somebody 10 000 000 its not different. I know it not like PoS but its not fair. So if somebody have 7 000 000 Xem so better is make 2 different supernodes than make one with 7 000 000 coins ? Its stupid for me sorry for opinion. Any exponeision ?


Edit: I dont have 7kk xem thats number was as example that better have more supernodes but one "bigger" I mean more coins.

[fragout]

I read about supernode but I dont know why somebody want have one ?
I dont know difference with delegated harvested. And only some % fee from transaction ? nothing more profit than delegated harvested ? so what different what node somebody have ? I no have yet its theoritical ask because i dont read what difference is.
Its dont matter how many coins supernode have minimal is 3 000 000 coins but if somebody 10 000 000 its not different. I know it not like PoS but its not fair. So if somebody have 7 000 000 Xem so better is make 2 different supernodes than make one with 7 000 000 coins ? Its stupid for me sorry for opinion. Any exponeision ?

They are regularly tested on their bandwidth, chain height, chain parts, computing power, version, ping, and responsiveness to make sure that they are performing to high standards. If they meet all these requirements, they are randomly given rewards.

And if you have 7mill, yes its better to make 2 nodes, but in different locations.

[rigel]

I read about supernode but I dont know why somebody want have one ?
I dont know difference with delegated harvested. And only some % fee from transaction ? nothing more profit than delegated harvested ? so what different what node somebody have ? I no have yet its theoritical ask because i dont read what difference is.
Its dont matter how many coins supernode have minimal is 3 000 000 coins but if somebody 10 000 000 its not different. I know it not like PoS but its not fair. So if somebody have 7 000 000 Xem so better is make 2 different supernodes than make one with 7 000 000 coins ? Its stupid for me sorry for opinion. Any exponeision ?

Soon supernodes rewarding program will start paying rich bonuses to supernodes owners.
The more supernodes you run, the more bonuses you will get.

[kennyP]

I can't get remote harvesting working for a few months now. Every time I boot NIS it stops after a few minutes. If I remove "nis.shouldAutoHarvestOnBoot = false" from the config my NIS will sync, but then when I try and start local harvesting on my remote node it throws an error
"ERROR 306 NIS: UNEXPECTED ERROR"

I was hoping the new version would fix this problem but it hasn't. I did a full uninstall of the old version before installing too. Does the account I use to boot my remote node need to have a positive NEM balance? It always worked until Dec 2015 with a zero balance, but did something change? Help!!

"local harvesting on my remote node"

it shouldnt allow you to start local harvesting when connected to a remote nis

the account you use to boot can been negative and should be, unless you boot it with a delegated harvesting key. for the health of the network its better to boot with a harvesting key(for account security), of which the originating account should have a positive balance.

you need a balance of at least 10k (vested) xem to harvest.

activate delegated harvesting with the account that has funds, then go to your nis config and set auto-boot on and use the delegated accounts private key as the boot key. the delegated account cannot be used to move funds so the coins cannot be stolen even if your remote nis is compromised and delegated key stolen.

in relation to harvestig with a zero balance, that should be impossible.

Thanks for the reply kod! What I did was use my laptop  to delegate my main account for harvesting on my VPS. I did that last year and have rarely used my laptop NEM since. On my VPS i used 'nis.shouldAutoHarvestOnBoot = true' and setup a NEM account with zero balance in the config file to use with 'nis.bootKey =xxxxxxxxxx'. This setup was working great for months and I harvested many blocks and reboots of the VPS caused no problem as NIS would start from a shortcut in startup folder

But then in Dec 2015 the NIS on my VPS just kept stopping. I tried re-installing and deleting the cache files (smaragda's tip) but nothing worksed, NIS always stops after a few minutes. Then I noticed that if I change 'nis.shouldAutoHarvestOnBoot' to false the NIS on my VPS will sync, but when I login with my account on the VPS (i.e. the account I use with 'nis.bootKey =xxxxxxxxxx' in the config) and try and start harvesting on the VPS manually by clicking the harvesting button in the GUI I get the error "ERROR 306 NIS: UNEXPECTED ERROR".

I gave up and decided to wait for a new version, but I tried yesterday and NEM Beta 0.6.74 is doing the exact same behavior.

any love for kenny on this one?

[patmast3r]

I can't get remote harvesting working for a few months now. Every time I boot NIS it stops after a few minutes. If I remove "nis.shouldAutoHarvestOnBoot = false" from the config my NIS will sync, but then when I try and start local harvesting on my remote node it throws an error
"ERROR 306 NIS: UNEXPECTED ERROR"

I was hoping the new version would fix this problem but it hasn't. I did a full uninstall of the old version before installing too. Does the account I use to boot my remote node need to have a positive NEM balance? It always worked until Dec 2015 with a zero balance, but did something change? Help!!

"local harvesting on my remote node"

it shouldnt allow you to start local harvesting when connected to a remote nis

the account you use to boot can been negative and should be, unless you boot it with a delegated harvesting key. for the health of the network its better to boot with a harvesting key(for account security), of which the originating account should have a positive balance.

you need a balance of at least 10k (vested) xem to harvest.

activate delegated harvesting with the account that has funds, then go to your nis config and set auto-boot on and use the delegated accounts private key as the boot key. the delegated account cannot be used to move funds so the coins cannot be stolen even if your remote nis is compromised and delegated key stolen.

in relation to harvestig with a zero balance, that should be impossible.

Thanks for the reply kod! What I did was use my laptop  to delegate my main account for harvesting on my VPS. I did that last year and have rarely used my laptop NEM since. On my VPS i used 'nis.shouldAutoHarvestOnBoot = true' and setup a NEM account with zero balance in the config file to use with 'nis.bootKey =xxxxxxxxxx'. This setup was working great for months and I harvested many blocks and reboots of the VPS caused no problem as NIS would start from a shortcut in startup folder

But then in Dec 2015 the NIS on my VPS just kept stopping. I tried re-installing and deleting the cache files (smaragda's tip) but nothing worksed, NIS always stops after a few minutes. Then I noticed that if I change 'nis.shouldAutoHarvestOnBoot' to false the NIS on my VPS will sync, but when I login with my account on the VPS (i.e. the account I use with 'nis.bootKey =xxxxxxxxxx' in the config) and try and start harvesting on the VPS manually by clicking the harvesting button in the GUI I get the error "ERROR 306 NIS: UNEXPECTED ERROR".

I gave up and decided to wait for a new version, but I tried yesterday and NEM Beta 0.6.74 is doing the exact same behavior.

any love for kenny on this one?

You're gonna need to provide logs. Also head over to forum.nem.io and look at the Request for help category. You'll find some more things to try there.

[kennyP]

I can't get remote harvesting working for a few months now. Every time I boot NIS it stops after a few minutes. If I remove "nis.shouldAutoHarvestOnBoot = false" from the config my NIS will sync, but then when I try and start local harvesting on my remote node it throws an error
"ERROR 306 NIS: UNEXPECTED ERROR"

I was hoping the new version would fix this problem but it hasn't. I did a full uninstall of the old version before installing too. Does the account I use to boot my remote node need to have a positive NEM balance? It always worked until Dec 2015 with a zero balance, but did something change? Help!!

"local harvesting on my remote node"

it shouldnt allow you to start local harvesting when connected to a remote nis

the account you use to boot can been negative and should be, unless you boot it with a delegated harvesting key. for the health of the network its better to boot with a harvesting key(for account security), of which the originating account should have a positive balance.

you need a balance of at least 10k (vested) xem to harvest.

activate delegated harvesting with the account that has funds, then go to your nis config and set auto-boot on and use the delegated accounts private key as the boot key. the delegated account cannot be used to move funds so the coins cannot be stolen even if your remote nis is compromised and delegated key stolen.

in relation to harvestig with a zero balance, that should be impossible.

Thanks for the reply kod! What I did was use my laptop  to delegate my main account for harvesting on my VPS. I did that last year and have rarely used my laptop NEM since. On my VPS i used 'nis.shouldAutoHarvestOnBoot = true' and setup a NEM account with zero balance in the config file to use with 'nis.bootKey =xxxxxxxxxx'. This setup was working great for months and I harvested many blocks and reboots of the VPS caused no problem as NIS would start from a shortcut in startup folder

But then in Dec 2015 the NIS on my VPS just kept stopping. I tried re-installing and deleting the cache files (smaragda's tip) but nothing worksed, NIS always stops after a few minutes. Then I noticed that if I change 'nis.shouldAutoHarvestOnBoot' to false the NIS on my VPS will sync, but when I login with my account on the VPS (i.e. the account I use with 'nis.bootKey =xxxxxxxxxx' in the config) and try and start harvesting on the VPS manually by clicking the harvesting button in the GUI I get the error "ERROR 306 NIS: UNEXPECTED ERROR".

I gave up and decided to wait for a new version, but I tried yesterday and NEM Beta 0.6.74 is doing the exact same behavior.

any love for kenny on this one?

You're gonna need to provide logs. Also head over to forum.nem.io and look at the Request for help category. You'll find some more things to try there.

Ok, will do! I was hoping someone would recognise the symptoms and have the cure at hand

[mepsipax]

KennyP  when this happened to me, I shut down Nem.

Then I deleted (backup first to be safe) my 'accounts_cache_mainnet.json'  which you can find within your C:/users/username/nem/ncc folder.

Then I restarted Nem, and it worked properly.

Give this a try to see if it helps

[BloodyRookie]

@mepsipax: the problem you are descibing only cause NCC to not start. His problems are different.
@KennyP: as Patmast3r said, go to https://forum.nem.io/ and i will solve your problem.

[instacalm]

happybelatedbirthday NEM!

[$dakini]

Any idea why the price is nose diving lately.
Some bad news???

[Nortan12rx]

Any idea why the price is nose diving lately.
Some bad news???

no.
on polo low volume in last days

24hr Volume: 12882.197 BTC / 802.536 XMR / 68335.251 USDT

[nembit86]

Any idea why the price is nose diving lately.
Some bad news???

no.
on polo low volume in last days

24hr Volume: 12882.197 BTC / 802.536 XMR / 68335.251 USDT

dont worry, it will reverse....

[$dakini]

Any idea why the price is nose diving lately.
Some bad news???

no.
on polo low volume in last days

24hr Volume: 12882.197 BTC / 802.536 XMR / 68335.251 USDT

dont worry, it will reverse....

I hope so too. 

[Scharfenberger]

Any idea why the price is nose diving lately.
Some bad news???

I don't think so. NEM is a longterm-investment. It has a slowly but steady growth. Those downtrends are artificially created by some daytraiders.

[greentea]

Any idea why the price is nose diving lately.
Some bad news???

I don't think so. NEM is a longterm-investment. It has a slowly but steady growth. Those downtrends are artificially created by some daytraiders.

Appears some individuals are trying to accumulate more at lower prices ...

[iTradeChips]

Any idea why the price is nose diving lately.
Some bad news???

I don't think so. NEM is a longterm-investment. It has a slowly but steady growth. Those downtrends are artificially created by some daytraiders.

Appears some individuals are trying to accumulate more at lower prices ...

came in a littler late to buy at 320's for a few bucks. i missed the sub-310 dip.

[nembit86]

      https://forum.nem.io/t/nem-apostille-application-for-funding-procedure/2006

       this is the last full day to vote on this project looking for community funds
   
       we urge anybody who has not voted to please do so today

        we are NEM, we are strong !!!!!!!

         
       

[nembit86]

Any idea why the price is nose diving lately.
Some bad news???

I don't think so. NEM is a longterm-investment. It has a slowly but steady growth. Those downtrends are artificially created by some daytraiders.

Appears some individuals are trying to accumulate more at lower prices ...

came in a littler late to buy at 320's for a few bucks. i missed the sub-310 dip.

   I know for a fact that people are going to look back at 310's and 320's and ask themselves why the hell didnt they buy ........ !!!!!!!!!