nxt client

Early NXT investor ‘MAAC‘ has taken much of the limelight as he overruled “normal” participants by using the advanced features of the Nxt Blockchain as well as his stake to get ahead of the competition from Day 1.

In what was supposed to be a fair and equal early-bird lottery, divided into 12 batches as a way to stop whales from buying up all the tokens in the early stage of the ICO (as they tend to do), the IGNIS ICO was meant to be different.

The Get-There-First Hackathon

The theory that MAAC had used a bot to pick up the first 2 batches of Round 1 got turned down by MAAC himself, but behind the scenes, intense coding WAS going on, and an investment bot with the aim to out-compete all other attempts to invest in the IGNIS ICO WAS underway.

NRS 1.11.7 is not a small bugfix release – you must run this client version if you want a chance to get JLRDA tokens from the ICO. Furthermore, with NRS 1.11.7 you will not have to get up early / stay up late for the 2 daily 30-minute release windows, you can just enter your bid in advance and check the result of the lottery later as it fits your schedule. Read more…

So, are we equal now?

A public message from another whale that got his hands on most of Batch #7, soon kicked off discussions among new and veteran Nxt users.

Speculation and over-thinking

Coincidence? Will leasing your NXT stake to a forging pool optimize your chances of getting an early stake in IGNIS? Could it be that connecting to 500 peers instead of the client’s default helps? How about hallmarking your node, will that give extra chances? How much does the size of the fee matter?

Well, let me be straight: About as much as the color of the shirt I wear matters.

Private discussion groups have been forming in Slack and all kind of mods and optimization tricks have been pulled off and tested, but no matter how hard anyone tries, the facts are hard to ignore:

# Maintain active connections with at least that many peers.
nxt.maxNumberOfConnectedPublicPeers=75

apenzl [1:02 PM]

Were you forging or was your account balance leased to a forging account?

scor2k [1:03 PM]

No )))

The number of Nxt nodes is growing, Nxtwiki sees new visitors; driven by a monetary incentive crypto investors are learning about the Nxt technology, not just the coin, which will be the backbone of Ignis and the Ardor Platform. And so, they begin to understand Nxt’s features (mind you, most crypto ICO’s usually sell tickets to not-existing technology – Nxt has been running stable and been improved upon by world-class developers for almost 4 years).

This is good.

By learning about the NRS client and server they grasp the power of Nxt, Ignis, and Ardor.

forkedchain [9:39 PM]

it appears that MAAC was splitting his NXT into orders with 400.000 NXT in each

napdude [9:43 PM]

MAAC risked tons of nxt to get his fills in the last many rows

“This shit project will not exist next year”!

Oh yes, it will. We must emphasize something, though:

Nxt’s powerful ‘Smart Transactions’ (inbuilt smart contracts) are only as smart as the people using them! Some people get desperate or make transactions too fast without knowing what they do.

Then they get angry.

PLEASE DO NOT PLAY AROUND WITH FEATURES YOU DON’T UNDERSTAND!

A few ICO adventurers have tried to take shortcuts but ended up worse than they started.

Some have bought JLRDA look-a-like currencies from the Monetary Exchange, fake JLRDA assets on the Nxt AE or the Nxt Marketplace, despite all warnings. One new user managed to broadcast a phased transaction to himself, which has locked his NXT for 7 days, using advanced functionality in the client.

One new user managed to broadcast a phased transaction to himself, which has locked his NXT for 7 days, using advanced functionality in the client.

That’s “learning the hard way”. One can react sanely, or by simply crying “shit ICO you bad take my money”, frown publicly upon Nxt, Ignis, Ardor, Jelurida – and about everything from the 1 NXT transaction fees to – understandably – not being able to get in at this very early point of the ICO.

Most though has found the ICO setup ingenious.

The adrenaline!!!!

Yes, IGNIS will be traded on exchanges eventually, and ICO participants may or may not (well, we won’t give trading advice here) make a fortune from their early investment, but what Jelurida is selling are operational tokens, the access to the first child chain of the Ardor Blockchain Platform.

Don’t fall for scammers

An old scam trick on the Nxt blockchain is sending out teasers in the form of tokens, for example, an asset issued for 1000 NXT but worth a lot more if the scammer succeeds, so he sends it to NXT accounts, it’s like ads on blockchain, an airdrop of assets which he hopes will make Nxt users think: Wow. Is this what I’m looking for? I’ll buy more!

NRS 1.11.7 release notes

This release adds the ability to submit a JLRDA purchase transaction from the IGNIS Token Sale page even before the sell offer has been published.

Such transactions are not broadcasted immediately, but held in memory and only sent out when the expected sell offer arrives in the unconfirmed transaction pool.

For this to work, you must keep the node running after submitting the purchase transaction, until the sell offer has been received and processed.

