- Ixian-Core: Functionality common to all other projects.
- Ixian-DLT: Implementation of the blockchain-processing part (the Master Node software).
- Ixian-S2: Implementation of the streaming network (the S2 Node software).
- Spixi: Implementation of the Spixi messaging client for Windows, Android and iOS.
Ixian DLT is a revolutionary blockchain that brings several innovative advantages, such as processing a high volume of micro-transactions quickly while consuming a low amount of processing power, disk space and energy.
Homepage: IXIAN Project Homepage
Discord: Ixian Community
Bitcointalk: ANN Thread
The IXIAN repository is divided into four main parts:
- IxianDLT: Implementation of the blockchain-processing part.
- IxianS2: Implementation of the streaming network.
- IxianCore: Functionality common to both IxianDLT and IxianS2.
- SPIXI: Implementation of the mobile messaging client.
There are two main development branches:
- master-mainnet: This branch is used to build the binaries for the official IXIAN DLT network. It should change slowly and be quite well-tested.
- master: This is the main development branch and the source for testnet binaries. The branch might not always be kept bug-free, if an extensive new feature is being worked on. If you are simply looking to build a current testnet binary yourself, please use one of the release tags which will be associated with the master branch.
Download the latest binary release or you can compile the code yourself.
Double-click the corresponding .bat file in the IxianDLT directory to quickly start.
or
Open a terminal in the IxianDLT directory and type
IxianDLT.exe -h
to find out how to configure and run the IxianDLT node.
Download and install the latest Mono release for your Linux distribution. The default Mono versions shipped with most common distributions are outdated.
Go to the Mono official website and follow the steps for your Linux distribution. We recommend you install the mono-complete package.
Open a terminal and navigate to the IxianDLT folder, then type
mono IxianDLT.exe -h
to find out how to configure and run the IxianDLT node.
Visual Studio 2017 is required (Community Edition is fine), you can get it from here: Visual Studio
Several NuGetPackages are downloaded automatically during the build process.
Download and install the latest Mono release for your Linux distribution. The default Mono versions shipped with most common distributions are outdated.
Go to the Mono official website and follow the steps for your Linux distribution.
We recommend you install the mono-complete package.
For Debian based distributions such as Ubuntu, type
sudo apt install mono-complete nuget msbuild git gcc
or if you have a Redhat based distribution, type
sudo yum install mono-complete nuget msbuild git gcc
Next you'll need to build the Ixian solution. You can do this by typing the following commands in the terminal:
git clone -b master-mainnet https://github.com/ProjectIxian/Ixian-source.git
cd Ixian-source/IxianDLT
nuget restore DLTNode.sln
msbuild DLTNode.sln /p:Configuration=Release
The IxianDLT will be compiled and placed in the bin/Release/ folder.
For the IxianDLT node to work correctly, you'll need to copy the libargon2.so shared library in the bin/Release/ folder. You can use the library provided in the latest Ixian Binary release.
If you want to build the libargon2 shared library yourself, you can do this by typing the following commands in the terminal:
git clone https://github.com/P-H-C/phc-winner-argon2.git
cd phc-winner-argon2
make
Copy the resulting libargon2.so file to the IxianDLT bin/Release/ folder.
The DLT project expects an argon2 shared library in the run path. You can build one using this project: Argon2 Reference implementation
If you feel like you can contribute to the project, or have questions or comments, you can get in touch with the team through Discord: (https://discord.gg/dbg9WtR)
If you would like to send an improvement or bugfix to this repository, but without permanently joining the team, follow these approximate steps:
- Fork this repository
- Create a branch (preferably with a name that describes the change)
- Create commits (the commit messages should contain some information on what and why was changed)
- Create a pull request to this repository for review and inclusion.