Author

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

legendary
Activity: 1162
Merit: 1005
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley

You cannot change the description once it is written in there.

It is possible to send a message to every stakeholder.

Maybe from the issuer but the issuer is UP and as you probably noticed he isn't here very often these days Smiley

No need to be issuer to send messages to stakeholder NXT accounts. Everyone can send messages to everyone from personal NXT account.

I thought there was a function for an issuer to automatically message all holders if his asset.
You mean to manually send a message to all holder of NEMStake ?

Yes manually. There is 482 stakeholders as for now. But I do not insist of doing it Smiley Maybe few days before deadline, it will be not so much Nemstake owners left.
There is also possibility to send dividends automatically to shareholders. Possible to send 0.0000001 NXT as dividend with message in transaction.
hero member
Activity: 980
Merit: 1001
Is NEM stake from BTT can be redeemed already? I guess it was answered multiple times already, but still... so much information - I got lost.
And if yes, which guide do I have to use? The One for the Phase 2 from the OP?  Huh

P.S. I got my token and registered it as it should be in Phase 1.

If you only have the stake on btt (seems that way since you received a token) then phase 2 hasn't started for you yet. It will on nov 1st. Monitor the thread, twitter and forum.nemcoin.com to find more information once it starts.
hero member
Activity: 621
Merit: 507
Radix-The Decentralized Finance Protocol
Is NEM stake from BTT can be redeemed already? I guess it was answered multiple times already, but still... so much information - I got lost.
And if yes, which guide do I have to use? The One for the Phase 2 from the OP?  Huh

P.S. I got my token and registered it as it should be in Phase 1.
hero member
Activity: 980
Merit: 1001
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley

You cannot change the description once it is written in there.

It is possible to send a message to every stakeholder.

Maybe from the issuer but the issuer is UP and as you probably noticed he isn't here very often these days Smiley

No need to be issuer to send messages to stakeholder NXT accounts. Everyone can send messages to everyone from personal NXT account.

I thought there was a function for an issuer to automatically message all holders if his asset.
You mean to manually send a message to all holder of NEMStake ?
legendary
Activity: 1162
Merit: 1005
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley

You cannot change the description once it is written in there.

It is possible to send a message to every stakeholder.

Maybe from the issuer but the issuer is UP and as you probably noticed he isn't here very often these days Smiley

No need to be issuer to send messages to stakeholder NXT accounts. Everyone can send messages to everyone from personal NXT account.
hero member
Activity: 1134
Merit: 502

public key is  a01414be9d7f0063add8c184adfa06361defad5f9f9aeb17bc152e0a7d27ea7c

thank you

sent
newbie
Activity: 6
Merit: 0
Hi guys, can you please send me 2 nxt on NXT-7WKM-AFS8-NTSY-4L9V9
I will send it back to you ASAP
public key is  a01414be9d7f0063add8c184adfa06361defad5f9f9aeb17bc152e0a7d27ea7c

thank you
hero member
Activity: 980
Merit: 1001
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley

You cannot change the description once it is written in there.

It is possible to send a message to every stakeholder.

Maybe from the issuer but the issuer is UP and as you probably noticed he isn't here very often these days Smiley
legendary
Activity: 1162
Merit: 1005
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley

You cannot change the description once it is written in there.

It is possible to send a message to every stakeholder.
hero member
Activity: 980
Merit: 1001
REAL ADDRESSES USED FOR REDEMPTION DO NOT START WITH T. THEY START WITH AN N. IF YOU SENT AN ADDRESS WITH A T WITH YOUR ASSET THEN YOU'VE FAILED.

Could you confirm whether the current version of the wallet is the one in which NEM will be received?
And when is phase 2 likely to start (or has it already started)?

The current version of the wallet is NOT the one we'll launch with.
Phase 2 has started for stakes on the AE already and will start on 31st of oct for btt stakes (1st nov. latest, need to adapt the portal).
legendary
Activity: 1059
Merit: 1016
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley

You cannot change the description once it is written in there.
sr. member
Activity: 280
Merit: 250
REAL ADDRESSES USED FOR REDEMPTION DO NOT START WITH T. THEY START WITH AN N. IF YOU SENT AN ADDRESS WITH A T WITH YOUR ASSET THEN YOU'VE FAILED.

Could you confirm whether the current version of the wallet is the one in which NEM will be received?
And when is phase 2 likely to start (or has it already started)?
hero member
Activity: 798
Merit: 1000
Move On !!!!!!
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.



I think that majority of the people is well aware of this. They are just waiting and trying to squeeze the most of the profits out of it by trading and they are also hoping for the big price increase in the last week.

Nevertheless it should be done, just so the people can't complain if they forget!!  Smiley
sr. member
Activity: 406
Merit: 500
Hey everybody.

