Topic: NRS v1.2.5f (Read 14583 times)

Jean-Luc · « **on:** August 15, 2014, 10:24:00 pm »

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Release 1.2.5f

https://bitbucket.org/JeanLucPicard/nxt/downloads/nxt-client-1.2.5f.zip

sha256:

b6f3a06936debdde4f9730369dafeba9c49e2b681d3f311c9976df3b04f00432 nxt-client-1.2.5f.zip

Change log:

Bugfixes. Keep retrying block generation when failing due to invalid transactions.

Ignore peer weights when hallmark protection is disabled. Set hallmark protection
to disabled by default as it can break blockchain downloading in some cases. This
is a change in nxt-default.properties.

The changelog from 1.2.5b is repeated below:

This release disables all outgoing transactions from the BTER account:
10715382765594435905 after block height 209885.

If you use this release, existing blocks after that height will be deleted,
but the transactions in them preserved and reprocessed, except those originating
from the BTER account, and those with deadline already expired.

A rescan with validation will be performed automatically at start, it will take
longer and perform another rescan at the end.

This is an optional release. Forgers have a choice whether to use it, or stay
with the old 1.2.5 release, the community needs to decide whether to do the
rollback or stay with the old fork.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBAgAGBQJT7oZlAAoJEFOhyXc7+e2A6f8P/RiDs1c3J2bXAoRk9x2iMV7B
4twnwCyk/hVxNhBpN5wAI8FJ5yx9azznH8vxD3Yir8XbtDdbtDRauF508Y1A6NH8
IOJX3/zeiHIphaa5aqS3kW1fgcDNaiVuaI80GH+5ygoRkJQwAWtZ/v26nGJPe7wS
u7JE+p0r7OeWexowNmXWDo8InxYV+hMj/vjqT4CTCsSEVDqhyISMrq6pN7emsJNa
hVqPDOMDDgkTXsUC7QSIrOS5VADTdii/+nAfpkjac54Hfg1sSOAnFO1rrSMz4v7H
UPUfPB4bIpyp1HlKKHkc2hZYrJpGQna9XUs0nuhM+oZJxv5VFuLf9dUulPJj6QPq
qhDaMknwVqUEMvq9wGgPWhL88ZyNg39LWsDpLftp3ogGw00Zvx2EAjODaWo9YTF7
mLatB/c9QWo1DGUPcUfpKvaKESU0Mm3Gl7gleyn3DN/a/7isTaAZIcMbFLz1mdnX
r4Qs1Mn2AMEPa0dkaC28j+bY4usw1KLnsg8Slg7ciaQaZ66r6wBv2PJvhxMH8g9o
eMYCQpLFsC0m8+hAytj2C+P7kg/9DkXdMWB/tYfPT8lRWbwnUE9SgPCT1fm2avZM
sxawtAalijviwLERrqR9pCKAhE7FzWB64fnt3GGeefvHeGxNzFoNCzPjdazNd4Fz
7FjKB9vc1LEVZPgjn7iZ
=HLiy
-----END PGP SIGNATURE-----

beor · « **Reply #1 on:** August 15, 2014, 10:29:50 pm »

Uff, updated!

apenzl · « **Reply #2 on:** August 15, 2014, 10:31:31 pm »

Thanks for giving this option.

lezin · « **Reply #3 on:** August 15, 2014, 10:57:29 pm »

Thanks for giving the option too

renat0 · « **Reply #4 on:** August 15, 2014, 11:04:16 pm »

Please let us help bter. I'll be forging for bter. They helped us before with the klee incident. Don't let this opportunity pass by, we only have a few hours. 2m$ is a lot of money.

TeamWealth · « **Reply #5 on:** August 15, 2014, 11:07:29 pm »

Take that bitcoin! You have had no development to speak of in the past few months but today alone we have had 5 complete releases! Anyone want to help market this?!?!

Either way, all the NXT i hold is leased out to other people on all accounts, Im just glad i dont have to make a bad decision vs a bad decision.

colin012 · « **Reply #6 on:** August 16, 2014, 12:17:14 am »

Let me see if I understand this. The new versions, 'd' and 'f' would only freeze the hackers account rather than do a roll back?

colin012 · « **Reply #7 on:** August 16, 2014, 12:19:44 am »

Quote from: apenzl on August 15, 2014, 10:31:31 pm

Thanks for giving this option.

While I still refuse to state my opinion on what we should do. I think it is important that this option is provided. Thank you JL!

