blockchain

4 posts

aws

AWS WAF adds AI traffic monetization capability to help content owners charge AI bots for content access | Amazon Web Services (opens in new tab)

AWS WAF introduces AI traffic monetization, allowing publishers to charge AI bots for content access at the network edge. Owners can set prices and access rules by content path and agent verification tier without changing origin infrastructure or building payment systems. The capability uses stablecoin payments and the x402 protocol, helping publishers recover costs from AI traffic that generates little referral value. ## Why AI Traffic Monetization Matters - AI crawlers now represent more than half of web traffic for many content providers. - AI-specific crawler activity has reportedly grown over 300% year over year. - Unlike search crawlers, AI agents often consume content without sending users back to the publisher. - Publishers still pay for bandwidth and infrastructure while losing potential page views, advertising impressions, and subscriptions. - AWS WAF Bot Control previously supported visibility, blocking, and rate limiting, but not payment collection. ## Setting Up a Protection Pack - AWS WAF Bot Control must be enabled at the Common or Targeted level on the web ACL associated with a CloudFront distribution. - A protection pack defines: - Monetized content paths - Pricing by agent verification tier - Accepted payment methods - License terms - Protection packs can be created in the AWS WAF and Shield console. - Users can associate CloudFront distributions, select managed security protections, and customize monetization settings. - Multiple protection packs can apply different pricing policies to separate content zones. ## Analyzing AI Bot Traffic - The AI traffic analysis dashboard divides requests into: - All bot requests - AI bot requests - Verified AI bot traffic - Unverified AI bot traffic - It reports bandwidth usage, estimated monthly cost, and peak request rates. - A per-path heatmap shows when and where AI agents access content. - AWS WAF Bot Control classifies more than 650 AI bot and agent types, including GPTBot, Claude-Web, and Perplexity-Bot. ## Agent Verification Tiers - **Verified:** Identity is confirmed through Web Bot Auth Ed25519 signatures or documented IP ranges with known user-agent and domain information. - **Unverified:** The agent is identified using user-agent matching, behavioral fingerprints, and IP reputation, but lacks cryptographic confirmation. ## Access and Pricing Actions For each verification tier, publishers can choose one of six actions: - **Monetize:** Charge for access and return an HTTP 402 response. - **Allow:** Provide free access. - **Block:** Deny the request. - **Count:** Log the request without charging. - **CAPTCHA:** Require human verification. - **Challenge:** Silently verify that the client is a browser rather than a bot. ## Stablecoin Payments and x402 - Publishers select supported blockchain networks and provide a wallet address. - Pricing is set as a base page price in USDC, with support for multiple networks. - AWS does not process payments or take a share of content revenue; settlement is handled by the publisher or wallet provider. - Monetized requests return an HTTP 402 response containing an x402 JSON price manifest. - The manifest specifies: - USDC price - Accepted networks, such as Base and Solana - Destination wallet - Payment timeout - Payment scheme - Compatible AI agents can submit signed payment authorizations autonomously. - AWS WAF verifies the payment, uses third-party facilitators such as Coinbase’s x402 Facilitator for on-chain settlement, retrieves the content, and returns it to the agent. ## Deployment Limits and Testing - Monetization rules are supported only on web ACLs associated with Amazon CloudFront distributions. - Regional web ACLs cannot use the Monetize action. - Real and Test currency modes can be switched from the monetization configuration page. - Test mode is intended for validating pricing, wallet settings, and x402 payment flows before production deployment. - Stripe account payments and Machine Payments Protocol support are planned for future releases. Publishers should first enable Bot Control and study AI traffic patterns before setting prices. Protection packs and test mode provide a way to apply differentiated policies while validating that automated payment and content delivery work correctly.

discord

Game On: Discord Is Backing the Next Generation of Dutch Gaming Founders (opens in new tab)

Discord and Techleap are launching the Gaming Founders Circle to support five ambitious Dutch gaming companies through the end of 2026. The program aims to help founders scale by connecting them with peers, investors, industry networks, and Discord leadership. It reflects Discord’s broader view that gaming grows through strong relationships among developers, players, and business communities. ## A New Support Program for Dutch Gaming - Discord is partnering with: - **Techleap**, which supports Dutch scaleups. - **The Dutch Games Association**, which provides connections to the local games industry. - The Netherlands is especially significant to Discord because it hosts the company’s European headquarters. - Discord says its platform offers developers direct access to players and real-time feedback: - More than 90% of Discord users play games. - Over 80 million users participate in more than 10,000 gaming communities. ## The Five Founders in the Cohort The first Gaming Founders Circle cohort represents a broad range of gaming technologies and business models: - **VaultN**: Digital distribution infrastructure used by publishers such as Bethesda, 2K, and Take-Two. - **Poki**: A self-funded web gaming platform with 90 million monthly players. - **MAXYMUM**: AI-powered tools for game design, recently validated at GDC. - **YOM**: Decentralized cloud gaming infrastructure combining blockchain and streaming. - **Immens**: A European game engine designed around AI and led by an experienced industry veteran. Discord, Techleap, and the Dutch Games Association selected the companies jointly. ## What Participants Receive The program focuses on practical challenges faced by growing gaming companies, including: - **Peer learning** on hiring, fundraising, distribution, community building, and international expansion. - **Investor access** through Techleap’s Dutch and international network, particularly important as later-stage studio funding becomes more difficult. - **Industry connections** through Discord’s gaming ecosystem. ## Program Milestones - The program runs through the end of **2026**. - In **October**, participants will travel to San Francisco for: - A meeting with Discord leadership. - An investor dinner hosted by Techleap and Prince Constantijn. - The initiative concludes at the **Dutch Games Awards in November**. The Gaming Founders Circle is intended to strengthen Dutch gaming by giving founders the relationships, knowledge, and capital connections needed to grow. Discord’s recommendation is clear: supporting individual companies while building stronger connections across the entire national games sector.

