I have setup a server to support the nextcoin network and have a question about the web.xml file. Should I add an asterix * to AllowedHosts?
If I understand NRS correctly, you shouln't add the asterix, since everyone would be able to forge on my server this way. But I'm not sure if other clients can establish a connection without the asterix. So, should I add an asterix to AllowedHost or not?
Topic: NXT :: descendant of Bitcoin - Updated Information - page 734. (Read 2761645 times)
Now, Nxt-e list INK/BTC INK/NXT [FLAPPY/NXT]
Nxt-e.com supports multiple languages (
) Japanese or other language volunteers please contact us, thanks.
nxt-e.com deposit BTC LTC NXT, and get 400 flappy for free
Nxt-e.com supports multiple languages (
) Japanese or other language volunteers please contact us, thanks.nxt-e.com deposit BTC LTC NXT, and get 400 flappy for free
wow,the site is beautiful！
Anyone else having problems with Wesley's client?
Initially, I tried the auto-update (I was running .22/0.7.6). No luck, wouldn't start.
Redownloaded the client (.23), tried updating to 0.8.0, and same thing.
This seems to happen often with the Mac client update.
Whenever this happens, I usually find a stray "java" process in System monitor, when there shouldnt be any left.Initially, I tried the auto-update (I was running .22/0.7.6). No luck, wouldn't start.
Redownloaded the client (.23), tried updating to 0.8.0, and same thing.
This seems to happen often with the Mac client update.
Just kill the process and NxtMac usually starts up fine
Now, Nxt-e list INK/BTC INK/NXT [FLAPPY/NXT]
http://t.nxt-e.com/nxt-e.gif
Nxt-e.com supports multiple languages (http://img.freeflagicons.com/thumb/fluttering_flag/united_states_of_america/united_states_of_america_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/france/france_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/china/china_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/russia/russia_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/germany/germany_64.png ) Japanese or other language volunteers please contact us, thanks.
nxt-e.com deposit BTC LTC NXT, and get 400 flappy for free
http://t.nxt-e.com/nxt-e.gif
Nxt-e.com supports multiple languages (http://img.freeflagicons.com/thumb/fluttering_flag/united_states_of_america/united_states_of_america_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/france/france_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/china/china_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/russia/russia_64.pnghttp://img.freeflagicons.com/thumb/fluttering_flag/germany/germany_64.png ) Japanese or other language volunteers please contact us, thanks.
nxt-e.com deposit BTC LTC NXT, and get 400 flappy for free
I believe that one element of BCNext's plan is to set the minimum transaction fee to zero. And now I've posted my theory here, for posterity, so that I can either be mocked for my stupidity, in the future, or praised for my intuition.
We need something to counteract spam-transactions. But we indeed could set fees to 0 and use hashcash approach.
Hm, this is interesting. Still allows for users to pay via mobile (just slower, or they can use a service provider that lends their CPU power for small fees).
CfB, Jean Luc (or anyone else smart enough...)
The Nxt game we want to develop will be running on a server; would jython or Groovy be appropriate scripting languages to access things like the asset exchange?
Is there any work being done on parallel blockchains at the moment?
The Nxt game we want to develop will be running on a server; would jython or Groovy be appropriate scripting languages to access things like the asset exchange?
Is there any work being done on parallel blockchains at the moment?
Subscribe to the issue, what are the next steps
Anyone else having problems with Wesley's client?
Initially, I tried the auto-update (I was running .22/0.7.6). No luck, wouldn't start.
Redownloaded the client (.23), tried updating to 0.8.0, and same thing.
This seems to happen often with the Mac client update.
Initially, I tried the auto-update (I was running .22/0.7.6). No luck, wouldn't start.
Redownloaded the client (.23), tried updating to 0.8.0, and same thing.
This seems to happen often with the Mac client update.
I believe that one element of BCNext's plan is to set the minimum transaction fee to zero. And now I've posted my theory here, for posterity, so that I can either be mocked for my stupidity, in the future, or praised for my intuition.
We need something to counteract spam-transactions. But we indeed could set fees to 0 and use hashcash approach.
Hm, this is interesting. Still allows for users to pay via mobile (just slower, or they can use a service provider that lends their CPU power for small fees).
But here's my future prediction:
I can imagine in the future where companies built on-top of NXT will actually want to pay very small fees to thousands of decentralized super-nodes (high bandwidth service providers) to do the forging to secure the network for them and enable 1000+ TPS. Because companies are paying the fees, users will have to pay 0 fees. Perhaps add in hashcash to reduce spam somewhat.
CfB, Jean Luc (or anyone else smart enough...)
The Nxt game we want to develop will be running on a server; would jython or Groovy be appropriate scripting languages to access things like the asset exchange?
Is there any work being done on parallel blockchains at the moment?
The Nxt game we want to develop will be running on a server; would jython or Groovy be appropriate scripting languages to access things like the asset exchange?
Is there any work being done on parallel blockchains at the moment?
Can you please ask BCNext his opinion on implementing a social credit system? Such a system would allow Nxt to be used as a platform for LETSystems.
Explain the system here.
BCNext already stated in the second part of his plan that tx fees should be kept low. I agree with this.
BCNext doesn't want hashcash to be used coz 1000 tps would require a lot of electricity to be burnt, which is not very "green".
That's a good point.
Can you please ask BCNext his opinion on implementing a social credit system? Such a system would allow Nxt to be used as a platform for LETSystems.
Quote
BCNext already stated in the second part of his plan that tx fees should be kept low. I agree with this.
BCNext doesn't want hashcash to be used coz 1000 tps would require a lot of electricity to be burnt, which is not very "green".
That's a good point.
Can you please ask BCNext his opinion on implementing a social credit system? Such a system would allow Nxt to be used as a platform for LETSystems.
BCNext already stated in the second part of his plan that tx fees should be kept low. I agree with this.
BCNext doesn't want hashcash to be used coz 1000 tps would require a lot of electricity to be burnt, which is not very "green".
What do the Nxt stakeholders think about releasing the current source code earlier than April 1st?
We discussed this with CfB some time ago, as a way to get more developers involved and make it easier for client developers, not having to rely on decompiled code to see the Nxt internals. The copycats are already decompiling the Nxt classes, so there aren't any hidden secrets. I thought I would at least wait until I finish the 0.8.0 refactoring, but now that this is also released, it may be a good time to think about making the source open earlier, say March 1st?
We discussed this with CfB some time ago, as a way to get more developers involved and make it easier for client developers, not having to rely on decompiled code to see the Nxt internals. The copycats are already decompiling the Nxt classes, so there aren't any hidden secrets. I thought I would at least wait until I finish the 0.8.0 refactoring, but now that this is also released, it may be a good time to think about making the source open earlier, say March 1st?
I think releasing the source code early would be a good idea.
I believe that one element of BCNext's plan is to set the minimum transaction fee to zero. And now I've posted my theory here, for posterity, so that I can either be mocked for my stupidity, in the future, or praised for my intuition.
We need something to counteract spam-transactions. But we indeed could set fees to 0 and use hashcash approach.
The hashcash approach might limit transaction times on slower devices. It would depend on how much computation the device would have to use.
BCNext already stated in the second part of his plan that tx fees should be kept low. I agree with this.
I was hoping the third part of his plan would be to include a social credit system.
why has this thread gone so quite?
becausse NXT is dead, it is having hughe flaws end DEV cant fix them, just saying if you want to save some money sell it all now
I love you, you big soppy silly.
Nice comeback Damelon - the reaction of someone who, knowing he's on the winning side, is prepared to be magnanimous
Proofread, not proofwatch 
Images not ready.
Images not ready.
Looks good to me.
bitcoin sucks bigtime, it ruined my CPU.
didnt opened my wallet for some time and blockchain download took ages.
CPU overheated 3 times during blockchain download with result every time laptop turned itself off.
I realy don"t see it in bitcoin honestly.
The common user doesn't have to download the entire bitcoin blockchain. Use lightweight client like Electrum ..
Client issues are really not the issue. those kinds of problems are an inconvenience, but in the long term they are something that can be overcome. Honestly, to someone like myself who doesn't have a high level of knowledge when it comes to computers, the NXT client is difficult to operate, but that problem will be solved in time as the software is developed. The real problem is indicated by the reluctance of people to adopt NXT because of the method of dispersal. People don't want to commit to NXT because you have to invest in the currency and can't get NXT by mining in the way that Bitcoin and most other Cryptos are mined. People think that proof of stake is unfair to those who don't have a lot of stake and they don't want to run the client for the sake of the network with a decreased probability in receiving free coins. So what is going to happen when Bitcoin is mined out and there is NO chance of receiving coins for operating 1000 watt mining equipment. Are people still going to be willing to maintain the Bitcoin network then? There is an initial investment required to become a NXTER but once that investment is made, maintaining the network by running your client is not as much of a liability as running asic equipment, the return from forging is directly proportional to your investment, and forging is perpetual and you will never run out of coins to forge. People who support Bitcoin really don't support Bitcoin (most of them anyway). They support mining free Bitcoins, and eventually there are going to be no more Bitcoins to mine and running mining equipment will be an expense with no possibility of return. In that respect, Bitcoin is a sinking ship and when there are no more coins to mine, Bitcoin supporters will abandon the network like rats........ along with the long confirmation times and malleability problems........ and block chain downloading..........and overall lack of usable features Bitcoin is a walking dinosaur.
Thanks! Great post - written in non technical language, using metaphors (sinking ship) to aid understanding. Especially useful for Noobs like me. Perhaps posts like this could be collated to form the basis of a beginners' guide.
BTW dinosaurs were walking around for about 165 million years. Walking disasters however can measure their life expectancy in months at most.
Bye bye Bitcoin :-)
CfB thought I might want to make my suggestion for a possible different future of TF clearer.
What I am advocating would mean that the % chance to forge would effectively be the number of "forging accounts + IP addreses" you have (for most average people that is going to be 1).
So rather than having to get 100K or more NXT to forge you would only need to purchase 1 "forging account" (say 1 NXT?) to forge.
I hope that explains it better (unfortunately sometimes I just *assume* people understand my ideas).
What I am advocating would mean that the % chance to forge would effectively be the number of "forging accounts + IP addreses" you have (for most average people that is going to be 1).
So rather than having to get 100K or more NXT to forge you would only need to purchase 1 "forging account" (say 1 NXT?) to forge.
I hope that explains it better (unfortunately sometimes I just *assume* people understand my ideas).
@CfB
what is the API for generating a website token? It is not on the wiki, but it must exist as the NRS has the "key" functioning
what is the API for generating a website token? It is not on the wiki, but it must exist as the NRS has the "key" functioning
No such API, u r supposed to generate it on client side coz it requires to know a passphrase.
Any chance you can open up the website "key" creation code? We already have a way to verify the key, so it only makes sense to have a way to create a signature. I just dont want to mess around with Curve encryption, or whatever I have to do, when I know the code is already there and working.
James
Jump to: