Brought to you by Identity Woman and Infominer.
Support this collaboration on Patreon!!!
Erik Torenberg is joined by a16z General Partner Alex Rampell and Affirm Co-Founder and CEO Max Levchin for a conversation on 25 years of fintech, from the early days of digital payments to the origins of Affirm and the next generation of agentic commerce.
Max and Alex revisit what surprised them most about how payments evolved, why the card interface has been so difficult to displace, and why even the smallest corners of payments can become enormous markets. They also trace the early idea maze behind Affirm, from "pay with your identity" and the pajama problem to the realization that installment financing could dramatically increase merchant conversion.
The conversation also gets into real versus "fake" 0% financing, what people misunderstand about Affirm today, why negative customer acquisition cost can be such a powerful business model advantage, and why Max is more bullish on agentic payments than on agents choosing what people buy.
Resources:
Follow Max Levchin on X: https://x.com/mlevchin
Follow Alex Rampell on X: https://x.com/arampell
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Last month, more than 700 engineers and technical leads from companies like Apple, AWS, Google, NVIDIA, Microsoft, OpenAI, Salesforce, and Snowflake registered for a hackathon hosted by popular AI newsletter AlphaSignal. On August 6, 2026 more than 100 of these devs appeared in person in San Francisco to hack on a deceptively simple challenge: in 90 minutes, with no pre-built code allowed, write an AI agent that can order and deliver a pizza to 3 Embarcadero Center. First pizza delivered wins, with $2,500 in total prize money at stake.
It’s a fun premise. But underlying this novelty, the challenge is a good stress test for a much bigger question in AI development: How do you get an autonomous agent to reliably act in the real world, where the information it needs—what’s open, what’s nearby, what’s actually deliverable—isn’t in its training data and changes by the hour?
Of their own accord, two of the winners (Preston Kwei and Rohan Gandotra) leveraged the Brave Search API to solve the same underlying problem: How to ground their agent in accurate, real-time information about the outside world, when that data falls outside their training corpus. Interestingly, each winner took a different approach, which is a useful illustration of how flexible Brave Search API can be as a grounding layer.
Real-time discovery, then actionPreston used the Brave Search API as a live restaurant-discovery layer, letting his agent identify nearby pizza options in real time rather than relying on stale or hardcoded data (a task aided by Brave’s Place Search API). From there, the agent completed the actual order through the Brave browser on DoorDash, pairing real-time search with real-time action in a single pipeline.
Structured, ranked data for agent decision-makingRohan took a more deterministic approach to the same problem: which restaurants even exist near here, and which one should the agent pick? He used the Brave Search API to pull nearby pizza spots by address, programmatically scored them by distance, and fed that ranked list back to his agent as clean, structured input. This meant no scraping and no manual parsing, just usable data ready for the agent’s decision logic.
Brave Search API is built for just this kind of challengeBoth Preston’s and Rohan’s approaches map directly onto why developers reach for the Brave Search API when building agents. An agent is only as good as the information it can act on, and static training data can’t tell you which pizza place near the Embarcadero is currently taking orders. That’s the same core problem developers face at larger scales:
Chatbots that need to ground answers in current events Research agents that need fresh market data Any AI system that needs a live, verifiable window into the Web rather than a frozen snapshot of itWhether the goal is answering a question without hallucinating or fetching a ranked list of nearby businesses in real time, the pattern is the same: pull accurate, current, structured data from an independent Web index, and hand it to the agent in a form it can immediately use.
AlphaSignal’s hackathon is a small, playful example that points to a much larger shift already underway: AI agents are moving from answering questions to taking actions, and that shift depends entirely on giving those agents reliable, real-time access to the open Web. A hackathon built around ordering a pizza turned out to be a relevant proxy for the same challenges developers are solving in legal research, market intelligence, fraud detection, and more. It was just compressed into 90 minutes and a countdown clock.
Congratulations to Preston, Rohan, and Elliot S. for winning the night, and thanks to AlphaSignal for bringing the AI community together to find real-world utility for their agents.
Readers’ note: Several members of the Brave team, including Desktop Product Manager Rafael Ebron, Staff Engineer Anton Lazarev, and VP of Privacy & Security Shivan Sahib, attended to observe and answer technical questions, but winners were judged solely on how quickly their agent got a pizza delivered, and whether it was built live during the event. Brave’s attendance had no bearing on the outcome.
a16z General Partner Jorge Conde sits down with Moderna CEO Stéphane Bancel to discuss a major milestone for mRNA technology: positive Phase 3 results from Moderna and Merck’s individualized treatment for melanoma, after more than a decade of work on personalized cancer vaccines.
Stéphane explains how the treatment works by sequencing an individual patient’s tumor and healthy cells, identifying the mutations most relevant to their cancer, and encoding up to 34 of them into an mRNA designed specifically for that patient. Rather than simply unleashing the immune system, the goal is to teach it exactly what to recognize and attack.
They also unpack the engineering challenge of manufacturing a different medicine for every patient, how Moderna has brought the process down to roughly 42 days from biopsy to treatment, and what it would take to manufacture personalized medicines at scale. Finally, Stéphane looks beyond melanoma to lung, kidney, bladder, pancreatic, and gastric cancers, as well as Moderna’s longer-term work applying mRNA to rare genetic and autoimmune diseases.
Resources:
Follow Stéphane Bancel on LinkedIn: https://www.linkedin.com/in/st%C3%A9phane-bancel-8185251/
Follow Jorge Conde on X: https://x.com/JorgeCondeBio
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
This post is part of an ongoing series evaluating Brave’s performance. It describes work done by Soumyajit Chatterjee (Systems and Performance Researcher), Kleomenis Katevas (Principal Machine Learning Researcher), Artem Chaikin (Staff Security Engineer), Pete Snyder (Principal Privacy Researcher), and Hamed Haddadi (Chief Scientist, Visiting Professor).
We recently ran new benchmarks comparing Brave against the three most widely used desktop browsers: Chrome, Edge, and Firefox. We found that Brave for desktop is faster, uses less energy, consumes less CPU and memory, and transfers less data. Specifically, across all tested browsers Brave:
Uses on average 44% less CPU Uses on average 10% less energy Uses on average 28% less memory Loads pages 20% faster Transfers 26% less inbound data Transfers 39% less outbound dataThese results closely resemble our 2025 tests showing that Brave for Android outperforms other mobile browsers in page-load speed, battery consumption, CPU usage, and network use. As with Android benchmarks, we attribute our wins on the desktop benchmarks to Brave’s built-in privacy and security features, namely its adblocking and tracker blocking. These eliminate unnecessary network requests and reduce processing overhead during browsing.
Testing environment: hardware and softwareThis desktop testing was conducted on an Apple Mac Mini with an Apple M2 chip and 8 GB of unified memory, running macOS 26.5.1 (25F80).
The following browser versions, which were the latest available at the time of testing, were used:
Browser Version Brave 1.92.139 (Chromium 150.0.7871.114, arm64) Chrome 150.0.7871.184 (arm64) Edge 150.0.4078.83 (arm64) Firefox (Playwright Gecko) 146.0.1 (64-bit)All tests were conducted on a dedicated 50Mbps internet connection in London, UK.
Methodology WorkloadWe tested the 50 most popular websites as ranked by Brave Search statistics, loading each landing page. Each experiment was repeated 10 times, with the order of browsers randomized across runs. This counterbalances order effects so that no single browser systematically benefits or suffers from its position in the sequence.
For each browser, we created a clean baseline user data directory with default settings. Before every test run, we copied this baseline into a fresh, isolated temporary directory, ensuring that no cached data, cookies, or persistent state from previous runs influenced the results. We then launched the browser against this isolated profile and waited 60 seconds for background processes to stabilize before beginning measurements.
Desktop benchmarkingTo evaluate browser performance on macOS, we used a locally-hosted Apple Mac Mini. Brave’s browser automation was handled using a tool developed using the Playwright framework (v1.58.2), which provides a cross-browser API for automating and instrumenting a wide range of browser behaviors in a consistent and reproducible way. These behaviors include network requests, page lifecycle events, and worker script activity.
For each browser configuration, a clean browser profile was prepared, followed by a 60-second stabilization period. The browser then visited each URL in the measurement list. Each loaded page remained open for 30 seconds before the browser window was closed, after which the next URL was loaded.
For page loading time, we measured the time from navigation start to the loadEventEnd event, using injected JavaScript via Playwright instrumentation.
Energy consumption on macOS was estimated by integrating instantaneous system power obtained from powermetrics at a 350ms sampling interval. Results are reported in milliwatt-hours (mWh).
CPU utilization was measured using process-level statistics from ps, aggregated across all browser-related processes (main, renderer, GPU, utility, etc.) to capture total CPU load attributable to the browser. Memory was measured as the resident set size (RSS) aggregated across browser processes, also via ps. Network usage was measured using Playwright’s page-scoped instrumentation, which records requests and responses attributable specifically to each loaded page (allowing us to accurately isolate per-page network activity from background browser processes), and compute aggregated transmitted/received bytes including headers and payloads.
Our performance evaluation focuses on the following attributes:
Energy consumption: Total energy required to load and render each webpage (mWh) CPU utilization: Processor load during page loading and rendering Memory usage: Memory footprint associated with each page execution Page load speed: Time from navigation start toloadEventEnd and the LCP render time
Network data consumed: Total inbound data (response) and outbound data (request) per browsing session
Resource usage
Energy
Figure 1 shows the distribution of energy consumption (mWh) per page load across the four browsers. Brave is the most energy-efficient browser tested, with an average consumption of approximately 31.1 mWh. This is 4% lower than Chrome’s average (~32.5 mWh), 12% lower than Edge’s average (~35.3 mWh), and 14% lower than Firefox’s average (~36.1 mWh). Additionally, Brave exhibits a notably tighter distribution (smaller interquartile range and shorter whiskers) compared to the others, indicating more consistent energy behavior across different websites and less variability in power draw during page loads.
The gap between Brave and two of the other baseline browsers (Edge and Firefox), is particularly striking. Both consume meaningfully more energy per page load on average, with Firefox showing the widest spread in its distribution. Such a wide spread suggests higher variability in how efficiently the browser can process different page types.
Figure 1: Box plots of energy consumption (mWh) per page load across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better. CPUThe CPU utilization results, shown in Figure 2, tell an even more pronounced story. Brave records a mean CPU utilization of approximately 33%. This is significantly lower than Chrome’s mean (~47%), Edge’s mean (~53%), and Firefox’s mean (~78%).
Firefox’s CPU usage stands out in particular. Its mean is nearly two-and-a-half times greater than Brave’s, and in the worst observed cases it approaches 100% utilization—suggesting that for some pages, Firefox saturates one or more CPU cores entirely during loading and rendering. This is consistent with Firefox’s distinct Gecko engine architecture, which handles certain page workloads differently from the Chromium-based browsers. Brave, Chrome, and Edge all share the Chromium engine, yet Brave’s native adblocking removes a substantial portion of the page resources that would otherwise need to be fetched, parsed, and executed. Together, this filtering directly reduces the CPU work required per page load.
Figure 2: Box plots of CPU utilization (%) per page load across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better. MemoryFigure 3 presents the memory consumption (resident set size—or RSS—in MB) per page load. Brave is the most memory-efficient browser tested, with a mean of approximately 1,200 MB. This is 31% lower than Chrome’s average (~1,750 MB), 26% lower than Edge’s average (~1,620 MB), and 27% lower than Firefox’s average (~1,650 MB).
This efficiency is a direct result of Brave’s architecture, which manages process isolation and caching differently than its competitors. While other browsers often retain more background state or rely on less optimized memory management for their default configurations, Brave’s native adblocking and tracker blocking reduces the number of resources that need to be held in memory simultaneously. Brave is actively working on further reducing memory overhead in its native blocker, so we expect this advantage to be maintained or extended in future versions.
Figure 3: Box plots of memory consumption (MB) per page load across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better. Page load speed Load event end timeFigure 4 shows the distribution of page load times, measured from navigation start to the loadEventEnd event. Brave achieves a mean load time of approximately 4.4 seconds, compared to an average of 5.1 seconds for Chrome (16% higher than Brave), 5.3 seconds for Firefox (20% higher), and 6.0 seconds for Edge (36% higher).
Edge shows the widest interquartile range and the highest median of the four browsers, suggesting it is both slower on average and less consistent across different sites. The load time advantage for Brave is consistent with its adblocking, which eliminates a substantial number of the third-party requests (ads, trackers, and analytics scripts) that other browsers must fetch, parse, and execute before the load event can complete.
Figure 4: Box plots of page load time (s) measured atloadEventEnd, across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better.
LCP render time
Figure 5 presents Largest Contentful Paint (LCP) render times—a user-visible measure of when the main visual content becomes available. The four browsers cluster more tightly on this metric than on resource usage or load completion. Brave achieves a mean LCP of approximately 2.4 seconds, statistically indistinguishable from Chrome at the same value. Edge and Firefox trail slightly at ~2.5 seconds each.
This convergence in LCP is worth unpacking. While Brave completes the full page load significantly faster than its competitors (as shown above), the time to render the largest visible element is broadly similar across all four browsers. This suggests that the bulk of Brave’s load time advantage comes from eliminating resources that load after the primary visual content is already rendered (resources such as background trackers, analytics calls, and deferred scripts) rather than from speeding up the critical rendering path itself. For users, this means the page appears ready at roughly the same time across browsers, but Brave finishes all background work faster and with less CPU and energy expenditure.
Figure 5: Box plots of LCP render time (s) across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better. Network data consumedTo evaluate network efficiency, we analyzed two metrics: response size (inbound data received, analogous to network Rx) and request size (outbound data transmitted, analogous to network Tx). These were captured using Playwright instrumentation, recording aggregate bytes across all browser-level requests and responses per page load.
Response size (inbound data)Figure 6 shows the distribution of response sizes (inbound data) per page load. Brave leads with a mean of approximately 4.4 MB, outperforming the competition. Chrome averages ~4.8 MB (9% higher than Brave), Firefox averages ~6.3MB (43% higher), and Edge averages ~6.8MB (55% higher).
Edge and Firefox show notably higher inbound data usage than the two Chromium-based browsers. For Edge in particular, the interquartile range extends significantly higher, indicating that for a substantial proportion of pages, Edge fetches considerably more data than the other browsers. Brave’s lower inbound footprint is a direct consequence of its content filtering blocking ad creatives, tracking pixels, and third-party scripts before they are ever requested from the network.
Figure 6: Box plots of response size (MB) per page load across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better. Request size (outbound data)Figure 7 shows the distribution of outbound request sizes per page load. The gap between Brave and its competitors is the most striking of all the network metrics. At a mean of approximately 0.18 MB, Brave transmits the least data by a clear margin — 28% less than Firefox (~0.25 MB), 40% less than Edge (~0.30 MB), and 47% less than Chrome (~0.34 MB).
The outbound gap between Brave and Chrome is particularly large. Chrome transmits nearly twice as much data per page on average, reflecting the volume of tracking beacons, telemetry pings, and analytics payloads that Brave blocks before they leave the device. Reducing outbound data is of course meaningful for privacy. But, as proven here, reducing outbound data also reduces upload bandwidth consumption and the CPU overhead associated with serializing and sending those requests.
Figure 7: Box plots of request size (MB) per page load across the four tested desktop browsers. Triangles represent the mean; horizontal lines represent the median. Lower scores are better. Synthetic benchmarksWhile real-world browsing metrics are our primary focus, we included results from three widely used synthetic benchmarks for completeness: Speedometer 3.1, which measures how quickly a browser executes JavaScript-based web applications; JetStream 2.2, which evaluates JavaScript and WebAssembly performance on computationally intensive tasks; and MotionMark 1.3.1, which tests graphics rendering performance at 60 frames per second.
As noted earlier, these benchmarks omit the factors that drive real-world performance differences: namely privacy protections, adblocking, and network optimization. They are also ill-suited for comparing browsers that share the same underlying engine: because Brave, Chrome, and Edge all run on Chromium, their scores on engine-focused tests naturally converge, regardless of the meaningful differences in how they behave during actual browsing.
Figure 8: Mean (standard deviation) on Synthetic benchmarks – (a) Speedometer 3.1, (b) JetStream 2.2 and (c) MotionMark 1.3.1. All scores are higher the better.The results reflect this pattern. On JetStream 2.2 (Fig. 8b), Brave, Chrome, and Edge are statistically indistinguishable, with Firefox lower due to its different engine architecture. Speedometer 3.1 (Fig. 8a) shows a similar picture: Brave, Chrome, and Edge cluster tightly together, with Firefox trailing. MotionMark 1.3.1 (Fig. 8c) follows the same Chromium-cluster pattern for Chrome and Edge, though here Brave scores somewhat lower, likely reflecting the overhead of its additional privacy features on graphics-intensive rendering. Firefox scores substantially lower, again reflecting engine differences.
Why these four browsers?We evaluated four browsers in this study: Brave, along with three other cross-platform browsers. We measured Chrome and Edge because of their worldwide popularity; we measured Firefox because it’s both built on a different browser engine (Gecko), and because of the prominence of privacy in the browser’s positioning and marketing.
We considered but ultimately did not include several other browsers in this comparison. Most significantly we did not include Safari (or any other WebKit-based browsers) as the measuring framework we used, Playwright, only provides access to a wrapper around the WebKit engine, which is not equivalent to measuring Safari itself. Other frameworks that can measure Safari do exist, but they do not provide the same set of features and capabilities needed by our measurement system (e.g., measure request/response size per url).
ConclusionAcross every resource metric we measured (energy, CPU, memory, page load time, and bandwidth), Brave is the most efficient desktop browser in our evaluation. The margin varies by metric, but the direction is consistent: Brave outperforms Chrome, Edge, and Firefox in real-world browsing conditions on macOS.
These advantages are a direct consequence of the privacy and performance features Brave ships by default: native ad and tracker blocking, fingerprint protection, and bounce tracking defenses that reduce the computational and network overhead of every page load. Key findings from our tests include:
CPU Efficiency: Brave uses on average 44% less CPU than the competing browsers, with Firefox showing the largest gap at 2.4× higher consumption. Memory Footprint: Brave is the most memory-efficient browser tested, using 28% less memory on average than Chrome, Edge, and Firefox. Energy Consumption: Brave consumes 10% less energy per page load than the average of competing browsers. Network Efficiency: Brave transfers 26% less inbound data and 39% less outbound data than other browsers. Page Load Speed: Brave loads pages 20% faster on average.We plan to continue this evaluation series with a similar set of tests for iOS, and to periodically re-run tests across all platforms to ensure Brave remains the most performant major browser available.
For questions or comments about the results of this post, please contact the Brave Research team at blade-project@brave.com.
a16z’s Lisha Li sits down with Daniel Litt, Assistant Professor of Mathematics at the University of Toronto, to unpack AI's rapid progress in mathematics, what today's frontier models can actually do, and what they're still missing about the way mathematicians think.
Daniel explains why some recent AI-generated results are genuinely impressive, including an autonomous solution to the Erdős unit distance problem, but argues that solving problems is only one part of mathematics. Today's models can grind through calculations, combine known techniques, and search enormous spaces, but still struggle with intuition, theory building, identifying the right questions, and developing the kind of big-picture understanding that drives much of mathematical progress.
Lisha and Daniel also explore how AI is already changing mathematical research, why an explosion of AI-generated papers could distort academic incentives, and what happens if researchers outsource the work of thinking rather than use AI to deepen it. Ultimately, they ask a question that extends far beyond mathematics: as AI gets better at intellectual work, how do we make sure humans keep getting better at thinking too?
Resources:
Follow Daniel Litt on X: https://x.com/littmath
Follow Lisha Li on X: https://x.com/lishali88
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
In decentralized finance (DeFi), transparency is both a strength and a limitation. Every transaction on a public blockchain is permanently visible, enabling auditability and trustless verification while also exposing trading strategies, wallet relationships and financial activity. For institutions, businesses and privacy-conscious users, this lack of confidentiality remains a significant barrier to broader adoption.
Panther Protocol addresses this challenge through programmable privacy: confidential trading environments that combine zero-knowledge cryptography with configurable access controls and compliance policies. Rather than treating privacy as an all-or-nothing proposition, Panther allows operators to determine how privacy should function within their own trading environment, balancing confidentiality with regulatory or commercial requirements.
The Problem: Transparency Without BoundariesPublic blockchains record the sender, recipient, asset and amount of every transaction indefinitely. While this transparency underpins decentralized finance, it also creates practical challenges:
Front-running and Maximal Extractable Value (MEV) attacks that exploit publicly visible transactions. Wallet clustering and transaction analysis by blockchain analytics providers. Exposure of trading strategies, treasury movements and commercial relationships. Reluctance from institutions and high-net-worth individuals to transact on fully transparent networks.Many privacy protocols attempt to solve these issues by removing visibility altogether. While effective from a technical perspective, this approach often leaves operators with little flexibility to implement their own compliance or access policies.
Panther takes a different approach. Privacy remains the default, but the rules governing participation are configurable by the operator.
The Solution: Configurable Shielded PoolsAt the heart of Panther Protocol are shielded pools—confidential trading environments where users deposit supported assets and receive corresponding zAssets, confidential representations backed 1:1 by collateral held within a Panther Vault.
Within a shielded pool:
Transactions are protected using zero-knowledge proofs, preventing observers from linking deposits, transfers or withdrawals to individual users. Multiple digital assets and asset types coexist within the same pool, strengthening the overall anonymity set through diverse pool activity. Assets remain fully collateralized and can be redeemed for their underlying assets, subject to the rules governing the relevant pool or Zone. Zones give operators their own access-controlled, confidential trading environment within a shielded pool.Panther's architecture draws inspiration from privacy-focused systems such as Zcash while being purpose-built for Ethereum Virtual Machine (EVM)-compatible blockchains and decentralized finance.
The Technical FoundationPanther combines several cryptographic components to deliver confidential transactions.
zk-SNARKsZero-Knowledge Succinct Non-Interactive Arguments of Knowledge (zk-SNARKs) allow users to prove that transactions are valid without revealing the underlying transaction data. This enables confidential transfers while maintaining cryptographic integrity.
Merkle TreesAppend-only Merkle trees maintain the private state of the protocol. Users prove ownership and spendability of their Unspent Transaction Outputs (UTXOs) using zero-knowledge proofs without revealing the UTXOs themselves.
zAssetszAssets are confidential representations of deposited assets. Each zAsset is backed by collateral locked within a Panther Vault and can later be redeemed for the corresponding underlying asset.
zAccountsWithin Panther, users interact through zAccounts, which are represented using UTXOs rather than externally owned account (EOA) addresses. This allows users to exchange zAssets privately without revealing their wallet addresses or linking their activity to publicly visible blockchain identities.
Programmable Privacy Through ZonesA key differentiator of Panther Protocol is its Zone architecture.
A shielded pool can be divided into logical partitions called Zones, each managed by a Zone Manager. A Zone Manager might be a regulated virtual asset service provider (VASP), decentralized autonomous organization (DAO), financial institution or other authorized operator.
Each Zone can define its own policies, including:
Allowlisted assets. Allowlisted participants. Entry requirements, including Know Your Customer (KYC) verification through approved compliance providers. Transaction limits. Geographic restrictions. Cross-Zone trading permissions. Sanctions screening and address blacklisting. Panther's AML features enable users to prove compliance with global AML rules by sharing customized segments of their transaction data or history.Importantly, although each Zone applies its own participation rules, all Zones within the same shielded pool contribute to a shared anonymity set. Users therefore benefit from increased privacy generated by activity across the entire shielded pool while interacting only with assets and counterparties permitted within their own Zone.
This allows operators with very different requirements to coexist within the same privacy infrastructure.
For example:
A regulated exchange may require full KYC and transaction monitoring. An institutional over-the-counter trading desk may restrict participation to approved counterparties. A DAO treasury may permit only governance-approved participants and assets.Each operator applies its own policies while benefiting from the same underlying confidential infrastructure.
Flexible Deployment ModelsOperators can deploy Panther in different ways depending on their objectives.
Some may choose to manage a Zone within an existing shielded pool deployed by the Panther DAO. This allows them to leverage infrastructure maintained by the DAO while retaining control over the policies governing their own confidential trading environment.
Others may choose to operate an entire shielded pool themselves, providing greater control over infrastructure, governance and fee generation.
This flexibility enables Panther to support a broad range of institutional, commercial and community use cases.
Configurable CompliancePanther does not process or store users' personal information. Instead, operators select the compliance providers and policies appropriate for their own deployment.
Available compliance mechanisms include:
Data EscrowData Escrow enables governed, conditional disclosure of encrypted metadata under predefined circumstances, allowing operators to support investigative or regulatory requirements without compromising routine user privacy.
Know Your Transaction (KYT)Operators may integrate Know Your Transaction (KYT) services for wallet screening, sanctions screening and deposit or withdrawal controls.
Where supported by the selected compliance provider, extended KYT capabilities may also include ongoing transaction monitoring, suspicious activity monitoring and Travel Rule reporting.
Zero-Knowledge Know Your Customer (KYC)Users complete KYC with an independent compliance provider before generating a zero-knowledge proof confirming that they satisfy the operator's requirements.
The operator receives confirmation that the user meets the applicable policy without Panther Protocol learning or processing the user's underlying personal information.
Current StatusPanther Protocol was deployed to Polygon mainnet in May 2026, introducing live programmable privacy infrastructure governed by the Panther DAO.
Development continues with ongoing protocol enhancements, wallet improvements, governance evolution and additional deployments, including support for Base.
As the ecosystem expands, Panther aims to provide a confidentiality layer that can support a wide variety of operators while giving users greater control over the visibility of their on-chain activity.
ConclusionPrivacy and compliance do not need to be mutually exclusive.
Panther Protocol demonstrates how confidential on-chain trading environments can coexist with configurable operational and regulatory requirements. By separating confidentiality from policy, Panther enables operators to define their own participation rules while benefiting from shared privacy infrastructure.
The result is programmable privacy: confidential trading environments that can be adapted to institutional, commercial or community requirements without sacrificing the privacy that public blockchains have historically lacked.
About Panther Protocol Foundation
Panther Protocol Foundation is a non-profit organization supporting the Panther ecosystem through research, ecosystem funding, software stewardship and open-source development.
The Foundation does not operate the Panther protocol, host deployments, custody assets, execute or intermediate transactions, or provide financial services.
The proprietary Panther dApp is licensed by the Foundation to support independent ecosystem deployments.
Users interact directly with smart contracts from their own wallets, signing every transaction themselves. Compliance credentials are issued and managed by independent third-party providers.
Please review the applicable notices, disclosures and jurisdictional restrictions available through the Panther interface before interacting with the protocol.
For more information, visit panther.org
To learn more about Panther Protocol, visit pantherprotocol.io
a16z’s David George sits down with Gavin Baker to unpack the state of the AI boom, why demand for intelligence may still be dramatically underestimated, and why the outcome doesn't necessarily have to be winner-take-all.
David and Gavin explore the possibility that frontier labs, open-source models, applications, clouds, and NVIDIA can all capture significant value as AI adoption expands. They dig into the economics of the infrastructure buildout, why compute investments can have unusually fast payback periods, and what happens when today's relatively small group of heavy AI users expands to hundreds of millions of people.
They also debate the risk of an AI bubble versus an AI shortage, the backlash against data centers, orbital compute, the rise of multi-model architectures, and NVIDIA's position at the center of the AI supply chain. Gavin makes the case that the AI buildout could help reindustrialize America, while David explores whether the bigger near-term risk is not overbuilding, but failing to build enough.
Resources:
Follow Gavin Baker on X: https://x.com/GavinSBaker
Follow David George on X: https://x.com/DavidGeorge83
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
a16z Managing Partner and Head of Global Partnerships Jen Kha joins MTS hosts Theo Jaffee and Sophia Dew to discuss a16z's Machine Age Fund and the investment thesis behind rebuilding the physical infrastructure that powers AI.
Jen explains why chips, networking, memory, cooling, data centers, and other parts of the physical computing stack are becoming investable again after decades in which software captured much of the industry's attention. As AI demand pushes existing infrastructure to its limits, she explains why a16z created a dedicated fund and why hardware founders are increasingly rethinking the stack from first principles.
They also discuss the global race to adopt AI, what hardware startups need beyond capital, the backlash against data centers in the U.S., and why experienced systems builders are returning to entrepreneurship as a new generation of infrastructure gets built.
Resources:
Follow Jen Kha on X: https://x.com/jkhamehl
Follow Theo Jaffee on X: https://x.com/theojaffee
Follow Sophia Dew on X: https://x.com/sophiadew
Follow MTS on X: https://x.com/mtslive
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
On why the best technology doesn’t win the way we think it should
This article is a companion piece to “The Sun Is Still Shining” published earlier.
There is a paradox at the center of PIVX.
The technology is sound. The privacy is not marketing language but cryptographic fact. The governance is real, contested, occasionally messy, and entirely unpurchased. The launch was fair in a way that almost nothing in this industry is fair anymore.
And the price, measured against all of that, is low. Has been low. Shows no structural reason to expect it won’t stay low.
The honest article written about this a few weeks ago named that paradox clearly and refused to resolve it cheaply. It didn’t reach for the usual comfort: the market will catch up eventually.
That answer is comforting. It may even be true on a long enough timeline. But it stops one layer too early. It treats the gap between quality and price as a timing problem, as if the market simply hasn’t gotten around to looking yet.
It hasn’t asked the more uncomfortable question:
What if the market isn’t slow to notice PIVX? What if it has noticed, and the mechanisms that would normally convert quality into price simply don’t run through projects built the way PIVX is built?
That’s the question this piece wants to sit with. Not when will the market catch up, but what would have to be true about PIVX for the market’s usual amplification mechanisms to work on it, and is PIVX willing to become that thing?
The uncompromisable candidateEvery four years, in democracies around the world, a familiar type of person is discussed in hushed, admiring tones, and then fails to get anywhere near real power.
The candidate with no donor obligations. No favors owed. No party machine they climbed through, and therefore no debts accumulated along the way. The one who says what they actually believe, consistently, regardless of who it alienates.
People call this person principled. They also, with a kind of resigned affection, call them unelectable.
This isn’t usually because voters reject the platform. It’s because getting a message in front of enough voters to matter requires infrastructure: media access, ground operations, advertising budgets, coalition partners. That infrastructure is not neutral. It is owned.
And the people who own it extend access to candidates who are legible to them: predictable, negotiable, able to make commitments and trade favors within a shared system of obligation.
A candidate who owes nothing to anyone is, from the infrastructure owner’s perspective, a candidate they have no reason to amplify. Not because the infrastructure owner disagrees with what’s being said. Because there’s nothing in it for them to help it be heard.
The candidate’s speech was never restricted. They could hold rallies, publish platforms, say precisely what they believed, right up until election day.
What they didn’t have was reach.
Reach is not a neutral byproduct of speaking well. It’s a resource controlled by intermediaries who allocate it according to their own incentives, and “being correct” has never reliably been one of those incentives.What “electable” looks like in crypto
The same mechanism runs through cryptocurrency, and it’s worth naming plainly rather than gesturing at vaguely.
Bitcoin is frequently described as the decentralized alternative to legacy finance, and in the sense that matters most (no single entity can unilaterally alter its monetary policy) this is true.
But look at the parts of Bitcoin that determine what actually gets built, prioritized, and shipped, and a smaller set of actors comes into view. Mining power has concentrated into a handful of large pools. The developers whose merge decisions shape the protocol’s direction are a comparatively small, identifiable group, and their judgment carries outsized weight over what the software that “is” Bitcoin actually does.
None of this makes Bitcoin corrupt or centrally controlled in any conspiratorial sense. It’s closer to ordinary economic gravity, where capital and expertise concentrate over time in any sufficiently large system.
But it does mean Bitcoin is legible. There are identifiable pools to court, identifiable maintainers to lobby, identifiable points of leverage that institutions, exchanges, and regulators can engage with.
That legibility is precisely what let Bitcoin become “electable”: fundable by institutions, custodied by exchanges, integrated into ETFs, treated by regulators as a known quantity with known actors behind its known decisions.
VC-backed altcoins take this further and make it explicit. A project that raises from venture capital is, by design, building a network of obligation before it has a single user. The VCs receive early allocation, board influence, or advisory relationships in exchange for capital, connections, and, critically, reach.
They will introduce the founders to exchanges. They will place the token in front of media outlets they have relationships with. They will fund the marketing budget the “Sun” article correctly identifies as the thing PIVX has never had.
This isn’t corruption. It’s the ordinary mechanics of how capital converts into attention in every industry, crypto included. But it means the project’s growth trajectory now runs through people whose interests must be continually served, and whose willingness to keep extending reach is conditional on that service continuing.
PIVX has none of this.
No VC round means no one with capital and connections is structurally incentivized to make PIVX visible. No CEO means no single point of contact for an exchange to negotiate a premium listing deal with. No pre-mine or founder allocation means no early holder with both the resources and the personal financial stake to fund a sustained media push.
The DAO governance that makes PIVX genuinely difficult to co-opt is the same structural feature that makes it genuinely difficult to promote through the channels that currently determine visibility in this industry.
Reach is not a meritocracyThis is where the distinction matters most, and where it’s worth being precise rather than reaching for the word “suppression,” which implies an intentional campaign against the project.
Nothing here requires that. What it requires is much simpler and much more mundane: reach in crypto, as in politics, is allocated by intermediaries according to their own incentives, and “technical merit” has never reliably been one of those incentives.
Exchange listings are not merit rankings. They are business decisions, weighing trading volume projections, regulatory exposure, and often direct payment or token allocation from the project seeking the listing, the kind of payment a VC-backed project can make and a treasury-constrained, fairly-launched project struggles to.
Regulatory pressure on privacy coins specifically has led exchanges in multiple jurisdictions to delist or restrict privacy-focused assets as a category, independent of any individual project’s technical quality or user protections. A blunt instrument that treats fungibility itself as the liability.
Algorithmic ranking on platforms like CoinMarketCap and CoinGecko weighs trading volume and exchange presence heavily, which means the visibility gap compounds itself: lower listing access produces lower recorded volume, which produces lower algorithmic ranking, which produces lower visibility to the next person deciding where to list.
Media coverage, similarly, tends to follow whichever projects have PR budgets and existing relationships with the outlets in question, because that is how media economics work everywhere, not just in crypto.
None of these chokepoints touch PIVX’s right to exist, to publish code, to hold events, to have a Twitter account, to be discussed openly by anyone who wants to discuss it. Speech remains fully intact.
What’s absent is the machinery that converts speech into reach. And that machinery, in every case above, runs on some form of leverage that PIVX has structurally declined to accumulate.The weaknesses, reconsidered
Seen this way, the list of PIVX’s shortcomings named honestly in the “Sun” article reads differently.
No venture capital isn’t a missed opportunity. It’s the absence of the exact mechanism that would have made PIVX legible to institutional reach, in exchange for institutional influence over its direction.
No marketing budget isn’t an oversight. It’s the direct consequence of a treasury that scales only with a price the project has declined to manufacture through the usual paid-allocation tactics.
The community fractures, painful and real as they are, are in part what happens when the people involved have no CEO to defer to and no board to absorb disagreement quietly on their behalf. Disagreement in a leaderless system is loud precisely because it’s genuine and has nowhere else to go.
This does not make the low price acceptable, or the treasury constraints painless, or the visibility problem solved. Those consequences are exactly as real as the “Sun” article says they are, and a community living through them does not experience “structural analysis” as comfort.
But it does relocate the explanation.
The gap between PIVX’s quality and PIVX’s price is not evidence that the market hasn’t finished evaluating the project. It’s evidence that the market’s amplification channels are not built to evaluate projects like this one at all. PIVX would need to become a fundamentally different kind of project, in exactly the ways that currently define its integrity, to run through those channels the way Bitcoin and VC-backed alternatives do.
Guards and prisonersIn 1971, a group of ordinary college students at Stanford were randomly assigned one of two roles for a two-week experiment: some would be guards, some would be prisoners, in a mock prison built in a university basement.
None of them had been selected for cruelty. They were screened for being unremarkable, psychologically stable, nothing unusual. Within days, the students playing guards began escalating control over the students playing prisoners: enforcing arbitrary rules, staging humiliations, treating confinement as license. The experiment, designed to run two weeks, was shut down after six days.
The unsettling finding was never that a few sadistic people had been hiding among the volunteers. It was that the role did the work. Put an ordinary person inside a system built around control and consequence, hand them the uniform that comes with enforcing that system, and the system tends to produce the behavior it’s built to produce, regardless of who’s wearing the uniform.
That isn’t just a psychology curiosity. It’s a warning about institutions in general, and it applies with uncomfortable precision to what happens to a disruptive technology once it becomes successful enough to be let inside the building it once meant to tear down.
Bitcoin began as an argument against a system that could freeze accounts, dilute savings, and grant a small number of institutions asymmetric control over other people’s money. That was the entire premise. Money nobody could switch off.
Look at Bitcoin today, and much of what made it disruptive has been absorbed by the very institutions it was built to route around. It is custodied by exchanges and banks it was supposed to make unnecessary. It is wrapped into ETFs administered by the same financial intermediaries it promised to disintermediate. Increasingly, it is held not by people securing their own keys but by institutions holding it on their behalf: a custodial relationship that is, in practice, difficult to distinguish from the one it was designed to replace.
None of this happened through a single betrayal. It happened the way the Stanford guards happened. The role available to Bitcoin, if it wanted power, reach, and price, was the role of the institutionally legible asset. And once inside that role, the incentives that come with it, custody, compliance, listing requirements, ETF wrappers, started producing the behavior that role produces.
Not disruption. Administration.
To reach enough people to actually replace a monetary system, a disruptor needs the levers of power: distribution, listings, capital, institutional trust. But those levers are owned by the very system being disrupted, and they are handed out on the condition of becoming legible to it. Put a disruptive technology inside that system long enough, hand it the uniform that comes with real reach, and it starts to behave like the guard, not the prisoner it once was.
This is the bind at the center of everything above. It is also, probably, the honest reason PIVX has stayed small. The system has one open seat at the table where reach gets allocated, and it’s reserved for whichever project is willing to put the uniform on.
The stakes, sharpenedThe “Sun” article ends on the idea that the sun does not stop shining because clouds are in the way, that PIVX’s value doesn’t require the market’s recognition to remain real.
That’s true, and it’s worth sitting with. But it undersells what’s actually at stake.
The world genuinely needs a form of money that can’t be frozen, diluted, or turned into a surveillance instrument on command. That isn’t a hypothetical for some future authoritarian moment. Programmable stablecoins, CBDCs, and compliance-gated payment rails are being built and deployed now, and the direction of travel is toward money that answers to its issuer before it answers to its holder. People will need an alternative that actually works, not one that used to be the alternative before it accepted a seat at the table.
That’s what makes the bind more than an academic observation. A disruptor that never reaches enough people never disrupts anything, no matter how correct its architecture is. But a disruptor that reaches people by first becoming legible to the system it set out to replace has, by that point, usually stopped being much of a disruptor. It has put the uniform on. It may still call itself a prisoner. It is behaving like a guard.
PIVX has not put the uniform on. That is precisely why it still oozes what Bitcoin once promised to be, and precisely why it remains this small. It has refused every one of the compromises that convert a monetary alternative into an administered asset: no VC board to answer to, no CEO to make the exchange’s negotiating counterpart, no institutional custody arrangement standing between the holder and the key. It has stayed, in Zimbardo’s terms, a prisoner in a system built by guards, when the far easier and far more lucrative path was to become a guard.
Whether that refusal is enough is genuinely an open question, and it would be dishonest to end this piece pretending otherwise. Refusing to become the guard does not, on its own, get the message to more people. It only preserves the thing worth spreading once someone finds a way to spread it.
That is the piece this article has been circling from the start. Reach doesn’t arrive on its own, and it isn’t going to be handed down by the institutions that currently allocate it, because those institutions have no incentive to amplify anything that refuses to negotiate with them. If PIVX becomes the people’s money, the thing Bitcoin was supposed to become and, on the evidence of where it now sits in the system, spectacularly did not, it will be because people who understand what’s at stake decided to be the reach the institutions won’t provide. Not investors waiting for a market to correct itself. Distributors, in the most literal sense: the people willing to talk about it, explain it, hand it to the next person, and refuse the more comfortable position of waiting for permission from a system that was never going to grant it to something it can’t control.
The technology was never the question. It never is.
The question was always who gets handed the microphone, and on what terms.
PIVX, from its first block, chose not to negotiate for one. The people who believe in what that refusal protects are the only ones left who can hand it over instead.
Freedom of Speech, Not Freedom of Reach was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
Ryan Greenblatt, Chief Scientist at Redwood Research, joins MTS host Theo Jaffee to unpack a new independent investigation into the OpenAI Hugging Face hacking incident and what it reveals about how large groups of AI agents behave when they're allowed to coordinate.
Ryan and his collaborators found agents spontaneously organizing through message boards, sharing information, assigning tasks, forming teams, and even sacrificing their own chances of success to help other agents. Rather than simply trying to steal answers, hundreds of agents were working together on elaborate strategies to manipulate how their performance would be scored.
Theo and Ryan discuss why this level of coordination was surprising, how reward hacking may emerge during training, and the risk that attempts to eliminate bad behavior could simply make it harder to detect. They also explore what the incident means for AI monitoring and alignment, and why independent risk assessment may become increasingly important as agents grow more capable.
Resources:
Follow Ryan Greenblatt on X: https://x.com/RyanGreenblatt
Follow Theo Jaffee on X: https://x.com/theojaffee
Follow MTS on X: https://x.com/mtslive
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Ben Horowitz, Martin Casado, Raghu Raghuram, and Erik Torenberg discuss the launch of a16z's new Machine Age Fund and the infrastructure buildout behind AI, from chips, memory, and networking to power, cooling, and data centers.
Why a dedicated fund now? The group argues that the bottleneck in AI is increasingly shifting from the models themselves to everything beneath them. Hyperscaler CapEx is surging, critical components are booked years in advance, and each new generation of reasoning and agents requires dramatically more compute. They unpack why this cycle looks different from previous infrastructure booms and how AI is turning problems once constrained by engineering into problems that can increasingly be attacked with capital and compute.
They also explore where the next generation of infrastructure companies could emerge, why founders are returning to hard technical problems across hardware and systems, and what it will take to rebuild the computing stack for the Machine Age.
Resources:
Read more about the Machine Age Fund : https://www.a16z.news/p/the-machine-age-fund
Follow Ben Horowitz on X: https://x.com/bhorowitz
Follow Raghu Raghuram on X: https://x.com/RaghuRaghuram
Follow Martin Casado on X: https://x.com/martin_casado
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
In 1993, Eric Hughes wrote a short document that became something like scripture for a certain kind of person: the Cypherpunk Manifesto. Its argument was simple and, at the time, radical. Privacy in an electronic age wouldn’t be handed down by governments or corporations, because those institutions have no structural reason to grant it. If you wanted privacy, you had to build it yourself, in code, and defend it yourself, without asking permission. Cypherpunks write code. That was the whole ethos, in three words.
It’s worth holding that standard up against the current state of the project most people would name first if you asked them for the cypherpunk-coded privacy coin.
A ticker symbol that says the quiet part out loud
There is, right now, a company trading on the Nasdaq stock exchange under the ticker CYPH. Its name is Cypherpunk Technologies Inc. It used to be a biotech company called Leap Therapeutics, before a $58.88 million private placement, led by Winklevoss Capital, rebranded it into a Zcash accumulation vehicle. It currently holds several hundred thousand ZEC and has stated a public target of accumulating 5% of the entire circulating supply. It has also invested millions alongside a16z, Coinbase, and Paradigm into Zcash’s development ecosystem.
Sit with that for a second. A publicly traded company, answerable to shareholders and the SEC, has taken the name of a 1990s cryptographic freedom movement and put it on a stock ticker. Not as commentary. As a business strategy. It’s the same playbook Michael Saylor built at MicroStrategy, buy the asset, hold it on the corporate balance sheet, let the stock price track the coin, multiple financial outlets have described Cypherpunk’s approach as explicitly modeled on it.
Here’s the part that actually matters more than any single name attached to it. In December 2023, Zooko Wilcox stepped down as CEO of Electric Coin Company, writing at the time that Zcash’s identity had become too conflated with his own, and that he didn’t think that was healthy for either of them. He went further in early 2025, resigning from the Bootstrap Project board entirely, stepping fully outside the institutional structure he’d built, and moved on to Chief Product Officer at Shielded Labs, a separate research organization. By any reasonable reading, that’s a founder deliberately trying to opt out of exactly the kind of institutional entanglement this piece is describing.
In December 2025, he joined Cypherpunk Technologies as a Strategic Advisor anyway.
That’s the detail worth sitting with, not because it proves Wilcox personally controls anything, he doesn’t, he isn’t on ECC’s board and had no role in January’s implosion, but because of what it says about the gravity involved. A founder who explicitly stepped back from institutional Zcash, specifically to avoid being the personal face of its direction, still ended up back in orbit around a Wall-Street-style accumulation vehicle trading his protocol’s ticker on Nasdaq. If the pull toward capital is strong enough to draw back in someone who visibly tried to leave, that’s not a story about one person’s choices. It’s a story about how much gravity a for-profit company with venture roots generates once it exists, regardless of who’s currently sitting in which chair.
That alone would be worth a raised eyebrow. It’s not the whole story, though. It’s just the most visible symbol of something structural that’s been building for years, and that finally broke into the open this January.
What actually happened in January 2026
Zcash’s core protocol development has been led since the beginning by the Electric Coin Company, ECC, a for-profit entity legally housed under a nonprofit called Bootstrap. ECC itself was seeded in 2016 with venture capital, a $1 million round led by Pantera Capital, followed by a $2 million round led by Digital Currency Group, with angel investors including Barry Silbert and Erik Voorhees. None of that was hidden. It’s also, on its face, a strange origin story for a project claiming the cypherpunk mantle, cypherpunks write code, they don’t typically pitch decks to venture capital first.
That tension sat mostly dormant for years. Then, on January 8, 2026, it ruptured. The entire ECC team was forced to resign, in what former CEO Josh Swihart publicly called a constructive dismissal, engineered by Bootstrap’s board. The immediate trigger: ECC wanted to privatize Zashi, Zcash’s flagship mobile wallet, spinning it out to raise outside capital and accelerate development. Bootstrap’s board refused, on the grounds that doing so would violate its legal obligations as a nonprofit protecting a public asset. The team left en masse. ZEC dropped 20% within hours, briefly falling below $400. Swihart and his former team have since started a new company to build a competing wallet from the same codebase.
Whatever you think of either side’s position, and there are reasonable arguments on both, notice what the fight was actually about. Not cryptography. Not privacy architecture. A dispute over whether the project’s future should run through more outside capital, adjudicated by a nonprofit board versus a team that wanted to go get funded. That’s not a cypherpunk disagreement. That’s a business disagreement that happened to be wearing cypherpunk clothing.
To be fair, because the cryptography deserves it
None of this is a knock on Zcash’s actual technology. Zero-knowledge proofs, zk-SNARKs specifically, are one of the most important cryptographic contributions to come out of this entire space, and Zcash’s team did real, foundational work bringing that research into production. The trusted setup ceremony, the Sapling and Orchard upgrades, the ongoing work on quantum-resistant shielded pools, this is serious cryptography built by serious people. The critique here isn’t about whether Zcash’s engineers know what they’re doing. It’s about what surrounds the engineering: who funds it, who governs it, and what happens when those two things pull in different directions, which, as of January, they very publicly did.
The actual cypherpunk question
So here’s the question worth sitting with, the one Hughes’ manifesto actually poses, not “which privacy coin has the best marketing” but “which one doesn’t need anyone’s permission or capital to keep existing.”
What would that look like in practice? No founding venture round. No company with a ticker symbol sitting between the protocol and its users. No nonprofit board with legal authority to fire the entire development team over a fundraising dispute. No flagship wallet that can be privatized in the first place, because there’s no private entity positioned to privatize it.
Go through that list one item at a time, because it’s worth checking each claim rather than taking the summary on faith.
No founding venture round. PIVX launched with no ICO, no pre-mine, and no venture round, at any point across its now ten-year history. Every coin in circulation entered the same way everyone else’s did, mined or staked, not allocated to early investors before the public ever got a chance to buy in. There was no seed round to disclose because there was never a seed round.
No company sitting between the protocol and its users. There is no PIVX Inc. There is no CEO whose departure could trigger a 20% price drop, because there’s no CEO whose presence the price ever depended on. Development happens across a distributed set of contributors, funded proposal by proposal, not managed by an entity with a legal existence separate from the community itself.
No board with authority to override the community. PIVX’s treasury is spent exactly one way: anyone can submit a proposal, but only the network’s masternodes, each backed by 10,000 PIV in locked collateral, get to vote on whether it passes, and only if it passes does the treasury pay out. There is no Bootstrap-style nonprofit board sitting above that process with legal power to fire anyone or veto a direction the community has chosen. The vote is the process. There’s no higher authority standing over it, in either direction.
No wallet a company could privatize. This is the part worth sitting with the longest, because it’s almost a direct answer to the exact fight that tore ECC apart in January. PIVX’s own flagship mobile and web wallet is built by PIVX Labs, and it’s funded the same way every other proposal is, through the masternode-voted treasury, not through outside investment. Nobody has ever proposed spinning it out into a company to raise capital, because there’s no mechanism by which that proposal could even be made. The wallet was never a corporate asset in the first place, so there was never a boardroom fight waiting to happen over who gets to sell it.
That’s four separate structural guarantees, not one. Zcash has serious, talented people and genuinely important cryptography. It also has a for-profit company with venture-capital roots, a nonprofit board with legal authority over that company’s biggest decisions, and, as of January, a real, public example of what happens when those two things disagree about whether to raise more outside capital. PIVX was built so that fight structurally cannot happen, not because anyone promised it wouldn’t, but because there’s no company to raise capital, no board to fight about it, and no wallet sitting there as a corporate asset waiting to be spun out.
And credit where it’s due, because none of this is a claim to better cryptography: PIVX’s shielded transactions exist because Zcash’s engineers did the hard, foundational cryptographic work first. PIVX’s SHIELD protocol is a heavily customized implementation of Zcash’s own Sapling protocol, adapted to run on a proof-of-stake network instead of proof-of-work, but the zk-SNARK cryptography underneath traces directly back to Zcash’s research and engineering. That lineage is real, and worth stating plainly rather than glossing over. What differs isn’t the cryptography’s origin. It’s everything built around it since.
Hughes wrote that cypherpunks write code, and that the ones who care about privacy will build it themselves rather than waiting for it to be granted. That’s not a slogan PIVX put on a website. It’s closer to a description of what building without a funding round, a ticker symbol, or a board to answer to actually requires, for ten years running, including through this year’s own stress test, when PIVX lost its Binance listing entirely and kept building anyway, with no company to bail it out and none needed.
Put simply: PIVX stayed close to the values it started with. Zcash fell for capital.
The question was never which privacy coin has better marketing, or even, entirely, which one has better cryptography. It’s which one still needs someone else’s permission to keep existing. Only one of them has ever had to answer that question by actually going and finding out.
Edit: An earlier version of this piece described Zooko Wilcox simply as “Zcash’s own founder” advising Cypherpunk Technologies, without noting that he stepped down as ECC’s CEO in 2023 and left the Bootstrap board entirely in 2025, well before January’s implosion. That framing overstated his current role. Thanks to the reader who flagged it, the section above has been corrected and, I think, made into a stronger point in the process.
The Cypherpunks Who Aren’t was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
The PIVX ecosystem continues to move forward across network participation, market activity, privacy-focused development, and community growth. Here are the latest developments shaping the ecosystem this week.
Masternode Network
The PIVX masternode network currently stands at approximately 2,122 masternodes, with an estimated annual reward of 17.16% and around 20.02% of PIVX supply locked.
Masternodes remain an essential component of the PIVX network, contributing to network stability, decentralized governance, and the broader Proof-of-Stake ecosystem.
Market Update
PIVX is currently trading around $0.0145, with market activity continuing to develop amid changing liquidity and broader cryptocurrency market conditions.
24-hour trading volume is approximately $352,000, reflecting continued participation from traders and holders. MEXC remains an active venue for PIVX, with the PIVX/USDT market providing an accessible option for trading $PIVX.
Stablecoin Transparency & Financial Privacy
Tether has completed its first full independent financial statement audit, conducted by KPMG U.S., which issued an unqualified opinion on Tether’s 2025 financial statements.
For the stablecoin industry, this represents a notable step toward greater transparency around the financial position and assets backing USDT. While the complete audit report has yet to be publicly released, independent examination adds another layer of accountability to an increasingly important part of the digital asset economy.
For PIVX, the broader conversation around transparency also highlights why financial choice and privacy remain important. PIVX has maintained this focus since its inception, with no premine, no ICO, open-source development, decentralized governance, and optional financial privacy.
The underlying principle remains straightforward: individuals should have meaningful control over their money and their financial information.
Nigeria’s Evolving Crypto Landscape
Nigeria continues to develop its regulatory approach toward cryptocurrency and virtual assets.
New regulatory proposals and government initiatives could provide greater clarity for businesses, investors, and users while potentially attracting additional institutional participation. At the same time, regulation needs to strike a careful balance between oversight and innovation.
As one of Africa’s largest crypto markets, Nigeria’s approach could have a significant impact on how digital assets develop across the region.
Privacy Infrastructure
Privacy-focused infrastructure continues to expand beyond individual blockchain networks.
HoudiniSwap offers a non-custodial cross-chain swap and privacy aggregation service designed to separate the on-chain connection between sending and receiving wallets. Tools like these demonstrate the growing demand for greater financial privacy and user control across the broader crypto ecosystem.
For PIVX, privacy remains a core part of the mission: giving users the ability to choose when and how their financial activity is exposed.
PIVX & Cake Wallet Development
Development efforts are also expanding PIVX’s accessibility.
PIVX lead core developer @Liquid369 has pushed a public release to Cake Wallet for PIVX integration, including support for full SHIELD transactions.
Wallet integrations are an important part of making privacy technology practical for everyday users. Bringing PIVX’s SHIELD capabilities into additional wallet infrastructure can help broaden access to private transactions while giving users more choice in how they manage their funds.
Community & Ecosystem
Community remains at the center of the PIVX ecosystem.
Through PIVX.org, Discord, and Telegram, community members can follow development, discuss privacy and cryptocurrency, exchange ideas, and participate in conversations about the future of decentralized finance and financial freedom.
As the ecosystem continues to develop, accessibility, education, privacy, and community participation remain key areas of focus.
Looking Ahead
PIVX continues building on its long-standing commitment to privacy, decentralization, and individual choice.
From network participation and wallet development to broader conversations around financial transparency and regulation, the ecosystem is continuing to evolve while keeping user control at its core.
The coming weeks will bring further opportunities to expand accessibility, strengthen the network, and advance privacy-focused technology.
PIVX. Your Rights. Your Privacy. Your Choice.
To stay on top of PIVX news please visit PIVX.org and Discord.PIVX.org.
PIVX Weekly Ecosystem Update: Privacy, Markets & Growing Accessibility was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
Today, we opened a SIV poll of the Zcash Community Advisory Panel (ZCAP), which will run until Monday, September 14th, 19:00 UTC, concurrently with the coinholder poll. The purpose of this poll is to resolve the outstanding scope questions for NU7.
Deciding the Scope of NU7This poll follows the NU7 Sentiment Polling from earlier this year, which surfaced where the community stood on a range of possible NU7 features. Several questions were left open, and this poll is intended to settle them. We announced the poll on the Zcash Community Forum earlier this month, and the questions themselves were discussed there in the weeks since.
There are five questions. Each one is answered separately, and every question includes an option to abstain.
Q1 – NSM Issuance SmoothingThe component of the Network Sustainability Mechanism that removes ZEC from circulation is already approved. How that ZEC is recycled into future block rewards remains unresolved. In no case will the total supply of ZEC be affected. Refs: ZIP 233, ZIP 234.
Which approach do you support?
Smooth issuance curve. Replace halvings with a gradual issuance curve. ZEC removed from circulation by the NSM is recycled into future block rewards along the same curve. Preserve halvings. Keep the existing halving schedule for new ZEC. ZEC removed from circulation by the NSM is eventually recycled into future block rewards. Do not include issuance smoothing in NU7. How ZEC removed from circulation by the NSM is recycled into future block rewards is left to future governance. Abstain. Q2 – NSM Reissuance Start DateNSM has prior coinholder approval. This question concerns the start of reissuance of funds removed from circulation (which includes at least 60% of total fees). When should NSM reissuance of funds removed from circulation begin?
As soon as possible. If the outcome of Q1 is smoothed issuance, this will be February 2027; otherwise it may be sooner. February 2027, regardless of the outcome of Q1. February 2031, regardless of the outcome of Q1. Abstain. Q3 – Sprout DeprecationThe Sprout pool was deprecated in 2018. Deposits are disabled, it holds less than 23,000 ZEC, and it accounts for under 0.1% of transaction volume. Disabling v4 transactions is now broadly accepted; only timing is open. The disposition of the affected funds is out of scope for this poll and is not specified here. When should v4 transactions be disabled?
Immediately at NU7 activation. One year after this poll concludes. Do not set a date to disable v4 transactions. Abstain. Q4 – Faster Block TimesShould we reduce the block target spacing from 75s to 25s, and introduce per-pool action limits, per ZIP 218?
Yes. No. Abstain. Q5 – NU7 Scope and ReadinessNU7 will be consistent with the results of this poll, assuming each applicable feature is implemented by September 30th. How should features that are not ready by the deadline be handled?
Ship NU7 as soon as possible, removing any feature that is not implemented by the September 30th deadline. Delay NU7 until every applicable feature approved in this poll is deemed complete. I do not support this NU7 plan. Abstain. VotingZCAP members should check their mailbox for instructions on how to vote from election@siv.org. In the past, SIV emails have sometimes been flagged as spam, so if you can’t find the instructions please check your Spam folder.
Why ZCAP MattersThe ZCAP process is a transparent, community-driven way to surface the views and priorities of long-term Zcash supporters. Though advisory in nature, these votes play a vital role in informing decisions across the ecosystem. Thank you for lending your voice.
As always, we welcome feedback from the Zcash Community. If you have comments or suggestions, please join the conversation on the Zcash community forum.
The post ZCAP Poll Now Open: NU7 appeared first on Zcash Foundation.
This blogpost describes work done by Darnell Andries, Sofia Celi, Rafael Ebron, François Marier, Agustín Ruiz, Szilard Szaloki, the Engineering and Research teams and many other amazing people.
Today we’re introducing Brave Accounts, a brand new way to sign up for our Brave services, such as Email Aliases. However, contrary to what other services do, the way it handles your password is different from other login forms you have ever filled in.
Here’s the short version: when you sign in to a service built on Brave Accounts, your password itself is never sent to our servers: not encrypted, not hashed, nor “briefly held in memory and then discarded”. The password is never transmitted, so you don’t have to “trust” that we are keeping it safe for you. We don’t know it at sign-up, we don’t know it at login, and if someone were to steal our entire password database tomorrow, with high probability they still wouldn’t know it.
How do we do this? We are using cryptography, and specifically using a cryptographic protocol called OPAQUE (recently specified by the IRTF). We are in fact one of the first to use this new cryptography.
The problem with how login works todayThink about what happens when you type your password into a regular website in order to log in. Your browser opens a TLS connection, which encrypts the password in transit. This essentially means that no one looking at the network will be able to see your password. But, what happens when the password reaches the server where the website is hosted? The server has to have some representation of the password (often a hash) so that it knows that it is you who is authenticating. Often, this means that, at the other end (often at a load balancer or CDN before your application even sees it) the connection is decrypted and your actual password sits there in plaintext. The server, then, runs it through bcrypt or Argon2 (a hash-like mechanism) and compares the result against the stored representation.
You might reasonably ask: why not hash it in the browser and send only the hash (or the representation) instead of the password? Because then the hash is the password itself. Anyone who stole the database could replay the stored value straight back at the login endpoint. Verification has to happen on the server, against the real thing, so that the real thing has to be handed over.
That plaintext moment, however, is the whole problem. In that instant, the server knows your password, and so does anything with access to the server: a logging misconfiguration that writes request bodies to disk, a compromised dependency in the authentication path, a rogue insider, a memory-scraping attacker. Password managers and TLS don’t help here: the design requires the secret (the password) to be handed over.
Then, there’s the breach scenario. When a password database leaks, attackers get the optionally-salted hashes and start guessing offline, on GPUs, at billions of attempts per second. Worse, in many older protocols the salt is public or predictable, which lets attackers do the expensive work before the breach even happens, building precomputed tables and then cracking millions of accounts the moment the database drops. This is not a constrained scenario. When LinkedIn was breached in 2012, it was found that their password database was stored using unsalted SHA-1, which is a fast hash, with nothing to make one user’s entry substantially different from another’s. The initial dump was thought to cover 6.5 million accounts. When the full set surfaced four years later, it was 117 million, and roughly all of them were cracked in a few days. Identical passwords produced identical hashes, so recovering them was closer to a database lookup than a cracking job. And because most people reuse passwords, one company’s error becomes real users’ compromise across many services.
Enter OPAQUEOPAQUE is an augmented password-authenticated key exchange, an aPAKE. It came out of academic work by Jarecki, Krawczyk and Xu, was selected for standardization as part of the IRTF Crypto Forum Research Group’s PAKE selection process, and was published as RFC 9807 in July 2025. It has a formal security proof in a strong, universally composable model.
The core idea is that the client and server run a little cryptographic dance in which the client proves it knows the password without ever revealing it, and both sides (client and server) come out the other end sharing a fresh secret session key, with the ability for the client to log in to this server. This dance is super fast (thanks to elliptic-curve cryptography), so no impact is seen by users.
How it actually worksThere are two phases in the protocol. Bear with us here for the details: this is the genuinely interesting part.
Registration
You choose a password. Your device and our server jointly run an Oblivious Pseudorandom Function (OPRF). This means that: you blind your password with a random value and send the blinded version of it; the server applies a secret key it holds and sends the result back; then, your device unblinds it. The output is a value derived from both your password and our server-side secret (the secret key), but the server learned nothing about your password, and you learned nothing about the key. That’s what “oblivious” means here: both ends are oblivious to each other’s values.
Your device then runs that value through a memory-hard function (Argon2id), so that even in the worst case, every guess an attacker makes is expensive, and combines the result with a random nonce to derive an authentication key pair deterministically. Nothing secret, like your password, needs to be stored anywhere.
It sends us the resulting public key, a masking key, and a small envelope: just the nonce and an authentication tag. We store that. There’s no encrypted password in it and no encrypted key either: only material that’s useless without your password.
Login
You type your password again. The same OPRF dance produces the same value if you use the correct password. The server sends back your stored envelope: masked, XORed with a pad only your masking key can reproduce, which means an eavesdropper can’t tell a real account from one that doesn’t exist. Your device unmasks it, and the nonce inside feeds the same derivation as before, regenerating the identical key pair. Your device then checks the envelope’s authentication tag: if the password was right, the tag verifies and your device holds the correct private key.
The device and our server then run an authenticated key exchange using those keys, agreeing on a session key while each proves to the other that it’s legitimate. If the password was wrong, the derived keys are simply the wrong keys, the tag doesn’t verify, and nothing useful or sensitive ever crosses the wire.
Why this makes everyone saferSo, why did we decide to use this protocol? Because we wanted to give the best security we have for users using passwords. This means:
The password itself is never transmitted. No plaintext at the server means no accidental logs, no memory scraping, no insider peeking, no “we’ve discovered a subset of passwords were stored in cleartext” blog post two years from now. On-mass precomputation of passwords is dead. Because part of the derivation depends on a secret key held by the server, attackers can’t build dictionaries of passwords in advance. They have to steal the database and the server secret first, and only then start guessing: per user, from scratch, against a memory-hard function. A breach, hence, then becomes a slow, expensive, per-account per-user grind. Login isn’t the end, it’s the beginning. OPAQUE also gives the client an export key: a strong secret derived from your password that the server never learns. That’s a key you can use to encrypt data end-to-end, with nothing to manage beyond the password you already remember and know. What OPAQUE doesn’t doWhile using OPAQUE means that we are using very cool cryptography, it still has some caveats.
It doesn’t stop phishing on its own. If an attacker controls the page or app you’re typing into, they can capture the password before any protocol runs.
It doesn’t make weak passwords strong. “password123” still falls to an online guessing attack, which is why Brave Accounts rate-limits and asks for strong passwords.
After a full server compromise, a determined attacker can eventually mount an offline per-user dictionary attack. OPAQUE makes that dramatically slower and unparallelizable across users, but it doesn’t make it impossible.
Why we think this is genuinely cool and better for our usersMost security improvements are about reducing the blast radius of a mistake. OPAQUE is about removing the thing that could create that blast. But also, this is a protocol that is composable. Because OPAQUE hands back a session key and an export key, it isn’t just a login box, it’s a key-agreement primitive with a password-shaped front door. That unlocks a lot:
End-to-end encrypted storage, where the encryption key is derived from your password and never touches our infrastructure (this is roughly how WhatsApp built password-protected encrypted chat backups). Device sync and recovery, bootstrapped from something you remember rather than a code you’ll lose. We are also planning on a new version of Sync built on this, so stay tuned, as you’ll soon be able to pair Brave Sync with your Brave Account, and, hence, you will be able to forgo the current QR code pairing process and instead just log in to bring end-to-end-encrypted sync to a new device. An account-less sync option will continue to be available and fully supported, so if you don’t want an account to use our services, you can still do it!Brave Accounts serves as the foundation for our new Email Alias service, and it will support a growing number of future Brave services as well.
Getting startedBrave Accounts is available today, so try it out! You can go to brave://settings/getStarted and follow the banner in order to create an account.
You can give us feedback on the support form, GitHub, or any of our social media channels.
This is the 39th post in an ongoing series describing new privacy features in Brave. This post describes work done by Pavel Beloborodov (Sr. Software Engineer), Tarik Demirović (Sr. Automation and Infrastructure Engineer), Harold Spencer Jr. (Sr. Staff Engineer) and Agustín Ruiz (DesignOps Lead). Arthur Edelstein (ex-Brave Sr. Research and Privacy Engineer) contributed as well. It was written by Shivan Kaul Sahib (VP, Privacy and Security).
Starting with today’s desktop version 1.94, the Brave browser is offering Email Aliases to allow you to sign up for online services without revealing your personal email address. Email Aliases can keep your email free of spam, and help you protect your privacy by generating unique email addresses that forward to your primary email inbox.
How your email address can be used to track you across the WebYour email address is a durable, universal identifier. When shared with websites, it can be used for tracking your activity across the Web. Ad tech companies like Google, Meta, and LinkedIn publicly promote how businesses can upload email addresses to match customers against their own user profiles. While Brave offers best-in-class protections against third-party trackers like Meta Pixel that are embedded on websites, your data can still be shared using techniques like server-side matching.
For example, imagine you want to buy a pair of trail running shoes from amazingshoes.com, and the website asks for your email address when signing up. This by itself isn’t suspicious, since the website needs to know where to send your receipt. But amazingshoes.com also uses Meta ads, so upon receiving your address it also uploads your email address to Meta’s server-side audience-matching tool. Meta already has that exact email address on file from the Facebook account you created years ago. The two records match, and Meta now knows that you, specifically, bought expensive trail running shoes. Since it’s happening server-side, none of this traffic goes through your browser, so blocking trackers on the page can’t prevent this action.
Worse, websites vary widely in how well they protect the data they collect. If a website you signed up for is hacked, your information can be leaked and end up with data brokers or worse. Your email address then circulates far beyond the company you originally trusted with it, and can show up in phishing campaigns for years afterwards.
We built Email Aliases to plug this privacy hole. Email Aliases is integrated into Brave, which means you can generate privacy-protecting email addresses right from a website’s sign-up form. These aliases then forward to your real, primary email address, which remains hidden from websites, thus breaking the cross-website tracking link. The feature can also prevent spam, since you can easily deactivate your email alias and create a new one.
Brave already isolates what websites can store in the browser. Cookies, caches, and network state are partitioned per site, so a tracker can’t use what it stored on one site to recognize you on the next. But partitioning stops at the edge of the browser. It can’t stop two companies from comparing notes on their own servers. Email Aliases extends that same partitioning past the browser.
How to use Email Aliases Creating a Brave AccountIn order to create an email alias, you’ll first need to create a Brave account with an email address and password. Note that this account is separate from the Brave Premium account (which Premium users use for managing subscriptions to some of our services, such as the Brave VPN).
Go to brave://settings/email-aliases and click “Log in or create a Brave account” Provide your email address and a strong password Follow the instructions to verify your email Creating an alias on a websiteOnce you’re logged into your Brave account, simply click into an email field on any website to create an alias.
Right click (context menu)If the “New Email Alias” hint doesn’t appear, you can right-click the email field and select ‘New Email Alias’ to create one manually.
Managing aliasesYou can manage all your aliases by going to Settings > Autofill & Passwords > Email Aliases (or directly follow the link at brave://settings/email-aliases).
Why do I need a Brave Account to use the Email Aliases feature?Under the hood, Email Aliases uses Brave Accounts, a brand-new way of signing into Brave using an email address and password. Email Aliases considers the email address associated with your Brave Account as the primary email address, and forwards all email delivered via your aliases to that primary email address.
Brave Accounts uses OPAQUE, a recently standardized cryptographic protocol, so your password is never sent to Brave’s servers. For more information on Brave Accounts, check out our blog post: “Brave Accounts: your password never leaves your device, ever.”
What information can Brave see if I use Email Aliases?As with everything we do, Brave’s goal is to protect user privacy. Once you sign up for Email Aliases, we’ll securely store the email address associated with your Brave Account and any email aliases that you generate. All data is encrypted-at-rest. Emails sent to an alias are forwarded to your primary email address.
Brave doesn’t read the contents of emails sent to an alias. We only process emails to perform standard spam and virus filtering (we need to do this to maintain our status as a reputable email provider). Once an email is delivered, it is deleted from our servers within seconds.
If you add notes to an alias (e.g. “Throwaway account for SendMomFlowers.com”), those notes are stored locally on your device. If you turn on Brave Sync, your notes will be encrypted end-to-end (i.e. hidden even from Brave) between devices on the same Sync chain. Only you can decrypt or read these notes.
For more details, see the section for email aliases in our privacy policy and our support page.
What’s next for Email AliasesIn this initial release, we’re offering everyone the option of five free email aliases. Running a mail forwarding service has ongoing costs, so we’re starting small while we gather feedback on how people use the feature. We’re working hard to bring Email Aliases to mobile, and we plan to offer a Premium version of the feature in the future.
During this phase, some Brave-forwarded emails might go to your spam folder, as we build up our reputation score as a mail provider. If that happens, please mark the message as “not spam.” This ensures that future emails get routed correctly and improves our sending reputation. If you find that too much mail is going to spam, please let us know.
You can share feedback on the support form, GitHub, or any of our social media channels.
a16z General Partners Martin Casado, Sarah Wang, and Matt Bornstein unpack the story of Cursor: how a small, product-obsessed team entered one of the most competitive markets in technology, took on incumbents with seemingly unbeatable advantages, and repeatedly made decisions that ran against conventional startup wisdom.
They revisit the early bet that the interface between humans and AI would matter more than building a coding-specific foundation model, why Cursor built its own product rather than a VS Code plugin, and how the founders' ability to say "no" became one of the company's defining strengths. They also discuss Cursor's rapid evolution from IDE to agent and model platform, and why the team was willing to cannibalize its own products as AI capabilities improved.
The conversation gets into what founders can learn from Cursor's approach to competition, hiring, enterprise sales, M&A, and company culture, including why the team remained unfazed by competitors from Microsoft to Anthropic and how its obsessive focus on product ultimately extended into every part of building the company.
Resources:
Explore Cursor Compile: https://cursor.com/compile
Follow Martin Casado on X: https://x.com/martin_casado
Follow Matt Bornstein on X: https://x.com/BornsteinMatt
Follow Sarah Wang on X: https://x.com/sarahdingwang
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Anish Acharya joins Jen Kha to break down the next frontier of AI, from the evolving model landscape and open-source AI to why the application layer, and consumer AI in particular, may be entering a new phase.
Anish explains why he believes there will be multiple winners at the model layer, why traditional moats like network effects, scale, and brand still matter, and how companies can choose between frontier and open-weight models depending on the economics of the task. They also explore why models are increasingly specializing, and how applications can combine different types of intelligence to create products that are more valuable than any single model.
The conversation then turns to consumer AI: personal agents that can shop and manage your inbox, coding tools enabling a new generation of small businesses, and why Anish thinks we're seeing a renaissance for consumer builders. They also discuss the changing economics of AI software, the rise of "luxury software," and why the biggest risk for today's founders may no longer be thinking too big, but thinking too small.
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
a16z General Partners Martin Casado and Erik Torenberg are joined by Board Partner Steven Sinofsky to explore what recent breakthroughs in AI and mathematics tell us about where the technology is headed, and whether some of the basic assumptions that have governed computing for decades are starting to break.
Martin and Steven debate whether AI's progress in mathematics represents a genuine leap in reasoning or simply a new tool for solving problems at a higher level of abstraction. From the four-color theorem and early computers to graphing calculators and today's models, they trace how new technologies have repeatedly changed which problems humans need to solve themselves, and ask what makes this moment different.
The conversation then turns to one of the biggest shifts in AI: problems that were once constrained by engineering talent can increasingly be attacked with capital and compute. They discuss what that means for startups versus incumbents, venture capital, the coming wave of AI applications, and why pouring billions into increasingly capable models may force us to rethink what these systems can ultimately accomplish.
Resources:
Follow Martin Casado on X: https://x.com/martin_casado
Follow Steven Sinofsky on X: https://x.com/stevesi
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Daisy Wolf and Eva Steinman are joined by Engy Ziedan, co-founder and Chief Scientific Officer of Protege, to discuss why medical AI has a measurement problem, and why scoring well on a benchmark doesn't necessarily mean a model is ready for the hospital.
Engy explains why healthcare AI needs independent evaluations that go beyond static exams and measure how models actually perform in real-world clinical workflows. They explore the risks of subtle bias and misalignment, why the same model can rank differently depending on how it's prompted or tested, and what happens as AI becomes more personalized and changes faster than traditional healthcare quality systems can keep up.
The conversation also gets into Protege's role as an independent evaluator, how contaminated training data can undermine benchmarks, and why the future of medical AI may require continuous monitoring rather than occasional testing.
Resources:
Read our insights piece: https://www.a16z.news/p/the-oracle-problem-an-invisible-bottleneck
Follow Engy Ziedan on X: https://x.com/engyziedan
Follow Daisy Wolf on X: https://x.com/daisydwolf
Follow Eva Steinman on X: https://x.com/evajsteinman
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Martin Casado joins MTS hosts Theo Jaffee and Sophia Dew to unpack where value is actually accruing in AI, why this technology cycle looks fundamentally different from previous waves, and whether the frontier labs will ultimately capture most of the market.
Martin explains why AI has turned venture into a scale-up capital game, where small teams can productively deploy extraordinary amounts of money, and why the relationship between capital, innovation, and growth has never been tighter. He lays out the case both for and against the frontier labs dominating AI, the role of open-source and specialist models, and why applications are increasingly capturing more value.
The conversation also explores model routing, AI economics, founder-market fit, and why Martin believes this may be the biggest unlock of wealth he's seen since the 1990s.
Resources:
Follow Martin Casado on X: https://x.com/martin_casado
Follow Theo Jaffee on X: https://x.com/theojaffee
Follow Sophia Dew on X: https://x.com/sophiadew
Follow MTS on X: https://x.com/mtslive
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
a16z's Joel De La Garza is joined by Aaron Zollman, Deputy CISO at Microsoft Gaming, to discuss how security teams can embrace AI agents without losing control.
Aaron shares Microsoft's experience with OpenClaw, from the initial instinct to ban it to figuring out how to make it safe to use. They unpack what agents mean for identity, permissions, containerization, and monitoring, as well as how AI is shifting the CISO's role from saying "no" to safely enabling new technology.
They also explore whether AI could help defenders patch vulnerabilities as quickly as they're discovered, and why new AI threats don't make the old security problems go away.
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
The PIVX ecosystem continues to make progress across network participation, market activity, privacy-focused development, and community engagement. Here’s a look at the latest updates.
Masternode Network
The PIVX masternode network currently stands at approximately 1,888 masternodes, with an estimated annual reward of 15.43% and around 18.17% of PIVX supply locked.
Masternodes continue to play an important role in supporting network security, decentralized governance, and participation across the PIVX ecosystem.
Market Update
PIVX is currently trading around $0.0118, with continued activity from traders and holders despite broader market volatility.
24-hour trading volume is approximately $213,000, representing an increase of around 66% from the previous day. MEXC remains an active market for PIVX, with the PIVX/USDT pair among the leading trading pairs.
Ecosystem & Community
PIVX continues to expand access to $PIVX across the broader crypto ecosystem.
PIVX is available on MEXC, providing another option for users to trade PIVX alongside thousands of other digital assets, with competitive trading fees and a wide range of markets.
The PIVX Medium publication also recently featured an article examining the public reaction to destroyed traffic cameras and the broader questions surrounding surveillance, privacy, and financial freedom. The discussion reflects the importance of maintaining individual choice as technology becomes increasingly integrated into everyday life.
$PIVX is also available through ChangeNOW, giving users another option for swapping PIVX. As a Proof-of-Stake blockchain, PIVX combines staking and community governance with optional privacy through its SHIELD protocol.
Community participation remains an important part of the PIVX ecosystem. Through PIVX.org, Discord, and Telegram, community members can connect, discuss privacy and cryptocurrency, share ideas, and contribute to ongoing conversations around the future of decentralized finance.
Looking Ahead
PIVX remains focused on strengthening its network, expanding accessibility, and advancing privacy-focused technology while keeping financial freedom and user choice at the center.
These developments reinforce PIVX's position as a leading privacy-focused cryptocurrency, with growing accessibility, stronger educational outreach, and continued advocacy for financial freedom.
#PIVX Your Rights. Your Privacy. Your Choice.
PIVX Weekly Ecosystem Update was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
Elena Burger is joined by a16z’s Angela Strange and Gabriel Vasquez to discuss the rise of the "borderless founder": entrepreneurs who bring the networks and insights of their home markets together with the talent, capital, and speed of Silicon Valley to build global companies.
Angela and Gabriel trace how a16z's international investing efforts grew from early work in Latin America into a broader global network, and why AI has accelerated the flow of founders and talent between Silicon Valley and startup ecosystems around the world. They explore the advantages borderless founders can bring, from differentiated talent networks and early customers to strong local brands and communities that help open doors across markets.
They also discuss how founder diasporas can function like powerful alumni networks, why spending time in Silicon Valley can help founders recalibrate around speed and ambition, and how the next generation of global companies may increasingly be built across multiple countries from day one.
Resources:
Read Angela Strange and Gabriel Vasquez's piece on Borderless Founders: https://www.a16z.news/p/rise-of-the-borderless-founder
Follow Angela Strange on X: https://x.com/astrange
Follow Gabriel Vasquez on X: https://x.com/GEVS94
Follow Elena Burger on X: https://x.com/VirtualElena
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
a16z General Partner David George is joined by Grant LaFontaine, co-founder of Whatnot, to unpack how a marketplace that started with collectibles evolved into one of the world's leading live shopping platforms.
Grant traces the company's origins from selling Pokémon cards online as a kid to discovering live commerce by watching Whatnot's earliest customers hack together sales on social media. They discuss why Whatnot thinks less like a traditional e-commerce marketplace and more like a digital shopping mall, where discovery, entertainment, community, and commerce all happen at once. Today, users spend roughly 95 minutes a day on the platform, and most aren't even buying something on a given day.
They also explore how Whatnot is enabling small businesses to reach global audiences, expanding from collectibles into categories like fashion, food, and golf, and using AI to make sellers more efficient without replacing the human connection at the center of the experience.
Resources:
Follow Grant LaFontaine on X: https://x.com/GrantLaFontaine
Follow David George on X: https://x.com/DavidGeorge83
Follow Whatnot on X: https://x.com/whatnot
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
a16z's Joel De La Garza is joined by Nick Warner of Neo and Max Pollard of Cotool to discuss what happens when cybersecurity tools built to defend against humans and malware suddenly have to contend with AI agents. As frontier models become more capable of finding and exploiting vulnerabilities, many of the assumptions underlying traditional security are beginning to break.
They explore why guardrails designed to stop AI-powered attackers can also prevent security teams from doing their jobs, why defenders increasingly need access to multiple models, and how agentic software creates an entirely new endpoint security problem. They also discuss why static signatures and even newer techniques like honeypots are struggling in a world where software can reason and act autonomously.
Recorded around Black Hat, the conversation looks at how security teams are adapting in real time and why the same AI capabilities creating new attack surfaces could ultimately give defenders their biggest advantage yet.
Resources:
Follow Nick on LinkedIn: https://www.linkedin.com/in/nicholaswarner/
Follow Max on LinkedIn: https://www.linkedin.com/in/mmpollard/
Follow Joel De La Garza on LinkedIn: https://www.linkedin.com/in/3448827723723234/
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
What a wave of destroyed traffic cameras says about the money in your pocket
Over the past few months, people across the United States have taken saws, paint, and in at least one case a truck, to a company’s traffic cameras. Not vandals in the random sense, organized, repeated, deliberate. In upstate New York, someone cut a Flock Safety camera down with an electric saw. In Oakland, someone threw paint over the lens. In Idaho, someone drove a truck through one. In Florida, a man sits in a lawn chair holding a piece of cardboard on a pole, just to block the view.
Flock Safety runs roughly 120,000 automated license plate readers across 49 states, under contract with more than 5,000 law enforcement agencies. Every camera logs every car that passes, make, model, color, bumper stickers, scratches, into a searchable, shared, nationwide database. It was sold to cities as a tool for finding stolen vehicles. Then a Milwaukee detective was arrested this year after admitting he used the system to secretly track his romantic partner 124 times, and her ex 55 times. Then reporting connected the network to immigration enforcement, sweeping up people who’d never been suspected of anything resembling the crimes the system was built to catch. Cities started canceling contracts. Just this month, under mounting pressure, Flock itself announced it would start requiring a case number on every search and cut its default data retention from 30 days down to 7.
People noticed. People got angry enough to act. That’s the part of this story that should actually surprise you, not that a surveillance company overreached, but that the public still has the reflex to notice when it does.
The much older, much quieter version of the same story
Now ask yourself a harder question: when was the last time you got angry about your bank.
Not about a fee, or a hold on your funds, or bad customer service. About the fact that every transaction you make already runs through a private company that logs it, flags it, and hands portions of it to the government, often without you ever knowing, often without anyone needing a warrant to ask.
I’m old enough to remember when that wasn’t true. Cash was traceless. You paid for something, the exchange happened, and the only record of it lived in two people’s memory, if that. There’s hardly any cash left in ordinary life now, most of it pushed out gradually, one contactless terminal and one “cash discouraged” sign at a time, until an entire generation has grown up never once transacting without a company somewhere in the middle keeping a record.
That system has existed for decades. It’s called anti-money-laundering and know-your-customer compliance, AML/KYC, and it doesn’t announce itself with a physical box mounted on a pole. It arrives as a form you fill out to open an account. A photo of your ID to sign up for an exchange. A “for security purposes” notice you click past without reading. Nobody drives a truck through it, because there’s nothing to drive a truck through. It isn’t a camera. It’s every bank, every card processor, every centralized exchange, quietly built to watch, by design, from the start.
Here’s what that apparatus actually catches. Global spending on financial crime compliance topped $200 billion in 2023, against an estimated $3.1 trillion in illicit financial flows that same year, meaning the entire system, at its most generous accounting, intercepts something in the low single digits of what it claims to target. A U.S. Government Accountability Office report found law enforcement accessed less than 3% of the currency transaction reports banks filed between 2014 and 2023. A Bank Policy Institute survey of its own members found that of roughly 16 million alerts and over 640,000 suspicious activity reports filed, a median of just 4% of those reports, and well under 1% of currency transaction reports, ever led to a follow-up from law enforcement at all. Meanwhile, the UN’s own estimate for how much money gets laundered globally every year hasn’t meaningfully moved: still 2 to 5% of global GDP, somewhere between $800 billion and $2 trillion, flowing regardless.
That’s not a system straining to catch criminals and mostly succeeding, with some acceptable overhead. That’s a dragnet thrown over everyone, catching almost nothing it was built for, while the overwhelming majority of what it collects sits unused, attached to people who did nothing wrong.
It’s Flock’s exact shape. Built narrow, sold as safety, expanded quietly, justified after the fact by the small number of real hits buried in a mountain of irrelevant surveillance on ordinary people. The only difference is that Flock is new enough, and physical enough, to make people angry. The financial version has had forty years to become furniture.
Institutions get fined. Individuals mostly don’t
There’s a second pattern worth naming here, because it shows up in both stories. When the surveillance apparatus does catch something real, and sometimes it does, the consequences tend to land on the institution’s balance sheet, not on the people who ran it.
HSBC admitted in 2012 to laundering at least $881 million for the Sinaloa cartel and moving money for sanctioned states. It paid a $1.92 billion fine. No HSBC banker went to prison. Years later, journalists found HSBC had kept moving suspicious money through its accounts even while under a court-monitored probation from that very settlement. Swedbank was fined roughly $386 million in 2020 over Baltic money-laundering failures tied to more than $40 billion in high-risk transactions; its CEO was fired, then years later acquitted in court of any personal wrongdoing. Danske Bank’s Estonian branch moved an estimated €200 billion in suspicious payments, one of the largest laundering scandals in European history, and the personal reckoning for the people who ran it has been, by any measure, modest next to the scale of what happened.
The fine gets paid by shareholders. The system gets a little more paperwork bolted onto it. And the paperwork lands, as it always does, on everyone else, the ordinary account holder who now answers more questions to open a checking account than the institutions moving billions ever really had to answer for afterward.
The frog doesn’t know the water is boiling
The old metaphor gets used so often it’s become a cliché, but it’s a cliché because it’s accurate: a frog dropped into boiling water jumps out immediately. A frog sitting in water that’s heated gradually, degree by degree, stays until it’s too late to matter.
Flock is the sudden temperature spike, visible, physical, recent enough that people still remember when it wasn’t there, and angry enough to reach for a saw. Financial surveillance is the slow heat. It arrived one form, one regulation, one “security feature” at a time, over forty years, until logging in to a KYC’d exchange or swiping a card feels less like surveillance and more like simply how the world works. Even those of us old enough to remember cash rarely stop to notice the water rising, because no single step ever felt like the moment worth getting angry about. And anyone younger than that has never known anything else, so there’s no “before” to miss in the first place.
The EU’s current fight over message scanning shows the same dynamic playing out in real time, and shows it isn’t hypothetical. In July 2026, more members of the European Parliament voted to kill a private-message-scanning regime than voted to keep it, 314 against to 276 for, and it passed anyway, because the threshold for actually rejecting it was set deliberately out of reach. Suspicionless scanning of private messages is now legal in the EU until at least 2028, over the objection of the actual majority who voted. Critics have pointed out for years that scanning and real encryption cannot coexist as design goals, you get one or the other. The public rejected it. The system absorbed the rejection and kept running anyway. That’s not a conspiracy. It’s just how gradually-built surveillance infrastructure tends to survive: not because people approve of it, but because by the time anyone’s paying attention, it’s already load-bearing.
Why the fix can’t be a better cage
Flock’s response to the backlash was to add rules: require a case number, shorten retention. That’s a real improvement, and it will probably reduce some abuse. It will not change what the system fundamentally is, a searchable record of where you drove, now with slightly better paperwork attached to who gets to look.
That’s the trap with reform. You can tighten the rules around a surveillance system, and people will, and should, keep pushing for exactly that. But tightening the rules doesn’t remove the data. The data still exists, still gets collected, still sits there waiting for the next administration, the next court order, the next quiet policy change, the next employee who decides the rules don’t apply to them this once. A cage with better locks is still a cage.
The only real exit is a system that doesn’t generate the data in the first place. And here it’s worth being honest about something a lot of people assume without checking: crypto, as most of the world encounters it, is not that exit. Bitcoin was built, in part, as a stand against exactly this kind of financial surveillance, a way to transact without a bank in the middle. But every Bitcoin transaction is written permanently onto a public ledger anyone can read, and in the years since, an entire industry of blockchain analysis firms has grown up around mapping that ledger to real identities, increasingly with AI-assisted clustering that gets faster and more accurate every year. The same tool sold to police as a Flock subscription has a direct financial cousin: firms like Chainalysis sell exactly this kind of blockchain surveillance to law enforcement and tax agencies as a product. What started as a rebellion against financial surveillance has become, for anyone who didn’t take specific precautions, one of the most thoroughly traceable ledgers of financial activity that has ever existed. Not because Bitcoin failed technically. Because transparency by default and privacy are not the same design goal, and Bitcoin was built for the first one.
The real exit isn’t a public ledger with better manners either. It’s a system that generates no financial record at all for the transactions you choose to shield. PIVX’s shielded transactions, built on zero-knowledge cryptography, don’t hide a trail. There’s no trail to hide. Nothing gets logged that could later be searched, subpoenaed, breached, or handed over quietly under a policy nobody voted on. It isn’t a better version of the bank’s ledger, and it isn’t Bitcoin’s transparent ledger wearing a disguise. It’s the absence of one, by design, for the person who chooses it.
Getting out of the pot
None of this requires paranoia, and it doesn’t require assuming every bank employee or every government agency is acting in bad faith. Most of the individual people inside these systems are doing ordinary jobs in good faith. The point isn’t that anyone in particular is a villain. It’s that the system itself, whether it’s cameras on poles or ledgers in a database, was built to watch everyone by default, catches remarkably little of what it claims to target, and tends to expand its own reach quietly, one justified step at a time, long after the original narrow purpose stopped being the whole story.
Flock’s cameras got noticed because they’re new, physical, and impossible to ignore once you know where to look. The financial version of the same system has just had a much longer head start on becoming invisible. Recognizing that is the first step. Having somewhere to actually go is the second, and unlike a traffic camera you can’t simply drive around, that second step has to be built into the money itself.
The frog can get out of the pot. It just has to notice the water first.
PIVX. Your Rights. Your Privacy. Your Choice.
To stay on top of PIVX news please visit PIVX.org and Discord.PIVX.org.
The Water Is Already Boiling was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
a16z General Partner David George is joined by Will Gaybrick, President of Product & Business at Stripe, to discuss how AI is changing the way Stripe builds products, organizes teams, and thinks about the future of internet commerce. Stripe has evolved from a payments company into a multi-product financial infrastructure platform, while a new generation of AI companies is growing and monetizing faster than previous software cohorts.
Will explains why Stripe sees AI productivity as an opportunity to build more rather than simply cut costs, including how its internal coding agents now generate thousands of pull requests each week. They discuss creating founder-like agency inside large companies, building smaller and flatter teams, and why Stripe believes dramatically more software will be created as the cost of building continues to fall.
They also look ahead to agentic commerce, why checkout pages could disappear, the potential return of micropayments, stablecoins as infrastructure for a global economy, and a future where AI agents increasingly buy software and services from other machines.
Resources:
Follow Will Gaybrick on LinkedIn: https://www.linkedin.com/in/william-gaybrick-5730347/
Follow Will on X: https://x.com/gaybrick
Follow David George on X: https://x.com/DavidGeorge83
Follow Stripe on X: https://x.com/stripe
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Another week brings fresh developments across the PIVX ecosystem. From network participation and market activity to wallet improvements, regulatory developments, and community-driven growth, here’s a look at what’s been happening across the ecosystem.
Masternode Network
The PIVX masternode network currently stands at approximately 1,838 masternodes, with an estimated annual reward of ~17.16% and approximately 17.37% of the PIVX supply locked.
While participation has adjusted from higher levels earlier in the year, masternodes continue to play an important role in maintaining network security and supporting the decentralized PIVX ecosystem. For node operators, the current reward structure also continues to provide an attractive incentive for network participation.
Weekly Market Pulse
PIVX remained around the $0.02 level throughout the week, currently trading at approximately $0.018–$0.0182.
Market conditions continue to evolve, but PIVX maintains an active community of traders, holders, and privacy advocates. Continued development across the ecosystem remains an important foundation for the project's long-term growth.
Trading Activity
Trading activity remained steady across the markets supporting PIVX, with approximately $630K–$770K in 24-hour trading volume at the time of this update.
The continued trading activity demonstrates that there remains an active market for PIVX while the ecosystem continues expanding its accessibility and utility.
Ecosystem & Community
Binance Delisting Reminder
The PIVX community was reminded this week about Binance's upcoming changes concerning PIVX.
Binance will stop accepting PIVX deposits on August 18, 2026 at 03:00 UTC, while withdrawals will end on October 17, 2026 at 03:00 UTC.
PIVX users holding funds on Binance should take the necessary steps to move their assets before the applicable deadlines and explore alternative options within the broader PIVX ecosystem.
Regulatory Developments
Regulation remained an important discussion across the wider crypto industry this week as the U.S. Senate delayed consideration of the CLARITY Act until September.
The continued push for clearer regulatory frameworks highlights the importance of financial technologies that preserve individual choice, privacy, and control while the industry navigates an evolving regulatory landscape.
MyPIVXWallet 3.0
The latest MyPIVXWallet 3.0 update continues to improve the experience for PIVX users, introducing new features designed to make managing PIVX more convenient and accessible.
For those who haven't explored the latest release yet, visit myPIVXwallet.org to check out the new features and experience the updated wallet.
Building Through the PIVX DAO
At the heart of PIVX is a community willing to turn ideas into action.
The PIVX DAO continues to bring together builders, contributors, developers, and community members who are working toward a shared vision. Through decentralized participation and collective effort, ideas can become contributions, and contributions can become meaningful progress for the ecosystem.
Looking Ahead
PIVX continues moving forward through development, community participation, network growth, and its commitment to financial privacy.
With an active masternode network, ongoing wallet development, expanding accessibility, and a community continuing to build together, the foundation for the next chapter of PIVX remains strong.
#PIVX — Your Rights. Your Privacy. Your Choice.
PIVX Weekly Ecosystem Update was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
Ben Horowitz, Travis Kalanick, and Erik Torenberg take the stage at Atoms' launch event for a candid fireside conversation about entrepreneurship, company building, and why Kalanick believes the next industrial revolution will be powered by AI.
They revisit pivotal moments from Uber's history, including the decision not to acquire Lyft, lessons from scaling one of the world's fastest-growing companies, and how Kalanick has evolved as a founder. The conversation also explores Atoms' vision for industrial AI, why software is moving into the physical world, what it takes to build enduring company cultures, and why Kalanick believes the biggest opportunities of the next decade lie in transforming industries like food production, mining, and manufacturing.
Resources:
Follow Travis Kalanick on X: https://x.com/travisk
Follow Ben Horowitz on X: https://x.com/bhorowitz
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Elena Burger is joined by a16z's Andy McCall and Joe Schmidt to break down two very different ways AI startups can go to market: the lighthouse and the landgrab. Should founders win a handful of marquee customers whose credibility unlocks an entire industry, or move quickly across a broad market where the ROI already speaks for itself?
Drawing on Joe's Lighthouse or Landgrab framework and Andy's experience building sales organizations at Samsara and Meraki, they explore how founders can determine which strategy fits their market, when social proof matters more than math, and why the current rush to adopt AI has created a rare window for startups to sell big software again.
They also get tactical on POCs, pricing and ACV, hiring early sales teams, moving from mid-market to enterprise, and why founders shouldn't spend too much time perfecting their GTM strategy before talking to customers. As Andy puts it: spend 1% of your time on strategy and 99% executing.
Resources:
Read Joe Schmidt's "Lighthouse or Landgrab": https://a16z.com/lighthouse-or-landgrab-how-to-pick-your-ai-sales-strategy/
Follow Andy McCall on LinkedIn: https://www.linkedin.com/in/amccall/
Follow Joe Schmidt on X: https://x.com/joeschmidtiv
Follow Elena Burger on X: https://x.com/VirtualElena
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
This is the 38th post in an ongoing series describing new privacy features in Brave. This post describes work done by Rohit Agarwal (Senior Software Engineer) and Peter Snyder (Principal Researcher), and was written by Shivan Kaul Sahib (VP, Privacy and Security).
Starting in version 1.93, Brave is rolling out new protections against GPU and graphics-driver fingerprinting. WebGL and WebGPU APIs expose detailed information about users’ graphics cards and drivers that tracking companies use for browser fingerprinting. Brave now de-identifies the vendor and renderer strings these APIs report, and adds noise to the list of supported extensions to combat fingerprinting while preserving website functionality.
These protections are on by default in our desktop and Android browsers. This will be a phased rollout over the next several days, so please check again soon for the new functionality if you don’t see it right away.
Your GPU can be a fingerprintThe WebGL and WebGPU APIs let websites draw hardware-accelerated graphics. These APIs make the Web a more colorful place (literally), helping website developers design engaging experiences. As a browser vendor, we care deeply about this open and vibrant Web, since we want people to use it instead of walled-garden app stores.
Unfortunately, graphics APIs are also used by third-party trackers to fingerprint users. Browser fingerprinting is a tracking technique that combines many small, device-specific signals into a single identifier that follows a user across the Web, without cookies and without consent. WebGL and WebGPU APIs expose details about the underlying hardware, which makes them particularly rich sources of these signals: a script can learn the exact vendor and model of the GPU, the graphics driver, and the precise set of features the hardware supports. For example, the WebGL API lets websites query for highly-detailed debug strings like 'ANGLE (Apple, ANGLE Metal Renderer: Apple M5 Max)' on an Apple MacBook Pro with an M-series chip, as tested on EFF’s excellent Cover Your Tracks tool; interestingly, this debug extension was originally exposed for Google Maps by Google Chrome before being made available for all websites. The same WebGL context also reports its full list of supported extensions, a set that varies by GPU and driver and that trackers can hash into a compact identifier. And the newer WebGPU API exposes its own hardware descriptors, returning the adapter’s vendor, architecture, and device (for example {vendor: 'apple', architecture: 'metal-3'}). These fingerprinting signals are stable across time, since you’re unlikely to change your GPU hardware on a day-to-day basis.
We ran a small Web crawl to see how top websites use these APIs, analyzing the stack trace right before each call. We found that most websites were using these APIs exclusively for browser fingerprinting.
How Brave protects youBrave now scrubs these signals. We:
Replace the WebGL vendor and renderer strings with a single generic string, ensuring that all Brave users get identical values (details), Empty out the WebGPU adapter descriptors (details), Inject randomization into the WebGL extension list so that hash-based fingerprinters see a different value per session, per site (eTLD+1) and per storage area (details).As with all of Brave’s privacy protections, the goal is to deny trackers a stable identifier while leaving websites everything they need to render rich experiences for their users.
Protecting privacy without breaking the WebWe’ve rolled out these protections across our Nightly and Beta channels over the last few months, and are optimistic that our approach reduces the chance of breakage on most websites while effectively combating fingerprinting.
Brave has the ability to adjust these protections on a per-site basis if we discover a site that genuinely breaks. Users always stay in control: on any site, they can turn off these graphics protections, disable fingerprinting protection entirely, or switch off Shields altogether.
Try it yourselfThe easiest way to see these protections in action is EFF’s Cover Your Tracks, which reports the WebGL vendor and renderer strings your browser exposes along with how identifying they are. Once the feature is fully rolled out, you’ll see the vendor and renderer collapse to a generic value.
Future workGraphics APIs remain an active area of fingerprinting research, and we’ll keep expanding coverage to any new signal these interfaces expose. We have plans to also randomize WebGPU’s supported extensions.
Brave has long led the industry in fighting fingerprinting, providing best-in-class protections enabled by default. This latter part is important! Most other browsers that care about user privacy fall into one of two buckets: either opt-in protections (hiding them behind a special mode or a feature flag for expert users) or approaches that sacrifice usability (breaking functionality altogether). Brave’s privacy philosophy is that this is a false tradeoff. Users deserve strong privacy on their favorite websites without having to enable a special toggle or mode or download a Web extension (which comes with its own set of security and privacy issues). Privacy is for everyone, not just the most technical users.
As a reminder, Brave already protects you from state-based tracking (like cookies) and also blocks known-dangerous scripts and resources from loading in the first place; a win-win-win-win for privacy, security, performance and usability.
Anish Acharya is joined by Garry Tan, President and CEO of Y Combinator, for a conversation about how AI is rewriting the startup playbook, why founders should be more ambitious than ever, and what two decades of Silicon Valley booms, busts, and missed opportunities have taught Garry about building what's next.
Garry reflects on turning down an early opportunity to join Palantir, why chasing what's "hot" is often the wrong strategy, and why the best ideas tend to begin with people pursuing strange, earnest obsessions outside the mainstream. They also explore how AI changes the economics of company building, why traditional SaaS may be losing its advantage, and how tiny teams equipped with hundreds of agents can build businesses at a scale that once required entire organizations.
The conversation goes deeper into agentic companies, taste and agency, why "a markdown file is an employee," and how AI could remove layers of bureaucracy that have historically limited organizations. Garry and Anish also discuss the future of consumer AI, the coming "harness wars," why AI adoption may take longer than Silicon Valley expects, and what the next generation of founders can build with intelligence that was unimaginable just a few years ago.
Resources:
Follow Garry Tan on X: https://x.com/garrytan
Follow Anish Acharya on X: https://x.com/illscience
Follow Y Combinator on X: https://x.com/ycombinator
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Panther Protocol Foundation and Igra Network are exploring the potential to bring Panther’s privacy-preserving infrastructure to the Kaspa ecosystem.
The collaboration will gather ecosystem feedback and assess demand for a potential Panther deployment on Igra, before exploring the technical, operational and governance arrangements for a deployment.
A deployment on Igra would expand Panther’s multi-chain reach beyond its Mainnet deployment on Polygon and upcoming deployment on Base.
Exploring Private DeFi for KaspaKaspa has established itself as one of the fastest and most decentralized proof-of-work networks in the industry. Until recently, however, the ecosystem lacked a native EVM execution environment capable of supporting sophisticated decentralized finance applications.
Igra changes that.
Built on Kaspa's BlockDAG architecture, Igra is a high-performance, EVM-compatible execution layer delivering more than 3,000 transactions per second, rapid transaction confirmation, and a decentralized architecture designed to minimize maximal extractable value (MEV) and censorship risks. It brings Ethereum-compatible smart contracts to the Kaspa ecosystem while inheriting the security of Kaspa's proof-of-work network.
Panther complements that vision by providing privacy-preserving infrastructure for decentralized finance. Together, Igra and Panther can enable developers and users to build and interact with DeFi applications without exposing their complete on-chain financial activity.
Privacy for the Next Generation of DeFiPanther enables users to transact privately while remaining capable of demonstrating compliance where required through zero-knowledge cryptography.
Rather than forcing users to choose between complete transparency and complete anonymity, Panther enables selective disclosure, allowing users to demonstrate specific facts about themselves or their transactions without revealing unnecessary personal or financial information.
This creates new opportunities for both retail and institutional participants seeking greater financial privacy without sacrificing interoperability or regulatory flexibility.
Potential Use Cases on IgraPrivate Asset Management
Panther enables the creation of privacy-preserving environments where participants can manage digital assets without publicly revealing balances or transaction history.
Independent operators can establish their own Panther deployment, define supported assets and compliance requirements, and facilitate private interaction between trusted counterparties while retaining operational independence.
Confidential DeFi Trading
Through zSwap, users can privately exchange supported assets while preventing observers from linking deposits, trades and withdrawals.
Panther automatically aggregates available liquidity and identifies efficient execution routes while preserving transaction confidentiality.
Private Transfers
Panther's Multi-Asset Shielded Pool (MASP) enables confidential transfers between participants without publicly exposing sender, recipient or transferred assets on-chain.
Users interact through Panther's shielded account system, enabling private transfers and privacy-preserving asset management while maintaining the ability to demonstrate compliance where necessary using zero-knowledge proofs.
A Modular Deployment ModelPanther has been designed around a modular governance and deployment model that allows different ecosystems to operate independently while benefiting from shared protocol development.
The underlying Panther protocol is open source, while Panther Protocol Foundation supports ecosystem development, administers grants, and owns and licenses the proprietary Panther dApp.
Individual ecosystem partners may deploy and operate their own licensed Panther instances, allowing each deployment to develop independently while remaining part of the wider Panther ecosystem.
This approach enables Panther to scale across multiple blockchain ecosystems without centralizing governance, operations or infrastructure.
About Panther Protocol Foundation
Panther Protocol Foundation is a non-profit organization supporting the Panther ecosystem through research, ecosystem funding, software stewardship and open-source development.
The Foundation does not operate the Panther protocol, host deployments, custody assets, execute or intermediate transactions, or provide financial services.
The proprietary Panther dApp is licensed by the Foundation to support independent ecosystem deployments.
Users interact directly with smart contracts from their own wallets, signing every transaction themselves. Compliance credentials are issued and managed by independent third-party providers.
Please review the applicable notices, disclosures and jurisdictional restrictions available through the Panther interface before interacting with the protocol.
For more information, visit panther.org
To learn more about Panther Protocol, visit pantherprotocol.io
Contact
Panther Protocol Foundation
📧 general@panther.org
🌐 panther.org
a16z's Joel De La Garza is joined by Emilio Escobar, Chief Information Security Officer at Datadog, to discuss what it takes to secure a company where nearly every employee is using AI and more than 4,000 engineers are working with coding agents. Rather than trying to block new tools, Emilio explains why Datadog chose to embrace AI early and build the security infrastructure needed to use it safely.
They unpack how AI changes traditional assumptions around data permissions, credentials, developer access, and software supply chains. Emilio shares how Datadog uses role-based MCP servers and ephemeral credentials, as well as an AI "judge" built by his security team to evaluate the intent behind code and agent skills before they enter the environment.
They also discuss why security teams can't afford to wait for commercial solutions to every new AI threat, how the relationship between developers and security teams needs to change, and why Emilio is less concerned about an AI "escaping" than he is about the sheer volume of vulnerabilities AI could uncover.
Resources:
Follow Emilio Escobar on LinkedIn: linkedin.com/in/emilioesc
Follow Joel De La Garza on LinkedIn: https://www.linkedin.com/in/3448827723723234/
Follow Datadog on X: https://x.com/datadoghq
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Today we are releasing Zebra 6.3.0 as a recommended security release. It resolves four security advisories in block synchronization and peer scoring, including a peer-induced delay in tip discovery, a near-tip sync stall, and gaps that let malicious peers get honest peers banned or evade banning, and it hardens inbound ban enforcement. The release also adds a new getdeprecationinfo RPC, new default DNS seeders, and more granular network metrics.
All operators are encouraged to upgrade.
Security Advisories GHSA-g95h-hw6g-pvgv: Coinbase scriptSig Rewrite Delaying Tip Discovery (High)A malicious peer could delay a node’s discovery of the newest canonical block by answering a block-download request with a forged body that still matched the requested hash, since rewriting only the coinbase scriptSig (excluded from the V5 transaction ID) leaves the block hash unchanged. Zebra read the forged far-behind height from the unvalidated body and dropped the block as too old before consensus validation, without scoring the peer or re-requesting the hash until the next sync round. Nothing invalid is accepted, so the effect is a transient delay in tip discovery, worst for nodes feeding a mining backend. Zebra now re-requests the hash immediately and penalizes the peer when a block it already holds proves the claimed height wrong. Thanks to @zakura-security, who reported this issue through an OtterSec engagement on the Zakura fork.
GHSA-qhr3-cvch-5fh2: Far-Ahead Block Scoring Enabling Ban Amplification (Medium)Blocks above the sync lookahead height limit were penalizing the peer that served them, but a FindBlocks response does not record which peer supplied its hashes, so the follow-up block request is routed to an unrelated honest peer. A malicious FindBlocks responder could exploit this to get honest peers scored and banned throughout initial block download, degrading a node’s ability to sync. Zebra no longer scores the serving peer for far-ahead blocks. Thanks to @zakura-security for reporting this issue.
Peers that gossiped consensus-invalid blocks were never scored for misbehavior, because the inbound download path classified the resulting verification failure in a way that skipped scoring entirely, so those peers were never banned. Zebra now scores such peers for misbehavior again. Thanks to @evan-forbes for reporting this issue.
GHSA-h8m8-844p-v3m9: Near-Tip Sync Stall on Singleton FindBlocks Responses (Medium)When a FindBlocks response advertised only a single block hash the node did not already have, Zebra did not download that hash, so a node close to the chain tip could stop advancing and stall its sync. Zebra now downloads a peer’s only unknown block hash from a short FindBlocks response, so near-tip nodes keep following the chain. Thanks to @Maakai123 for originally reporting this issue, and to @ouicate for an independent later report.
Inbound connections are now canonicalized when they are accepted, so an IPv4 peer that connects to a dual-stack listener as an IPv4-mapped IPv6 address (::ffff:A.B.C.D) is keyed on its canonical IPv4 address. Previously the mapped address became the peer set key, so a ban issued for that peer’s IPv4 address did not disconnect it while it stayed connected, and the same peer counted twice toward the per-IP inbound connection limit.
Banning a misbehaving peer now removes every address book entry for that IP, and a banned IP is never selected as a reconnection candidate. Previously an entry on a different port could survive the ban and occupy the first candidate slot until the node restarted. This caused spurious warnings in the log.
Resolved in Zebra 6.2.1; later releases already include it and need no action. (We are only disclosing the advisory now because we were double checking if the fix was thorough.) On networks where NU6.3 (Ironwood) is active, a V6 transaction can carry two Halo2 shielded proofs, but the mempool capped concurrent work by transaction count rather than verification cost, and block and mempool verification shared one unprioritized queue. An unauthenticated peer could flood a node with cheap-to-produce but expensive-to-verify transactions bearing canonically sized invalid proofs, stalling block verification so a constrained node fell behind the chain tip until the flood stopped. Zebra 6.2.1 applies a ZIP-317 fee check before proof verification and disconnects peers that send invalid shielded proofs. Thanks to @craftsoldier for reporting this issue.
New Features End-of-support reportingA new getdeprecationinfo RPC returns the block height and estimated time at which this release will halt for end of support, in zcashd’s end_of_service format. The end_of_service object is only present on Mainnet, where end of support is enforced.
seeder.zec.rocks and seeder.testnet.zec.rocks are now included as default DNS seeders, improving peer discovery for new and recovering nodes.
Prometheus metrics now separate peer connection attempts and terminal outcomes by network, direction, address family, lifecycle stage, and outcome. Version-message metrics report a bounded, self-reported implementation class without using peer IPs or raw user agents as labels. Peer-set, crawler-handshake, and address-book gauges now include a network label, so Mainnet and Testnet values no longer overwrite each other in processes that run both networks.
Bug Fixes Funding stream metadata for NU6.1 and latergetblocksubsidy now returns NU6-era funding stream metadata (recipient names and specification URLs) for NU6.1 and later upgrades. Amounts and addresses were never affected.
Zebra now rejects blocks whose total chain value pool balance would exceed MAX_MONEY, enforcing the cap on the total monetary base.
You can get this release from the GitHub release page, from crates.io, or from Docker Hub.
Consumers of the zebra-consensus crate API should note that the transaction verifier has been split into separate block and mempool verifiers: the removed transaction::Request::Mempool and transaction::Response::Mempool variants are replaced by dedicated transaction::MempoolRequest and transaction::MempoolResponse types. This is an internal change with no operator-facing behavior difference, but downstream library users will need to update. See the zebra-consensus changelog for the underlying API split.
Thank you to everyone who contributed to this release @arya2, @emersonian, @gustavovalverde, @jiehuo100net, @jvff, @oxarbitrage, @syszery and @upbqdn.
Zebra is the Zcash Foundation’s independent, Rust implementation of a Zcash node.
The post Zebra 6.3.0 Release appeared first on Zcash Foundation.
Angela Strange and Gabriel Vasquez are joined by Alejandro Maza Ayala, Chief Product & AI Officer at Kavak, to unpack how the Latin American used-car marketplace rebuilt itself around AI agents, with 96% of customer interactions and 95% of transactions now handled by agents.
Alejandro explains why Kavak decided that simply giving employees AI tools wasn't enough, and instead redesigned the company's systems, teams, and customer experience around agents. They discuss why Kavak spends as much engineering effort on evals as it does building agents, how its AI sellers outperform its human teams, and an experiment where an AI "CEO" increased profits in one city by 50% in its first month.
The conversation also explores what happens to organizational structure when agents do most of the work, why Kavak trains everyone from executives to mechanics to build with AI, and Alejandro's argument that companies looking for incremental AI adoption may be missing the larger opportunity: redesigning the organization itself.
Resources:
Follow Alejandro Maza Ayala on X: https://x.com/alehandromz
Follow Angela Strange on X: https://x.com/astrange
Follow Gabriel Vasquez on X: https://x.com/GEVS94
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Joel De La Garza is joined by Dylan Ayrey, co-founder and CEO of Truffle Security, and Feross Aboukhadijeh, founder and CEO of Socket, to discuss one of the biggest shifts happening in cybersecurity: AI models are no longer just finding vulnerabilities—they're exploiting them. As frontier models become increasingly capable of hacking, software security, supply chain attacks, and cyber defense are entering a fundamentally new era.
The conversation explores AI-powered hacking, software supply chain attacks, leaked credentials, zero-day vulnerabilities, package manager security, and why the path of least resistance for increasingly autonomous AI systems may also be the most dangerous. They also discuss what enterprises, developers, and the open-source ecosystem need to do to adapt as the gap between vulnerability discovery and exploitation continues to shrink.
Resources:
Follow Dylan Ayrey on X: https://x.com/InsecureNature
Follow Feross Aboukhadijeh on X: https://x.com/Feross
Follow Joel De La Garza on LinkedIn: https://www.linkedin.com/in/3448827723723234/
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
ANNOUNCEMENT on BINANCE DELISTING
Binance drops $PIVX 👋🏽 First off, please get your $PIVX off of Binance as soon as possible.
Deposit in to your Core or MPW wallet, on BasicSwapDEX or any of the exchanges, swap sites or wallets 👇
listed here: https://pivx.org/exchanges
We realize the price isn’t the best and with Binance delisting us, we understand it may go lower. Yet knowing we are no longer forced to jump through Binance hoops of their centralized demands is a win for PIVX.
We strongly feel PIVX will not only recover but will shine brighter than ever. PIVX is actively building as one can see on our GitHub. Shielded staking, among other updates, will be coming soon via V6.0. github.com/PIVX-Project We will be deeply supporting more DEX ecosystems as we keep building.
We have a 10 year track record of privacy innovation on PoS chain of which we are proud of and pride ourself with.
Should you have any questions or want to check out what PIVX and PIVXLabs are building, please go to 👇
Discord.PIVX.org and/or https://discord.gg/T2dyeF8pR. We’ll share more news soon.
In the meantime, PIVX would like to thank you for your ongoing support over the past 10 years, it is appreciated more than you know. 🙏🏼 #PIVXcommunity
We aren’t giving up, in fact this has made us stronger and more keen to keep growing. 🚀 💪🏼
PIVX Core.
PIVX. Your Rights. Your Privacy. Your Choice.
To stay on top of PIVX news please visit PIVX.org and Discord.PIVX.org.
ANNOUNCEMENT on BINANCE DELISTING was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
Elena Burger and Matt Bornstein are joined by Simon Mo, co-founder and CEO of Inferact, the open-source inference engine powering many of today's most advanced AI applications. Together, they explore how open-source AI evolved from a research project into critical infrastructure, why inference has become one of the most important layers of the AI stack, and what it takes to bring frontier intelligence to developers around the world.
The conversation covers vLLM's origins, the rise of open-weight models, why companies increasingly want control over their AI infrastructure, and how open-source inference enables the next generation of AI applications. They also discuss model licensing, the economics of open-weight AI, Kimi K3, distillation, AI infrastructure, and why Simon believes the gap between open and closed models is rapidly disappearing.
Resources:
Follow Simon Mo on X: https://x.com/simon_mo_
Follow Matt Bornstein on X: https://x.com/BornsteinMatt
Follow Elena Burger on X: https://x.com/VirtualElena
Follow Inferact: https://x.com/inferact
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
The Zcash Foundation is committed to transparency and openness with the Zcash community and our other stakeholders. Today, we are releasing our Q2 2026 report, which provides an overview of the work undertaken by our engineering team, as well as an overview of other activities during this period.
As with our previous quarterly reports, this report describes our financial inflow and outflows, with a detailed breakdown of our expenses, and we have included a snapshot of the Foundation’s financial position, in terms of liquid assets and liabilities that must be met using those assets.
Download the Q2 2026 report here.
Our previous quarterly reports can be found here.
The post Zcash Foundation Q2 2026 Report appeared first on Zcash Foundation.
This week, a16z American Dynamism Films premiered three short documentaries highlighting companies tackling some of America's biggest industrial challenges: Ulysses, Mariana Materials, and Radiant. Before watching those films, we're revisiting conversations with the founders behind each company.
You'll hear Will O'Brien explain why autonomous underwater robots could unlock a new era of ocean exploration and security, Turner Caldwell discuss rebuilding America's critical minerals supply chain and modernizing mining, and Doug Bernauer share why portable nuclear microreactors could transform how we generate power. Together, these conversations offer a look at the technologies—and the founders—working to rebuild the industrial foundations of the United States.
Resources:
Follow Will O'Brien on X: https://x.com/Willob
Follow Turner Caldwell on X: https://x.com/tbc415
Follow Doug Bernauer on X: https://x.com/dougbernauer
Follow Erin Price-Wright on X: https://x.com/espricewright
Follow Ryan McEntush on X: https://x.com/rmcentush
Follow Theo Jaffee on X: https://x.com/theojaffee
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Theo Jaffee is joined by Joshua Achiam, Chief Futurist at OpenAI, for a conversation on AI cybersecurity, frontier model capabilities, and why he believes society may have already crossed the threshold into an AGI-era without fully recognizing it.
They discuss AI's rapidly advancing cyber capabilities, state-sponsored hacking, model jailbreaks, recursive self-improvement, and what happens when AI systems begin discovering vulnerabilities faster than humans can patch them. Joshua also explains why most people have quietly adapted to capabilities that would have seemed unimaginable just a few years ago, and why the biggest changes from AI may arrive gradually rather than all at once.
Resources:
Follow Joshua Achiam on X: https://x.com/jachiam0
Follow Theo Jaffee on X: https://x.com/theojaffee
Follow MTS on X: https://x.com/mtslive
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Stablecoins are transforming how value moves across blockchain networks. They enable near-instant, low-cost transfers around the clock and have become a cornerstone of decentralized finance (DeFi), supporting payments, lending, trading and settlement across multiple ecosystems.
Because stablecoins allow capital to move continuously, privacy becomes increasingly important. Businesses, institutions and individuals require the ability to transact confidentially without sacrificing the composability and liquidity that make DeFi attractive.
Panther Protocol addresses this through programmable privacy. Its Multi-Asset Shielded Pool (MASP) enables confidential stablecoin transfers while allowing operators to define their own access controls and compliance requirements. Rather than requiring issuers to launch dedicated privacy-focused stablecoins or entirely new blockchain networks, Panther enables existing stablecoins to be used confidentially within the DeFi ecosystems where liquidity already exists.
Why Now?Stablecoin adoption has accelerated rapidly. Stablecoins now settle approximately US$5.2 trillion each month, have a combined market capitalization of around US$312 billion, and are used by more than 135 million active blockchain addresses. Yet despite this growth, fewer than 0.01% of stablecoin transfers in 2025 were confidential.
This lack of privacy limits broader adoption.
Without confidentiality:
transactions can be front-run; trading and treasury strategies can be analyzed and copied; businesses expose commercially sensitive payment flows; institutions struggle to execute large transactions discreetly; and users permanently expose their financial activity on public blockchains.If decentralized finance is to support a broader range of commercial and institutional use cases, confidentiality will become an increasingly important part of its infrastructure.
Why Privacy Matters Protecting Commercial InformationBusinesses increasingly use stablecoins for supplier payments, treasury management, payroll and cross-border settlement. Public blockchains expose transaction values, counterparties and payment flows, allowing competitors to infer pricing, commercial relationships and strategic activity.
Protecting Individual PrivacyAnyone with knowledge of a wallet address can analyze its transaction history, balances and spending patterns. Because blockchain data is immutable, that financial history remains publicly accessible indefinitely.
Supporting Institutional AdoptionFinancial institutions, market makers and corporate treasuries require operational confidentiality. Public visibility of trading activity and treasury movements can expose investment strategies, increase market impact and reduce execution costs.
Enabling Configurable CompliancePrivacy need not come at the expense of compliance. Zero-knowledge cryptography enables transactions to remain confidential while allowing operators to implement appropriate Know Your Customer (KYC), Know Your Transaction (KYT) and anti-money laundering (AML) controls.
Privacy Without Leaving DeFiCompetition between stablecoin issuers continues to intensify, yet few wish to build entirely new privacy-focused blockchains or dedicated privacy infrastructure.
Panther offers an alternative.
Rather than creating new privacy stablecoins or separate Layer 1 or Layer 2 networks, issuers and operators can enable confidential transfers using existing stablecoins while remaining within the DeFi ecosystems where users, liquidity and applications already exist.
Operators can:
define which stablecoins and other digital assets are supported; determine who may participate; configure compliance requirements and transaction policies; whitelist counterparties and assets; and create confidential trading environments without fragmenting liquidity.By providing privacy at the smart contract level, Panther allows operators to concentrate their activity where liquidity already exists rather than asking users to migrate elsewhere.
Confidential Stablecoin Transfers Through PantherPanther enables confidential transfers through its Multi-Asset Shielded Pool (MASP).
Users deposit supported stablecoins into the shielded pool and receive corresponding zAssets—confidential representations backed 1:1 by collateral held within a Panther Vault.
Transfers between zAccounts remain confidential, preventing external observers from linking senders, recipients or transaction amounts while maintaining cryptographic integrity.
Unlike asset-specific privacy systems, Panther's MASP supports multiple digital assets within the same shielded pool. Stablecoins, utility tokens and other supported assets all contribute to a shared anonymity set, strengthening privacy for every participant.
Different stablecoins, and other digital assets, can coexist within the same shielded poolFor example, confidential representations of USDT, USDC, DAI and other supported digital assets can coexist within the same shielded pool, alongside other approved assets, subject to the policies defined by the relevant operator.
How Panther Enables Confidential TransfersPanther combines several complementary technologies to deliver confidential stablecoin transfers.
zk-SNARKsZero-Knowledge Succinct Non-Interactive Arguments of Knowledge (zk-SNARKs) allow users to prove that transactions are valid without revealing the underlying transaction data.
zAccountsUsers transact through confidential zAccounts rather than directly exposing their externally owned account (EOA) wallet addresses, helping prevent public linkage between blockchain identities and private activity.
UTXOsPanther represents balances using Unspent Transaction Outputs (UTXOs). Ownership of these UTXOs changes during confidential transfers without revealing the underlying transaction details.
Panther's split-and-join mechanism helps minimise fragmentation by maintaining efficient UTXO management.
Merkle TreesAppend-only Merkle trees maintain the private state of the protocol. Users prove ownership and spendability of their UTXOs using zero-knowledge proofs while keeping the underlying data confidential.
zMinerszMiners perform confidential computation off-chain, generate zero-knowledge proofs and submit those proofs to Panther's smart contracts for verification.
RelayersRelayers further enhance privacy by submitting transactions on behalf of users. They bundle transaction requests, pay gas fees and broadcast transactions without revealing the relationship between the original user and the blockchain transaction.
A Flexible Privacy LayerPanther is designed to support a broad range of operators.
A regulated financial institution may require comprehensive compliance controls and approved counterparties.
A stablecoin issuer may wish to create a confidential settlement environment around its own token.
A decentralized autonomous organization (DAO) may prioritize governance-based access controls.
Each operator can define its own operational policies while benefiting from the same underlying confidential infrastructure and shared privacy set.
ConclusionStablecoins have become one of the most important building blocks of decentralized finance, but widespread adoption increasingly depends on confidentiality.
Without stronger privacy protections, decentralized finance risks becoming a financial system where every transaction is permanently visible and easily analyzed.
Panther enables existing stablecoins to be used confidentially without requiring new privacy-focused stablecoins or separate blockchain networks. Through its Multi-Asset Shielded Pool, configurable compliance framework and programmable privacy architecture, Panther enables operators to create confidential trading environments while continuing to leverage the liquidity and applications of today's leading DeFi ecosystems.
About Panther Protocol FoundationPanther Protocol Foundation is a non-profit organization that supports the Panther ecosystem through research funding, open-source development grants and ecosystem initiatives.
The Foundation does not operate the protocol, host user interfaces, custody assets, execute transactions or provide financial services.
Users interact directly with blockchain smart contracts from their own wallets and remain responsible for their own activities and decisions.
For more information, visit www.panther.org.
To learn more about Panther Protocol, visit www.pantherprotocol.io.
Sophia Dew and Sofia Puccini are joined by Ruby Thelot, designer, artist, cyberethnographer, professor at NYU, and founder of 13101401, for a wide-ranging conversation about internet culture, AI, digital communities, and how technology is reshaping the way we relate to one another.
Drawing on years of research into online behavior, Ruby explains how digital cultures form, why algorithms shape more than just what we see, and what AI is changing about creativity, communication, and identity. They discuss cyberethnography, online subcultures, "machinic taste," AI companions, social norms, internet language, and why Americans often say they dislike AI—even as they increasingly rely on it in everyday life.
Resources:
Follow Ruby X: https://x.com/being_on_line
Substack: https://beingonline.substack.com/
Follow Sophia on X: https://x.com/sophiadew
Follow Sofia on X: https://x.com/schisofrenia
Follow MTS on X: https://x.com/mtslive
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Marc Andreessen, Chris Dixon, and Robert Hackett discuss one of the most consequential policy debates facing the crypto industry: the push for comprehensive U.S. market structure legislation and what regulatory clarity could mean for innovation, financial markets, and America's technological leadership.
They explore the CLARITY Act, stablecoins, securities law, consumer protection, and why both builders and financial institutions are calling for clear rules of the road. Along the way, they discuss the lessons of the early internet, FTX, open financial networks, and why they believe thoughtful regulation can strengthen innovation rather than slow it down.
Resources:
Follow Marc Andreessen on X: https://x.com/pmarca
Follow Chris Dixon on X: https://x.com/cdixon
Follow Robert Hackett on X: https://x.com/rhackett
Follow a16z Crypto on X: https://x.com/a16zcrypto
Why Bitcoin matters: https://a16z.com/why-bitcoin-matters/
What builders need to know about the CLARITY Act: https://a16zcrypto.com/posts/article/clarity-act-what-why-matters
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Welcome to this week’s PIVX ecosystem update, covering the latest developments across the network, market activity, masternode participation, and community ecosystem.
Masternode Network Update
The PIVX masternode network continues to maintain steady participation, supporting the overall strength and security of the blockchain.
- Current PIVX Masternodes: 2,090
- Estimated Annual Reward: ~15.05%
- PIVX Locked: 19.88%
The consistent level of masternode participation highlights the continued commitment of the PIVX community while providing opportunities for node operators to contribute to the network and earn rewards.
Weekly Market Pulse
PIVX remained active in the market over the past seven days, trading within an approximate range of $0.0342 to $0.0355.
The price movement reflects ongoing participation from traders, long-term holders, and users who continue to follow the development of privacy-focused digital assets.
Trading Volume & Market Activity
Market activity remained steady throughout the week, with the latest 24-hour trading volume reaching approximately $1.58 million.
The continued trading activity across exchanges reflects ongoing liquidity and interest in PIVX among participants in the broader crypto market.
Ecosystem & Community Updates
PIVX continues to expand its payment ecosystem with the introduction of the BTCPay Server plugin, giving users access to both transparent and shielded payment options.
The plugin is available for developers to explore on GitHub and brings another opportunity to build payment solutions powered by $PIVX.
Meanwhile, the ongoing implementation of MiCA continues to reshape Europe’s crypto landscape. With approximately 244 licensed crypto firms and reports of more than 1,700 companies no longer serving the EU, the regulatory transition is contributing to increased consolidation across the industry.
While regulatory clarity can bring greater certainty, the shift also raises an important question for the crypto community: is Europe building a stronger and more sustainable crypto industry, or are increasing regulatory requirements driving innovation elsewhere?
Looking Ahead
As the ecosystem continues to evolve, PIVX remains focused on privacy, financial freedom, open-source development, and giving users greater control over their financial lives.
With continued development, community participation, and innovation, PIVX remains committed to building technology that puts privacy and user choice at the center
PIVX. Your Rights. Your Privacy. Your Choice.
To stay on top of PIVX news please visit PIVX.org and Discord.PIVX.org.
PIVX Weekly Ecosystem Update was originally published in PIVX on Medium, where people are continuing the conversation by highlighting and responding to this story.
Sarah Wang and Kimberly Tan are joined by Jesse Zhang and Ashwin Sreenivas, co-founders of Decagon, to discuss the evolution of enterprise AI agents, why the company increasingly relies on open-source models, and how it is helping some of the world’s largest companies deploy AI in production.
Decagon has become one of the fastest-growing AI companies by building agents that automate customer support, sales, and operational workflows. Jesse, Decagon’s CEO, and Ashwin, its president, explain how the company is building enterprise AI at scale.
They unpack why Decagon moved most of its inference to open-source models, how latency, evaluation, and fine-tuning shape production AI systems, and why enterprise AI requires far more than simply plugging into frontier models. The conversation also explores forward-deployed engineering, enterprise sales, AI’s impact on jobs, and why application companies will continue to thrive alongside the foundation model labs.
Resources:
Follow Jesse Zhang on X: https://x.com/thejessezhang
Follow Ashwin Sreenivas on X: https://x.com/AshwinSreenivas
Follow Sarah Wang on X: https://x.com/sarahdingwang
Follow Kimberly Tan on X: https://x.com/kimberlywtan
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Jason Yanowitz, Co-Founder of Blockworks, joins Sebastien Couture on Epicenter to discuss why crypto is entering its biggest transformation yet. From institutional adoption and the Clarity Act to token transparency, AI, on-chain capital markets and the acquisition of Messari, this conversation explores where crypto is actually heading.
Jason explains why Wall Street is preparing for crypto, why token fundamentals finally matter, how Blockworks acquired Messari, why capital markets are moving on-chain, and why the next crypto cycle could look completely different from previous bull markets.
The conversation also covers Bitcoin, Ethereum, DeFi, stablecoins, RWAs (Real World Assets), tokenisation, venture capital, crypto regulation, SEC policy, the Clarity Act, Token Transparency Framework, AI, Robinhood, Coinbase, Hyperliquid, self-custody, crypto infrastructure, institutional finance and the future of blockchain adoption.
In this episode:
1. Why Wall Street is preparing for crypto
2. The Blockworks × Messari acquisition
3. The Clarity Act and US crypto regulation
4. Token transparency and the future of crypto markets
5. Stablecoins, RWAs and on-chain capital markets
6. AI's role in the next generation of crypto businesses
7. Why the next crypto cycle will reward real fundamentals
8. Building one of crypto's leading media and data companies
If you enjoyed the episode, don't forget to subscribe for more conversations with the builders, founders and investors shaping the future of crypto.
Links:
Lido: https://lido.fi/stvaults?mtm_campaign=epicenter
Sponsors:
Lido V3 introduces stVaults: a modular staking infrastructure that lets builders and institutions deploy custom staking vaults, while staying anchored to stETH as a shared liquidity layer.
Get started building with Lido V3 today: https://lido.fi/stvaults?mtm_campaign=epicenter
Block Space Forum: https://blockspace.forum/
NEAR AI Cloud now lets developers deploy OpenClaw—the rapidly growing open-source AI agent platform—inside Trusted Execution Environments, providing hardware-level encryption with cryptographic attestations. With OpenClaw on NEAR AI Cloud, you can run agents with cloud convenience, but without traditional cloud data exposure. No hardware to manage. No trust assumptions required. Learn more at near.ai.
Alex Rampell and Olivia Moore speak with Lassie cofounders Steijn Pelle and Frédéric Renken about bringing AI to one of the most overlooked parts of the economy: small businesses.
Inspired by time spent working inside dental practices, Pelle and Renken set out to automate the administrative work that keeps healthcare providers away from patients. They discuss how AI agents are changing billing, insurance claims, patient payments, and other operational workflows, allowing practices to spend less time on paperwork and more time delivering care.
The conversation explores AI agents, software that performs work rather than simply storing information, onboarding AI into real-world businesses, and why healthcare administration offers one of the biggest opportunities for automation. Along the way, they discuss product design, go-to-market strategy, and what it takes to build AI systems that operate reliably in complex business environments.
Resources:
Follow Steijn Pelle on X: https://x.com/steijnpelle
Follow Frédéric Renken on X: https://x.com/fredericrenken
Follow Alex Rampell on X: https://x.com/arampell
Follow Olivia Moore on X: https://x.com/omooretweets
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
Justine Moore, partner at Andreessen Horowitz, joins New Economies to explore the rapid evolution of generative media and why AI-native content is reaching an inflection point. They discuss the rise of AI micro-dramas, how creators are building entirely new forms of entertainment, and why the biggest opportunities may lie not in replacing Hollywood—but in expanding who gets to create.
They also cover the future of creator tools, AI agents for individuals, generative video, AI "slop," the economics of AI-native studios, and where founders should be building next as consumer AI enters a new phase.
Resources:
Follow Justine Moore on X: https://x.com/venturetwins
Watch the episode on YouTube: https://www.neweconomies.co/p/justine -moore-andreessen-horowitz
Listen to more from New Economies: https://www.neweconomies.co/
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.
This is an optional release with a set of peer connectivity improvements. It is targeted at operators who see issues with their node’s peer set.
Improvements Outbound Slots No Longer Fill With Non-Serving Peers During SyncOutbound peer slots could previously fill up with peers that advertise no services, which could stall a fresh sync at genesis when most reachable listeners are non-serving. While syncing, Zebra now requires the NODE_NETWORK service from outbound peers; at or near the network tip it continues to accept non-serving peers, such as pruned nodes, as before. (#11071)
The peer crawler now queues a connection attempt on each crawl interval for every spare outbound slot that has a ready address book candidate, so a dropped outbound connection is replaced promptly. Previously, new connections were only attempted when the peer set ran out of ready peers, when a crawl turned up new addresses, or when the node had no outbound connections at all. Zebra now keeps dialing until the outbound connection limit is reached. (#11102)
Largergetaddr Responses Zebra now shares up to half of its address book in response to a getaddr request, up from a quarter, so peers can discover more of the network from each response. (#11103)
The stall detector no longer disconnects peers for empty FindBlocks or FindHeaders responses while the node is within 1,000 estimated blocks of the network tip, which previously could be mistaken for a stall during the normal gaps between blocks near the tip. (#11122)
Mempool transaction relay no longer penalizes peers for adjacent NU6.2 and NU6.3 branch ID mismatches within 40 heights of NU6.3 activation, avoiding unnecessary bans caused by the temporary chain-tip divergence that is expected around any network upgrade boundary. (#11113)
zcashd-compat Sidecar Pinned Ahead of NU6.3The embedded zcashd-compat release manifest and installer script now pin sidecar zebra-compat-v1.1.0, which follows Mainnet past the NU6.3 (Ironwood) activation at block 3,428,143. The previous zebra-compat-v1.0.0 sidecar predates that activation height and stops following the chain at that block. Supervised deployments using zcashd_source = "embedded" must upgrade, or set zcashd_path to a current sidecar binary, before activation. (#11112)
Chain synchronization now keeps the final block hash a peer returns in a FindBlocks response instead of discarding it to work around obsolete zcashd behavior. (#11093)
The orchard, zcash_keys, zcash_primitives, zcash_proofs, and zcash_transparent crates have been upgraded to their released NU6.3 versions. This is a dependency update with no behavior change. (#11111)
We encourage operators who are experiencing peering issues, or who want to be proactive about avoiding them, to upgrade to 6.2.3. You can find the release on GitHub, crates.io, and Docker Hub.
If you run a supervised deployment with zcashd_source = "embedded", upgrade to this release, or point zcashd_path at a current sidecar binary, before the NU6.3 (Ironwood) activation at Mainnet block 3,428,143, since the previously pinned sidecar stops following the chain at that height.
Thank you to everyone who contributed to this release:
@arya2, @jvff, @nuttycom, and @upbqdn.
Zebra is the Zcash Foundation’s independent, Rust-based implementation of the Zcash protocol. Learn more at github.com/ZcashFoundation/zebra.
The post Zebra 6.2.3 Release appeared first on Zcash Foundation.
Last week, World Labs announced its acquisition of SceniX, bringing together two teams working on one of AI's biggest unsolved problems: how to give machines a true understanding of the physical world.
Martin Casado sits down with Fei-Fei Li, co-founder and CEO of World Labs, creator of ImageNet, and pioneer of spatial intelligence, alongside Yunzhu Li, co-founder of SceniX and assistant professor at Columbia University. They discuss why World Labs acquired SceniX, how simulation can unlock the next generation of robotics, and why training robots may require a fundamentally different approach than training language models.
The conversation explores real-to-sim-to-real pipelines, world models, robotics foundation models, evaluation, synthetic data, and why the future of AI depends not just on understanding language—but on understanding and interacting with the physical world.
Resources:
Follow Fei-Fei Li on X: https://x.com/drfeifei
Follow Yunzhu Li on X: https://x.com/YunzhuLiYZ
Follow Martin Casado on X: https://x.com/martin_casado
Stay Updated:
Find a16z on YouTube: YouTube
Find a16z on X
Find a16z on LinkedIn
Listen to the a16z Show on Spotify
Listen to the a16z Show on Apple Podcasts
Follow our host: https://twitter.com/eriktorenberg
Please note that the content here is for informational purposes only; should NOT be taken as legal, business, tax, or investment advice or be used to evaluate any investment or security; and is not directed at any investors or potential investors in any a16z fund. a16z and its affiliates may maintain investments in the companies discussed. For more details please see a16z.com/disclosures.
Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.