Author

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

hero member
Activity: 798
Merit: 500
No, his Windows system was most likely compromised with keylogger/trojan. He didn't use vanitygen at all, afaik.

I also want to repeat my advice to use private browsing mode, or a separate browser profile, when accessing the Nxt server at localhost. It is a known issue that localhost url's containing the user secret phrase are retained in the browser memory cache. Could a malicious javascript planted on some website access and retrieve those?


Any plans to fix this?
hero member
Activity: 840
Merit: 1002
Simcoin Developer
- agree 100%

web-client is one of the most attractive feature of Nxt.

It also allows you to easily have both local and remote wallets.
sr. member
Activity: 392
Merit: 250
When I went jdeserialize.jar on the blocks.nxt, it could not read the iostream. Did I use a corrupt blocks.nxt, or is blocks.nxt encoded with a different iostream than transactions.nxt?
thanks!  Smiley
No, except there is a custom readObject method for the Block class. I have never tried that deserializer tool.
legendary
Activity: 1806
Merit: 1038
So what's the plan for it?
Get rid of it ASAP.
Why? It's not that bad. Already open-sourced. And it doesn't require anything, except a browser.
- agree 100%

web-client is one of the most attractive features of Nxt.
sr. member
Activity: 392
Merit: 250


oops: got the following on my raspi:

[2014-01-19 13:18:53.017] Loading transactions...
[2014-01-19 13:19:37.863] ...Done
[2014-01-19 13:19:37.866] Loading blocks...
[2014-01-19 13:20:22.443] ...Done
[2014-01-19 13:20:22.446] Scanning blockchain...
[2014-01-19 13:21:20.902] Error initializing Nxt servlet


maybe I have to try and start again without blocks.nxt and transactions.nxt ?!?!

Does it print out anything else after that? It should log the stack trace of the exception that caused the error.
hero member
Activity: 840
Merit: 1002
Simcoin Developer
BCNext is not a fan of MVC pattern and created a monolithic code that contains core functions and interface calls. We should get rid of interface to get a good-looking code.

And I was just about to revive the old bitcoin suggestion to split into core library and pure-interface clients... Sad

That idea has its benefits. For example, I don't have time to create a full-scale client, but wouldn't mind working on a simple interface, preferably in HTML+JS.


Nahh, ugly and unsecure. Some browsers cache your passphrase and so on...

Ugly can be fixed. Passphrases are only stored if they are passed via GET. This is bad API design, not client's fault.
hero member
Activity: 490
Merit: 504
I am so proud on a good idea to distribute the demythologization of the Nxt Myths Smiley
If this would be NXT without the very questionable initial distribution (and potentially more improvements over time compared to NXT because of opensource and more developers), then count me in. May be very interesting.
Q:  How would you solve problem with scam accusations according to "unfair" distribution Nxt to 73 big stakeholders?
BCNext: “This problem can not be solved.  Even if we had a million stakeholders the rest seven billion people would call this unfair.  A world with the money can not be perfect.”
That was a very bright reflection. Creds to this dude for putting sucha stupid statement in sucha serious way.

Yep. It's, called Capitalism. You have to have people at the top if you want people at the bottom, and without people at the bottom, there wouldn't be anyone at the top. The bottom want to be at the top, and the top don't want to be at the bottom. Of course it's unfair. It's Capitalism.

Based on the facts:

I just saw I had published Myths n. 2 without some text, so here it is all:

Q: „Do you think the unequal distribution of bitcoin / big gains of early adopters / will be a deterrent in a more widespread adoption of bitcoins?“
A: „No. Early adopters get bigger gains (as they should) because they take on bigger risk. A bitcoin can be divided into 100 million pieces, so I don't see divisibility or distribution as a problem.“
Cameron Winklevoss

The distribution of Nxt has many phases:

       Original IPO (1 NXT = 2 Satoshi)
       First week (1 NXT = 100 Satoshi)
       Second week (1 NXT = 400-2000 Satoshi) - first exchange
       Next month (1 NXT = 3000-6000 Satoshi) - aliases
       February (?) – distributed exchanges, stock exchanges (?)
       March (?) – transparent forging (?)
       April (?) – colored coins (?)

The distribution of NXT is very fair because it still continues. Now it isn’t in hand of one man, but it is a community effort. BCNext gave us a long time to get on the train.

If all coins are in existence already, doesn't this make the original holders of Nxt very wealthy?
Potentially. The original stakeholders of Nxt all made an investment of Bitcoin to seed their holdings, however, with no promise of any kind of success or return on investment.[1] In order to get more users they started to sell their stakes in undervalued prices and also they spent tenths of millions on bounties or giveaways. And BTW – who are original stakeholders? These who paid 2 Satoshi? Or 100? Or 400?

Q:  How would you solve problem with scam accusations according to "unfair" distribution Nxt to 73 big stakeholders?
BCNext: “This problem can not be solved.  Even if we had a million stakeholders the rest seven billion people would call this unfair.  A world with the money can not be perfect.”

Why was the launch of Nxt speeded?
Come-from-Beyond: „BCNext explained why he speeded up the launch. He wants the stake holders to make all important decisions“.  
BCNext: “I wanted Nxt to be launched by the community, not by a single person.  Success of Nxt is supposed to be achieved by work of a LOT of PEOPLE.”

