<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>WalletD research and engineering</title><description>Technical studies on ledger correctness, resilience, and scale, backed by open evidence.</description><link>https://walletd.io/</link><language>en</language><item><title>From Points to Perks: Build a Loyalty System with WalletD</title><link>https://walletd.io/blog/build-loyalty-points-system-with-walletd/</link><guid isPermaLink="true">https://walletd.io/blog/build-loyalty-points-system-with-walletd/</guid><description>Use WalletD reward rules to turn captured payments into loyalty points and wallet credit, with practical guidance on rounding, retries, refunds, and launch checks.</description><pubDate>Tue, 15 Sep 2026 00:00:00 GMT</pubDate><category>WalletD wallet infrastructure</category><category>loyalty points</category><category>rewards API</category><category>payments</category></item><item><title>How to Set Up Your Own Wallet with WalletD API</title><link>https://walletd.io/blog/setup-your-own-wallet-with-walletd-api/</link><guid isPermaLink="true">https://walletd.io/blog/setup-your-own-wallet-with-walletd-api/</guid><description>Learn how to set up a digital wallet with WalletD API. Follow curl examples to create users, fund wallets, check balances, send money, and connect webhooks.</description><pubDate>Sun, 13 Sep 2026 00:00:00 GMT</pubDate><category>wallet API</category><category>getting started</category><category>integration</category><category>top-ups</category><category>transfers</category></item><item><title>How we load-test a ledger, and what a payment per second really means</title><link>https://walletd.io/blog/reading-the-benchmark/</link><guid isPermaLink="true">https://walletd.io/blog/reading-the-benchmark/</guid><description>A benchmark number is only as good as its definition. Here is exactly how we drive load against the ledger, what one transaction per second counts, and why the method maps to real production traffic rather than a lab trick.</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><category>load testing</category><category>benchmarking</category><category>transactions per second</category><category>methodology</category><category>production readiness</category></item><item><title>We pushed our ledger until something broke. It wasn&apos;t the ledger.</title><link>https://walletd.io/blog/room-to-grow/</link><guid isPermaLink="true">https://walletd.io/blog/room-to-grow/</guid><description>We kept driving the payment path until we found the next limit, removed a database contention point, and left the ledger database running at about half capacity at peak.</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><category>scalability</category><category>database contention</category><category>headroom</category><category>ledger</category><category>horizontal scaling</category></item><item><title>Fast and correct is half the job. The other half is failing safely.</title><link>https://walletd.io/blog/graceful-under-load/</link><guid isPermaLink="true">https://walletd.io/blog/graceful-under-load/</guid><description>Any system can look good at its rated load. We deliberately pushed the platform to twice its comfortable rate and watched whether it failed safely without moving the books.</description><pubDate>Thu, 27 Aug 2026 00:00:00 GMT</pubDate><category>graceful degradation</category><category>load shedding</category><category>resilience</category><category>payments</category><category>ledger correctness</category></item><item><title>We proved our ledger stays correct at 1,600 payments a second.</title><link>https://walletd.io/blog/ledger-at-scale/</link><guid isPermaLink="true">https://walletd.io/blog/ledger-at-scale/</guid><description>A ledger has one job it can never get wrong: the books must balance, always, no matter how much money is moving. We load-tested for speed and correctness, then published every number.</description><pubDate>Wed, 26 Aug 2026 00:00:00 GMT</pubDate><category>ledger</category><category>load testing</category><category>double-entry</category><category>correctness</category><category>database throughput</category></item></channel></rss>