Topic: NXT :: descendant of Bitcoin - Updated Information - page 1728. (Read 2761645 times)

Reasons?

I can help on the wiki/whitepaper. Username is gbeirn

Fixed.

Thanks, I posted some initial outline, will work on this today to flesh it out with [notes] to indicate where I need help

Is something like the following for an abstract ok?


*******
NXT: a peer-to-peer electronic economy system

Abstract:  Bitcoin has proven that a peer-to-peer electronic cash system can indeed work and fulfill payments processing without requiring trust or a central mint. However, bitcoin has several shortcomings that prevent it from becoming the basis of an electronic economy. In order for an entire electronic economy to be based on a peer-to-peer solution, it must be able to do the following:

1) Process thousands of transactions, quickly
2) Provide a means for generating interest income
3) Practical means for adding new features
4) Be able to run on mobile devices

NXT satisfies all these requirements and additionally eliminates the Ghash arms race that bitcoin's proof of work requires. NXT is based on 100% proof-of-stake and this required an initial distribution to be made. While many are not comfortable with the specific initial distribtion of the genesis block, as BCNext himself said, "nothing that involves money can be perfect" [need to find exact quote]

The fundamental improvement of NXT is Transparent Forging. This is the key innovation that NXT has which allows it to process thousands of transactions per minute.

Difficulty is very high.

That's the toughie. Ideally I want to verify each alias with at least 3 peers, and they should all return the same value or otherwise the link is considered invalid. Now, if you have the client running locally it will connect to that, ask for it's peer list and then connect to 3 random peers. If you do not have the client running, it will have to connect to somewhere on the internet to get a list of peers or rely on an internal database of peers instead.

Thank you.

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

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).

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

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

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.

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'm stuck half an hour on block 37723. Restart made, stuck still.

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

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

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

Correct.


allowedBotHosts set to * in config?

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?

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!