Note that after submitting a purchase transaction in advance of the sell offer, you will get a pop-up that your currency buy order has been submitted, but it will not show in the unconfirmed pool. This is normal as such advance orders are kept separately.

This functionality is currently available for full nodes only, i.e. those that have downloaded the full blockchain. Users of light clients can submit JLRDA purchase transactions only after the sell offer has been accepted in a block. To switch from a light client to full node, set nxt.isLightClient=false in conf/nxt.properties, and wait for the blockchain to download.

More IGNIS Token Sale UI bugfixes and improvements:

Add paging buttons to the exchange history table on the Ignis page.

Initialize the JLRDA units field to 0.

Fixed "calculate fee" when connecting to a remote node with remembered passphrase.

ScheduleCurrencyBuy API accepts same parameters as CurrencyBuy API, and an additional offerIssuer parameter. Instead of broadcasting the prepared transaction immediately, it schedules it to be broadcast as soon as an unconfirmed currency exchange offer transaction from that issuer, for that currency and a sell rate not higher than the requested, arrives in the unconfirmed transaction pool. The broadcast parameter must be set to false. This API requires a full node (not a light client) and admin password unless running on localhost.

GetScheduledTransactions API returns a list of all scheduled transactions for a given account.

Note that these APIs were specifically added for the purpose of the IGNIS Token Sale, and may be removed or modified in the future.

Other fixes and improvements:

Allow blacklisting the real remote host, not the proxy, when running a public node behind a reverse proxy. Use the nxt.forwardedForHeader property to configure the header added by the proxy to the API http requests (normally X-Forwarded-For).

Fixed printing of paper wallet for passphrases containing special characters.

WARNING: If you printed out a paper wallet for an account passphrase which contains special characters using an earlier release, this passphrase may have been printed out incorrectly, with those characters missing, or truncated. In this case you are advised to print out a correct copy using this version. The QR codes were not affected by this bug, and neither were the standard account passphrases generated by the client.

Also note that some long passphrases may be cut off by your printer unless page size is adjusted to width.

ALWAYS VERIFY THAT THE PRINTED PASSPHRASE IS CORRECT BEFORE RELYING ON A PAPER WALLET AS YOUR ONLY BACKUP!

FAQ

NRS is a locally hosted client server application. By default it downloads the Nxt blockchain, but from version 1.10.0e you can run it as a light client as well as a full node. To forge and earn forging fees from processing transactions on the network you must run the Nxt Client in full mode, which is possible even on small devices like laptops, or on a Raspberry Pi.

The Nxt Client is easy to install. Use the 1-click installers for Linux, Mac and Windows or read this INSTALLATION GUIDEto launch the NRS .zip from terminal.

ICO Release FAQ

Q: What's the priority to execute these buy orders when they will hit blockchain? Same as usual?

A: As soon as the node scheduler storing the scheduled transactions sees the exchange offer as an unconfirmed transaction, it will immediately broadcast your currency buy transactions.

And they will compete with the rest of the transaction for inclusion in the next block, according to the usual transaction priority.

Q: So, if I understand correctly, this new stuff is for users to make buy transaction in advance, instead of lurking near PC and try to be fast?

A: Exactly

Q: And if my advanced buy order is not filled, I need to repeat the same before the next batch? Am I right, this new stuff do not solve MAAC problem?

A: It does solve it, since MAAC found a way to submit his transaction while the Jelurida exchange offer was still unconfirmed and invisible to the UI.

With 1.11.7, every scheduled transaction will do exactly that.

Q: When does Jelurida exchange offers become valid? Only when approved or broadcasted?

A: When the Jelurida exchange offer is still unconfirmed the scheduler will submit the buy orders

Q: Will not wait for approval of it?

A: They will all approve in the same block, the exchange offer will have the earliest arrival time so the currency buy transactions will match it in the same block just like MAAC did it manually

Q: But looking at history, approval account approves exchange offer few block later. I feel some confusion here. Always thought, that without approval any transaction is not "valid".

A: The exchange offer will no longer be phased, just a regular transaction

Q: And if my scheduled buy order is not filled, I need to repeat the same order before the next batch?

NRS is a locally hosted client-server application. By default, it downloads the Nxt blockchain, but from version 1.10.0e you can run it as a light client as well as a full node. To forge and earn forging fees from processing transactions on the network you must run the Nxt Client in full mode, which is possible even on small devices like laptops, or on a Raspberry Pi. There are also bounties for running public nodes.

The Nxt Client is easy to install. Use the 1-click installers for Linux, Mac, and Windows or read this INSTALLATION GUIDEto launch the NRS .zip from terminal.

NRS is a locally hosted client server application. By default it downloads the Nxt blockchain, but from version 1.10.0e you can run it as a light client as well as a full node. To forge and earn forging fees from processing transactions on the network you must run the Nxt Client in full mode, which is possible even on small devices like laptops, or on a Raspberry Pi. There are also bounties for running public nodes.

