The Tari core developers always trying to improve and simplify the process of developing templates. However, if you're eager to start experimenting with templates on Tari, we've simplified the...

Code audits On behalf of the Tari community, we are happy to announce that Coinspect will be conducting an audit of the Tari base node (Minotari) code and wallet library. Coinspect is a well-known...

Our initial take on [Cerberus] consensus came with a massive number of learnings for the team. The variant could best be described as a coming together of chained-hotstuff and optimistic-Cerberus...

In MimbleWimble things work a little differently than other blockchains. In most blockchains, a transaction is sent to a public key. Users then scan the blockchain for their public keys and know when...

We all know and love the console wallet but the mobile Aurora wallet has been quietly and steadily been getting faster, easier to use, and more reliable for the last few years. We decided that...

The Tari network has three primary clients, namely Validator Nodes, Wallets, and Indexers, excluding the Minotari network clients. Validator nodes execute transactions and reach an agreement using a...

Versioning This week we released new versions of StageNet, NextNet, and Development aka Esmeralda. All of the versions are available at Tari. The detailed versioning guide can be found here: detailed...

The two-layer system A recent post explained the two layer system in Tari. The two layers have had generic names for ages. The base layer/mimblewimble chain/Tari L1 is the proof-of-work layer that...

Breaking changes Another release, another breaking change. Jokes aside as we move closer and closer to a release we are trying to optimize the code base and include all features that might require...

Fees on the second layer prevent spam, and also provide an incentive for validator nodes to process transactions. When designing the fee mechanics, the Tari development community decided to use the...