Who Is Building Tari? Understanding the Core Contributor Program

Table of contents

Introduction

When we talk about Tari, we often talk about its privacy technology, mining, Tari Universe, or Ootle, which is still being built. Behind those names, though, is a more concrete question: who keeps them moving forward?

Some people maintain the underlying code. Others turn complex technology into usable products, run nodes, or troubleshoot failures. Still others answer questions and write guides day after day, helping people from different regions and language communities take part.

That work does not always make it into announcements, but it is what keeps an open-source project running.

Tari’s Core Contributor program is now operating in practice. As of September 12, 2026, ten contributors had been formally admitted through public nominations and votes and added to the forum’s CoreContributor group.

This is more than another list of names. It is an opportunity to meet people who have been building Tari for a long time and understand the responsibilities they are taking on.

What Is a Core Contributor?

CC stands for Core Contributor.

Tari’s CC program is for people who consistently contribute high-quality work and demonstrate reliable skills and a constructive approach to collaboration. It covers not only code but also product, infrastructure, project coordination, ecosystem collaboration, and community building.

Becoming a CC formally recognizes contributions already made and trust already earned. It also means continuing to take responsibility. CCs can participate in day-to-day decisions within their areas of work, receive access to resources as needed, and vote in Tari Council elections.

It is not an employment status at Tari Labs, nor an honorary title automatically earned by completing a certain number of tasks.

Likewise, CC membership does not automatically grant merge rights across every repository, server access, or other sensitive permissions. Access should match the work a person needs to do, rather than come bundled with a title.

The program connects three things that already belong together: sustained contributions, responsibility, and participation in project governance.

How Do CCs, the Council, and Tari Labs Relate?

These names often appear together, but they refer to different things.

The Tari Council is responsible for project-level governance, direction, and oversight. Core Contributors continue building within their respective fields and form the electorate that chooses the Council.

A person can be both a Council member and a CC, but the roles are not interchangeable. Serving on the Council does not automatically make someone a CC, and becoming a CC does not confer the Council’s decision-making authority.

Tari Labs is an organization that supports some of Tari’s development and product work. Some contributors it sponsors have joined the CC program, but corporate affiliation and CC membership are separate matters. Those contributors also went through public nomination and confirmation.

Beyond these formal roles is a wider community of contributors. Anyone can report problems, improve documentation, submit code, create tools, or help users within the scope of their abilities.

You do not need to become a CC before you can start building Tari. Not having the title does not make your contributions less important.

Meet the Current Core Contributors

The following introductions summarize the main grounds for nominating these ten members, as set out in their public forum nomination posts. They are not exhaustive accounts of everything each person has done. Each introduction includes the original nomination link for readers who want to learn more.

References to corporate support or sponsorship concern support for a contributor’s work, not payment for CC membership. They are also distinct from a nominator’s recommendation. Disclosure helps the community understand contributors’ relationships with organizations; the absence of a disclosure does not establish the absence of support.

Code CCs: Code and Development

blackwolfsa (GitHub: SWvheerden)

Nominated by: Fox

blackwolfsa is a longstanding core contributor to Tari’s L1. His nomination describes him as its current principal developer, with work directly tied to Minotari’s ongoing development and maintenance.

Alongside his code contributions, he regularly answers questions on the forum about the project’s history and technical implementation and asks direct, specific questions about proposals. For a base-layer protocol project, someone who understands both implementation details and their historical context is an important source of knowledge.

According to his nomination post, his contributions are sponsored by Tari Labs.

https://community.tari.com/t/cc-nomination-blackwolfsa/251

sprucetree (GitHub: brianp)

Nominated by: Fox

sprucetree is a core contributor and principal developer of Tari Universe. His work involves balancing product design with engineering requirements and turning design intent into working software.

His nomination also notes his work across other Tari repositories and deployments, along with important feedback on the CC program. One point he emphasized was that access should follow specific work and responsibilities, rather than become a package of rewards attached to a title.

According to his nomination post, his contributions are sponsored by Tari Labs.

https://community.tari.com/t/cc-nomination-sprucetree/254

Fox (GitHub: Kelketek)

Nominated by: kinkajou

Fox’s contributions span code, infrastructure, and governance processes.

He helped establish the Tari community forum and wiki, led the transition from the RFC process to the TIP process, and drafted and advanced the Core Contributor program. This work provides foundations for community discussion, shared knowledge, and formal decision-making.

