deploy: f7319bd8c8
This commit is contained in:
@@ -4,7 +4,7 @@
|
||||
<meta charset="UTF-8">
|
||||
<meta name="generator" content="Docusaurus v2.4.0">
|
||||
<title data-rh="true">Jackal Proof-of-Persistence | Jackal Chain Docs</title><meta data-rh="true" name="viewport" content="width=device-width,initial-scale=1"><meta data-rh="true" name="twitter:card" content="summary_large_image"><meta data-rh="true" property="og:url" content="https://docs.jackalprotocol.com/docs/protocol/p-o-p"><meta data-rh="true" name="docusaurus_locale" content="en"><meta data-rh="true" name="docsearch:language" content="en"><meta data-rh="true" name="docusaurus_version" content="current"><meta data-rh="true" name="docusaurus_tag" content="docs-default-current"><meta data-rh="true" name="docsearch:version" content="current"><meta data-rh="true" name="docsearch:docusaurus_tag" content="docs-default-current"><meta data-rh="true" property="og:title" content="Jackal Proof-of-Persistence | Jackal Chain Docs"><meta data-rh="true" name="description" content="Jackal Storage functions by a Proof-of-Storage algorithm we call Proof-of-Persistence. The Jackal Proof-of-Persistence (JPOP) works through a series of contracts formed between the storage provider and the user. These contracts contain the Merkle Tree root hash of the file and the information required to prove ownership of the file. Storage Providers are responsible for posting Merkle Proofs within a challenge window determined by the blockchain. These challenge windows require the provider to post the raw chunk of data corresponding to the index of the challenge window alongside the required Merkle Hashes to prove the data belongs to the Merkle Root stored on the contract. These challenge indexes are chosen at random by the blockchain using a block-hash-based random number generator paired with a random data oracle."><meta data-rh="true" property="og:description" content="Jackal Storage functions by a Proof-of-Storage algorithm we call Proof-of-Persistence. The Jackal Proof-of-Persistence (JPOP) works through a series of contracts formed between the storage provider and the user. These contracts contain the Merkle Tree root hash of the file and the information required to prove ownership of the file. Storage Providers are responsible for posting Merkle Proofs within a challenge window determined by the blockchain. These challenge windows require the provider to post the raw chunk of data corresponding to the index of the challenge window alongside the required Merkle Hashes to prove the data belongs to the Merkle Root stored on the contract. These challenge indexes are chosen at random by the blockchain using a block-hash-based random number generator paired with a random data oracle."><link data-rh="true" rel="icon" href="/img/favicon.ico"><link data-rh="true" rel="canonical" href="https://docs.jackalprotocol.com/docs/protocol/p-o-p"><link data-rh="true" rel="alternate" href="https://docs.jackalprotocol.com/docs/protocol/p-o-p" hreflang="en"><link data-rh="true" rel="alternate" href="https://docs.jackalprotocol.com/docs/protocol/p-o-p" hreflang="x-default"><link rel="stylesheet" href="https://fonts.googleapis.com/css2?family=Poppins:wght@700&display=swap">
|
||||
<link rel="stylesheet" href="https://fonts.cdnfonts.com/css/segoe-ui-4"><link rel="stylesheet" href="/assets/css/styles.87b06ad6.css">
|
||||
<link rel="stylesheet" href="https://fonts.cdnfonts.com/css/segoe-ui-4"><link rel="stylesheet" href="/assets/css/styles.79723e9d.css">
|
||||
<link rel="preload" href="/assets/js/runtime~main.8937eb3a.js" as="script">
|
||||
<link rel="preload" href="/assets/js/main.3642d910.js" as="script">
|
||||
</head>
|
||||
|
||||
Reference in New Issue
Block a user