NXT :: descendant of Bitcoin - Updated Information

[chanc3r]

Is it possible to get a list of active peers and other stats from the client via http://localhost:7874/nxt?

Interested to see if I can script something to check on the client externally, e.g. restart if certain conditions are met

thanks,

Ian

Check http://localhost:7874/nxt?requestType=getState and http://localhost:7874/nxt?requestType=getPeers.

Cool, tyvm will see what I can do with that..

[Come-from-Beyond]

I'm still suffer from catching up problem,
I was stuck at some point this morning, so i restore the *.nxt files to height 23522, unfortunately i stuck 23522 for more than 5 hours;
I restart nxt several times, no help;    

Show us ur well-known peers list plz.

[dzarmush]

Question from a new nxt/btc exchange (nxtchg.com) founder: "Guys, what's the best way to check a NXT address for incoming transactions without installing the client? Block explorer? Is there an API for this sort of thing? It's needed for automated NXT deposits.".

[Come-from-Beyond]

Question from a new nxt/btc exchange (nxtchg.com) founder: "Guys, what's the best way to check a NXT address for incoming transactions without installing the client? Block explorer? Is there an API for this sort of thing? It's needed for automated NXT deposits.".

An exchange must host its own client. Any other way is insecure (at least now, when hallmark protection is not used for everything).

[MyZhre]

I'm still suffer from catching up problem,
I was stuck at some point this morning, so i restore the *.nxt files to height 23522, unfortunately i stuck 23522 for more than 5 hours;
I restart nxt several times, no help;    

Show us ur well-known peers list plz.

^M
                <init-param>^M
                        <param-name>wellKnownPeers</param-name>^M
                        <param-value>162.243.214.68; 95.85.46.164; 162.243.216.55; 162.243.143.15; 95.85.46.249; 93.190.92.74; 37.209.120.192; 93.190.92.75; 85.25.134.59; 93.190.92.76; vps1.nxtcrypto.org;  vps2.nxtcrypto.org;  vps3.nxtc
rypto.org;  vps4.nxtcrypto.org;  vps5.nxtcrypto.org; nxtwallet.com; 31.220.50.208; nxt.ddos.me; 203.174.12.25; 88.198.142.92; 66.197.138.90; 64.120.180.106; 109.230.224.65; 80.86.92.50; node1.nextcoin.it; node2.nextcoin.it; node3.nextco
in.it; node4.nextcoin.it; node5.nextcoin.it; nxt.homer.ru; 31.204.130.123; 209.222.0.194; 209.222.16.10; node1.nxtbase.com; node11.nxtbase.com; node21.nxtbase.com; node27.nxtbase.com; node31.nxtbase.com; node41.nxtbase.com; node51.nxtba
se.com; node61.nxtbase.com; node71.nxtbase.com; node81.nxtbase.com; node84.nxtbase.com node91.nxtbase.com; node95.nxtbase.com; node98.nxtbase.com; 85.214.222.82; 78.46.95.28;</param-value>^M
                </init-param>^M

There are more than 40 active peers listed, communication seems good.

[Come-from-Beyond]

There are more than 40 active peers listed, communication seems good.

Set "communicationLoggingMask" to "3", "pullThreshold" to "1" and "readTimeout"/"connectTimeout" to higher values. The log will show what is wrong.

[laowai80]

NEWS

On the 3rd of January the source code of basic features will be published for peer review. BCNext decided to make it more interesting to do a review, so the code will contain 3 security flaws - serious, critical and fatal ones. The 1st person who reports one of these flaws in a special thread will get a reward (1'000, 10'000 and 100'000 NXT accordingly). There will be SHA256 hashes of flaw descriptions published, the descriptions will be revealed after the flaws r reported. If some unreported ones left after 3 months, BCNext may decide to reveal them at any time.

PS: This has a nice side-effect, copycats have to wait for full disclosure or do their own research.

Is this still the plan? I mean the flaws.

[lophie]

Question from a new nxt/btc exchange (nxtchg.com) founder: "Guys, what's the best way to check a NXT address for incoming transactions without installing the client? Block explorer? Is there an API for this sort of thing? It's needed for automated NXT deposits.".

An exchange must host its own client. Any other way is insecure (at least now, when hallmark protection is not used for everything).

So tiring to code.... The one I am working on is without hot wallet and seek consensus over multiple self hosted highly hallmarked  nodes.

[dzarmush]

I see that the blockchain explorer server is down for 24h.
Does this mean that there will be no transactions between DGEX and our wallets for the next 24h?
Thanks

blockchain explorer is just a website with stats

[joefox]

I see that the blockchain explorer server is down for 24h.
Does this mean that there will be no transactions between DGEX and our wallets for the next 24h?
Thanks

No.  The two sites are completely unrelated and do not depend on each other.

[coolfish]

The account secret Phrase is dangerous! Even setting more than 60 characters and contains special symbols.

Imagine, when the future of NXT popular, maybe just one random password combination can open an random account.

[dzarmush]

The account secret Phrase is dangerous! Even setting more than 60 characters and contains special symbols.

Imagine, when the future of NXT popular, maybe just one random password combination can open an random account.

The sun will blow up sooner )

[MyZhre]

There are more than 40 active peers listed, communication seems good.

Set "communicationLoggingMask" to "3", "pullThreshold" to "1" and "readTimeout"/"connectTimeout" to higher values. The log will show what is wrong.

There are lot of logs like this:

[2013-12-30 16:28:36.539] "209.222.0.194": {"blockId":"9925845212617437891","requestType":"getNextBlocks"} >>> java.io.IOException: Premature EOF
[2013-12-30 16:29:14.248] "node3.nextcoin.it": {"blockId":"9925845212617437891","requestType":"getNextBlocks"} >>> java.io.IOException: Premature EOF
[2013-12-30 16:29:49.957] "209.222.0.194": {"blockId":"9925845212617437891","requestType":"getNextBlocks"} >>> java.io.IOException: Premature EOF
[2013-12-30 16:30:24.736] "64.237.37.148": {"blockId":"9925845212617437891","requestType":"getNextBlocks"} >>> java.io.IOException: Premature EOF
[2013-12-30 16:30:59.489] "209.222.0.194": {"blockId":"9925845212617437891","requestType":"getNextBlocks"} >>> java.io.IOException: Premature EOF

does this mean my blockchain file corrupted? I always restart nxt by Ctrl+C

[coolfish]

The account secret Phrase is dangerous! Even setting more than 60 characters and contains special symbols.

Imagine, when the future of NXT popular, maybe just one random password combination can open an random account.

The sun will blow up sooner )

Try traverse password dictionary, login, maybe can successfully enter some people's account..

[Come-from-Beyond]

Is this still the plan? I mean the flaws.

Yes.

[GröBkAz]

This coin needs more advertising.

[Come-from-Beyond]

The account secret Phrase is dangerous! Even setting more than 60 characters and contains special symbols.

Imagine, when the future of NXT popular, maybe just one random password combination can open an random account.

Isn't that cool? This is another step to Communism.

[Come-from-Beyond]

does this mean my blockchain file corrupted? I always restart nxt by Ctrl+C

This just means that ur peers r overloaded with requests.

[landomata]

This coin needs more advertising.

Pls help us do more

[zhangdu]

just one idea comes to my mind， one day， the nxt spread so widely， of course，price going up，1 nxt worth to piece of hamburger，but when i buy it，i have to pay the extra 1 nxt for the transaction fee. it's so bad!
is there anyone knows about after 3rd jan, the transaction fee will reduce or remain the same?