Could we implement that a node can only be connected to the network if an account is opened and has at least 1 Nxt ?
Also, don't laught since i have no coding background. Zombie node is the node connected to the network but having no account, right ? I understand that they could overwhelm a hall mark node, but do they pass on any information ? Educate me before BCNext and Cfb come in and release an update.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2232. (Read 2761638 times)
Yes, of course, the lowest recent average ping time make sense. It distributes the load most efficiently and automatically adjusts to each servers current load.
Best part is that it is very pseudo-random as the ping time between nodes is different for each node.
The Ddos'ers would have to spend the most resources to bog down a network like that!
James
Best part is that it is very pseudo-random as the ping time between nodes is different for each node.
The Ddos'ers would have to spend the most resources to bog down a network like that!
James
23394 2132153496119786677 martes, 24 de diciembre de 2013 1:18:57
3 8 + 3 397 B
1 6638148417768391106 5010202507 %
that's the right chain?
3 8 + 3 397 B
1 6638148417768391106 5010202507 %
that's the right chain?
it looks like overwhelmed to me. all dead connections going in. less than 10% green. before it could even make 20 minutes. 4gb ram and 2 cores.
I'm gonna destroy it and in the morning make an even more powerful one, and maybe increase the weight from 100
I'm gonna destroy it and in the morning make an even more powerful one, and maybe increase the weight from 100
.. hallmarking nodes is just a bad idea in my opinion. Instead of using hallmarked nodes to stay in sync, nodes should simply use other nodes with the lowest ping time.
- namely, zombie. 
funnily enough, my local install caught up really fast, in sync with my hallmarked node up to block 23537 then just froze there again
either just lost its connection, or its another bad fork.
either just lost its connection, or its another bad fork.
Either your hallmarked node became overwhelmed with requests or like you said, you downloaded a bad block and are now on a fork.
got you loud and clear.
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
No. All non-hallmarked VPS should be eliminated. They create additional and unneeded work for hallmarked nodes and provide no benefit to the network. If you start up a VPS, you should hallmark it.
But how does hallmarking help? besides taking all the bots? I had a hallmarked VPS up earlier and it had 800 connections, most with 0 weights
Im reseting a Hallmarked VPS with 4gb ram and 2cores. see it it does anything
https://162.243.214.183:7875/ set up and catching up.
If I understand 2Kool4Skewl correctly, your hallmark node can help the network by sharing a part of the attacks caused by zombie nodes. Non hall-mark node does not help since no peer sync the blockchain from a non-hallmark node and non hall-mark node can actually cause more stresses to the existing hall-mark nodes.
I think 2Kool4Skewl made a very good point here that no node should bear a over-sized responsibility to keep the network running since it would become a prime target for attackers. Now we have only a few hall-mark nodes bear major responsibility of spreading the blockchain. No wonder the network crumbles when they become targets.
You understand me correctly. This is exactly my point.
Would it be possible to allocate half the network load to hallmarked servers and half to non-hallmarked servers?
If there was a way to evenly split the traffic, then wouldn't that make it so that even if all the hallmarked servers are bogged down, the smaller servers would still be there as a backup. Not sure about how the network retry code is setup, but a random bit to choose hallmark or not hallmark, after initial timeout from hallmarked server. That way if the hallmarked servers are unmolested, the network takes advantage of the (presumably) faster hallmarked servers. If they are bogged down for whatever reason, they are only then expected to carry half the load.
If there was a way to update all the network as to the current percentage of requests being answered by the hallmarked servers (doesn't have to be totally precise), then that could be used to reduce the initial request to the hallmarked servers when their percentage goes below some threshold.
Forgive me if I am way off base, just guessing as to what the code must be doing
James
If there was a way to evenly split the traffic, then wouldn't that make it so that even if all the hallmarked servers are bogged down, the smaller servers would still be there as a backup. Not sure about how the network retry code is setup, but a random bit to choose hallmark or not hallmark, after initial timeout from hallmarked server. That way if the hallmarked servers are unmolested, the network takes advantage of the (presumably) faster hallmarked servers. If they are bogged down for whatever reason, they are only then expected to carry half the load.
If there was a way to update all the network as to the current percentage of requests being answered by the hallmarked servers (doesn't have to be totally precise), then that could be used to reduce the initial request to the hallmarked servers when their percentage goes below some threshold.
Forgive me if I am way off base, just guessing as to what the code must be doing
James
I'm sure that would be possible, but hallmarking nodes is just a bad idea in my opinion. Instead of using hallmarked nodes to stay in sync, nodes should simply use other nodes with the lowest ping time.
funnily enough, my local install caught up really fast, in sync with my hallmarked node up to block 23537 then just froze there again
either just lost its connection, or its another bad fork.
either just lost its connection, or its another bad fork.
Sending nxt: When I try to send from my account (which has plenty of nxt), I enter the recipient, the amount, and leave it as 24hrs deadline and click send and it says "confirmed" but then no nxt is deducted from my account and it seems like nothing happens. Anyone know what I'm doing wrong?
got you loud and clear.
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
No. All non-hallmarked VPS should be eliminated. They create additional and unneeded work for hallmarked nodes and provide no benefit to the network. If you start up a VPS, you should hallmark it.
But how does hallmarking help? besides taking all the bots? I had a hallmarked VPS up earlier and it had 800 connections, most with 0 weights
Im reseting a Hallmarked VPS with 4gb ram and 2cores. see it it does anything
https://162.243.214.183:7875/ set up and catching up.
If I understand 2Kool4Skewl correctly, your hallmark node can help the network by sharing a part of the attacks caused by zombie nodes. Non hall-mark node does not help since no peer sync the blockchain from a non-hallmark node and non hall-mark node can actually cause more stresses to the existing hall-mark nodes.
I think 2Kool4Skewl made a very good point here that no node should bear a over-sized responsibility to keep the network running since it would become a prime target for attackers. Now we have only a few hall-mark nodes bear major responsibility of spreading the blockchain. No wonder the network crumbles when they become targets.
got you loud and clear.
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
No. All non-hallmarked VPS should be eliminated. They create additional and unneeded work for hallmarked nodes and provide no benefit to the network. If you start up a VPS, you should hallmark it.
But how does hallmarking help? besides taking all the bots? I had a hallmarked VPS up earlier and it had 800 connections, most with 0 weights
Im reseting a Hallmarked VPS with 4gb ram and 2cores. see it it does anything
https://162.243.214.183:7875/ set up and catching up.
Hallmarking helps by taking workload off of other hallmarked servers. The larger balance the hallmarked node has, the higher priority it has with other peers. This is the reason you had 800 peers with 0 weights. They were attempting to connect to a hallmarked node to download the blockchain and sync. They behave like this regardless if the hallmarked node they are attempting to download from is in sync itself.
well getting that hallmark running did get me back online.
any other non trivial nxt holders that would like a VPS set up, please message me. I have a good budget right now from donated coins.
send me your hallmark and I will set you up
any other non trivial nxt holders that would like a VPS set up, please message me. I have a good budget right now from donated coins.
send me your hallmark and I will set you up
Would it be possible to allocate half the network load to hallmarked servers and half to non-hallmarked servers?
If there was a way to evenly split the traffic, then wouldn't that make it so that even if all the hallmarked servers are bogged down, the smaller servers would still be there as a backup. Not sure about how the network retry code is setup, but a random bit to choose hallmark or not hallmark, after initial timeout from hallmarked server. That way if the hallmarked servers are unmolested, the network takes advantage of the (presumably) faster hallmarked servers. If they are bogged down for whatever reason, they are only then expected to carry half the load.
If there was a way to update all the network as to the current percentage of requests being answered by the hallmarked servers (doesn't have to be totally precise), then that could be used to reduce the initial request to the hallmarked servers when their percentage goes below some threshold.
Forgive me if I am way off base, just guessing as to what the code must be doing
James
If there was a way to evenly split the traffic, then wouldn't that make it so that even if all the hallmarked servers are bogged down, the smaller servers would still be there as a backup. Not sure about how the network retry code is setup, but a random bit to choose hallmark or not hallmark, after initial timeout from hallmarked server. That way if the hallmarked servers are unmolested, the network takes advantage of the (presumably) faster hallmarked servers. If they are bogged down for whatever reason, they are only then expected to carry half the load.
If there was a way to update all the network as to the current percentage of requests being answered by the hallmarked servers (doesn't have to be totally precise), then that could be used to reduce the initial request to the hallmarked servers when their percentage goes below some threshold.
Forgive me if I am way off base, just guessing as to what the code must be doing
James
Somebody knows why http://coinmarketcap.com/ has removed NXT from their list? it was in the 4th or 5th position some hours ago.
It sounds like it was pulling its price from dgex.com API and there was some problems with that.
I don't think that coinmarketcap is an editorial list, it seems like pure data.
Somebody knows why http://coinmarketcap.com/ has removed NXT from their list? it was in the 4th or 5th position some hours ago.
got you loud and clear.
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
No. All non-hallmarked VPS should be eliminated. They create additional and unneeded work for hallmarked nodes and provide no benefit to the network. If you start up a VPS, you should hallmark it.
But how does hallmarking help? besides taking all the bots? I had a hallmarked VPS up earlier and it had 800 connections, most with 0 weights
Im reseting a Hallmarked VPS with 4gb ram and 2cores. see it it does anything
https://162.243.214.183:7875/ set up and catching up.
got you loud and clear.
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
No. All non-hallmarked VPS should be eliminated. They create additional and unneeded work for hallmarked nodes and provide no benefit to the network. If you start up a VPS, you should hallmark it.
got you loud and clear.
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
tell me should I set up VPS and not hallmarked? I can get 5 online in 15 minutes
these forks are getting so frustrating. I know the ddos is messing us up but its next to impossible to get anywhere on the blockchain tonight.
I killed the 5 VPS I had set up seeing as nothing is working. I will gladly set them up again if we determine this to be useful.
I tried deleting the blocks and transactions and then I'm stuck on block 1. we are frozen.
hope 0.4.XX is the answer
I killed the 5 VPS I had set up seeing as nothing is working. I will gladly set them up again if we determine this to be useful.
I tried deleting the blocks and transactions and then I'm stuck on block 1. we are frozen.
hope 0.4.XX is the answer
Once a node downloads a bad block, it seems to require a complete re-download of the blockchain to get back in sync.
Hey i am seeing that, but if I trash the blocks and transactions, I'm not getting ANYTHING from the network. Sits at block 1
in my nxt folder, the blocks.nxt and transactions.nxt are time stamped to the current time, but the blockchain is stuck at 3 hours ago
This is probably because you are unsuccessfully attempting to download the blockchain from hallmarked nodes, but these nodes are currently under DDoS attack and cannot fulfill your request. There are other nodes, which are not hallmarked and are up-to-date, but due to the hallmark code, your node prioritize it's request to hallmarked nodes. This is why you are not connecting to other nodes which could fulfill your request.
Jump to: