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.
 
 
 
 
 
 
ValarDragon f76312ffe6 docs: Update secure-p2p doc to match the spec + current implementation 6 years ago
.circleci test make localnet in CI (#2281) 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 Make mempool aware of MaxGas requirement (#2360) 6 years ago
benchmarks rpc: Transform /status result.node_info.other into map (#2417) 6 years ago
blockchain p2p: Integrate new Transport 6 years ago
cmd [types] add Address to GenesisValidator (#2418) 6 years ago
config switch from jmhodges/levigo to DataDog/leveldb 6 years ago
consensus proxy: remove Handshaker from proxy pkg (#2437) 6 years ago
crypto crypto/secp256k1: Fix signature malleability, adopt more efficient en… (#2239) 6 years ago
docs docs: Update secure-p2p doc to match the spec + current implementation 6 years ago
evidence Implement BFT time (#2203) 6 years ago
libs Output error instead of panic when the given db_backend is not initialised (#2411) 6 years ago
lite Implement BFT time (#2203) 6 years ago
mempool Make mempool cache a proper LRU (#2407) 6 years ago
networks update some docs 7 years ago
node p2p: add RPCAddress to NodeInfoOther.String() (#2442) 6 years ago
p2p p2p: add RPCAddress to NodeInfoOther.String() (#2442) 6 years ago
privval Implement BFT time (#2203) 6 years ago
proxy proxy: remove Handshaker from proxy pkg (#2437) 6 years ago
rpc p2p: Integrate new Transport 6 years ago
scripts add script to add links in changelog 6 years ago
state proxy: remove Handshaker from proxy pkg (#2437) 6 years ago
test Remove gogoproto from Makefile's TOOLS (#2198) 6 years ago
tools tools/tm-bench: bounds check for txSize and improving test cases (#2410) 6 years ago
types [types] add Address to GenesisValidator (#2418) 6 years ago
version version: add and bump abci version 6 years ago
.editorconfig merge 2 rules in .editorconfig 7 years ago
.gitignore fix docs links (#2352) 6 years ago
CHANGELOG.md update UPGRADING.md and minor docs fixes 6 years ago
CHANGELOG_PENDING.md Make mempool cache a proper LRU (#2407) 6 years ago
CODE_OF_CONDUCT.md Add Code of Conduct 8 years ago
CONTRIBUTING.md contributing guide typos (#1831) 7 years ago
Gopkg.lock update Gopkg.lock 6 years ago
Gopkg.toml crypto/secp256k1: Fix signature malleability, adopt more efficient en… (#2239) 6 years ago
LICENSE GPLv3 -> Apache2.0 9 years ago
Makefile makefile: lint flags 6 years ago
README.md update readme, clsoes #2357 (#2359) 6 years ago
ROADMAP.md version bump. add roadmap back. minor fixes 7 years ago
SECURITY.md security.md 7 years ago
UPGRADING.md minor note in UPGRADING.md 6 years ago
Vagrantfile update Vagrantfile to install go1.11 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 a consensus proof and detailed protocol analysis checkout 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 :)

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.10 or higher

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

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.