Through joining Metal blockchain as a subnet, XPR Network can increase transaction speed, settlement finality, and a connection to the numerous subnets that are launching from various communities and institutions.

In support of this objective, Object Computing Inc (OCI) performed research (herein called

Phase 0) to prototype a C++ version of an existing Go virtual machine under Avalanche as part.

OCI also produced an architectural design for a virtual machine (VM) capable of:

● Leap block production with Antelope protocol compatible blocks

● Leap transaction execution and validation

● Leap HTTP API access, both read and write

● Gossiping transactions across an Avalanche subnet

● Utilizing the Snowman consensus engine that the Metal Blockchain uses to achieve

finality consensus

● Launching from a genesis based on existing XPR state

Additionally, OCI explored two options for the move of XPR to the Metal Blockchain: a cutover

with minimal user downtime, and a cutover with no user downtime. Cutover tasks will be

considered for a future phase of work.

Phase 1 Overview

Goals

This proposal builds upon the results of Phase 0. The goal for the conclusion of this project

(Phase 1) is for OCI to provide code to enable the move of the XPR Network onto the Metal

Blockchain in a testnet.

Tasks

To enable the move of the XPR Network into the Metal Blockchain, OCI will perform the

following tasks under this proposal:

1. Determine the submodule or fork of Leap

2. Stand up a testnet that demonstrates Avalanche/Leap

3. Submit transactions

4. Gossip transactions

5. Block sync in a new node

6. Set-up equivalent Avalanche gRPC endpoints to passthrough to Leap HTTP endpoints

7. Develop/port appropriate Leap integration tests to work against Leap VM

8. Stand up a new testnet with an XPR snapshot

9. Implement items noted in the Security section of this document

10. Minimal technical documentation

Security Tasks

As an ISO/IEC 27001:2022 certified organization, OCI practices ‘security by design’ in each

project we deliver. OCI security responsibilities in this project are expected to include:

1. Ensuring the OCI team follows practices and policies that Metallicus has in place

2. Attending meetings

3. Performing targeted code reviews

4. Evaluation and discussion of security implications of engineering decisions

5. Other tasks as directed by Metallicus

Project Team and Estimates

OCI will provide an expert Agile software development team to engage on a

time-and-materials basis. Our team will include a dedicated principal software engineer, as well

as additional contributions from key experts that hold the following positions at OCI:

● Principal Software Engineer

● Senior Technical Architect

● Senior Security Engineer

● Senior Delivery Consultant

Throughout this engagement, OCI will be regularly collaborating with the core developer of XPR Network, Metallicus, on a suggested cadence of every 2 weeks to review progress and, where relevant, demonstrate work completed. As we reach different stages of the work, we will optimize the composition of our team, if needed, to ensure that we are utilizing the expertise and talent required.

As noted previously, there are multiple items still open for consideration or excluded from the

project (e.g. how a minimal downtime cutover should be performed, if OCI will assist with the

verification of the staking/voting mechanism in Avalanche/Leap, etc.). These open items could

alter the estimates provided below if OCI were asked to perform additional tasks not already

identified. OCI is ready and happy to contribute to these open items.

Testnet Deployment Estimate

OCI anticipates the effort to complete the General Tasks and Security Tasks as outlined above

to be delivered over approximately 14-15 weeks.

Conclusion

OCI is excited about the opportunity to help meet XPR Network’s needs with this project and sees tremendous value by running XPR and Metal on a single network. Through increasing transaction speed, settlement times, and integrating a more efficient consensus mechanism we can expect to see a considerable performance increase of XPR Network and interoperability on a modular blockchain.

Q/A

Will my tokens, NFTs and other digital assets on the dPoS network migrate fluidly to the new network on Metal blockchain?

Yes - all assets will be carried over during the cut off, so if you hold XYZ assets on the dPoS network, this will appear in your wallet on the new network, the same holds true for all smart contracts.

If I’m staking XPR or any other asset, will that carry over during the migration process?

Yes - any staked assets will remain in the contract and mirror on the new network.

As a developer, will I have to change anything to migrate my dApp?

Yes - you will need to change end-points, and some minor front-end changes. Make sure to join the XPR dev community on Telegram if you have any questions (https://t.me/protondev)

As a developer, will I have to change anything to migrate my dApp?

Yes - you will need to change end-points, and some minor front-end changes. Make sure to join the XPR dev community on Telegram if you have any questions (https://t.me/protondev)

As a block producer, does anything change in terms of my existing votes or rewards?

No - everything with the existing consensus around 15/21 BPs and having 21 active BPs stays the same, all of your votes will transfer over during the migration. The only change is that it becomes much easier to become a Block Producer, similar to being a Metal validator, the technical requirements are much simpler, allowing virtually anyone to become a BP.