On the technical side, his nomination also lists contributions to Tari’s website, assistance with community template development on Ootle, and reviews of consensus-related issues such as difficulty adjustment.

Fox’s contributions are sponsored by his own business, Artconomy.com.

https://community.tari.com/t/cc-nomination-fox/257

animalst (GitHub: sdbondi)

Nominated by: kinkajou

animalst is a lead developer of Ootle and a principal engineer of Tari’s L2.

As well as advancing Ootle through code, he answers developer questions on Discord and the forum, helping others understand the system and work through development problems. Combining core development with developer support helps more people build on the technology.

According to his nomination post, his contributions are sponsored by Tari Labs.

https://community.tari.com/t/cc-nomination-animalst/259

Product CCs: Product and Design

Naveen

Nominated by: kinkajou

Naveen is the founder of Tari Labs and has long been involved in product development. His nomination cites work ranging from Yats to Tari Universe, with particular emphasis on his experience in product management, design judgment, and visual quality.

For Tari Universe, that work concerns not just whether a feature exists, but how it is presented, whether interactions are clear, and whether the overall experience is consistent.

According to his nomination post, his contributions are sponsored by Tari Labs.

https://community.tari.com/t/cc-nomination-naveen/263

Infrastructure CCs: Infrastructure

Impala (GitHub: Snipa22)

Nominated by: kinkajou

Impala has long operated a mining pool and multiple Tari nodes and has published open-source tools used by the community.

Since Tari’s early days, he has helped debug wallet, network, and pool issues. He also continues to help users troubleshoot difficult problems on Telegram and Discord.

Keeping nodes stable, pools running, and wallet problems diagnosable is work that often becomes visible only when something goes wrong. Impala’s nomination reflects the importance of infrastructure maintenance and practical technical support to the project.

https://community.tari.com/t/cc-nomination-impala/258

Project CCs: Project Coordination

kinkajou (GitHub: m4r1m0)

Nominated by: Fox

kinkajou’s contributions are not confined to a single field.

His nomination cites experience coordinating blockchain upgrades with exchanges, moving community voice events from X Spaces to Discord, proposing and simulating network security improvements, and longstanding efforts to help community members understand and use Tari.

The Project CC role reflects the ability to connect different pieces of work: identifying what needs attention, coordinating the people involved, and helping get it done.

https://community.tari.com/t/cc-nomination-kinkajou/255

Community CCs: Community Building

ZhaoXi (GitHub: xt1085)

Nominated by: Fox

ZhaoXi has been involved in developing Tari’s Chinese-speaking community since its early days, answering questions on Telegram and Discord, coordinating moderators, and helping Chinese-speaking users understand the project.

His nomination also points to TariTalk, a website that documents Tari’s progress and organizes information for Chinese-speaking readers.

These efforts share a purpose: helping Tari cross language barriers so that people whose first language is not English can follow the project, use its tools, and participate in discussions.

https://community.tari.com/t/cc-nomination-zhaoxi/256

Terence

Nominated by: ZhaoXi

Terence is a longstanding administrator of Tari Chinese and Tari Million Club. He helps manage the groups and answer users’ questions and is also active across the wider Tari community’s channels.

He wrote an illustrated Chinese guide to common wallet questions, published by TariTalk, covering practical issues such as Tor settings, recovery phrases, wXTM conversion, missing balances, and transaction history.

This kind of contribution addresses everyday use: turning specific difficulties into solutions people can understand and follow.

https://community.tari.com/t/cc-nomination-terence/304

Yushan Ren (GitHub: eccstartup)

Nominated by: ZhaoXi

Yushan has long helped manage the Chinese-speaking community, supported users, and maintained Tari Show Archives.

He wrote a Chinese guide to Minotari nodes and the command-line wallet and continues to write about Mimblewimble, security, blockchain privacy, and Tari.

His contributions combine community support with technical education: helping users carry out practical tasks while also explaining the principles and limitations of privacy technology.

https://community.tari.com/t/cc-nomination-yushan-ren/305

Ecosystem CCs: Ecosystem Development

As of September 12, 2026, none of the ten formally admitted members listed above had been admitted under the Ecosystem CC category.

By nomination category, these ten members comprise four Code CCs, three Community CCs, and one each in Product, Infrastructure, and Project, with none yet in Ecosystem.

Different Kinds of Work, Building Tari Together

These nominations reveal a group of builders broader than a core development team alone.

