This guide has been created to assist with the impending token swap from CPX (NEP5) to PHX (NEP5). All NEP5 addresses holding CPX will receive 2.5 PHX for each 1 CPX held.

• View full details on the swap here!
• Important: You should withdraw your CPX from all exchanges immediately. CPX can be stored on any wallet that supports Neo and Nep5 tokens such as O3 wallet and Neon wallet. More details below.

Important dates

• Monday, Nov 2: Apex/Phoenix teams will mint new PHX/PHB tokens to support the new merged supply
• Friday, Nov 6th (estimated), at NEO block height 6,422,886: Snapshot will be taken of all NEO wallet balances holding CPX…

Dear Red Pulse Phoenix and APEX Network Community,

Many thanks for your patience over the last two weeks. We are excited to announce the logistics of the merger of the Red Pulse Phoenix and APEX Network token economies, infrastructure, project teams, and community. For background, please see previous announcements:

• Red Pulse Phoenix Merger Announcement
• APEX Network Merger Announcement

CPX:PHX swap ratio and conversion to PHB

Per the announcements, current CPX token holders will be airdropped 2.5 PHX for every 1 CPX that they hold. This PHX (NEP-5 token on NEO blockchain) can either be held in its current state, or can be converted to PHB (BEP-2 on Binance blockchain) by depositing the PHX into their Binance.com wallet. …

Development status report — #8

Dear community members,

Below you will find an overview of development tasks performed over the last three weeks

Week 40 — tasks completed

This week’s focus topics were a continuation of the work from week 39 — Ledger and Federated learning

• We continued making headway with the technical work regarding Ledger implementation
• Continued work on the oracle scheme
• Further federated learning opcode optimizations

Week 41 — national holiday

Week 42 — tasks competed

This week our focus topics were our oracle protocol and the technical aspect of our partnership with Red Pulse

• Completed further frontend work for the Desktop Client
• Finished the cooperation solidity contract between APEX and Red Pulse
• Chainlink, Tellor, DOS, Band and NEST were selected to converge into the aggregated oracle…

Dear APEX Network community and partners,

After months of meticulous planning and discussion, APEX Network and Red Pulse Phoenix have made a calculated decision to take our projects, platforms, and ecosystems to the next stage through a merger that will create a comprehensive enterprise data blockchain platform. The merger will create a larger, more powerful infrastructure and ecosystem, effectively leveraging the best resources both projects have to offer (technology, platforms, token economies, token liquidity, human talent, community, and marketing).

The combined entity will become Phoenix Global, and CPX token holders will be granted PHB (BEP-2) tokens at a ratio calculated based on moving average price, with details on the swap forthcoming.

This will accomplish what very few projects have done successfully — achieve synergies via a combined greater user base, market cap, and real-world applications, catalyzing growth and expanding the ecosystem. …

Development status report — #7

Below you will find an overview of development tasks performed over the last two weeks:

Week 38 — tasks completed

• Reviewed desktop wallet source code and design documents to facilitate integration with ledger app.
• Created specifications for numerical precision model — enhancements to instructions for handling of calculations, rounding, and comparisons.
• Implemented event listening and optimised bandwidth for communication via blockchain since APEX Federated Learning can only be conducted through blockchain.

Week 39 — tasks competed

• Completed approximately 70% of the work on Ledger wallet integration.
• Defined and documented the APEX blockchain scheme for handing oracles.
• Optimized code for AFL contract creation using the create2 opcode (instead of the web3 library). …

The CPX buyback program (Phase 1) has just commenced as of August 30, 2020 — we have not released much details as the plan and strategy is still in the process of optimization and refinement. However, we now feel that we are able to share more concrete plans for the buyback.

Buyback channels

• Exchanges [Primary, will be used for the long term]
• Private sale investors (OTC) [Secondary, will be used initially for batch trades]

Structure

APEX Network Core Development

• Team Buyback

A good portion of the buyback allocation will go to the team for long-term incentives, options, and/or investment. This portion includes Jimmy’s own CPX buyback allocation, currently planned to be around 50% of the team portion. …

Development status report — #6

Weeks 36–37 have brought us yet another step further towards release — we invite you to have a look at the latest tasks that have been completed:

Week 36 — tasks completed

• Migrated parts of the front end code from the web wallet to adapt to the Ledger wallet integration
• Smart contracts: Optimized the code of the Apex Federated Learning smart contract to reduce gas consumption
• Optimized the AFL message standard to reduce gas consumption; the witness hash will be uploaded to the blockchain instead of the encrypted tree data structure

Week 37 — tasks completed

• Adjusted the UI of the wallet to adapt to the Ledger wallet integration
• Referenced the protocols used by MetaMask and WalletConnect to make the Ledger HW wallet easy to use with our client. …

Development status report — #5

Another two weeks have passed, and we are happy to share the latest aspects of our blockchain related progress:

Week 34 — tasks completed

• We have constructed the APEX Federated Learning register module using Vyber (contract language like Python). This register module is used with AFL’s to aid the data requestor in searching for relevant data providers and verifying their identity
• Implemented the encryption module of the APEX Desktop Client
• We also refactored the interaction logic of the light node mode and MongoDB to increase fault tolerance, increasing stability and sustained performance.

Week 35 — tasks completed

• This week we continued with the refactoring of the communication between the light node and the MongoDB module to further perfect its…