update portal post

Author: daryakaviani

_posts/2023-06-28-Fordefi MPC Wallet.md …/2023-06-28-Crypto Fordefi MPC Wallet.md_posts/2023-06-28-Fordefi MPC Wallet.md renamed to _posts/2023-06-28-Crypto Fordefi MPC Wallet.md _posts/2023-06-28-Fordefi MPC Wallet.md renamed to _posts/2023-06-28-Crypto Fordefi MPC Wallet.md

@@ -0,0 +1,25 @@
+---
+title: Portal Web3 Infrastructure Provider
+date: 2023-07-06 16:40:00 -0800
+categories: [Infrastructure, Crypto Wallet]
+toc: true
+image:
+    path: https://storage.googleapis.com/portal-logos-and-images/portal-product-image.png
+author: parsa
+---
+
+Portal provides end-to-end embedded blockchain infrastructure tools so organizations can launch blockchain products with minimal time or effort. The Portal integration offers various security features, including a firewall which automatically blocks malicious dApps, smart contracts, and addresses.
+
+Portal’s Threshold Signature Scheme (TSS) MPC wallet uses a two of two parallel threshold architecture that ensures users retain full control of their digital assets at signing, backup and recovery. With this design, organizations never take custody of their users’ assets and users can export their private keys to another wallet at any time. Two of two means there are only two signing key shares and two backup key shares and both are required at all times. The key shares are never stored together; the wallet’s private key is never reconstructed. The end user always has control of one signing key share and one backup key share. Neither transactions nor wallet recovery can be completed without the user.
+
+Portal provides a lightweight SDK and fully featured integrations, such as a Wallet Connect v2 integration.
+
+### Code
+
+[Github Repo](https://github.com/portal-hq)
+
+### Links
+
+[Portal Website](https://www.portalhq.io/)
+
+[Developer Docs](https://docs.portalhq.io/)

_posts/2023-07-07-Crypto Portal Web3 Infrastructure Provider.md

@@ -10,6 +10,6 @@ order: 2
 To add a new MPC deployment, you simply need to create a PR with a new Markdown file.
 1. Add yourself as an author in [`/_data/authors.yml`](https://github.com/dots-platform/dots-platform.github.io/blob/master/_data/authors.yml). The first element will be your author ID and the first link will be where on the web people can find you.
 2. Copy the [`/_posts/YYYY-MM-DD-Title.md`](https://github.com/dots-platform/dots-platform.github.io/blob/master/_posts/YYYY-MM-DD-Title.md) template file in the [`/_posts/`](https://github.com/dots-platform/dots-platform.github.io/tree/main/_posts) directory.
-3. Fill in the deployment's information. Details above the `---` and the description are required. For examples of what text and typography is supported, see these [template](https://chirpy.cotes.page/posts/text-and-typography/) [resources](https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/_posts/2019-08-08-text-and-typography.md). Posts should be concise with an emphasis on links to where readers can learn more.
-4. Submit the PR with a description of the change to [github.com/dots-platform/dots-platform.github.io](https://github.com/dots-platform/dots-platform.github.io). To help us out, please [confirm locally](https://chirpy.cotes.page/posts/getting-started/#running-local-server) that your version renders.
+3. Fill in the deployment's information. Details above the `---` and the description are required. For examples of what text and typography is supported, see these [template](https://chirpy.cotes.page/posts/text-and-typography/) [resources](https://github.com/cotes2020/jekyll-theme-chirpy/blob/master/_posts/2019-08-08-text-and-typography.md). Posts should be concise technical summaries with an emphasis on links to where readers can learn more. Refrain from "advertising" the deployment; keep it informational.
+4. Submit the PR with a description of the change to [github.com/dots-platform/dots-platform.github.io](https://github.com/dots-platform/dots-platform.github.io). To help us out, please [confirm locally](https://chirpy.cotes.page/posts/getting-started/#running-local-server) that your version renders. Include how many users the deployment has reached.
 5. We will review the PR, suggest any changes, and hopefully merge your update!