January 20, 2023
RFC documentation is up to date*
*Most of it. Until the next PR is merged at least.
The Tari Requests for Comment site plays a few critical roles in the Tari community:
- It serves as a reference for the design and philosophy of the Tari protocol.
- It is the venue for proposing new ideas and major changes to the protocol.
- It provides a written record of how the project has developed over time.
The first of these roles is the most difficult to maintain consistently. The core contributors, by and large, enjoy writing code more than they relish maintaining swathes of documentation.
It’s not unexpected then, that a given feature of the Tari system and its associated RFC may diverge over time. A
maintainer will typically slap an
out-of-date label on the RFC when this happens so that readers aren’t mislead by
Over the course of time, almost all of our RFCs were marked
out-of-date. Late last year, we, as the core
contributor community set out to rectify that situation.
As of today, I’m very happy to announce that all RFCs related to the Tari Base Node have achieved
This was a massive collective effort that stretched over about eight weeks. Some 35 RFCs were reviewed, updated, and in some cases completely rewritten so that they reflect what is happening under the hood.
It was a bit like cleaning out the attic. There were a few RFCs, covered in dust underneath some old scuba gear that made us say,
“Oh, remember this old thing? Wow, I can’t believe we thought that was cool once”.
Those RFCs are captured for posterity in the Deprecated RFCs chapter of the site. Again, like cleaning out the attic, you never end up throwing anything away.
Of course, the 2nd law of thermodynamics never sleeps, entropy always wins, and these RFCs will eventually become out of date again. Fortunately, the base node code is fairly stable and well tested, and so the slide to disorder is not as steep as it used to be. As always, the code remains the source of truth.
Tari release v0.43.4
It was quiet over the festive season, but that didn’t stop the release train. v0.43.4 was released on 12 January and a minor bug-fix release landed on the 18th.
- automatically set base node fetures on startup, sign only if necessary (#5108) (9aa9436)
- vanity_id example should create id with base node features (#5107) (3b21199)
- add new igor seeds (#5106) (61d1b5e)
- add to/from json string for unblinded utxo in wallet ffi (#5098) (af25b63)
- add const to FixedHash::zero (#5084) (2d1bc82)
- console wallet spacing and naming (#5025) (e4a6303)
- functional wallet encryption (issue #5007) (#5043) (7b2311e)
- header sync start info (#5086) (df53843)
- header sync stuck trying to sync from base node (#5080) (0961f49)
- improved encryption key handling (#5027) (b2bed79)
- update message and signature key types (#5064) (a94189d)
- use range proof batch splitting (#5081) (70c522b)
- wallet errors (#5045) (9b16ffb)