The Nxt Client is easy to install. Use the 1-click installers for Linux, Mac and Windows or read this INSTALLATION GUIDEto launch the NRS .zip from terminal.

ARDR Snapshots

Snapshotting will start at block 870400 (expected July 14) and end at block 1000000 (Oct 12). Relevant reading: Ardor distribution

To get your ARDR tokens, it is recommended that you keep your NXT balance in your own account.

For balances on exchange accounts, it will be up to each exchange to handle the re-distribution of the ARDR tokens that will get automatically sent to the exchange account at snapshot end.

The 3 major exchanges for NXT;Poloniex, BTC38, andBittrex will all run internal snapshots of their customers' NXT balances synchronized with the main blockchain. The Ardor tokens will then be distributed to their rightful owners at a ratio of 1 Ardor token for 1 NXT. The exchanges are prepared for new customers outside the Fintech and investment world looking to purchase Nxt tokens for future Ardor tokens with the introduction of fiat currency exchange. Retail customers will now be able to access the Ardor platform and purchase tokens using fiat currency.

NRS 1.9.2 release notes

This is the first stable release in the 1.9 series. Update to this release on mainnet is optional up until block 1000000 (Oct 12), however users are advised to do it earlier, as after July 14th updating will trigger a blockchain rescan.

NRS is a locally hosted client server application. By default it downloads the Nxt blockchain, but from version 1.10.0e you can run it as a light client as well as a full node. To forge and earn forging fees from processing transactions on the network you must run the Nxt Client in full mode, which is possible even on small devices like laptops, or on a Raspberry Pi. There are also bounties for running public nodes.

The Nxt Client is easy to install. Use the 1-click installers for Linux, Mac and Windows or read this INSTALLATION GUIDEto launch the NRS .zip from terminal.

The 3 major exchanges for NXT;Poloniex, BTC38, andBittrex will all run internal snapshots of their customers' NXT balances synchronized with the main blockchain. The Ardor tokens will then be distributed to their rightful owners at a ratio of 1 Ardor token for 1 NXT. The exchanges are prepared for new customers outside the Fintech and investment world looking to purchase Nxt tokens for future Ardor tokens with the introduction of fiat currency exchange. Retail customers will now be able to access the Ardor platform and purchase tokens using fiat currency.

NRS 1.9.0e release notes

This is an experimental release.
It is a required update for all testnet nodes, optional for main net.

This release enables taking multiple snapshots of accounts NXT balances, every 60 blocks, for a period of 90 days, and distributing an ARDR token based on the average of those balances, at the end of the snapshot, to be used for the Ardor consensus chain token distribution in Nxt 2.0.

On testnet, the snapshot will start at block 649400 and end at block 779000 (June 24).

On mainnet, the snapshot will start at block 870400 (expected July 14) and end at block 1000000 (Oct 12).

Since on testnet the starting block is in the past, on upgrade to this release a blockchain rescan will be performed automatically in order to calculate past account balances. Those who delay upgrading their mainnet nodes until after block 870400 will also experience such a rescan. However, the hard fork block is set at the end of the snapshot, so the final deadline for upgrading to 1.9 is at blocks 779000 and 1000000 respectively.

To get your ARDR tokens, it is essential that you keep your NXT balance in your own account. There is no need to run a node or forge. It is the confirmed NXT balance that is used for the snapshot, not the unconfirmed (available) balance, so having some NXT locked in open AE bid orders, shufflings, etc, will not affect your ARDR distribution.

For balances on exchange accounts, it will be up to each exchange to handle the re-distribution of the ARDR tokens that will get automatically sent to the exchange account at snapshot end.

A new getFxtQuantity API has been added, which allows retrieving the already accumulated ARDR quantity for each account during the snapshot, and an estimate for the quantity yet to be obtained. While snapshots are done every 60 blocks, the numbers that this API returns are updated once every 720 blocks only.

Snapshot balances used for the ARDR distribution for a specific account can be recorded in the log by setting the nxt.logFxtBalance property to that account number, and performing a rescan if the snapshot has already started.

Added some additional transaction bytes validation, and phasing parameters validation, to take effect after the hardfork.

Added getAssetDividends API, to retrieve the dividend payment history for an asset. It can be viewed in the client by clicking on the new "View Asset Dividends" link on the asset exchange page. Dividend payments made before a node is updated to 1.9.0e will not show in this history, unless a blockchain rescan is forced manually.

After the hardfork block, asset dividend payment transactions will be limited to not more than one per asset every 60 blocks.

Added a new Messages table in the client UI. Allowed uploading a file as a message attachment, plain or encrypted, and downloading such messages as files.

