Topic: NXT :: descendant of Bitcoin - Updated Information - page 495. (Read 2761624 times)

Keep us updated!

Sure. For a quick start, use this web client (do not use real account!)

http://nxtra.org/nxt-client/

Ask for some testNXT's here:

https://forums.nxtcrypto.org/viewtopic.php?f=2&t=832

And use them to issue assets, and to execute ask/bid orders etc.

We missed you!


Could anybody run the forging simulator with forging groups? It was BCNext's idea. And throw in some penalization, maybe.

Is there already a piece of code that can generate an account number from an secret passphrase in another language than Java?
Like the offline paperwallet generators for BTC

 

Fantastic job!!!!  

some remaining issues

criptsy
poloniex
Password Generator
2-step authentification


Here some open source plug in . Maybe someone can contact the developers of this plug in to adapt them to Nxt if required

Pronounceable Password Generator
Extension Author: Jan Benjamin Engracia, Extension Language: English

This plugin adds a custom password generation algorithm, which generates pronounceable passwords.

The plugin is available here: http://sourceforge.net/projects/pronouncepwgen/ [Downloads]

Readable Passphrase Generator
Extension Author: Murray Grant, Extension Language: English

The Readable Passphrase Generator plugin generates passphrases, which are (mostly) grammatically correct, but nonsensical. These are easy to remember (for humans), but difficult to guess (for humans and computers).

The plugin is available here: http://readablepassphrase.codeplex.com/

WordSequence Generator
Extension Author: fireOut, Extension Language: English

The WordSequence plugin generates passphases consisting of words.

The plugin is available here: http://sourceforge.net/projects/kpwordsequence/

Here another one TFA. Maybe someone can contact the developers of this plug in to adapt them to Nxt if required

http://keepass.info/plugins.html#keeotp

OtpKeyProv
Plugin Author: Dominik Reichl, Plugin Language: English

OtpKeyProv is a key provider based on one-time passwords. After protecting your database using this plugin, you need to generate and enter one-time passwords in order to open your database.

All generator tokens that follow the OATH HOTP standard (RFC 4226) are supported.

Download plugin: [v2.2 for KeePass 2.20 and higher]
Download source code: [v2.2 for KeePass 2.20 and higher]

If you instead want KeePass to generate one-time passwords, see the {HMACOTP} placeholder. For generating time-based OTPs, see the KeeOtp and Tray TOTP plugins.

KeeChallenge
Plugin Author: Ben Rush, Plugin Language: English

Allows to protect KeePass databases using challenge-response authentication.

The plugin is available here: [KeeChallenge Plugin Website].

KeeOtp
Plugin Author: Devin Martin, Plugin Language: English

This is a KeePass plugin that adds support for two factor authentication into other systems using TOTP (Timed One Time Passwords). It stores TOTP secret keys in the KeePass database and generates TOTP codes from the key within KeePass.

KeeOtp is compatible with Google's 2-Step Verification and Amazon AWS MFA. It will work with most other RFC 6238 compliant TOTP implementations as well.

