0xGabi

{
  "merkleRoot": "0x47c52ef48ec180964d648c3783e0b02202f16211392b986fbe2627f021657f2b",
  "tokenTotal": "0xbdbc41e0348b300000",
  "claims": {
    "0x3C44CdDdB6a900fa2b585dd299e03d12FA4293BC": {
      "index": 0,
      "amount": "0x3635c9adc5dea00000",
      "proof": [
        "0x11079118024000df209172a1af6eb7a9ea4e5b2bd6e2760481566ce6bee3e0cd",
        "0xf46478da86f39b5d4f0af753bbc54ab402404b5ed5369f359e8fb24268b12edc"

brianclements

Commit Message Format

This specification is inspired by and supersedes the [AngularJS commit message format][commit-message-format].

We have very precise rules over how our Git commit messages must be formatted. This format leads to easier to read commit history.

Each commit message consists of a header, a body, and a footer.

guilherme

#!/bin/sh
# Redirect output to stderr.
exec 1>&2
# enable user input
exec < /dev/tty

consoleregexp='console.log'
# CHECK
if test $(git diff --cached | grep $consoleregexp | wc -l) != 0
then