NXT :: descendant of Bitcoin - Updated Information

[yan83]

ok

[xyzzyx]

I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!

What do you think about that?

I think this is a great idea and I will support including it in the official client.

Apologies if I posted this already - why can't we just add a check digit instead of changing the account number to alphabetti-spaghetti, not perfect but i would catch the majority of errors.

http://en.wikipedia.org/wiki/Luhn_algorithm

I was originally thinking around the same lines.  I was playing around with a modified Luhn code that used a check character rather than a digit since some account numbers without a check digit would pass the Luhn check.  It was easier to see that 1234567A was a checked code (for the naked account number 1234567), rather than 12345671, for example, and it could still be easily used without the check character for clients that didn't support the Luhn check.

The reason I was looking at a modified Luhn, rather than a CRC or the Verhoeff algorithm, was that the check could be calculated by hand, or mentally with a little practice.

However, with a little reflection, I think ricot's proposal is much better.  It has error correction built in, which is a huge plus.

[chanc3r]

I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!

What do you think about that?

I think this is a great idea and I will support including it in the official client.

Apologies if I posted this already - why can't we just add a check digit instead of changing the account number to alphabetti-spaghetti, not perfect but i would catch the majority of errors.

http://en.wikipedia.org/wiki/Luhn_algorithm

I was originally thinking around the same lines.  I was playing around with a modified Luhn code that used a check character rather than a digit since some account numbers without a check digit would pass the Luhn check.  It was easier to see that 1234567A was a checked code (for the naked account number 1234567), rather than 12345671, for example, and it could still be easily used without the check character for clients that didn't support the Luhn check.

The reason I was looking at a modified Luhn, rather than a CRC or the Verhoeff algorithm, was that the check could be calculated by hand, or mentally with a little practice.

However, with a little reflection, I think ricot's proposal is much better.  It has error correction built in, which is a huge plus.

I can see the benefits of ECC but it generates something that in my humble view is even harder to get right - I've tried a few account numbers in his useful website - yes its balanced by error correction but I don't think its solving usability.

[ricot]

Besides the automatic error correction, there are other advantages like branding (everyone can now see that it's an NXT address, even if they don't know, what exactly NXT is ), an obvious grouping that helps a lot with readability, and you just can't hit a wrong account number, practically.

[xyzzyx]

I can see the benefits of ECC but it generates something that in my humble view is even harder to get right - I've tried a few account numbers in his useful website - yes its balanced by error correction but I don't think its solving usability.

I'm not sure the NXT client/server is the correct place to have end users.  I see everything we have now as just low-level stuff, just barely above the network itself.  

What I believe needs to be done to solve usability is to have everything we're doing now abstracted away from the end user.

In the future you download your NXTransaction App from Google Play, put in your account number edit:phrase once in the configuration section, then use a user selectable 4 or so digit pin from then on to sign transactions securely within the phone software itself.

Using NXT should look no different than using a Point-of-Sale kiosk at this point.

[gimre]

I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!

What do you think about that?

I think this is a great idea and I will support including it in the official client.

Apologies if I posted this already - why can't we just add a check digit instead of changing the account number to alphabetti-spaghetti, not perfect but i would catch the majority of errors.

http://en.wikipedia.org/wiki/Luhn_algorithm

cause if you look at two strings: DatS7 and opKrN you instantly see the difference, the lesser the alphabet, the less difference is visible on two words over that alphabet...

[chanc3r]

I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!

What do you think about that?

I think this is a great idea and I will support including it in the official client.

Apologies if I posted this already - why can't we just add a check digit instead of changing the account number to alphabetti-spaghetti, not perfect but i would catch the majority of errors.

http://en.wikipedia.org/wiki/Luhn_algorithm

cause if you look at two strings: DatS7 and opKrN you instantly see the difference, the lesser the alphabet, the less difference is visible on two words over that alphabet...

I agree but the current proposal is not restricted to alphanumerics based on the examples I tried, it gets special characters like #$ etc which makes things harder especially on a smart phone.