Website: [https://bitbucket.org/devinmartin/keeotp/wiki/Home]
Downloads: [https://bitbucket.org/devinmartin/keeotp/downloads]

KeePass has a built-in placeholder to generate HOTPs (but not TOTPs), see {HMACOTP}.

If you instead want to protect your KeePass database using one-time passwords (i.e. one-time passwords need to be generated and entered in order to open your database), see the OtpKeyProv plugin.

Tray TOTP
Plugin Author: Alexandre Gravel, Plugin Language: English

Time-based One-Time Password plugin to enable 2-step authentification (supports Google and Dropbox) by generating TOTPs from the KeePass tray icon. This plugin also provides a custom column to display and/or generate TOTPs. Auto-Type is also supported when the specified custom field is used in a keystroke sequence.

Website: [https://sourceforge.net/projects/traytotp-kp2/]
Downloads: [https://sourceforge.net/projects/traytotp-kp2/files/]

KeePass has a built-in placeholder to generate HOTPs (but not TOTPs), see {HMACOTP}.

If you instead want to protect your KeePass database using one-time passwords (i.e. one-time passwords need to be generated and entered in order to open your database), see the OtpKeyProv plugin.

I am interested in helping the testing for the asset exchange but don't know where to start. I'm currently running the NRS 0.8.5 client on a Windows Vista machine. I have not done any experimentation with the AE yet.

Can someone point me in the direction of what I need to do to pitch in with the AE testing?

Could you please follow this up?

My theory is that Satoshi simply had this idea and then had to learn how to code, not the other way around.
I think the same goes for BCNext.

From http://mag.newsweek.com/2014/03/14/bitcoin-satoshi-nakamoto.html:


BCNext followed Satoshi even in this...

Maybe.

You may be referring to me saying that BCNext told us that NXT is a experiment for him and that he has abandoned the project.
I haven't seen anyone talk about talking to BCNext there.
I got to ask some question through proxy (CfB) to him and he answered, but as far as I know noone else is talking to him

no, nothing special about that. just had it sitting there in the script .

Here is version 2.2 of my Windows/Mac OSX NXT client "NXT Solaris".


Changelog
-Mac OSX version added (source is included in the Windows downloads)
-GUI Performance improvements
-Changed the default testnet address to "http://tn01.nxtsolaris.info:6876/"
-The JCL is no longer needed to compile the source code
-Fixed a bug that prevented sending NXT to accounts without a public key in the BC
-Fixed Bter market data retrieval
-Fixed "secret maps to expected account number" check for secrets with characters beyond ascii
-Added checks for enough funds before broadcasting transactions


Download
64-bit Windows Version: NXTSolaris-v2.2-Win64bit.zip (36.3 MB) – Download here
SHA256 checksum for NXTSolaris-v2.2-Win64bit.zip: BCDC7C27755A138E44AE51FB3F842BB8E12FAC6AF3117F44BB99B9B01B581F95

32-bit Windows Version: NXTSolaris-v2.2-Win32bit.zip (34.3 MB) – Download here
SHA256 checksum for NXTSolaris-v2.2-Win32bit.zip: 0F6851CE16411756EB5ED9ADFBD1AF730CEC0B68D8566660D8A8257C0DF3F7B1

32-bit Mac OSX Version: NXTSolaris-v2.2-OSX32bit.zip (9.5 MB) – Download here
SHA256 checksum for NXTSolaris-v2.2-OSX32bit.zip: 76B416EB3783410E33AC14353501F9FC735863CE725205AE0DF78C1E678F76BD


For screenshots and everything else please visit: http://nxtsolaris.wordpress.com/


Installation
Simply unzip the archive and run the NXTSolarisStarter.exe file.

The current version 2.2 is compatible with the previous versions 2.1.

Roadmap
1.) Move current version of my code to XE5 and release closed source 32-bit and 64-bit versions for Windows. [DONE]
2.) Refactor code to a MVC architecture, so that I can create separate GUIs while using the same version of the business logic code. [DONE]
3.) Create new GUIs for Windows and OS X using the same business logic, but based on the cross-platform Firemonkey libraries. [DONE]
4.) Release Windows version (32 and 64 bit) based on FireMonkey. [DONE]
5.) Implement new features from the TODO list [DONE]
6.) Release source-code for FireMonkey Windows version (February 16th, 2014 latest) [DONE]
7.) Implement new features from the TODO list
8.) OSX compatibility changes
9.) Release OSX version based on FireMonkey.
10.) Release source code for FireMonkey OSX version.


I've reached the end of my roadmap! :-)


TODO list
-Arbitrary message encryption
-Offer a simple and advanced GUI, with the simple GUI targeted at new users



Donations
I hope you like my client and I’d be extremely happy to see some donations for the future of this project!

NXT: 1758531264253431177

Jesse James Aka DoctorEvil on the nextcoin forum (the one who cracked the genesis account passphrase) agreed to do some audit on the Crypto/Curve25519 code.

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

He said it mi-february. Any news?

Is there anything special about numpy's random generation? Why not just


?

Edit: You can also use os.urandom which is supposedly better since it uses the OS' native generator (/dev/urandom on Linux)

Fixed

BCNext intentionally used an algo that creates a small bias, otherwise he would use plain lottery for forging...

Am only referring to the "difficulty" question (not overall power to forge - they can divide up their NXT into multiple accounts right now).

couldn't the account just spread the NXT over more accounts and open more clients to forge?