NEM Foundation Support Update - Technology and Product

NEM Foundation Support Update
Technology and Products

Translations

Japanese: Here.
Russian: Here.
Chinese: Here.
Italian: Here.
Spanish: Here.

TL;DR - New year, new brand, new ways to connect. Get direct help in NEM2 Slack, and follow along with release updates. New test network and existing test network will run in parallel. Symbol branding being implemented. TREZOR will not be available until after XYM launch due to new TREZOR listing criteria. Final testing happening now on opt-in data processing practice runs.

Communications & Support Update

As we are getting into the home stretch of testing before the public network launch, we are updating how tech and product are communicating with and supporting our community.

Communications: We will post regular updates as we move through release cycles and these final phases to the public network launch.

Support (Where To Go To Get Tech and Product Questions Answered.)

  • NEM development Slack group

The latest invite link is always available at the bottom of the developer center site: https://nemtech.github.io.

The most popular Slack channels for help relating to testnet and general testing are:

  • #help
  • #sig-testing

Latest Update: Symbol Testnet

  • With the latest release it was required to generate a new nemesis block. Instead of restarting the existing network, we typically start a new network alongside the existing one (this approach allows for minimal to no impact for all the various internal and external developers and partners who are leveraging the network)

  • New network was launched on Wednesday 1/22 and after verification of the network behaving as expected a new public release was made of the code for version 0.9.2.1 (https://github.com/nemtech/catapult-server/tree/v0.9.2.1).

    • This marks the first test network launched with the new ticker “symbol.xym” which was recently chosen after the finalized community vote.
    • All future test networks and eventual main net launch will use the new ticker and related branding (more on that below).
  • The previous network that has been running for a couple of months will continue to run for another few weeks, we will then begin to shut down the base services for it. This will give everyone ample time to move their testing and efforts over to the new network when it is convenient. While having ample time you should begin to migrate your testing efforts now.

  • There are currently at least two more known sets of updates and fixes coming to the core server code base, some of which will require a reset/restart of the network, and some that do not. Over the next couple of weeks the core development team will be prepping these updates while finishing off some scoping and estimates for implementation and testing timing. As we progress on development more updates will be provided on scheduling of any future test network updates and resets.

Moving to the Symbol.xym Network

  • Moving your existing development and testing efforts from the old network to the new symbol.xym network is relatively easy depending on how you have been engaging with the network.

If you have created any accounts, wallets, etc, note that they will not exist on the new network. Any balances, mosaics, namespaces, etc that were created on the previous network will have to be recreated on the new one if they are part of your ongoing testing and development.

NOTE: this update was built with the same parameters as the previous so if you have any network parameters such as currency mosaic IDs or network generation hash values hard wired in your testing, your connection should still work without changes

  • As noted above, should you not want to disrupt your current dev/testing efforts feel free to slowly migrate your setup over the next couple of weeks, we will announce as we start shutting down previous version services.

  • If you are/were running a test network node you will need to use the latest version which behaves in the same manner but has been prepared with the new nemesis created for the network and a couple config updates. You can find it here.

  • Links and details also updated in the latest documentation release here.

NOTE: If you were before, or are planning to run permanent testnet nodes and harvesters feel free to drop notes on the #sig-testing channel and team members can send, or re-send, larger amounts of symbol.xym to increase harvesting odds.

  • For those that have been using and testing the desktop wallet, we have setup a new temporary repository for the movement to the new network:
  • If you previously were using the wallet you can delete the previous installations as this new one will point automatically to the new network.

Server Support For Older x86 Architectures

  • Currently the builds and releases of the core server is focused on x86 architectures that are not very old.

  • We have received messages from various testers via the #help channel that have experienced errors trying to launch nodes on hardware that is much older. We are aware and will be putting some efforts into test builds to target older x86 arch’s and will update when there are builds/releases available for testing.

NIS1 Opt-in Updates

Lots of questions are being asked about the status of opt-in preparation and readiness.

  • The team is in the final testing stretch to simulate and verify the opt-in data processing side of things. This covers the process that will occur after the opt-in snapshot height is reached and the tools being built will read and verify the NIS1 opt-in data and generate the output that will be fed into the nemesis creation for the new Symbol network. Once this final testing phase is completed we will be ready to package and release the first parts of the opt-in tool.

  • The first phase of opt-in tool release is in the form of the NEM Wallet (also called nanowallet). Users that use the NEM Wallet will be able to download a new release and perform the opti-in procedure.

  • The library that powers the NEM Wallet plugin will also be made available for any 3rd parties or people interested in programmatically performing opt-in via their own custom process(es) or client(s).

  • We are also looking into packaging the library into a focused stand-alone mobile application for those that do not have access to a computer that can run NEM Wallet. More updates on this to come, this will be released some time AFTER the NEM Wallet plugin/release.

Symbol Hardware Wallet Support

Work has been progressing on hardware wallet support, with initial focus on TREZOR and ledger support.

  • TREZOR work has been completed to the point of being in the final ready state for packaging and submission to review. We have recently learned that TREZOR now has updated criteria for welcoming new tokens to their hardware (which is problematic with launching a new network/token.)
  1. Must be a “top 30” token.
  2. Must leverage new implementation technique for better support between old/new TREZOR hardware.
  3. Pass basic review of a pull request for their firmware.

This means we will be pushing to finalize the approval process with them after the XYM token launch when it settles into its place in the markets.

  • Ledger support is still under development, we will have more updates in February for the state of it and their related update/listing criteria as we move things along.

  • Some of the NEM team is looking into other backups for hardware wallet support beyond TREZOR/Ledger, as they progress research and conversations the tech and product team will take that input and engage where needed.

Symbol Branding and Product Updates

  • As many of you in the community have already seen, the project is creating a new brand for the launch of the version 2 network and related products/services.

  • The final piece was settled recently with the completed vote for the ticker for the public network token. The branding agency and NEM marketing team are now working to create and finalize all the necessary design and branding assets needed for the launch. This includes design assets that will be leveraged in the various products and services that we have today and new ones that will be worked on in the future.

  • In the coming weeks you will start to notice a range of minor then major updates for reflecting the new branding. This will include the block explorer, desktop wallet, the cli tool, developer/documentation site and several other areas in the project.

We encourage everyone to set up a node and try testnet, let’s grow together! Guide here.

Sincerely,

The NEM development team

15 Likes

Very nice.

1 Like

I cannot stress this enough: These are the type of updates we want! Please do this more frequently.

I have been asking multiple times about when the test network would be reset or the update would be implemented. And with this post you are mentioning that the new update has been running parallel for over a week? Is it so hard to just make a statement at the correct time about what is happening???

3 Likes

From what i’ve read it sounds like the code is ready but will not be in official firmware for the launch of symbol.

If my assumption is right, is there a way to release a custom Trezor firmware to give NEM/Trezor users an option? From a security point of view it is bad to move coins just for a snapshot, it also means that node operators with Trezor have to redo their node config.

6 Likes

I want more specific progress on mobile wallet. I don’t think there is any decent information since the roadmap was announced last May.

2 Likes

Apologies for the delay Trend, we’re working on getting you an accurate update.

4 Likes

is there anyone who could answer? thanks

1 Like

Related: This is open source, right? Any fork/repo/branch/PR of/in the Trezor firmware monorepo to play with?

anyone? :laughing: :grinning:

1 Like

:cricket: Cri cri cri… silent…

1 Like

There should be a tech update in the next day or so. It will include mobile progress. Thanks for patience.

2 Likes

That is quite a risky thing to do if you want my honest opinion:

  1. Firmware will not be signed with correct keys and therefor there is good chance Trezor hardware wouldn’t even recognize it (rendering work useless if that happens.)

  2. People that own hardware wallet, own them for security measures. Using a tweaked/modified firmware for your hardware wallet is something i will always discourage. After all, you are using a hardware wallet because you really want to own the sensitive information it holds.

That be said, I would still be looking into publishing a forked firmware but cannot guarantee that this is really feasible. Other questions that pops up is: If we do fork off their firmware, will that affect their decision about our integration?

1 Like

Thanks for answering.

I cant disagree and i know the security concerns around it. When we talk about security we have to consider that it was the reason for most to go with a Trezor in first place because it makes security easy.

The fact that the release of the software seems to be somehow tied to our position on a market cap site is just not acceptable for me. I dont even want to talk about if/when symbol reach top 30, which it has to do in order for Trezor to be considered for the official firmware. Simply, it is not in our control anymore to support existing official wallet integrations and this is really a bad thing.

I thought about the most secure way for a Trezor user to move on and at the moment what seems the best way is to create 3 cosigner accounts offline and setup multisig, then move XEM from Trezor to new account for opt-in and claiming of XYM later. This way the only risk seems to be if 2 of 3 offline created accounts get compromised which is highly unlikely.

What is your take on this “migration path” for a Trezor user?

I dont know if everyone is able to do that in a secure environment in time for snapshot and thus a custom firmware could be the easier way for some users. Anyway, i think we should have a Trezor migration guide available to address concerns of Trezor users.

2 Likes

“Server Support For Older x86 Architectures”

Look forward to this progress

2 Likes

Expansion of “node” depends on this

1 Like