So what is the most sensible solution?
We are discussing right now what we should discuss. Don't rush things.
Ahahah
I don't want to rush anything, but the solution is simple .. Ps: sorry if I seem a little hasty
Topic: NXT :: descendant of Bitcoin - Updated Information - page 688. (Read 2761645 times)
We are discussing right now what we should discuss. Don't rush things.
Ahahah
I don't want to rush anything, but the solution is simple .. Ps: sorry if I seem a little hasty
please send some testNxt: 17102884928221738157
- 5k testNXT sent.hi abctc, do you have some testnxt left? -> 9998590259914237067
thx
If you have your node running, but don't have any NXT, you are not securing the blockchain.
This is why the NXTcoins will payout dividends in NXT. for a signing bonus, I will probably just seed every miner with 1 NXTJames, please do not build upon false statements.
? What false statements. What do you think I am saying?
We are searching for the right incentives for:
- running a node (this secures the network)
- running a node, have an open nxt account and forging with it (this secures the security of nxt = 90% attacks ?!) DONE by TF.
- running a node (this secures the network)
FIFY.
I think we shouldn't ignore the second point in our discussion since we need forging nodes. You say it is "done by TF" but TF only is the mechanism which saves us from 51% attacks. But we still need to talk about incentives for forging.
We are searching for the right incentives for:
- running a node (this secures the network)
- running a node, have an open nxt account and forging with it (this secures the security of nxt = 51% attacks ?!) DONE by TF.
- running a node (this secures the network)
FIFY.
Even with transparent forging, Nxt is still susceptible to 90% PoS attacks.
Somebody buys up all the NXT.
I raised this, but CfB said is was acceptable
Yes. It would be very hard to mount this attack, because you would have to own 90% of the currency.
Don't forget that some people just won't sell.
Everybody has their price
HODL
So what is the most sensible solution?
We are discussing right now what we should discuss. Don't rush things.
yes.. we're searching to a donations/bounties to run a node .. or to forge ( help the Nxt server ) .
I think this is a bad idea. Either the network/nxt itself can care of or this will fail.
but if we want more nodes, and people can not create new ones because it has no budget .. how do we support the Nxt ?
This is a part of the whole discussion, my friend
https://bitcointalksearch.org/topic/m.5355317
We are searching for the right incentives for:
- running a node (this secures the network)
- running a node, have an open nxt account and forging with it (this secures the security of nxt = 51% attacks ?!) DONE by TF.
- running a node (this secures the network)
FIFY.
Even with transparent forging, Nxt is still susceptible to 90% PoS attacks.
Somebody buys up all the NXT.
I raised this, but CfB said is was acceptable
Yes. It would be very hard to mount this attack, because you would have to own 90% of the currency.
Don't forget that some people just won't sell.
Everybody has their price
yes.. we're searching to a donations/bounties to run a node .. or to forge ( help the Nxt server ) .
I think this is a bad idea. Either the network/nxt itself can care of or this will fail.
but if we want more nodes, and people can not create new ones because it has no budget .. how do we support the Nxt ?
This is a part of the whole discussion, my friend
So what is the most sensible solution?
Hey guys,
To those that have tried my web client http://nxtra.org/nxt-client ; A beta version is now available for download here:
http://nxtra.org/nxt-client/dev.zip
Unzip, move the dev folder to nxt/html/tools/dev
Then go to http://localhost:7876/dev
This is assuming you have 0.8.1e installed (it will not work correctly on older versions!) - do not try
I suggest you connect to TestNet first though; in the upper left corner you can switch between TestNet and localhost. Try everything out in TestNet first, when you are comfortable you can connect locally. There may still be errors in the code, it's a beta after all.
Not everything is done yet, and Internet Explorer is completely untested. I suggest you use either chrome/firefox or safari for now.
Also need to do some more interactive updating after submission of forms, etc.
if you want, you can send me a message there via the alias wesleynxt (just open the send message dialog and type wesleynxt in the account field). Messages are not yet encrypted.
Let me know what you think.
To those that have tried my web client http://nxtra.org/nxt-client ; A beta version is now available for download here:
http://nxtra.org/nxt-client/dev.zip
Unzip, move the dev folder to nxt/html/tools/dev
Then go to http://localhost:7876/dev
This is assuming you have 0.8.1e installed (it will not work correctly on older versions!) - do not try
I suggest you connect to TestNet first though; in the upper left corner you can switch between TestNet and localhost. Try everything out in TestNet first, when you are comfortable you can connect locally. There may still be errors in the code, it's a beta after all.
Not everything is done yet, and Internet Explorer is completely untested. I suggest you use either chrome/firefox or safari for now.
Also need to do some more interactive updating after submission of forms, etc.
if you want, you can send me a message there via the alias wesleynxt (just open the send message dialog and type wesleynxt in the account field). Messages are not yet encrypted.
Let me know what you think.
I have the active 0.8.1.e client and I can not connect through the client file :/ / / C :/ nxt / html / tools / dev / dev / index.html #
You should put it at tools/dev not tools/dev/dev (but it shouldn't matter).
You are acessing it through http://localhost:7876/dev/ right? Do not double click on index.html as it will open via file:// which does not work.
Go! Google Chrome could not find the page localhost: 7876.
Have you just clicked the link here:
http://localhost:7876/dev/
That should work, otherwise your java may not be running. Check if http://localhost:7875 works
Anyway, I'm off, will answer questions later.
Go! Google Chrome could not find the page localhost: 7875
java is working because nrs client 8.0.1e is working well
How do you know 8.0.1e is working if you can't access http://localhost:7875 ?
I access by http://127.0.0.1:7875/
OK, have you tried http://127.0.0.1:7876/dev
Please show a screenshot of the error on that page.
Is penalizing not a part of TF?
No, penalizing isn't part of TF....Imagine someone is going to do a "51%" attack against Nxt and he owns 90% of all coins. The adversary must stop generating blocks for legit branch coz he won't be able to compete against 100% mining power with his 90%. So he decides to "skip" his turn to generate a block. The rest 10% of the network detects this and penalizes the adversary by setting his mining power to 0 and distributing it among other miners.
yes.. we're searching to a donations/bounties to run a node .. or to forge ( help the Nxt server ) .
I think this is a bad idea. Either the network/nxt itself can care of or this will fail.
but if we want more nodes, and people can not create new ones because it has no budget .. how do we support the Nxt ?
This is a part of the whole discussion, my friend
Hey guys,
To those that have tried my web client http://nxtra.org/nxt-client ; A beta version is now available for download here:
http://nxtra.org/nxt-client/dev.zip
Unzip, move the dev folder to nxt/html/tools/dev
Then go to http://localhost:7876/dev
This is assuming you have 0.8.1e installed (it will not work correctly on older versions!) - do not try
I suggest you connect to TestNet first though; in the upper left corner you can switch between TestNet and localhost. Try everything out in TestNet first, when you are comfortable you can connect locally. There may still be errors in the code, it's a beta after all.
Not everything is done yet, and Internet Explorer is completely untested. I suggest you use either chrome/firefox or safari for now.
Also need to do some more interactive updating after submission of forms, etc.
if you want, you can send me a message there via the alias wesleynxt (just open the send message dialog and type wesleynxt in the account field). Messages are not yet encrypted.
Let me know what you think.
To those that have tried my web client http://nxtra.org/nxt-client ; A beta version is now available for download here:
http://nxtra.org/nxt-client/dev.zip
Unzip, move the dev folder to nxt/html/tools/dev
Then go to http://localhost:7876/dev
This is assuming you have 0.8.1e installed (it will not work correctly on older versions!) - do not try
I suggest you connect to TestNet first though; in the upper left corner you can switch between TestNet and localhost. Try everything out in TestNet first, when you are comfortable you can connect locally. There may still be errors in the code, it's a beta after all.
Not everything is done yet, and Internet Explorer is completely untested. I suggest you use either chrome/firefox or safari for now.
Also need to do some more interactive updating after submission of forms, etc.
if you want, you can send me a message there via the alias wesleynxt (just open the send message dialog and type wesleynxt in the account field). Messages are not yet encrypted.
Let me know what you think.
I have the active 0.8.1.e client and I can not connect through the client file :/ / / C :/ nxt / html / tools / dev / dev / index.html #
You should put it at tools/dev not tools/dev/dev (but it shouldn't matter).
You are acessing it through http://localhost:7876/dev/ right? Do not double click on index.html as it will open via file:// which does not work.
Go! Google Chrome could not find the page localhost: 7876.
Have you just clicked the link here:
http://localhost:7876/dev/
That should work, otherwise your java may not be running. Check if http://localhost:7875 works
Anyway, I'm off, will answer questions later.
Go! Google Chrome could not find the page localhost: 7875
java is working because nrs client 8.0.1e is working well
How do you know 8.0.1e is working if you can't access http://localhost:7875 ?
I access by http://127.0.0.1:7875/
yes.. we're searching to a donations/bounties to run a node .. or to forge ( help the Nxt server ) .
I think this is a bad idea. Either the network/nxt itself can care of or this will fail.
but if we want more nodes, and people can not create new ones because it has no budget .. how do we support the Nxt ?
We are searching for the right incentives for:
- running a node (this secures the network)
- running a node, have an open nxt account and forging with it (this secures the security of nxt = 51% attacks ?!) DONE by TF.
- running a node (this secures the network)
FIFY.
Even with transparent forging, Nxt is still susceptible to 90% PoS attacks.
Somebody buys up all the NXT.
I raised this, but CfB said is was acceptable
Yes. It would be very hard to mount this attack, because you would have to own 90% of the currency.
Don't forget that some people just won't sell.
You did not understand my idea, I do not mean to repay the costs of a node ... but only a part, for example 30% ..
Right now, this idea sounds really lame. You talk about donations and bounties.
Maybe I just don't get your idea
Maybe I'm wrong to call them donations, but the sense is that ..
I do turn on my VPS ten nodes to help the communities ( nxt server ). it would be nice to get some nxt..
Maybe my idea is not that nice?
You are talking about incentives for running a node. Thats one part of the discussion. Please don't use the words donations/bounties. Would be really wrong wrong wrong.
We are searching for the right incentives for:
- running a node (this secures the network)
- running a node, have an open nxt account and forging with it (this secures the security of nxt = 51% attacks ?!) DONE by TF.
- running a node (this secures the network)
FIFY.
Even with transparent forging, Nxt is still susceptible to 90% PoS attacks.
Somebody buys up all the NXT.
I raised this, but CfB said is was acceptable
"Somebody buys up all the NXT." <<< How?
with all fiats coordinating, most NXT owners would probably sell.
That would take $90,000,000,000. I doubt that occurs.
You did not understand my idea, I do not mean to repay the costs of a node ... but only a part, for example 30% ..
Right now, this idea sounds really lame. You talk about donations and bounties.
Maybe I just don't get your idea
Maybe I'm wrong to call them donations, but the sense is that ..
I do turn on my VPS ten nodes to help the communities ( nxt server ). it would be nice to get some nxt..
Maybe my idea is not that nice?
This was my thought too.
https://bitcointalksearch.org/topic/m.5354163
We are searching for the right incentives for:
- running a node (this secures the network)
- running a node, have an open nxt account and forging with it (this secures the security of nxt = 90% attacks ?!) DONE by TF.
- running a node (this secures the network)
FIFY.
I think we shouldn't ignore the second point in our discussion since we need forging nodes. You say it is "done by TF" but TF only is the mechanism which saves us from 51% attacks. But we still need to talk about incentives for forging.
Or someone steals (yes, I am looking at you MtGox) 90+% which can happen if we have 10-12 pools with most of the coins in them.
Wrong. Lease forging power to pools means not give NXT away.
You are right, thank you for pointing this out!
Jump to: