-
Notifications
You must be signed in to change notification settings - Fork 25
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[DOCS]chore: add articles 2019 (#858)
- Loading branch information
1 parent
5d26f56
commit e95e031
Showing
187 changed files
with
2,893 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
--- | ||
--- |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file not shown.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Oops, something went wrong.
Binary file added
BIN
+95.7 KB
packages/apps/docs/public/assets/blog/2019/1_0xKrN3s6yzLmc23Kj7IzxA.webp
Binary file not shown.
Binary file added
BIN
+33.4 KB
packages/apps/docs/public/assets/blog/2019/1_2tCoP7nddaQefAs0TVlygg.webp
Binary file not shown.
Binary file added
BIN
+1.68 MB
packages/apps/docs/public/assets/blog/2019/1_5QtIuWilmEdMKrygNeF79Q.webp
Binary file not shown.
Binary file added
BIN
+51 KB
packages/apps/docs/public/assets/blog/2019/1_68w6sDAETJxMRc_R4wjKmw.webp
Binary file not shown.
Binary file added
BIN
+9.18 KB
packages/apps/docs/public/assets/blog/2019/1_8dws7pDUv76OAVl5jkxWsQ.webp
Binary file not shown.
Binary file added
BIN
+77.5 KB
packages/apps/docs/public/assets/blog/2019/1_Cxpn_A_lQAYXzrV1hHZkCg.webp
Binary file not shown.
Binary file added
BIN
+8.06 KB
packages/apps/docs/public/assets/blog/2019/1_GTgK9aN3QCghHn7Zd9GeoQ.webp
Binary file not shown.
Binary file added
BIN
+7.72 KB
packages/apps/docs/public/assets/blog/2019/1_InzUGFWZa3qVMCGz0vk50g.webp
Binary file not shown.
Binary file added
BIN
+7.68 KB
packages/apps/docs/public/assets/blog/2019/1_IrroP0tY715BTcfxlBHKVg.webp
Binary file not shown.
Binary file added
BIN
+162 KB
packages/apps/docs/public/assets/blog/2019/1_JLawwD1nZ9HTXmK8l6TVaA.webp
Binary file not shown.
Binary file added
BIN
+68.5 KB
packages/apps/docs/public/assets/blog/2019/1_Jc_B0lNInkVYLWQGBjEwuQ.webp
Binary file not shown.
Binary file added
BIN
+21.8 KB
packages/apps/docs/public/assets/blog/2019/1_O0A6f20g8Tmzq-Lv3z_NxA.webp
Binary file not shown.
Binary file added
BIN
+28.7 KB
packages/apps/docs/public/assets/blog/2019/1_byNwUdcRqQV2pExRsgK5KA.webp
Binary file not shown.
Binary file added
BIN
+41.5 KB
packages/apps/docs/public/assets/blog/2019/1_etPC4GFJ1YN9Ik3mlmp1dQ.webp
Binary file not shown.
Binary file added
BIN
+39.1 KB
packages/apps/docs/public/assets/blog/2019/1_gf6Csh42f-b_REgXgnO7Fw.webp
Binary file not shown.
Binary file added
BIN
+489 KB
packages/apps/docs/public/assets/blog/2019/1_kpy5UKorBY2Kp6bf8MYL4g.webp
Binary file not shown.
Binary file added
BIN
+27.6 KB
packages/apps/docs/public/assets/blog/2019/1_qhD0Y3potANXrt29pt4GJA.webp
Binary file not shown.
Binary file added
BIN
+244 KB
packages/apps/docs/public/assets/blog/2019/1_ssB8LvGuMvA270XnoZWHBQ.webp
Binary file not shown.
Binary file added
BIN
+86.5 KB
packages/apps/docs/public/assets/blog/2019/1_tEA_fMNfsI8hnH_M7BEF0w.webp
Binary file not shown.
Binary file added
BIN
+55.8 KB
packages/apps/docs/public/assets/blog/2019/1_wfE_quseTu5kg7RQQtSHzQ.webp
Binary file not shown.
Binary file not shown.
Binary file added
BIN
+20.1 KB
packages/apps/docs/public/assets/blog/2023/1_2TrpexM2c0w9JVwBL2JO9g.webp
Binary file not shown.
Binary file added
BIN
+20.4 KB
packages/apps/docs/public/assets/blog/2023/1_9DXpJZc5zfpIaGdpYrz2cw.webp
Binary file not shown.
Binary file added
BIN
+21.7 KB
packages/apps/docs/public/assets/blog/2023/1_krjtCp-A_aYk8Q4mchWoqg.webp
Binary file not shown.
Binary file added
BIN
+18.2 KB
packages/apps/docs/public/assets/blog/2023/1_o2Ry6xVk_GnK-GvZrICtew.webp
Binary file not shown.
123 changes: 123 additions & 0 deletions
123
...s/src/pages/docs/blogchain/2019/faq-for-kadenas-public-blockchain-2019-12-02.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,123 @@ | ||
--- | ||
title: FAQ for Kadena’s Public Blockchain | ||
description: | ||
Kadena has released mainnet mining to the public, inviting the mining | ||
community to begin solving blocks on the Kadena public blockchain. Kadena’s | ||
network has come alive with activity as miners from all over the world | ||
participate on the Kadena network. | ||
menu: FAQ for Kadena’s Public Blockchain | ||
label: FAQ for Kadena’s Public Blockchain | ||
publishDate: 2019-12-02 | ||
author: Rebecca Rodriguez | ||
layout: blog | ||
--- | ||
|
||
![](/assets/blog/2019/1_ssB8LvGuMvA270XnoZWHBQ.webp) | ||
|
||
# FAQ for Kadena’s Public Blockchain | ||
|
||
[Kadena has released mainnet mining](https://medium.com/kadena-io/kadena-releases-mainnet-mining-and-announces-token-sale-e4a8866da56) | ||
to the public, inviting the mining community to begin solving blocks on the | ||
Kadena public blockchain. Kadena’s network has come alive with activity as | ||
miners from all over the world participate on the Kadena network. | ||
|
||
In addition to mainnet mining, Kadena also announced | ||
[Block Explorer](https://explorer.chainweb.com/), a tool that allows for | ||
real-time monitoring of Kadena’s parallel chains. View the propagation and | ||
braiding of blocks, or dive into any block for key details such as block height, | ||
PoW hash, neighbors, and payload. | ||
|
||
The Kadena network has experienced significant growth in its first few weeks: | ||
|
||
- Before the end of week one, the hash rate grew to over 500 GH/s through CPU | ||
mining alone. | ||
|
||
- Before the end of week three, the network achieved a hash rate of over 4.0 | ||
TH/s with the introduction of GPU mining. | ||
|
||
Kadena will continue to listen to the community and make improvements that | ||
benefit the network’s health and accessibility. | ||
|
||
For those with general questions about participating in Kadena’s mainnet, read | ||
on for more information. | ||
|
||
## Where can I find more information about Kadena tokens? | ||
|
||
Read the | ||
[token economics breakdown](https://medium.com/kadena-io/the-kadena-token-economic-model-8090d7545eef) | ||
for more information on the Kadena token model. | ||
|
||
**What hashing algorithm does Kadena use?** | ||
|
||
Blake2s_256 | ||
|
||
**Where can I find the latest release of binaries?** | ||
|
||
Our latest releases are always open-sourced on GitHub. Chainweb Node is | ||
[here](https://github.com/kadena-io/chainweb-node/releases) and Chainweb Miner | ||
is [here](https://github.com/kadena-io/chainweb-miner/releases). Make sure you | ||
are on the most up-to-date releases, or else it’s possible that your | ||
_miner/node_ will not work properly. | ||
|
||
**What kind of computer is required to run a Kadena public blockchain node?** | ||
|
||
As of publication, the minimum requirements are 2 cores and 2 GB RAM. However, | ||
our recommendation is to use 4 cores and 4 GB RAM. | ||
|
||
Currently, disk space is rarely an issue and a few gigs should be more than | ||
enough. Note that the amount of data in the blockchain will continually grow and | ||
will eventually consume a more significant amount of disk space. Please plan | ||
accordingly. | ||
|
||
**What is the target block time?** | ||
|
||
The target is to reach a new block height every 30 seconds and there are 10 | ||
blocks (i.e. 10 chains) at every height. | ||
|
||
**How can I check my account details, including balance?** | ||
|
||
You can check your account details by sending a Pact local API request calling | ||
*coin.details *on any node. | ||
|
||
For more on how to do this, see: | ||
[Pact Local Queries](https://github.com/kadena-io/chainweb-node/wiki/Pact-Local-Queries) | ||
|
||
**How can I tell if a node is minable?** | ||
|
||
We recommend that you connect to our bootstrap nodes that are closest to your | ||
geography and turn on mining. You can find our list of bootstrap nodes | ||
[here](https://github.com/kadena-io/chainweb-node/wiki). | ||
|
||
You can also test if public nodes are minable by pointing your miner at any of | ||
the available nodes and see if it starts mining. This is easiest if you set the | ||
default log level to debug. For example: | ||
|
||
_./chainweb-miner cpu — cores 2 — node us-w2.chainweb.com:443 — miner-account | ||
<some account> — miner-key <some key> — log-level debug_ | ||
|
||
**How come my balance doesn’t exist on all chains?** | ||
|
||
Kadena’s public blockchain architecture is unique in the fact that account names | ||
are not global entities. Account names, as a result, only exist for the chain(s) | ||
on which you create them. Consequently, you will also have a distinct balance on | ||
each chain. The easiest way to get your account on all chains right now is to | ||
mine. | ||
|
||
**Can my account name be different from my public key?** | ||
|
||
Our public blockchain supports | ||
[cross-chain transfers](https://github.com/kadena-io/chainweb-node/blob/5ba732d8d003d00afb68053bab6b2f549d6157bc/pact/coin-contract/coin.pact#L408) | ||
which allow you to unify your accounts across all chains, but there is always | ||
the possibility that if you wait, you will not be able to reserve the account | ||
name you want. We recommend reserving an account name at your earliest | ||
convenience. | ||
|
||
**Need more support?** | ||
|
||
For a more extensive FAQ about participating in Kadena’s public blockchain, head | ||
over to our | ||
[GitHub](https://github.com/kadena-io/chainweb-node/wiki/Chainweb-FAQ). Keep in | ||
touch with Kadena through | ||
[Discord](https://discordapp.com/invite/bsUcWmX?utm_source=tropyc) or by | ||
following announcements shared on [Twitter](https://twitter.com/kadena_io) and | ||
[Medium](https://medium.com/kadena-io). |
84 changes: 84 additions & 0 deletions
84
...chain/2019/kadena-1-1-release-schedule-chainweb-transfers-roadmap-2019-11-25.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,84 @@ | ||
--- | ||
title: Kadena 1.1 Release Schedule/Chainweb Transfers Roadmap | ||
description: | ||
As part of our ongoing efforts to keep the community informed, we are sharing | ||
the release schedule for Kadena 1.1, which enables coin transfers on the | ||
Kadena public blockchain. After the initial release, the transition from | ||
version 1.0.5 to 1.1 will take place over three stages from December 2 to | ||
December 6, 2019, followed by a ramp-up period of transfer volume. | ||
menu: Kadena 1.1 Release Schedule/Chainweb Transfers Roadmap | ||
label: Kadena 1.1 Release Schedule/Chainweb Transfers Roadmap | ||
publishDate: 2019-11-25 | ||
author: Stuart Popejoy | ||
layout: blog | ||
--- | ||
|
||
![](/assets/blog/2019/1_kpy5UKorBY2Kp6bf8MYL4g.webp) | ||
|
||
# Kadena 1.1 Release Schedule/Chainweb Transfers Roadmap | ||
|
||
_**12/4/19 Update:** Thank you to one of our community members who has | ||
identified a potential security vulnerability. Coming back from the Thanksgiving | ||
holiday, our team investigated this yesterday and has confirmed that it needs to | ||
be addressed. Since we want to be cautious and diligent about preserving network | ||
stability and token value, we are moving the date of enabling token transfers to | ||
**December 17**. Please visit Kadena’s | ||
[Discord](https://discordapp.com/invite/bsUcWmX?source=post_page---------------------------) | ||
channel to share your comments and questions._ | ||
|
||
As part of our ongoing efforts to keep the community informed, we are sharing | ||
the release schedule for Kadena 1.1, which enables coin transfers on the Kadena | ||
public blockchain. After the initial release, the transition from version 1.0.5 | ||
to 1.1 will take place over three stages from December 2 to December 6, 2019, | ||
followed by a ramp-up period of transfer volume. | ||
|
||
## Kadena 1.1 Software Release (December 2): | ||
|
||
- Kadena 1.1 is required to operate the blockchain after the rollover is | ||
complete. | ||
|
||
- It contains the necessary protocol changes to allow coin transfers on the | ||
platform. | ||
|
||
- It also contains important improvements and fixes for the protocol, P2P layer, | ||
transfer performance, and stability. | ||
|
||
## Soft Rollover Stage (December 2–5): | ||
|
||
- Kadena versions 1.0.5 and 1.1 are both fully operational and cross-compatible. | ||
|
||
- Both versions continue to mine empty blocks only (no transfers). | ||
|
||
- Miners are encouraged to update as soon as possible so we can address any | ||
unforeseen issues with the upgrade in the soft rollover stage. | ||
|
||
## Hard Rollover Stage (December 5–6): | ||
|
||
- All Kadena versions 1.0.x will stop mining new blocks at 00:00 UTC December 5. | ||
Miners will have to upgrade at this point to keep mining. | ||
|
||
- Kadena version 1.1 will continue to mine empty blocks as before. | ||
|
||
## Kadena 1.1 Transfers Enabled (December 6): | ||
|
||
- At the end of the hard rollover stage, the Kadena blockchain will start | ||
accepting coin transfers and other coin-related operations. | ||
|
||
- We will provide documentation on methods for performing transfers. | ||
|
||
## Transfer Limit Ramp-up | ||
|
||
Building on the success of the limited beta release on October 30, the Kadena | ||
1.1 blockchain will gradually ramp up transfer throughput over the following | ||
weeks after December 6, so we can continue to address issues that might arise | ||
with the new functionality. | ||
|
||
On December 6, Kadena 1.1 will have a low gas limit that defaults to | ||
approximately 10 transfers per block. We plan to increase this limit | ||
periodically with close coordination with the mining community on an | ||
approximately weekly basis. Initial increases will result in block transfer | ||
limits of 25, 50, etc. We expect to continually release upgrades during this | ||
time to improve transfer handling and enable greater throughput. | ||
|
||
Have questions? Join our [Discord](http://discord.io/kadena) to get answers and | ||
receive updates. |
56 changes: 56 additions & 0 deletions
56
...a-and-rymedi-validate-quality-of-medicinal-products-on-blockchain-2019-12-06.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,56 @@ | ||
--- | ||
title: Kadena and Rymedi Validate Quality of Medicinal Products on Blockchain | ||
description: | ||
Kadena, the first blockchain technology company to come out of JP Morgan’s | ||
Blockchain Center for Excellence, announced a strategic partnership with | ||
Rymedi, providers of a data platform revolutionizing healthcare supply chains. | ||
Rymedi’s integration with Kadena’s blockchain provides immutable supply | ||
genealogy and multi-partner data access, extending existing client | ||
capabilities, ranging from tracking pharmaceutical supply chain in developing | ||
countries such as Mongolia and Kenya to assisting hemp/CBD growers and | ||
extractors looking to bring the safest products to market. | ||
menu: Kadena and Rymedi Validate Quality of Medicinal Products on Blockchain | ||
label: Kadena and Rymedi Validate Quality of Medicinal Products on Blockchain | ||
publishDate: 2019-12-06 | ||
author: Rebecca Rodriguez | ||
layout: blog | ||
--- | ||
|
||
![](/assets/blog/2019/1_8dws7pDUv76OAVl5jkxWsQ.webp) | ||
|
||
# Kadena and Rymedi Validate Quality of Medicinal Products on Blockchain | ||
|
||
[Kadena](http://www.kadena.io/), the first blockchain technology company to come | ||
out of JP Morgan’s Blockchain Center for Excellence, announced a strategic | ||
partnership with [Rymedi](https://www.rymedi.com/), providers of a data platform | ||
revolutionizing healthcare supply chains. Rymedi’s integration with Kadena’s | ||
blockchain provides immutable supply genealogy and multi-partner data access, | ||
extending existing client capabilities, ranging from tracking pharmaceutical | ||
supply chain in developing countries such as Mongolia and Kenya to assisting | ||
hemp/CBD growers and extractors looking to bring the safest products to market. | ||
|
||
By integrating Kadena’s blockchain into its existing platform, Rymedi further | ||
empowers consumers as well as supply chain members with vital data that’s | ||
previously been unavailable. By scanning a simple barcode with their cell | ||
phones, customers can get data about a product’s origin and journey. This | ||
validates purchasing and authenticity, especially useful in geographies and | ||
industries where fraud and quality concerns remain potentially life-threatening | ||
issues. | ||
|
||
“The partnership with Rymedi shows how blockchain technology can positively | ||
contribute to crucial aspects of the healthcare supply chain,” said Will | ||
Martino, Founder and CEO of Kadena. “Many times, illegitimate products can mean | ||
life-or-death for vulnerable communities. We look forward to being part of a | ||
solution that helps prevent the tampering of medicinal products.” | ||
|
||
David Stefanich, CEO of Rymedi shares, “With their deep experience in financial | ||
markets and transaction data, Kadena is a uniquely aligned partner for us. With | ||
several use cases already live around the world, we’re making plans to broaden | ||
our partnership and offer even more value to our customers across healthcare | ||
data-silos.” | ||
|
||
Blockchain’s capacity to guarantee quality in medicinal products allows everyone | ||
from suppliers to customers to have greater confidence. Kadena and Rymedi look | ||
forward to further collaborating on a data platform that ensures verifiable | ||
medicinal products while also discovering new solutions that can benefit | ||
communities across the globe. |
Oops, something went wrong.
e95e031
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
docs-storybook – ./packages/apps/docs
kadena-js-docs.vercel.app
docs-storybook-kadena-js.vercel.app
docs-storybook-git-main-kadena-js.vercel.app
e95e031
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Successfully deployed to the following URLs:
alpha-docs – ./packages/apps/docs
alpha-docs-git-main-kadena-js.vercel.app
docs-silk-two.vercel.app
alpha-docs-kadena-js.vercel.app
alpha-docs.kadena.io