When did Nxt really launch? Was it really in the day when the Billion NXT was transferred from the Genesis account to the original stakeholders? The IPO had been running for weeks in November 2013. In first days NXT cost 100 Satoshi. In first weeks of the December the price of Nxt was still about 400 Satoshi. Then 1500, 2000, 4000 before Christmas and if we don’t count the first bubble, we came back to the original 4000 in the middle of the January. But still – we have really bad client. Nxt is not yet traded in any of the big exchanges. There are many features – already programmed and tested – but they still weren’t implemented why?

Because we are still in a Beta. The launch wasn’t in November 24, it wasn’t in January 3, it will be in February/April. We all - 15.000 Nxt users - are beta original stakeholders. The distribution of NXT is extremely fair. The IPO still continues. We haven't launched yet. We can forget about some 73 stakeholders... Now everyone has an opportunity to jump on the train... and also to drive him! Why Nxt doesn’t use all features now? Because CBNext’s plan is to bring as many as possible users before the real Nxt will be released. Then we will have – more users, more features, all source code, but most important – this launch will be leaded by all Nxt community. This will be made by decisions of stakeholders. The success of Nxt is now supposed to be achieved by Nxt community, not BCNext.

What happened with the 21 Bitcoins?
Bitcoins were required to determine how to split the stake among founders. That's why BCNext asked for tiny amounts. These bitcoins were used to fund development but they covered only part of expenses. When people talk about Nxt IPO they forget about this important detail.  21 Bitcoins were used as a token amount. They didn’t represent any real world development costs.

Smiley
hero member
Activity: 910
Merit: 1000
So what's the plan for it?

Get rid of it ASAP.

Why? It's not that bad. Already open-sourced. And it doesn't require anything, except a browser.

Nahh, ugly and unsecure. Some browsers cache your passphrase and so on...
legendary
Activity: 2142
Merit: 1010
Newbie
Why? It's not that bad. Already open-sourced. And it doesn't require anything, except a browser.

BCNext is not a fan of MVC pattern and created a monolithic code that contains core functions and interface calls. We should get rid of interface to get a good-looking code.
legendary
Activity: 1181
Merit: 1018


oops: got the following on my raspi:

[2014-01-19 13:18:53.017] Loading transactions...
[2014-01-19 13:19:37.863] ...Done
[2014-01-19 13:19:37.866] Loading blocks...
[2014-01-19 13:20:22.443] ...Done
[2014-01-19 13:20:22.446] Scanning blockchain...
[2014-01-19 13:21:20.902] Error initializing Nxt servlet


maybe I have to try and start again without blocks.nxt and transactions.nxt ?!?!
hero member
Activity: 840
Merit: 1002
Simcoin Developer
So what's the plan for it?

Get rid of it ASAP.

Why? It's not that bad. Already open-sourced. And it doesn't require anything, except a browser.
legendary
Activity: 2142
Merit: 1010
Newbie
So what's the plan for it?

Get rid of it ASAP.
legendary
Activity: 1181
Merit: 1018
I tried that neat gimmick with jdeserialze to inspect the transactions.nxt -- NICE (thanks for the hint)

When I went jdeserialize.jar on the blocks.nxt, it could not read the iostream. Did I use a corrupt blocks.nxt, or is blocks.nxt encoded with a different iostream than transactions.nxt?
thanks!  Smiley
hero member
Activity: 597
Merit: 500

Added Asset Exchange related APIs:
getAskOrder, getAskOrderIds, getBidOrder, getBidOrderIds,
getAccountCurrentAskOrderIds, getAccountCurrentBidOrderIds.


great, thank you very much for adding these new calls jean-luc, the core
is going better and more stable every day, i really appreciate your work.

You need to thank CfB for that, he is the one working on adding APIs.

many thanks to both of you and all working on the core!
hero member
Activity: 840
Merit: 1002
Simcoin Developer
Added transaction re-broadcasting. To make sure a new transaction has
been received by the network, it is broadcasted every minute, until
it shows in the list of unconfirmed or confirmed transactions.

Oh my god, thank you!

This is not persisted between NRS restarts!

Ok. Still a big improvement, should cover 99% of problems.

Another issue I want to mention: if you restart NRS, but forget to reload the browser page, it can then pretend to send money, but won't actually do it.

Would be nice to have some sort of warning that you need to re-unlock your account.

Also, I know a lot of new clients are supposed to come soon, but I kinda like this browser-based client. So what's the plan for it?
newbie
Activity: 4
Merit: 0
Does it matter if i use http or https on localhost?
legendary
Activity: 2142
Merit: 1010
Newbie
Restarts? What restarts? 0.5.9 will need to be restarted only when 0.6.0 is released!

Right. But I have to shut NRS down when switch my computer off. Smiley
sr. member
Activity: 392
Merit: 250
Added transaction re-broadcasting. To make sure a new transaction has
been received by the network, it is broadcasted every minute, until
it shows in the list of unconfirmed or confirmed transactions.

Oh my god, thank you!

This is not persisted between NRS restarts!
Restarts? What restarts? 0.5.9 will need to be restarted only when 0.6.0 is released!
sr. member
Activity: 392
Merit: 250
Fast & Smooth!   Grin   ...can someone drop a few words on that JVM,--dry-run, etc. warning please...
Ask the jetty experts. I don't know why those warnings are needed, and how to disable them. They appear whenever a system property is defined in the jetty conf files, but the only simple way to disable the noisy jetty warnings is by defining the system property org.eclipse.jetty.LEVEL=OFF. I also use system properties nxt.debug and nxt.enableStackTraces to control our own logging.
hero member
Activity: 772
Merit: 500
Tried it using the faucet coins are missing and no where to found.

nxt account --> 4263246297020418968 Cry Cry Cry Cry
Jump to: