Continued maintenance of Trinity V1

Tens of thousands of people are already using Trinity 1.0.0 and so its continued maintenance is extremely important. The team will continue to dedicate much of their weekly work to ensure that any outstanding bug fixes, crash reports, and minor feature adjustments are resolved efficiently.

There are a handful of outstanding features that we would still like to include in V1, but we will soon be setting a feature cut-off point where all new features must be developed for V2. We would like to have a quicker turnaround time for the release of this second iteration, and so (near-to) full team attention will be required soon.

Some of the remaining new features for V1 include:

Ledger Nano X Bluetooth support: Ledger Nano X has been available for a couple of months and, although supported via USB on Trinity desktop, we are yet to add Bluetooth support. With this addition, Trinity Mobile users will also be able to secure their funds with a Ledger Nano X.

Trinity Desktop dev mode: This will make using the wallet with devnets / private tangles a more straightforward process.

Spent Address Recovery Tool: Back in the day when users were grappling with the original (pre-Trinity) IOTA wallet, there were few checks on address spend statuses when sending transactions. Unsurprisingly, many users ended up with funds on spent addresses.

With Trinity V1, it’s near impossible to end up in a situation where funds arrive on a spent address. Nonetheless, some users may send tokens using other software that does not make the same checks. Therefore, it is necessary to provide a means of rescuing tokens that have inadvertently arrived on a spent address. Until now, users have had to resort to using the CLI wallet to recover their funds. We recognize the substantial UX issues here.

This is not a simple process because once you spend from an IOTA address you reveal 50% of that address’ private key. We must make use of a process known as ‘Bundle Hash Mining’ to create a suitable bundle that reveals as minimal additional private key fragments as possible.

This is the final piece in the address reuse puzzle for Trinity V1 and we appreciate that some users have been patiently waiting for this feature.

We are working hard to provide an update on these features soon.