Уважаемые, поправьте если ошибаюсь. Для обновление надо удалить папку lib из каталога установки NXT и разархивировать туда содержимое 1.10.1 с перезаписью?

Change log:

This release adds transaction replay protection, to be enabled at the hard fork
scheduled for block 1,000,000. Upgrading to 1.10.1 or later before that block
is mandatory for all.

The ecBlockId and ecBlockHeight transaction fields, previously populated but
not used, will begin to be used for enforcing that a transaction submitted on
one blockchain or fork will not be accepted on another blockchain or fork that
shares the same code. These fields by default will be set to a block 720 blocks
behind the last block at the time the transaction is created, and transactions
will only be accepted if their ecBlockId and ecBlockHeight values point to an
existing block when they are included in the blockchain. This default setting
provides protection against replaying the transaction on a hard fork that has
diverged more than 720 blocks from the one where the transaction was created.

Light clients that have no way of verifying the ecBlock values returned by a
remote node will use hardcoded values, to be updated manually at some releases.
Transactions from legacy light clients that leave eBlockId and height set to 0
will still be accepted, but cannot benefit from such replay protection.

All CreateTransaction APIs now accept additional ecBlockId and ecBlockHeight
parameters, allowing the default values to be overridden by the client.

Minor bugfixes and UI improvements.

Updated Jetty to version 9.3.11, delete the old lib folder before unpacking on
top.

Столкнулся с противоречивой записью( не дословно)- форжинг не доступен, у вас должно быть более 1440 подтверждений- они все с плюс ком показаны!!!

Проблемы есть. Нету этого файла nxt-default.properties.

Если я продам NXT до 12 октября то я не получу FNX, а ассеты ARDR я получу в таком случае?

вычистил с нуля начинаю ...блокчейн качать... мне интересен процесс форжинга

Прошелся по Вашей инструкции , еще раз , только перед тем вручную прописял весь путь - и удалось попасть куда следует!!!
Все повторил точь в точь , только блокчейн все равно с какого то перепуга продолжал качатся!!!

Подскажите, после запуска NXT2.0 платформа будет именоваться ...

Правильно ли я понимаю, что нужно будет загружать версию 1.9 дабы не потерять свои активы после выхода версии 2.0?

Чуть подробнее можно?

А зачем нужны регистрация псевдонимов?
Зарегал псевдоним  к нему адрес сайта прикрепил и что это дает?

Сделал. Но у меня нету файла nxt-default.properties. Только nxt.properties.

вопросик для начала назрел - 3-4 сутки железку не выключаю , а блокчейн так и не скачал , зависло дело где то POSередине процесса , 405 тысяч блоков осталось докачать!!!

Any word on sending out the IOTAs yet?

Farl4bit [2:08 AM] 
Still I have “Attaching to tangle”… @come-from-beyond Abord it?

robeneu [8:56 AM] 
I did some transaction replays and attached addresses but transaction has still no confirmations (0%). I will try to do more activity

Achim Heiniger [9:43 AM] 
@robeneu: The only thing that helped me to get old transactions from account A to B confirmed was to send all iotas to a new account C, wait for 100%, and then send to B again.

Andrew Lekar [5:55 PM] 
I have initiated tx in 1.0.1 and it was not confirmed. Now I upgraded to 1.0.2 and cannot get it confirmed as well   I have it stuck for 2-3 days already

Deng Shihao [6:12 PM] 
both 2 my bundles (different seeds) from 22.07 and 23.07 are at 0%

marcus [6:22 PM] 
I have the same situation. I have 2 bundles and done my tx from 23 july to 30 july. And only 1 tx is 100%

Andrew Lekar [10:03 PM] 
@dom: I got only one stuck tx and replay didnt help
so you can replay and replay forever

david c [3:57 PM] 
so my tx went through
but it stays at 0% persostence

Roman Latkovic [6:01 PM] 
What should I do guys? Subtangle not solid and Getting tips for days. I am unable to make one single transaction   Have enough nodes, all are working...

al joe [6:09 PM] 
@ dom How's it hanging? all my fake message bundles are confirmed with 100% Your leet iota package is still at 0%. Am doing something wrong here?

Coin Ter [7:08 PM] 
I have the same issue like greyghost. "subtangle not solid" since days... 24 / 146809 (2753) with 7 active neighbors...

Al3ks a [7:31 PM] 
how long wait for 100%   i wait for hours...

Coin Ling [9:09 PM] 
any news on how to get the persistence above 0%? !?
tried to replay like 10 times already and it is definitely not double spend

Roman Latkovic [9:10 PM] 
i'll trow a party if I ever manage to send a single transaction

Mickey Wood [10:44 PM] 
hmm, I'm still waiting for an incoming transaction from 23/07/2016... how long untill it is 100%? It's 8 days now ?!?

cryptokrill [11:42 PM] 
I’ve never seen replay work for me.

_mr_e [1:51 AM] Hi guys, this is a tx to me, that has not confirmed in 8 days
before 1.0.1 it was unreplayable by me
after the new gui, I have been able to replay it, but it hasn't helped

Arno Stachler [9:43 AM] Yes, incoming transactions. Yesterday they were 100%. After restarting the client, they showed 0%. Syncing over night didn't solve the problem. I tried replay, but after 6 hours nothing happend.

Michael M [9:51 AM] some transactions stuck at 0% persistence despite numerous replays.
I have replayed it, then turned on the spammer. I have done this for three days now. No luck.

Jon Comer [10:07 AM] Seems like wallet improvements are slight so far. Guess my escrow buyers will continue to wait

Stas [10:27 AM] did some sends that got 100% persistance, then after some time restarted the client and all of them got to 0% again

