MassGrid-Core (MGD) v1.3.3.1

MassGrid Integration/Staging Tree

https://www.massgrid.com

What is MassGrid

Coin Suffix: MGD
PoW Algorithm: JumpHash
PoW Median Target Spacing: 300 Seconds
PoW Difficulty Retarget: 288 Blocks
Full Confirmation: 6 Blocks
Total Coins: 168,000,000 MGD
Block Size: 1 Mega-bytes (MB)

The goal of MassGrid is to become the world's largest distributed GPU high-performance cloud computing network. MassGrid intends to transform the meaningless POW hash computing to general parallel computing that could be used for practical purpose through our improved POW algorithm and redesigned blockchain network architecture.

MainNet Parameters P2P Port = 9443 RPC Port = 9442

TestNet Parameters P2P Port = 19443 RPC Port = 19442

UNIX BUILD NOTES

Some notes on how to build MassGrid in Unix.

Note

Always use absolute paths to configure and compile MassGrid and the dependencies, for example, when specifying the the path of the dependency:

../dist/configure --enable-cxx --disable-shared --with-pic --prefix=$BDB_PREFIX

Here BDB_PREFIX must absolute path - it is defined using $(pwd) which ensures the usage of the absolute path.

To Build

cd MassGrid
./autogen.sh
./configure
make
make install # optional

This will build MassGrid-Qt as well if the dependencies are met.

Dependencies

These dependencies are required:

Library	Purpose	Description
libssl	SSL Support	Secure communications
libboost	Boost	C++ Library

Optional dependencies:

Library	Purpose	Description
libdb4.8	Berkeley DB	Wallet storage (only needed when wallet enabled)
qt	GUI	GUI toolkit (only needed when GUI enabled)
protobuf	Payments in GUI	Data interchange format used for payment protocol (only needed when GUI enabled)
libqrencode	QR codes in GUI	Optional for generating QR codes (only needed when GUI enabled)

System requirements

C++ compilers are memory-hungry. It is recommended to have at least 1 GB of memory available when compiling MassGrid. With 512MB of memory or less compilation will take much longer due to swap thrashing.

Dependency Build Instructions: Ubuntu & Debian

Build requirements:

sudo apt-get install git build-essential libtool autotools-dev autoconf pkg-config libssl-dev libcrypto++-dev libevent-dev libminiupnpc-dev libgmp-dev

for Ubuntu 12.04 and later or Debian 7 and later libboost-all-dev has to be installed:

sudo apt-get install libboost-all-dev

db4.8 packages are available here. You can add the repository using the following command:

    sudo add-apt-repository ppa:bitcoin/bitcoin
    sudo apt-get update

Ubuntu 12.04 and later have packages for libdb5.1-dev and libdb5.1++-dev, but using these will break binary wallet compatibility, and is not recommended.

for Debian 7 (Wheezy) and later: The oldstable repository contains db4.8 packages. Add the following line to /etc/apt/sources.list, replacing [mirror] with any official debian mirror.

deb http://[mirror]/debian/ oldstable main

To enable the change run

sudo apt-get update

for other Debian & Ubuntu (with ppa):

sudo apt-get install libdb4.8-dev libdb4.8++-dev

Dependencies for the GUI: Ubuntu & Debian

If you want to build MassGrid-Qt, make sure that the required packages for Qt development are installed. Qt 5 is necessary to build the GUI. If both Qt 4 and Qt 5 are installed, Qt 5 will be used. Pass --with-gui=qt5 to configure to choose Qt5. To build without GUI pass --without-gui.

For Qt 5 you need the following:

sudo apt-get install libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools libprotobuf-dev protobuf-compiler libcrypto++-dev

libqrencode (optional) can be installed with:

sudo apt-get install libqrencode-dev

Once these are installed, they will be found by configure and a MassGrid-Qt executable will be built by default.

Notes

The release is built with GCC and then "strip MassGridd" to strip the debug symbols, which reduces the executable size by about 90%.

Berkeley DB

It is recommended to use Berkeley DB 4.8. If you have to build it yourself:

SILK_ROOT=$(pwd)

# Pick some path to install BDB to, here we create a directory within the silk directory
BDB_PREFIX="${SILK_ROOT}/db4"
mkdir -p $BDB_PREFIX

# Fetch the source and verify that it is not tampered with
wget 'http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz'
echo '12edc0df75bf9abd7f82f821795bcee50f42cb2e5f76a6a281b85732798364ef  db-4.8.30.NC.tar.gz' | sha256sum -c
# -> db-4.8.30.NC.tar.gz: OK
tar -xzvf db-4.8.30.NC.tar.gz

# Build the library and install to our prefix
cd db-4.8.30.NC/build_unix/
#  Note: Do a static build so that it can be embedded into the exectuable, instead of having to find a .so at runtime
../dist/configure --prefix=/usr/local --enable-cxx
make
sudo make install

Note: You only need Berkeley DB if the wallet is enabled (see the section Disable-Wallet mode below).

Boost

If you need to build Boost yourself:

wget https://dl.bintray.com/boostorg/release/1.66.0/source/boost_1_66_0.tar.gz

tar -xvf boost*.tar.gz

sudo chmod a+x bootstrap.sh

sudo ./bootstrap.sh

sudo ./bjam install

Security

To help make your MassGrid installation more secure by making certain attacks impossible to exploit even if a vulnerability is found, binaries are hardened by default.

Hardening enables the following features:

Position Independent Executable Build position independent code to take advantage of Address Space Layout Randomization offered by some kernels. An attacker who is able to cause execution of code at an arbitrary memory location is thwarted if he doesn't know where anything useful is located. The stack and heap are randomly located by default but this allows the code section to be randomly located as well.

On an Amd64 processor where a library was not compiled with -fPIC, this will cause an error such as: "relocation R_X86_64_32 against `......' can not be used when making a shared object;"

To test that you have built PIE executable, install scanelf, part of paxutils, and use:
```
  scanelf -e ./MassGridd
```
The output should contain: TYPE ET_DYN
Non-executable Stack If the stack is executable then trivial stack based buffer overflow exploits are possible if vulnerable buffers are found. By default, silk should be built with a non-executable stack but if one of the libraries it uses asks for an executable stack or someone makes a mistake and uses a compiler extension which requires an executable stack, it will silently build an executable without the non-executable stack protection.

To verify that the stack is non-executable after compiling use: scanelf -e ./MassGridd

the output should contain: STK/REL/PTL RW- R-- RW-

The STK RW- means that the stack is readable and writeable but not executable.

Example Build Command

Qt Wallet and Deamon, CLI version build:

qmake && make && cd src && make -f src/makefile.unix

Deamon Only Build:

cd src && make -f src/makefile.unix

JiaTaoXie/MassGrid