I think that some kind of warning should be placed in the description of the NEMstake asset (here: https://nxtblocks.info/#section/assets_exchange/stakeholders/12465186738101000735), so people know that it will be worth nothing in the near future unless they follow the procedure to redeem it for real NEM.

Maybe something like: "This asset will be worthless after XXXX date. The keep the value inherent to this asset, follow this instructions ASAP: [link to the phase 2 redemption stage]"

This way we can keep the number of unclaimed NEMstakes to a minimum.

hero member
Activity: 888
Merit: 1001
Proof-of-Stake Blockchain Network
On account of a 5M. Send 4700 000. He writes: "Your account does not have enough funds to send this amount NEM".
A sum of up to 1M go.

Second time comes this story. First time as it is self-recovered after a while ...
hero member
Activity: 840
Merit: 500
Risk taker & Black Swan farmer.
Please refrain from posting and wallet addresses here or your post will be immediately deleted. We don't want to risk closing of this thread.

If you want to receive some test NEM please post your address here: https://forum.nemcoin.com/index.php?topic=2547.0
legendary
Activity: 1232
Merit: 1001
mining is so 2012-2013

BTW..... Are any of you devs getting footage of you living in small dark cramped run down apartments with your hair all nasty because you have been coding for the last 30 hours?  And then you talk in a kind of mad man's sleepless ramble about how your will die or make this thing work???  That makes for really great footage later.

Interesting idea. I'll have to get some photos of myself writing code while drinking sake.

I still think we need to get more people involved in NEM, especially gearing up for launch:
https://forum.nemcoin.com/index.php?topic=2352.msg4130#msg4130

 Grin Grin
Be careful this man code and drink sake


haha



So, I've been running my node since beta and it seems like everything is fine because I am green on that chart and everything, but I just noticed that my NIS is not syncing now. It says I am stuck on block 6980. Is everyone else still running fine? As far as I can tell NIS and NCC are running normally but it has been about an hour now since I last checked and still not syncing...

EDIT: I just rebooted NIS and my local node and it synchronized. I wonder why it stopped in the first place though?

Could it be this?


I had the exact same problem. Just restarted nis/ncc this morning and it works again now.

Oh no!!! Makato, was it the sake that broke NEM at #6980!?!? Hehehe

Just joking, but I had the same problem and wrote about it here. https://forum.nemcoin.com/index.php?topic=2546.msg7506#msg7506  Were either of you experimenting with remote harvesting?
legendary
Activity: 1596
Merit: 1000
I am not Dorian Nakamoto.
oi can anyone tell me if this is s full address size? (for creating "real address")

xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxx

It says to make sure you copy the whole thing. I sent before i triple checked and sent something this length.  looks same size as the beta address I have..

Looks good to me. It should start with an N.
legendary
Activity: 1610
Merit: 1008
Forget-about-it
oi can anyone tell me if this is s full address size? (for creating "real address")

xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxx

It says to make sure you copy the whole thing. I sent before i triple checked and sent something this length.  looks same size as the beta address I have..
legendary
Activity: 1596
Merit: 1000
I am not Dorian Nakamoto.
So, I've been running my node since beta and it seems like everything is fine because I am green on that chart and everything, but I just noticed that my NIS is not syncing now. It says I am stuck on block 6980. Is everyone else still running fine? As far as I can tell NIS and NCC are running normally but it has been about an hour now since I last checked and still not syncing...

EDIT: I just rebooted NIS and my local node and it synchronized. I wonder why it stopped in the first place though?

Could it be this?

Code:
10 24, 2014 5:36:43 午前 org.nem.core.async.NemAsyncTimerVisitor b
警告: Timer CHECKING CHAIN SYNCHRONIZATION raised exception: org.nem.core.connect.FatalPeerException: java.net.ConnectException: Connection refused: no further information
java.util.concurrent.CompletionException: org.nem.core.connect.FatalPeerException: java.net.ConnectException: Connection refused: no further information
at java.util.concurrent.CompletableFuture.internalComplete(Unknown Source)
at java.util.concurrent.CompletableFuture$ThenApply.run(Unknown Source)
at java.util.concurrent.CompletableFuture.postComplete(Unknown Source)
at java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source)
at org.nem.core.connect.HttpMethodClient$a.failed(HttpMethodClient.java:202)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.connectionRequestFailed(DefaultClientExchangeHandlerImpl.java:308)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.access$100(DefaultClientExchangeHandlerImpl.java:63)
at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl$1.failed(DefaultClientExchangeHandlerImpl.java:351)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)
at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager$InternalPoolEntryCallback.failed(PoolingNHttpClientConnectionManager.java:471)
at org.apache.http.concurrent.BasicFuture.failed(BasicFuture.java:130)
at org.apache.http.nio.pool.RouteSpecificPool.failed(RouteSpecificPool.java:161)
at org.apache.http.nio.pool.AbstractNIOConnPool.requestFailed(AbstractNIOConnPool.java:527)
at org.apache.http.nio.pool.AbstractNIOConnPool$InternalSessionRequestCallback.failed(AbstractNIOConnPool.java:746)
at org.apache.http.impl.nio.reactor.SessionRequestImpl.failed(SessionRequestImpl.java:154)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:175)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvents(DefaultConnectingIOReactor.java:147)
at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor.execute(AbstractMultiworkerIOReactor.java:348)
at org.apache.http.impl.nio.conn.PoolingNHttpClientConnectionManager.execute(PoolingNHttpClientConnectionManager.java:189)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.doExecute(CloseableHttpAsyncClientBase.java:67)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase.access$000(CloseableHttpAsyncClientBase.java:38)
at org.apache.http.impl.nio.client.CloseableHttpAsyncClientBase$1.run(CloseableHttpAsyncClientBase.java:57)
at java.lang.Thread.run(Unknown Source)
Caused by: org.nem.core.connect.FatalPeerException: java.net.ConnectException: Connection refused: no further information
at org.nem.core.connect.HttpMethodClient$a.failed(HttpMethodClient.java:199)
... 19 more
Caused by: java.net.ConnectException: Connection refused: no further information
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source)
at org.apache.http.impl.nio.reactor.DefaultConnectingIOReactor.processEvent(DefaultConnectingIOReactor.java:173)
... 7 more

I had the exact same problem. Just restarted nis/ncc this morning and it works again now.
Jump to: