NXT :: descendant of Bitcoin - Updated Information

[pinarello]

That is good news thank you !

[1714475193]

1714475193

[1714475193]

1714475193

[1714475193]

1714475193

[1714475193]

1714475193

[1714475193]

1714475193

[Come-from-Beyond]

NEWS

BCNext & stakeholders decided to publish the source code of base features on the 3rd of January. If I don't fix all stability issues I hope the community will help me.

good knews, how did the stakeholders decided?

Some of them posted on nextcoin.org. The rest kept silence.

[Come-from-Beyond]

BCNext & stakeholders decided

Interesting. I am >1M stakeholder but nobody asked me

I did. But u seemed to overlook my posts.

[salsacz]

it is strange that when client is running - I can't even watch youtube films - everything is lagging, it is using 100 percent of CPU

Strange. I see no CPU consumption and Youtube works on 1 Mbps without problems.

Can anyone confirm that Nxt soft uses a lot of resources?

so after 3 hours of downloading blocks it stopped to eat 50 percent of my CPU. But Jawa now wants 180 MB of RAM memory (at the start it was 60 MB)

[pinarello]

BCNext & stakeholders decided

Interesting. I am >1M stakeholder but nobody asked me

 >1M stakeholder but no >500M

[achimsmile]

I have problems setting up a node...

I enter something like:

http://localhost:7874/nxt?requestType=markHost&secretPhrase=i-wont-tell-you&host=92.104.121.108&weight=1000000&date=2013-21-09

I get a hallmark value, which I copy to web.xml:

<param-name>myHallmark</param-name>
<param-value>thats where I paste the looong string</param-value>

When I decode it:

http://localhost:7874/nxt?requestType=decodeHallmark&hallmark=HEX_STRING

I get:

{"errorCode":4,"errorDescription":"Incorrect \"hallmark\""}

What did I do wrong? 

[Come-from-Beyond]

I have problems setting up a node...

I enter something like:

http://localhost:7874/nxt?requestType=markHost&secretPhrase=i-wont-tell-you&host=92.104.121.108&weight=1000000&date=2013-21-09

I get a hallmark value, which I copy to web.xml:

<param-name>myHallmark</param-name>
<param-value>thats where I paste the looong string</param-value>

When I decode it:

http://localhost:7874/nxt?requestType=decodeHallmark&hallmark=HEX_STRING

I get:

{"errorCode":4,"errorDescription":"Incorrect \"hallmark\""}

What did I do wrong? 

Tell us ur long string. It can be revealed.

[starik69]

I did. But u seemed to overlook my posts.

Posts? You are kidding? I thought BCNext promised some voting system. Without that any statement on behalf of stakeholders cannot be proved. So it is false. 

>1M stakeholder but no >500M

How do you know?

[Come-from-Beyond]

Posts? You are kidding? I thought BCNext promised some voting system. Without that any statement on behalf of stakeholders cannot be proved. So it is false. 

Sorry if I didn't make it clear enough that this was a plan, not a promise.

[starik69]

Sorry if I didn't make it clear enough that this was a plan, not a promise.

So you confirm, that you cannot prove that stakeholders decided something?

[Come-from-Beyond]

Sorry if I didn't make it clear enough that this was a plan, not a promise.

So you confirm, that you cannot prove that stakeholders decided something?

No, http://nextcoin.org/index.php/topic,22.0.html lets me think that stakeholders did decide to release the source code on the 3rd.

[starik69]

No, http://nextcoin.org/index.php/topic,22.0.html lets me think that stakeholders did decide to release the source code on the 3rd.

I already asked you - where are stakeholders there? Remember your answer?
What you think is not what you can prove, isn't it?

[achimsmile]

Tell us ur long string. It can be revealed.

Ok here we go

<param-value>3dab3e2a9beac77fd6d0c6b220e2f5e65a482a8edf72a641ba7a40a21d6f97260e0039322e31303 42e3132312e313038640000000d31330191fc48cac816b751a62c2e34aa302d668e7779bcb87f24 0c6db0a3b0f2b6817e0e0be497008480880066abda376bca481d825ae1e0c1935d2ec07e90d43b9 b1977</param-value>

thank you

[PGPpfKkx]

what happens if i run the client/server without doing the web.xml stuff? am I still mining?

also i get exceptions with wallet 0.3.16 when the previous version was running so i can't even open my wallet but wth.

java.lang.nullpointerexception alltime classic.

[idev]

guess a kill -9 will damage the files?

Yes.

How can it be stopped safely ?

[grizmoblust]

NEWS

BCNext & stakeholders decided to publish the source code of base features on the 3rd of January. If I don't fix all stability issues I hope the community will help me.

Are you saying that the 71 stakeholders obtain white paper, and the source code from the start?

[bahamapascal]

NEWS

BCNext & stakeholders decided to publish the source code of base features on the 3rd of January. If I don't fix all stability issues I hope the community will help me.

LOL, I am stake holder as well ( around 3M) and did not vote as I did not know about it
The vote turned out in my best interest, I would have voted the same but still would have been nice if it were announced better

CfB: Dose a news thread exist? If not, what do you think about (me ?) opening one? Then we would have one place with the latest news and latest client updates, that would help many to stay in the loop with nxt
Let me know what you think.

[kwest]

NEWS

BCNext & stakeholders decided to publish the source code of base features on the 3rd of January. If I don't fix all stability issues I hope the community will help me.

Are you saying that the 71 stakeholders obtain white paper, and the source code from the start?

I'm a stakeholder.. and no, we did not get the source code. Nobody has it at this time except CfB and BCNext.

[Gonzo418]

I'm no expert in this, BUT wouldn't it be better to open source the source code ? Maybe nxt would grow and would attract much more interest. For the stakeholders (I'm none ) and for all others who own only small amounts.

I thought the source code was available already, but I must have misunderstood some things.

[nexern]

guess a kill -9 will damage the files?

Yes.

How can it be stopped safely ?

depends on your system, a ctr-c sends a sigint (2) to stop the process gracefully, which should be fine.
a sigterm (15) also but more stringent. a sigkill (9) just pulls the plug, not good because the process
can't clean up gracefully. in this case a possible broken file descryptor damaged the file.