Austria will be the capital of NXT hahahaha
91.115.213.16
with:
24089 518 %
Donations welcome at: 16134099701168321966
Love this Project
Topic: NXT :: descendant of Bitcoin - Updated Information - page 2204. (Read 2761629 times)
Just setup another Node that works fine with NRS 0.4.4
Austria will be the capital of NXT hahahaha
91.115.213.16
with:
24089 518 %
Donations welcome at: 16134099701168321966
Love this Project
Austria will be the capital of NXT hahahaha
91.115.213.16
with:
24089 518 %
Donations welcome at: 16134099701168321966
Love this Project
Working on node infrastructure with a full redesign of nxtbase to support 100+. I won't open source my new management stuff for a bit, but here's a handy one for you VPSers running ubuntu.
will it work on debian 7 x64?Code:
$ sudo apt-get install --yes supervisor
$ sudo service supervisor restart
$ sudo service supervisor restart
It should. Let us know!
i got the supervisor thing installed. do i also need to install nxtbase or what? where does my web.xml go?
+1. I'm liking a lot how the community rallied back from the attack stronger than ever.
Don't relax too much. The storm is imminent...
Good point. We mustn't be complacent and should keep trying to strengthen the network.
When using the API, what's the difference between balance and effectiveBalance?
My effectiveBalance still shows 0 even though have over 3000 coins in my balance and the associated transactions have around 400 confirms. This is what I'm seeing exactly:
{"balance":325200,"effectiveBalance":0,"unconfirmedBalance":325200}
"unconfirmedBalance" is the balance minus all unconfirmed sent transactions. It doesn't include double-spending and unconfirmed received transactions. A user sees the unconfirmed balance in the client. My effectiveBalance still shows 0 even though have over 3000 coins in my balance and the associated transactions have around 400 confirms. This is what I'm seeing exactly:
{"balance":325200,"effectiveBalance":0,"unconfirmedBalance":325200}
+1. I'm liking a lot how the community rallied back from the attack stronger than ever.
Don't relax too much. The storm is imminent...
Guys and hopefully some gals too keep building more nodes.
We don't have much time until the next big DDOS.
keep building more nodes.We don't have much time until the next big DDOS.
When using the API, what's the difference between balance and effectiveBalance?
My effectiveBalance still shows 0 even though have over 3000 coins in my balance and the associated transactions have around 400 confirms. This is what I'm seeing exactly:
{"balance":325200,"effectiveBalance":0,"unconfirmedBalance":325200}
My effectiveBalance still shows 0 even though have over 3000 coins in my balance and the associated transactions have around 400 confirms. This is what I'm seeing exactly:
{"balance":325200,"effectiveBalance":0,"unconfirmedBalance":325200}
0.4.4 seems to solve my problems!
Yeah, CfB delivers! We get new features and settings as promised!
Actually, I think it's coz we added more nodes.
Looks like we dodged a bullet there. This was like a stresstest and we beat it =)
Gj us all!
+1. I'm liking a lot how the community rallied back from the attack stronger than ever.
0.4.4 seems to solve my problems!
Yeah, CfB delivers! We get new features and settings as promised!
Actually, I think it's coz we added more nodes.
Looks like we dodged a bullet there. This was like a stresstest and we beat it =)
Gj us all!
im a bit paranoid about security. i have 7874 open from the router does this pose any risk?
can in any way my coins be stolen while forging cause i have a pc forging 24/7?
is there any downside of not opening this port? blocks seem to download normally with closed
can in any way my coins be stolen while forging cause i have a pc forging 24/7?
is there any downside of not opening this port? blocks seem to download normally with closed
0.4.4 seems to solve my problems!
Yeah, CfB delivers! We get new features and settings as promised!
Actually, I think it's coz we added more nodes.
0.4.4 seems to solve my problems!
Yeah, CfB delivers! We get new features and settings as promised!
Putting aside the current client implementation, is it theoretically possible within the API for a node to have enough information to forge/sign a block, but not enough to do anything with the contents of the account (e.g. transfer funds to another account)?
In future it will be possible to "freeze" an account using multi-sig feature. U can forge but can't do transactions.
But Active peers tab shows only 14 nodes. Is that not too low? Is the reason - the hallmark protection?
The reason is low value of maxNumberOfConnectedPublicPeers. It was 20, I set it to 10 in 0.4.4. U can see 14 active peers if 4 of them were with red flags at some moment.
Ok, clear now.
24063 5154541454348994634 Dienstag, 24. Dezember 2013 20:54:25
1 0 + 1 140 B
1 9348240326299815071 190 %
had some problems with my node, should be back fine now
0.4.4 seems to solve my problems!
1 0 + 1 140 B
1 9348240326299815071 190 %
had some problems with my node, should be back fine now
0.4.4 seems to solve my problems!
But Active peers tab shows only 14 nodes. Is that not too low? Is the reason - the hallmark protection?
The reason is low value of maxNumberOfConnectedPublicPeers. It was 20, I set it to 10 in 0.4.4. U can see 14 active peers if 4 of them were with red flags at some moment.
Quote
CfB has mentioned that if one gets access to the memory of Java Virtual Machine then your passphrase would be exposed.
Quote
That makes forging a *very* risky endeavor!
Wouldn't a big stakeholder have to have the biggest balls in the world to forge? Everyone knows their IP. Does everyone know their account number (and balance) if they're forging? If so, they're a massive target with a huge reward.
To me, this seems key. Has it been addressed?
Putting aside the current client implementation, is it theoretically possible within the API for a node to have enough information to forge/sign a block, but not enough to do anything with the contents of the account (e.g. transfer funds to another account)?
It's better to copy files. Imagine what will happen if everyone deletes the blockchain simultaneously.
Ok, I'll update the guide.
So copying the .bak versions is the proper way?
No. U must copy *.nxt files. Use *.bak only if *.nxt corrupted.
Ok, I am just trying to set up a simple guide for users who can't operate in linux at all, so too many options would look too complicated.
One observation.
I downloaded a fresh version of NXT to my home PC, installed with default settings, blockchain synced from 0, all good.
But Active peers tab shows only 14 nodes. Is that not too low? Is the reason - the hallmark protection?
It's better to copy files. Imagine what will happen if everyone deletes the blockchain simultaneously.
Ok, I'll update the guide.
So copying the .bak versions is the proper way?
No. U must copy *.nxt files. Use *.bak only if *.nxt corrupted.
Working on node infrastructure with a full redesign of nxtbase to support 100+.
I'm going to add trusted peers list next to well-known peers. U'll be able to create a mini-cluster that shares all the data. Need to think how to implement it in the best way though.
wellKnownPeers is getting a little crowded with 30 names! I'm interested in this cluster idea.
Jump to: