Giter VIP home page Giter VIP logo

atom_one's Introduction

Tendermint

UPDATE: TendermintCore featureset is frozen for LTS, see issue #9972
This is the latest stable release used by cosmoshub-4, version 0.34.24
The previous main branch (v0.38.xx) can now be found under "main_backup"

banner

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

Version API Reference Go version Discord chat License Sourcegraph

Branch Tests Linting
main Tests Lint

Tendermint Core is a 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, refer to the Tendermint Specification.

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

Documentation

Complete documentation can be found on the website.

Releases

Please do not depend on main as your production branch. Use releases instead.

Tendermint has been in the production of private and public environments, most notably the blockchains of the Cosmos Network. we haven't released v1.0 yet since we are making breaking changes to the protocol and the APIs. See below for more details about versioning.

In any case, if you intend to run Tendermint in production, we're happy to help. You can contact us over email or join the chat.

More on how releases are conducted can be found here.

Security

To report a security vulnerability, see our bug bounty program. For examples of the kinds of bugs we're looking for, see our security policy.

We also maintain a dedicated mailing list for security updates. We will only ever use this mailing list to notify you of vulnerabilities and fixes in Tendermint Core. You can subscribe here.

Minimum requirements

Requirement Notes
Go version Go 1.18 or higher

Install

See the install instructions.

Quick Start

Contributing

Please abide by the Code of Conduct in all interactions.

Before contributing to the project, please take a look at the contributing guidelines and the style guide. You may also find it helpful to read the specifications, and familiarize yourself with our Architectural Decision Records (ADRs) and Request For Comments (RFCs).

Versioning

Semantic Versioning

Tendermint uses Semantic Versioning 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 users of 0.X.X versions of Tendermint, the MINOR version is used to signal breaking changes across Tendermint's API. This API includes all publicly exposed types, functions, and methods in non-internal Go packages as well as the types and methods accessible via the Tendermint RPC interface.

Breaking changes to these public APIs will be documented in the CHANGELOG.

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 blockchain histories.

For more information on upgrading, see UPGRADING.md.

Supported Versions

Because we are a small core team, we only ship patch updates, including security updates, to the most recent minor release and the second-most recent minor release. Consequently, we strongly recommend keeping Tendermint up-to-date. Upgrading instructions can be found in UPGRADING.md.

Resources

Libraries

Applications

Research

Join us!

Tendermint Core is maintained by Interchain GmbH. If you'd like to work full-time on Tendermint Core, we're hiring!

Funding for Tendermint Core development comes primarily from the Interchain Foundation, a Swiss non-profit. The Tendermint trademark is owned by Tendermint Inc., the for-profit entity that also maintains tendermint.com.

atom_one's People

Contributors

jaekwon avatar moul avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

atom_one's Issues

Improve the Liquid Staking tax language

It's a bit clunky as is, and 1% per month increase may be too fast.

The language should also apply to each ICS blockchain, but for now I think it is safer to experiment with liquid staking on ATOMs. Perhaps the same system described for the Cosmos Hub with ATOMs can be applied individually for each blockchain, but this seems complicated. It may make sense to limit the total amount of staked interchain accounts for ICS to the Liquid Staking Factor.

how to immunize against the mark of the beast

The powers of the world as represented by the WEF is intent on implementing the mark of the beast. As per the Book of Revelation,

  • The nations of the world were deceived by pharmakia/medicine (Revelation 18 23)
  • The mark (in original Koine greek, a needle prick) is required to buy or sell (Revelation 13:17)
  • The mark gives you sores (Revelation 16:2) // NOTE: have no fear about it even if you got the shot.

How could it be that a two millenia old document can predict what is happening today? Well, most people don't read the bible at all, and anyone can see the light and turn into a white-hat. It appears to me that the white-hats have shepherded the black-hats into following a script that ends up exposes them when it is too late. And now the "true Christians" have indeed exposed the NWO agenda, and this awareness is growing exponentially.

This control grid was leaked by whistleblower Senator Larry McDonald in the 70's, whose plane was soon after shot down. (highly censored https://twitter.com/Xx17965797N/status/1578662395358384128?s=20&t=MrwxzKymkKv6ehdfhvKlAA) . The "monolithic and ruthless conspiracy that relies on covert means" was leaked before by JFK who was assassinated in 1963. https://www.youtube.com/watch?v=RhkjYJAHCjM . Now we have experienced the NWO control grid by the WEF, and its young global leaders, such as Fauci, Gates, Gavin Newsom, Trudeau; and even experiencing the war between Zelenski and Putin. The WEF, whose leader Schwab boasted about having infiltrated government cabinets, also wants us to "own nothing and be happy". If it isn't clear enough, their logo even includes a subtle 666.

The fact of the matter is, we probably do want some regulatory system to deal with large scale theft of coins resulting from bugs or human error/malice. Even if such a regulatory system is not imposed upon any zones, zones may want to voluntarily adopt some kind of regulatory policy. And zones probably want to enforce these policies across zones that choose to adopt the same policies.

It follows, that in a minimal system, zones should be allowed to choose their own set of regulatory policies, and the Hub can help enforce these policies when it comes to IBC transfers across zones, or from hub to zone. From the perspective of the Hub, this is still a permissionless, voluntary system.

When it comes to transactions on the hub, and transactions from zones to the hub, we should adopt the most minimal regulatory system. We could arguably do nothing--until it is too late, and we learn our lesson that we need something in the case of large scale theft from malice or bugs. The minimal nonzero policy we can adopt, is to enable one or more bonded DAOs to designate one or more addresses as being affected, with full justification, to temporarily freeze those coins, where the coins will unfreeze automatically until the hub's governance votes to act upon the frozen coins or to freeze the coins for longer to determine the facts. Something along these lines is a minimal regulatory system. Also, it is probably sensible for the hub to implement a kind of delayed transfer system, so that accounts with large token amounts can be protected by this regulatory system in the case of theft. Perhaps accounts can opt out of this transfer-delay protection.

The above minimal regulatory system still begs for a full system of checks and balances. That's another rabbit hole for another issue/document. The ATOM1 constitution hints at a system of checks and balances, but IMO it isn't complete yet, at least not in its current written form.

The challenge is to (a) further refine and minimize the aforementioned hub internal regulatory policy, and (b) to define the inter-zone permissionless regulatory framework. With these implemented, the hub can ensure the rights to property, protect property in the case of theft, and allow zones to permissionlessly set their own policies. This is a critical architecture/constitutional/regulatory problem we should be discussing today. Until it is implemented, IMO crypto will not be ready for the general population.

The problem is, getting this wrong is significantly worse than not implementing it. When done wrong, either it will become destructive (tokens being frozen/stolen by the regulatory system), or it will become abusive (think 1984 global ************ as per the NWO agenda, followed by global human depopulation). It follows that the Cosmos Hub should not implement a regulatory framework such that it can allow the permission innovation and proofing of regulatory frameworks over time. This best increases the chances of success in designing the right regulatory framework.

A Rule should be added to the constitution to succinctly represent the above paragraph.

unbonding PHOTON -> ATOM should turn into bonded ATOMs.

This is safer for PHOTON users who want to unbond to ATOMs to protect against governance takeover.
When the PHOTON -> ATOM unbonding extension hits, more users will want to unbond, possibly creating a cascade.
The sudden creation of free ATOMs will spook the markets, whereas if it becomes bonded ATOMs, this is less of an issue.

Add ATOM ICS for simple replication

Through discussions with Seb and Brian on the interop, came to the rightful conclusion that the simple ICS implementation with ATOM bonding should be supported alongside the PHOTON ICS system.

tweak quorum

The quorum should probably just use ATOM tokens per usual.
The total votes tallied can use ATOM + PHOTON (with the whole of PHOTONs being at most 50% of voting power).

slash factor

When 1/3 are involved in double signing or a complex attack, how much they are slashed should depend on factors.
The main factor should be whether there was a bug/exploit involved. Even so, they should be slashed.
If the attack was intentional, then they should be slashed 100%. If not, they should be slashed some factor of 100%.

clarify burns

When ATOMs are burned via stake slashing, the ATOMs bonded under PHOTONs get slashed pro-rata as explained in the constitution.
When PHOTONs are burned via ICS2 slashing, or even tx fee burn, I believe they can simply burn and disappear, making the ATOM tokens more valuable in comparison. In other words, the invariant that there will always be 1 billion PHOTONs can always be preserved, for as long as there is one iota of an ATOM.

Translations

Chinese: mirror.xyz/0xshushu.eth
Korean: (see PR)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.