Two services drove 96% of x402 settlement address changes in 90-day study

·3 views

A 90-day analysis of the x402 payment protocol directory tracked over 8,000 changes across 630 listed services, revealing 1,077 settlement address (payTo) rotations in total. Nearly all of that activity was concentrated in just two services: Tavily Search alone accounted for 964 rotations, cycling to a fresh wallet address every 16 minutes for ten consecutive days in late July and early August. A second service, altahub-vivarium, followed the same 16-minute rotation rhythm on a smaller scale with 82 changes over roughly 22 hours. Stripping out those two outliers, the remaining 628 services produced only 31 address changes across 22 services over the entire 90-day period. The findings warn that AI agents caching a payTo address at scrape time risk sending funds to a stale wallet, since the discovery document is designed to be re-fetched at the moment of payment.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

How One Developer Built Simple Family Account Switching Without Full Permissions System

A developer building MyVitals, a household lab-report management app, chose a lightweight account-delegation model over a full role-based access control system. The solution uses a FamilyMember database record that transitions from a pending invite to an accepted membership, with a sparse unique index trick to prevent duplicate-key errors on invite tokens. Access checks run as a live database read on every request rather than being cached, ensuring that revoking a family member's access takes effect immediately. The acting user's identity is tracked separately from the effective user ID in each request, though the developer acknowledges this relies on convention and code review rather than type enforcement. The all-or-nothing, symmetric access model is intentionally simple and designed to be replaced rather than extended if more granular permissions are ever needed.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

IcebergApp Links Google Sheets to Apache Iceberg Lakehouses via BigQuery

An open-source library called IcebergApp has been developed to connect Google Workspace directly to Apache Iceberg lakehouses running on Google Cloud. The tool addresses well-known limitations of Google Sheets as an enterprise data store, including a 10-million cell cap, slow CRUD operations, and Apps Script memory constraints. IcebergApp uses BigQuery as a serverless query engine to push predicate filters down through Iceberg's metadata layers, enabling ACID-compliant transactions and sub-second query responses. The library also supports time-travel queries and agentic AI integration, all accessible from within Google Apps Script. The project aims to let organizations retain familiar spreadsheet workflows while scaling analytical workloads to petabyte-level datasets on object storage.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Kimball Dimensional Modeling Demystified Using a Fictional Coffee Shop

A DEV Community tutorial series uses a fictional café called Bean & Stalk to teach Ralph Kimball's dimensional modeling concepts, which underpin modern data warehousing. The five-part series covers core topics including fact and dimension tables, grain selection, star versus snowflake schemas, and Slowly Changing Dimensions. The first installment focuses on foundational vocabulary through a relatable business scenario involving sales, loyalty data, and seasonal menus. Despite the rise of modern tools like dbt and cloud-based lakehouses, the author argues that dimensional modeling remains relevant because it reflects how humans naturally frame business questions. A companion repository with schema definitions, seed data, and exercises accompanies the series.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Bridge Tables Solve Many-to-Many Relationships in Kimball Data Modeling

In dimensional data modeling, most fact tables assume a clean one-to-many relationship, but real-world scenarios like insurance claims often involve multiple diagnosis codes per record, creating a genuine many-to-many problem. A common but flawed approach is adding multiple fixed columns — such as diagnosis_1, diagnosis_2, diagnosis_3 — directly to the fact table, which breaks as soon as the number of values exceeds the column count. This structure also forces analysts to repeat filter logic across every column, making queries brittle and prone to silent errors when new columns are added later. Ralph Kimball addressed this problem using a healthcare billing example, introducing what he called a Diagnosis Group table — now commonly known as a bridge table — to properly model the relationship. The bridge table pattern sits between the fact and dimension tables, allowing an unlimited number of dimension values to link to a single fact row without duplicating or distorting measures like billed amounts.

0 comments Read more at DEV Community