WTF again not on time?
~CfA~
OMG  Keep calm guy and shut up, lol. the dev is online, so the url will be available soon I hope  |
|
|
|
Why do you need NXT ID? If i don't have it i can't contribute?
You will have to register one, because the stakes are given to you on nxt ae. |
|
|
|
So is it cool if I register using my NXT address from my online wallet at myNXT.info?
Can someone answer this question please.  You have to login locally, because otherwise you won't get access to the built-in nxt exchange.... |
|
|
|
To avoid confusion we have changed the account activity rules slightly.
The new rules are as follows.
a) Your BTT account is older than 3 months and has less than 20 quality posts
b) Your BTT account is younger than 3 month and has less than 40 quality posts
Remember, you can still apply if your BTT account activity puts you into a) or b) above, you'll just have an extra hurdle to jump over to register for Kora. We're trying to strike a balance - stop multiple account abuse from sockpuppets but not disadvantage new users of this forum.
Great! But what will this extra hurdle be? Is this already fixed? |
|
|
|
|
Maybe I will give this a try
|
|
|
|
|
Is there any gpu miner for this?
|
|
|
|
Can't wait to register  |
|
|
|
|
When will the beta be available afterwards?
|
|
|
|
|
When will the beta be available?
|
|
|
|
Sounds really interesting |
|
|
|
|
Count me in. When will the details regarding rule 6 be published?
|
|
|
|
|
Count me in. When will the details regarding rule 6 be published?
|
|
|
|
I setup two nodes, but the node registration site claims that the wallet is not detected on both nodes. Port 9084 is reachable. What´s wrong here`?
It should run without -disablerpc parameter. Port 9085 should be reachable. Indeed this was the error. Thank You! |
|
|
|
|
I setup two nodes, but the node registration site claims that the wallet is not detected on both nodes. Port 9084 is reachable. What´s wrong here`?
|
|
|
|
I have will check there thanks again anyway, dynamic ip here too  We have had some people that successfully run dyndns and get bounty. This work with dynamic ip. Allthough if you are unlucky you can miss some bountys when the dns updates. I have 5 servers running in the cloud. I SSH into each to run NHZ and unfortunately every day, because my service provider is dynamic, I get disconnected and need to restart each client. Wish there was a way around this annoying problem. Anyone know a simple solution? Edit: I should clarify, the servers are on digital ocean and running NHZ. It is the local machine that "disconnects" from SSH connection. Will keep tinkering. You should use screen. Start screen and run NHZ in this session. Press Ctrl+A then D. The screen session gets disconnected from your session and will run in the background. |
|
|
|
Absolutely agree!
Must be 3000! Will be lovely, otherwise people will stop their Nodes...
It was 333 a day. I'm ok with 666. With this amount, the distribution will last some days and many people can contribute and get some NHZ. |
|
|
|
|
I really like this coin. But the diff is really hard now
|
|
|
|
I set up a hallmark, have been running for 3 days, and still have yet to receive my coins.
At some point there was something that looked like a bounty to be paid out under unconfirmed transactions. When I logged back in later it was showing 0 again.
Should I be getting coins by now?
The same here. Account: 12930652463845167717 Btw: I would not call this a fair distribution, if you give out 20000 to 40000 NHZ for simple translations or blog posts and the nodes are getting 333 per day. You have to run a node for a hundred days, which is quite more expensive and time consuming to get the same amount of NHZ. You can set up a small vps for 5$/month - this takes less than 10 minutes of time True, but maintaining it over hundred days will be ~20$ and much more time |
|
|
|
|
Show Posts
