NXT :: descendant of Bitcoin - Updated Information

[gbeirn]

When i ping dgex.com i get IP address 200.35.149.26

When i enter that IP address as URL in my browser i get the homepage of http://dunecom.com/
Is this an indication dgex is hacked 

Could someone try the same and confirm?

An nslookup gives me the same IP, I assume it's the hosting company they use

Is there a way to verify?

http://whois.net/whois/dgex.com

http://whois.net/whois/dunecom.com

[Come-from-Beyond]

Things like that are not supposed to happen. Perhaps I was on a forked, fake chain?

Try F5 next time.

[davethetrousers]

edumacated kids with loads of high potency cannabis

Seems legit. I had unusual network loads earlier today from somewhere in Amsterdam

Add a node from every nxtbase region?

node1.nxtbase.com; node11.nxtbase.com; node21.nxtbase.com; node31.nxtbase.com; node41.nxtbase.com; node51.nxtbase.com; node61.nxtbase.com; node71.nxtbase.com; node81.nxtbase.com; node91.nxtbase.com;

These just went into the server list for The Update Script.

[Pablito89]

Adding well know peers in your web.xml increase your chances to be on real main blockchain at any moment

Instructions:
1- Close your java process (if it's running)
2- Go to the following directory nxt/webapps/root/WEB-INF/
3- Open web.xml with a text editor
4- find this line:

Code:

<param-name>wellKnownPeers</param-name>

5- into the following lane copy/paste the easyCopyString between <param-value>HERE</param-value>
6- it will looks like:

Code:

<param-name>wellKnownPeers</param-name>
<param-value>87.230.14.1; 46.19.137.116; 95.85.22.142; 162.243.214.183; scum2.bounceme.net; 162.243.213.115; node11.nxtbase.com; 78.46.63.221; scum5.bounceme.net; scum4.bounceme.net; vps5.nxtcrypto.org; node16.nxtbase.com; scum.bounceme.net; scum2.bounceme.net; scum5.bounceme.net; scum6.bounceme.net</param-value>

7- save
8- restart next java process

UPDATED easyCopyString:
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.nxtcrypto.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.nextcoin.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; node31.nxtbase.com; node41.nxtbase.com; node51.nxtbase.com; node61.nxtbase.com; node71.nxtbase.com; node81.nxtbase.com; node91.nxtbase.com; 85.214.222.82;

Vps Owners: keep updated the easycopystring adding your nodes!!!!

[superresistant]

Has anyone taken a look at the ip addresses of the attackers? Are they hiding behind TOR?

Some of them were hosted in universities.

edumacated kids with loads of free time + High bandwidth provided by uni's + high potency cannabis/alcohol/nose-candy = attack Nxt? Sounds about right.

What they don't realise is that they are making NXT much stronger.

Haha this is great !

I failed to pass the test in the 1st time. I think I should take a break...

You need to sleep once per 24h. Do it for NXT.

[garp]

@dgex.com:
"DGEX is performing server migration. Trading should be online by 11:00 PM GMT. Thank you for your patience. (Flush your DNS to access the new server sooner)."

Ah, that long?

[ZeroTheGreat]

ZeroTheGreat, remember that those are upper bounds on forge time.

A wallet that is unlocked 24/7 on an always up-to-date server will forge a block more often, because of the large portion of all NXT currently in locked accounts, lagging/stuck nodes (temporary phenomenon atm, though) etc.

No, that feature postponed. If 900M locked, 100M now'll forge like 100M. Later we'll have to say "200k unfrozen equivalent coins", and full amount can be any. Multiplier unthinkable now.

[laowai80]

What they don't realise is that they are making NXT much stronger.

Yeah, it's simply stupid to DDoS the exchange, users can't even panic sell, they are stuck with their coins, even if they wanted to give it all up and sell, they can't

[davethetrousers]

ZeroTheGreat, remember that those are upper bounds on forge time.

A wallet that is unlocked 24/7 on an always up-to-date server will forge a block more often, because of the large portion of all NXT currently in locked accounts, lagging/stuck nodes (temporary phenomenon atm, though) etc.

No, that feature postponed. If 900M locked, 100M now'll forge like 100M. Later we'll have to say "200k unfrozen equivalent coins", and full amount can be any. Multiplier unthinkable now.

Really? That would mean that when 90% NXT are locked, forging would only go on at 10% speed. Sounds strange to me.

[ZeroTheGreat]

I really like the basic concept and nxt and I also hold some but damn the forging is not worth at all. On a side note: I hate Java so hard.

Forging = 95% supporting concept + 5% business. Smth like that for now.

[ZeroTheGreat]

DGEX :: descendant of MTGOX -

 

Unwanted child )))

[gbeirn]

@dgex.com:
"DGEX is performing server migration. Trading should be online by 11:00 PM GMT. Thank you for your patience. (Flush your DNS to access the new server sooner)."

Ah, that long?

Only 5 and a half hours.

[ZeroTheGreat]

Question on forging:

Say I have 100K Nxt. One simple case is to forge to get tx fee in a single account, and the other case is to distribute those 100K Nxt into 5 account with each one 20K Nxt and forge with those 5 account at the same time. So do they have exactly the same probability for forging for a block?

Same EV, different dispersion (so foring pool reasonable in future).

[davethetrousers]

@dgex.com:
"DGEX is performing server migration. Trading should be online by 11:00 PM GMT. Thank you for your patience. (Flush your DNS to access the new server sooner)."

Ah, that long?

Only 5 and a half hours.

Price will dance all over the place right after restart.

Later on it will be more smooth than ever, if the new server is actually better than before.

[TwinWinNerD]

ZeroTheGreat, remember that those are upper bounds on forge time.