Wakasaki808 · « **Reply #8 on:** August 16, 2014, 12:21:44 am »

Quote from: colin012 on August 16, 2014, 12:17:14 am

Let me see if I understand this. The new versions, 'd' and 'f' would only freeze the hackers account rather than do a roll back?

none of what Luc did would be a rollback. They just freeze the accounts.

colin012 · « **Reply #9 on:** August 16, 2014, 12:30:23 am »

Quote from: Wakasaki808 on August 16, 2014, 12:21:44 am

Quote from: colin012 on August 16, 2014, 12:17:14 am
Let me see if I understand this. The new versions, 'd' and 'f' would only freeze the hackers account rather than do a roll back?

none of what Luc did would be a rollback. They just freeze the accounts.

To my understanding, it locks/freezes the account from the block just before the theft, which would still make it a rollback that makes it so the theft never really happened. Can one of the devs confirm that I understand this right?

eimon · « **Reply #10 on:** August 16, 2014, 12:40:36 am »

Is it compatible with the MGW? If not I won't use it. MGW was my main reason for investing in NXT

Coradan · « **Reply #11 on:** August 16, 2014, 06:46:35 am »

There will be a problem with this if hacker buys BTCs or LTCs by MGW or another exchange for NXT

nexern · « **Reply #12 on:** August 16, 2014, 07:13:08 am »

thx jean luc to provide a choice (it's all about choice, no matter what result) and btw, you are doing a very good job at all (like a swiss watch).
i am glad you are handling the core and providing besides a rock solid core also the best api seen in cryptocountry.

blueface · « **Reply #13 on:** August 16, 2014, 07:16:25 am »

Quote from: nexern on August 16, 2014, 07:13:08 am

thx jean luc to provide a choice (it's all about choice, no matter what result) and btw, you are doing a very good job at all (like a swiss watch).
i am glad you are handling the core and providing besides a rock solid core also the best api seen in cryptocountry.

yeah,its a choice,anybody can do this..

bgcaffe · « **Reply #14 on:** August 16, 2014, 07:55:16 am »

We just keep getting the following error running this client:
nxt.NxtException$NotValidException: attempted to create a block with 276 transactions
at nxt.BlockImpl.<init><BlockImp1.java:50)

Is the f client fully functional?

Are we still getting the choice to freeze the hackers account or is it too late?

wesley · « **Reply #15 on:** August 16, 2014, 07:56:05 am »

Quote from: bgcaffe on August 16, 2014, 07:55:16 am

We just keep getting the following error running this client:
nxt.NxtException$NotValidException: attempted to create a block with 276 transactions
at nxt.BlockImpl.<init><BlockImp1.java:50)

Is the f client fully functional?

Are we still getting the choice to freeze the hackers account or is it too late?

You can stop running this client, it's too late.

bgcaffe · « **Reply #16 on:** August 16, 2014, 08:31:08 am »

Quote from: wesleyh on August 16, 2014, 07:56:05 am

Quote from: bgcaffe on August 16, 2014, 07:55:16 am
We just keep getting the following error running this client:
nxt.NxtException$NotValidException: attempted to create a block with 276 transactions
at nxt.BlockImpl.<init><BlockImp1.java:50)

Is the f client fully functional?

Are we still getting the choice to freeze the hackers account or is it too late?

You can stop running this client, it's too late.

Ok. Thanks. So we are waiting on Bter to see if they can resolve this, I guess the funds on Bter are probably lost then..

igmaca · « **Reply #17 on:** August 16, 2014, 10:55:33 am »

must promote mgw.
It is the best solution

S3MKi · « **Reply #18 on:** August 16, 2014, 05:28:18 pm »

too late

bgcaffe · « **Reply #19 on:** August 16, 2014, 05:41:43 pm »

Quote from: wesleyh on August 16, 2014, 07:56:05 am

Quote from: bgcaffe on August 16, 2014, 07:55:16 am
We just keep getting the following error running this client:
nxt.NxtException$NotValidException: attempted to create a block with 276 transactions
at nxt.BlockImpl.<init><BlockImp1.java:50)

Is the f client fully functional?

Are we still getting the choice to freeze the hackers account or is it too late?

You can stop running this client, it's too late.

According to JL it is not too late, we can still choose the f client for a hard fork. This type of misinformation is not fair, it seems like most of the senior members are not really explaining to users the choice they have?

News:

Author Topic: NRS v1.2.5f (Read 14583 times)