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

[shiva.India]

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



Thanks,
Shiva

[1715575506]

1715575506

[1715575506]

1715575506

[1715575506]

1715575506

[1715575506]

1715575506

[lordoliver]

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



Thanks,
Shiva

until the exchange is hacked ;-)

[LiteMag]

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 <NAE5VJB76PIR6FWO3FYSCRD7F7NWUSKBGFX3EVW6>] @ [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 <NAE5VJB76PIR6FWO3FYSCRD7F7NWUSKBGFX3EVW6>] @ [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 <NAE5VJB76PIR6FWO3FYSCRD7F7NWUSKBGFX3EVW6>] @ [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 <NAE5VJB76PIR6FWO3FYSCRD7F7NWUSKBGFX3EVW6>] @ [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!

[BloodyRookie]

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:
2017-03-20 14:00:58.090 INFORMATION failed to synchronize with Node [Hi, I am Alice6 <NAE5VJB76PIR6FWO3FYSCRD7F7NWUSKBGFX3EVW6>] @ [108.61.168.86]: org.nem.core.connect.FatalPeerException: remote node is evil: REMOTE_RETURNED_INVALID_HASHES (org.nem.nis.BlockChain a)
Does anyone know what I can do about it?

I have the latest version 0.6.84.

Thanks in advance!

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

[LiteMag]

Thanks! I will try that! 

[suky321]

I send 30 000 xem from nanowallet, to poloniex. Block was already opened. Money retiremented from nanowallet 2 hours ago. But didn't come to poloniex. Said, please where should I write to pay back xem

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

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

[Tehfiend]

Thanks for the explanation. If I understand correctly, it is still up to the company running the private blockchain to decide whether or not they want to leverage the public blockchain by linking the two.

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

Immutability in this case could still be achieved by running the private blockchain on multitude of nodes effectively making them decentralized—although it would not be as reliable as linking to a public blockchain.

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.

[tomkat]

I send 30 000 xem from nanowallet, to poloniex. Block was already opened. Money retiremented from nanowallet 2 hours ago. But didn't come to poloniex. Said, please where should I write to pay back xem

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."

[greentea]

The purpose of linking a private blockchain (Mijin) to a public blockchain (NEM) is for immutability. A private blockchain has a central authority which can alter that blockchain at their discretion. Linking it to a public chain which is immutable due to it's decentralized nature solves that problem and you get best of both worlds.

Thanks for the explanation. If I understand correctly, it is still up to the company running the private blockchain to decide whether or not they want to leverage the public blockchain by linking the two. Immutability in this case could still be achieved by running the private blockchain on multitude of nodes effectively making them decentralized—although it would not be as reliable as linking to a public blockchain.

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.

[kauppalahti]

I send 30 000 xem from nanowallet, to poloniex. Block was already opened. Money retiremented from nanowallet 2 hours ago. But didn't come to poloniex. Said, please where should I write to pay back xem

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

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

Number of transaction 1030856. nbhl6v-hsapkr-2jkoa7-uqxatf-leye2r-b3hbvd-neus  is not my wallet. Does 30 000 xem went on it? NBZMQO7ZPBYNBDUR7F75MAKA2S3DHDCIFG775N3D - my wallet (3 xem). I forgot write message in transaction. Advise please how pay back nem?

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

[tomkat]

I send 30 000 xem from nanowallet, to poloniex. Block was already opened. Money retiremented from nanowallet 2 hours ago. But didn't come to poloniex. Said, please where should I write to pay back xem

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

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

Number of transaction 1030856. nbhl6v-hsapkr-2jkoa7-uqxatf-leye2r-b3hbvd-neus  is not my wallet. Does 30 000 xem went on it? NBZMQO7ZPBYNBDUR7F75MAKA2S3DHDCIFG775N3D - my wallet (3 xem). I forgot write message in transaction. Advise please how pay back nem?

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

try to contact their support

[visaco]

nem wallet dark skin

[visaco]

multisignature 

[pgb]

nem wallet dark skin

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

[visaco]

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

[NEMergizer]

nem wallet dark skin

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

You are right about that. The pics at the bottom corners is a horrible joke.

[dadingsda]

nem wallet dark skin

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

You are right about that. The pics at the bottom corners is a horrible joke.

 

lol. Looks like an android-game but not like a wallet i want to store real money

[NEMergizer]

nem wallet dark skin

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

You are right about that. The pics at the bottom corners is a horrible joke.

 

lol. Looks like an android-game but not like a wallet i want to store real money

Pay attention whenever you use a third party client and/or skin. For your security you should only use the official skins and clients.

[adiru]

Hey folks,

This is my first post here, I have been sitting back and carefully analysing the comments and collating the common themes.  
One thing certain, NEM is building some very strong foundations and moving forward at a steady pace.  With this being the case I have created an “ebay” style site called nemBid.  

Consider this an all-NEM coin alternative version of eBay.  
Yep, there's nothing too large or too small to be auctioned off on nemBid. With the potential for over 120,000 items being listed every month, there will be plenty to purchase.
   
Trusted Australian based site
   Introductory fee structure.  The first six (6) months of operation there will be zero fees incurred for listing or selling items *
        
         www.nemid.xyz  (currently displaying under construction)

Yes this is a genuine domain name owned and hosted in Australia.  CR Digital Solutions Australian Company Number 93160467274

Launch date is expected to be 27/03/2017.  Updates throughout the week will be posted.

I truly hope that the NEM community can appreciate the importance of this site and embrace it with open arms.  I have plans in the future to launch a mobile version of the site and many other interactive features.


*Over time it is planned for the site to grow in strength by numbers of auctions and active members.  For us to get the ball rolling and to gain momentum, the first six months of operation there will be a zero (0) selling fee.  After which it will revert to a 3.3% fee for selling.  Conditions apply

[jelin1984]

very nice and cool