<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cryptography on map(learn, world)</title><link>/tags/cryptography/</link><description>Recent content in Cryptography on map(learn, world)</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 03 Apr 2026 22:06:19 +0900</lastBuildDate><atom:link href="/tags/cryptography/index.xml" rel="self" type="application/rss+xml"/><item><title>eciesjs 0.5.0: Seven Years, Fifty Releases</title><link>/posts/eciesjs-50th-release/</link><pubDate>Fri, 03 Apr 2026 00:00:00 +0000</pubDate><guid>/posts/eciesjs-50th-release/</guid><description>&lt;p&gt;&lt;em&gt;The 50th release of the quietly influential JavaScript ECIES library.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id="the-journey"&gt;The Journey&lt;/h2&gt;
&lt;p&gt;On November 28, 2018, I published &lt;code&gt;eciesjs&lt;/code&gt; v0.0.1 to &lt;a href="https://www.npmjs.com/package/eciesjs/v/0.1.0"&gt;npm&lt;/a&gt;. It was a small, focused library — a JavaScript/TypeScript counterpart to &lt;a href="https://github.com/ecies/py"&gt;eciespy&lt;/a&gt; — born from a simple gap: the JavaScript ecosystem needed a clean, correct Elliptic Curve Integrated Encryption Scheme implementation.&lt;/p&gt;
&lt;p&gt;Seven years and fifty releases later, the core API is still two functions: &lt;code&gt;encrypt&lt;/code&gt; and &lt;code&gt;decrypt&lt;/code&gt;. That simplicity is deliberate. Cryptographic libraries should be boring — prevent misuse and get out of your way.&lt;/p&gt;</description></item></channel></rss>