Thank you guys for the responses.
I just looked into my keepass 2 and i was using the following feature: 256-Bit Hex key Generator (Built-in). I never realized this is no truly random password because i didn't read the word "hex" ....
Does this make the password totally unsafe???
|
|
|
Omg, someone cleared 3 of my accounts.... I used 256bit keys generated by Keepass 2. I am using NRS 0.5.8 that installed today and downloaded from nxtcrypto.org. I am using Windows 7 Professional and am running Avira and Microsoft Security Essentials. The NXT was transferred about half an hour ago, also while i was forging. My PC was running unlocked but i can be 99.99% sure that no one had access to it physically. So I don't really know how this happend?!? It can't be bruteforce right? My accounts: 8423671173148912884 107,217 12345678612257264594 71 13486646175575465553 998 The NXT are now in this account: 696356957947686421 Balance Total : 108,286 NXT Fuck me... Btw the password of the third account was for example: af5c73ca7cf5f25ffa3b6b1689f40aaf60fd040b0de298c1ca661f8602d38311 Any chance of seeing these NXT again? ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
I predict the page 1000 will start in 1 Hour!
|
|
|
Why is there even a discussion? This is a POS currency, that says it is a 100% POS currency, now people want to game the POS system? lol@game playing, that is basically POW and the reason i prefer this coin over others.
1 NXT = 1 Vote but we should include a 0.01% Fee on voting (1 FEE or 0.01% whatever is higher)
|
|
|
I'll finally admit that I took all the investors money and tried to blame it on the Chinese Devs. This is the whole story, I was contacted by Chinese Devs on New Years about Shares. It seemed all legit and they sent me the Client and everything and they wanted me to post it . So I did and posted a Bitcoin Wallet that was in control by me and the Chinese Devs. Eventually after I saw all the money piling up I kinda got greedy. I said WOW look at all this money that I could have!!! So I devised a plan to steal the BTC and blame it on the Chinese Devs. Now knowing what I have done is big which could send me to Jail, I started to send out refunds to everyone. At First I had good intentions but after seeing how much money investors were throwing at Shares I got greedy. I'm still sending out refunds and only have a few btc left to give out. I'm sincerely sorry and once this is all done I will be gone off the forums for ever.
I want my 0.1 BTC back!!! 18888888PPJ8oGeqR6AKmoiKUme9da48Xf
|
|
|
can't access the site now, anybody has same issue?
edit:its able to access again, wonder why
I can access it, no problems.
|
|
|
Interesting that the account number 12968364353024827435 sent 100,000 NXT to the account 100000. He is the owner of the domain Gridcoinnetwork.org. I would like to know if he knows the password for the ID 100000 or did he sent it as a gift for the one who will get the account in the future. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) My bet is that he doesnt know the password to that one most likely that was a typo when he sent the same amount of coins to the field used for address does nxt handle 256 character passphase?
I believe the cutoff is 100 characters. But I dont believe there is anything preventing the use of a wallet.dat type client with 256bit long keys What is the sence in using a 256 character password on the wallet.dat if you could just bruteforce the first 100 digits passwords on the client directly? (I know this is all a very theoretical question, as noone can bruteforce a truly random 100 digit password ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) ) As I understand it, the 256 bits are checked on outgoing transactions, so you wouldn't be able to send money. no, a wallet file would be a client side implemention, and if you found the 100 digit private key, you will be able to send it.
|
|
|
Interesting that the account number 12968364353024827435 sent 100,000 NXT to the account 100000. He is the owner of the domain Gridcoinnetwork.org. I would like to know if he knows the password for the ID 100000 or did he sent it as a gift for the one who will get the account in the future. ![Huh](https://bitcointalk.org/Smileys/default/huh.gif) My bet is that he doesnt know the password to that one most likely that was a typo when he sent the same amount of coins to the field used for address does nxt handle 256 character passphase?
I believe the cutoff is 100 characters. But I dont believe there is anything preventing the use of a wallet.dat type client with 256bit long keys What is the sence in using a 256 character password on the wallet.dat if you could just bruteforce the first 100 digits passwords on the client directly? (I know this is all a very theoretical question, as noone can bruteforce a truly random 100 digit password ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) )
|
|
|
Why do you think this will be more successful than the hunt for tradefortress?
|
|
|
Awesome news. Thank you, Giancarlo!!!!
|
|
|
On way to avoid this is to just lower the rate you want. Higher rates are only take for ultrashorttime trades at this moment. (Just my 2 cents)
So if you offer a more competitive rate, your CFD will stay in a position much longer.
Well in the last hour, i had the same thing happen to me too. Maybe my strategy isn't as sound as i thought. Within 1 hour, the same amount canceled 5 times. (Always offered the best rate at 2 days lending time) ![](https://ip.bitcointalk.org/?u=https%3A%2F%2Fi.imgur.com%2Fosa4rtL.png&t=663&c=J9j07kEGQ9Wsfg)
|
|
|
On way to avoid this is to just lower the rate you want. Higher rates are only take for ultrashorttime trades at this moment. (Just my 2 cents)
So if you offer a more competitive rate, your CFD will stay in a position much longer.
|
|
|
rH2bnvsNhxwaVevV5Z8hRAdR2BAjEaXQxR
thx
|
|
|
thx rH2bnvsNhxwaVevV5Z8hRAdR2BAjEaXQxR
|
|
|
where's the original guy that was working on a whitepaper?
Busy, spending NXTs he got in advance, I think... If Nxt price doesn't rise too fast he'll run out of money in a few months and will complete the work... Where is rickyjames? ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) edit: oh yeah on the hunt for visacoin... Pin haha is he really? No. I'm trying to get a life. That is a good plan too! Also i think nothing will happen to visacoin, the case around TradeFortress showed, that not even 4000 BTC in claims are enough to track down someone and force him to give everything back ![Sad](https://bitcointalk.org/Smileys/default/sad.gif)
|
|
|
BTW why isn't the .bat file included in the zip ? It would one step less to launch Nxt.
because it doens't work on all windows instances. I for example have to specify the exact java.exe path.
|
|
|
where's the original guy that was working on a whitepaper?
Busy, spending NXTs he got in advance, I think... If Nxt price doesn't rise too fast he'll run out of money in a few months and will complete the work... Where is rickyjames? ![Cool](https://bitcointalk.org/Smileys/default/cool.gif) edit: oh yeah on the hunt for visacoin... Pin haha is he really?
|
|
|
WARNING: COME-FROM-BEYOND SAID IT IS UNSAFE TO LOGIN ON A NODE THAT IS NOT YOUR OWN.
|
|
|
With now nearly 100% of the IPOs being scams, i think that a solution has to be found. I think that a POS coin has some major advantages and a solution has to be found.
Solution 1: Burning the coins. To participate in the IPO you need to send BTC to a provably unspendable address. Solution 2: Donation the coins. An institution like Sean's Outpost could do so much good with the BTC that would otherwise get burned. Burned BTC make already rich people richer (all BTC holder profit marginally) Solution 3: Old system of just paying the Devs. Solution 4: A set goal of work needs to be done to participate. Set up a website or participate in the beta phase. Solution 5: Everyone that wants to participate just needs to sign up.
All of them have some downsides, so I think the solution with the biggest support has to be chosen for new legit projcts.
PS: I for one will not participate in any IPOs with option 2 anymore....
|
|
|
thanks, got: 12345678612257264594
|
|
|
|