All create transaction APIs that support prunable message attachments now also optionally accept multipart file uploads as messageFile or messageToEncryptFile parameters, or when using client-side encrypted data the data part can also be uploaded using encryptedMessageFile parameter. As the test API page does not support multiple file upload parameters, upload buttons for those are not currently available there.

Added client UI support for decrypting messages using a shared key, to allow disclosing the shared key for a specific encrypted message to a third party in order to decrypt it without having to reveal the account passphrase.

Forging optimization to reduce block skipping when switching forks.

Minor other bugfixes and UI improvements.

Updated H2 library to version 1.4.192, tika to 1.13, and slf4j to 1.7.21. If
installing manually, make sure to delete the old lib folder first.

NRS is a locally hosted client server application. By default it downloads the Nxt blockchain, but from version 1.10.0e you can run it as a light client as well as a full node. To forge and earn forging fees from processing transactions on the network you must run the Nxt Client in full mode, which is possible even on small devices like laptops, or on a Raspberry Pi. There are also bounties for running public nodes.

The Nxt Client is easy to install. Use the 1-click installers for Linux, Mac and Windows or read this INSTALLATION GUIDEto launch the NRS .zip from terminal.

New features

Coin Shuffling

Coin shuffling can be used to perform mixing of NXT, MS currencies (unless created as non-shuffleable), or AE assets. Any account can create a new shuffling, specifying the holding to be shuffled, the shuffle amount, number of participants required, and registration deadline. This is done using the shufflingCreate API.

The subsequent shuffling steps can be done either manually, by using the shufflingRegister (for accounts other than the
creator), shufflingProcess, shufflingVerify or shufflingCancel APIs, or, much more conveniently, by starting an automated Shuffler, using the startShuffler API.

Once started, the Shuffler monitors the blockchain state for transactions relevant to the specified shuffle, and automatically submits the required transactions on behalf of the user, performing shuffle processing, verification, or cancellation as needed. To do this, the Shuffler is required to keep the user secret phrase in memory, therefore it should be run on a trusted local machine only.

A restart or a crash of the node requires the shuffler to be started again using the startShuffler API, as it should never save the user secret phrase on disk.

To participate in a shuffling, a deposit of 1000 NXT is needed, in addition to the amount of currency or asset being shuffled. Or if shuffling NXT, the amount of the shuffle must exceed this 1000 NXT minimum. If the shuffling completes successfully, this amount is added to the recipient account balance, to allow it to send outgoing transactions (as it is required that only new, unused accounts are specified as recipients). If the shuffle fails due to a registered participant failing to participate as required, or intentionally submitting false data, the participant responsible for the shuffle cancellation is penalized by retaining this deposit and sending it to the forgers of the shuffle finish block and the previous three blocks instead.

If a shuffle is cancelled because the required number of participants is not met, nobody is penalized and all deposits are refunded. On testnet, the deposit and penalty is 7 NXT only.

After shuffling registration is complete, participants must submit processing data within a 100 blocks period each (10 blocks on testnet). For the verification and blame phase, the total allowance for all participants is 100 + numberOfParticipants blocks (again reduced to 10 + n blocks on testnet).

Full blocks are not counted towards the limit. If at any stage the deadline is reached without some participant submitting the next required transaction, the shuffling is cancelled at this participant’s fault. It is therefore critical that after registering for a shuffling, the shuffler started is left running until its successful completion. If the node must be restarted, all previously running shufflers must be started again manually.

If desired, finished shufflings can be automatically deleted from the database if the nxt.deleteFinishedShufflings property is set to true (default is false).

The fee for creating a shuffling or registering in one is 1 NXT, for the
shuffling process or shuffling cancel transactions 10 NXT, and for the verify transaction 1 NXT.

Account control for phased transactions

Any account can be restricted to only be allowed to issue phased transactions subject to a specific voting model.

This is achieved by the account submitting a setPhasingOnly transaction using the setPhasingOnlyControl API. The getPhasingOnlyControl API can be used to retrieve the status of an account phasing control, and getAllPhasingOnlyControls to get all accounts subject to phasing control with their respective restrictions.

Once set, the phasing only account control can only be disabled or changed with another setPhasingOnly transaction, itself subject to the currently set phasing restrictions.

Note that by-transaction and by-hash voting models are not allowed for phasing control, and setting voting model to none is used to disable the control.

To prevent deadlocks due to cyclic account control restrictions, approval transactions themselves (PhasingVoteCasting) are not subject to phasing only account control.

When setting phasing account control, a maximum fees total can be specified, limiting the total fees for currently pending phased transactions of the controlled account, and limits can be placed on minimum and maximum phasing duration allowed.

Transactions of accounts subject to phasing account control with restriction on maximum fees are throttled at one per account per block.

Immediate release of phased transactions on approval

