Closed Thread

[sava0123]

If somebody can, please provide a screen shot of that error!

[englishbad]

If somebody can, please provide a screen shot of that error!

yes！

[SillkRoad]

@Thanks for testing
We write all the errors here https://docs.google.com/document/d/1Mu1BG811L2-OGJTBdKTARtQKljs1SXIJnFWoRcKSLFI/edit
In the next version we will gradually fix all errors

[hypersire]

@devs

I am afraid the people that were reporting getting a different account were right...  

I had only checked my balance through the block explorer because there was no SSL...  waited patiently for the client...  plugged in my passphrase...  different account...  

NO copy paste from a text file either...  I have the passphrase hand-written on a piece of paper...  


Edit:  Can you please upload the Account Generator somewhere?  

I am referring to the one we used when you asked us to change accounts...  I want to see if I am getting the same account number.  

smaragda, from what I remember from people who reported the same issue, it turned out to be caused by one of two reasons:

1) the person was using an account number from the first server and never made an account on the new server when the devs requested it (when they did the sock puppet IP check)

2) I remember someone else who had their passphrase written down, and after trying several variations they were able to get in.

Don't know what else it could be as the devs has assured everyone that nothing has been touched in the algorithm since the second server went live. So if you logged in and verified the account then, it should be the same today.

[zhaohui]

the wallet shows: Loading .......please wait!

[zhaohui]

Loading ... Please wait!      how long do I have to wait?

[SillkRoad]

Loading ... Please wait!      how long do I have to wait?

https://docs.google.com/document/d/1Mu1BG811L2-OGJTBdKTARtQKljs1SXIJnFWoRcKSLFI/edit

wait for the update next version

You need to understand something is the first version, we will fix bugs

[HunterMinerCrafter]

Linux/OSX client?  Source?

The nodewebkit binary version shipped for the client has some known vulnerabilities.  I would not recommend to anyone to run this version until we can easily run against our own nodewebkit.

Anyone know of an easy way to extract a nodewebkit app from a windows exe packaging?  I'm not too familiar with nodewebkit binary builds.

EDIT: nevermind, I got it... I'll post an analysis and hopefully some instructions on how to run this thing more safely shortly.

[yaoxin]

Loading ... Please wait!      how long do I have to wait?

can not open the wallet , have waited 10 minutes

[BigWait]

Loading ... Please wait!      how long do I have to wait?

can not open the wallet , have waited 10 minutes

can not open ,too

[DynhoSts]

The nodewebkit binary version shipped for the client has some known vulnerabilities.  I would not recommend to anyone to run this version until we can easily run against our own nodewebkit.

Are you trying to say it doesn't run locally?   

this guy @hunterminer.... only want to spread  fud to this coin ...

[HunterMinerCrafter]

The nodewebkit binary version shipped for the client has some known vulnerabilities.  I would not recommend to anyone to run this version until we can easily run against our own nodewebkit.

Are you trying to say it doesn't run locally?   

Dunno, haven't actually run the thing just yet.  

All I'm saying is that it appears that the node binary included is not most recent, so some known vulnerabilities are there.

[HunterMinerCrafter]

this guy @hunterminer.... only want to spread  fud to this coin ...

Only want to see the source running safely and decentralized, as was promised, still.

[HunterMinerCrafter]

Source inside the binary was partially obfuscated, but not very well.  Here is the source to the app.js: http://pastebin.com/a7JzU7kv

EDIT: These devs love those low entropy passwords, eh?

Code:

        var Config = function() {
            return {
                port: 19775,
                host: "127.0.0.1",
                starPeers: ["5.45.124.65:19776", "5.45.114.108:19776"],
                peerPort: 19776,
                serverKey: "qwerty123456",
                devMod: false
            }
        }();

<3 that serverKey!

[SillkRoad]

Source inside the binary was partially obfuscated, but not very well.  Here is the source to the app.js: http://pastebin.com/a7JzU7kv

EDIT: These devs love those low entropy passwords, eh?

Code:

        var Config = function() {
            return {
                port: 19775,
                host: "127.0.0.1",
                starPeers: ["5.45.124.65:19776", "5.45.114.108:19776"],
                peerPort: 19776,
                serverKey: "qwerty123456",
                devMod: false
            }
        }();

<3 that serverKey!

This password access to the IP logs
The Commission knows
What do you want to say it?

[dzarmush]

OOPS...  PLEASE DELETE ALL MESSAGES IN WHICH YOU HAVE QUOTED ME REPORT THE PASSPHRASE ISSUE...  I HAD THE WRONG PIECE OF PAPER IN FRONT OF ME!?!?!     ROFLMAO!  

...I will delete all my posts immediately...

No, let's show it to everybody) People should check everything on their side before starting freaking out and blaming devs  

[gvans]

OOPS...

Well that is good news anyhow. Good for you and me too... was getting anxious to get home from work to double check my account 

[DynhoSts]

people !!! send emails to BITTREX E-MAIL LINK to add NODE ... we want more people sending emails to bittrex add our coin

[HunterMinerCrafter]

This password access to the IP logs
The Commission knows
What do you want to say it?

I know, it is just funny in the context of my having found coins behind the low entropy password.

I've just finished skimming the app.js and everything looks decent.

I am happy to see that the address generation is not nearly as broken as it appeared from external analysis!  No worry of address collisions.

Now I go on to verify the node_modules packages and the frontend.  Things are looking up, but you will certainly want to run this with newest nodejs versions, v0.8.28 and v0.10.30.  The version in the distribution is older, and has known vulnerabilities which appear to be able to be exploited through the peering.  (Specifically, I just tested the most recent stack munging from Fedor et al in a sandbox and was able to (at least  ) remotely crash a peer.)

[baby222]

so next version when will release？