Topic: NXT :: descendant of Bitcoin - Updated Information - page 1227. (Read 2761626 times)

May I add this to the nxtcrypto.org website? There are PIN buttons to pin it to Pinterest and I can share it socially too.

Can I use it with my iPad? Where can I download it?

And is it based on the blockchain? I don't see any of your messages on the blockchain?

For the Miami conference NiftyNikel emailed me a notification when there was something to add to the Nxtcrypto Twitter, Facebook or Google pages. We had pretty consistent coverage of the conference. PM me if you would like my help with upcoming events. With 5400+ (3200+ talking about this) FB followers and 740 Twitter followers, this could be an important way to let the community know about your participation there.

IMO, if we are to use a prefix, it should ONLY be N and not NXT, and then there should be no dash between the N and the rest of the account.

AND that N should participate in whatever error correcting code we choose.  If it doesnt then it is completely useless.

I still say no prefix at all, I like shorter account numbers - less to deal with.

PLEASE SEE THE YOUTUBE VIDEO OF NXTTY APP IN ACTION

http://www.youtube.com/watch?v=Gj0CRqoNsYc&feature=youtu.be

Iphone Dev Team (Nextcoin usernames):
Rriky92
Wolfgang
Taylormcm

To avoid the situation were people choose weak password, there is a simple solution.
Do not let them choose. The client should generate an account itself.

It would be like the bitcoin private keys. Hidden from the user, unless he's looking for it.

Thanks NxtChg, the format I wrote
"Nxxxx xxxx X xxxx xxxxT" or even just "Nxxx xxxx xxxx xxxx"
instead of NXTxx xxxxx xxxxx xxxxx

this addresses two of the "arguments against" branding

Arguments against:

    Longer addresses, usability suffers.
->  Harder to find address visually, because all 3 first letters are the same.
->  Needless duplication in case of:

Phone: 123-4122-312
Email: [email protected]
Skype: john_doe
BTC: 1dff943fjfj90234jfidsjf98430jffj03
NXT: NXT-JOHN-2342-S4FW4-DFSESE

Even if the branding is more subtle I think it still functions.

I also prefer removing confusing letters/numbers rather than mapping I=1 etc. to the same code, "For rare cases where you need to actually type in the address".  Maybe I'm wrong but I thought the point of using shortened "visible ID" addresses in NXT is so people can type an address.  Mapping I=1 to the same code makes people nervous because they don't know it will do that.  I think using unambiguous alphabet is better.  What is the value in making it easy for people create a vanity address that starts with a word,  Why not just register an alias?

oh Boy - FrictionlessCoin, there is something you fundamentally misunderstood when your momma explained that curious thing about them 'pussies' to you ...

his claim is that since the public key is a curve25519 hash of the private key that it is exposed.   

https://bitcointalksearch.org/topic/m.4799666

I wish my idea would get some traction.  Also, look at the HUGE EMPTY BOX available when we type in a passphrase.  Why is there not some info in that box for a new user to read, warning that their NXT WILL be stolen if they use a simple word/phrase, even a long sentence if it is in some vulgate?

Please point me where you found "Exposing the private key" phrase, I can't see it.

FrictionlessCoin == Hazard !!!

Both state the same silly things.

Exactly, if we are not getting a booth, I'd argue that even brochures is a bit much (unless they are quite small) and not common at these events.

- Business Cards
- Good handshake and eye contact
- Ability to figure out who are the decision makers
- Ability to setup mini 10 minute meetings with booth merchants
- Frequent updates to the community during the event

That's the slam dunk, more than most people are doing there.

Can''t be fixed.   It is fundamental broken.   Exposing the private key (even if it is hashed) is just fundamentally wrong.

Thanks. Any other comments?

hopefully new clients will have built system for creating strong passwords / not allowing weak ones

This is really scary.  There is apparently a continuous, ongoing attack against NXT looking for weak passwords.  There is no way to know how many hackers are doing this or how much computer horsepower is being directed towards this because the attack can be run offline against a copy of the blockchain.  Every day we are signing up 100 users on average and we are hoping to get many, many more.  NEW USERS ARE NOT BEING TOLD OFTEN ENOUGH OR STRONGLY ENOUGH ABOUT THE IMPORTACE OF A LOOOONG RANDOM PASSWORD.  Every day new users are coming in and using a short password and immediately lose their NXT just like dzarmush did.  

They do not put a happy smile after their experience.

They do not put a happy smile after their experience.  

They do not put a happy smile after their experience.  

I truly believe that one of the biggest threats to NXT is word of mouth about poor security.  "Yeah, I tried to buy some NXT, it was stolen in 24 hours, better steer clear of that coin..."

That kind of talk - and the poor security hygiene that precipitate it - needs to be nipped in the bud NOW.  We only get a fresh reputation once - and people are losing NXT at an alarming rate, at least it seems that way to me.

Some day when I am all caught up (ha ha ha) I want to start a Wiki page listing every known past instance of lost NXT and have new users record their experiences on what happened to them in some kind of table.  This is data we need to be accumulating.

ebereon: and how can you manage it? You can connect it to the notebook or google nexus 7?  

Encrypted messaging via AM

I coded an encryption tool, which encrypts a message with AES (128, 192 and 256 bit). After the encryption you can send it to the blockchain.

You need to specify a key and an initialization vector. More info you can find on my website and wikipedia. If anyone has an idea how I can make a system where the recipient knows which key and initialization vector he has to use, let me know! :)

For the encryption part I used this php version!

To the Msg Encrypter!


I made 2 test encryption messages, they were send from the website directly.



You can also view them on my AM Explorer (IDs: 1100, 1101)


If everything works fine I will implement it into nxtion.com in form of a messaging tool between all users, where the key/init_vect are known (if wanted).


Thank you.

PS: I also participate with this in the AM contest. :)

To be honest, I totally disregards both that, and the message about it in the client (after 1440 confirms your client starts giving you forging ETAs).

I go by "it will take a lot of time". 
Saves me a lot of stress.