<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Oleksandr Dendeberia on foojay.io - Friends Of OpenJDK</title><link>http://foojayio.github.io/website/today/author/oleksandr-dendeberia/</link><description>Articles written by Oleksandr Dendeberia on foojay.io - Friends Of OpenJDK</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 22 Aug 2026 08:43:04 +0000</lastBuildDate><atom:link href="http://foojayio.github.io/website/today/author/oleksandr-dendeberia/index.xml" rel="self" type="application/rss+xml"/><item><title>Offline Crypto Address Validation in Java</title><link>http://foojayio.github.io/website/today/offline-crypto-address-validation-in-java/</link><pubDate>Sat, 22 Aug 2026 08:43:04 +0000</pubDate><guid>http://foojayio.github.io/website/today/offline-crypto-address-validation-in-java/</guid><description>&lt;p&gt;Backend validation often starts with simple questions.&lt;/p&gt;&#10;&lt;p&gt;Is the input empty? Does it have the expected shape? Can it be parsed? Does it belong to the selected domain?&lt;/p&gt;&#10;&lt;p&gt;Crypto wallet addresses are no different, except the formats vary across chains and simple regular expressions are rarely enough.&lt;/p&gt;&#10;&lt;p&gt;If a Java backend accepts crypto withdrawal addresses, address-book entries, CSV imports, support-tool input, or transaction preflight requests, it should reject clearly invalid addresses before calling RPC nodes, explorers, exchange APIs, or internal money-movement systems.&lt;/p&gt;</description></item></channel></rss>