Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
anything.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a CHANGELOG file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
tag of a log message
|
|
|
|
|
|
|
|
|
|
|
|
use reference to create the reference to the zblock we want to comment at, while comments will produce the zblock with our comment only.
|
|
|
|
|
|
|
|
default for when recursing a zchain. Thoughts?
|
|
|
|
- Added gpg verification option (currently works for hosted chain)
- Refactored the log output
|
|
to a seed block (default seed: IPFS hash link of an empty file)
|
|
|
|
GENESIS. We force an entry on the fly for it.
|
|
|
|
Feature:
Outputs your local's chain zblocks, with their signatures,
timestamp, gpg public key and previous zblock. Iterates the whole chain
and returns a JSON array of these entries sorted from latest to oldest.
|
|
|
|
|
|
|
|
|