Phased transactions with a voting model that does not depend on account balance (such as by-transaction or by-hash), or by-account with no minimum balance and with a whitelist, will be released before their finish height as soon as approved (in the block in which the transaction causing their approval is executed), if possible.

Such early finish is guaranteed for transaction types known to be phasing safe. For others, if the early finish does not succeed due to the transaction failing validation at this height or conflicting with another transaction in the same block, a second, final release attempt will be performed at finish height.

New base target adjustment algorithm

Average block times will be 60 s, with 1440 blocks per day. Block times should practically never exceed 10 min.

Limit of 1000 NXT on minimum forging balance

This applies to the total of the account own guaranteed balance plus any balances leased to it, but not to each individual balance lease. An account with balance lower than the limit can still lease its balance to another.

Account properties

Those are name / value pairs that can be set on any account (except Genesis), by either the account owner, or by another account. Names are limited to 32 characters, and values to 160 characters. Names are unique per account and per setter account, but not globally unique. Account properties cannot be transferred between accounts.

The setter of an account property can edit it by replacing its value with another. Either the setter, or the recipient (if different) of an account property can delete it. There is no limit on the number of properties an account can have. Fee for setting account property is 1 NXT for value up to 32 chars, with additional 1 NXT fee for every 32 chars after that.

Account properties are managed using the setAccountProperty and
deleteAccountProperty APIs. To query the properties of an account, or those set by an account, the getAccountProperties API can be used.

Singleton assets

Issuing an asset with a quantity of 1, decimals 0, and description length not exceeding 160 characters, will require a base minimum fee of 1 NXT only, instead of the regular 1000 NXT asset issuance fee. For description of more than 32 chars, an extra 1 NXT fee is added for each 32 chars. Asset name for singleton assets is limited to 10 chars, same as for regular assets.

Throttling of unique resource allocation transactions

Asset issuance (excluding singleton assets), monetary system currency issuance, and alias assignment (excluding re-assignment), will be limited to only one transaction of each type accepted per block.

Spreading back block fees for asset and currency issuance

The transaction fees for asset (excluding singleton assets) and currency issuance will be split between the forgers of the current and the previous three blocks in a 4:3:2:1 ratio.

Prunable plain and prunable encrypted message attachments both allowed in the same transaction

The maximum data size for each such attachment is 42 kbytes, but when coexisting in the same transaction the sum of the two is still being limited by the maximum payload size of 44880 bytes.

Peers that provide http or https API access open to anyone are labelled as providing a service

Peers that provide http or https API access open to anyone, configured with nxt.apiServerHost=0.0.0.0 and nxt.allowedBotHosts=* , are now labelled as providing a service, API or API_SSL, and can be found using the getPeers API with the corresponding “service” parameter. This API has been modified to
accept multivalued “service” parameter, returning peers that match all requested services. The ports on which the open API access is running are included in the peer info of peers providing those services as apiPort and apiSSLPort fields.

Incompatible changes

Deletion of asset shares

Deletion of asset shares will be performed as a separate AssetDelete
transaction type instead of as sending the shares to Genesis. Sending shares to Genesis will no longer be allowed. A new API, getAssetDeletes has been added to retrieve asset deletions, as using the getAssetTransfers API to find transfers to Genesis account no longer can be used for that purpose.

There is also a new API, getExpectedAssetDeletes, to get asset deletes expected in the next block, analogous to getExpectedAssetTransfers.

Messages

Since both prunable plain and prunable encrypted messages can now be added to the same transaction, the APIs getAllPrunableMessages, getPrunableMessage, and
getPrunableMessages cannot continue to use just a single “isText” boolean field in the JSON response to indicate if the prunable message is text or binary.

For all prunable plain messages, a new “messageIsText” boolean field is added, and for all prunable encrypted messages, a new “encryptedMessageIsText” boolean field is added in the response of the above APIs, for each message.

For backwards compatibility, the “isText” field will continue to be added, but only for transactions that have either plain, or encrypted, prunable message attachment, not for those that have both.

This change does not affect the attachment JSON returned from getTransaction API, as there are already separate messageIsText and encryptedMessage.isText fields there.

Fees and size limit changes

Several transaction types or attachments will have new fees and size limits, to encourage users to utilize the prunable versions when available, and to make fees proportionate to actual blockchain space consumed.

Aliases

Base fee 2 NXT, with 2 NXT additional fee for each 32 chars of name plus URI total length, after the first 32 chars. Name and URI size limits remain at 100 and 1000 chars respectively.

Messages and EncryptedMessages (non-prunable)

Maximum length reduced to 160 bytes. 1 NXT fee for each 32 bytes after the first 32 bytes. For encrypted messages, the length is measured excluding the nonce and the 16 byte AES initialization vector, and to account for those there is an extra fee of 1 NXT.

Fees and size limit for prunable messages remain unchanged.

AccountInfo