Anyway I agree with xyzzyx that this is low level stuff and once its stored then we will use pin access, although I assume we would load the ECC version of the account number into the phone with a QR scan so I guess it really doesn't matter - the important thing is the account gets set correctly.

[jl777]

I just posted a proposal to fix the account number typo-problem over at the official forums:
https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 <- making NXT account numbers awesome!

What do you think about that?

I think this is a great idea and I will support including it in the official client.

Apologies if I posted this already - why can't we just add a check digit instead of changing the account number to alphabetti-spaghetti, not perfect but i would catch the majority of errors.

http://en.wikipedia.org/wiki/Luhn_algorithm

cause if you look at two strings: DatS7 and opKrN you instantly see the difference, the lesser the alphabet, the less difference is visible on two words over that alphabet...

I agree but the current proposal is not restricted to alphanumerics based on the examples I tried, it gets special characters like #$ etc which makes things harder especially on a smart phone.

Anyway I agree with xyzzyx that this is low level stuff and once its stored then we will use pin access, although I assume we would load the ECC version of the account number into the phone with a QR scan so I guess it really doesn't matter - the important thing is the account gets set correctly.

correct

We need a layer above current unprotected accts and might as well go with best possible method, which is undoubtedly an ECC layer. https://forums.nxtcrypto.org/viewtopic.php?f=17&t=524 has a great discussion on the reed solomon method ricot proposed.

Once we have that, we can build more user friendly layers such as allowing people to use their cellphones and scan QRcodes to send/recv payments.

One step at a time. Or since we are decentralized, all steps all the time! As soon as Reed Solomon accts are defined, no reason cellphone QRcodes can't be implemented on top of ECC accts

James

[rickyjames]

rickyjames,

I've got most of the whitepaper content thrown together, but it is still very rough and not really reading like a whitepaper to me.

It needs somebody elses touch and I like how you write. Could you take a stab at editing it so it reads like a whitepaper? I have some more content for NXT yields section 11, but the rest is ready for some new eyes

James

Roger.  Will look at it later tonite after my tablet and I finish supper.

[xyzzyx]

although I assume we would load the ECC version of the account number into the phone with a QR scan

For face-to-face transactions and point-of-sale with your phone, NFC for those that support it and QR for those that don't. 

For web sites, transactions need to be as behind-the-scenes as possible. 

I'm personally waiting to see what comes out of the Curve25519 JavaScript bounty. I think signing transactions from within the browser could potentially solve the on-line store problem.

[jl777]

rickyjames,

I've got most of the whitepaper content thrown together, but it is still very rough and not really reading like a whitepaper to me.

It needs somebody elses touch and I like how you write. Could you take a stab at editing it so it reads like a whitepaper? I have some more content for NXT yields section 11, but the rest is ready for some new eyes

James

Roger.  Will look at it later tonite after my tablet and I finish supper.

Thanks!

[allwelder]

So, you premined 100% and still don't do a giveaway?

So, you decided you would come in, spout your opinion and ask for a giveaway?

Not asking for a giveaway. Just questioning your marketing strategies

If you'd done some research, you'd know that there have been giveaways and there still are loads of bounties for people who contribute.

You'd also know that the word "mine" doesn't apply here.

I did know that. I did my research. Still don't think that's sufficient

I have been thinking about that last sentence, and the only answer I can come up with is: "So, how do you propose to solve that? Force people to give it away?"
Or is it basically just a statement that means to say "I disapprove"?

The people who hold the big load should give more away, yes. That's the only way 'the masses' will approve of this coin. As long as a few people hold 90% of the coins, this won't work.

and then one cheater came, created 70 accounts and gatheret 35.000 nxt with them in generous giveaways... not cool

Investigation and check is necessary before giveaways, e.g. what he/she has done.

[coolfish]

DGEX 24h Volume:   1499620.00 (72.67411380 BTC)

Less than 100btc
The new record, we should celebrate?

[gvans]

Did I get this right? The asset exchange will be implemented, no voting for it. But buying/selling/transferring aliases is questionable and will be voted for?

