Skip to content
master
Switch branches/tags
Go to file
Code

Latest commit

 

Git stats

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
 
 
 
 
doc
 
 
 
 
src
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

README.md

  /$$$$$$  /$$$$$$$  /$$$$$$ /$$      /$$
 /$$__  $$| $$__  $$|_  $$_/| $$$    /$$$
| $$  \__/| $$  \ $$  | $$  | $$$$  /$$$$
| $$ /$$$$| $$$$$$$/  | $$  | $$ $$/$$ $$    GRIM 2018
| $$|_  $$| $$__  $$  | $$  | $$  $$$| $$
| $$  \ $$| $$  \ $$  | $$  | $$\  $ | $$
|  $$$$$$/| $$  | $$ /$$$$$$| $$ \/  | $$
 \______/ |__/  |__/|______/|__/     |__/

GRIMcoin - POW/POS

  • Algorithm: Scrypt
  • Latest Version: 1.2.1

Technical Specifications:

  • Type: PoW/PoS
  • Coin name: Grimcoin
  • Coin abbreviation: GRIM
  • Address letter: G
  • RPC port: 24862
  • P2P port: 24861
  • Block reward: 500 GRIM

Coin Info:

  • Total coin supply: 233,333,333 GRIM
  • Premine percent: 10 %
  • Premine amount: 23,333,333 GRIM
  • PoS percentage: v1.2 Updated to 525% Per Year (from 100%)
  • Last PoW block: 5000
  • Coinbase maturity: 6 blocks
  • Target spacing: 64 seconds
  • Target time span: 1 block
  • Transaction confirmations: 4 blocks

Community:

Exchanges (More Coming):

Wallets:

Wallet Downloads: https://github.com/GrimReaperCoins/GRIM/releases

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are regularly created to indicate new stable release versions of Grim.

Feature branches are created when there are major new features being worked on by several people.

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.