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

many youtubers start talking seriously about NEm   good news




https://www.youtube.com/channel/UC2L7yK17LXIOAs-zNmSspOQ/videos



https://www.youtube.com/channel/UCqeAkF8g3fN4niuwNDYAOWw



https://www.youtube.com/channel/UCsF18TXYx_cYrTZJ42t-CuQ

Looks great!! only thing I don't like is the pics at the bottom corners, but that's just me.

multisignature 

nem wallet dark skin

NBZMQO7ZPBYNBDUR7F75MAKA2S3DHDCIFG775N3D is probably Poloniex address
http://chain.nem.ninja/#/search/NBZMQO7ZPBYNBDUR7F75MAKA2S3DHDCIFG775N3D

try to contact their support

It is on crypto space without unique message. Ask help fom polo with your above details.

Mijin is a great 1-2 punch, as it gets the foot in the door, and once the company sees the power of mijin, a switch/link to NEM is much easier and they will be more comfortable having already worked with mijin.  of course not all companies will use the public chain, but even a small percentage can be huge.

Companies are much more willing to test with a private chain they control than jumping right in with a public chain.  This 1-2 business model is actually very genius in my mind, and every company that tests with mijin is indirectly exposed to NEM.

Did you use a message as instructed in Poloniex deposit form?

They say "You MUST send your deposit using the unique Message above. Failure to do so may result in the loss of your deposit."

Yes, not all private chains will want immutability but many will which is a very valuable feature.


In a private blockchain, a single entity controls all of the nodes so they would be able to change the blockchain at their discretion so immutability is not possible without a decentralized public block chain to anchor to.

Search for your transaction on here: See if it went to correct address:

http://chain.nem.ninja/#/blocks/0

Thanks! I will try that! 

Your node is on a deep fork. Either sync from scratch or download a recent db from Bob:

bob.nem.ninja/nis5_mainnet-1002k.h2.db.zip

Hello.

My NIS is not synching and I am 22 Days behind. I don't know what to do. Has anyone the same problem?

Here is my log:
java.util.concurrent.CompletionException: org.nem.core.connect.FatalPeerException: org.apache.http.ConnectionClosedException: Connection closed
   at java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:292)
   at java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:308)
   at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:593)
   at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
   at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:474)
   at java.util.concurrent.CompletableFuture.completeExceptionally(CompletableFuture.java:1977)
   at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.failed(HttpMethodClient.java:201)
   at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:134)
   at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.failed(AbstractClientExchangeHandler.java:419)
   at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput(HttpAsyncRequestExecutor.java:341)
   at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:263)
   at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:81)
   at org.apache.http.impl.nio.client.InternalIODispatch.onInputReady(InternalIODispatch.java:39)
   at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputReady(AbstractIODispatch.java:116)
   at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:164)
   at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:339)
   at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:317)
   at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:278)
   at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:106)
   at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:590)
   at java.lang.Thread.run(Thread.java:745)
Caused by: org.nem.core.connect.FatalPeerException: org.apache.http.ConnectionClosedException: Connection closed
   at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.wrapException(HttpMethodClient.java:210)
   ... 15 more
Caused by: org.apache.http.ConnectionClosedException: Connection closed
   ... 12 more
 (org.nem.core.async.NemAsyncTimerVisitor notifyOperationCompleteExceptionally)
2017-03-20 14:00:55.884 INFORMATION Time synchronization: found 11 nodes to synchronize with. (org.nem.nis.time.synchronization.NisTimeSynchronizer synchronizeTime)
2017-03-20 14:00:56.344 INFORMATION NC2ZQKEFQIL3JZEOB2OZPWXWPOR6LKYHIROCR7PK: network time offset to local node is -20ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.344 INFORMATION NC5A7OIVQ6YNXDWY6656MBCS4IYZNQTB6EWMYZHS: network time offset to local node is -15ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.344 INFORMATION NCZ6YBREMON6BP5X4M7KOMKPV6JW6YY2SHB3RJ7D: network time offset to local node is -14ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.345 INFORMATION NAE5VJB76PIR6FWO3FYSCRD7F7NWUSKBGFX3EVW6: network time offset to local node is -11ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.345 INFORMATION NBCYZ7REMOHQAASWEUDWE3NV35SU4P4XQOZC7MQQ: network time offset to local node is -6ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.345 INFORMATION NCL63DFN3TD5RUDVEMPTHSAUHZFDCTXFOW6KFV7J: network time offset to local node is -6ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.345 INFORMATION NA76OOREMOGJYHUKH4SU7OS73456L35J7NOIJWQM: network time offset to local node is 9ms (org.nem.nis.time.synchronization.DefaultTimeSynchronizationStrategy a)
2017-03-20 14:00:56.763 INFORMATION synchronizing with Node [Hi, I am Alice6 ] @ [108.61.168.86] (org.nem.peer.services.NodeSynchronizer b)
2017-03-20 14:00:58.090 INFORMATION failed to synchronize with Node [Hi, I am Alice6 ] @ [108.61.168.86]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)
2017-03-20 14:00:58.090 INFORMATION synchronizing with Node [Hi, I am Alice6 ] @ [108.61.168.86] finished (org.nem.peer.services.NodeSynchronizer b)
2017-03-20 14:00:58.090 INFORMATION Updating experience with Node [Hi, I am Alice6 ] @ [108.61.168.86]: FAILURE (org.nem.peer.PeerNetworkState a)

Does anyone know what I can do about it?

I have the latest version 0.6.84.

Thanks in advance!

until the exchange is hacked ;-)

Hello ,
           How long we can keep my nem coins in Exchange ?...



Thanks,
Shiva

You can PM me.

better keep a record of the PRIV KEY too + the wallet (*.wlt) file.

maybe write it down somewhere in a piece of paper

goodluck sir!

When I export wallet from NEM client its backuped and I can restore it on the other PC? Or do I still need to copy over files from user/data etc..

Running it on a multitude of nodes does not make something decentralized if you control all of those nodes.

I guess the idea with linking is that you can make it decentralized without handing out control over your nodes, thus keeping control over your own chain while it is still immutable.

I want to try adding my XEM to a supernode too, where or who can I possibly contact someone that can add my xem to his/her supernode?