A central hub where users can perform operations on their Coretime and easily access the marketplace.
The currently supported operations via the UI are:
- Region partitioning
- Region interlacing
- Region transferring
- Naming Regions
- Region task assignment
- Cross-Chain(xcRegion) transfers
Before running the webapp locally it is required to have the proper environment set up. To be able to test all of the frontend functionality you should run the full Coretime-Mock network as described here.
Before running locally the environment variables must be specified properly.
- Install NodeJs
npm i
npm run build
npm start
- Go to
http://localhost:3000
to interact with the webapp
The environment variables are automatically set in the Dockerfile; however, if you modify anything, those will need to be updated accordingly.
- Make sure to have Docker installed
- To build an image run:
docker build -t corehub .
- To run the app:
docker run -dp 3000:3000 corehub
- Go to
http://localhost:3000/
to interact with the webapp
- Build the RegionX-Node
- Follow the Getting started with zombienet steps and run
npm run zombienet
- Set up the environment by running the initialization script after the parachains started producing blocks.
- Set the environment variables to the following:
WS_KUSAMA_RELAY_CHAIN="ws://127.0.0.1:9900"
WS_KUSAMA_CORETIME_CHAIN="ws://127.0.0.1:9910"
WS_REGIONX_CHAIN="ws://127.0.0.1:9920"
EXPERIMENTAL=true
- Run
npm run dev
- Purchase a core from the bulk market
- Cross chain transfer the core from the Coretime chain to the RegionX parachain.
- Upon successful transfer the region record should be set on the RegionX parachain, and you should see the region location set to
RegionX chain
.