[cryptonoob50khs]

few investors "bought" 100% premine. i have seen enough big-big walls on dgex that were made only to fear people, manipulation and scam. hope you will have your personal place in the Hell. 

[coolfish]

After listening to your criticism I decided to reduce the BTC withdrawal fee to 0.0001 BTC (just enough to cover the cost of the transfer)

Please reconsider using NewAltEx.com

Thank you

Good job, I am already registered.

[opticalcarrier]

The NXT Foundation will at not cost to you manage your VPS; this offer comes with a custom SCREENNAME.vps.nxtcrypto.org domain name visible in peer lists!  All you hae to do is pay for the VPS and we will do the rest.

1) Sign up https://www.budgetvm.com/account/cart.php?gid=64  They accept PayPal.  Or use Digital Ocean.  Or use any other provider.  You need at least 1024MB of RAM on the VPS though.

2) The 1024MB VPS for $4.99/month should be sufficient unless you have a hallmark balance with more than 1,000,000 NXT, in that case please choose the 2048MB VPS for $9.99/month

3) When signing up for a VPS, when they ask for a hostname for your VPS, enter in: SCREENNAME.vps.nxtcrypto.org

4) When selecting an OS, please choose Debian6 x64

5) Send a Private Message in the NXT Foundation Forums to user forkedchain.  The Forums are at http://forums.nxtcrypto.org and in the PM please include the VPS's IP address, root password, and your generated hallmark for hostname SCREENNAME.vps.nxtcrypto.org.  You can generate your hallmark at https://localhost:7875/admin.html but please do this in private browsing mode so that your passphrase isnt cached to your disk

6) The NXT Foundation will 100% manage the VPS for you; you will still have shell access and I will give you a script on your server you can run ant any time to check your server at any time, like user abctc has on the VPS we are managing for that user account.

root@abctc:~# nxtstat

    "availableProcessors": 1,
    "cumulativeDifficulty": "1027491128460853",
    "freeMemory": 109647744,
    "lastBlock": "9944586979784265880",
    "lastBlockchainFeeder": "vps12.nxtcrypto.org",
    "maxMemory": 259522560,
    "numberOfAccounts": 13905,
    "numberOfAliases": 45068,
    "numberOfAssets": 0,
    "numberOfBlocks": 38813,
    "numberOfOrders": 0,
    "numberOfPeers": 284,
    "numberOfTransactions": 79792,
    "numberOfUsers": 0,
    "time": 4197595,
    "totalEffectiveBalance": 98952817300,
    "totalMemory": 259522560,
    "version": "0.5.5"

root@abctc:~#

[mnightwaffle]

Gang,

Would appreciate Chinese speakers looking this over for errors. Also, I know nothing about leading/kerning/spacing with Chinese characters and what's appropriate.

big image - snip

Also, full-size PDF is here

EDIT: sorry, forgot to credit Miramare from the nextcoin.org forum for supplying Chinese text.

There are more features without mention, for example, arbitrary message, voting system and so on.

Having my friend look at it now. Will try to translate arbitrary message, voting system too.

[jl777]

http://qz.com/165273/the-existential-threat-to-bitcoin-its-boosters-said-was-impossible-is-now-at-hand/

It is nice to know NXT does not have to worry about 51% attack like bitcoin. Even 90% attack can be thwarted.

James

[opticalcarrier]

http://qz.com/165273/the-existential-threat-to-bitcoin-its-boosters-said-was-impossible-is-now-at-hand/

It is nice to know NXT does not have to worry about 51% attack like bitcoin. Even 90% attack can be thwarted.

James

bitcoin is vulnerable for a very unfair advantage even if a pool only owns 33% of the hashing power.  A research paper from Cornell University explains more and this following article gives a laymans view of the risk as described by the Cornell researchers: http://hackingdistributed.com/2013/11/04/bitcoin-is-broken/

I read this article about the 33% attack in November, and it is what prompted me to start searching for what I thought had the possibility to replace bitcoin, which is how I found NXT.