google

Safeguarding cryptocurrency by disclosing quantum vulnerabilities responsibly (opens in new tab)

Google Quantum AI argues that future cryptographically relevant quantum computers could break the elliptic-curve cryptography securing many cryptocurrencies sooner and with fewer resources than previously estimated. Its research presents circuits for attacking 256-bit elliptic-curve discrete logarithms using fewer than 1,200–1,450 logical qubits and 70–90 million Toffoli gates. Google urges cryptocurrency developers to migrate to post-quantum cryptography while disclosing the findings through verifiable zero-knowledge proofs rather than publishing exploitable attack details. ## Updated Quantum Resource Estimates - The relevant threat is Shor’s algorithm running on a large, fault-tolerant quantum computer. - Google developed two circuits for solving ECDLP-256: - Fewer than 1,200 logical qubits and 90 million Toffoli gates. - Fewer than 1,450 logical qubits and 70 million Toffoli gates. - Under assumptions aligned with some superconducting quantum hardware, the attack could require: - Fewer than 500,000 physical qubits. - Only a few minutes of computation. - This represents an estimated 20-fold reduction in physical-qubit requirements compared with earlier estimates. - Google connects the findings to its proposed 2029 timeline for beginning migration to post-quantum cryptography. ## Protecting Cryptocurrencies with PQC - Most blockchains and cryptocurrencies rely on elliptic-curve cryptography for essential security functions. - Post-quantum cryptography offers a practical, established direction for protecting blockchains against quantum attacks. - Migration will take significant time, creating urgency for networks to begin transitioning now. - Short- and long-term recommendations include: - Avoid exposing vulnerable wallet addresses. - Do not reuse vulnerable addresses. - Consider policy responses for abandoned or inaccessible coins. - The post points to existing post-quantum blockchain projects and experimental deployments as evidence that migration is feasible. ## Responsible Disclosure Through Zero-Knowledge Proofs - Public vulnerability disclosure must balance two risks: - Revealing enough information for defenders to respond. - Giving attackers a usable blueprint. - Cryptocurrency disclosure is especially sensitive because fear and unsupported claims can damage public confidence even before a technical attack is possible. - Google says it reduced this risk by clarifying which blockchain components are not vulnerable and emphasizing existing post-quantum progress. - It also published a zero-knowledge proof that allows independent parties to verify the resource estimates without accessing the underlying quantum circuits. - Google encourages other research groups to adopt similarly responsible disclosure practices. ## Outlook for the Cryptocurrency Ecosystem - Google hopes the work will encourage coordinated discussion among quantum researchers, security experts, cryptocurrency developers, and policymakers. - The broader goal is to preserve confidence in blockchain systems while giving them enough time to complete a post-quantum transition. Cryptocurrency projects should begin planning and testing PQC migration now, while avoiding address exposure and reuse in the interim. At the same time, quantum researchers should disclose attack estimates in ways that support verification and defense without unnecessarily enabling exploitation.

figma

Designing an Open Financial System at Coinbase | Figma Blog (opens in new tab)

Coinbase’s mission to make cryptocurrency accessible depends on design that simplifies complex technology. The company found that Figma’s browser-based, collaborative workspace replaced fragmented tools with an open process involving designers, engineers, product managers, and leadership. This improved communication, alignment, and speed while supporting a more inclusive design culture. ## Designing for an Open Financial System - Coinbase aims to create an open financial system for the world. - Its design principles are to: - Guide users through complex crypto concepts - Empower people to participate - Humanize technical experiences - Simplify blockchain and digital-currency interactions - The company views design as essential to making cryptocurrency accessible beyond technical experts. ## Moving from Siloed Design to Open Collaboration - Coinbase’s previous workflow relied on separate tools for: - Designing - Prototyping - Developer handoff - Switching between platforms created context loss, version-control problems, and communication overhead. - Figma provided a shared, browser-based workspace where multiple people could work together and access the latest files through a link. - This made design more transparent and encouraged feedback and participation from people outside the design team. ## Faster Communication Across Teams - Centralized files allowed designers, product managers, engineers, and executives to stay aligned on current work. - Stakeholders could give feedback directly in Figma, reducing bureaucracy and shortening communication loops. - Teams could speak “the same language” in the same location instead of relying on disconnected tools and handoffs. - The result was faster iteration and clearer, more coordinated product development. ## Collaborative Design Sessions - Coinbase also used Figma for informal, ad hoc projects such as posters and company swag. - Designers could gather in the Design Lounge, open a shared file, and create together in real time. - These sessions demonstrated that collaborative tools could support creativity and team connection, not just formal product work. ## Building a More Inclusive Design Culture - Coinbase’s design team became faster, more nimble, and better aligned. - Figma helped establish a collaborative process in which design was no longer created behind a “black box.” - The team recognized that tools should empower designers and support an inclusive, diverse culture rather than add complexity. - Coinbase presents Figma as an important foundation for continuing to scale its open design practice.