Я однажды заслал перья в форкнутую цепочку - и ничего не вернулось. Если у nxt предусмотрена защита от этого - то здорово.
Да ну, перья устроены так же как и всё остальное. Не может так быть, чтоб после отката форкнутой цепочки деньги не вернулись. В худшем случае может быть надо блокчейн пересканировать, чтоб кошелек подсчитал баланс адреса. Я сидел на форкнутой и товарищ тоже, он получил я отправил. И все, потом в основной цепочке даже этих транзакций не оказалось. Перезагрузили блокчаин и все заработало Транзакций - не оказалось. Но и деньги не должны были пропасть - сколько было до транзы, столько у обоих и должно остаться. Мне в связи с этим очень интересны рассуждения господина Гравитона - куда у него 800000 NXT с dgex пропало. Но он как-то не очень поясняет - куда. Гравитон - это ЭпикТомас-2, тот еще жук. Поясните, о каких 800к идет речь? |
|
|
|
|
My question to BCnext:
What is your global plan?
|
|
|
|
hi, i'm yueye000 Considering Arbitrary Message is coming soon, I thinking about add more information into the alias, making this system more socialize. at least we need a avatar. I hope there is a standard for every client developer, but unfortunately, no standard. so i made this rule: Alias: yueye Uri: nxter:acc=5693933960808456307&img=bbyk.sinaapp.com/snake.png And we can add more, like nxter:acc=5693933960808456307&img=bbyk.sinaapp.com/snake.png&email=xxx@gmail.com&tel=12334555 I am not sure this is the best way, please tell me if something wrong.  This is very big security/privacy hole to force a client to load the image from external URL. |
|
|
|
guys I am stuck and no more blocks are getting downloaded  stuck at 32940 15401440438959943842 Sun 05 Jan 2014 Same here. Just restarted the daemon to get it working again. It's too bad that we need to do this daily. |
|
|
|
so if i want to run a hatcher on a VPS.... will it require any emunie credentials to be stored on the VPS?
I think so, there 'll be something like wallet.dat |
|
|
|
The customer who lost 14699 NXT has been reimbursed and I now also have a reserve fund.
It's not big, so there are sill no guarantees, but if your withdrawal is small enough and gets lost, there's a chance I will be able to cover it.
For larger sums - you are still on your own!
I don't want to end up in the same situation as dgex. Any losses will be immediately reported and if I won't cover them, they will be passed to the customer, instead of spreading among all other users.
So request smaller withdrawals, the volume is not high, I can handle additional load.
Argh, sometime you 'll understand how not serious it was  |
|
|
|
О, знакомые лица По теме - набирает обороты запасная любительская биржа 3го дивизиона - nxtchg.com |
|
|
|
|
Ricky, thank you for your investigation and help. NXT community should be proud of having such members.
I trust in case #3, possible another person found the poisoned code and changed it to sniff passwords to this own server instead of default hosted by EpicThomas.
Let's refresh my and other people memory by posting some facts again.
Did [ plasticAiredale, Framewood, PaulyC, sparta_cuss, or newcn ] report about running infected NXT client software ? It's quite important part of the investigation.
|
|
|
|
|
The first post of this thread should be updated with latest version 0.5.0 of the NXT Client Software released today.
|
|
|
|
|
Intel
Articles: info.nxtcrypto.org - NXT News website
|
|
|
|
It is indeed best if a forum were used that has no ties with any of the exchanges so that it can act in good faith at all times.
The best way is to host such a forum on Nxt network. Agree....would also protect forum from being DDOS Agree ... but till than we have to survive. Pin also afer NxT is able to host a forum we need normal web platforms. currently NxT has 8000 accounts and every user has min. 3-4 accounts. that meens we have 4000 user maximum. this is nothing, nobody knows about NxT at this moment. so we still need to provide all support in the normal web, also if there is an NxT internal forum. As soon as IM function of NXT 'll be ready, there 'll be possible millions of users, which is quite enough for truly anonymous communication stack building. |
|
|
|
any eta on that client prototype you built? it looked very nice from the pic starting tomorrow from scratch. the prototype was to evaluate different design approaches (code & gui). 3 weeks for the beta. 1 week testnet -> release, if no major bugs are found. Do you plan to make it open-source? |
|
|
|
|
Ok, digging the code right now. 3rd April is too long to wait for.
|
|
|
|
So when you send a transaction there is like a 0.1% chance it's corrupted and lost in the network.
It should be a priotiry to fix that. Like adding some byte of checksum.
And whatever if it's decreasing the "transaction-per-second" potential because nobody will use a network if it's not reliable. (even with it happen only 0.0001% of the time)
Reliability is 100 time more important than scalability
+1 |
|
|
|
Unfortunately due to the lack of support from the founders, with the exception of aldrin, I am forced to say goodbye.
I have worked through my vacation to come up with a strategic plan for NXT to get to 0.01 BTC and beyond. When the security issue came up, I debated with CfB who was stuck on "its impossible to add second layer of security because NXT is not centralized" to "API v2 will support second layer of security" Doesn't anybody see the significance of this?
I have pointed out the flaws in the addressing, came up with a solution, but not even acknowledgement from jean-luc and a few days later the same problem comes up again.
I have to make a living and I was willing to use up all my savings for living expenses while I worked fulltime on NXT. All I asked for was some incentive options, got only two responses. The more promising one was a "I will wait and see".
This lack of support does not give me the confidence to use up all my savings and I do have to make a living. I was one week late in discovering NXT, due to this I couldn't get enough to be set for life even if it does go up tenfold. Not sure if I will even be able to keep up with this thread, but I will try.
Goodbye NXT, I wish you luck in dealing with the competitors, bugs, usability issues, etc. without a strategic plan or anybody who is working on implementing the plan.
James
James, we really need you. Possible you are too tired of non-stop information flow of NXT. Just take a pause, your idea about public key in alias is excellent, it may find a continue. |
|
|
|
I just saw the warning and updated to .4.8, my balance is showing as zero but im behind on the blocks. I am super worried, my face is flush and I am scared! How can I catch up or see if anything happened? This would be really devastating to me if I got exploited with the fake client  Post the recent blocks information here |
|
|
|
Checksums will not help with this type of bug. Very likely the account to which the transaction was wrongly sent will also have passed the checksum.
If the address got corrupted on its way from GUI to server, then to network, checksum will prevent other nodes from accepting it. Not from the GUI to server, but during the interpretation in a corrupted Java process. The Java process simply can do any crazy thing when crashing. It's why many of You get their blockchain corrupted time to time - exactly for the same reason - Java process got corrupted during blockchain update. But in our case Java process got corrupted (for any reason) during transaction. |
|
|
|
|
** Do you keep the log with those exceptions? Please post it here or send it to me.
Unfortunately no.
What version were you running?
0.4.8 most likely
** Were you logged in at one account only at the time, or had several browser windows open?
** Were any other account mining in the background (if you closed their tabs without clicking the unlock icon first)? Any other relevant detail?
Several tabs with several accounts, one of them was forging.
** if you closed their tabs without clicking the unlock icon first
I do this often. It's possible.
** Checksums will not help with this type of bug.
** Very likely the account to which the transaction was wrongly sent will also have passed the checksum.
I agree
|
|
|
|
I bet i know the real reason for this. I had this issue also (transaction was sent to another account).
So, after i clicked "send", the GUI waited too long. Finally it said "sent". Then i checked blocks tab and found wrong recent blocks number, unconfirmed transactions and other signs of freezed java process. I instantly logged into the server and found several exceptions (not related to timeout) in the log. Few minutes later daemon died by not enough memory exception.
Instead of that useless CRC checks, it's better first to implement an additional check that the process itself is heathly and can be used to transfer money. Right, just few integrity checks before NXT transfer execution. It's Java. It's cross-platform. It's terrible and not really your friend.
GUI waits until all peers receive the transaction, the time heavily depends on pushThreshold value. Before sending a transaction NRS checks that its signature matches signed data, if recipient value was changed after signing the transaction wouldn't be confirmed. Due to crash of java process, the number entered and transferred to the daemon by Javascript UI was corrupted (or mixed during interpretation) inside the very first stage of transfer process itself. |
|
|
|
|
Show Posts