Base fee 1 NXT, with 2 NXT additional fee for each 32 chars of name plus description total length, after the first 32 chars. Name and description size limits remain at 100 and 1000 chars. AccountInfo transactions throttled at one per block.

Polls

Base fee 10 NXT for polls with up to 20 options, and total size of poll name plus poll description plus total option length not exceeding 320 chars. For each option above 20, an additional fee of 1 NXT, and for each 32 chars after 320, an additional fee of 2 NXT. Poll creation throttled to one per block.

DGS Listing

Base fee 2 NXT, with 2 NXT additional fee for each 32 chars of name plus description total length, after the first 32 chars. Name and description size limits remain at 100 and 1000 max. DGS Listing throttled at one per block.

Phasing

In addition to the current fee for phasing (1 NXT for balance independent, 20 NXT otherwise), 1 NXT will be added for each 32 bytes of hashedSecret or linkedFullHash fields.

Referenced transactions

An extra fee of 1 NXT for the 32 byte referencedTransactionFullHash if set, i.e. if the transaction is using the referenced transactions feature.

To facilitate migration of legacy client code to the new fees, if the property nxt.correctInvalidFees=true has been set in nxt.properties (default is false), the server will automatically replace insufficient fees for submitted unsigned transactions with the minimum fee needed, depending on the transaction, as if feeNQT=0 has been specified. Fees exceeding the minimum, or fees for already
signed transactions, will not be corrected.

Secondary sort of search results after sorting by relevance, by timestamp if
for any seller, or by name and then by timestamp if for a single seller.

Improved performance of Marketplace page, show counts for goods in stock only.

Increased default purchase delivery deadline to 168 hours (1 week).

Include full peer info in getPeers API if includePeerInfo=true, to avoid having
to do a separate getPeer request for each peer.

Include cumulativeDifficulty in the block JSON.

Allow transaction signing in signTransaction to skip the validation of the
transaction bytes being signed, if an optional validate=false parameter is added.
This would be useful when signing transaction bytes on a machine that doesn’t have
the full blockchain downloaded, which normally prevents validation.

This is the first major update after initial mofowallet release. Improvements were made on almost all levels.

API Request Manager

The network request layer has been completely rewritten, it is now aware of all active and pending (API) requests. Requests are grouped and can be prioritized or cancelled all together, requests are bound to the controllers that started them and are automatically destroyed when the controller is destroyed.

Network requests are executed from a central interval (timer) and is no longer event based. The interval acts as an external agent that can take action and cancel requests if they either time out or take too long to start (when higher ranked requests take up all available slots).

The number of concurrent requests are set at six for now, this seems to work well while running on localhost and when connected to public API servers.

Decentralized API

Improvements are made in the usage of the decentralized API, users can run their own API server and add these to mofowallet. Because multiple public API servers are used, synchronization among those servers has to be performed on startup. Synchronizing involves a check if the server is up and functioning and a detailed analysis of the fork that the server is on.

Public API servers that are on a fork are ignored for the current session, thereby not wasting any network traffic.

API servers are required to have SSL enabled and must use a proper certificate.

Embedded Servers

Users are prompted if they want to start the embedded FIMK and/or NXT server on startup, options for each server are available to either start automatically or never start at all.

Users can run both servers at the same time but this does put a higher load on your system. However, running the servers is not required since mofowallet is fully functional when operating on the public API servers only.

Forging

Forging/mining is supported for all embedded servers. The blockchain must be downloaded before you can forge blocks. The forging UI has been updated and now requires your secret phrase to be entered only once, either enter your secret phrase or open your wallet file containing your secret phrase.

To see if you forged any blocks you will, for now, need to look at the amount forged label in the accounts section. Better feedback of exactly what blocks you forged and other info, like charts and averages, are under development.

Namespaced Aliases

Namespaced aliases now support encryption. This is the same encryption AES encryption offered for normal messages. Namespaced Aliases can be encrypted so only the owner account can decrypt or where the owner account and one other account can decrypt that.

Asset Exchange

Introducing the initial Asset Exchange UI for FIMK and NXT. UI is read only in this release meaning you cannot enter or cancel orders. Asset Exchange is a work in progress and it’s anticipated that it will change considerably. Our aim is to offer a professional full featured interface to both the FIMK and NXT decentralized exchanges. We consider a professional UI one that offers traders all tools required to do your daily trading.

Current AE UI includes:

1. historical price charts
2. listing of all available assets
3. display of current price and 24 hour percent change

Planned AE UI additions:

Better Messaging

Better support for sending plain text or encrypted messages. Message transactions in the transaction history are displayed inline now. If you provided your secret phrase, messages are decrypted on the fly and can be seen inline in the account transaction history but also in the blockexplorer.

Startup Service

New service available to all plugins, plugins register with the startup service to do intialization upon application startup. Plugins register so called activities that show progress in the startup dialog, activities can be made to run only after certain other activities have finished running.

