NXT :: descendant of Bitcoin - Updated Information

[wesleyh]

I've created a PHP API library to send / receive money programmatically.

You can download it here:

http://nxtra.org/api/

I hope this can be used as a starting point for you to create your own games, or perhaps even an automated exchange.

It re-broadcasts transactions as per cfb's instructions and waits for 10 confirmations on incoming transactions before confirming that transaction.

Remember to test the code yourself though, there's always the possibility of bugs.

If you use this, or like this idea, please donate to my nxt account: 8189784314684138350

Thank you.

[1714895173]

1714895173

[1714895173]

1714895173

[1714895173]

1714895173

[martismartis]

Just wanted to say that 0.5.3 is running incredibly well for me.  Is anyone still having problems with stuck blocks?

yes,me too ,but I used 0.5.4e now,and looks good.

Making transfer gives lot of jetty errors in command window. Version 0.5.4e

[davethetrousers]

I've created a PHP API library to send / receive money programmatically.

Finally, someone did it. I almost felt the need to write something myself, in Python or PHP.

I'll probably make use of that someday.

[joefox]

Good day I want to help make the translation into Romanian, with whom I contact for more information

The wiki needs translators.  See http://wiki.nxtcrypto.org/wiki/Help_translate

[joefox]

Re-posting my Public Service Announcement:

If you are new to Nxt and don't want to read through 865 pages of forum posts, come to the wiki:
- Learn about Nxt
- Get started
- get basic questions answered in the FAQ and common problems pages
- Learn how to set up a public node on a VPS, using laowai80's steps
- read up on the Nxt high-level API, which you can use to build apps, games, clients, utilities, and more

Also remember there are great forums with lots of info and support for beginners. Many of the best Nxt wiki articles are based on information originally contributed here:
- The nxtcrypto.org forum
- The nextcoin.org forum

I comb these forums every day and pull tidbits to update the wiki with, so that you don't have to.  

This thread is long and daunting for new folks.  Don't get frustrated -- come to the places where new folks are welcomed and pampered!

NEW WIKI SECTION ADDED:  For Programmers

[jl777]

Is this ongoing?

I suggest to put a document onlin for all to work on.

Who will take action here please? (utopian, Anon, Alias?)

Pin

This is trivial to do on the wiki.  I can set up a Whitepaper namespace and create Whitepaper:Nxt.  Then anyone who wants to contribute can pitch in, and the wiki will track everyone's contribution down to the last byte.  The bounty can then be divided fairly among the contributors.

I created jl777 acct on wiki. Where do I start putting in text for whitepaper?

[newsilike]

I'm currently discussing NXT and Proof of Stake with reddit folks:
http://de.reddit.com/r/Bitcoin/comments/1uvn22/in_future_can_bitcoin_switch_to_proofofstake/

People with more sophisticated knowledge then me might want to step in the conversation.

One guy posted this:
http://www.reddit.com/r/Bitcoin/comments/1uoq6e/what_do_you_guys_think_of_proof_of_stake_mining/cek7vbc

What do you think about that?

[l8orre]

Hi,

2 quick Qs from me regarding the API:

I am running on my raspberry pi 0.5.3 (very stable), but I have no screen/mouse/kbd attached to it, I use ssh from my laptop and autostart of nxt at boot.

Q1.: maybe I missed something, but I do not have any portforwarding in my router (DSL) to 7874/7875 - and yet nxt is running nicely. Do I only need to activate portforwarding when I want MY node exposed to the internet so that other ppl can log in to it, but when I just want the backend to forge and send+receive money, I don't need forwarding?

Q2.: I am a python guy, and I am experimenting with the api. When I direct some api calls as documented in the wiki at my nxt on my laptop with http://locahost:7874, I get nice answers.
When I query https://192.168.178.XX:7875 on my raspi, I get '{"errorCode":7,"errorDescription":"Not allowed"}'

Is this a feature, or am I making a mistake?  

Thanks!

[notsoshifty]

Namecoin has never worked because necessity to install browser plugins (or do other things like setting special DNS servers) ruined its brilliant idea at the very beginning.

There are 2 main ways to use Nxt DNS without third-party plugins.

1]  Server-side.  A web server analyses Nxt blockchain and replaces nxt-links with corresponding addresses before sending HTML documents to users.
2]  Client-side.  A web browser runs a JS script that connects to Nxt bootstrapping nodes and replaces nxt-links.  This way requires to embed a small script and run it on "onload" event.  The script will do all the work via CORS, JSONP or other techniques.

Just re-reading old posts. Is this proposal still sound, if applied to aliases? Has such a JS library been developed? If not, would it be a good idea to post a bounty for one, and start using it in places like the nxt wiki?

[davethetrousers]

Q1.: maybe I missed something, but I do not have any portforwarding in my router (DSL) to 7874/7875 - and yet nxt is running nicely. Do I only need to activate portforwarding when I want MY node exposed to the internet so that other ppl can log in to it, but when I just want the backend to forge and send+receive money, I don't need forwarding?

Correct.

Q2.: I am a python guy, and I am experimenting with the api. When I direct some api calls as documented in the wiki at my nxt on my laptop with http://locahost:7874, I get nice answers.
When I query https://192.168.178.XX:7875 on my raspi, I get '{"errorCode":7,"errorDescription":"Not allowed"}'

