Skip to content

MinterTeam/minter-go-node

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 
Β 

Repository files navigation

Version Go version License Last commit Go Report Card Github Actions Report Card Docker Pulls

Minter is a global rewards and loyalty points network powered by a fast blockchain. Any brand, community, or blogger can create their own coins and launch their reward or loyalty system in minutes.

NOTE: This is alpha software. Please contact us if you intend to run it in production.

Installation

Docker

  1. Grab latest docker-compose, save docker-compose.yml and run docker-compose up -d. To run it in production we recommend to use bind host mount instead of volume.

  2. To build from source clone this repo, make your changes and run docker-compose up --build -d

Manual

You can get official installation instructions in our docs.

  1. Download Minter Node

    Get latest binary build suitable for your architecture and unpack it to desired folder.

  2. Run Minter Node

./minter node

Resources

Related repositories

Community

Versioning

SemVer

Minter uses SemVer to determine when and how the version changes. According to SemVer, anything in the public API can change at any time before version 1.0.0

To provide some stability to Minter users in these 0.X.X days, the MINOR version is used to signal breaking changes across a subset of the total public API. This subset includes all interfaces exposed to other processes, but does not include the in-process Go APIs.

Upgrades

In an effort to avoid accumulating technical debt prior to 1.0.0, we do not guarantee that breaking changes (ie. bumps in the MINOR version) will work with existing blockchain. In these cases you will have to start a new blockchain, or write something custom to get the old data into the new chain.

However, any bump in the PATCH version should be compatible with existing histories (if not please open an issue).