maybe they created it so they can control the world after NXT will have a billion of users
What for? They already has Bitcoin. They can attack it with their own ASICs, but they can't attack Nxt the same way.
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2426. (Read 2761629 times)
What for? They already has Bitcoin. They can attack it with their own ASICs, but they can't attack Nxt the same way.
Congratulations with a fortnight anniversary of Nxt to all !!
Especially to BCNext, the creator, and CfB, the helper of the creater.
Especially to BCNext, the creator, and CfB, the helper of the creater.
Do u think Nxt is already on their radars? 
I remember that story with BCNext ... Oh, wait, somebody knock on my door...
maybe they created it so they can control the world after NXT will have a billion of users
Is VPN necessary? Only hoster of 88.198.210.245 knows my name. And this is plain cheap VPS.
VPN is not really necessary, just another level of indirection for the extra paranoid. If your VPN provider and VPS host are even in different countries, you need an adversary of the rank of NSA to force both of them to cooperate, or to track you down by monitoring global internet traffic.Do u think Nxt is already on their radars?
I would like to setup a VPS but my skill level isn't that high, and I want to ensure my setup is 100% secure. Are you able to help me? I've never used linux before, and a windows VPS is more expensive, and maybe less stable for NXT from other user reports anyway. I'm thinking Digital Ocean is the best option, but am very open to other suggestions. I want to contribute towards making the network stable & secure.
thanks
thanks
Install CentOS 6 64 bit and send me IP and root password.
PM sent, thanks c-f-b
Is VPN necessary? Only hoster of 88.198.210.245 knows my name. And this is plain cheap VPS.
VPN is not really necessary, just another level of indirection for the extra paranoid. If your VPN provider and VPS host are even in different countries, you need an adversary of the rank of NSA to force both of them to cooperate, or to track you down by monitoring global internet traffic.Running Nxt over tor
I tried to run Nxt over tor using torsocks, but apparently this doesn't work for java. The way to tell java to use a socks proxy is to define socksProxyHost and socksProxyPort properties, in a system properties file or on the command line:
Replace 127.0.0.1 and 9050 with your tor host and socks port, if not default. Basically this is equivalent to the socks proxy options in the configuration of bitcoin-qt, if you use that.
You cannot use tor if you want to advertise a public IP or run a bootstrapping node, so only use it on your mining node, if you care about preserving your privacy. And you cannot hallmark a node ran behind tor, so if you are a stakeholder and want to contribute to the network stability, please consider running a separate publicly visible hallmarked node (and if you want to anonymize that one too, need to use a VPN which allows port forwarding and dynamic DNS).
I tried to run Nxt over tor using torsocks, but apparently this doesn't work for java. The way to tell java to use a socks proxy is to define socksProxyHost and socksProxyPort properties, in a system properties file or on the command line:
Code:
java -DsocksProxyHost=127.0.0.1 -DsocksProxyPort=9050 -Xmx1024M -jar start.jar
Replace 127.0.0.1 and 9050 with your tor host and socks port, if not default. Basically this is equivalent to the socks proxy options in the configuration of bitcoin-qt, if you use that.
You cannot use tor if you want to advertise a public IP or run a bootstrapping node, so only use it on your mining node, if you care about preserving your privacy. And you cannot hallmark a node ran behind tor, so if you are a stakeholder and want to contribute to the network stability, please consider running a separate publicly visible hallmarked node (and if you want to anonymize that one too, need to use a VPN which allows port forwarding and dynamic DNS).
Is VPN necessary? Only hoster of 88.198.210.245 knows my name. And this is plain cheap VPS.
Running Nxt over tor
I tried to run Nxt over tor using torsocks, but apparently this doesn't work for java. The way to tell java to use a socks proxy is to define socksProxyHost and socksProxyPort properties, in a system properties file or on the command line:
Replace 127.0.0.1 and 9050 with your tor host and socks port, if not default. Basically this is equivalent to the socks proxy options in the configuration of bitcoin-qt, if you use that.
You cannot use tor if you want to advertise a public IP or run a bootstrapping node, so only use it on your mining node, if you care about preserving your privacy. And you cannot hallmark a node ran behind tor, so if you are a stakeholder and want to contribute to the network stability, please consider running a separate publicly visible hallmarked node (and if you want to anonymize that one too, need to use a VPN which allows port forwarding and dynamic DNS).
I tried to run Nxt over tor using torsocks, but apparently this doesn't work for java. The way to tell java to use a socks proxy is to define socksProxyHost and socksProxyPort properties, in a system properties file or on the command line:
Code:
java -DsocksProxyHost=127.0.0.1 -DsocksProxyPort=9050 -Xmx1024M -jar start.jar
Replace 127.0.0.1 and 9050 with your tor host and socks port, if not default. Basically this is equivalent to the socks proxy options in the configuration of bitcoin-qt, if you use that.
You cannot use tor if you want to advertise a public IP or run a bootstrapping node, so only use it on your mining node, if you care about preserving your privacy. And you cannot hallmark a node ran behind tor, so if you are a stakeholder and want to contribute to the network stability, please consider running a separate publicly visible hallmarked node (and if you want to anonymize that one too, need to use a VPN which allows port forwarding and dynamic DNS).
I noticed one weird thing, seems like blacklisted peers just accumulate without ever being removed from the blacklist. I have other machines running Nxt, and their IPs were in the blacklist of fluke, even though they were up and running. This morning everything under active peers were zombies with 0 traffic. I removed peers.nxt and restarted, to clear the blacklist. And, on a machine without public IP address, all I see in active peers are the 3-4 well-know nodes. On another one that advertises its public IP, I do see nodes other than the well-known in the active peers list, but not that many. Is all that normal?
No, I think when I rewrite networking part completely this issue will go away.
Finally, please don't put both fluke.airdns.org and nxt.airdns.org in your well-known nodes list - those two point to the same IP, I only run one bootstrapping node, not two. I intended nxt.airdns.org to be used, but somehow another DDNS name I used before, fluke, leaked out and became more well-known.
Fixed.
Last night fluke.airdns.org didn't crash, so I hope the tcp tuning I did yesterday fixed it. There are almost no close_wait connections at the moment. This is what my /etc/sysctl.conf looks like now:
and I also have the open files limits increased to 400000 in /etc/security/limits.conf.
I noticed one weird thing, seems like blacklisted peers just accumulate without ever being removed from the blacklist. I have other machines running Nxt, and their IPs were in the blacklist of fluke, even though they were up and running. This morning everything under active peers were zombies with 0 traffic. I removed peers.nxt and restarted, to clear the blacklist. And, on a machine without public IP address, all I see in active peers are the 3-4 well-know nodes. On another one that advertises its public IP, I do see nodes other than the well-known in the active peers list, but not that many. Is all that normal?
Finally, please don't put both fluke.airdns.org and nxt.airdns.org in your well-known nodes list - those two point to the same IP, I only run one bootstrapping node, not two. I intended nxt.airdns.org to be used, but somehow another DDNS name I used before, fluke, leaked out and became more well-known.
Code:
net.ipv4.conf.default.rp_filter=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.tcp_syncookies=1
net.ipv4.conf.all.accept_redirects = 0
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.all.accept_source_route = 0
net.core.wmem_max=12582912
net.core.rmem_max=12582912
net.ipv4.tcp_rmem= 10240 87380 12582912
net.ipv4.tcp_wmem= 10240 87380 12582912
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1
net.ipv4.tcp_fin_timeout = 7
net.ipv4.tcp_max_syn_backlog = 16384
net.ipv4.tcp_synack_retries = 1
net.ipv4.tcp_tw_reuse = 1
net.ipv4.tcp_keepalive_intvl = 30
net.ipv4.tcp_keepalive_probes = 5
I noticed one weird thing, seems like blacklisted peers just accumulate without ever being removed from the blacklist. I have other machines running Nxt, and their IPs were in the blacklist of fluke, even though they were up and running. This morning everything under active peers were zombies with 0 traffic. I removed peers.nxt and restarted, to clear the blacklist. And, on a machine without public IP address, all I see in active peers are the 3-4 well-know nodes. On another one that advertises its public IP, I do see nodes other than the well-known in the active peers list, but not that many. Is all that normal?
Finally, please don't put both fluke.airdns.org and nxt.airdns.org in your well-known nodes list - those two point to the same IP, I only run one bootstrapping node, not two. I intended nxt.airdns.org to be used, but somehow another DDNS name I used before, fluke, leaked out and became more well-known.
I have a thought: Why Nxt use brain wallet? Maybe partly a solution for PoS forging security. As we know, PoS forging need to open the account, if we use the wallet file, the hot wallet security is vital for the user and there will be a lot virus trying to steal the wallet. Any comment?
NovaCoin uses secial RPC command "walletpassphrase" to unlock wallet temporary, in memory only, for PoS mining purposes. I have a thought: Why Nxt use brain wallet? Maybe partly a solution for PoS forging security. As we know, PoS forging need to open the account, if we use the wallet file, the hot wallet security is vital for the user and there will be a lot virus trying to steal the wallet. Any comment?
Again balance is broken. Another strange thing today - no blacklisted peers, all are known now 
What server do u use? Ur own?
I locked/unlocked account without restarting client - balance still zero, but peers now look ok.
Down? Hm, my local node is working without any issues.
My node doesn't work...When I write 88.198.210.245 only into wellKnownPeers it tries to find another nodes, blocks everything it found and nerver downloads even one block. It doesn't matter if I delete all .nxt files, or start with those you give me yesterday.
If I unlock my account, ir tries to generate block and orphaned it, and then again and again...
Well, u have to wait for 0.3.16.
Down? Hm, my local node is working without any issues.
My node doesn't work...When I write 88.198.210.245 only into wellKnownPeers it tries to find another nodes, blocks everything it found and nerver downloads even one block. It doesn't matter if I delete all .nxt files, or start with those you give me yesterday.
If I unlock my account, ir tries to generate block and orphaned it, and then again and again...
Again balance is broken. Another strange thing today - no blacklisted peers, all are known now
What server do u use? Ur own?
I would like to setup a VPS but my skill level isn't that high, and I want to ensure my setup is 100% secure. Are you able to help me? I've never used linux before, and a windows VPS is more expensive, and maybe less stable for NXT from other user reports anyway. I'm thinking Digital Ocean is the best option, but am very open to other suggestions. I want to contribute towards making the network stable & secure.
thanks
thanks
Install CentOS 6 64 bit and send me IP and root password.
Again balance is broken. Another strange thing today - no blacklisted peers, all are known now
@Come-from-Beyond: the network is officially down by the hacker(s), nxt.airdns.org and fluke.airdns.org are almost capturing all the nodes, Everytime I start, I get stuck at 9861 block and stay there ad infinitum. I have the same collection of txs on both my accounts, but see all kind of weird balances from 0 to 1 and sometimes -5 , no matter which account and which IP (I use a wireless dynamic IP based connection).
Please if you are not able to introduce a resolution during today 12/08/2013 , at least provide temporarily that client server you had for us to send some txs at initial days. I really need to send some txs and I really do not care the fuckkk about how insecure it might be to use your server (I've sold Nxt to some guys, their btc resides in my wallet, and I am fighting with the clients 3.13, 3.14 and now 3.15 for 3 days
)
Waiting for your reply, to see if I can send these guys their Nxt or should their BTC back!
Please if you are not able to introduce a resolution during today 12/08/2013 , at least provide temporarily that client server you had for us to send some txs at initial days. I really need to send some txs and I really do not care the fuckkk about how insecure it might be to use your server (I've sold Nxt to some guys, their btc resides in my wallet, and I am fighting with the clients 3.13, 3.14 and now 3.15 for 3 days
)Waiting for your reply, to see if I can send these guys their Nxt or should their BTC back!
Down? Hm, my local node is working without any issues. If u r a stakeholder u should buy VPS and follow the instruction for 0.3.15.
I would like to setup a VPS but my skill level isn't that high, and I want to ensure my setup is 100% secure. Are you able to help me? I've never used linux before, and a windows VPS is more expensive, and maybe less stable for NXT from other user reports anyway. I'm thinking Digital Ocean is the best option, but am very open to other suggestions. I want to contribute towards making the network stable & secure.
thanks
Jump to: