NXT :: descendant of Bitcoin - Updated Information

[Sharky444]

It still makes sense to sell at these low prices to make the holder base and the network stronger.

[1715019891]

1715019891

[1715019891]

1715019891

[1715019891]

1715019891

[Come-from-Beyond]

It still makes sense to sell at these low prices to make the holder base and the network stronger.

+1

But leave a few coins for urself, so u won't blame urself after other features released and price skyrockets.

[Come-from-Beyond]

Well, good news my VPS has been running the app with no crashes since the last update and the block number seems accurate.

The only problem, one that I haven't been able to resolve, is the blacklisting of peers. I've got 8 Active peers and 41 Blacklisted. Is there any way you can quickly implement something to periodically clear the blacklist? I've got a clock sync running on a cron-job to periodically sync the clock, this didn't help.

These are the only ports I have open: 7874, 7875, 80 (forwards to 7875) all TCP.

Stop client. Delete peers.nxt. Start client.

[Come-from-Beyond]

What is the difference between the windows Client and the online wallet http://88.198.210.245:7875/? Did I just need a Password to access the wallet? what is of different people use the same password (secret phrase)?

If they use the same password they will share the account. LOL

Local client is better. Online wallet is insecure.

[Come-from-Beyond]

Published mining and blockchain downloading source code.

[inkadnb]

Well, good news my VPS has been running the app with no crashes since the last update and the block number seems accurate.

The only problem, one that I haven't been able to resolve, is the blacklisting of peers. I've got 8 Active peers and 41 Blacklisted. Is there any way you can quickly implement something to periodically clear the blacklist? I've got a clock sync running on a cron-job to periodically sync the clock, this didn't help.

These are the only ports I have open: 7874, 7875, 80 (forwards to 7875) all TCP.

Stop client. Delete peers.nxt. Start client.

Can you not make this part of the client? I'm thinking long-term here..

[Come-from-Beyond]

Can you not make this part of the client? I'm thinking long-term here..

Well, in long-term blacklisting should be used. It's just a list of peers that were offline when u tried to connect to them. In a week u may decide to unblacklist them and try to connect again. I see nothing wrong with this approach.

[inkadnb]

Can you not make this part of the client? I'm thinking long-term here..

Well, in long-term blacklisting should be used. It's just a list of peers that were offline when u tried to connect to them. In a week u may decide to unblacklist them and try to connect again. I see nothing wrong with this approach.

It just seems like unnecessary maintenance that could be automated. Why not traverse through the blacklist every 30 minutes or so and see if you can connect to them?

Most users aren't going to want to maintain the blacklist, and they shouldn't need to.

[Come-from-Beyond]

Can you not make this part of the client? I'm thinking long-term here..

Well, in long-term blacklisting should be used. It's just a list of peers that were offline when u tried to connect to them. In a week u may decide to unblacklist them and try to connect again. I see nothing wrong with this approach.

It just seems like unnecessary maintenance that could be automated. Why not traverse through the blacklist every 30 minutes or so and see if you can connect to them?

Most users aren't going to want to maintain the blacklist, and they shouldn't need to.

Maybe u r right. BCNext has his own ideas and usually they look strange. At the moment this issue is not in the high-priority list.

[Come-from-Beyond]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

[klee]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Sure - if you help me out!
What do we need to do?

[Come-from-Beyond]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Sure - if you help me out!
What do we need to do?

Owners of nodes that r accessible from the Internet should just PM me with their static IPs/domains.

[inkadnb]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Yes, nxt.c4c.io

[Come-from-Beyond]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Yes, nxt.c4c.io

Thx.

BTW, post ur IPs here, so I don't need to resend them to BCNext.

[inkadnb]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Yes, nxt.c4c.io

Thx.

BTW, post ur IPs here, so I don't need to resend them to BCNext.

Do clients automatically do reverse DNS lookup before broadcast? I noticed that on other clients it doesn't show "nxt.c4c.io" on announced address.

[Come-from-Beyond]

Do clients automatically do reverse DNS lookup before broadcast? I noticed that on other clients it doesn't show "nxt.c4c.io" on announced address.

I don't know. Let's wait when source code of peer connection revealed. This will happen soon.

[nexern]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Sure - if you help me out!
What do we need to do?

Owners of nodes that r accessible from the Internet should just PM me with their static IPs/domains.

-> 87.230.14.1

question to the java pros here.
with the latest version the nulllpointerexeptions are gone which is fine.
but still having many ReadPendingException, ClosedChannelException, IOException
and stuff like this, which leads into many freezes when using the api intense.
already tested different socket libs (libcurl, native socket and even via piped wget commandline)
and different java versions (openjdk/sun) to access the api with no difference.

starting the client with bigger heap size doesn't work either.
instead adding more features to the blockchain explorer i am busy coding
workarounds for this which bothers me a little.
(the last days i wished bcnext would have coded the client in plain ansi c instead java)

the client is running on a lean debian server, so this shouldn't be the reason
but a final check could be to change the os, perhaps the *java-diva* ;-) needs
something different. any further ideas i could look into?

edit: an api-errorcode listing would be nice to.

[dr_yan_yan]

I had problems with the Blocks and such not updating when I went to the new Client version.
Tried it a couple of times etc. without any luck.

Deleted the peers list... now I have only 3 peers.
88.198.210.245      88.198.210.245      0 B      34 B      -   
146.185.168.142      146.185.168.142      0 B      18 B      -   
162.243.145.83      162.243.145.83      0 B      50 B      -   

But seems it does not connect to them.
I opened up port 7874, but still nothing. Looks like i am sending, but not receiving anything.
And no other Peers are showing up  (previously there were 15 accepted, 30 blacklisted)

[Come-from-Beyond]

I had problems with the Blocks and such not updating when I went to the new Client version.
Tried it a couple of times etc. without any luck.

Deleted the peers list... now I have only 3 peers.
88.198.210.245      88.198.210.245      0 B      34 B      -   
146.185.168.142      146.185.168.142      0 B      18 B      -   
162.243.145.83      162.243.145.83      0 B      50 B      -   

But seems it does not connect to them.
I opened up port 7874, but still nothing. Looks like i am sending, but not receiving anything.
And no other Peers are showing up  (previously there were 15 accepted, 30 blacklisted)

Time/timezone issue.

[Come-from-Beyond]

We need more bootstrapping peers, the old ones went offline. Anyone wants to become a well-known peer with blue balloon next to its address?

Sure - if you help me out!
What do we need to do?

Owners of nodes that r accessible from the Internet should just PM me with their static IPs/domains.

-> 87.230.14.1

question to the java pros here.
with the latest version the nulllpointerexeptions are gone which is fine.
but still having many ReadPendingException, ClosedChannelException, IOException
and stuff like this, which leads into many freezes when using the api intense.
already tested different socket libs (libcurl, native socket and even via piped wget commandline)
and different java versions (openjdk/sun) to access the api with no difference.

starting the client with bigger heap size doesn't work either.
instead adding more features to the blockchain explorer i am busy coding
workarounds for this which bothers me a little.
(the last days i wished bcnext would have coded the client in plain ansi c instead java)

the client is running on a lean debian server, so this shouldn't be the reason
but a final check could be to change the os, perhaps the *java-diva* ;-) needs
something different. any further ideas i could look into?

edit: an api-errorcode listing would be nice to.

BCNext gave me a new version that is supposed to fix problem related to direct buffers issue. It's a fix for peer connections only, if it works he will do the same for bots (API). I hope this will solve ur problem and no workaround will be necessary. I'm testing/profiling it now.

I had the list of codes somewhere, give me 5 mins.