The underlying protocol needs development and maintenance. Products need design and implementation. The network needs nodes and pools. Developers need documentation and support, while everyday users need guides, answers, and communities where they can talk to others.

These are different kinds of work, and they are not interchangeable. Once code is written, people still need to run it, help others understand it, and keep finding problems through real use.

The CC program did not create these contributions from scratch. All members had already been making sustained contributions to Tari before receiving formal CC status. What changes is that public nominations and admission procedures make contribution evidence, recommendations, and disclosed sponsorship relationships easier for the community to examine, while connecting sustained work with governance participation.

Of course, these ten people are not all of Tari’s builders. The formal roster records those who have completed the admission process; it does not define the limits of contribution.

How Does Someone Become a Core Contributor?

Tari’s CC program is built around the three Cs:

• Commitment: sustained involvement. Staying involved in the project over time, rather than completing a few tasks in a short burst.
• Conduct: reliable behavior and collaboration. Respecting others, disagreeing constructively, and helping fellow contributors.
• Caliber: ability and quality of work. Demonstrating sound judgment and the ability to deliver in one’s field.

The program also requires at least six months of participation in Tari. That is not an automatic route to eligibility once enough time has passed. The existing team must still judge whether a person has earned sufficient trust and is ready for responsibility, based on their contributions.

Candidates must be nominated by an existing CC or Council member, with evidence of their contributions and disclosure of corporate sponsorship. Nominations have a fourteen-day discussion and voting period. At the current size of the electorate, admission requires at least five affirmative votes and no negative votes.

If there is an explicit objection, the candidate may appeal to the Council. An override requires a unanimous Council decision and publicly stated reasoning.

After joining, CCs must continue to meet the expectations for commitment, conduct, and caliber. Membership is not an irrevocable status secured by a single vote.

For people who are not yet CCs, the more practical starting point remains the same: find a genuine need and do good work within a scope you can take responsibility for. That might mean fixing a problem, improving documentation, writing a clear bug report, or consistently helping users.

From Ten Members to the Next Stage

The CC program is still in its bootstrap period.

Under its rules, Council members can vote on CC nominations until the program has inducted its eleventh member. After that, Council membership alone no longer carries this regular voting right. The CC body votes on subsequent admissions, while the appeals process remains in place.

Council members who are also CCs can still vote as CCs. This milestone therefore ends the bootstrap arrangement; it does not mean the two groups will cease to overlap.

The forum has already hosted discussions about that overlap, corporate sponsorship, and voting methods. Some participants worry about concentrated governance influence. Others argue that overlapping roles help keep things running at an early stage when active contributors are relatively few.

Those discussions should not be hidden, but they need not be the only lens through which to understand the program. What deserves continued attention is whether membership broadens, whether sponsorship and access relationships remain transparent, and whether members continue to deliver and help new contributors grow.

Reaching a membership threshold is a procedural milestone. Building broader, more reliable collaboration is the longer-term work.

Tari’s Builders Extend Beyond This List

The strength of an open-source project depends not only on the vision it puts forward, but also on whether people are willing to keep doing the work well.

Tari’s CC program is now operating in practice. It makes it easier for the community to see who is maintaining the protocol, developing products, running infrastructure, and supporting users, and who is taking ongoing responsibility for that work.

That deserves to be documented and recognized. Many contributions are not dramatic, but through fixes, documentation, and everyday help, they keep the project moving forward.

The opportunity to build Tari, however, is not limited to the published roster, nor does it belong only to developers.

For anyone willing to take part, the starting point need not be a grand plan. It can be fixing one problem, writing one clear guide, helping one user, or staying with something worthwhile long enough to make a difference.

How far can Tari go? No one can know in advance. But we believe Tari’s future is taking shape through the work of each person building it.

Behind these names are real people. Each contributes in their own way, helping turn privacy and freedom from ideals into things people can use and choices they can make. And the journey they are shaping together continues.

Sources

This article draws on public program documents and forum nomination materials checked as of September 12, 2026. Membership and program rules may change. It is a community introduction by TariTalk, not an official statement from the Tari Council.

• Core Contributor program:
  https://rfc.tari.com/Process/TIP-PROC-0006_core_contributor_program
• Forum discussion of the CC program:
  https://community.tari.com/t/the-core-contributor-program/204
• Discussion of overlapping Council and CC roles:
  https://community.tari.com/t/should-council-members-be-ccs-too/260

Individual nomination sources are linked in the corresponding introductions.