<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Jay Prakash on Medium]]></title>
        <description><![CDATA[Stories by Jay Prakash on Medium]]></description>
        <link>https://medium.com/@jayprakash_81937?source=rss-e05f73fd3ed5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*bQ59qMMYKJNPY99E.</url>
            <title>Stories by Jay Prakash on Medium</title>
            <link>https://medium.com/@jayprakash_81937?source=rss-e05f73fd3ed5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 04:01:45 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jayprakash_81937/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Silence Laboratories Acquires 0xPass Passport Protocol and Launches Agentic Wallet Infrastructure…]]></title>
            <link>https://medium.com/silence-laboratories/silence-laboratories-acquires-0xpass-passport-protocol-and-launches-agentic-wallet-infrastructure-44a19641a9e0?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/44a19641a9e0</guid>
            <category><![CDATA[agentic-wallet]]></category>
            <category><![CDATA[digital-wallet]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[crypto-custody]]></category>
            <category><![CDATA[agents]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Tue, 24 Dec 2024 08:13:31 GMT</pubDate>
            <atom:updated>2024-12-24T08:13:31.778Z</atom:updated>
            <content:encoded><![CDATA[<h3>Silence Laboratories Acquires 0xPass Passport Protocol and Launches Agentic Wallet Infrastructure Kit</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bS3KZ_C0pvuHZH626USg6Q.jpeg" /></figure><p><a href="https://www.silencelaboratories.com/">Silence Laboratories</a> has acquired <a href="https://0xpass.io/">0xPass Passport Protocol,</a> strengthening our commitment to building secure, user-friendly, and programmable account management and privacy infrastructure.</p><p>This acquisition builds on a longstanding collaboration between 0xPass and Silence, with <a href="https://www.silencelaboratories.com/silent-shard">Silence Laboratories’ core MPC libraries</a> already serving as the foundational key management module of Passport Protocol- the <a href="https://github.com/yhl125/mpc-benchmarks">fastest distributed key management network</a> with &lt;500ms performance.</p><p><strong>Krish Chelikavada, Co-Founder of 0xPass</strong>, commented: <em>“We’re happy to partner with Silence Laboratories given our longstanding collaboration. Passport has always been the fastest distributed key management network, powered by Silence’s algorithms already. This acquisition is mutually beneficial for our customers and theirs, enabling both teams to deliver even greater flexibility, performance, and infrastructure options to builders.”</em></p><h4>A. <strong>How would our partners benefit?</strong></h4><blockquote><em>Now, anyone would be able to spin out their own </em><strong><em>KMS and Agentic Authorisation and Transaction Policy network </em></strong><em>in a moment of days and hours! Silence Laboratories now is licensing an end-to-end MPC-TSS network kit which further adds to the offering of Silent Network SDK.</em></blockquote><p>The <strong>Silent Network Kit </strong>includes:</p><ul><li>Core MPC-TSS library based on DKLs23 algorithm (Rust core) which is potentially the fastest TSS library in production (transaction signature generation in less than a few milliseconds),</li><li>TSS network creator SDK with features for:<br>1.<em> Spinning out own threshold signature networks</em> with operators and validators; of <em>arbitrary network size</em> and <em>quorum structure</em>,<br>2. <em>Identifiable Abort </em>to add slashing mechanisms to avoid cheating and non-compliant parties,<br>3. <em>Weighted signatures</em> to account for different signing authority and policies,<br>4. <em>Quorum change</em> (switching members and modifying size) without changing the public keys,</li><li>Operators can be onboarded either on GCP, AWS, or bare metal with support for respective confidential computing platforms,</li><li>Inherent support of secure enclaves,</li><li>Authkit to support social logins, passkeys, and any arbitrary authentication channel,</li><li><strong>Agent policy engine</strong> for designing transaction modules and delegating transactions,</li><li>Smart account and session key kit with support for smart wallet SDKs like Biconomy,</li><li>Option for ready-to-use and deployment as an AVS on the EigenLayer.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/760/1*wgcXZa7kHbbwmLcn3xcw9g.png" /></figure><p>The addition of Passport Protocol will expand Silence Laboratories’ suite of products by adding authentication and programmable transaction capabilities. The enhanced product suite will help Silence reach a broader audience by providing a more comprehensive solution to wallet builders and other developers.</p><h4><strong>B. Competitive edge and quick GTM for our partners and customers</strong></h4><p>One of the primary reasons for the acquisition was to provide our current and future partners with a competitive edge, enabling them to accelerate their go-to-market strategy. This allows them to focus primarily on business logic and policy developments while retaining full ownership of the infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K8ydMqRjsQ8rVJTlnOm0VQ.png" /></figure><blockquote>“One will be able to build their own agentic wallet auth and policy network from scratch, write the logic for authorising transactions based on variables of choice, connect with programable session keys etc; basically all nuts and bolts required to create Agentic Wallets running over MPC-TSS and re-staking backed distributed systems of nodes”</blockquote><p>Talking about the acquisition Jay Prakash, CEO of Silence Laboratories, remarked “<em>This strategic acquisition will significantly fast-track product road map and GTM (ability to launch own infrastructure in a matter of weeks instead of quarters) for wallet builders, adding significant further capabilities to our best-in-class MPC libraries</em>” Jay added.</p><p>The acquisition will also be beneficial to current customers of Passport Protocol as they will benefit from more flexibility on infrastructure options and integration wrappers for the combined product. Security, support, and maintenance for the core MPC-TSS library as well as the other modules, will now also be enhanced under the stewardship of Silence’s advanced cryptography team which works with some of the biggest institutional players in the web3 space.</p><h4>C. You own the code and the infrastructure for true guarantees to your customers and regulators</h4><p>We believe that digital asset enterprises should <em>own the code and infrastructure for maximal assurance to their customers and regulators.</em> Hence, our construct gives full code visibility and freedom to deploy and run the aforementioned fundamental elements of digital asset wallets.</p><p><em>We welcome you to join in the discussion, collaborate, and build together. Please write to us by email or by booking a slot to discuss things, through our </em><a href="https://calendly.com/jay-prakash-ece09/30min"><em>Calend</em></a><em>ly here.</em></p><blockquote><strong><em>ABOUT US: Silence Laboratories</em></strong></blockquote><p><a href="http://silencelaboratories.com/"><em>Silence Laboratories</em></a><em> is a deep-tech, decentralized, compute and authentication-infrastructure (MPC-focused) provider that offers developer-focused SDKs and libraries, for protocols, wallets, and projects that can be used to embed/build distributed, zero-trust authentication and authorization products, alike. We aim to be a defacto MPC and Proofing product suite for other builders to build on top of. For ease of integration, we are application, protocol, custodian, and stack agnostic, collaboration-friendly, and future-forward.</em></p><p>Learn more about their work: <a href="https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsilencelaboratories.com%2F&amp;data=05%7C01%7Cjessica_sasayiah%40sutd.edu.sg%7C7c03bfdaa25f4aa089a308da8bbb0e21%7C3476b776e9904f72b95062489831623d%7C0%7C0%7C637975932794750762%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=XZ1d8viCCwN4Z0p769GyYzBRbGW%2F7oGfYvJ%2FyZxeBy8%3D&amp;reserved=0">https://silencelaboratories.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44a19641a9e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/silence-laboratories/silence-laboratories-acquires-0xpass-passport-protocol-and-launches-agentic-wallet-infrastructure-44a19641a9e0">Silence Laboratories Acquires 0xPass Passport Protocol and Launches Agentic Wallet Infrastructure…</a> was originally published in <a href="https://medium.com/silence-laboratories">Silence Laboratories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing our $4.1]]></title>
            <link>https://medium.com/silence-laboratories/announcing-our-fund-raise-towards-the-mission-of-privacy-preserving-authorization-and-computation-0907851dd913?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/0907851dd913</guid>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[fundraising]]></category>
            <category><![CDATA[privacy-preserving-tech]]></category>
            <category><![CDATA[mpc]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Fri, 01 Mar 2024 07:33:01 GMT</pubDate>
            <atom:updated>2024-03-01T08:39:29.646Z</atom:updated>
            <content:encoded><![CDATA[<h3>Announcing our $4.1 M Fund Raise towards the Mission of Privacy-Preserving Authorization and Computation</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VlBG37caII7yKcbH0kK_RA.jpeg" /></figure><p>We are glad to share about the continued trust of investors as we navigate and champion the territories of Privacy-Preserving Authorisations and Computations.</p><p><a href="https://www.forbes.com/sites/davidprosser/2024/02/29/how-silence-laboratories-plans-to-quiet-the-privacy-storm/"><strong>Feel free to read more at Forbes’s Coverage of the Funding:</strong></a></p><p><a href="https://www.forbes.com/sites/davidprosser/2024/02/29/how-silence-laboratories-plans-to-quiet-the-privacy-storm/">How Silence Laboratories Plans To Quiet The Privacy Storm</a></p><p>🔑 We are strengthening our decentralized authorization library, <a href="https://www.silencelaboratories.com/silent-shard">Silent Shard, </a>which assists enterprises and users in distributing the risk of private key exposure and in designing innovative authorization policies for digital assets.</p><p>📁 We are enabling privacy-preserving collaboration among institutions with our newly launched product, <a href="https://www.silencelaboratories.com/silent-compute">Silent Compute.</a></p><p>⚙ We are inching towards a global convergence where the best of web2 and web3 architectures will solve for the general good and our privacy-preserving stack would be a key enabler.</p><blockquote><em>Please feel free to</em><a href="https://calendly.com/jay-prakash-ece09/20?utm_source=Hero"><em> block a discussion </em></a><em>on anything around MPC, threshold signature or privacy-preserving computation.</em></blockquote><p>Other Coverages:</p><p>A. <a href="https://techcrunch.com/2024/02/29/silence-laboratories-a-cryptographic-security-startup-secures-funding/"><strong>Covered at Techcrunch</strong></a></p><p><a href="https://techcrunch.com/2024/02/29/silence-laboratories-a-cryptographic-security-startup-secures-funding/">Silence Laboratories, a cryptographic security startup, secures funding | TechCrunch</a></p><p>B.Covered at Business Insider</p><p><a href="https://markets.businessinsider.com/news/stocks/silence-laboratories-raises-4-1m-funding-to-enable-privacy-preserving-collaborative-computing-1033117270">Silence Laboratories Raises $4.1M Funding to Enable Privacy Preserving Collaborative Computing</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0907851dd913" width="1" height="1" alt=""><hr><p><a href="https://medium.com/silence-laboratories/announcing-our-fund-raise-towards-the-mission-of-privacy-preserving-authorization-and-computation-0907851dd913">Announcing our $4.1</a> was originally published in <a href="https://medium.com/silence-laboratories">Silence Laboratories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Chalo and Silence Laboratories Forge an Innovative Partnership to Revolutionise Offline Ticket…]]></title>
            <link>https://medium.com/silence-laboratories/chalo-and-silence-laboratories-forge-an-innovative-partnership-to-revolutionise-offline-ticket-d13268c60b12?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/d13268c60b12</guid>
            <category><![CDATA[peer-to-peer]]></category>
            <category><![CDATA[urban-transportation]]></category>
            <category><![CDATA[mobility]]></category>
            <category><![CDATA[authentication]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Sun, 08 Oct 2023 14:49:32 GMT</pubDate>
            <atom:updated>2023-11-29T18:58:31.760Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Chalo and Silence Laboratories Forge an Innovative Partnership to Revolutionise Offline Ticket Authentication</strong></h3><p><em>By Sidharth Pruthi and </em><a href="https://medium.com/u/edd49a56936a"><em>Silence Laboratories</em></a><em> Team</em></p><blockquote><em>The Alliance aims to transform the public transportation experience globally by offering a fast and reliable offline ticket verification solution.</em></blockquote><p><a href="https://www.silencelaboratories.com/multi-modal-proofs">Silence Laboratories,</a> a leader in decentralized security and cyber-proof technology solutions is excited to announce its partnership with <a href="https://chalo.com/">Chalo</a>, India’s premier public transportation technology platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iXOrA3jQ9UfaUlYi3h3AHA.png" /></figure><p>The goal is to offer a fast and reliable offline solution for the verification of bus tickets booked through Chalo’s mobile app using advanced authentication libraries, making the boarding experience of public transportation users contactless, fast, and more efficient.</p><p>The verification of the ticket happens, using Silence Laboratories’s SDK- <strong>SilentAuth</strong>, through two-way communication between the passenger’s phone and the POS terminal held by the conductor/installed in the bus using radio frequency. All of this happens <strong>within 1 second </strong>leading to a seamless and secure offline solution for passengers and bus operators.</p><blockquote>It creates an NFC-like experience and works across NFC and non-NFC devices.</blockquote><p>The technology ‘Silent Auth’ is predicted to be <em>the successor of QR code</em> and <em>OTP-based</em> methods that are:</p><p>1. Slow (QR code-based verifications took 7 seconds on average due to human errors, variability in light conditions, etc) and</p><p>2. Increasingly vulnerable to scams.</p><p>With the rise of sophisticated hacking techniques, traditional authentication methods are becoming less secure, leaving businesses and individuals at risk of data breaches and cyber threats. Silent Auth is a next-generation technology that provides a highly secure and efficient way of authenticating passengers offline with proof-of-proximity and full duplex communication.</p><blockquote>This collaboration also addresses the region’s low penetration of NFC-enabled phones, noisy environment, and heterogeneous smartphone hardware.</blockquote><p>Additionally, it also aids bus operators in managing their fleets more effectively. With a streamlined ticketing process, operators can optimize routes, monitor ridership, and plan schedules more accurately.</p><p><em>“In our quest to digitize mobility and especially ticketing, partnership with Silence Laboratories has been crucial in delivering a seamless, reliable, and blazing fast in bus transaction experience. Using Silent Auth in an offline, secure, and P2P mode, we have been able to offer an under 1 second tap-to-pay experience to the masses of India. “ </em>said Vinayak Bhavnani, Co-Founder &amp; CTO at Chalo,</p><p>Chalo has launched the first phase of deployments for any commonly available smartphone, to tap on the conductor’s POS terminal and validate a ticket bought on the app — simply tap and board!</p><p>Vinayak highlighted that ”on-ground ticket validation through QR code took 7 seconds on average, owing to multiple points of interactions through applications on both the conductor and passenger sides. Silent Auth transformed this. Faster, offline, and usable verification are very important to create an NFC-like experience, particularly in Indian and South Asian geographies where bus stops are very crowded”</p><p>As pioneers in their respective fields, both Silence Laboratories and Chalo share the common goal of making a lasting impact on the transportation industry and setting a new standard for public transportation in South Asia and globally. This partnership is just the beginning, and both companies are excited to explore further opportunities for innovation.</p><p>Please contact <em>info@silencelaboratories.com</em> or book a call <a href="https://calendly.com/jay-prakash-ece09/30min">here</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d13268c60b12" width="1" height="1" alt=""><hr><p><a href="https://medium.com/silence-laboratories/chalo-and-silence-laboratories-forge-an-innovative-partnership-to-revolutionise-offline-ticket-d13268c60b12">Chalo and Silence Laboratories Forge an Innovative Partnership to Revolutionise Offline Ticket…</a> was originally published in <a href="https://medium.com/silence-laboratories">Silence Laboratories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Redefining the Nomenclature of Web3 Custody]]></title>
            <link>https://medium.com/silence-laboratories/redefining-nomenclature-of-custody-81ee28f20731?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/81ee28f20731</guid>
            <category><![CDATA[mpc]]></category>
            <category><![CDATA[custody]]></category>
            <category><![CDATA[self-custody]]></category>
            <category><![CDATA[threshold-signature]]></category>
            <category><![CDATA[wallet]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Mon, 15 May 2023 04:02:43 GMT</pubDate>
            <atom:updated>2023-06-13T07:52:04.236Z</atom:updated>
            <content:encoded><![CDATA[<p>Jay and the team at <a href="https://medium.com/u/edd49a56936a">Silence Laboratories</a></p><blockquote>Self-Custody, Custodial, Non-Custodial, and similar such jargon are loosely used across the industry by products and protocols, creating confusion and a cascaded loss of trust. Let’s fix this once and for all.</blockquote><p>While nomenclature helps consolidate discussions, it also opens up doors for <em>exploits, </em>especially if the definitions have<em> loose ends</em> because these ultimately affect the Web3 users&#39; trust and expectations<em>.</em></p><blockquote>As part of our series of blogs analyzing designs that enable decentralization through a user-centric lens, we attempt to tighten the definitions of digital asset solutions, serving different constructs of custody.</blockquote><p>‘Custody’, is defined as <a href="https://dictionary.cambridge.org/dictionary/english/custody"><em>the legal right or duty to care for someone or something</em></a><em>. </em>The subjects to be associated with this legal right in our discussion are ‘digital asset account keys’ and ‘their functional controls’ thereof.</p><p>The current wallet landscape maps products claiming to be either <em>self-custodial</em> or <em>custodial </em>in nature. A <em>bilateral </em>conjecture<em> </em>of wallets was fine until they remained within the domain of just private-key custody types. But with the development of numerous wallet types: Social wallets, MPC wallets, Multi-Sig wallets, Custodial wallets, Semi-custodial, Non-Custodial wallets, hybrid wallets, browser-extension based wallets, newly coined ‘Smart Accounts’ à la (Gnosis) Safe, and many more, not to mention the upcoming wave of Ethereum Improvement Proposal (EIP) number 4337 <a href="https://twitter.com/MessariCrypto/status/1633490272318550017?s=20">being deployed on the mainnet</a> which will produce some new types too, the lines in nomenclature and custodialism are blurring.</p><blockquote>What’s worrisome here is that a large number of these wallets project themselves as self-custodial. While competition is healthy for the digital asset ecosystem, we also need to ensure that nomenclature are not misused, and thereby, users misled.</blockquote><p>CEXs have shown multiple instances of how delegated custody is dangerous. Because FTX <a href="https://decrypt.co/resources/coins-keys-wallet">controlled users’ wallets and keys for them</a>, users depended heavily on FTX to access their holdings and were unable to access or withdraw their own assets once FTX began to experience liquidity issues. This is not a new phenomenon, several such cases have been experienced by the industry before also.</p><blockquote>In the previous<a href="https://medium.com/silence-laboratories/the-third-dimension-of-user-centric-studies-for-decentralised-systems-e2579552d0ba"> blog</a>, we proposed a framework to study and analyze digital asset wallets through a tri-dimensional lens: Usability, Security, and Empowerment.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*MzAHpeOLmczJ4GF4" /><figcaption><em>Figure 1: User-centric studies should analyze the empowerment levels of digital asset products.</em></figcaption></figure><p>As a continuation of our effort to standardize the nomenclature and push for better solutions with empowerment in mind, we encourage folks to think about custody<strong> </strong><em>primarily</em> from the perspective of user empowerment.</p><p>Empowerment is a function of the user’s freedom, <em>ownership,</em> and <em>capabilities</em> of their account, generally manifested in the <strong>access </strong>of the wallet’s key. The concept of Empowerment can, therefore, be captured across four features:</p><ol><li><strong>Perpetual access </strong>and <strong>complete control </strong>of digital assets held by the user,</li><li><strong>Permissionless movement of assets</strong> from one wallet service provider to another,</li><li><strong>Permissionless recovery</strong> of accounts/wallets/access to digital assets, and</li><li><strong>Platform Transparency </strong>w.r.t their type of custody and steps to take for safekeeping</li></ol><p>It is to be noted that the majority of these features can be manifested through abilities encompassing possession of a private key and the generation of a valid signature across Web3. Building on the four features and capabilities, we propose the following nomenclature:</p><ul><li><strong>A. Self-Custody<br>A. 1<em> </em></strong><em>Localized Self-Custody</em><strong><br>A.2 </strong><em>Distributed Self-Custody</em></li><li><strong>B. Shared-Custody<br>B.1 </strong><em>Enterprise Shared-Custody</em><strong><br>B2. </strong><em>P2P (Peer-to-Peer) Shared-Custody</em></li><li><strong>C. Delegated Custody<br>C.1</strong> <em>Designated Localized/Centralized Custody<br></em><strong>C.2</strong><em> Designated Distributed Custody</em></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l6AaHGmY3ZSZ3Lf-VGVW7A.png" /><figcaption>Fig. 2 A broader classification based on nature and construct of custody.</figcaption></figure><blockquote>Custody should be seen as Spectrum as a function of empowerment.</blockquote><h4>A. Self-Custody</h4><p>Users of self-custody wallets have total and perpetual access-cum-control of their digital assets. The user controls the private key as a whole or in parts. No matter what, unless not exposed to theft and cyber-attack, they <em>cannot be blocked</em> from performing any transactions. The self-custody wallet service provider<em> cannot deny their users from exporting wallets</em> and shifting to a different service provider. Recovery of the wallet to a new device does not involve the wallet service provider’s approval. Users can never be blocked from recovery. All these are possible because <strong><em>the private keys of the wallet are under the control of the users </em></strong>(stored locally in the browser’s or phone’s storage). Since the users completely control their Private Keys, wallet providers cannot fiddle with the user’s funds.</p><blockquote>Note that while the keys are under the control of the users, their <strong><em>localization</em></strong> still possibly leads to a<strong><em> single point of failure</em></strong> (keys can be stolen or users can be phished to type seed phrases) which affects all such wallets; be it MetaMask, Trust Wallet or Exodus.</blockquote><p>On the bright side, the recent adoption of cryptographic methods for decentralization of signatures through <em>MPC-Threshold Signature</em> or <em>Multi-Signatures</em> has led to designs where private keys do not exist as a whole, throughout the lifetime of the wallet; rather key shares are used to either compute a valid signature or generate multi-signature verifications. If the key shares are still controlled by the user somehow, all previously suggested benefits of<em> single private-key-based self-custody </em>wallets can be supported while bringing <strong>risk decentralization</strong> to these wallets.</p><p>In light of the above discussions, we further segregate self-custody into two parts:</p><ol><li><strong>Localized Self-Custody: </strong>Private keys as a whole are locally stored and accessed by the wallets (eg: Trust Wallet, Electrum, Exodus, and MetaMask in their current adopted forms)<br><em>a) Signature:</em> Pull the private key from local storage and generate a signature.<br><em>b) Recovery: </em>Dominantly seed-phrase based.</li><li><strong>Distributed Self-Custody: </strong>Wallets in this category (should/would) provide <em>distributed signature</em> methods wherein private keys do not exist ever as a whole, rather distributed key shares (shards) exist. The distributed nature of self-custody is possible through cryptographic algorithms based on multi-party computation (MPC)-Threshold Signatures, Multi-Signature, etc. <br>It is to be noted that users of these wallets control all key shares and can sign any transaction using <em>MPC-Threshold Signatures</em> (for example, <em>Silent Shard</em> by<a href="https://silencelaboratories.com/"><em> Silence Laboratories </em></a><em>where distributed key-shares are agreed between user’s devices during the first installation of the distributed key generation (DKG) phase, while setting-up an MPC wallet or exporting an EOA wallet to MPC).</em> Multi-sig (for example, SAFE (Gnosis-based Multi-Sig between different users))<em> </em>can also enable distributed self-custody smart-contract(SC) wallets, through some hybrid innovations<em>. </em>Several account abstraction SC and hybrid wallets, with all signing factors under the user’s control, will also fall under this category.<br><em>a) Signature:</em> Private keys are never exposed, and distributed signature is generated through relaying MPC protocols between devices or signature aggregation through multi-sigs<br><em>b) Recovery: </em>Cloud-based recoveries, social recovery, enterprise-assisted encrypted backup, self-custodial backup on hardware of Decentralized Storage products, etc.</li></ol><blockquote>The beauty of distributed self-custody is in the fact the while there is no single point of failure, thanks to MPC and related technologies, the user still has the very maximum level of empowerment.</blockquote><p>As shown in Table 1, both the designs of self-custody tick all metrics of empowerment, basis the model proposed in the previous <a href="https://medium.com/silence-laboratories/the-third-dimension-of-user-centric-studies-for-decentralised-systems-e2579552d0ba">article</a>. <em>A detailed blog on designing distributed self-custody wallets is coming up soon, stay tuned. </em>We’re already seeing the adoption of such designs by major <a href="https://www.frontier.xyz/blog/frontier-forms-a-strategic-partnership-with-silence-laboratories-to-enhance-wallet-security-via-mpc-technology/">wallet players.</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1IhFJM7PVngUvhlaTXp1Sw.png" /><figcaption>Fig. 3 Distributed MPC between user-controlled devices/forms: Distributed Self-Custody gives the exact same UX as a standard 2FA, which millions of internet users are already habituated to</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hDmMOJZUeYvZkiwYwHS6Dw.png" /><figcaption>Table 1 Different levels of empowerment as a function of the nature of custody.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tTnavD-hItRZssizIdFDvg.png" /><figcaption>Fig. 4 Positioning some of the popular wallets across the nature of custody.</figcaption></figure><h4>B. Shared-Custody</h4><p>In another set of designs, wallets are associated with<em> distributed key shares </em>held in <em>parts by the user and the enterprises</em> (providing wallets) or a set of guardians. A threshold number of parties (each with a key share) must come online (synchronously or asynchronously) and participate in the signature generation process. Alternatively, a threshold number of parties (guardians) can be affiliated with Multi-sig Smart Contract Wallets for validations as well.</p><p>In light of the above discussions, we further segregate shared custody into two verticals:</p><ol><li><strong>Enterprise Shared-Custody: </strong>As a popular construct of distributed signature, wallets have adopted shared key shares between phone wallets and enterprise servers, cloud, rackspace or storage.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1Rlwv4fGrbHJdRv9NPkPag.png" /><figcaption>Fig. 5 Enterprise Shared Custody Model with {2, 2} TSS construct</figcaption></figure><p>The generic design, as popularized by <a href="https://zengo.com/security/">Zengo</a> and <a href="https://docs.cloud.coinbase.com/waas/docs/mpc-waas">Coinbase</a>, has certainly given a boost in security over traditional seed phrases and single private-key-based wallets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8CB6SZq8zWp-YuXza9-50w.png" /><figcaption>Fig. 6 Enterprise Shared Custody Model with {t, n} TSS construct</figcaption></figure><p>We would be seeing multiple variants of such design including 2 to ’n’ number of MPC nodes, each having a key share. Several clients who come to us, adopt something similar wherein the resilience, load-sharing, and risk aversions of the computation have been key decision-makers.</p><p><em>a) Signature:</em> Private keys are never exposed, and distributed signature is generated through chatty MPC protocols between the smartphones and the enterprise servers.<br><em>b) Recovery: </em>Cloud-based recoveries, enterprise-assisted encrypted backup, etc.</p><p><strong>2. P2P Shared-Custody: </strong>In another set of designs, particularly with Multi-Sig constructs, signing authorities are shared between peers. There are examples of social multi-sigs using Gnosis SAFE or MPC-based custody solutions where peers in a company share key shares.</p><p><em>Key notes on Shared-Custody design:</em></p><p>a) While there is a big jump in the dimensions of security, this design lags behind <em>Distributed Self-Custody</em> along the dimensions of<em> empowerment. </em>A user/signer may be blocked (for example, if the server part of the key-share is disallowed from participating in the signature or recovery) from accessing/shifting the account by the enterprise or the co-signing peers.</p><p>b) This is actually desirable under enterprise (digital asset management companies) settings where consensus or hierarchical approval is needed. But a retail user might expect a higher degree of empowerment where nobody can deny them from accessing services.</p><p>More and more, we have to make user and case-centric design decisions when products are first conceptualized, and make them as the first choice.</p><p><strong>C. Delegated Custody<br></strong>In yet another set of designs, keys or key shares are handled by delegated enterprises or a network. We can position any centralized exchange that controls and stores the keys of customers in this category. The mayhem such models can create in the case of deeply centralized enterprises like FTX needs no explanation. When one enterprise has the highest authority, we can call that design a <em>Designated Localized Custody.</em></p><p>When the delegated key shares are held by a group of enterprises or a network of nodes, we can categorize them under <em>Designated Distributed Custody. </em>While the risk is distributed, users are not in ultimate control of their assets. Users typically provide some form of identity to trigger MPC or Multi-Sig protocols and generate a valid transaction/signature on their behalf.</p><p>As part of this blog series, we would be doing deep dive into each of these designs from different perspectives.</p><p>We have come a long long way as an industry — from seed phrases to sophisticated designs around custody. Thanks to the researchers who’ve been pushing the boundaries of cryptography and engineers who have been keeping pace to test, ratify and scale those algorithms. What a time to build together!</p><p><strong>Conclusive remarks:</strong></p><ol><li>Industry nomenclature needs to be revisited and an attempt has to be made in general consensus towards <em>standardization</em>. This blog is just a start.</li><li>While Self-Custody and Shared Custody are at the higher end of the empowerment spectrum, innovation around distributed self-custody and shared custody are emerging as promising paths for safeguarding digital assets.</li></ol><p>If we decide to solve the management of the digital assets at enterprise and retail levels, let’s make user empowerment a moonshot target and march towards building a trustless system.</p><blockquote><em>While distributed self-custody wallets</em> <em>check a much-needed box in the balance across the 3 dimensions,</em> <em>unfortunately</em> there are hardly any EOA wallets in this domain. <em>Silence Laboratories provides </em><strong><em>dedicated SDKs</em></strong><em> for converting existing wallets to distributed self-custody, and shared-custody wallets. As of today, the SDKs use </em><a href="https://medium.com/silence-laboratories/a-compute-perspective-of-mpc-tss-paillier-in-ecdsa-revisited-3e7e92f4bd0a">‘DKLs’ protocols: DKLs18, DKLs19,</a> <em>Lindel17 and GG20 with niche features in access, synchronizations and structuring quorums.</em></blockquote><p>As always, progress is a collaborative affair, and we’re open to feedback and conducting joint research. Aiming to open-source the framework, methodology, and results, with all credits attributed, we welcome you to join the discussion by emailing <a href="/service/mailto:info@silencelaboratories.com">info@silencelaboratories.com</a>, booking a slot to discuss more through <a href="https://calendly.com/jay-prakash-ece09/30min?month=2023-05">Calendly</a>, or writing to us on <a href="https://twitter.com/silentauth">@SilentAuth</a> on Twitter.</p><p>ABOUT US:</p><p><a href="http://silencelaboratories.com/"><em>Silence Laboratories</em></a><em> is a deep-tech authentication provider that offers developer-friendly SDKs and libraries for protocols, wallets, and custodians that can be used to embed/build distributed, zero-trust authentication or authorization products alike. We aim to be a defacto MPC and Proofing product suite for others to build on top of. For ease of integration, we are application, protocol, custodian, and stack agnostic, technologically fluid and future-forward.</em></p><h4><strong>Acknowledgements</strong></h4><p>Thanks to the continuous discussions with <a href="https://t.me/DieSchwarzeKatze">Schwarze Katze</a> and <a href="https://medium.com/u/3ba056ecac33">Alexander Chopan</a>, and for their detailed feedback and edits.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=81ee28f20731" width="1" height="1" alt=""><hr><p><a href="https://medium.com/silence-laboratories/redefining-nomenclature-of-custody-81ee28f20731">Redefining the Nomenclature of Web3 Custody</a> was originally published in <a href="https://medium.com/silence-laboratories">Silence Laboratories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Compute Perspective of MPC-TSS: Paillier in ECDSA Revisited]]></title>
            <link>https://medium.com/silence-laboratories/a-compute-perspective-of-mpc-tss-paillier-in-ecdsa-revisited-3e7e92f4bd0a?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e7e92f4bd0a</guid>
            <category><![CDATA[threshold-signature]]></category>
            <category><![CDATA[multi-party-computation]]></category>
            <category><![CDATA[cybersecurity]]></category>
            <category><![CDATA[wallet]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Tue, 07 Feb 2023 07:07:26 GMT</pubDate>
            <atom:updated>2023-03-08T11:40:11.863Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Yashvanth, Jay, and members at</em><a href="https://silencelaboratories.com/"><em> Silence Laboratories</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HYX7fNXF-5uSoBX0M_m1jQ.png" /></figure><p>Multi-Party Computation (MPC) as a technology has seen promising growth and wider adoption, in large part due to interest fueled by recent attacks exploiting <em>single</em> points of failure in managing private keys. High-profile failures of centralized entities (like FTX, most recently) have particularly added to the interest in shifting towards decentralized financial products, where <a href="https://medium.com/silence-laboratories/the-third-dimension-of-user-centric-studies-for-decentralised-systems-e2579552d0ba">user empowerment is of utmost concern.</a></p><blockquote>This is part of a series of blogs wherein we will shed light on recent developments in distributed authentication, understand the constraints of applications, and discuss problems that we solve.</blockquote><p>The history of MPC dates back to the 1980s, when several foundational results [Yao86, BGW88, GMW86, CCD88] established its feasibility. Threshold Signatures Schemes (TSS), an application of MPC with tailored protocols, enjoys broad deployment in enterprise settings today. The protocols of Lindell, GG19, GG20, CMP to name a few, are used to decentralize key management for the ECDSA Signature Scheme. In this series of blog posts, we will explore an alternative approach to distributing ECDSA signatures, namely the ‘DKLs’ protocols: DKLs18, DKLs19, capable of achieving a different efficiency profile that we find better suited to build our key management solutions.</p><blockquote>Silence Laboratories has had the pleasure of discussing the future in TSS an author of the DKLs series of papers - Yashvanth Kondi, who (disclosure) also leads Silence Laboratories’s research and technical aspects of cryptographic protocols.</blockquote><p>In the foundational Bitcoin whitepaper [Bitcoin], Satoshi Nakamoto specified the ECDSA scheme with the secp256k1 curve to be used as the canonical signature scheme for the Bitcoin protocol. This choice has obvious merits — ECDSA produces compact signatures that are fast to generate and verify. In addition, it has withstood decades of cryptanalysis and enjoys wide compatibility across audited libraries. However, its <em>non-linear</em> structure has famously posed a challenge for MPC protocol designers aiming to decentralize its computation.</p><h4>A. <strong>A Recap of Threshold Signatures</strong></h4><p><a href="https://medium.com/silence-laboratories/how-is-silent-shard-transforming-the-authentication-support-of-crypto-wallets-and-exchanges-5851a3be3ed9">MPC</a> enables a set of parties that do not trust each other, to jointly compute a function over the combination of their individual private inputs. Threshold signatures are a special case of MPC where the function to be computed is a cryptographic digital signature, and the private inputs are<a href="https://medium.com/silence-laboratories/collusion-free-protocol-with-an-honest-mediator-in-secret-sharing-scheme-3993dddc7a10"> secret shares</a> of the signing key.</p><p>Threshold Signature protocols vary in complexity depending on the structure of the signature scheme in consideration; they can be straightforward and non-interactive as in the case of BLS (Boneh, Lynn, and Shacham), mildly interactive (but technically simple) as in the case of EdDSA/Schnorr, or relatively complex, using sophisticated cryptographic primitives such as secure multiplication and zero-knowledge proofs, as in the case of ECDSA.</p><p><em>In general, Threshold Signatures have three phases:</em></p><ul><li>Distributed Key Generation (DKG),</li><li>Distributed Signing, and</li><li>Pro-activization i.e. Key rotation/refresh.</li></ul><p>Each phase has its own distinct set of cryptographic operations and interaction patterns amongst computing nodes that hold shares of the signing key. These nodes can be any device with sufficient computational and memory capability, including smartphones, server nodes, and edge devices.</p><h4>B. <strong>Threshold ECDSA Signing</strong></h4><p>As mentioned earlier, protocols to distribute ECDSA signing are relatively complex, especially as compared to EdDSA/Schnorr signatures which can be decentralized with a simple three-round protocol [Lin22]. However ECDSA was broadly standardized decades ago, and is used across the industry today (including in Bitcoin, Ethereum, etc.) — decentralization was not a ‘top-priority’ concern during standardization.</p><p>Modern MPC protocols are typically designed modularly, with complex tasks being encapsulated in self-contained subroutines. Protocols for ECDSA signing become much simpler to construct given a subroutine for “secure multiplication”, which we will refer to as ‘MUL’ henceforth.</p><blockquote>Roughly, the MUL subroutine is run between a pair of parties, say, Alice and Bob, who input private integers ‘a’ and ‘b’ respectively, and receive randomly distributed private outputs ‘u’ and ‘v’ that respect the correlation: ‘u+v=a*b’.</blockquote><p>Instantiating such an MUL subroutine is where much of the complexity lies, and one common approach to this problem is via Paillier’s encryption scheme [Pai99].</p><h4>C. Threshold ECDSA with Paillier Encryption</h4><p>Paillier-based MUL instantiations are used in several deployed protocols to distribute ECDSA [Lindell 17, GG18, GG20] and are typically accompanied by <em>zero-knowledge proofs</em> (ZKPs) to validate their correct usage. Paillier encryption comes from the family of <em>integer factoring-based cryptography</em>, unlike ECDSA which is based on Elliptic Curves. This mismatch broadens the trustbase of the overall system in terms of mathematical assumptions, as well as requiring more audited and battle-tested libraries (implementing and auditing factoring-based cryptography comes with its own challenges).</p><p>Well-chosen Elliptic Curves are believed to be ‘optimally’ secure — i.e. no attacks better than generic brute force are known — meaning that schemes like ECDSA are safe to use with small, tight parameters. Concretely, most deployments of ECDSA today, operate over 256-bit integers. In contrast, integer-factoring is known to admit solutions better than generic brute force, meaning that concrete parameters have to be inflated to account for such attacks. <br>In practice, this means operating over integers that are over an order of magnitude larger than elliptic curves in bitlength; the Paillier cryptosystem (including encryption and ZKPs) involves arithmetic with integers that are thousands of bits in size, which is of course much more demanding of computational resources. Using Paillier encryption for threshold ECDSA therefore, considerably burdens the <em>low computational footprint</em> that made ECDSA itself a good choice for many devices.</p><p>To develop a better understanding of the performance of Paillier-based MUL in the ECDSA context, we ran benchmarks with a Java TSS library on a diverse set of hardware — including a range of phones and edge devices such as smartwatches. The TL;DR is that the time for Paillier-based key generation exists in the range of 100s of microseconds, and up to 1 full second for a few phones. As the number of parties grows, the aggregated time is in full seconds and accounts for more than 50% of the time taken in the whole protocol. Figure 1 provides further insight into the results of our benchmarks.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hb4cD3cDOPsI71TT1WiJBQ.png" /><figcaption>Figure 1: Sample snapshot from benchmarking conducted by Silence Laboratories across 200+ smartphones (with prices in ascending order)</figcaption></figure><p>Further, we studied how the same library would perform on edge devices such as smartwatches. We ran our {2, 2} TSS wherein the shards were held between a phone and a watch. As shown in Figure 2, Paillier key generation alone takes close to 2 seconds on the smartwatch, and the total time for key generation becomes very perceptible by the user. Putting it together, employing Paillier-MUL in user-facing applications and running on commercial of-the-shelf devices would induce substantial latency, which we would like to avoid as an industry.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7U5RJtsLkobnN70F" /><figcaption>Figure 2: Snapshot from TSS {2, 2} between a SmartPhone (Realme X7) and a SmartWatch (Fossil GEN 6)</figcaption></figure><h4>D. <strong>An Alternative to Paillier: OT-MUL via DKLs</strong></h4><p>MUL is a fundamental MPC building block, and today’s literature is rich with approaches for its instantiation. Rather than building protocols on top of Paillier-based MUL, the threshold ECDSA protocols of Doerner (et al.) [DKLs18, DKLs19] instead make use of <em>Oblivious Transfer</em> (OT) to construct MUL, which we will refer to as OT-MUL henceforth. At a high level, they harden and use Gilboa’s OT-based secure multiplication protocol [Gil99], which when combined with OT ‘Extension’ [Roy22], incurs a computation cost of a few thousand hashes — only a few milliseconds on modern hardware. Their protocol additionally makes use of a few simple consistency checks that obviate the need for any zero-knowledge proofs, while retaining a high-security guarantee.</p><p>Unlike Paillier’s encryption scheme, OT-MUL can be built from the same elliptic curve and hash function as ECDSA itself. This means that<em> integer computations stay </em><strong><em>small</em></strong><em>, and factoring-based cryptography</em> (with its separate mathematical assumptions and implementation/audit complexity) <em>is </em><strong><em>not needed</em></strong>.</p><blockquote>We will dive deeper into the technical details in a future post, but the takeaway, for now, is that the DKLs protocols achieve an efficiency profile that is <strong>much lighter on computation</strong> than any approach that uses Paillier-based MUL.</blockquote><p>Of course, nothing comes for free; the DKLs protocols pay a <em>higher bandwidth</em> cost for OT-MUL. However, our benchmarks show that it is a worthwhile tradeoff to make in many real-world deployment scenarios, including our MPC-based wallet solutions — especially given the proliferation of high-speed connectivity today. In particular, we are able to construct an MPC-based self-custody wallet that, even when using low-budget smart devices, is able to complete signing with latency that is barely perceptible to the user.</p><p>In our <em>upcoming posts</em>, we will also explore other usability concerns that are directly impacted by the DKLs protocols’ <em>smaller computation footprint</em>, including memory and battery consumption. We hope that the insights we provide will serve as a <em>useful reference for designers </em>and <em>architects of scalable TSS solutions</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/972/0*JoWE9QfRvU9hX48p" /><figcaption><a href="https://eprint.iacr.org/2019/523.pdf">https://eprint.iacr.org/2019/523.pdf</a></figcaption></figure><p><em>We welcome you to join in the discussion, collaborate and build together. Please write to us on </em><a href="/service/mailto:jay.prakash@silencelaboratories.com"><em>email</em></a><em> or by booking a slot to discuss things, through our </em><a href="https://calendly.com/jay-prakash-ece09/30min"><em>Calend</em></a><em>ly here.</em></p><blockquote><strong><em>ABOUT US</em></strong></blockquote><p><a href="http://silencelaboratories.com/"><em>Silence Laboratories</em></a><em> is a deep-tech, decentralized, authentication-infrastructure (MPC-focused) provider that offers developer-focused SDKs and libraries, for protocols, wallets, and projects that can be used to embed/build distributed, zero-trust authentication and authorization products, alike. We aim to be a defacto MPC and Proofing product suite for other builders to build on top of. For ease of integration, we are application, protocol, custodian, and stack agnostic, collaboration-friendly, and future-forward.</em></p><h4>References:</h4><ol><li>[Yao86] A. Yao. How to generate and exchange secrets. In Proc. FOCS, pages 162–167, 1986.</li><li>[BGW88] Michael Ben-Or, Shafi Goldwasser, Avi Wigderson: Completeness Theorems for Non-Cryptographic Fault-Tolerant Distributed Computation (extended abstract), 1988. In STOC ’88 Proceedings of the twentieth annual ACM symposium on Theory of computing.</li><li>[GMW86] O. Goldreich, S. Micali, and A. Wigderson. How to play any mental game. In STOC, 1987.</li><li>[CCD88] David Chaum, Claude Crépeau, Ivan Damgård: Multiparty Unconditionally Secure Protocols. In STOC ’88 Proceedings of the twentieth annual ACM symposium on Theory of computing</li><li>[Pai99] Pascal Paillier. Public-key cryptosystems based on composite degree residuosity classes. In EUROCRYPT, 1999.</li><li>[Lindell 17] Yehuda Lindell. Fast secure two-party ECDSA signing. In CRYPTO, 2017.</li><li>Lin22] Yehuda Lindell. Simple three-round multiparty schnorr signing with full simulatability. Cryptology ePrint Archive, 2022.</li><li>[GG 18] Rosario Gennaro and Steven Goldfeder. Fast multiparty threshold ECDSA with fast trustless setup. In CCS, 2018.</li><li>[GG 19] [GG20] Rosario Gennaro and Steven Goldfeder. One round threshold ECDSA with identifiable abort. Cryptology ePrint Archive, Report 2020/540, 2020. <a href="http://eprint.iacr.org/2020/540.">http://eprint.iacr.org/2020/540.</a></li><li>[Roy22] Lawrence Roy. Softspokenot: Communication–computation tradeoffs in OT extension. Cryptology ePrint Archive, Report 2022/192, 2022. <a href="https://ia.cr/2022/192.[Gil99],Niv">https://ia.cr/2022/192.</a></li><li><a href="https://ia.cr/2022/192.[Gil99],Niv">[Gil99] Niv</a> Gilboa. Two-party RSA key generation. In CRYPTO, 1999</li><li>[DKLs18] Jack Doerner, Yashvanth Kondi, Eysa Lee, and Abhi Shelat. Secure two-party threshold ECDSA from ECDSA assumptions. In IEEE S&amp;P, 2018</li><li>[DKLs19] Doerner, J., Kondi, Y., Lee, E., &amp; Shelat, A. (2019, May). Threshold ECDSA from ECDSA assumptions: the multiparty case. In 2019 IEEE Symposium on Security and Privacy (SP) (pp. 1051–1066). IEEE.</li><li>[Bitcoin] <a href="https://bitcoin.org/bitcoin.pdf">https://bitcoin.org/bitcoin.pdf</a></li><li>[CMP] <a href="https://eprint.iacr.org/2020/492">https://eprint.iacr.org/2020/492</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e7e92f4bd0a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/silence-laboratories/a-compute-perspective-of-mpc-tss-paillier-in-ecdsa-revisited-3e7e92f4bd0a">A Compute Perspective of MPC-TSS: Paillier in ECDSA Revisited</a> was originally published in <a href="https://medium.com/silence-laboratories">Silence Laboratories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[NPCI is just the Trailer: Here’s how India can lead the Design of a National Identity (Key-Chain)…]]></title>
            <link>https://medium.com/@jayprakash_81937/npci-is-a-trailer-how-india-can-lead-design-of-a-national-identity-key-chain-framework-5ac06e20b047?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/5ac06e20b047</guid>
            <category><![CDATA[aadhaar]]></category>
            <category><![CDATA[upi]]></category>
            <category><![CDATA[national-wallet]]></category>
            <category><![CDATA[india]]></category>
            <category><![CDATA[digital-identity-wallet]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Mon, 06 Feb 2023 04:26:45 GMT</pubDate>
            <atom:updated>2023-02-06T15:09:43.415Z</atom:updated>
            <content:encoded><![CDATA[<h3>NPCI is just the Trailer: Here’s how India can lead the Design of a National Identity (Key-Chain) Framework.</h3><p><em>This is us, igniting discussions around the creation of a National Identity Infrastructure for universal access to web services: a service that any application can integrate with a one-click login. No OTPs, no passwords, just a universally accepted scan, layered on top of UPI (by </em><a href="https://www.npci.org.in/">National Payments Corporation of India (</a><em>NPCI), backed by Key Management infrastructure. A nationwide Single Sign-On (SSO) to access any web service as a citizen.</em></p><p>Enough of logging in through phone numbers, entering identity numbers and OTPs, and managing so many online credentials for financial service access — that too without empathetic usability and inclusivity! It’s high time that we replicate the success of the NPCI-led UPI framework in a National Identity Framework for mass adoption of standardized formats in all-things-identity.</p><blockquote>UPI and multiple fintech applications built on top of it have revolutionized the payment ecosystem in India, which in nearly unmatched across the globe.</blockquote><p>This article is about enabling a <em>seamless</em> and <em>empowering</em> experience for internet users through a similar framework for <em>National Identity Wallet. </em>Please note that we are <strong><em>not talking </em></strong>about creating new smartphone applications and spending millions on marketing them again. We are talking about developer-friendly libraries, enabled by public infrastructure, that existing wallets can use to empower users with fast and secure log-ins to web services. A national SSO with easy developer support for businesses, if you will.</p><blockquote><strong><em>A. Present Supportive Metrics:</em></strong></blockquote><p>There are three things to be taken into account:</p><ol><li>We already have identity data of a large population base collected over the past decade. Initiatives like <a href="https://indiastack.org/index.html">India Stack</a> have enabled many useful applications through a set of open APIs and digital public goods.</li><li>We have an impeccable proliferation of fintech applications on top of <a href="https://www.npci.org.in/what-we-do/upi/3rd-party-apps">UPI</a> today.</li><li>Access to high-speed cellular internet and smartphones.</li></ol><blockquote><strong><em>B. So what can be the Potentially New Web-Access UX?</em></strong></blockquote><p>Enough of passwords, OTPs! Let’s enable a <em>National Key Management Framework on UPI. The aforementioned</em> three metrics suggest the possibility of the design of a backbone for <em>National Identity Wallets </em>wherein NPCI or a similar agency adds identity-key management infrastructure. We can see a framework where we enable:</p><ul><li><em>Per-Wallet</em> (fintech application in service)<em> </em>and <em>Per-person </em><strong><em>Private Keys</em></strong><em> Derivation </em><strong><em>for identities</em></strong><em>, </em>and</li><li>Multiple seamless web-access modalities <em>such as Enabling Login through UPI || Login-in through PhonePe || Log-in through PayTm or Login through DigiLocker </em>on top of the decentralized key-management layer.</li></ul><p>Leaving technicalities aside for brevity and known ways to implement, <strong>the flow </strong>can be something like this:</p><ul><li>The user goes to a web service.</li><li>A QR code pops up with an exhaustive list of wallets and other associated digital services, the user selects his choice.</li><li>The user opens the corresponding wallet, scans the code, and gets access to the service.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ga76gYb-zpPcNWY5g3bHVQ.png" /><figcaption>A sample of how log-in can look like (<a href="https://cloudin.my.canva.site/">https://cloudin.my.canva.site/</a>)</figcaption></figure><p><em>For Eg: Imagine sign-in into IRCTC (Indian Railway Catering and Tourism Corporation) with just a scan through your PhonePe / DigiLocker / any application that is integrated with these identity framework libraries.</em></p><blockquote><strong><em>C. Design Decisions and Stake Holders</em></strong></blockquote><ol><li>An infrastructure with open access to APIs will enable faster adoption and integrations, rather than building a new application.</li><li>Integration of the key-chain SDK and APIs with some of the existing wallets (given certain compliances on key-management-related security, <a href="https://medium.com/silence-laboratories/the-third-dimension-of-user-centric-studies-for-decentralised-systems-e2579552d0ba">custody, and proper-recovery</a> mechanisms) sounds like the go-to path. We can see such integration with wallets like PhonePe, Paytm, and others.</li><li>Even Digilocker can be a good point for enabling Login-Pass with proper integrations.</li></ol><blockquote><strong><em>D. What’s happening already across different agencies?</em></strong></blockquote><p>Multiple agencies have been proactively working to design the core infra which can enable something like what we are discussing.</p><ol><li>Some commendable works are ongoing under the leadership of CDAC (Centre for Development of Advanced Computing):<strong> e-Pramaan</strong>: <a href="https://epramaan.gov.in/">https://epramaan.gov.in/</a>. e-Pramaan is a good move to create an SSO. MeriPehchaan authenticates the user based on multiple authentication parameters like username, mobile number, Aadhaar, PAN, etc. <em>The basic objective of MeriPehchaan is to </em><strong><em>eliminate individual &amp; repetitive sign-on procedures by centralizing user authentication and identity management at a central identity provider</em></strong><em>.</em></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xgjRNaljwuGrM2BfvW9oGQ.png" /><figcaption>Source: <a href="https://department.epramaan.gov.in/">https://department.epramaan.gov.in/</a></figcaption></figure><p>2. <a href="https://indiastack.org/identity.html">India Stack </a>has built a great framework and suite of digital identity products centered around Aadhaar. India Stack seems to be a good leader who can enable the discussed architecture for Nationwide adoption with a large oath already covered and API ecosystem built by their team.</p><blockquote><strong><em>E. Some successful examples from other Nations:</em></strong></blockquote><p>1. Singapore has seen massive success and a usability boost for the residents through <a href="https://www.singpass.gov.sg/">SingPass.</a> Users can sign in digitally, and remotely to get access and perform transactions.</p><blockquote><em>Singapore launched </em><a href="https://www.singpass.gov.sg/"><em>Singpass</em></a><em> in 2003 and has been enhancing it over the years. Singpass’s initial goal was to authenticate citizens to government agencies and has since expanded to use in the private sector quite successfully. Today, Singaporeans use Singpass to securely access over 1,700 services from more than 460 government agencies and private sector organisations (source: </em><a href="https://auth0.com/blog/auth0-integration-with-singpass/"><em>https://auth0.com/blog/auth0-integration-with-singpass/</em></a><em>)</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_O6kV26nDK6GVob-.png" /></figure><blockquote><strong><em>Existing Validations in India</em></strong></blockquote><ol><li>FASTag is an example of identity binding with NPCI’s efforts.</li><li>The rich API ecosystem by <a href="https://indiastack.org/identity.html">India Stack </a>has already done major efforts.</li></ol><p>3. Further, services like OTPless have started to enable WhatsApp-based logins, which is suggestive of preparing user shift/training. But it is good from the universality, resilience, and privacy perspective that dependence, of the core infra, on third-party enterprises is reduced.</p><blockquote><strong><em>For Developers</em></strong></blockquote><p>A good starting point is looking at the design documents and Auth0 integration support of SingPass: <a href="https://auth0.com/blog/auth0-integration-with-singpass/">https://auth0.com/blog/auth0-integration-with-singpass/</a>.</p><blockquote><strong><em>Policy Makers</em></strong></blockquote><p>We all need to sit with the policy, design, cryptography, and UX decision-makers to enable a developer-friendly stack that orchestrates private-key management and access layers, with easy-to-integrate documentation.</p><p><em>This post is just the tip of the iceberg. Would be happy to create a community-driven discussion and contribute to the building of National Infrastructure products on the discussed lines.</em></p><p><em>Feel free to connect with me </em><strong><em>@jayece09</em></strong><em> on Telegram. Would be happy to discuss collaborations, particularly from a distributed/decentralised key management infra perspective.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5ac06e20b047" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Third Dimension of User-Centric Studies for Decentralised Systems]]></title>
            <link>https://medium.com/silence-laboratories/the-third-dimension-of-user-centric-studies-for-decentralised-systems-e2579552d0ba?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2579552d0ba</guid>
            <category><![CDATA[usability]]></category>
            <category><![CDATA[mpc]]></category>
            <category><![CDATA[wallet]]></category>
            <category><![CDATA[self-custody]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Thu, 02 Feb 2023 15:11:33 GMT</pubDate>
            <atom:updated>2023-02-02T16:00:41.613Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong><em>Usability, Security, and Empowerment</em></strong></h3><p><em>Jay and the team at</em><a href="https://silencelaboratories.com/"><em> Silence Laboratories</em></a></p><blockquote><em>Welcome to the series towards studying and analysing designs that enable decentralisation, through a user-centric lens, with a focus on those catering to the proliferation of security in digital assets.</em></blockquote><p>Above all, infrastructure to enable decentralization inherently aims to empower users. A Digital Asset ecosystem is a powerful concept when put into actual practice. The field is evolving, thanks to developers, founders, and backing from communities and venture funds alike. As of now, the mass adoption of digital assets needs unprecedented user experience, security, and trust improvements.</p><p>We need a scientific approach to conduct <em>qualitative and quantitative evaluations</em> of these designs that govern the transition to decentralization. We attempt to address the most important parameters that need capturing, in this series.</p><blockquote>While Decentralization brings unique opportunities, it also highlights a grey area around user empowerment.</blockquote><p>Centralized systems, financial ecosystems in particular, are positioned at the end of the spectrum in terms of control and capabilities open to the users. While decentralised systems envision complete control placed in the hand of the users, products, and services in design today vary a lot in terms of what users can and cannot do, leading to a <strong>clouded contrast </strong>wrt centralised financial institutions<strong>. </strong><em>Ultimately, these deter mass adoption and affect user trust.</em></p><p>Targeting user-centricity in the approach to design identity, security, and financial products for digital assets, we propose to add a dimension of <em>‘User-Empowerment’</em>. A dedicated framework with acceptable universality is needed for course-correcting design decisions, at both protocols and UX levels, based on closed-loop feedback from users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*peNRd7PTcuPYv6kv" /></figure><p><em>Figure 1:User-centric studies should analyze the empowerment levels of digital asset products.</em></p><p>While security metrics capture <em>single points of failures, probabilities of theft, phishing, shoulder-surfing,</em> and others (covering loss of private keys, account access, etc.), usability caters to <em>cognition and physical efforts </em>(remembering seed-phrases, master password, recovery keys, carrying hardware tokens/wallets, etc.)<em> </em>expected from the user.</p><h4>Capturing Empowerment:</h4><p>In the context of empowerment, the framework tries to capture the following:</p><ul><li><em>Ownership,</em> and</li><li><em>Capabilities </em>of the users of the products providing the interfaces to Digital Assets.</li></ul><p>At the end of the ideal product spectrum, empowerment would mean that:</p><ol><li><strong><em>No service provider should be able to block a user</em></strong> from conducting transactions involving their digital assets. These include, but are not limited to:<br>a. Signature to perform a transaction,<br>b. Account Recovery in case of loss of the form factor managing the product (phone/PC in case of wallets).</li><li><strong>Transparency in operations:</strong> Product and service providers should not be able to move/use assets without the user’s engagement or confirmation.</li><li>A user, if the time comes, should be able to <strong>switch between service providers</strong> at their will, and the enterprise should never be able to block such migration.</li></ol><h4>Framework Design:</h4><p>There have already been commendable studies that led to the stabilization of 2FAs/MFAs, and passwordless solutions where frameworks have been used, such as the framework of<a href="https://www.cl.cam.ac.uk/~fms27/papers/2012-BonneauHerOorSta-password--oakland.pdf"> Bonneau et al</a> [1–3], that considers 25 evaluation parameters, termed as ‘benefits’, derived from the perspective of usability, deployability, and security, that an authentication scheme should ideally provide.</p><p>We add the vector of “empowerment” in the framework to conduct a proper study of products catering to digital assets. Each vector’s parameter is rated as either offering or not offering the benefit; if a solution/product almost offers the benefit, but not quite, we indicate this with the <em>somewhat</em> offering.</p><p>To begin with, an initial attempt has been made to enumerate the offerings of the two most popular form factors of wallets: Browser Plugin and Phone Application-based wallets.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*t30wHGiz9NYaNRnr" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/723/0*lyacc_sJ6IX9Zk0I" /><figcaption><em>Figure: A small Sample of the adopted framework when used to study Plugins and Phone wallets. The full paper for the original framework can be found at References [1]</em></figcaption></figure><p>As is evident, since plugin wallets hold the private keys locally in the browser’s storage, self-empowerment is ideal. At the same time, phone wallets which are controlled by exchanges with keys being stored on centralized servers, land themselves on the deep end of zero empowerment.</p><p>Continuing context from this article, we will keep attempting to define the nomenclature/definition of products (wallets in particular), as a function of who holds the custody and ownership of the wallet primitives (keys, shards, backup, policy). Please expect the below and more, in the other articles to come.</p><p>Our next articles will cover:</p><p>1. <em>Revisiting the ‘nomenclature’ of wallets: b</em>ecause the ‘custodial/non-custodial nomenclature are being heavily misused. While users do not care about these names, they care more about striking a balance between all parameters under discussion.</p><p>2. <em>A detailed study of all digital asset products and where they position themselves in the framework.</em></p><p>3. <em>How user-centric designs and cryptographic primitives can push products towards the optimum balance across the four vectors under discussion</em></p><p>As always, progress is a collaborative affair and we’re open to discussions, improvements, feedback, and conducting joint studies. Aiming to open-source the framework, methodology, documentation, and results, with all credits given, we welcome you to join the discussion by email at info@silencelaboratories.com, booking a slot to discuss more through<a href="https://calendly.com/jay-prakash-ece09/30min"> Calend</a>ly, or writing us on @SilentAuth on Twitter.</p><p>ABOUT US:</p><p><a href="http://silencelaboratories.com/"><em>Silence Laboratories</em></a><em> is a deep-tech authentication provider that offers developer-focused SDKs, and libraries, for protocols, wallets, and projects that can be used to embed/build distributed, zero-trust authentication and authorization products, alike. We aim to be a defacto MPC and Proofing product suite for other builders to build on top of. For ease of integration, we are application, protocol, custodian, and stack agnostic, collaboration-friendly and future-forward.</em></p><h4>References</h4><ol><li>J. Bonneau, C. Herley, P. C. v. Oorschot, and F. Stajano, “<em>The quest to replace passwords: A framework for comparative evaluation of web authentication schemes,</em>” in 2012 IEEE Symposium on Security and Privacy, 2012, pp. 553–567.</li><li><em>Countering Concurrent Login Attacks in “Just Tap- Push-based Authentication: A Redesign and Usability Evaluations,”</em> Jay Prakash et.al., 2021 IEEE European Symposium on Security and Privacy (EuroS&amp;P)</li><li><em>An Empirical Study of a Decentralized Identity Wallet: Usability, Security, and Perspectives on User Control; </em>Maina Korir, University of Bedfordshire; Simon Parkin, TU Delft; Paul Dunphy, OneSpan in 2022 SOUPS USENIX.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2579552d0ba" width="1" height="1" alt=""><hr><p><a href="https://medium.com/silence-laboratories/the-third-dimension-of-user-centric-studies-for-decentralised-systems-e2579552d0ba">The Third Dimension of User-Centric Studies for Decentralised Systems</a> was originally published in <a href="https://medium.com/silence-laboratories">Silence Laboratories</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Can we infuse Plastic-Phobia in the Animal Kingdom?]]></title>
            <link>https://medium.com/@jayprakash_81937/can-we-infuse-plastic-phobia-in-the-animal-kingdom-8397df485eb0?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/8397df485eb0</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[pollution]]></category>
            <category><![CDATA[signal-processing]]></category>
            <category><![CDATA[plastic]]></category>
            <category><![CDATA[animals]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Sun, 15 Mar 2020 07:27:33 GMT</pubDate>
            <atom:updated>2020-03-19T02:17:34.113Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Treating disoriented treatment.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*92Q47u6neV7C1Kgc" /><figcaption>Photo by <a href="https://unsplash.com/@popnzebra?utm_source=medium&amp;utm_medium=referral">Pop &amp; Zebra</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>For a while, let’s forget the policies to curb plastic, let’s forget people’s adoption, let’s forget tonnes of non-degradable polymer being manufactured the moment we read through these lines. Let’s establish the fact that plastic is an epidemic and a luring trap for the helpless animal kingdom. Are not the news and snapshots of dead birds, fishes and animals filled with plastic in digestive tracts disturbing enough to ponder!</p><p>We have gone totally wrong and blindfolded here. Imagine a similar <em>epidemic</em> spreading across <em>homo sapiens</em>. We would have developed a completely different strategy. Our response would have been multi-modal:</p><ul><li>identifying and eradicating sources, including predictive and pro-active measures and</li><li>knowledge transfer across boundaries.</li></ul><p>The later, involving victims and patients in the loop, is a cause that we have been able to control and eradicate worst of infections, accidents and biological hazards. That’s totally absent in this case! Human race’s ability to learn from mistakes, correct them and pass on to peers and generations had led pillars of cognition and unparalleled progress.</p><p><strong>What&#39;s the reason for “mistake” on the animal’s side?</strong></p><p>Helpless animals surely lack these abilities. They are slow self-learners. Can we be responsible peers this time? Let’s help them learn! To tackle tonnes of plastic already spread across demographics of the planet, let’s help them be <em>plastic phobic</em> or at least <em>plastic aware</em>.</p><p>“<em>Animals have very different sensory, perceptive abilities to us. In some cases they’re better and in some cases, they’re worse, but in all cases they’re different,” says Matthew Savoca at the NOAA Southwest Fisheries Science Center in Monterey, California </em>[1]<em>. </em>Majority of aquatic animals tend to have a bit of plastic due to imbibed smell from seaweeds and dead cells [2]. Similarly, terrestrial nomads are attracted towards hills of man-made trash. The smell, due to leftovers and organic wastes acts, a proxy for the consumption of the plastic.</p><p><strong>Directions?</strong></p><p>The problem of finding methods to discourage the consumption of plastics should be confronted with a multi-modal approach: a blend of design thinking, product development, wireless sensing algorithms and animal psychology.</p><p>Foremost step can be to help them learn the presence of plastic, indirectly. The problem can be redefined as “designing a method to intrigue detest for artificial polymers”. It might be a moonshot at first glance but can be accended with proper strategy.</p><p><strong>A. Sensing cum Alert cum Bheviourial Change</strong></p><ul><li>First, can we design a <strong>sensory module </strong>which identifies the presence of polymers?<br>A small electronic module can be configured to use acoustics or radio-frequency waves to identify materials. Acoustics based sensing can either be based on passive listening (filtering clues from noise while animals are digging in for food) [4][5] or can exploit active probing. <strong>Active acoustics sensing</strong> has been proven to be a promising avenue for liquid identification as proposed by a recent work published in Mobisys 2019 from CSAIL, MIT [6]. Reflections from acoustic probes can give an idea about the shape and motion of the objects. Sonic pulses have been long used for underwater communication and object tracking. Applications of underwater tracking should be very helpful for detecting underwater polymers.<br>Even ultra-wideband (UWB) <strong>RF sensing-based</strong> material identification has shown very promising results for the classification of liquids, as proven in LiquidId work by SyNRG group at CSL, UIUC [7]. Though privacy breaching, vision-based path navigation: alerting animals if they approach plastics in their language, can be used as well. Recent works from mmwave based image generations can be enhanced/miniaturised for privacy-preserving scanning.</li><li>Second, we need to study how those miniature devices can be installed as small body-worn chipsets, neck-collars of terrestrial animals or fixed locations at potentials places of piles.</li><li>As an interesting example, some animals, both aquatic and terrestrial, use eco-location to locate and track food/prey and obstacles. We can rather use the concept of friendly-jamming on the same range of frequency to ensure that the areas with polymers are missed!</li><li>Third, we can identify fear creating sensory situations which animals acknowledge, respond and can be tweaked to help them learn through feedback. We can artificially create them, with graceful degradation. Animal behavioural research would a play</li></ul><p><strong>B. Smell Sensing Neuromorphic Chip</strong></p><p>Intel and Cornell University today published a joint paper demonstrating the ability of Intel’s neuromorphic chip, <a href="https://venturebeat.com/2019/07/15/intels-pohoiki-beach-is-a-neuromorphic-computer-capable-of-simulating-8-million-neurons/">Loihi</a>, to learn and recognize 10 hazardous materials from smell — even in the presence of “significant” data noise and occlusion. The co-authors say it shows how neuromorphic computing could be used to detect the precursor smells to explosives, narcotics, polymers, and more [8].<br>That would a good fit to trigger research in these directions!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*200k-jBuznbv4OuVNk6GYg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QZ_HdCet9wCUx-0OB9vbFA.png" /><figcaption>Terrestrial animals can have neck collars with sensing units and mechanism for the transfer of alert. These can either produce smells which these animals don&#39;t like or some sound or mechanical tweaks.</figcaption></figure><p>Serious research in these directions and trials for negating any side effects would save the lives of many animals who are in danger of eating “existing piles of polymers”</p><p>Drop a message to discuss more!</p><p><strong>References</strong></p><ol><li><a href="https://ourblueplanet.bbcearth.com/blog/?article=why-do-marine-animals-eat-plastic"><em>https://ourblueplanet.bbcearth.com/blog/?article=why-do-marine-animals-eat-plastic</em></a></li><li><a href="https://www.popsci.com/fish-eat-plastic-because-it-smells-like-food/"><em>https://www.popsci.com/fish-eat-plastic-because-it-smells-like-food/</em></a></li><li><a href="https://www.eurekalert.org/pub_releases/2018-04/rooi-hca042318.php"><em>https://www.eurekalert.org/pub_releases/2018-04/rooi-hca042318.php</em></a></li><li>Material Classification through Knocking and Grasping by Learning of Structure-Borne Sound under Changing Acoustic Conditions, <a href="https://ieeexplore.ieee.org/document/8560527">https://ieeexplore.ieee.org/document/8560527</a></li><li>ISNN: Impact Sound Neural Network for Audio-Visual Object Classification, Proceedings of the European Conference on Computer Vision (ECCV), 2018</li><li>Liquid Testing with Your Smartphone, <a href="http://people.csail.mit.edu/scyue/projects/capcam/">http://people.csail.mit.edu/scyue/projects/capcam/</a></li><li>LiquID: A Wireless Liquid IDentifier, <a href="https://dl.acm.org/doi/10.1145/3210240.3210345">https://dl.acm.org/doi/10.1145/3210240.3210345</a></li><li>Intel trains neuromorphic chips for smell sensing, <a href="https://venturebeat.com/2020/03/16/intel-trains-neuromorphic-chip-to-detect-10-different-odors/">https://venturebeat.com/2020/03/16/intel-trains-neuromorphic-chip-to-detect-10-different-odors/</a></li><li><em>Gsearch: can animals detect plastic</em></li><li><em>Gsearch: jamming echolocation animals</em></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8397df485eb0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Future of Wireless Networks in BlockChain Era]]></title>
            <link>https://medium.com/@jayprakash_81937/future-of-wireless-networks-in-blockchain-era-f531370382e1?source=rss-e05f73fd3ed5------2</link>
            <guid isPermaLink="false">https://medium.com/p/f531370382e1</guid>
            <category><![CDATA[wireless]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[Jay Prakash]]></dc:creator>
            <pubDate>Wed, 24 Jan 2018 15:02:07 GMT</pubDate>
            <atom:updated>2018-01-24T15:02:07.684Z</atom:updated>
            <content:encoded><![CDATA[<img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f531370382e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>