The Tari Show (June 9, 2026)
🛡 Security: AI scanning over traditional audits
- Kinkachu asked about hiring an auditor like Trail of Bits, citing recent Zcash and Mythos bugs. Naveen: Zcash was audited multiple times and the bug still existed. AI models never get bored, can run in swarms, and will change the auditing landscape within 12 months. Should be a Council priority.
- Fox: models follow the faintest scent a human researcher would skip past.
- Mimblewimble helps here: supply is verifiable with simple math (sum of outputs minus inputs), unlike protocols relying on obscure cryptography.
🔧 Ootle: L2 shipping this year
- Stan opened three PRs: variable substate reads, indexer improvements, transaction pool bug fixes.
- Stablecoin issuer making progress on their end.
⛏ L1, Bridge, Mining
- SW working on node stability.
- Martins fixing bridge issues, patch out later this week or next.
- Lucky pool node was unsynced; fix expected same day.
🤖 Moderation: bots first, humans as backstop
- Lapse over the weekend (inappropriate material in Telegram), but community flagged it and bots recovered. Fox: impressed by the backend after initial skepticism. Good moderation contributors are candidates for the core contributor program.
📐 TIP: Breaking Up Tari Universe
Simon proposed breaking Universe into separate apps (mining, wallet, bridge) that ship independently. Universe hasn't released in 5+ weeks with PRs backing up.
Naveen cautioned against refactoring something that already works. Universe took years to build.
Sean O'Brien: modular components help the dev ecosystem, but don't lose the polished UX. Start with the most support-heavy pieces (GPU mining).
Fox proposed an app runner model: separate binaries connecting to the wallet via API, with sandboxed transaction permissions.
No resolution. Candidate for a formal TIP.
📡 TIP: Moving Spaces to Discord
Simon proposed hosting the weekly Space on Discord to reach the Gen Z demographic. Fox: Discord is more reliable than X, and most dev communities already live there. Naveen: moving platforms alone won't create growth, but it costs nothing to try.
🔐 Mimblewimble Privacy
DHC asked about the deanonymization attack that hit Grin (listener nodes observing mempool transactions). Naveen: needs more research, not convinced it constitutes full deanonymization on Tari.
🏛 Governance and Leadership
Zachary Levy (first-time speaker, following Tari ~6 years) asked whether the project is ready to operate without strong centralized leadership.
Fox: the Council isn't leaderless. It's a core group making product and direction decisions. Core developers remain full-time at Tari Labs. Component leads (Stan on L2, Brian on Universe) continue to own their areas.
Sean O'Brien: drive-by open source contributions are only 10-15% of a project's commits. A funded core is essential.
Naveen's goal: Council fully decided by next week.
Got thoughts on any of the TIP ideas? Come talk about them on next week's Space.
🛡 Security: AI scanning over traditional audits
- Kinkachu asked about hiring an auditor like Trail of Bits, citing recent Zcash and Mythos bugs. Naveen: Zcash was audited multiple times and the bug still existed. AI models never get bored, can run in swarms, and will change the auditing landscape within 12 months. Should be a Council priority.
- Fox: models follow the faintest scent a human researcher would skip past.
- Mimblewimble helps here: supply is verifiable with simple math (sum of outputs minus inputs), unlike protocols relying on obscure cryptography.
🔧 Ootle: L2 shipping this year
- Stan opened three PRs: variable substate reads, indexer improvements, transaction pool bug fixes.
- Stablecoin issuer making progress on their end.
⛏ L1, Bridge, Mining
- SW working on node stability.
- Martins fixing bridge issues, patch out later this week or next.
- Lucky pool node was unsynced; fix expected same day.
🤖 Moderation: bots first, humans as backstop
- Lapse over the weekend (inappropriate material in Telegram), but community flagged it and bots recovered. Fox: impressed by the backend after initial skepticism. Good moderation contributors are candidates for the core contributor program.
📐 TIP: Breaking Up Tari Universe
Simon proposed breaking Universe into separate apps (mining, wallet, bridge) that ship independently. Universe hasn't released in 5+ weeks with PRs backing up.
Naveen cautioned against refactoring something that already works. Universe took years to build.
Sean O'Brien: modular components help the dev ecosystem, but don't lose the polished UX. Start with the most support-heavy pieces (GPU mining).
Fox proposed an app runner model: separate binaries connecting to the wallet via API, with sandboxed transaction permissions.
No resolution. Candidate for a formal TIP.
📡 TIP: Moving Spaces to Discord
Simon proposed hosting the weekly Space on Discord to reach the Gen Z demographic. Fox: Discord is more reliable than X, and most dev communities already live there. Naveen: moving platforms alone won't create growth, but it costs nothing to try.
🔐 Mimblewimble Privacy
DHC asked about the deanonymization attack that hit Grin (listener nodes observing mempool transactions). Naveen: needs more research, not convinced it constitutes full deanonymization on Tari.
🏛 Governance and Leadership
Zachary Levy (first-time speaker, following Tari ~6 years) asked whether the project is ready to operate without strong centralized leadership.
Fox: the Council isn't leaderless. It's a core group making product and direction decisions. Core developers remain full-time at Tari Labs. Component leads (Stan on L2, Brian on Universe) continue to own their areas.
Sean O'Brien: drive-by open source contributions are only 10-15% of a project's commits. A funded core is essential.
Naveen's goal: Council fully decided by next week.
Got thoughts on any of the TIP ideas? Come talk about them on next week's Space.
The Tari Show — June 16, 2026
🔧 Ootle
- Stan published two PRs on genesis substates.
- He also fixed wallet skin, header retention, indexer, and CI issues.
- L2 is still expected to ship this year.
- Open question: whether to launch with the stablecoin ready, or shortly after.
- The stablecoin issuer is actively working with contributors now.
🖥 Universe
- No new release yet.
- Brian has been traveling.
- A new version is expected in the next week or two.
🌉 Bridge
- The community asked about transaction limits.
- They exist to prevent bridge exploits.
- Naveen is open to a short-term increase.
- Simon will publish a TIP to double the limits that can be decided quickly.
🏛 Kraken
- Tari was on Kraken’s listing roadmap and got dropped.
- Naveen said exchanges list what drives trading fees, not charity.
- The community should advocate and make the business case.
- The private stablecoin on L2 is the differentiator.
- Kraken’s leadership is pro-freedom — it still lists Monero in the US — so values are aligned.
🗳 Council
- The Council should be formalized within the next week to week and a half.
- Naveen is courting both community and industry candidates for the inaugural Council.
- Several TIPs are queued and waiting.
💰 Bounties
- There has been a dry spell of new bounties.
- Issues are piling up that should be converted into bounties.
- This is being addressed this week.
📡 Announcement
- The Tari Show is moving to Discord next week.
- It will also be streamed to X and YouTube.
- The team is working on getting Stan into an upcoming Space.
🔧 Ootle
- Stan published two PRs on genesis substates.
- He also fixed wallet skin, header retention, indexer, and CI issues.
- L2 is still expected to ship this year.
- Open question: whether to launch with the stablecoin ready, or shortly after.
- The stablecoin issuer is actively working with contributors now.
🖥 Universe
- No new release yet.
- Brian has been traveling.
- A new version is expected in the next week or two.
🌉 Bridge
- The community asked about transaction limits.
- They exist to prevent bridge exploits.
- Naveen is open to a short-term increase.
- Simon will publish a TIP to double the limits that can be decided quickly.
🏛 Kraken
- Tari was on Kraken’s listing roadmap and got dropped.
- Naveen said exchanges list what drives trading fees, not charity.
- The community should advocate and make the business case.
- The private stablecoin on L2 is the differentiator.
- Kraken’s leadership is pro-freedom — it still lists Monero in the US — so values are aligned.
🗳 Council
- The Council should be formalized within the next week to week and a half.
- Naveen is courting both community and industry candidates for the inaugural Council.
- Several TIPs are queued and waiting.
💰 Bounties
- There has been a dry spell of new bounties.
- Issues are piling up that should be converted into bounties.
- This is being addressed this week.
📡 Announcement
- The Tari Show is moving to Discord next week.
- It will also be streamed to X and YouTube.
- The team is working on getting Stan into an upcoming Space.
😇1
The Tari Show (June 23, 2026)
First show on Discord. Stan and SW, two core protocol engineers, joined as guests. Better experience than X all around. No longer "Spaces."
🔧 Ootle: hardening and a Taproot-style upgrade
- Stan has spent the last month hardening the Ootle: putting bounds in place, fixing DOS vectors, and preventing untrusted sources from doing things outside the design.
- Building a MAST/Taproot-style construction so spends can carry rules without a full contract. Privacy benefit: only the script you actually use is revealed at spend time; the rest stays hidden behind a local root.
- Martins added a Go SDK for the Ootle. Now three: TypeScript, Python, and Go.
- Test net reset planned next week to introduce the Taproot-style scripts and other breaking changes.
🖥 Universe: release targeted for second week of July
- Brian is allocating significant time next week to review the backlog of open PRs and run end-to-end QA testing.
- He'll work alongside SW so Universe releases aren't a single point of failure going forward.
- Backlog is significant, so expect several days. New release likely around the second week of July. Fox has a PR in the queue.
⛏ L1 (SW)
- Working on wallet infrastructure, Universe integration, and an updated proof-of-work RFC. Also the point of contact for exchanges and other counterparties that have integrated Tari.
🗜 Pruning
- Prune mode is in beta. A full node DB is ~110GB on the current release, ~60GB on the prerelease, and a pruned node runs ~20GB. Set a pruning horizon in the config to enable it. SW is debugging a possible issue. This is Mimblewimble's core advantage: you only track the unspent set plus kernels, not the whole chain.
🌉 Bridge
- Bridge limits were doubled, executed in a few days. Shoutout to the team.
🔗 Atomic swaps?
- Doable on both L1 (Tari script) and L2. RFCs already exist for BTC and Monero swaps. Choice depends on what you want at the end (Tari, a stablecoin, etc.) and your finality/speed needs.
🧱 Smart contract upgrades
- Ootle components can be upgraded: add fields, change the template code behind them. Limited on purpose. You generally must be the original creator, and you can lock a contract down so it has no owner at all.
- Post-mainnet, contracts must stay backwards-compatible or you risk a hard fork. This is why breaking changes are happening now, pre-mainnet.
- Infinite loop? Every WASM op code has a cost. Once the transaction's budget is exhausted, it aborts.
🛰 Validator decentralization
- The Ootle launches centralized. BFT/HotStuff consensus needs a registered validator list, unlike Nakamoto consensus where anyone can produce a block. Centralized launch makes upgrades far easier early on.
- The planned path to permissionless: submit a validator registration on L1, which the L2 validators pick up to add you to the list. Likely proof-of-stake, with stake burned into the L2. Sharding (Cerberus) makes this harder. Timeline uncertain, significant work ahead. May start federated with trusted parties (possibly the Council).
- Stake amount undecided. Currently zero (which doesn't work on mainnet). "More than one, less than 21 billion." Intent is to keep it affordable.
💰 Staking rewards
- Two mechanisms: validator node operators earn a meaningful share of L2 transaction fees, and early validators may get additional incentives from the community pool premine tokens.
🔐 Privacy and interactive payments
- Interactive transactions were dropped to remove the Tor dependency. Wallet-to-wallet comms are a massive problem on mobile, and Tor proved too unreliable.
- Full transaction graph unlinkability isn't feasible on Tari. Because Tari script requires all inputs to validate the scripts, you can't fully cut through. You can combine transactions to shrink the anonymity set, but the inputs remain.
🏛 Governance
- The difficulty algorithm change (consecutive block penalty adjustment) is a good test case: it needs a decision, and because it's a hard fork it requires ~3 months minimum notice to exchanges and the community.
First show on Discord. Stan and SW, two core protocol engineers, joined as guests. Better experience than X all around. No longer "Spaces."
🔧 Ootle: hardening and a Taproot-style upgrade
- Stan has spent the last month hardening the Ootle: putting bounds in place, fixing DOS vectors, and preventing untrusted sources from doing things outside the design.
- Building a MAST/Taproot-style construction so spends can carry rules without a full contract. Privacy benefit: only the script you actually use is revealed at spend time; the rest stays hidden behind a local root.
- Martins added a Go SDK for the Ootle. Now three: TypeScript, Python, and Go.
- Test net reset planned next week to introduce the Taproot-style scripts and other breaking changes.
🖥 Universe: release targeted for second week of July
- Brian is allocating significant time next week to review the backlog of open PRs and run end-to-end QA testing.
- He'll work alongside SW so Universe releases aren't a single point of failure going forward.
- Backlog is significant, so expect several days. New release likely around the second week of July. Fox has a PR in the queue.
⛏ L1 (SW)
- Working on wallet infrastructure, Universe integration, and an updated proof-of-work RFC. Also the point of contact for exchanges and other counterparties that have integrated Tari.
🗜 Pruning
- Prune mode is in beta. A full node DB is ~110GB on the current release, ~60GB on the prerelease, and a pruned node runs ~20GB. Set a pruning horizon in the config to enable it. SW is debugging a possible issue. This is Mimblewimble's core advantage: you only track the unspent set plus kernels, not the whole chain.
🌉 Bridge
- Bridge limits were doubled, executed in a few days. Shoutout to the team.
🔗 Atomic swaps?
- Doable on both L1 (Tari script) and L2. RFCs already exist for BTC and Monero swaps. Choice depends on what you want at the end (Tari, a stablecoin, etc.) and your finality/speed needs.
🧱 Smart contract upgrades
- Ootle components can be upgraded: add fields, change the template code behind them. Limited on purpose. You generally must be the original creator, and you can lock a contract down so it has no owner at all.
- Post-mainnet, contracts must stay backwards-compatible or you risk a hard fork. This is why breaking changes are happening now, pre-mainnet.
- Infinite loop? Every WASM op code has a cost. Once the transaction's budget is exhausted, it aborts.
🛰 Validator decentralization
- The Ootle launches centralized. BFT/HotStuff consensus needs a registered validator list, unlike Nakamoto consensus where anyone can produce a block. Centralized launch makes upgrades far easier early on.
- The planned path to permissionless: submit a validator registration on L1, which the L2 validators pick up to add you to the list. Likely proof-of-stake, with stake burned into the L2. Sharding (Cerberus) makes this harder. Timeline uncertain, significant work ahead. May start federated with trusted parties (possibly the Council).
- Stake amount undecided. Currently zero (which doesn't work on mainnet). "More than one, less than 21 billion." Intent is to keep it affordable.
💰 Staking rewards
- Two mechanisms: validator node operators earn a meaningful share of L2 transaction fees, and early validators may get additional incentives from the community pool premine tokens.
🔐 Privacy and interactive payments
- Interactive transactions were dropped to remove the Tor dependency. Wallet-to-wallet comms are a massive problem on mobile, and Tor proved too unreliable.
- Full transaction graph unlinkability isn't feasible on Tari. Because Tari script requires all inputs to validate the scripts, you can't fully cut through. You can combine transactions to shrink the anonymity set, but the inputs remain.
🏛 Governance
- The difficulty algorithm change (consecutive block penalty adjustment) is a good test case: it needs a decision, and because it's a hard fork it requires ~3 months minimum notice to exchanges and the community.
Likely one of the Council's first decisions.
- Roughly 5 TIPs are queued waiting on the Council. First meeting will be packed. Council gets announced first, then the first conversations get organized.
- Working groups aren't fully scoped yet. For now: start collaborating on the forums and submit TIPs as a group. Refinement comes once the Council is in place.
- Naveen has been recruiting community members with complementary talents and connections for a strong inaugural Council.
🛍 dApps in Universe
- DHC argued for making Ootle apps accessible through Tari Universe (safer than Googling and risking phishing, and more decentralized than browser-wallet setups). Naveen agreed on both points: Universe can surface "known safe" apps vetted by the Council, while the community builds its own verification muscle.
- Expect two modes: dApps inside Universe and dApps outside it. Both are fine; an agent-focused dApp might live entirely outside Universe.
🎉 Bounties
- Sanrishi's UTXO race condition fix was merged. Shoutout.
- New Ootle bounty live and being worked on: 150,000 XTM.
Shoutouts: Stan and SW for the protocol work, Kinkaju for organizing the show, Fox, Simon, DHC, and JJ for great questions. Same time next week, on Discord.
- Roughly 5 TIPs are queued waiting on the Council. First meeting will be packed. Council gets announced first, then the first conversations get organized.
- Working groups aren't fully scoped yet. For now: start collaborating on the forums and submit TIPs as a group. Refinement comes once the Council is in place.
- Naveen has been recruiting community members with complementary talents and connections for a strong inaugural Council.
🛍 dApps in Universe
- DHC argued for making Ootle apps accessible through Tari Universe (safer than Googling and risking phishing, and more decentralized than browser-wallet setups). Naveen agreed on both points: Universe can surface "known safe" apps vetted by the Council, while the community builds its own verification muscle.
- Expect two modes: dApps inside Universe and dApps outside it. Both are fine; an agent-focused dApp might live entirely outside Universe.
🎉 Bounties
- Sanrishi's UTXO race condition fix was merged. Shoutout.
- New Ootle bounty live and being worked on: 150,000 XTM.
Shoutouts: Stan and SW for the protocol work, Kinkaju for organizing the show, Fox, Simon, DHC, and JJ for great questions. Same time next week, on Discord.
The Tari Show (June 30, 2026)
🔧 Ootle: test net reset
- Template fees are now quadratic (larger templates cost more). Templates with unnecessary debug sections are rejected; wallets auto-strip them. Merkle script tree working in UTXOs, enabling HTLC-style spend rules on L2.
- Stan asked for community feedback on the new fee structure.
⛏ L1: burn commitments and replay prevention
- Burnt commitments now enforced as unique via consensus rule. SW also changed UTXO selection to prevent a replay attack exploiting matching blinding factors against exchanges.
- Additional fixes to pruned sync edge cases and peer exchange.
🖥️ Universe: five bounties merged, Fox's PNPM PR
- Four bounties merged this week totaling 105,000 XTM. 0xPepeSilvia: Windows auto-start fix (60K) and Linux build docs (15K). Catnap7: CPU hashrate unit fix (15K) and stale binary cleanup (15K).
- Fox's NPM-to-PNPM switch merged, disabling post-install scripts by default to reduce supply chain attack surface.
🏛️ Council: 7 members, announcement this week
- Naveen, 3 community-voted, 3 behind-the-scenes community members. Marguerite introduced herself: Bitcoin creative, built Decred's community from scratch, tracked Tari since conception. Remaining members announced this week.
⚖️ Difficulty adjustment
- Kinkaju pushed for faster action on TIP-004. SW: the change helps prevent selfish mining but won't stop pool-hopping. 90-block window chosen through simulation; shorter windows cause oscillations.
- Naveen proposed the Council review TIP-004 as its first priority and adopt a regular hard fork cadence. SW: bundle any parameter changes into this fork.
🔗 L1 vs L2
- Fox asked when to use Tari Script vs the Ootle. SW: Tari Script is non-Turing complete, suited for atomic swaps and HTLCs. Everything in Tari Script can be done on the Ootle, but not the reverse.
📅 Next week's show might move to Wednesday.
🔧 Ootle: test net reset
- Template fees are now quadratic (larger templates cost more). Templates with unnecessary debug sections are rejected; wallets auto-strip them. Merkle script tree working in UTXOs, enabling HTLC-style spend rules on L2.
- Stan asked for community feedback on the new fee structure.
⛏ L1: burn commitments and replay prevention
- Burnt commitments now enforced as unique via consensus rule. SW also changed UTXO selection to prevent a replay attack exploiting matching blinding factors against exchanges.
- Additional fixes to pruned sync edge cases and peer exchange.
🖥️ Universe: five bounties merged, Fox's PNPM PR
- Four bounties merged this week totaling 105,000 XTM. 0xPepeSilvia: Windows auto-start fix (60K) and Linux build docs (15K). Catnap7: CPU hashrate unit fix (15K) and stale binary cleanup (15K).
- Fox's NPM-to-PNPM switch merged, disabling post-install scripts by default to reduce supply chain attack surface.
🏛️ Council: 7 members, announcement this week
- Naveen, 3 community-voted, 3 behind-the-scenes community members. Marguerite introduced herself: Bitcoin creative, built Decred's community from scratch, tracked Tari since conception. Remaining members announced this week.
⚖️ Difficulty adjustment
- Kinkaju pushed for faster action on TIP-004. SW: the change helps prevent selfish mining but won't stop pool-hopping. 90-block window chosen through simulation; shorter windows cause oscillations.
- Naveen proposed the Council review TIP-004 as its first priority and adopt a regular hard fork cadence. SW: bundle any parameter changes into this fork.
🔗 L1 vs L2
- Fox asked when to use Tari Script vs the Ootle. SW: Tari Script is non-Turing complete, suited for atomic swaps and HTLCs. Everything in Tari Script can be done on the Ootle, but not the reverse.
📅 Next week's show might move to Wednesday.
Tari Show recap — July 21 🐢
Core Contributor program debate is the main event. Naveen also confirmed the Ootle is still on track for this year.
Recap below.
---
Core Contributor program
Fox's TIP is under active debate. The uncontroversial part: CCs elect the Council.
The contested part: how people join and how access is granted. Can you be a CC with no specific access? Should status be tied to responsibility?
Still being hashed out.
---
Trust over checkboxes
Naveen's note on the framework: trust is earned, and a checklist doesn't prove someone is trustworthy.
His framing — this is a financial system, hopefully securing serious value one day. Worth being careful about who gets keys.
---
"Hard fork" → "network upgrade"
Kinkajou's advocacy has pushed a network upgrade forward. Code changes look done, testing next.
Fox noted the process isn't documented anywhere. It's going in the wiki.
Both agreed the term itself should change.
---
Ootle status
Still on track for this year. No delays flagged.
Current focus is refinement and hardening ahead of mainnet. Active development visible on GitHub — consensus protection, security handling.
---
Marketing: there is no strategy
Naveen, asked directly: right now there is no marketing strategy, by design.
No head of marketing, no KOL campaigns. The bet is on organic, decentralised community momentum.
Proof cited: Tari press coverage in a Korean economic newspaper, zero involvement from Labs or Council.
---
On Council members and reach
A community member asked why a Council member with 1.5M followers hasn't tweeted about Tari.
Naveen: they were brought in for their skill set in communication and narrative, not their follower count. No pressure is being applied to post.
---
Other bits
Meowmancer built an open-source GPU miner. Contributors are evaluating swapping it in for LOL Miner, which carries a dev fee.
Bridge transaction issues appear fixed — Brian worked on it.
blackwolfsa doing security hardening on Tari core. Two CVEs fixed, details held back.
---
Want a bounty? Open an issue.
Contributors flagged the core problem: by the time a bounty is well-defined, someone's usually solved it already.
Best thing you can do is open new issues and feature requests. That's what creates bounties.
Full show on the Tari Community YouTube.
Core Contributor program debate is the main event. Naveen also confirmed the Ootle is still on track for this year.
Recap below.
---
Core Contributor program
Fox's TIP is under active debate. The uncontroversial part: CCs elect the Council.
The contested part: how people join and how access is granted. Can you be a CC with no specific access? Should status be tied to responsibility?
Still being hashed out.
---
Trust over checkboxes
Naveen's note on the framework: trust is earned, and a checklist doesn't prove someone is trustworthy.
His framing — this is a financial system, hopefully securing serious value one day. Worth being careful about who gets keys.
---
"Hard fork" → "network upgrade"
Kinkajou's advocacy has pushed a network upgrade forward. Code changes look done, testing next.
Fox noted the process isn't documented anywhere. It's going in the wiki.
Both agreed the term itself should change.
---
Ootle status
Still on track for this year. No delays flagged.
Current focus is refinement and hardening ahead of mainnet. Active development visible on GitHub — consensus protection, security handling.
---
Marketing: there is no strategy
Naveen, asked directly: right now there is no marketing strategy, by design.
No head of marketing, no KOL campaigns. The bet is on organic, decentralised community momentum.
Proof cited: Tari press coverage in a Korean economic newspaper, zero involvement from Labs or Council.
---
On Council members and reach
A community member asked why a Council member with 1.5M followers hasn't tweeted about Tari.
Naveen: they were brought in for their skill set in communication and narrative, not their follower count. No pressure is being applied to post.
---
Other bits
Meowmancer built an open-source GPU miner. Contributors are evaluating swapping it in for LOL Miner, which carries a dev fee.
Bridge transaction issues appear fixed — Brian worked on it.
blackwolfsa doing security hardening on Tari core. Two CVEs fixed, details held back.
---
Want a bounty? Open an issue.
Contributors flagged the core problem: by the time a bounty is well-defined, someone's usually solved it already.
Best thing you can do is open new issues and feature requests. That's what creates bounties.
Full show on the Tari Community YouTube.
The Tari Show (July 28, 2026)
Fox hosted while Naveen was traveling.
🛡 L1 security
- webhop123 earned 60,000 XTM for fixing the stealth fee-claim bug.
- A Bulletproofs Plus bug made batch verification check only the first 250 proofs. It is fixed and deployed.
- SW's security work added request limits and fixed an idle-timeout DoS risk.
🌉 Bridge
- The bridge returned after a 24-hour queuing-bug outage. The team also addressed duplicate transactions.
⛏ Mining and upgrades
- The difficulty RFC now better explains the duplicate-block penalty.
- A six-month upgrade cadence was proposed to simplify protocol changes and exchange coordination.
🏛 Governance
- Fox revised the Core Contributor Program TIP. Comments have slowed and consensus appears to be converging.
💰 Unclaimed airdrop
- OKz's community poll is closing soon: burn the estimated 400M unclaimed coins or fund rewards and projects.
- The coins are in the genesis allocation. A burn is permanent; tail emission would not recreate it.
- Since the coins are locked and off-market, burning may have little immediate price effect. Any spending needs a public budget.
- The newly inducted Tari council has not yet assembled a budget but expects to soon.
🌐 Community
- The website redesign is close to merge; Discussion of long-term CMS changes is shelved for now, but may return later.
- GSXRspartan's cross-chain swap platform needs a swap-model decision.
Fox hosted while Naveen was traveling.
🛡 L1 security
- webhop123 earned 60,000 XTM for fixing the stealth fee-claim bug.
- A Bulletproofs Plus bug made batch verification check only the first 250 proofs. It is fixed and deployed.
- SW's security work added request limits and fixed an idle-timeout DoS risk.
🌉 Bridge
- The bridge returned after a 24-hour queuing-bug outage. The team also addressed duplicate transactions.
⛏ Mining and upgrades
- The difficulty RFC now better explains the duplicate-block penalty.
- A six-month upgrade cadence was proposed to simplify protocol changes and exchange coordination.
🏛 Governance
- Fox revised the Core Contributor Program TIP. Comments have slowed and consensus appears to be converging.
💰 Unclaimed airdrop
- OKz's community poll is closing soon: burn the estimated 400M unclaimed coins or fund rewards and projects.
- The coins are in the genesis allocation. A burn is permanent; tail emission would not recreate it.
- Since the coins are locked and off-market, burning may have little immediate price effect. Any spending needs a public budget.
- The newly inducted Tari council has not yet assembled a budget but expects to soon.
🌐 Community
- The website redesign is close to merge; Discussion of long-term CMS changes is shelved for now, but may return later.
- GSXRspartan's cross-chain swap platform needs a swap-model decision.
Tari Show recap —04/08/26 🐢
Big one: Naveen shared preliminary numbers on the unclaimed airdrop, and the full accounting lands with the Council this week.
Recap below.
---
The unclaimed airdrop numbers
Naveen gave high-level figures for the first time:
Community allocation is ~1B tokens. ~700M was earmarked for the airdrop. They estimate ~50% gets claimed, so roughly 350M claimed, leaving ~700M in the community bucket.
Not final. Full accounting comes this week.
---
Where the Council stands
Per the charter, control of the community tokens sits with the Council. Their call.
Naveen's honest take: skeptical that burns move the needle, having not seen it work elsewhere. Same skepticism on straight redistribution to holders. His framing: the real problem is tent size, not token count. Grow the community, price follows.
---
The process from here
Tari Labs commits to giving the Council the full accounting this week. Then the Council brainstorms and comes back to the community with options.
Fox: hard to decide anything without the numbers. Accounting first, decisions after. Both stressed transparency, "sunlight dispels rumors."
---
The unclaimed airdrop proposal
The community proposal on the unclaimed tokens was flagged as the most active thread on the forum. Naveen credited it for opening the conversation.
Next step is the audit, then Council discussion.
---
Other updates
Core Contributor program is basically ready, just needs the Council vote. Brian signed off on the changes.
Ootle still shipping this year, no change.
Dev activity slower right now, contributors on summer break, back mid next week.
Naveen teased game design work happening quietly with Council members.
Design standards to be open-sourced for the community.
---
Full show on the Tari Community YouTube.
Big one: Naveen shared preliminary numbers on the unclaimed airdrop, and the full accounting lands with the Council this week.
Recap below.
---
The unclaimed airdrop numbers
Naveen gave high-level figures for the first time:
Community allocation is ~1B tokens. ~700M was earmarked for the airdrop. They estimate ~50% gets claimed, so roughly 350M claimed, leaving ~700M in the community bucket.
Not final. Full accounting comes this week.
---
Where the Council stands
Per the charter, control of the community tokens sits with the Council. Their call.
Naveen's honest take: skeptical that burns move the needle, having not seen it work elsewhere. Same skepticism on straight redistribution to holders. His framing: the real problem is tent size, not token count. Grow the community, price follows.
---
The process from here
Tari Labs commits to giving the Council the full accounting this week. Then the Council brainstorms and comes back to the community with options.
Fox: hard to decide anything without the numbers. Accounting first, decisions after. Both stressed transparency, "sunlight dispels rumors."
---
The unclaimed airdrop proposal
The community proposal on the unclaimed tokens was flagged as the most active thread on the forum. Naveen credited it for opening the conversation.
Next step is the audit, then Council discussion.
---
Other updates
Core Contributor program is basically ready, just needs the Council vote. Brian signed off on the changes.
Ootle still shipping this year, no change.
Dev activity slower right now, contributors on summer break, back mid next week.
Naveen teased game design work happening quietly with Council members.
Design standards to be open-sourced for the community.
---
Full show on the Tari Community YouTube.
The Tari Show (August 11, 2026)
🔧 Ootle
- sdbondi is back with seven PRs, most of them hardening the stealth transfer system, including a fix for a bug that could authorize a transfer against the wrong key.
- A community member flagged a possible anonymity edge case in fee selection, tracing back to kinkajou's earlier stealth fee work. Still under review.
- Naveen spoke to the Ootle launch timeline and committed to keeping the community updated as it firms up.
🛡️ L1
- kamexETH earned 15,000 XTM for closing a peer-address filtering bug (S tier).
🏛️ Governance
- Seven nominees are in for the Core Contributor Program's first cohort: Fox and SW for Code CC, sprucetree and animalst also for Code CC, kinkajou for Project CC, ZhaoXi for Community CC, and Naveen for Product CC. Impala for Infrastructure CC. Votes still coming in.
- Fox walked through the program's structure, pointing to Open edX's Core Contributor model (OEP-54) as precedent.
- joseph raised whether Council members should also hold CC status, arguing an affirmative-support threshold and a veto mechanism solve two different problems. Still being weighed, not settled.
- Fox confirmed the Council has received an audit of the community tokens and the airdrop, and plans to post the results publicly this evening.
- GSXRspartan's private governance voting tool has a working GUI, close to multi-computer testing. kinkajou is building a second one. Early days on both.
- Kelketek and kinkajou (posting as m4r1m0 on GitHub) were both recognized for volunteer community work done ahead of the Council's founding, covering policy recommendations, moderation, and general support (L tier, 150,000 XTM total).
🖥️ Universe
- samrusani fixed a display bug in the wallet sync countdown, got a shoutout on the call.
🌐 Community
- luci666 proposed putting all of Tari's sub-sites on one shared platform, Jekyll, for design consistency and stronger SEO.
- The SEO/AEO work already proposed is stuck until the Core Contributor process is finalized.
- Marguerite joined the discussion on anonymous project design and web-of-trust models, with some added thoughts on the gaming market.
🔧 Ootle
- sdbondi is back with seven PRs, most of them hardening the stealth transfer system, including a fix for a bug that could authorize a transfer against the wrong key.
- A community member flagged a possible anonymity edge case in fee selection, tracing back to kinkajou's earlier stealth fee work. Still under review.
- Naveen spoke to the Ootle launch timeline and committed to keeping the community updated as it firms up.
🛡️ L1
- kamexETH earned 15,000 XTM for closing a peer-address filtering bug (S tier).
🏛️ Governance
- Seven nominees are in for the Core Contributor Program's first cohort: Fox and SW for Code CC, sprucetree and animalst also for Code CC, kinkajou for Project CC, ZhaoXi for Community CC, and Naveen for Product CC. Impala for Infrastructure CC. Votes still coming in.
- Fox walked through the program's structure, pointing to Open edX's Core Contributor model (OEP-54) as precedent.
- joseph raised whether Council members should also hold CC status, arguing an affirmative-support threshold and a veto mechanism solve two different problems. Still being weighed, not settled.
- Fox confirmed the Council has received an audit of the community tokens and the airdrop, and plans to post the results publicly this evening.
- GSXRspartan's private governance voting tool has a working GUI, close to multi-computer testing. kinkajou is building a second one. Early days on both.
- Kelketek and kinkajou (posting as m4r1m0 on GitHub) were both recognized for volunteer community work done ahead of the Council's founding, covering policy recommendations, moderation, and general support (L tier, 150,000 XTM total).
🖥️ Universe
- samrusani fixed a display bug in the wallet sync countdown, got a shoutout on the call.
🌐 Community
- luci666 proposed putting all of Tari's sub-sites on one shared platform, Jekyll, for design consistency and stronger SEO.
- The SEO/AEO work already proposed is stuck until the Core Contributor process is finalized.
- Marguerite joined the discussion on anonymous project design and web-of-trust models, with some added thoughts on the gaming market.
The Tari Show (August 18, 2026)
Naveen was out sick this week. Fox hosted and took questions from chat.
🏛 Governance
- Core Contributor voting is closing. Fox expects the full initial cohort to be inducted, likely Thursday, once the window closes in case of a late no vote.
- The Council has moved off a single Telegram chat onto a Council-only section of the forum, for flagging items, voting, and reporting back. Planning discussions still happen in the open.
- The Council meets Thursday to work through the budget. The burn proposal is under review in the new section.
- The charter calls for staggered elections, but the first Council was all seated at once. Options are assigning some members six-month terms or running an intermediate election. It goes to the Core Contributors. Next election is roughly 11 months out.
- Council rewards are capped by the charter. Fox wants the XTM figure to come down as the price rises, so the reward stays at its intended level rather than growing with it.
- No Council KPIs. Fox compared it to a company board.
- On a Council satisfaction poll: anyone can run one on the forum, and it would sit better with a Project CC than a Council member.
- Fox's focus for the next three months is process: who has access to what, how access gets granted, who needs consulting on which proposals, and keeping a consistent line open to marketplaces and miners. The aim is people acting without first hunting down a gatekeeper.
🔧 Ootle
- 20 PRs merged into L2 in a single week.
- No launch date yet. Fox hopes the Council can discuss timing soon.
- Validator requirements came up from chat and are still an open question.
🛡 L1
- SW is working on making sure people are rewarded for reporting security vulnerabilities. Report via the vulnerability reporting link on the L1 repo, or the security advisories path on tari-ootle for L2.
🌐 Community
- Okz released Caravel, private messaging with private transfers built on the Ootle. Posted in the forums and worth a try.
- Cross-posting is now live across X, Bluesky, and Mastodon, running on Postybirb. Shoutout to kinkajou for pushing it through and chasing down the access to make it work. Bluesky: @tariproject.bsky.social
- Terence started a directory of community apps running on Ootle testnet, also on the forum.
- A proposal is circulating to sponsor fee refunds for community market makers, which would make buying and selling XTM easier. The Council will discuss it.
🛠 Website
- The code merged, but the deployment pipeline failed and did not push it live. Fox tracked down who can repair it and they have been notified. Navigation update to follow.
📣 Other
- Naveen spoke to Cake, and Vic has agreed to look into the Tari PR.
Naveen was out sick this week. Fox hosted and took questions from chat.
🏛 Governance
- Core Contributor voting is closing. Fox expects the full initial cohort to be inducted, likely Thursday, once the window closes in case of a late no vote.
- The Council has moved off a single Telegram chat onto a Council-only section of the forum, for flagging items, voting, and reporting back. Planning discussions still happen in the open.
- The Council meets Thursday to work through the budget. The burn proposal is under review in the new section.
- The charter calls for staggered elections, but the first Council was all seated at once. Options are assigning some members six-month terms or running an intermediate election. It goes to the Core Contributors. Next election is roughly 11 months out.
- Council rewards are capped by the charter. Fox wants the XTM figure to come down as the price rises, so the reward stays at its intended level rather than growing with it.
- No Council KPIs. Fox compared it to a company board.
- On a Council satisfaction poll: anyone can run one on the forum, and it would sit better with a Project CC than a Council member.
- Fox's focus for the next three months is process: who has access to what, how access gets granted, who needs consulting on which proposals, and keeping a consistent line open to marketplaces and miners. The aim is people acting without first hunting down a gatekeeper.
🔧 Ootle
- 20 PRs merged into L2 in a single week.
- No launch date yet. Fox hopes the Council can discuss timing soon.
- Validator requirements came up from chat and are still an open question.
🛡 L1
- SW is working on making sure people are rewarded for reporting security vulnerabilities. Report via the vulnerability reporting link on the L1 repo, or the security advisories path on tari-ootle for L2.
🌐 Community
- Okz released Caravel, private messaging with private transfers built on the Ootle. Posted in the forums and worth a try.
- Cross-posting is now live across X, Bluesky, and Mastodon, running on Postybirb. Shoutout to kinkajou for pushing it through and chasing down the access to make it work. Bluesky: @tariproject.bsky.social
- Terence started a directory of community apps running on Ootle testnet, also on the forum.
- A proposal is circulating to sponsor fee refunds for community market makers, which would make buying and selling XTM easier. The Council will discuss it.
🛠 Website
- The code merged, but the deployment pipeline failed and did not push it live. Fox tracked down who can repair it and they have been notified. Navigation update to follow.
📣 Other
- Naveen spoke to Cake, and Vic has agreed to look into the Tari PR.
The Tari Show (August 25, 2026)
🏛 Governance
- Several Core Contributors are confirmed, and Fox is nearly done onboarding them.
- ZhaoXi nominated two more from the Chinese community.
- No answer yet on the airdrop remainder. The council probably won't go with the proposal as written; an alternative is in progress.
🔧 Ootle
- There was a testnet reset. If your builds stopped working, republish your templates and update your wallets.
- Template publishing got cheaper.
- hraxu built an L2 block explorer and it's live.
🚀 Launch
- Still expected before the end of the year. Fox proposed a date to the council and got no pushback, but isn't revealing it yet.
- The Ootle is mostly ready. What's needed now is testnet traffic and real usage.
- Contests are planned ahead of launch, with prizes from community tokens. Everything built moves to mainnet on launch day.
🛡 Security
- CCs are using retro bounties reward vulnerabilities already found and fixed. Not open work.
- HackerOne is retired. Report vulnerabilities through GitHub's private advisory panel.
🖥 Universe
- The new wallet is close. It's a full rewrite and should clear out many long-standing bugs.
- The Active Miners figure is static and inaccurate. It'll be retired or rebuilt.
⛏ L1
- SW's difficulty changes are in a feature branch. The block window change to 45 ships first.
- Esmeralda has too little hash rate to test properly. kinkajou is working on simulating real mining.
🔌 Universe as an App Gateway
- Plats proposed Universe as the one connection an agent needs to find Tari apps and spend from your wallet.
- Brian: possible, but plugins need a permissioned API first. Universe is open source, PRs welcome.
📣 Distribution
- Branded traffic has grown steadily since September 2025. Top sources citing Tari: fandom.com, youtube.com, reddit.com.
🐢 Brand
- No decision on dropping the turtle. The Ootle has no brand of its own; Fox invited branding ideas on the forums.
🏛 Governance
- Several Core Contributors are confirmed, and Fox is nearly done onboarding them.
- ZhaoXi nominated two more from the Chinese community.
- No answer yet on the airdrop remainder. The council probably won't go with the proposal as written; an alternative is in progress.
🔧 Ootle
- There was a testnet reset. If your builds stopped working, republish your templates and update your wallets.
- Template publishing got cheaper.
- hraxu built an L2 block explorer and it's live.
🚀 Launch
- Still expected before the end of the year. Fox proposed a date to the council and got no pushback, but isn't revealing it yet.
- The Ootle is mostly ready. What's needed now is testnet traffic and real usage.
- Contests are planned ahead of launch, with prizes from community tokens. Everything built moves to mainnet on launch day.
🛡 Security
- CCs are using retro bounties reward vulnerabilities already found and fixed. Not open work.
- HackerOne is retired. Report vulnerabilities through GitHub's private advisory panel.
🖥 Universe
- The new wallet is close. It's a full rewrite and should clear out many long-standing bugs.
- The Active Miners figure is static and inaccurate. It'll be retired or rebuilt.
⛏ L1
- SW's difficulty changes are in a feature branch. The block window change to 45 ships first.
- Esmeralda has too little hash rate to test properly. kinkajou is working on simulating real mining.
🔌 Universe as an App Gateway
- Plats proposed Universe as the one connection an agent needs to find Tari apps and spend from your wallet.
- Brian: possible, but plugins need a permissioned API first. Universe is open source, PRs welcome.
📣 Distribution
- Branded traffic has grown steadily since September 2025. Top sources citing Tari: fandom.com, youtube.com, reddit.com.
🐢 Brand
- No decision on dropping the turtle. The Ootle has no brand of its own; Fox invited branding ideas on the forums.
The Tari Show (September 1, 2026)
🚀 The Ootle Launches November 11
- Fox announced the date. Launch is phased: the Council and Tari Labs run the validators at first, then applications open to trusted community members, then to anyone meeting the requirements.
- Requirements aren't set yet. They depend on what phase one shows.
🏆 Contests
- kinkajou proposed five months of launch contests using 9,000,000 XTM from the community bucket, with a 1,000,000 XTM top prize on four. Poll is open on the forum, go vote.
- The first runs through September. Fox posts the rules on the forum today.
🔧 Ootle
- v0.39.3 shipped last Thursday. Validators and indexers upgrade together.
- Stan improved state sync and validator sync, fixed how indexers treat recently spent coins, and raised the compute ceiling so contracts can finish.
- What helps most now is people on testnet, breaking things.
⛏ L1
- SW has been improving node connections, malformed transaction handling, sync, and L1's interop with the L2.
🎨 Branding
- GSXRspartan asked what independent projects can do with Tari branding. Guidelines exist but were never published. Being fixed.
- Blake's thread on retiring the Soon turtle became a push to evolve it instead. Okz, 0xhra, Joseph, ApplewithWirms and Terence each pledged 100,000 XTM toward a reskin bounty. Ten pledges takes it public. Dirc posted concept art.
🌐 Community
- norman2 has a DAO prototype running on the Ootle, and found and fixed a real bug on the way.
- Okz approached the ThorChain team about XTM. Real opportunity, significant work, so the Council will look at it.
- dablacksplash shared a combined GPU and CPU merge miner for Tari and Monero, and wants testers.
- Terence added universe.tari.mw to the Ootle apps directory: a community-built L1 web wallet by Erebus Labs that also opens into the Ootle. Not the desktop app.
🖥 Universe
- A new underlying wallet is coming that should clear up many connectivity problems.
🚀 The Ootle Launches November 11
- Fox announced the date. Launch is phased: the Council and Tari Labs run the validators at first, then applications open to trusted community members, then to anyone meeting the requirements.
- Requirements aren't set yet. They depend on what phase one shows.
🏆 Contests
- kinkajou proposed five months of launch contests using 9,000,000 XTM from the community bucket, with a 1,000,000 XTM top prize on four. Poll is open on the forum, go vote.
- The first runs through September. Fox posts the rules on the forum today.
🔧 Ootle
- v0.39.3 shipped last Thursday. Validators and indexers upgrade together.
- Stan improved state sync and validator sync, fixed how indexers treat recently spent coins, and raised the compute ceiling so contracts can finish.
- What helps most now is people on testnet, breaking things.
⛏ L1
- SW has been improving node connections, malformed transaction handling, sync, and L1's interop with the L2.
🎨 Branding
- GSXRspartan asked what independent projects can do with Tari branding. Guidelines exist but were never published. Being fixed.
- Blake's thread on retiring the Soon turtle became a push to evolve it instead. Okz, 0xhra, Joseph, ApplewithWirms and Terence each pledged 100,000 XTM toward a reskin bounty. Ten pledges takes it public. Dirc posted concept art.
🌐 Community
- norman2 has a DAO prototype running on the Ootle, and found and fixed a real bug on the way.
- Okz approached the ThorChain team about XTM. Real opportunity, significant work, so the Council will look at it.
- dablacksplash shared a combined GPU and CPU merge miner for Tari and Monero, and wants testers.
- Terence added universe.tari.mw to the Ootle apps directory: a community-built L1 web wallet by Erebus Labs that also opens into the Ootle. Not the desktop app.
🖥 Universe
- A new underlying wallet is coming that should clear up many connectivity problems.
Tari Show (September 8th) - Key Takeaways
- The Ootle (Tari L2) testnet v0.40.4 was released last week, and Stan is working on optimizations and indexer improvements.
- The hardware specifications for validator nodes have not yet been released; this will be addressed once the first nodes are running.
- Ootle Mainnet Launch Date: November 11th
- Launch Goals: To make Tari highly programmable, allowing users to build their own applications and issue tokens, with adjustable token privacy.
- Turbine Model: A portion of Ootle transaction fees will be burned.
- Validator Node Deployment: Will be rolled out in three phases: first, centralized nodes managed by the team; then, invitations to trusted community members; and finally, public availability. The duration of each phase is yet to be determined.
- It is not expected that stablecoins will be launched simultaneously with the mainnet.
- Tari is a dual-layer network: L1 is a default, private Proof-of-Work chain; L2 (Ootle) is a highly programmable smart contract layer with adjustable privacy.
- The project is led by the Tari Council and the community.
- Council members Fox, King Kaju, Margarite, and Solex are organizing the preparations for the launch.
- OKZ is running a Twitter campaign to collect Ootle use cases, with a prize of 50,000 XTM (a community-driven initiative).
- The official September forum development competition is underway, with a deadline at the end of the month, and submissions are being received.
- A bounty for an open-source price bot was completed within a day.
- Noise Noise has created Tarorg: a DAO/treasury tool that runs on Ootle (with a Web UI and CLI). They describe it as a "toy" but it is already end-to-end functional.
- Some users have reported that the Ootle documentation is insufficient and suggest linking it to RFCs. The code is open-source, and AI can also be used to generate documentation.
- Bounty payments are delayed by approximately one week (due to plagiarism issues and complex revenue sharing).
- YATS still plans to migrate its "source of truth" to Ootle to achieve decentralization; details on how this will work will be released after the launch.
- Ledger support is available, but requires sideloading; it was developed by core contributor SV.
- The host will be speaking with Vic from Cake Wallet tomorrow to discuss the progress of the integration.
- The host emphasized the necessity of default privacy for both individuals and AI agents, and expressed disapproval of traditional, hype-driven marketing in the crypto space.
- The next episode of the show will air next week.
- The Ootle (Tari L2) testnet v0.40.4 was released last week, and Stan is working on optimizations and indexer improvements.
- The hardware specifications for validator nodes have not yet been released; this will be addressed once the first nodes are running.
- Ootle Mainnet Launch Date: November 11th
- Launch Goals: To make Tari highly programmable, allowing users to build their own applications and issue tokens, with adjustable token privacy.
- Turbine Model: A portion of Ootle transaction fees will be burned.
- Validator Node Deployment: Will be rolled out in three phases: first, centralized nodes managed by the team; then, invitations to trusted community members; and finally, public availability. The duration of each phase is yet to be determined.
- It is not expected that stablecoins will be launched simultaneously with the mainnet.
- Tari is a dual-layer network: L1 is a default, private Proof-of-Work chain; L2 (Ootle) is a highly programmable smart contract layer with adjustable privacy.
- The project is led by the Tari Council and the community.
- Council members Fox, King Kaju, Margarite, and Solex are organizing the preparations for the launch.
- OKZ is running a Twitter campaign to collect Ootle use cases, with a prize of 50,000 XTM (a community-driven initiative).
- The official September forum development competition is underway, with a deadline at the end of the month, and submissions are being received.
- A bounty for an open-source price bot was completed within a day.
- Noise Noise has created Tarorg: a DAO/treasury tool that runs on Ootle (with a Web UI and CLI). They describe it as a "toy" but it is already end-to-end functional.
- Some users have reported that the Ootle documentation is insufficient and suggest linking it to RFCs. The code is open-source, and AI can also be used to generate documentation.
- Bounty payments are delayed by approximately one week (due to plagiarism issues and complex revenue sharing).
- YATS still plans to migrate its "source of truth" to Ootle to achieve decentralization; details on how this will work will be released after the launch.
- Ledger support is available, but requires sideloading; it was developed by core contributor SV.
- The host will be speaking with Vic from Cake Wallet tomorrow to discuss the progress of the integration.
- The host emphasized the necessity of default privacy for both individuals and AI agents, and expressed disapproval of traditional, hype-driven marketing in the crypto space.
- The next episode of the show will air next week.
The Tari Show (September 15, 2026)
🏛 Governance
- Terence and Yushan Ren are onboarded as Core Contributors. One more and the CCs form an independent voting body.
🔧 Ootle
- Stan merged a security sweep: attacker-reachable panics gone, templates validated before they run, contracts can't touch each other's assets.
- Node eviction removed. A validator that goes quiet is no longer punished as malicious.
- Provisional validator hardware: 4 to 8 cores, 8 to 16 GB RAM, SSD, 5 Mbps symmetric minimum, 25 recommended.
- 0xhra asked for a decentralisation timeline. There isn't one yet. Initial validators are Council and core contributors; it opens up as real-world behaviour is measured. The code is open, so review it, build on it, file issues.
- Tari Labs will burn all fees from its launch validator.
⛏ L1
- SW is improving the Ledger wallet and working through community security reports.
- Bridge: secure, reliability work under way. Limits protect users; the goals are to remove them and decentralise the bridge.
🖥 Universe
- Balance zero after "Refresh Wallet History" in 1.6.12? Expected. It deletes the wallet and rescans from birthday. Wait it out.
🐢 Naming
- The Ootle token is TARI, not XTR: new people should only have to remember one name. Docs and data-site listings still need normalising.
🌐 Community
- luci666 built a trial docs site, wants feedback. GSXRspartan shared Private Ballot, a private voting tool.
- ThorChain: Fox reviewed the code required and it's massive. Smaller DEXs first.
- Clayton is onboarding around 100 new wallets this week and writing an Apple Pay to wXTM guide.
- Exchanges: conversations are happening, one meeting tomorrow, no promises. No protocol or privacy changes for any listing.
📣 Marketing
- Marguerite met Naveen in Nashville. A pre-launch campaign proposal goes to the Council, community kept informed as it develops.
🏆 RTeamProject earned a 150,000 XTM retro reward for the RWA token JWT fix.
🏛 Governance
- Terence and Yushan Ren are onboarded as Core Contributors. One more and the CCs form an independent voting body.
🔧 Ootle
- Stan merged a security sweep: attacker-reachable panics gone, templates validated before they run, contracts can't touch each other's assets.
- Node eviction removed. A validator that goes quiet is no longer punished as malicious.
- Provisional validator hardware: 4 to 8 cores, 8 to 16 GB RAM, SSD, 5 Mbps symmetric minimum, 25 recommended.
- 0xhra asked for a decentralisation timeline. There isn't one yet. Initial validators are Council and core contributors; it opens up as real-world behaviour is measured. The code is open, so review it, build on it, file issues.
- Tari Labs will burn all fees from its launch validator.
⛏ L1
- SW is improving the Ledger wallet and working through community security reports.
- Bridge: secure, reliability work under way. Limits protect users; the goals are to remove them and decentralise the bridge.
🖥 Universe
- Balance zero after "Refresh Wallet History" in 1.6.12? Expected. It deletes the wallet and rescans from birthday. Wait it out.
🐢 Naming
- The Ootle token is TARI, not XTR: new people should only have to remember one name. Docs and data-site listings still need normalising.
🌐 Community
- luci666 built a trial docs site, wants feedback. GSXRspartan shared Private Ballot, a private voting tool.
- ThorChain: Fox reviewed the code required and it's massive. Smaller DEXs first.
- Clayton is onboarding around 100 new wallets this week and writing an Apple Pay to wXTM guide.
- Exchanges: conversations are happening, one meeting tomorrow, no promises. No protocol or privacy changes for any listing.
📣 Marketing
- Marguerite met Naveen in Nashville. A pre-launch campaign proposal goes to the Council, community kept informed as it develops.
🏆 RTeamProject earned a 150,000 XTM retro reward for the RWA token JWT fix.