2019-07-19 15:05:58 +01:00
|
|
|
#Generated by ResourceBundle Editor (http://essiembre.github.io/eclipse-rbe/)
|
2019-07-09 12:40:00 +01:00
|
|
|
# SysTray pop-up menu
|
2019-07-19 15:05:58 +01:00
|
|
|
|
2019-07-25 11:08:43 +01:00
|
|
|
BLOCK_HEIGHT = height
|
|
|
|
|
|
2019-07-19 15:05:58 +01:00
|
|
|
CHECK_TIME_ACCURACY = Check time accuracy
|
|
|
|
|
|
2019-07-25 12:42:08 +01:00
|
|
|
CONNECTION = connection
|
2019-07-25 11:08:43 +01:00
|
|
|
|
|
|
|
|
CONNECTIONS = connections
|
|
|
|
|
|
2019-07-19 15:05:58 +01:00
|
|
|
EXIT = Exit
|
2019-07-09 12:40:00 +01:00
|
|
|
|
2019-10-29 17:46:55 +00:00
|
|
|
MINTING_DISABLED = NOT minting
|
2019-07-25 12:42:08 +01:00
|
|
|
|
2019-10-29 17:46:55 +00:00
|
|
|
MINTING_ENABLED = \u2714 Minting
|
2019-07-25 12:42:08 +01:00
|
|
|
|
2019-07-05 12:12:11 +01:00
|
|
|
# Nagging about lack of NTP time sync
|
2019-07-25 11:08:43 +01:00
|
|
|
NTP_NAG_CAPTION = Computer's clock is inaccurate!
|
|
|
|
|
|
|
|
|
|
NTP_NAG_TEXT_UNIX = Install NTP service to get an accurate clock.
|
2019-07-19 15:05:58 +01:00
|
|
|
|
2019-07-25 11:08:43 +01:00
|
|
|
NTP_NAG_TEXT_WINDOWS = Select "Synchronize clock" from menu to fix.
|
2019-07-19 15:05:58 +01:00
|
|
|
|
2020-03-10 13:32:10 +00:00
|
|
|
OPEN_UI = Open UI
|
2019-07-19 15:05:58 +01:00
|
|
|
|
|
|
|
|
SYNCHRONIZE_CLOCK = Synchronize clock
|
NTP and performance changes + fixes.
New NTP class now runs as a simplistic NTP client, repeatedly polling
several NTP servers and maintaining a more accurate time independent
of operating system.
Several occurrences of System.currentTimeMillis() replaced with NTP.getTime()
particularly where block/transaction/networking is involved.
GET /admin/info now includes "currentTimestamp" as reported from NTP.
Added support for block timestamps determined by generator, instead of
supplied by clock. (BlockChain.newBlockTimestampHeight - not yet activated).
Incorrect timestamps will produce a TIMESTAMP_INCORRECT Block.ValidationResult.
Block.calcMinimumTimestamp repurposed as Block.calcTimestamp for above.
Block timestamps are now allowed to be max 2000ms in the future,
was previously max 500ms.
Block generation prohibited until initial NTP sync.
Instead of deleting INVALID unconfirmed transactions in BlockGenerator,
Controller now deletes EXPIRED unconfirmed transactions every so often.
This also fixes persistent expired unconfirmed transactions on nodes
that do not generate blocks, as BlockGenerator.deleteInvalidTransactions()
was never reached.
Abbreviated block sigs added to log entries declaring a new block is generated
in BlockGenerator.
Controller checks for NTP sync much faster during start-up and SysTray's
tooltip text starts as "Synchronizing clock" until NTP sync occurs.
After NTP sync, Controller logs NTP offset every so often (currently every 5 mins).
When considering synchronizing, Controller skips peers that have the same block sig
as last time when synchronization resulted in no action, e.g. INFERIOR_CHAIN,
NOTHING_TO_DO and also OK. OK is included as another sync attempt would result in
NOTHING_TO_DO.
Previously this skipping check only happened after prior INFERIOR_CHAIN.
During inbound peer handshaking, if we receive a peer ID that matches an existing inbound
peer then send peer ID of all zeros, then close connection.
Remote end should detect this and cleanly close connection instead of waiting for handshake timeout.
Randomly generated peer IDs have lowest bit set to avoid all zeros.
Might need further work.
Networking doesn't connect, or accept, until NTP has synced.
Transaction validation can fail with CLOCK_NOT_SYNCED if NTP not synced.
2019-07-31 16:08:22 +01:00
|
|
|
|
2020-03-19 11:07:56 +00:00
|
|
|
SYNCHRONIZING_BLOCKCHAIN = Synchronizing
|
|
|
|
|
|
NTP and performance changes + fixes.
New NTP class now runs as a simplistic NTP client, repeatedly polling
several NTP servers and maintaining a more accurate time independent
of operating system.
Several occurrences of System.currentTimeMillis() replaced with NTP.getTime()
particularly where block/transaction/networking is involved.
GET /admin/info now includes "currentTimestamp" as reported from NTP.
Added support for block timestamps determined by generator, instead of
supplied by clock. (BlockChain.newBlockTimestampHeight - not yet activated).
Incorrect timestamps will produce a TIMESTAMP_INCORRECT Block.ValidationResult.
Block.calcMinimumTimestamp repurposed as Block.calcTimestamp for above.
Block timestamps are now allowed to be max 2000ms in the future,
was previously max 500ms.
Block generation prohibited until initial NTP sync.
Instead of deleting INVALID unconfirmed transactions in BlockGenerator,
Controller now deletes EXPIRED unconfirmed transactions every so often.
This also fixes persistent expired unconfirmed transactions on nodes
that do not generate blocks, as BlockGenerator.deleteInvalidTransactions()
was never reached.
Abbreviated block sigs added to log entries declaring a new block is generated
in BlockGenerator.
Controller checks for NTP sync much faster during start-up and SysTray's
tooltip text starts as "Synchronizing clock" until NTP sync occurs.
After NTP sync, Controller logs NTP offset every so often (currently every 5 mins).
When considering synchronizing, Controller skips peers that have the same block sig
as last time when synchronization resulted in no action, e.g. INFERIOR_CHAIN,
NOTHING_TO_DO and also OK. OK is included as another sync attempt would result in
NOTHING_TO_DO.
Previously this skipping check only happened after prior INFERIOR_CHAIN.
During inbound peer handshaking, if we receive a peer ID that matches an existing inbound
peer then send peer ID of all zeros, then close connection.
Remote end should detect this and cleanly close connection instead of waiting for handshake timeout.
Randomly generated peer IDs have lowest bit set to avoid all zeros.
Might need further work.
Networking doesn't connect, or accept, until NTP has synced.
Transaction validation can fail with CLOCK_NOT_SYNCED if NTP not synced.
2019-07-31 16:08:22 +01:00
|
|
|
SYNCHRONIZING_CLOCK = Synchronizing clock
|