<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title><![CDATA[ kris.dev - pckt ]]></title>
        <link><![CDATA[ https://krzysu.pckt.blog ]]></link>
        <description><![CDATA[ Notes on software, product, and everything around it ]]></description>
        <language>en</language>
        <pubDate>Wed, 29 Apr 2026 11:10:58 +0000</pubDate>

                    <item>
                <title>The Missing Piece: A Self-Custody Wallet for AI Agents</title>
                <link>https://krzysu.pckt.blog/the-missing-piece-a-self-custody-wallet-for-ai-agents-zc1vdj6</link>
                <description><![CDATA[Everyone talks about the web3 + AI symbiosis. Nobody is actually shipping a self-custody, agent-native wallet. I noticed this the way you tend to notice these things: by building something that exposed the gap. I&#039;d been working on a small MCP server for CoW Protocol so an AI agent could place swaps on my behalf. The MCP itself was the easy part: a thin protocol adapter that builds the EIP-712 typed data, exposes a few tools, and explicitly never holds a key. The hard part came right after, when ...]]></description>
                <author>kris.dev</author>
                <guid isPermaLink="false">the-missing-piece-a-self-custody-wallet-for-ai-agents-zc1vdj6</guid>
                <pubDate>Tue, 28 Apr 2026 12:06:24 +0000</pubDate>
                                <enclosure url="https://pckt-blog-media.s3.us-east-2.amazonaws.com/cover_image/345672fc-c03c-4545-bbea-f699b237b1a9/Self-Custody-Wallet-for-AI-Agents.png" type="image/jpeg" />
                            </item>
                    <item>
                <title>Designing a Quantum-Secure Ethereum Wallet</title>
                <link>https://krzysu.pckt.blog/designing-a-quantum-secure-ethereum-wallet-dc3v23r</link>
                <description><![CDATA[The smart contract architecture behind a wallet that transitions from classical to quantum-secure cryptography without ever moving your funds. Quantum computers are getting closer to breaking the elliptic curve cryptography that secures every Ethereum account. When that day comes, any wallet signed with ECDSA becomes vulnerable. I&#039;m proposing an open-source smart wallet that&#039;s ready for that future, using post-quantum signature schemes that already verify on-chain today. The core idea: this is a...]]></description>
                <author>kris.dev</author>
                <guid isPermaLink="false">designing-a-quantum-secure-ethereum-wallet-dc3v23r</guid>
                <pubDate>Mon, 30 Mar 2026 13:31:59 +0000</pubDate>
                            </item>
                    <item>
                <title>Product Thinking for Open Source Library Design</title>
                <link>https://krzysu.pckt.blog/product-thinking-for-open-source-library-design-qzw69a9</link>
                <description><![CDATA[What I discovered about library design while working on a dying open source project. Background photo by Shahabudin Ibragimov on Unsplash The best open source libraries are built like products. They need user research, competitive analysis, onboarding strategy, and distribution. The same things any product needs to win. But library authors rarely think this way. They go straight to code.]]></description>
                <author>kris.dev</author>
                <guid isPermaLink="false">product-thinking-for-open-source-library-design-qzw69a9</guid>
                <pubDate>Mon, 09 Mar 2026 10:15:09 +0000</pubDate>
                                <enclosure url="https://pckt-blog-media.s3.us-east-2.amazonaws.com/cover_image/cfbb8d3c-f0eb-410d-95c2-42fba1c31249/Product-Thinking-for-Open-Source-Library-Design.webp" type="image/jpeg" />
                            </item>
                    <item>
                <title>How to Use LLMs in a Trading Bot Stack</title>
                <link>https://krzysu.pckt.blog/how-to-use-llms-in-a-trading-bot-stack-h96yt4e</link>
                <description><![CDATA[Been playing with kraken-cli + Claude Code for a trading bot stack. Here&#039;s the split that clicked for me today: 🤖 Agentic for design &amp; validation — describe your strategy in natural language, the LLM figures out the implementation, fetches data, and paper trades. (strategy compiler) ⚙️ Deterministic for execution — once the logic is solid, extract it into a Python/Bash script. Predictable, loggable, no LLM in the hot path. Calculate signals, run strategies. (working implementation)]]></description>
                <author>kris.dev</author>
                <guid isPermaLink="false">how-to-use-llms-in-a-trading-bot-stack-h96yt4e</guid>
                <pubDate>Sun, 15 Mar 2026 18:52:02 +0000</pubDate>
                            </item>
            </channel>
</rss>