Farl4bit [11:57 AM] I am still trying to transfer IOTA, but did not succeeded in it for 2 weeks now.
I replayed it several times, I have good neighbours, I am synced. It just doesn’t seem to happen.

Andrew Lekar [2:25 PM] I saw at least 3 persons who only sent one tx at a time and still got a doublespending

Ian Metten [3:31 PM] ...with the third node I always get "The confirmed subtangle is not solid" error. I deleted db and resynched, selected various subset nodes in config. The node is on 24/7

david c [3:40 PM] my tx is still 0% after a replay... what should i do next?

Deng Shihao [3:47 PM] 2 my bundles are at 0% for a week, after 10th of replays, and after 3 re-sending to another adresses..

Farl4bit [5:25 PM] Two (small test) transactions went fine (both 100%). The third (big) transaction did not go well, after 3 hours still 0%. In the meantime I was spamming a lot with more than 100 transactions generated.

Interested [5:40 PM] why is my subtangle not solid i have 21 160283 and 2913 but it is still not solid

Farl4bit [11:07 PM] Fuck, still no confirmations.

Jon Comer [3:31 AM] Im fully synced and running well but cant confirm 3 hours and going

T Cy [3:36 AM] I have three pending transactions that I'm trying to get my purchased IOTA from ... I wonder how much longer it'll be until everything is running smoothly

mf11 [9:47 PM] Did several replays (followed by spamming) from sender and receiver side. Up to now without success....

robeneu [9:35 PM] So if my computer doesn't generate proof of work in less than 20 minutes, I can give up trying to send any iotas, right?
Not sure how long does it take for me. Address generation can take 45 mins. "Attaching" is shorter than "getting tips". So maybe I am within the limit.
But replays are much longer. 2 hours and more.. I have not a single confirmed transaction after several weeks of trying

Парни, подскажите почему на локалхост не заходит из правильного способа запуска? Помню была такая проблема на заре времен и вот сейчас опять.

2016-07-31 22:16:42 INFO: Nxt server 1.10.0e started successfully.
2016-07-31 22:16:42 INFO: Copyright © 2013-2016 The Nxt Core Developers.
2016-07-31 22:16:42 INFO: Distributed under GPLv2, with ABSOLUTELY NO WARRANTY.
2016-07-31 22:16:42 INFO: Client UI is at http://localhost:7876/index.html

В бирже полонеиксе при переводе необходимо available for withdrawal написать свой номер кошелка NXT-****-****-****-****? G

А известно когда будет этот момент запуска?

Для форжинга с помощью WEB-кошелька, нужно держать браузер открытым? Этот момент не совсем ясен.

запутался чуток. Будет еще одна монета? (тогда их называли FXT) Как я понял если я продам свои NXT до 12го то получу только Ardor, а что бы получить FXT нужно держать и после 12го?

This is an experimental release introducing the new light client and roaming
client features.

The roaming client feature, enabled by default, makes the client immediately
usable by forwarding API requests that need the full blockchain to a randomly
chosen peer (remote node), selected to provide the openAPI service. As all html
and javascript files are still served locally and not from the remote host,
this is considerably safer than just using a remote node. Outgoing transactions
are also signed locally, never sending the secret phrase to the remote peer.

This roaming client (API Proxy) mode is used automatically while the blockchain
is still downloading, with a switch to full client mode once the download is
complete.
It can be disabled by setting nxt.enableAPIProxy=false in nxt.properties.
For openAPI nodes, the API proxy remains disabled, ignoring this setting. For
light clients, the API proxy is always enabled.

The light client feature, disabled by default, makes the node run in roaming
mode permanently, without downloading the blockchain at all. It can be enabled
by setting nxt.isLightClient=true.
Light clients are not advertised as providing openAPI service even if they do
have their API publicly accessible.

The remote node to use when in roaming and light client modes is selected
randomly, but can be changed manually in the UI, or using the new
setAPIProxyPeer API, or forced to a specific peer using the
nxt.forceAPIProxyServerURL property.

Remote nodes can be blacklisted from the UI, or using the blacklistAPIProxyPeer
API. This blacklisting is independent from peer blacklisting. The API proxy
blacklisting period can be set using the nxt.apiProxyBlacklistingPeriod
property (default 1800000 milliseconds).

API requests that require sending the secret phrase, shared key, or admin
password to the server, for features like forging, shuffling, or running a
funding monitor, are disabled when in roaming or light client mode.

While a remote node cannot steal your secret phrase, and data returned by such
nodes is escaped to prevent javascript injection attacks, users must be aware
that the validity of such data cannot be verified. For example, a rogue remote
node can still return fake asset exchange recent trades or open orders prices,
or modified voting system poll options and descriptions.

To force using a remote node for testing APIs, the /test-proxy URL can be used
instead of /test for the API test page, i.e. http://localhost:7876/test-proxy.

A new sendTransaction API has been added, similar to broadcastTransaction but
without validating the transaction, without re-broadcasting the transaction and
without adding it locally as unconfirmed transaction. This API is mostly useful
for light or roaming clients that cannot validate or accept locally unconfirmed
transactions, but must nevertheless be able to send such to peers.

A new getNextBlockGenerators API has been added, returning the next block
generators ordered by hit time. The list of currently active forgers is first
initialized using the block generators with at least 2 blocks generated within
the previous 10,000 blocks, excluding accounts without a public key. The list
is updated as new blocks are processed. The results are not 100% correct since
previously active generators may no longer be running and new generators won't
be known until they generate a block.

Added a peer info modal. Minor other UI improvements and bugfixes.

Ух, то есть будет две независимых сети - ARDR и NXT 1.0?