allowedBotHosts set to * in config?

[wesleyh]

Namecoin has never worked because necessity to install browser plugins (or do other things like setting special DNS servers) ruined its brilliant idea at the very beginning.

There are 2 main ways to use Nxt DNS without third-party plugins.

1]  Server-side.  A web server analyses Nxt blockchain and replaces nxt-links with corresponding addresses before sending HTML documents to users.
2]  Client-side.  A web browser runs a JS script that connects to Nxt bootstrapping nodes and replaces nxt-links.  This way requires to embed a small script and run it on "onload" event.  The script will do all the work via CORS, JSONP or other techniques.

Just re-reading old posts. Is this proposal still sound, if applied to aliases? Has such a JS library been developed? If not, would it be a good idea to post a bounty for one, and start using it in places like the nxt wiki?

It would be trivial to take the browser extension script and convert it to a website script.

[vanea84]

Good day I want to help make the translation into Romanian, with whom I contact for more information

The wiki needs translators.  See http://wiki.nxtcrypto.org/wiki/Help_translate

Hello. I can translating Romanian languages.  Please add the Romanian language for Wiki

[opticalcarrier]

hey cfb i had this idea. i wont claim that its a good idea. but i think its atleast interesting enough to be worth sharing.

What if, rather than being associated with a single public key, entries in the accounting ledger were associated with 2 public keys. One could be used to sign transactions and one could be used to sign blocks. This division would add a lot of protection from theft for node operators. That way only the block signing key would need to be left unlocked meaning that leaving your account unlocked would entail no extra risk of theft. It would help us move towards a point where there is no cost associated with forging so node operators would be more intentioned to forge all of the time even if their chances of forging a block were slim. As it stands right now, someone who is not likely to forge more than one block per year may decide its not worth the risk to leave his client unlocked, where as if this idea were implemented than there would be no risk of theft and so he would have no reason not to leave it unlocked.

perhaps you could also pass it on to jean luc and bcnext just for the sake of giving them something interesting to think about that may lead to similar but better ideas.

This is an interesting idea, let's discuss it and implement if it's really good, the whole community should take part in the discussion. No need to ask BCNext, Jean-Luc or me.

hes only like the 3rd person to suggest this!  good we really need to get this implemented

[martismartis]

I'm stuck half an hour on block 37723. Restart made, stuck still.

[notsoshifty]

Just re-reading old posts. Is this proposal still sound, if applied to aliases? Has such a JS library been developed? If not, would it be a good idea to post a bounty for one, and start using it in places like the nxt wiki?

It would be trivial to take the browser extension script and convert it to a website script.

Not trivial to me

I suppose we'd need something that:
 - Is open source, with source hosted at somewhere like github
 - Has a suitably open licence
 - Is a single file that anyone who has a website can easily import into their html and use out-of-the-box; .js file served either from their own site or from some centrally hosted site(s)
 - Allows the website operator to use alias URLs seamlessly and in a simple way
 - Works cross browser
 - Has a nice hover-over tooltip (maybe)
 - Works with a set of trusted (how trusted?) externally hosted (how discovered?) NRS instances

[wesleyh]

Just re-reading old posts. Is this proposal still sound, if applied to aliases? Has such a JS library been developed? If not, would it be a good idea to post a bounty for one, and start using it in places like the nxt wiki?

It would be trivial to take the browser extension script and convert it to a website script.

Not trivial to me

I suppose we'd need something that:
 - Is open source, with source hosted at somewhere like github
 - Has a suitably open licence
 - Is a single file that anyone who has a website can easily import into their html and use out-of-the-box; .js file served either from their own site or from some centrally hosted site(s)
 - Allows the website operator to use alias URLs seamlessly and in a simple way
 - Works cross browser
 - Has a nice hover-over tooltip (maybe)
 - Works with a set of trusted (how trusted?) externally hosted (how discovered?) NRS instances

I'll be updating my extensions soon with some of this functionality and it should also work as a .js file integrated in the website.

[joefox]

I created jl777 acct on wiki. Where do I start putting in text for whitepaper?

Hey friend,

You've been tagged as a contributor to the wiki and can begin to edit.

I have created a stub for the whitepaper at http://wiki.nxtcrypto.org/wiki/Whitepaper:Nxt

[joefox]

Hello. I can translating Romanian languages.  Please add the Romanian language for Wiki

You can add it yourself!  As soon as you start to translate elements, "Romanian" will magically appear on any page where it is available.  Just go in and start translating!

To get set up, you need to follow these instructions: http://wiki.nxtcrypto.org/wiki/Help_translate

[notsoshifty]

...
 - Works with a set of trusted (how trusted?) externally hosted (how discovered?) NRS instances

I'll be updating my extensions soon with some of this functionality and it should also work as a .js file integrated in the website.

That's great.

Do you have solutions for 'how trusted?' and 'how discovered'?

Probably straightforward if just integrating with one or two known websites such as 22k.io etc, maybe just need SSL that's all. But how could it work in a decentralised way so nobody has to trust one specific website? (Without having to run NRS including full blockchain inside the .js library).

[nexern]

NEW WIKI SECTION ADDED:  For Programmers

thx joefox,

very good to aggregate the fragmented api, it's a real timesaver.
i have seen cfb has posted another message api snippet here today.

donation: +2