<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Data &amp; Methods on Kai | Technical Writer &amp; Data Analyst</title><link>https://defi-kai.github.io/kai-site/tags/data--methods/</link><description>Recent content in Data &amp; Methods on Kai | Technical Writer &amp; Data Analyst</description><generator>Hugo -- 0.168.0</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 09:00:00 -0400</lastBuildDate><atom:link href="https://defi-kai.github.io/kai-site/tags/data--methods/index.xml" rel="self" type="application/rss+xml"/><item><title>Jupiter Lend Under Stress: Analyzing the October 10 Liquidation Event</title><link>https://defi-kai.github.io/kai-site/writing/jupiter-lend-under-stress-october-10-liquidation-event/</link><pubDate>Mon, 05 Oct 2026 09:00:00 -0400</pubDate><guid>https://defi-kai.github.io/kai-site/writing/jupiter-lend-under-stress-october-10-liquidation-event/</guid><description>&lt;p&gt;On October 10, 2025, U.S. President Donald Trump announced that the U.S. would impose an additional 100% tariff on Chinese imports. This announcement was followed by a rapid market selloff: over the course of October 10, the price of ETH fell as much as 12% and SOL fell as much as 24%.&lt;/p&gt;
&lt;p&gt;The wave of selling ultimately triggered $19B in liquidations across derivative markets. But how did this affect other venues that offer leverage, like credit markets?&lt;/p&gt;</description></item><item><title>Reverse-Engineering Jupiter Lend Liquidations: Part 1</title><link>https://defi-kai.github.io/kai-site/work/reverse-engineering-jupiter-lend-liquidations-part-1/</link><pubDate>Mon, 28 Sep 2026 09:00:00 -0400</pubDate><guid>https://defi-kai.github.io/kai-site/work/reverse-engineering-jupiter-lend-liquidations-part-1/</guid><description>&lt;p&gt;Most onchain analysis starts with the assumption that someone has already decoded the dataset. On platforms like Dune, analysts can usually query human-readable tables without having to interpret the raw bytes recorded onchain.&lt;/p&gt;
&lt;p&gt;But what if the dataset you need doesn&amp;rsquo;t exist?&lt;/p&gt;
&lt;p&gt;I ran into this problem while trying to analyze liquidations on Jupiter Lend during the &lt;a href="https://www.fticonsulting.com/insights/articles/crypto-crash-october-2025-leverage-met-liquidity"&gt;market selloff on October 10, 2025&lt;/a&gt;. I wanted to determine how many liquidations were processed and their total value.&lt;/p&gt;</description></item><item><title>Reverse-Engineering Jupiter Lend Liquidations: Part 2</title><link>https://defi-kai.github.io/kai-site/work/reverse-engineering-jupiter-lend-liquidations-part-2/</link><pubDate>Sat, 26 Sep 2026 12:00:00 -0400</pubDate><guid>https://defi-kai.github.io/kai-site/work/reverse-engineering-jupiter-lend-liquidations-part-2/</guid><description>&lt;p&gt;In &lt;a href="https://defi-kai.github.io/kai-site/work/reverse-engineering-jupiter-lend-liquidations-part-1/"&gt;Part 1&lt;/a&gt;, we identified Jupiter Lend&amp;rsquo;s liquidation instructions, mapped their account arguments, and decoded the raw amounts of debt repaid and collateral seized.&lt;/p&gt;
&lt;p&gt;In this walkthrough, we&amp;rsquo;ll combine those findings into a single DuneSQL query using common table expressions (CTEs). The query reconstructs liquidation records from raw instructions and joins Dune&amp;rsquo;s &lt;a href="https://dune.com/data/prices.hour"&gt;&lt;code&gt;prices.hour&lt;/code&gt;&lt;/a&gt; table to calculate the USD value of debt repaid and collateral seized.&lt;/p&gt;
&lt;p&gt;We&amp;rsquo;ll work through the query in four phases, following how each CTE transforms and passes data to the next. &lt;strong&gt;Select a CTE in the interactive query below&lt;/strong&gt; to explore its role in building the final dataset.&lt;/p&gt;</description></item><item><title>Building an Agentic Pipeline for Onchain Data Analysis</title><link>https://defi-kai.github.io/kai-site/work/building-an-agentic-pipeline-for-onchain-analytics/</link><pubDate>Sun, 19 Apr 2026 20:15:00 -0400</pubDate><guid>https://defi-kai.github.io/kai-site/work/building-an-agentic-pipeline-for-onchain-analytics/</guid><description>&lt;p&gt;Using an LLM for data analysis can sometimes create more problems than it solves. In a chat-based workflow, the analyst still has to supply table schemas, API documentation, and project-specific context while copying and pasting data between multiple interfaces and tools. If you&amp;rsquo;re not careful, this setup can increase token costs and introduce errors &amp;ndash; undermining the time saved by using an LLM in the first place.&lt;/p&gt;
&lt;p&gt;At &lt;a href="https://x.com/blocmates"&gt;Blocmates&lt;/a&gt;, we created an agentic pipeline to automate these tasks. Instead of manually providing context and coordinating each step, the analyst fills out a data specification and sends it to Claude Code. The agent loads the necessary context, writes SQL queries, fetches data from APIs, and tests and publishes the queries to Dune.&lt;/p&gt;</description></item><item><title>Building a Local AI System to Stay Ahead of the Crypto News Cycle</title><link>https://defi-kai.github.io/kai-site/work/building-local-ai-system/</link><pubDate>Sun, 15 Mar 2026 09:00:00 -0500</pubDate><guid>https://defi-kai.github.io/kai-site/work/building-local-ai-system/</guid><description>&lt;p&gt;With Crypto operating 24/7 it&amp;rsquo;s challenging to keep up with current news while also going deep on a report. Writing forces you to focus on a project or sector deeply, but you still have to track headlines that could change your thesis or reframe the data.&lt;/p&gt;
&lt;p&gt;To solve this, I built an AI research assistant to keep me up to date with the latest news in crypto and finances everyday, in around 20 minutes reading time &amp;ndash; down from 1-2 hours. It runs on locally hosted models including OpenAI&amp;rsquo;s GPT OSS 20b, and Deepseek R1 via LM studio.&lt;/p&gt;</description></item></channel></rss>