You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Ismail Khoffi 6a80412a01 Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
.circleci circleci: update go version (#3051) 6 years ago
.github remove JB from codeowners file (#2174) 6 years ago
DOCKER move abci Dockerfile (still needs to be updated tho) 7 years ago
abci fix docs / proxy app (#2988) 6 years ago
benchmarks Set protocol versions in NodeInfo from state (#2686) 6 years ago
blockchain Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
cmd Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
config R4R: Split immutable and mutable parts of priv_validator.json (#2870) 6 years ago
consensus Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
crypto crypto: revert to mainline Go crypto lib (#3027) 6 years ago
docs docs: add rpc link to docs navbar and re-org sidebar (#3041) 6 years ago
evidence rename Accum -> ProposerPriority: (#2932) 6 years ago
libs Make testing logger that doesn't write to stdout (#2997) 6 years ago
lite Set accum of freshly added validator -(total voting power) (#2785) 6 years ago
mempool mempool: move tx to back, not front (#3036) 6 years ago
networks Docs cleanup (#2522) 6 years ago
node Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
p2p Update node_info.go (#3059) 6 years ago
privval Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
proxy fix docs / proxy app (#2988) 6 years ago
rpc R4R: Split immutable and mutable parts of priv_validator.json (#2870) 6 years ago
scripts R4R: Split immutable and mutable parts of priv_validator.json (#2870) 6 years ago
state don't ignore key when executing CONTAINS (#2924) 6 years ago
test validate reactor messages (#2711) 6 years ago
tools remove unnecessary "crypto" import alias (#2940) 6 years ago
types Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
version changelog and version 6 years ago
.editorconfig merge 2 rules in .editorconfig 7 years ago
.gitignore docs: Add assets/instructions for local docs build (#2453) 6 years ago
CHANGELOG.md changelog and version 6 years ago
CHANGELOG_PENDING.md Remove privval.GetAddress(), memoize pubkey (#2948) 6 years ago
CODE_OF_CONDUCT.md update some top-level markdown files (#2841) 6 years ago
CONTRIBUTING.md Bucky/v0.26.3 (#2872) 6 years ago
Gopkg.lock crypto: revert to mainline Go crypto lib (#3027) 6 years ago
Gopkg.toml crypto: revert to mainline Go crypto lib (#3027) 6 years ago
LICENSE GPLv3 -> Apache2.0 9 years ago
Makefile docs: networks/docker-compose: small fixes (#3017) 6 years ago
README.md update go version & other cleanup (#3018) 6 years ago
ROADMAP.md version bump. add roadmap back. minor fixes 7 years ago
SECURITY.md update some top-level markdown files (#2841) 6 years ago
UPGRADING.md update changelog and upgrading (#2974) 6 years ago
Vagrantfile small fixes to spec & http_server & Vagrantfile (#2859) 6 years ago
appveyor.yml appveyor: use make 7 years ago
codecov.yml Remove pb.go files from codecov 7 years ago
docker-compose.yml Switch ports 466xx to 266xx (#1735) 7 years ago

README.md

Tendermint

Byzantine-Fault Tolerant State Machine Replication. Or Blockchain for short.

version API Reference Go version riot.im license

Branch Tests Coverage
master CircleCI codecov
develop CircleCI codecov

Tendermint Core is Byzantine Fault Tolerant (BFT) middleware that takes a state transition machine - written in any programming language - and securely replicates it on many machines.

For protocol details, see the specification.

For detailed analysis of the consensus protocol, including safety and liveness proofs, see our recent paper, "The latest gossip on BFT consensus".

A Note on Production Readiness

While Tendermint is being used in production in private, permissioned environments, we are still working actively to harden and audit it in preparation for use in public blockchains, such as the Cosmos Network. We are also still making breaking changes to the protocol and the APIs. Thus, we tag the releases as alpha software.

In any case, if you intend to run Tendermint in production, please contact us and join the chat.

Security

To report a security vulnerability, see our bug bounty program

For examples of the kinds of bugs we're looking for, see SECURITY.md

Minimum requirements

Requirement Notes
Go version Go1.11.4 or higher

Documentation

Complete documentation can be found on the website.

Install

See the install instructions

Quick Start

Resources

Tendermint Core

For details about the blockchain data structures and the p2p protocols, see the the Tendermint specification.

For details on using the software, see the documentation which is also hosted at: https://tendermint.com/docs/

Tools

Benchmarking and monitoring is provided by tm-bench and tm-monitor, respectively. Their code is found here and these binaries need to be built seperately. Additional documentation is found here.

Sub-projects

  • Amino, a reflection-based improvement on proto3
  • IAVL, Merkleized IAVL+ Tree implementation

Applications

Research

Contributing

Yay open source! Please see our contributing guidelines.

Versioning

SemVer

Tendermint 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 Tendermint 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 (cli, rpc, p2p, etc.), but does not include the in-process Go APIs.

That said, breaking changes in the following packages will be documented in the CHANGELOG even if they don't lead to MINOR version bumps:

  • types
  • rpc/client
  • config
  • node
  • libs
    • bech32
    • common
    • db
    • errors
    • log

Exported objects in these packages that are not covered by the versioning scheme are explicitly marked by // UNSTABLE in their go doc comment and may change at any time without notice. Functions, types, and values in any other package may also change at any time.

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 tendermint blockchains. 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).

For more information on upgrading, see here

Code of Conduct

Please read, understand and adhere to our code of conduct.