Start building apps on the ProximaX Sirius platform

There are 2 networks involved, namely ProximaX Sirius which is the ProximaX main network and the NEM NIS1 network.

You will be able to swap your XPX tokens once the mainnet is live and the Sirius wallet swap function is available.

You will need to download the Sirius wallet and follow the instructions here.

Save your current NIS1 private keys i.e. the keys to your current wallet that holds your XPX tokens. Funds can be lost if you fail to do so.

1. Save and store your NIS1 private keys before starting the swap process.

2. Download the Sirius wallet.

3. Create a Sirius account wallet by importing your NIS1 account private key.

4. Select “SWAP” to begin the swap process and enter the quantity of XPX to be exchanged.

5. Once the transaction is confirmed and executed, your balance will be shown in the ProximaX Sirius wallet.

Any co-signatory to a multisig account can initiate a swap. The basic steps are:

1. One of the co-signatories of the multisig account downloads the Sirius mobile wallet.

2. He creates a Sirius account wallet by importing his NIS1 account private key.

3. He selects “SWAP” to begin the swap process and enters the quantity of XPX.

4. He then selects to create a multisig transaction.

5. The system validates the multisig transactions and it is sent to the NIS1 network to be signed by the other co-signatories of the multisig account. The co-signatories must sign-off within 24 hours.

6. Once the transaction is confirmed, the swap takes place and the XPX balance is shown in the Sirius account.

It can take anything from a few minutes to several hours for the swap to take place.

ProximaX will be launching the Sirius wallet, which will come in a desktop, web, and mobile version.

While this is possible, we will not be supporting this method as it is tedious. Hence, we strongly encourage all token holders to download the Sirius wallet and perform the swap there.

Yes, you will need your NIS1 private key and you will need some XEM (nem:xem) tokens to pay for the transaction. The amount required to pay for the transaction should be less than 1 XEM.

Yes, but the native token for transaction fees will be the XPX. XEMs will no longer be required.

We encourage all XPX holders to do the swap as soon as possible.

Your XPX tokens will exist until the year 2025 or when NIS1 is deprecated, whichever is sooner.

We are not involved in migration and do not know the schedule. We will endeavour to port across from NIS1 to NIS2, however we do not know nor have any control over that migration path.

Yes, if you don’t save your private key in a safe place (hardware wallet, piece of paper, engraved in metal, etc). We are not responsible for the loss of any account. Save Your Private Keys!

The development of Catapult started at around this time. We have decided to maintain the epoch time set by the core developers in the original code. This is to reflect the development time taken until the creation of the first mainnet launch using the Catapult technology. The second block is the official start time of the Sirius mainnet.

Finally, we would like to pay tribute to the core developers for their contribution to the technology: Jaguar0625, Bloody Rookie and Gimre.

For the tech savvy: constexpr auto Epoch_Time = std::chrono::duration<int64_t, std::milli>(1459468800000);

Technically, yes or if NAS supports Docker and if the hardware requirements are met, then yes it can be done as well. Sufficient bandwidth is also an important criterion.

There will be a docker image available for each type of peer-to-peer Storage Node.

A good amount of storage and a high bandwidth are prerequisites although the actual quantum is yet to be qualified in detail. However, a decent and adequate streaming speed for a node should be 20/20 Mbps.

In terms of disk space, there is no absolute minimum but the sharing of 1MB is not logical as it will inherit (almost) no rewards.

There is no cost to run it other than the cost to run it as a node in the cloud. As R&D progresses, certain security sensitive services such as directory and node discovery services in ProximaX are expected to require minimum vested amount of XPX to eliminate certain kinds of attacks.

It is likely that a similar structure will also be established although the details are still on the drawing board. It will be announced officially on all ProximaX’s communication channels when the time comes.

It is used to finance the initial 200 nodes while development of the reward and PoX consensus scheme continues. It is expected to run as a “free” solution for users to test, develop and even go into production while the ProximaX team work on the main releases.

The side chain is part of the NEM Catapult protocol.

Yes, this is possible but hardware requirements would be higher in this situation.

• - Main https://t.me/proximaxio
• - News https://t.me/Proximaxionews
• - Developers https://t.me/proximax_devs
• - Wakanda (fun/price talk) https://t.me/proximaxofftopic

A full list of our telegram channels can be found at https://github.com/Sateetje/awesome-proximax-telegram

Please find all links here: https://proximax.io/#Support

https://blog.proximax.io/ or https://t.me/Proximaxionews