NEM Mainnet Faucet OPEN!

Projects
#940

yeah but… its free money man

#941

As the saying goes: stupid with small amounts of money, stupid with big amounts too. After all, don’t just value an asset at the current price, albeit NEM does seem to be perpetually stuck around a quarter. Finally, I think you should look up some of those words you are using, I don’'t think you know what some of them mean.

#942

yeah okay i know but… still… its free money man

#943

Yep. But it’s only free money if we can withdraw it, isn’t it? Otherwise it’s just fantasy points in a game which is pretending to give away free money.

#944

yeah so… when withdraw enable?

#945

why faucet down now? when faucet up?

#946

i need to pay my rent…

#947

Surely a status update is not too much too ask after all of this time.

#948

Wait - Are you saying that a status update on the faucet issues would be nice?
Becuase that acutally is also my thinking… !

#949

Please stop spamming in this thread. Until official announcement of @namuyan faucet should be considered as closed.
I’m pretty sure that couple XEM from faucet is not enought to pay your rent.

1 Like
#950

Sorry, I’m now in trouble on NIS.
I think need to setup another server, so it takes a few days or more (If solve).
What’s rent? I’m not your father.

3 Likes
#951

namuyan. Could I help you with your NIS problem? I could at least do some researches for you if you pointed me in the direction you need looked at.

1 Like
#952

Don’t worry, take your time. Don’t listen to the people bitching for their “money” or other spoiled “kids” requests :wink:
Can’t you just restart your server or the whole network maybe ?

#953 
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.DefaultClientExchangeHandlerImpl.executionFailed(DefaultClientExchangeHandlerImpl.java:101)
        at org.apache.http.impl.nio.client.AbstractClientExchangeHandler.failed(AbstractClientExchangeHandler.java:426)
        at org.apache.http.nio.protocol.HttpAsyncRequestExecutor.endOfInput(HttpAsyncRequestExecutor.java:345)
        at org.apache.http.impl.nio.DefaultNHttpClientConnection.consumeInput(DefaultNHttpClientConnection.java:261)
        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:114)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(BaseIOReactor.java:162)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvent(AbstractIOReactor.java:337)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEvents(AbstractIOReactor.java:315)
        at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(AbstractIOReactor.java:276)
        at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseIOReactor.java:104)
        at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReactor$Worker.run(AbstractMultiworkerIOReactor.java:588)
        at java.lang.Thread.run(Thread.java:748)
Caused by: org.nem.core.connect.FatalPeerException: org.apache.http.ConnectionClosedException: Connection closed
        at org.nem.core.connect.HttpMethodClient$HttpMethodClientFutureCallback.wrapException(HttpMethodClient.java:210)
        ... 16 more
Caused by: org.apache.http.ConnectionClosedException: Connection closed
        ... 12 more
 (org.nem.core.async.NemAsyncTimerVisitor notifyOperationCompleteExceptionally)

Same error raised, I try to increase heap memory.
Does someone know the problem?

2 Likes
#954

Isn’t it a connectivity problem ?
I think you would have more feedback on stackoverflow or similar (dev) forums :wink:

I saw the faucet is back online ! Thanks ! No withdraw at this time though…

#955

when faucet up?

#956

hello namyuan, now faucet open again, but still have error. withdraw not possible… any update?

#957

faucet now up. when withdraw?

#958

i heard that the withdrawal function will be enabled soon! is this correct?

1 Like
#959

faucet now down again. when faucet up?