The startup dialog can be hidden by the user and the mofowallet is usable from that moment on. If certain functionality in mofowallet depends on an activity to complete it will be disabled until the activity has completed.

Highly Contextual Identifiers

All identifiers for blocks, transactions, accounts, aliases, block heights and more now support mouse events. Plugins can register for mouseover, mouse out and click events. This has enabled everything from the blockexplorer to the account section to be *clickable* and will show you a details dialog in which everything is again clickable.

Bugs fixed

Fixed a bug where sometimes sending a transaction does not immediately show up in your list of recent transactions. This now works correctly for all broadcasted transactions.

See exactly when one of your accounts will forge a block (through a countdown)

Send and receive NXT

View all your past transactions

Create or update your aliases

Issue assets on the asset exchange

Buy/Sell assets on the asset exchange

Manage your asset portfolio, see how much assets you own and what their current value is in BTC or EURO

Send and receive encrypted messages

Use it’s live block explorer which lists all past blocks and transactions and allows you to lookup any block, transaction or account

Access the block explorer from every part of the application, you can for instance click on an account number in your transaction overview and it will open that account in the block explorer (same goes for all transactions and blocks)

See blocks and transactions coming in live

Get a live view of all connected peers, see how much you upload/download, you can even send them a message (if they are hallmarked)

Blacklist/unblacklist any peer you are connected with

See exactly how far the blockchain has downloaded (up to the second)

Delete and re-download the blockchain simply from the menu.

And much more …

Download

OFFSPRING VERSION 0.4.5

Please see the WIKI for instructions on how to verify the SHA1 and MD5 hashes.

Basic info:

NXT Solaris

