This network and research framework is being developed for the purpose of student researchers, interested in developing blockchain solutions. We provide an alternate blockchain network option to expirement with, without the burden of high learning curves associated with softwares such as HyperLedger, Ethereum, etc.
This software is not a public network costing gas fees to expirement with, nor is its implementation complex. With this, researchers or other curious people are invited expirement with and fork our software to meet their use case.
We provide:
- Easy configurability
- An understanable code base
- A Framework for multiple use cases, such as defi or healthcare
This software heavily uses the following concepts in order to achieve a fully distributed, decentralized blockchain network:
- Servent (Server + Client)
- Java Sockets + TCP/IP
- Multi-threading
- Distributed Systems
- Decentralization
- Quorum Consensus
BlueChain is not production-grade software, and should not be externally hosted unless proper security has been implemented first.
- Lack of certain securities
- Few fail-safe mechanisms
- Brand-New
- Short-Lived Network
- Java 11
- Maven
- Navigate to the config.properties file (network/src/main/java/config.properties)
- Configure the network to the specifications you desire.
- Warning: The number of nodes your local machine can handle depends on the computing resources that the machine has.
- Use the startNetwork shell script (navigate back to network/)
./startNetwork.sh
- Launch the client associated with the use case defined in the config file
- For the Defi use case for example, run
./startDefiWallet.sh
For steps 1 and 2, please refer to the 'Running a Local Netork' section's steps 1 and 2
- Use Maven to compile the NetworkLauncher (navigate back to network/)
mvn clean install
- Running the NetworkLauncher
-
For this step, since we plan to run our network across multiple hosts, please ensure that the networking and firewall permissions / setting allow TCP/IP connections from the ports and hosts you will specify
-
Using the NetworkLauncher java program in this context works by running the program on each host you plan on using.
-
Every node on each host is required to submit it's public key to the Node Registry, a directory intended to be shared across hosts. This allows each node in the network to properly use DSA with one another in addition to local peer discovery.
-
It is suggested to specify a '-t for each program in order for the networks to bind but wait to connect until you have every host setup
-
An example for our first host to run
java -cp target/network-1.0-SNAPSHOT.jar NetworkLauncher -t 60000