A wallet that is unlocked 24/7 on an always up-to-date server will forge a block more often, because of the large portion of all NXT currently in locked accounts, lagging/stuck nodes (temporary phenomenon atm, though) etc.

No, that feature postponed. If 900M locked, 100M now'll forge like 100M. Later we'll have to say "200k unfrozen equivalent coins", and full amount can be any. Multiplier unthinkable now.

Really? That would mean that when 90% NXT are locked, forging would only go on at 10% speed. Sounds strange to me.

I really doubt that too! We are not too far of 1 Block/minute. So something doesnt compute here.

I guess it is like this now:

(Coins you forge with)/(total coins forging) = % change of creating the next block

[rickyjames]

I have a gap in my knowledge so I'm gonna ask a dumb question.  Just what IS the difference between a node up in the cloud and a peer running as a desktop (or Pi) client??  

We've got all these VPNs set up all over the world now - ferment alone has set up almost 100 - and these are "nodes".  They are all running the NXT 0.4.7e Java server software.  They are forging blocks.  Yet if I look at the "peer" list on my desktop client (where I have actually generated 9 blocks myself so far the past couple of days) I only see 52 "online peers".  If the "nodes" are generating "blocks" too, why aren't they considered "peers" as well and show up in the online "peer" list?  

I note one of the most prolific block generators is 4747512364439223888, a 50,000,000+ NXT account that has generated 3304 blocks so far, earning 56,290 NXT in fees.  Yet this chap  doesn't show up at all in the "online peer" list, which for me only lists two multi-million NXT accounts out of 54 as forging blocks : 78:46:63:221 at 6.6 million NXT and vps07.nxtcrypto.org with 2.1 million.   Somebody looking at just his desktop client with his minimum 10 NXT in it hoping to forge a block not only is at the back of the pack statistically speaking, he can't even see the front of the pack.

Am I missing something here?  Any elaboration somebody feels like sharing would be appreciated, thanks.

[TwinWinNerD]

I have a gap in my knowledge so I'm gonna ask a dumb question.  Just what IS the difference between a node up in the cloud and a peer running as a desktop (or Pi) client??  

We've got all these VPNs set up all over the world now - ferment alone has set up almost 100 - and these are "nodes".  They are all running the NXT 0.4.7e Java server software.  They are forging blocks.  Yet if I look at the "peer" list on my desktop client (where I have actually generated 9 blocks myself so far the past couple of days) I only see 52 "online peers".  If the "nodes" are generating "blocks" too, why aren't they considered "peers" as well and show up in the online "peer" list?  

I note one of the most prolific block generators is 4747512364439223888, a 50,000,000+ NXT account that has generated 3304 blocks so far, earning 56,290 NXT in fees.  Yet this chap  doesn't show up at all in the "online peer" list, which only lists two multi-million NXT accounts out of 54 as forging blocks : 78:46:63:221 at 6.6 million NXT and vps07.nxtcrypto.org with 2.1 million.   Somebody looking at just his desktop client with his minimum 10 NXT in it hoping to forge a block not only is at the back of the pack statistically speaking, he can't even see the front of the pack.

Am I missing something here?  Any elaboration somebody feels like sharing would be appreciated, thanks.

There are active peers and known peers. If your client runs long enough, you will see EVERYONE forging as an known peer.

EDIT: haha someone launched a node called giantdildo

[gbeirn]

I have a gap in my knowledge so I'm gonna ask a dumb question.  Just what IS the difference between a node up in the cloud and a peer running as a desktop (or Pi) client??  

We've got all these VPNs set up all over the world now - ferment alone has set up almost 100 - and these are "nodes".  They are all running the NXT 0.4.7e Java server software.  They are forging blocks.  Yet if I look at the "peer" list on my desktop client (where I have actually generated 9 blocks myself so far the past couple of days) I only see 52 "online peers".  If the "nodes" are generating "blocks" too, why aren't they considered "peers" as well and show up in the online "peer" list?  

I note one of the most prolific block generators is 4747512364439223888, a 50,000,000+ NXT account that has generated 3304 blocks so far, earning 56,290 NXT in fees.  Yet this chap  doesn't show up at all in the "online peer" list, which only lists two multi-million NXT accounts out of 54 as forging blocks : 78:46:63:221 at 6.6 million NXT and vps07.nxtcrypto.org with 2.1 million.   Somebody looking at just his desktop client with his minimum 10 NXT in it hoping to forge a block not only is at the back of the pack statistically speaking, he can't even see the front of the pack.

Am I missing something here?  Any elaboration somebody feels like sharing would be appreciated, thanks.

There are active peers and known peers. If your client runs long enough, you will see EVERYONE forging as an known peer.

EDIT: haha someone launched a node called giantdildo

Correct, every computer running NRS will show up eventually as long as they aren't behind a NAT. The reason for all the nodes we setup is to ensure there are a steady supply of nodes that are full open and accessible to everyone (i.e. not behind a NAT/firewall, running 24x7)

[rickyjames]

There are active peers and known peers. If your client runs long enough, you will see EVERYONE forging as an known peer.

So does this mean that some who are listed in the known peer list on a particular desktop client are actually active peers, and the given desktop client hasn't figured that out yet?  Just how long does it take for a desktop client to sync up and see all of these new VPSs out there on the cloud?

[TwinWinNerD]

There are active peers and known peers. If your client runs long enough, you will see EVERYONE forging as an known peer.

So does this mean that some who are listed in the known peer list on a particular desktop client are actually active peers, and the given desktop client hasn't figured that out yet?  Just how long does it take for a desktop client to sync up and see all of these new VPSs out there on the cloud?

no, that means, that node chose to only take these nodes as active peers. The number of active peers is limited and the peers are chosen randomly if i am not mistaken.

So you will be an active peer somewhere