(http://nxtsolaris.wordpress.com/)

Solaris is a full featured NXT client for Windows. As well as the usual Nxt features, including Asset Exchange, Solaris boasts several features that are not native to Nxt, such as marked information, monitoring and an address book, as well as support for multiple accounts. The installation process is simple, and the user can choose between open or closed source versions. The source code was released on February 16, 2014.

More info: http://www.nxtcoins.nl/client-showcase-nxt-solaris/

ClieNXT

ClieNXT is a simple open­source client written in Java, as is the native Nxt client, NRS.
The current version (0.0.4) has one­click install and autoupdate ability as well as all of the basic Nxt functionality. One additional feature us the ability to send multiple transactions or messages using Nxts AM system.

More info: http://www.nxtcoins.nl/client-showcase-clienxt/

DotNxt

DotNxt was announced on the 14th January 2014 as an entrant in the Nxt client competition and was released on the 18th of the same month. Source code was released on the 1st February. DotNxt aims to be a simple and accessible easy install client with a clean interface and simple design values. It supports all current features, and is built using Microsoft .Net Framework 4.0.

Offspring stoers NXT private keys (passphrase) together with Offspring account label in an encrypted file. While other clients still use “brainwallet”, this now provides wallet files known from Bitcoin wallets.

More info: http://www.nxtcoins.nl/client-showcase-offspring-dgex/

NXT Wallet

NXT Wallet is a web client with many features including Asset Exchange. It is currently connected to Testnet which is a test version of NXT network used by developers. It provides Contacts, Messages, Aliases and even Polls and a list of News. So you can read news from the Nxt forums, blogs, or social sites straight from the web client. It will be packaged as a downloadable program for Windows, Linux and Mac.

nxtFreeRider

(http://www.quicknxt.com/FreeRider)

This is not classical client for average users, but a valuable complement to the other clients: It is a powerful tool for developers, with focus on the Asset Exchange system. It is a fully open sourced python implementation for api communication. Program can be extended by anybody easily by modifying existing stuff in there.

Nxs

Nxs, pronounced “Nexus”, is a modified version of the default NRS web client that includes many new features and a more modern design. It allows to set a language or to show QR code of the current unlocked account. It includes new secret phrases generator. Users can also use up to 100 predefined sippers to obscure their secret phrase from dictionary words. Its source was released February 18.

How to start a newsletter when Nxt has already been on the roll for 2.5 months?

This week’s topics:

Upgrade!

Asset Exchange

Nxt Funds released

BCNext’s plan (part 2)

Organize, NXTers!

Clients

ANNOUNCEMENTS

Quote of the week

Words of wisdom of the week

Upgrade!

This week a critical bug was found in the Nxt core.
If you are still running a client below 0.6, update to the latest client at nxctcrypto.org (404 link removed) NOW.

Jean-Luc wrote:
Fixed a critical bug. Everybody should upgrade immediately.
No explanation, just that. Later followed the reason for several upgrades during the same day:

Critical bug DISCLOSURE

Come-from-Beyond:

Few days ago the guy who found a vulnerability in Blockchain.Info and picked the secret phrase of Nxt genesis account found a security flaw in NRS cryptographic algorithm. The flaw allowed to replay transactions that would lead to double-triple-etc amounts sent. In fact, by finding this flaw he conducted an audit of Crypto class and won the bounty that we collected specially for such a case.

I can’t explain details of the flaw, coz it’s out of my area of expertise. U can contact him directly via nextcoin.org forum. The flaw has been fixed and all who updated to 0.6.0+ are safe now. Users of older versions are safe too as long as they are connected to nodes with 0.6.0+.

It was a bright cold day in April, and the clocks were striking thirteen.

On the 05.02.2014, a “doctorevil” found Nxt vulnerable to a transaction replay attack, and sent CfB, Jean-Luc, and OpticalC THIS. Answering to the Nxt Community’s plea for him to immediately join the dev team:

I don’t have the time to contribute consistently, although I’d be happy to be an adviser. Either way, NXT is likely to benefit from my independent “Q.A. efforts” whether I’m formally part of the team or not 🙂

Anon136’s article “Why NXT ought to be taken seriously” is found HERE.

Now, when Nxt got its own community, it’s time to get rid of the facade and reveal true properties of Transparent Mining. These properties r obvious to everyone who spent some time analyzing Transparent Mining, but still…

All Nxters should read this and comment.
The open question is: WIll the community follow BCNext’s ideas – or choose a different path?

Organize, NXTers

Yes…. We DO have an urgent need to get the decentralized initiatives and Nxt development organized!
Good initiatives and visions drown in the thread. There are examples of Nxters developing the same features, not knowing eachothers’ plans, missing the chance to work together. This newsletter is an attempt to CENTRALIZE (there, I said it ;)) important informations. Zahlen has taken another step to fulfill the need:

I’ve started a section on the wiki for organizing our projects. In particular, check out the List of Proposals and Bounties page. We could link to stuff that is “active” there: Forum threads, google docs, or other wiki pages where projects are being discussed and hashed out, and project statuses are being updated. (…) Don’t worry about messing things up, it’s a wiki, everything can be reversed. And don’t worry if you don’t know wiki formatting, just type/copy and paste. Other people can help you clean things up. If there’s demand, I’ll put up a quick guide to simple wiki editing. I’ll be technical support. Anyone has a problem, e.g. getting errors, can’t figure out how to do something, ask me and I’ll troubleshoot.

It can’t be stressed enough: Go there.
This applies to ongoing projects and new initiatives: Write your project or idea into the wiki, please.
If you want to be sure to get your update or new project mentioned in the NXT Newsletter, post HERE.

Nxt will (eventually) get listed on Cryptsy

Quote of the week

Come-from_Beyond:

Imagine Bitcoin 100 years from now. Most of income comes as transaction fees. Nxt is a time machine that brings us to that era.

Words of wisdom of the week

Rickyjames:

This thread is a crazy roller coaster ride. It strains everybody’s abilities just to hang on for the ride. We all do it because if something interesting about NXT is going to pop up, it’s probably going to pop up here first. But it takes everybody’s personal mental bandwidth just to process these posts.

That said, to gather information and defragment the thread on bitcointalk is almost a full time job.
To be sure to get your message through to the newsletter, you can contact: http://test.nxter.org/contact .
Any feedback about the newsletter is welcome too. Donations? Ok, 196910366798475802. Thanks.

Android Client

Manage accounts
Set an easy to remember tag to each account
Get details about your transactions, with period options

All transactions are encrypted in local

Alias assign/check
Show aliases registered by your account
Assign a new alias or update the uri of your alias
You can check an alias, see if it was registered by other people

Address book
You can store the destination accounts that you use frequently
Import accounts to address book from your tracsactions history

Arbitrary Messages
Send messages to others and view all messages of your account.
Encrypted Message – only the sender or recipient can decode the encrypted message.

QRCode

Real-time price ticker

Nxt News

DOWNLOAD LINK

iOS Clients

iNxt

Info:
iPhone Client (thread) (404 link removed)

iNxt is the first client for the iPhone that allows you to keep track of the value of NXT compared to BTC (Bitcoin) and also shows a candlestick graph. You can also check the balance of any account Nxt simply entering your account number and will be shown a list of transactions. As a last feature for this release, you can do the search for an alias that will show connected account and also see all the aliases linked to an account with the respective URI.

Quote from: mael on Today at 07:53:25 pmother thing: the adress who got my NXT (NXT-XVBJ-B8VA-Q7MB-HGZXQ) has received a lot of transactions the same day, same hour. What's this ?This appears to be someone run...

yes, I will do that for Ignis snapshot.I just trusted bter when they announced they will take the Ardor Snapshot.Look, this is what you can find looking on archive.org a version of bter main site on September, 18th, 2016[url=https://web.archive.org/...