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

Hey, I made a windows app for my nxt web interface;

You can download it here: http://nxtra.org/nxt-client/NxtWalletWindows.zip

Just run NxtWallet.exe to start.

Proof of concept at this point, probably bugs in there. Please report.

Donations appreciated at 8189784314684138350

I have also sent the html interface to jean-luc, hopefully it will be in the next version (it is in this NxtWallet.exe already)

Btw, "tools" menu doesn't do anything at the moment.

Thanks, as far as I understand this, this is not the actual version but something about v0.7. Correct?

It doesn't

http://www.docjar.com/html/api/org/apache/commons/lang/RandomStringUtils.java.html

I am planning on generating a random seed when a user enables google authenticator and storing the encrypted version in the blockchain. That will keep it safe from being lost (at least until blockchain purge, guess need to regenerate seeds again).

I dont want to use keypass, I dont want to secure any database. I just want to be able to generate a google authenticator token when a withdraw request is made. So I need a C callable function where I pass in the random seed for the user and get back a pass/fail response. Some details about synchronizing the pass/fail response with user input.

I dont want to spend time figuring out how to configure a server, etc. I need somebody that can setup their own server with webpage that I can send an API to. Once it is all working, we can move it to the gateway server to avoid sending anything over the internet.

James

http://www.docjar.com/html/api/org/apache/commons/lang/RandomStringUtils.java.html

They use java.util.Random

Where do you see SercureRandom used by RandomStringUtils?

It will be shown as disconnected (permanently) if it cannot be reached at its announced address, or visible address in case it does not announce an address. It may also be switched to disconnected temporarily if a connection fails, but will appear connected again the next time it succeeds.

If you´ve read my PM, I am trying to help you build a core dev team...

We only publish in the near past, this way we control the future

https://bitbucket.org/JeanLucPicard/nxt/src/

Possibly, I will see what it takes for fractional assets. The comment field is an easier change, I will do that, but will have to reset the test blockchain again.

I´m glad you are back

Are there any plans to publish the complete and actual source code somewhere in the near future?

I only found the source code of v4.6. Is ther something more actual available?

To increase the benefit of "forging", we can add a commission (eg Nxt 0.01) each time you start the client, this creates more comisones for forging and people are more interested in not close the client, not to return to charge the fee.

Is this possible?

Sorry for my English
----------------------------------------
Para aumentar el beneficio de "forjar", podemos agregar una comision (ejemplo 0,01 Nxt) cada vez que iniciemos el cliente, esto crea mas comisones para los que forjan y la gente esta mas interesada en no cerrar el cliente, para no volver a cobrar la comision.

¿es esto posible?

Perdon por mi ingles

I don't believe I know better than the people from Apache who made that library.
That library is used in 1000s of production systems. You should not reinvent the wheel.

You are right about the difference between SecureRandom and Random, in the code I posted it does however not make sense to use SercureRandom. If you believe it does please explain why it does make sense in the code I posted.

https://github.com/ciyam/ciyam/blob/master/src/crypt_stream.cpp#L173

Although it is of course in C++ (if you search around you should be able to find it in C).

Am back from Hong Kong now (wasn't online at all for two days so have been busy trying catch up all afternoon).

As far as people wanting me to be a "core dev" I don't think it would make much sense as I am a C++ programmer not a Java programmer (and have only even looked at a small amount of the source code) so at this stage I will keep my main involvement to the AT side of things but may get involved with other things down the track.

As far as pools are concerned I think we are going to need them and without them we won't be able to create a "savings account" AT (which I think would be something fairly attractive from a marketing perspective).

I had stated before that my preference for limiting the power of an individual pool account would be to limit the number of accounts that it can use (so that trying to allocate your forging power to a "full" account would actually fail) or to limit the max. amount of forging power to a max. % of total coins (say 1%). Of course there is no reason that both of these limits would not be able to be imposed.

Someone else suggested the leased forging power to be restricted according to the balance of the forging account and I think that it could also be a reasonable way to do it.

The key thing that we are going to want to have is a "lot of small pools" rather then a "few huge ones" so I think we should try and focus on ideas that are going to make it easier for small pools and harder for large pools.

Yes, I will still be here after CfB leaves.

So you are saying I have managed to fix that bug? Are there any known AE bugs that are still reproducible in 0.8.6?

Instead of relying on RandomStringUtils, isn't it much simpler to just use SecureRandom to create the password?

char[] allowedCharacters = {'a','b','c','1','2','3','4'};

SecureRandom random = new SecureRandom();
StringBuffer password = new StringBuffer();

for(int i = 0; i < PASSWORD_LENGTH; i++) {
    password.append(allowedCharacters[ random.nextInt(allowedCharacters.length) ]);
}

I will look into that after I am done with the rest of my near term plan. I need to prioritize features, and this is again not a simple change. Supporting fractional amounts is critical because it is needed not only for the AE.

FreeRider AE Client released later today. Stay Tuned.