publish: try

reclaimprotocol · Jan 22, 2024 · e0ca9a9 · e0ca9a9
1 parent 6964503
commit e0ca9a9
Show file tree

Hide file tree

Showing 27 changed files with 452 additions and 101 deletions.
diff --git a/content/posts/gdpr-compliance.md b/content/posts/gdpr-compliance.md
@@ -0,0 +1,23 @@
+---
+title: "Staying GDPR Compliant "
+date: 2024-01-21T16:01:02-05:00
+draft: true
+---
+
+Collecting user data using Reclaim helps you to further your compliance with GDPR. Particularly, GDPR's requirement for explicity consent and purpose limitation.
+
+| In the GDPR, "explicit consent" is detailed under Article 7, which emphasizes that consent must be freely given, specific, informed, and unambiguous, with a clear affirmative action from the data subject. As for "purpose limitation," Article 5(1)(b) states that personal data must be collected for specified, explicit, and legitimate purposes and not further processed in a manner that is incompatible with those purposes. For the full legal text and further details, you can refer to the official GDPR legal text on gdpr-info.eu.
+
+When using Reclaim Protocol, you, the developer would request the data using the following code
+
+```
+const client = new ReclaimClient(appSecret);
+//...
+client.addContext({ message : "Requesting data for Acme Corp Airdrop"});
+/...
+```
+
+When you set the context message in the request, the user is asked to provide an explicit approval to share this information with you. 
+When the user signs in and generates a proof of their data, they are also shown the context for this proof that is being requested. When the proof is generated, the proof also contains a cryptographic affirmation from the user that they have generated the proof for this purpose, and this purpose alone. Even if you store this information on your database, you'd also be storing the affirmation the user provided. 
+
+As long as you store information and use the information for the stated purpose alone - you are GDPR compliant
diff --git a/content/posts/try.md b/content/posts/try.md
@@ -0,0 +1,14 @@
+---
+title: "Try Reclaim"
+date: 2024-01-22T10:36:44-05:00
+draft: false
+---
+
+# Developer App with Sample Integrations
+You can download the "Reclaim Protocol" app from Playstore and App Store
+- [Playstore](https://play.google.com/store/apps/details?id=com.reclaim.protocol)
+- [Appstore](https://apps.apple.com/in/app/reclaim-protocol/id6475267895)
+
+# Try without installing an app
+_Coming Soon_
+
diff --git a/public/index.html b/public/index.html
@@ -128,14 +128,27 @@
 <main class="main"> 
 
 <article class="first-entry"> 
+  <header class="entry-header">
+    <h2 class="entry-hint-parent">Try Reclaim
+    </h2>
+  </header>
+  <div class="entry-content">
+    <p>Developer App with Sample Integrations You can download the “Reclaim Protocol” app from Playstore and App Store
+Playstore Appstore Try without installing an app Coming Soon</p>
+  </div>
+  <footer class="entry-footer"><span title='2024-01-22 10:36:44 -0500 EST'>January 22, 2024</span></footer>
+  <a class="entry-link" aria-label="post link to Try Reclaim" href="https://blog.reclaimprotocol.org/posts/try/"></a>
+</article>
+
+<article class="post-entry"> 
   <header class="entry-header">
     <h2 class="entry-hint-parent">Duplication Counting : Ensuring one proof is used only once, without doxxing the user
     </h2>
   </header>
   <div class="entry-content">
     <p>Introduction For many applications, it will be critical that multiple users are not able to claim the same credential, at least without being detected. For example, suppose a user proves they own some funds in a certain bank account, and then later shares that their banking login to another user who then proves the same credential. An application that requires users t have some minimum collateral will need to be able to detect if the same bank account is being claimed multiple times....</p>
   </div>
-  <footer class="entry-footer"><span title='2024-01-16 14:19:53 -0800 PST'>January 16, 2024</span></footer>
+  <footer class="entry-footer"><span title='2024-01-16 14:19:53 -0800 -0800'>January 16, 2024</span></footer>
   <a class="entry-link" aria-label="post link to Duplication Counting : Ensuring one proof is used only once, without doxxing the user" href="https://blog.reclaimprotocol.org/posts/duplication-counting/"></a>
 </article>
 
@@ -147,7 +160,7 @@ <h2 class="entry-hint-parent">Honeypot Mechanism for additional protocol securit
   <div class="entry-content">
     <p>To discourage attestors from certifying false claims, we want to make this dishonest behavior as financially risky as possible. While the Reporting Mechanism already provides some such financial risk, even more risk can be added through the Honeypot Mechanism. This mechanism which allows users to prepare trap claims, and attestors who accept a bribe to certify a trap claim will get caught in the trap. Trapped attestors are then charged a penalty, and the penalty is given to the user who trapped them as a reward....</p>
   </div>
-  <footer class="entry-footer"><span title='2024-01-16 13:54:06 -0800 PST'>January 16, 2024</span></footer>
+  <footer class="entry-footer"><span title='2024-01-16 13:54:06 -0800 -0800'>January 16, 2024</span></footer>
   <a class="entry-link" aria-label="post link to Honeypot Mechanism for additional protocol security" href="https://blog.reclaimprotocol.org/posts/honey-pot/"></a>
 </article>
 
@@ -162,7 +175,7 @@ <h2 class="entry-hint-parent">Onchain Attestations
 PolygonID, on Polygon Reclaim Proofs can be created using PolygonID. It can also be stored securely for later use on the PolygonID Wallet.
 EAS, on Ethereum, Optimism and Arbitrum Ethereum Attestation Service is a simple attestation framework. One can consume and publish Reclaim Proofs as EAS Attestations....</p>
   </div>
-  <footer class="entry-footer"><span title='2024-01-09 20:33:55 -0800 PST'>January 9, 2024</span></footer>
+  <footer class="entry-footer"><span title='2024-01-09 20:33:55 -0800 -0800'>January 9, 2024</span></footer>
   <a class="entry-link" aria-label="post link to Onchain Attestations" href="https://blog.reclaimprotocol.org/posts/usecase-onchain/"></a>
 </article>
 
@@ -175,7 +188,7 @@ <h2 class="entry-hint-parent">Proof of Personhood in Crypto
     <p>Proof of personhood is essential in may dapps including airdrops, DAO voting, and Quadratic funding. However, there are not great solutions to do proof of personhood at scale effectively. Until today.
 Existing Solutions WorldID World ID is probably the most well funded startup trying to give a unique ID to every user. However, World ID suffers from three problems - scaling the orbs to several millions so that everyone has access to an Orb, trust on the hardware of the Orb hasn’t been compromised or will not be compromised, sharing biometric data as a privacy concern....</p>
   </div>
-  <footer class="entry-footer"><span title='2024-01-09 20:10:55 -0800 PST'>January 9, 2024</span></footer>
+  <footer class="entry-footer"><span title='2024-01-09 20:10:55 -0800 -0800'>January 9, 2024</span></footer>
   <a class="entry-link" aria-label="post link to Proof of Personhood in Crypto" href="https://blog.reclaimprotocol.org/posts/usecase-personhood/"></a>
 </article>
 
@@ -188,7 +201,7 @@ <h2 class="entry-hint-parent">Progressive KYC
     <p>KYC is a loaded term. Depending on your business, jurisdiction and usecase, you’d have different KYC requirements. Reclaim Protocol works with various customers across the spectrum. In this post, I’ll walk you through some of our customers and how they think about KYC - incase, some of it is suitable to you.
 Additionally, a few businesses where KYC requirements are unclear or uncertain - like crypto - we see customers taking the approach of progressive KYC....</p>
   </div>
-  <footer class="entry-footer"><span title='2024-01-09 19:10:15 -0800 PST'>January 9, 2024</span></footer>
+  <footer class="entry-footer"><span title='2024-01-09 19:10:15 -0800 -0800'>January 9, 2024</span></footer>
   <a class="entry-link" aria-label="post link to Progressive KYC" href="https://blog.reclaimprotocol.org/posts/usecase-kyc/"></a>
 </article>
 
@@ -201,7 +214,7 @@ <h2 class="entry-hint-parent">Onboarding &amp; Loyalty Using Reclaim Protocol
     <p>Most apps start with a zerostate for a new user, primarily because there is no data available about the said user. Not any more. Using Reclaim Protocol, app developers can ask their users to import their user profile and activity from a website they already use.
 Until today, it was not possible for a user to import their persona from one website into another. This is largely because of unavailability of APIs on most websites....</p>
   </div>
-  <footer class="entry-footer"><span title='2024-01-09 18:26:21 -0800 PST'>January 9, 2024</span></footer>
+  <footer class="entry-footer"><span title='2024-01-09 18:26:21 -0800 -0800'>January 9, 2024</span></footer>
   <a class="entry-link" aria-label="post link to Onboarding &amp; Loyalty Using Reclaim Protocol" href="https://blog.reclaimprotocol.org/posts/usecase-loyalty/"></a>
 </article>
 
@@ -241,20 +254,6 @@ <h2 class="entry-hint-parent">Reclaim Successfully Passed the ZK Circuit Securit
   <footer class="entry-footer"><span title='2023-10-02 21:41:13 +0500 +0500'>October 2, 2023</span></footer>
   <a class="entry-link" aria-label="post link to Reclaim Successfully Passed the ZK Circuit Security Audit" href="https://blog.reclaimprotocol.org/posts/chacha-circuit-audit/"></a>
 </article>
-
-<article class="post-entry"> 
-  <header class="entry-header">
-    <h2 class="entry-hint-parent">Reclaim Explained, Simply
-    </h2>
-  </header>
-  <div class="entry-content">
-    <p>By Maxwell Allman
-When you log in to your rideshare app, it might say that you’re a 5-star driver. Or when you log in to a banking website, it might say that you’ve never been late on a credit card payment. But how do you prove this information to someone else?
-The Reclaim Protocol lets you take ownership over the data that you receive online. Reclaim lets you share your data with others while:...</p>
-  </div>
-  <footer class="entry-footer"><span title='2023-09-20 23:10:45 +0000 UTC'>September 20, 2023</span></footer>
-  <a class="entry-link" aria-label="post link to Reclaim Explained, Simply" href="https://blog.reclaimprotocol.org/posts/reclaim-explained/"></a>
-</article>
 <footer class="page-footer">
   <nav class="pagination">
     <a class="next" href="https://blog.reclaimprotocol.org/page/2/">Next&nbsp;&nbsp;»

diff --git a/public/index.xml b/public/index.xml
@@ -6,8 +6,16 @@
     <description>Recent content on Reclaim Protocol Official Blog</description>
     <generator>Hugo -- gohugo.io</generator>
     <language>en-us</language>
-    <lastBuildDate>Tue, 16 Jan 2024 14:19:53 -0800</lastBuildDate>
+    <lastBuildDate>Mon, 22 Jan 2024 10:36:44 -0500</lastBuildDate>
     <atom:link href="https://blog.reclaimprotocol.org/index.xml" rel="self" type="application/rss+xml" />
+    <item>
+      <title>Try Reclaim</title>
+      <link>https://blog.reclaimprotocol.org/posts/try/</link>
+      <pubDate>Mon, 22 Jan 2024 10:36:44 -0500</pubDate>
+      <guid>https://blog.reclaimprotocol.org/posts/try/</guid>
+      <description>Developer App with Sample Integrations You can download the &amp;ldquo;Reclaim Protocol&amp;rdquo; app from Playstore and App Store
+Playstore Appstore Try without installing an app Coming Soon</description>
+    </item>
     <item>
       <title>Duplication Counting : Ensuring one proof is used only once, without doxxing the user</title>
       <link>https://blog.reclaimprotocol.org/posts/duplication-counting/</link>

diff --git a/public/page/2/index.html b/public/page/2/index.html
@@ -127,6 +127,20 @@
 </header>
 <main class="main"> 
 
+<article class="post-entry"> 
+  <header class="entry-header">
+    <h2 class="entry-hint-parent">Reclaim Explained, Simply
+    </h2>
+  </header>
+  <div class="entry-content">
+    <p>By Maxwell Allman
+When you log in to your rideshare app, it might say that you’re a 5-star driver. Or when you log in to a banking website, it might say that you’ve never been late on a credit card payment. But how do you prove this information to someone else?
+The Reclaim Protocol lets you take ownership over the data that you receive online. Reclaim lets you share your data with others while:...</p>
+  </div>
+  <footer class="entry-footer"><span title='2023-09-20 23:10:45 +0000 UTC'>September 20, 2023</span></footer>
+  <a class="entry-link" aria-label="post link to Reclaim Explained, Simply" href="https://blog.reclaimprotocol.org/posts/reclaim-explained/"></a>
+</article>
+
 <article class="post-entry"> 
   <header class="entry-header">
     <h2 class="entry-hint-parent">Proof Metrics
@@ -148,7 +162,7 @@ <h2 class="entry-hint-parent">Network State Tools using Reclaim Protocol
   <div class="entry-content">
     <p>Reclaim Protocol can be used to create numerous tools that can fastforward us towards a network state. We are going to be running hacker houses around the world for builders to hack on their ideas for a three to six months with all their basics covered. If you’re a builder who is passionate about network states and is building tools to fastforward the future, join our discord and tell us what you’re building....</p>
   </div>
-  <footer class="entry-footer"><span title='2023-09-11 17:14:31 -0700 PDT'>September 11, 2023</span></footer>
+  <footer class="entry-footer"><span title='2023-09-11 17:14:31 -0700 -0700'>September 11, 2023</span></footer>
   <a class="entry-link" aria-label="post link to Network State Tools using Reclaim Protocol" href="https://blog.reclaimprotocol.org/posts/network-state-tools/"></a>
 </article>
 
@@ -161,7 +175,7 @@ <h2 class="entry-hint-parent">Usecases to build using Reclaim
     <p>Reclaim protocol enables various usecases that were previously never possible. It unlocks a new design space letting builders build novel solutions that leverages the identity and credentials of the user - identities and credentials the users have accrued over time all over the internet. If you are building any of these ideas or products in the periphery of these ideas, we’d love to support with grants, funding, and engineering.
 Verification Usecases Address verification Currently address verification is done in one of the following modes - either by sending a person physically to the said address, or by utilizing addresses on official documentation like national ID, financial documents....</p>
   </div>
-  <footer class="entry-footer"><span title='2023-09-08 03:40:52 -0700 PDT'>September 8, 2023</span></footer>
+  <footer class="entry-footer"><span title='2023-09-08 03:40:52 -0700 -0700'>September 8, 2023</span></footer>
   <a class="entry-link" aria-label="post link to Usecases to build using Reclaim" href="https://blog.reclaimprotocol.org/posts/usecases/"></a>
 </article>
 
@@ -174,7 +188,7 @@ <h2 class="entry-hint-parent">Audits
     <p>Here is the list of audits in progress
 Phase : External Audit ZK Circuits (By ZkSecurity) Phase : Internal Audit TLS Libraries Reclaim SDKs Reclaim Wallet App Reclaim Wallet App Backend Reclaim Attestor </p>
   </div>
-  <footer class="entry-footer"><span title='2023-08-15 12:48:26 -0700 PDT'>August 15, 2023</span></footer>
+  <footer class="entry-footer"><span title='2023-08-15 12:48:26 -0700 -0700'>August 15, 2023</span></footer>
   <a class="entry-link" aria-label="post link to Audits" href="https://blog.reclaimprotocol.org/posts/audits/"></a>
 </article>
 
@@ -187,7 +201,7 @@ <h2 class="entry-hint-parent">Self Sovereign
     <p>Reclaim Protocol values user security, privacy and self soverignity. None of the user data is visible to anybody, including the Reclaim Servers, without the explicit consent of the user.
 Client Side Proofs All the proofs of identity and credentials are generated using the https sessions. These https sessions are initiated and executed completely on client side. The ZK Proofs are also generated completely on client side. So the data encapsulated within the proofs are held exclusively in the user’s device....</p>
   </div>
-  <footer class="entry-footer"><span title='2023-08-15 12:36:44 -0700 PDT'>August 15, 2023</span></footer>
+  <footer class="entry-footer"><span title='2023-08-15 12:36:44 -0700 -0700'>August 15, 2023</span></footer>
   <a class="entry-link" aria-label="post link to Self Sovereign" href="https://blog.reclaimprotocol.org/posts/self-sovereign/"></a>
 </article>
 
@@ -239,21 +253,9 @@ <h2 class="entry-hint-parent">Casestudy: Blue tick for verified devs on Lens Pro
   <div class="entry-content">
     <p>On any social media it is hard to say whether the user is who they really claim to be. For example, a developer may say that they are one of the core contributors to the Aave Github repository and run a scam on social media. One option is for the social media website to ask users to login using Github on their app, use Github API show a blue tick next to the user if they are a core contributor on the repository they claim to be of....</p>
   </div>
-  <footer class="entry-footer"><span title='2023-04-25 06:05:04 -0700 PDT'>April 25, 2023</span></footer>
+  <footer class="entry-footer"><span title='2023-04-25 06:05:04 -0700 -0700'>April 25, 2023</span></footer>
   <a class="entry-link" aria-label="post link to Casestudy: Blue tick for verified devs on Lens Protocol" href="https://blog.reclaimprotocol.org/posts/usecase-github-contributor/"></a>
 </article>
-
-<article class="post-entry"> 
-  <header class="entry-header">
-    <h2 class="entry-hint-parent">Reclaim protocol ensures privacy
-    </h2>
-  </header>
-  <div class="entry-content">
-    <p>Reclaim Protocol can prove that a user opened a certain webpage and the said webpage had some information on it. For example, a user opens their bank account webpage and generates a proof of their bank balance as mentioned on the web page. There are two parts to opening a webpage. The request, and the response. User’s privacy needs to be maintained in the request as well as the response. This post is going to talk about how the request is validated yet keeping the request private....</p>
-  </div>
-  <footer class="entry-footer"><span title='2023-04-18 18:02:09 -0700 PDT'>April 18, 2023</span></footer>
-  <a class="entry-link" aria-label="post link to Reclaim protocol ensures privacy" href="https://blog.reclaimprotocol.org/posts/reclaim-works-on-tls-1-3/"></a>
-</article>
 <footer class="page-footer">
   <nav class="pagination">
     <a class="prev" href="https://blog.reclaimprotocol.org/">