From 605806667552c4e6e39fc994e771225706120385 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 4 May 2023 03:37:51 +0000 Subject: [PATCH] deploy: 2c32d18a2d81449cd9e396045d9cff12d71c142a --- 404.html | 4 ++-- assets/js/{bbf127f0.0a335c46.js => bbf127f0.ec83b8ff.js} | 2 +- .../{runtime~main.d8129260.js => runtime~main.a289d71c.js} | 2 +- docs/contributors/foundation.html | 4 ++-- docs/contributors/join.html | 4 ++-- docs/contributors/labs.html | 4 ++-- docs/ecosystem/grants-funding.html | 4 ++-- docs/ecosystem/partnerships.html | 4 ++-- docs/intro.html | 4 ++-- docs/nodes/install.html | 4 ++-- docs/nodes/nodes/hardware.html | 4 ++-- docs/nodes/nodes/installation.html | 4 ++-- docs/nodes/nodes/mainnet.html | 4 ++-- docs/nodes/nodes/testnet.html | 4 ++-- docs/nodes/providers/building.html | 4 ++-- docs/nodes/providers/setting_up.html | 6 +++--- docs/nodes/validators/joining.html | 4 ++-- docs/official-links/jackal-foundation.html | 4 ++-- docs/official-links/jackal-labs.html | 4 ++-- docs/official-links/jackal-protocol.html | 4 ++-- docs/overview/jackal-tldr.html | 4 ++-- docs/overview/jkl.html | 4 ++-- docs/overview/why-jackal.html | 4 ++-- docs/protocol/encryption.html | 4 ++-- docs/protocol/modules/dsig.html | 4 ++-- docs/protocol/modules/filetree.html | 4 ++-- docs/protocol/modules/jklmint.html | 4 ++-- docs/protocol/modules/lp.html | 4 ++-- docs/protocol/modules/module-overview.html | 4 ++-- docs/protocol/modules/rns.html | 4 ++-- docs/protocol/modules/storage.html | 4 ++-- docs/protocol/modules/wasm.html | 4 ++-- docs/protocol/p-o-p.html | 4 ++-- docs/protocol/storageproviders/casual-build.html | 4 ++-- docs/protocol/storageproviders/diy-serious copy.html | 4 ++-- docs/protocol/storageproviders/enterprise.html | 4 ++-- docs/protocol/storageproviders/overview.html | 4 ++-- docs/protocol/tokens.html | 4 ++-- docs/protocol/validators.html | 4 ++-- docs/using-jackal/dashboard.html | 4 ++-- docs/using-jackal/delegate.html | 4 ++-- docs/using-jackal/fund.html | 4 ++-- docs/using-jackal/wallet/keplr.html | 4 ++-- index.html | 4 ++-- markdown-page.html | 4 ++-- 45 files changed, 89 insertions(+), 89 deletions(-) rename assets/js/{bbf127f0.0a335c46.js => bbf127f0.ec83b8ff.js} (54%) rename assets/js/{runtime~main.d8129260.js => runtime~main.a289d71c.js} (98%) diff --git a/404.html b/404.html index 5238a75..075b355 100644 --- a/404.html +++ b/404.html @@ -5,13 +5,13 @@ Page Not Found | Jackal Chain Docs - +
Skip to main content

Page Not Found

We could not find what you were looking for.

Please contact the owner of the site that linked you to the original URL and let them know their link is broken.

- + \ No newline at end of file diff --git a/assets/js/bbf127f0.0a335c46.js b/assets/js/bbf127f0.ec83b8ff.js similarity index 54% rename from assets/js/bbf127f0.0a335c46.js rename to assets/js/bbf127f0.ec83b8ff.js index 00c1eb2..5a6da2a 100644 --- a/assets/js/bbf127f0.0a335c46.js +++ b/assets/js/bbf127f0.ec83b8ff.js @@ -1 +1 @@ -"use strict";(self.webpackChunkcanine_docs=self.webpackChunkcanine_docs||[]).push([[5863],{3905:(e,t,n)=>{n.d(t,{Zo:()=>c,kt:()=>h});var r=n(7294);function o(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function a(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function i(e){for(var t=1;t=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var s=r.createContext({}),p=function(e){var t=r.useContext(s),n=t;return e&&(n="function"==typeof e?e(t):i(i({},t),e)),n},c=function(e){var t=p(e.components);return r.createElement(s.Provider,{value:t},e.children)},u="mdxType",d={inlineCode:"code",wrapper:function(e){var t=e.children;return r.createElement(r.Fragment,{},t)}},m=r.forwardRef((function(e,t){var n=e.components,o=e.mdxType,a=e.originalType,s=e.parentName,c=l(e,["components","mdxType","originalType","parentName"]),u=p(n),m=o,h=u["".concat(s,".").concat(m)]||u[m]||d[m]||a;return n?r.createElement(h,i(i({ref:t},c),{},{components:n})):r.createElement(h,i({ref:t},c))}));function h(e,t){var n=arguments,o=t&&t.mdxType;if("string"==typeof e||o){var a=n.length,i=new Array(a);i[0]=m;var l={};for(var s in t)hasOwnProperty.call(t,s)&&(l[s]=t[s]);l.originalType=e,l[u]="string"==typeof e?e:o,i[1]=l;for(var p=2;p{n.r(t),n.d(t,{assets:()=>s,contentTitle:()=>i,default:()=>d,frontMatter:()=>a,metadata:()=>l,toc:()=>p});var r=n(7462),o=(n(7294),n(3905));const a={sidebar_position:2},i="Setting Up JProvd",l={unversionedId:"nodes/providers/setting_up",id:"nodes/providers/setting_up",title:"Setting Up JProvd",description:"Pre-Requisites",source:"@site/docs/nodes/providers/2_setting_up.md",sourceDirName:"nodes/providers",slug:"/nodes/providers/setting_up",permalink:"/docs/nodes/providers/setting_up",draft:!1,editUrl:"https://github.com/JackalLabs/canine-docs/blob/master/docs/nodes/providers/2_setting_up.md",tags:[],version:"current",sidebarPosition:2,frontMatter:{sidebar_position:2},sidebar:"tutorialSidebar",previous:{title:"Creating Provider",permalink:"/docs/nodes/providers/building"}},s={},p=[{value:"Pre-Requisites",id:"pre-requisites",level:2},{value:"Installing",id:"installing",level:2},{value:"Initializing",id:"initializing",level:2}],c={toc:p},u="wrapper";function d(e){let{components:t,...n}=e;return(0,o.kt)(u,(0,r.Z)({},c,n,{components:t,mdxType:"MDXLayout"}),(0,o.kt)("h1",{id:"setting-up-jprovd"},"Setting Up JProvd"),(0,o.kt)("h2",{id:"pre-requisites"},"Pre-Requisites"),(0,o.kt)("p",null,"See ",(0,o.kt)("a",{parentName:"p",href:"/docs/nodes/install"},"Set-up"),"."),(0,o.kt)("h2",{id:"installing"},"Installing"),(0,o.kt)("admonition",{type:"tip"},(0,o.kt)("p",{parentName:"admonition"},"Check latest version ",(0,o.kt)("a",{parentName:"p",href:"https://github.com/JackalLabs/canine-provider/releases"},"here"),".")),(0,o.kt)("admonition",{type:"note"},(0,o.kt)("p",{parentName:"admonition"},"'Setting Up' instructions must be followed fully to add necessary golang path info to the current users ~/.profile. If these steps are skipped, 'make install' will not build jprovd--the provider daemon. Please ensure to perform the below steps as the 'jackal' user you previously made. ")),(0,o.kt)("p",null,"Install make and confirm installation. "),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"sudo apt update\n\nsudo apt install make\n\nmake --version\n\n")),(0,o.kt)("p",null,"Build jprovd and source the .profile to ensure your shell can find jprovd. Confirm installation. "),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"git clone https://github.com/JackalLabs/canine-provider.git\n\ncd canine-provider \n\ngit pull\n\ngit checkout {version}\n\nmake install\n\nsource ~/.profile\n\njprovd --version \n\n")),(0,o.kt)("p",null,"If you used ZFS to make a zpool. Give ownership of the zpool to the jackal user. "),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"\nsudo chown -R jackal:jackal /{pool-name}\n\n")),(0,o.kt)("h2",{id:"initializing"},"Initializing"),(0,o.kt)("admonition",{type:"tip"},(0,o.kt)("p",{parentName:"admonition"},"Your keybase identity can be left as ",(0,o.kt)("inlineCode",{parentName:"p"},'""')," if you don't want to link your provider to keybase.")),(0,o.kt)("ol",null,(0,o.kt)("li",{parentName:"ol"},"Export the path to your storage pool ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"export PHOME={path-to-pool-from-before}\n")),(0,o.kt)("ol",{start:2},(0,o.kt)("li",{parentName:"ol"},"Generate your provider's private key ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd client gen-key --home=$PHOME\n")),(0,o.kt)("ol",{start:3},(0,o.kt)("li",{parentName:"ol"},"Configure the chain-id ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd client config chain-id {chain-id} --home=$PHOME\n")),(0,o.kt)("ol",{start:4},(0,o.kt)("li",{parentName:"ol"},"Configure the rpc node your provider will use to connect to the chain ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd client config node {your node} --home=$PHOME\n")),(0,o.kt)("p",null,"Some users may find it easier to complete steps 3 and 4 manually. Instructions for Ubuntu are below:"),(0,o.kt)("p",null,"In your terminal, while inside of the PHOME directory, type 'nautilus'. This will open the nautilus file explorer.\nAt the top right corner, make sure 'Show Hidden Files' is checked.\nNavigate to your '.jackal-storage' folder to access the config folder.\nOpen the client.toml file to manually type in the 'chain-id' and 'node'.\nSave and close the client.toml file."),(0,o.kt)("p",null,"Testnet and Mainnet chain-ids can be found here: ",(0,o.kt)("a",{parentName:"p",href:"https://github.com/JackalLabs/jackal-chain-assets"},"https://github.com/JackalLabs/jackal-chain-assets"),".\nIf you are not running your own tendermint RPC node, Jackal Labs is currently hosting a testnet tendermint RPC node. Endpoint below:"),(0,o.kt)("p",null,(0,o.kt)("a",{parentName:"p",href:"https://testnet-rpc.jackalprotocol.com:443"},"https://testnet-rpc.jackalprotocol.com:443")),(0,o.kt)("p",null,"We will also be hosting a tendermint rpc node for mainnet, which will be made accessible to the public at launch of Jackal Storage. "),(0,o.kt)("p",null,"Before completing step 5 below, your account will need tokens.\nTestnet tokens can be obtained at ",(0,o.kt)("a",{parentName:"p",href:"https://testnet-faucet.jackalprotocol.com/"},"https://testnet-faucet.jackalprotocol.com/"),"\nMainnet tokens can be purchased on ",(0,o.kt)("a",{parentName:"p",href:"https://frontier.osmosis.zone/"},"https://frontier.osmosis.zone/")," "),(0,o.kt)("ol",{start:5},(0,o.kt)("li",{parentName:"ol"},"Initialize the provider ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd init {FQDN} {STORAGE_IN_BYTES} {KEYBASE_IDENTITY} --home=$PHOME\n")),(0,o.kt)("p",null,"example:"),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},'jprovd init "https://storagep1.chainstrategies.cloud" "9000" "" --home=$PHOME\n')),(0,o.kt)("p",null," Please note that 'https://' is required to be included in the FQDN or init will throw an error.\nLink for TB to Bytes converter: ",(0,o.kt)("a",{parentName:"p",href:"https://www.convertunits.com/from/TB/to/byte"},"https://www.convertunits.com/from/TB/to/byte")," "),(0,o.kt)("ol",{start:6},(0,o.kt)("li",{parentName:"ol"},"Start the provider ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd start --home=$PHOME\n")))}d.isMDXComponent=!0}}]); \ No newline at end of file +"use strict";(self.webpackChunkcanine_docs=self.webpackChunkcanine_docs||[]).push([[5863],{3905:(e,t,n)=>{n.d(t,{Zo:()=>c,kt:()=>h});var r=n(7294);function o(e,t,n){return t in e?Object.defineProperty(e,t,{value:n,enumerable:!0,configurable:!0,writable:!0}):e[t]=n,e}function a(e,t){var n=Object.keys(e);if(Object.getOwnPropertySymbols){var r=Object.getOwnPropertySymbols(e);t&&(r=r.filter((function(t){return Object.getOwnPropertyDescriptor(e,t).enumerable}))),n.push.apply(n,r)}return n}function i(e){for(var t=1;t=0||(o[n]=e[n]);return o}(e,t);if(Object.getOwnPropertySymbols){var a=Object.getOwnPropertySymbols(e);for(r=0;r=0||Object.prototype.propertyIsEnumerable.call(e,n)&&(o[n]=e[n])}return o}var s=r.createContext({}),p=function(e){var t=r.useContext(s),n=t;return e&&(n="function"==typeof e?e(t):i(i({},t),e)),n},c=function(e){var t=p(e.components);return r.createElement(s.Provider,{value:t},e.children)},u="mdxType",d={inlineCode:"code",wrapper:function(e){var t=e.children;return r.createElement(r.Fragment,{},t)}},m=r.forwardRef((function(e,t){var n=e.components,o=e.mdxType,a=e.originalType,s=e.parentName,c=l(e,["components","mdxType","originalType","parentName"]),u=p(n),m=o,h=u["".concat(s,".").concat(m)]||u[m]||d[m]||a;return n?r.createElement(h,i(i({ref:t},c),{},{components:n})):r.createElement(h,i({ref:t},c))}));function h(e,t){var n=arguments,o=t&&t.mdxType;if("string"==typeof e||o){var a=n.length,i=new Array(a);i[0]=m;var l={};for(var s in t)hasOwnProperty.call(t,s)&&(l[s]=t[s]);l.originalType=e,l[u]="string"==typeof e?e:o,i[1]=l;for(var p=2;p{n.r(t),n.d(t,{assets:()=>s,contentTitle:()=>i,default:()=>d,frontMatter:()=>a,metadata:()=>l,toc:()=>p});var r=n(7462),o=(n(7294),n(3905));const a={sidebar_position:2},i="Setting Up JProvd",l={unversionedId:"nodes/providers/setting_up",id:"nodes/providers/setting_up",title:"Setting Up JProvd",description:"Pre-Requisites",source:"@site/docs/nodes/providers/2_setting_up.md",sourceDirName:"nodes/providers",slug:"/nodes/providers/setting_up",permalink:"/docs/nodes/providers/setting_up",draft:!1,editUrl:"https://github.com/JackalLabs/canine-docs/blob/master/docs/nodes/providers/2_setting_up.md",tags:[],version:"current",sidebarPosition:2,frontMatter:{sidebar_position:2},sidebar:"tutorialSidebar",previous:{title:"Creating Provider",permalink:"/docs/nodes/providers/building"}},s={},p=[{value:"Pre-Requisites",id:"pre-requisites",level:2},{value:"Installing",id:"installing",level:2},{value:"Initializing",id:"initializing",level:2}],c={toc:p},u="wrapper";function d(e){let{components:t,...n}=e;return(0,o.kt)(u,(0,r.Z)({},c,n,{components:t,mdxType:"MDXLayout"}),(0,o.kt)("h1",{id:"setting-up-jprovd"},"Setting Up JProvd"),(0,o.kt)("h2",{id:"pre-requisites"},"Pre-Requisites"),(0,o.kt)("p",null,"See ",(0,o.kt)("a",{parentName:"p",href:"/docs/nodes/install"},"Set-up"),"."),(0,o.kt)("h2",{id:"installing"},"Installing"),(0,o.kt)("admonition",{type:"tip"},(0,o.kt)("p",{parentName:"admonition"},"Check latest version ",(0,o.kt)("a",{parentName:"p",href:"https://github.com/JackalLabs/canine-provider/releases"},"here"),".")),(0,o.kt)("admonition",{type:"note"},(0,o.kt)("p",{parentName:"admonition"},"'Setting Up' instructions must be followed fully to add necessary golang path info to the current users ~/.profile. If these steps are skipped, 'make install' will not build jprovd--the provider daemon. Please ensure to perform the below steps as the 'jackal' user you previously made. ")),(0,o.kt)("p",null,"Install make and confirm installation. "),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"sudo apt update\n\nsudo apt install make\n\nmake --version\n\n")),(0,o.kt)("p",null,"Build jprovd and source the .profile to ensure your shell can find jprovd. Confirm installation. "),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"git clone https://github.com/JackalLabs/canine-provider.git\n\ncd canine-provider \n\ngit pull\n\ngit checkout {version}\n\nmake install\n\nsource ~/.profile\n\njprovd version\n\n")),(0,o.kt)("p",null,"If you used ZFS to make a zpool. Give ownership of the zpool to the jackal user. "),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"\nsudo chown -R jackal:jackal /{pool-name}\n\n")),(0,o.kt)("h2",{id:"initializing"},"Initializing"),(0,o.kt)("admonition",{type:"tip"},(0,o.kt)("p",{parentName:"admonition"},"Your keybase identity can be left as ",(0,o.kt)("inlineCode",{parentName:"p"},'""')," if you don't want to link your provider to keybase.")),(0,o.kt)("ol",null,(0,o.kt)("li",{parentName:"ol"},"Export the path to your storage pool ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"export PHOME={path-to-pool-from-before}\n")),(0,o.kt)("ol",{start:2},(0,o.kt)("li",{parentName:"ol"},"Generate your provider's private key ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd client gen-key --home=$PHOME\n")),(0,o.kt)("ol",{start:3},(0,o.kt)("li",{parentName:"ol"},"Configure the chain-id ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd client config chain-id {chain-id} --home=$PHOME\n")),(0,o.kt)("ol",{start:4},(0,o.kt)("li",{parentName:"ol"},"Configure the rpc node your provider will use to connect to the chain ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd client config node {your node} --home=$PHOME\n")),(0,o.kt)("p",null,"Some users may find it easier to complete steps 3 and 4 manually. Instructions for Ubuntu are below:"),(0,o.kt)("p",null,"In your terminal, while inside of the PHOME directory, type 'nautilus'. This will open the nautilus file explorer.\nAt the top right corner, make sure 'Show Hidden Files' is checked.\nNavigate to your '.jackal-storage' folder to access the config folder.\nOpen the client.toml file to manually type in the 'chain-id' and 'node'.\nSave and close the client.toml file."),(0,o.kt)("p",null,"Testnet and Mainnet chain-ids can be found here: ",(0,o.kt)("a",{parentName:"p",href:"https://github.com/JackalLabs/jackal-chain-assets"},"https://github.com/JackalLabs/jackal-chain-assets"),".\nIf you are not running your own tendermint RPC node, Jackal Labs is currently hosting a testnet tendermint RPC node. Endpoint below:"),(0,o.kt)("p",null,(0,o.kt)("a",{parentName:"p",href:"https://testnet-rpc.jackalprotocol.com:443"},"https://testnet-rpc.jackalprotocol.com:443")),(0,o.kt)("p",null,"We will also be hosting a tendermint rpc node for mainnet, which will be made accessible to the public at launch of Jackal Storage. "),(0,o.kt)("p",null,"Before completing step 5 below, your account will need tokens.\nTestnet tokens can be obtained at ",(0,o.kt)("a",{parentName:"p",href:"https://testnet-faucet.jackalprotocol.com/"},"https://testnet-faucet.jackalprotocol.com/"),"\nMainnet tokens can be purchased on ",(0,o.kt)("a",{parentName:"p",href:"https://frontier.osmosis.zone/"},"https://frontier.osmosis.zone/")," "),(0,o.kt)("ol",{start:5},(0,o.kt)("li",{parentName:"ol"},"Initialize the provider ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd init {FQDN} {STORAGE_IN_BYTES} {KEYBASE_IDENTITY} --home=$PHOME\n")),(0,o.kt)("p",null,"example:"),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},'jprovd init "https://storagep1.chainstrategies.cloud" "9000" "" --home=$PHOME\n')),(0,o.kt)("p",null," Please note that 'https://' is required to be included in the FQDN or init will throw an error.\nLink for TB to Bytes converter: ",(0,o.kt)("a",{parentName:"p",href:"https://www.convertunits.com/from/TB/to/byte"},"https://www.convertunits.com/from/TB/to/byte")," "),(0,o.kt)("ol",{start:6},(0,o.kt)("li",{parentName:"ol"},"Start the provider ")),(0,o.kt)("pre",null,(0,o.kt)("code",{parentName:"pre",className:"language-sh"},"jprovd start --home=$PHOME\n")))}d.isMDXComponent=!0}}]); \ No newline at end of file diff --git a/assets/js/runtime~main.d8129260.js b/assets/js/runtime~main.a289d71c.js similarity index 98% rename from assets/js/runtime~main.d8129260.js rename to assets/js/runtime~main.a289d71c.js index 9fdca77..c074d25 100644 --- a/assets/js/runtime~main.d8129260.js +++ b/assets/js/runtime~main.a289d71c.js @@ -1 +1 @@ -(()=>{"use strict";var e,a,f,t,b,r={},c={};function d(e){var a=c[e];if(void 0!==a)return a.exports;var f=c[e]={id:e,loaded:!1,exports:{}};return r[e].call(f.exports,f,f.exports,d),f.loaded=!0,f.exports}d.m=r,d.c=c,e=[],d.O=(a,f,t,b)=>{if(!f){var r=1/0;for(i=0;i=b)&&Object.keys(d.O).every((e=>d.O[e](f[o])))?f.splice(o--,1):(c=!1,b0&&e[i-1][2]>b;i--)e[i]=e[i-1];e[i]=[f,t,b]},d.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return d.d(a,{a:a}),a},f=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,d.t=function(e,t){if(1&t&&(e=this(e)),8&t)return e;if("object"==typeof e&&e){if(4&t&&e.__esModule)return e;if(16&t&&"function"==typeof e.then)return e}var b=Object.create(null);d.r(b);var r={};a=a||[null,f({}),f([]),f(f)];for(var c=2&t&&e;"object"==typeof c&&!~a.indexOf(c);c=f(c))Object.getOwnPropertyNames(c).forEach((a=>r[a]=()=>e[a]));return r.default=()=>e,d.d(b,r),b},d.d=(e,a)=>{for(var f in a)d.o(a,f)&&!d.o(e,f)&&Object.defineProperty(e,f,{enumerable:!0,get:a[f]})},d.f={},d.e=e=>Promise.all(Object.keys(d.f).reduce(((a,f)=>(d.f[f](e,a),a)),[])),d.u=e=>"assets/js/"+({53:"935f2afb",54:"344debb6",92:"29af3fe3",229:"03cdf430",604:"ab3acb2a",1078:"5402824b",1148:"3e125dc6",1172:"b46b7d8b",1210:"18a433c4",1232:"7d26c06c",1251:"d07de6bd",1344:"723cbd1b",1385:"15018644",1770:"65b97a36",1817:"9c403616",1947:"e1923b53",2782:"f1994572",2891:"f3769d49",3085:"1f391b9e",3298:"ea96f03c",3523:"e289ecfd",4195:"c4f5d8e4",4286:"c97fbebf",4808:"ebbc57e7",4878:"c894e2df",5202:"c1147f98",5275:"5a6f97fe",5533:"874276e5",5689:"8b564e48",5798:"d1f710bd",5863:"bbf127f0",6164:"9093546b",6174:"23f3f2f9",6683:"a4043c8d",7026:"259b7029",7053:"b0580eac",7275:"7b9432de",7414:"393be207",7918:"17896441",8425:"b1fc7db6",8938:"5da52a1e",8957:"8a56e0ba",9042:"0558eea0",9293:"365ebb01",9404:"d07072fe",9514:"1be78505",9671:"0e384e19",9853:"a5b5e7c9"}[e]||e)+"."+{53:"c50bdb28",54:"11ce8114",92:"b7aa3bac",229:"dbf2f3d6",604:"8c5a5100",1078:"c38ae910",1148:"4cfeb910",1172:"1f4817c2",1210:"5df3b24e",1232:"28f5879a",1251:"cf69f933",1344:"9a02f066",1385:"6fe0ce4b",1770:"7909af7d",1817:"2692038c",1947:"d71b1720",2666:"44faa77f",2782:"ad8a18f1",2891:"76bc0d96",3085:"de6d2725",3298:"9d7c75c8",3523:"d57d11c2",4195:"9c9906aa",4286:"b26e26ff",4808:"cf14015f",4878:"e4f93de7",4972:"6c3329cb",5202:"0681d850",5275:"2b5dfa6c",5533:"1a81b093",5689:"05d51292",5798:"6916f84a",5863:"0a335c46",6164:"8ff0d5a1",6174:"54be1c3c",6683:"46fc645d",7026:"98508766",7053:"ac5d9951",7275:"17b3daef",7414:"c08b369d",7918:"6f3cf1c7",8425:"29933fec",8938:"c612a830",8957:"9518a51b",9042:"dd319e8b",9293:"a122dd0b",9404:"2296011a",9514:"d1735d66",9671:"459dce20",9853:"10cfff95"}[e]+".js",d.miniCssF=e=>{},d.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),d.o=(e,a)=>Object.prototype.hasOwnProperty.call(e,a),t={},b="canine-docs:",d.l=(e,a,f,r)=>{if(t[e])t[e].push(a);else{var c,o;if(void 0!==f)for(var n=document.getElementsByTagName("script"),i=0;i{c.onerror=c.onload=null,clearTimeout(s);var b=t[e];if(delete t[e],c.parentNode&&c.parentNode.removeChild(c),b&&b.forEach((e=>e(f))),a)return a(f)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:c}),12e4);c.onerror=l.bind(null,c.onerror),c.onload=l.bind(null,c.onload),o&&document.head.appendChild(c)}},d.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},d.p="/",d.gca=function(e){return e={15018644:"1385",17896441:"7918","935f2afb":"53","344debb6":"54","29af3fe3":"92","03cdf430":"229",ab3acb2a:"604","5402824b":"1078","3e125dc6":"1148",b46b7d8b:"1172","18a433c4":"1210","7d26c06c":"1232",d07de6bd:"1251","723cbd1b":"1344","65b97a36":"1770","9c403616":"1817",e1923b53:"1947",f1994572:"2782",f3769d49:"2891","1f391b9e":"3085",ea96f03c:"3298",e289ecfd:"3523",c4f5d8e4:"4195",c97fbebf:"4286",ebbc57e7:"4808",c894e2df:"4878",c1147f98:"5202","5a6f97fe":"5275","874276e5":"5533","8b564e48":"5689",d1f710bd:"5798",bbf127f0:"5863","9093546b":"6164","23f3f2f9":"6174",a4043c8d:"6683","259b7029":"7026",b0580eac:"7053","7b9432de":"7275","393be207":"7414",b1fc7db6:"8425","5da52a1e":"8938","8a56e0ba":"8957","0558eea0":"9042","365ebb01":"9293",d07072fe:"9404","1be78505":"9514","0e384e19":"9671",a5b5e7c9:"9853"}[e]||e,d.p+d.u(e)},(()=>{var e={1303:0,532:0};d.f.j=(a,f)=>{var t=d.o(e,a)?e[a]:void 0;if(0!==t)if(t)f.push(t[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var b=new Promise(((f,b)=>t=e[a]=[f,b]));f.push(t[2]=b);var r=d.p+d.u(a),c=new Error;d.l(r,(f=>{if(d.o(e,a)&&(0!==(t=e[a])&&(e[a]=void 0),t)){var b=f&&("load"===f.type?"missing":f.type),r=f&&f.target&&f.target.src;c.message="Loading chunk "+a+" failed.\n("+b+": "+r+")",c.name="ChunkLoadError",c.type=b,c.request=r,t[1](c)}}),"chunk-"+a,a)}},d.O.j=a=>0===e[a];var a=(a,f)=>{var t,b,r=f[0],c=f[1],o=f[2],n=0;if(r.some((a=>0!==e[a]))){for(t in c)d.o(c,t)&&(d.m[t]=c[t]);if(o)var i=o(d)}for(a&&a(f);n{"use strict";var e,a,f,t,b,r={},c={};function d(e){var a=c[e];if(void 0!==a)return a.exports;var f=c[e]={id:e,loaded:!1,exports:{}};return r[e].call(f.exports,f,f.exports,d),f.loaded=!0,f.exports}d.m=r,d.c=c,e=[],d.O=(a,f,t,b)=>{if(!f){var r=1/0;for(i=0;i=b)&&Object.keys(d.O).every((e=>d.O[e](f[o])))?f.splice(o--,1):(c=!1,b0&&e[i-1][2]>b;i--)e[i]=e[i-1];e[i]=[f,t,b]},d.n=e=>{var a=e&&e.__esModule?()=>e.default:()=>e;return d.d(a,{a:a}),a},f=Object.getPrototypeOf?e=>Object.getPrototypeOf(e):e=>e.__proto__,d.t=function(e,t){if(1&t&&(e=this(e)),8&t)return e;if("object"==typeof e&&e){if(4&t&&e.__esModule)return e;if(16&t&&"function"==typeof e.then)return e}var b=Object.create(null);d.r(b);var r={};a=a||[null,f({}),f([]),f(f)];for(var c=2&t&&e;"object"==typeof c&&!~a.indexOf(c);c=f(c))Object.getOwnPropertyNames(c).forEach((a=>r[a]=()=>e[a]));return r.default=()=>e,d.d(b,r),b},d.d=(e,a)=>{for(var f in a)d.o(a,f)&&!d.o(e,f)&&Object.defineProperty(e,f,{enumerable:!0,get:a[f]})},d.f={},d.e=e=>Promise.all(Object.keys(d.f).reduce(((a,f)=>(d.f[f](e,a),a)),[])),d.u=e=>"assets/js/"+({53:"935f2afb",54:"344debb6",92:"29af3fe3",229:"03cdf430",604:"ab3acb2a",1078:"5402824b",1148:"3e125dc6",1172:"b46b7d8b",1210:"18a433c4",1232:"7d26c06c",1251:"d07de6bd",1344:"723cbd1b",1385:"15018644",1770:"65b97a36",1817:"9c403616",1947:"e1923b53",2782:"f1994572",2891:"f3769d49",3085:"1f391b9e",3298:"ea96f03c",3523:"e289ecfd",4195:"c4f5d8e4",4286:"c97fbebf",4808:"ebbc57e7",4878:"c894e2df",5202:"c1147f98",5275:"5a6f97fe",5533:"874276e5",5689:"8b564e48",5798:"d1f710bd",5863:"bbf127f0",6164:"9093546b",6174:"23f3f2f9",6683:"a4043c8d",7026:"259b7029",7053:"b0580eac",7275:"7b9432de",7414:"393be207",7918:"17896441",8425:"b1fc7db6",8938:"5da52a1e",8957:"8a56e0ba",9042:"0558eea0",9293:"365ebb01",9404:"d07072fe",9514:"1be78505",9671:"0e384e19",9853:"a5b5e7c9"}[e]||e)+"."+{53:"c50bdb28",54:"11ce8114",92:"b7aa3bac",229:"dbf2f3d6",604:"8c5a5100",1078:"c38ae910",1148:"4cfeb910",1172:"1f4817c2",1210:"5df3b24e",1232:"28f5879a",1251:"cf69f933",1344:"9a02f066",1385:"6fe0ce4b",1770:"7909af7d",1817:"2692038c",1947:"d71b1720",2666:"44faa77f",2782:"ad8a18f1",2891:"76bc0d96",3085:"de6d2725",3298:"9d7c75c8",3523:"d57d11c2",4195:"9c9906aa",4286:"b26e26ff",4808:"cf14015f",4878:"e4f93de7",4972:"6c3329cb",5202:"0681d850",5275:"2b5dfa6c",5533:"1a81b093",5689:"05d51292",5798:"6916f84a",5863:"ec83b8ff",6164:"8ff0d5a1",6174:"54be1c3c",6683:"46fc645d",7026:"98508766",7053:"ac5d9951",7275:"17b3daef",7414:"c08b369d",7918:"6f3cf1c7",8425:"29933fec",8938:"c612a830",8957:"9518a51b",9042:"dd319e8b",9293:"a122dd0b",9404:"2296011a",9514:"d1735d66",9671:"459dce20",9853:"10cfff95"}[e]+".js",d.miniCssF=e=>{},d.g=function(){if("object"==typeof globalThis)return globalThis;try{return this||new Function("return this")()}catch(e){if("object"==typeof window)return window}}(),d.o=(e,a)=>Object.prototype.hasOwnProperty.call(e,a),t={},b="canine-docs:",d.l=(e,a,f,r)=>{if(t[e])t[e].push(a);else{var c,o;if(void 0!==f)for(var n=document.getElementsByTagName("script"),i=0;i{c.onerror=c.onload=null,clearTimeout(s);var b=t[e];if(delete t[e],c.parentNode&&c.parentNode.removeChild(c),b&&b.forEach((e=>e(f))),a)return a(f)},s=setTimeout(l.bind(null,void 0,{type:"timeout",target:c}),12e4);c.onerror=l.bind(null,c.onerror),c.onload=l.bind(null,c.onload),o&&document.head.appendChild(c)}},d.r=e=>{"undefined"!=typeof Symbol&&Symbol.toStringTag&&Object.defineProperty(e,Symbol.toStringTag,{value:"Module"}),Object.defineProperty(e,"__esModule",{value:!0})},d.p="/",d.gca=function(e){return e={15018644:"1385",17896441:"7918","935f2afb":"53","344debb6":"54","29af3fe3":"92","03cdf430":"229",ab3acb2a:"604","5402824b":"1078","3e125dc6":"1148",b46b7d8b:"1172","18a433c4":"1210","7d26c06c":"1232",d07de6bd:"1251","723cbd1b":"1344","65b97a36":"1770","9c403616":"1817",e1923b53:"1947",f1994572:"2782",f3769d49:"2891","1f391b9e":"3085",ea96f03c:"3298",e289ecfd:"3523",c4f5d8e4:"4195",c97fbebf:"4286",ebbc57e7:"4808",c894e2df:"4878",c1147f98:"5202","5a6f97fe":"5275","874276e5":"5533","8b564e48":"5689",d1f710bd:"5798",bbf127f0:"5863","9093546b":"6164","23f3f2f9":"6174",a4043c8d:"6683","259b7029":"7026",b0580eac:"7053","7b9432de":"7275","393be207":"7414",b1fc7db6:"8425","5da52a1e":"8938","8a56e0ba":"8957","0558eea0":"9042","365ebb01":"9293",d07072fe:"9404","1be78505":"9514","0e384e19":"9671",a5b5e7c9:"9853"}[e]||e,d.p+d.u(e)},(()=>{var e={1303:0,532:0};d.f.j=(a,f)=>{var t=d.o(e,a)?e[a]:void 0;if(0!==t)if(t)f.push(t[2]);else if(/^(1303|532)$/.test(a))e[a]=0;else{var b=new Promise(((f,b)=>t=e[a]=[f,b]));f.push(t[2]=b);var r=d.p+d.u(a),c=new Error;d.l(r,(f=>{if(d.o(e,a)&&(0!==(t=e[a])&&(e[a]=void 0),t)){var b=f&&("load"===f.type?"missing":f.type),r=f&&f.target&&f.target.src;c.message="Loading chunk "+a+" failed.\n("+b+": "+r+")",c.name="ChunkLoadError",c.type=b,c.request=r,t[1](c)}}),"chunk-"+a,a)}},d.O.j=a=>0===e[a];var a=(a,f)=>{var t,b,r=f[0],c=f[1],o=f[2],n=0;if(r.some((a=>0!==e[a]))){for(t in c)d.o(c,t)&&(d.m[t]=c[t]);if(o)var i=o(d)}for(a&&a(f);n Jackal Foundation | Jackal Chain Docs - +

Jackal Foundation

What is the Jackal Foundation?​

The Jackal Foundation serves as the cornerstone of the Jackal Community. As a non-profit organization, it propels development forward by conducting research, testing software, championing projects, and promoting decentralization.

What is the scope of the Jackal Foundation?​

  • Maintain and enhance the Jackal Protocol.
  • Allocate resources to foster ecosystem growth.
  • Establish and oversee Jackal Collectives.
  • Manage the core governance of the Jackal Protocol.
  • Uphold and implement changes resulting from the governance process.
- + \ No newline at end of file diff --git a/docs/contributors/join.html b/docs/contributors/join.html index e84aa5e..b68930c 100644 --- a/docs/contributors/join.html +++ b/docs/contributors/join.html @@ -5,13 +5,13 @@ Join the Community! | Jackal Chain Docs - +

Join the Community!

The Jackal Community is open to all.​

The Jackal Protocol is a transparent, open source, and community-driven project. We welcome all who want to help build a self-custodial and secure digital future.

To contribute; please join below.​

- + \ No newline at end of file diff --git a/docs/contributors/labs.html b/docs/contributors/labs.html index e058133..1e7e484 100644 --- a/docs/contributors/labs.html +++ b/docs/contributors/labs.html @@ -5,13 +5,13 @@ Jackal Labs | Jackal Chain Docs - +

Jackal Labs

Who is Jackal Labs?​

Jackal Labs, a Canadian software development company, played a pivotal role in the early development of the Jackal Protocol. As a decentralized and autonomous entity, the Jackal Protocol is not owned or operated by Jackal Labs. Instead, Jackal Labs contributes to the protocol's evolution by proposing changes through on-chain governance.

What is the scope of Jackal Labs?​

  • Spearhead the initial development of the Jackal Protocol.
  • Engage in ongoing research and development for the Protocol.
  • Suggest improvements to the protocol via the governance process.
- + \ No newline at end of file diff --git a/docs/ecosystem/grants-funding.html b/docs/ecosystem/grants-funding.html index a439179..62c8771 100644 --- a/docs/ecosystem/grants-funding.html +++ b/docs/ecosystem/grants-funding.html @@ -5,13 +5,13 @@ Grants and Funding | Jackal Chain Docs - +

Grants and Funding

The Jackal Foundation facilitates non-equity grants, seed funding, and beyond through our various funding programs. Ecosystem funding aims to focus on the following categories;

  • Research and Development
  • Infrastructure
  • Social Impact
  • dApps
  • Tooling
  • Services

For grants, applications will be reviewed based on the following criteria.

<100k100k - 200k200k+
One round of review.Two rounds of review.Interviews, formal committee review, full pitch.

For seed funding, the Jackal Foundation or Investment Network may support an ecosystem project with equity or token investments. For innovative founders that bring strategic value and adoption to the Jackal Ecosystem, please reach out directly to our team.

- + \ No newline at end of file diff --git a/docs/ecosystem/partnerships.html b/docs/ecosystem/partnerships.html index b52fa46..282ee76 100644 --- a/docs/ecosystem/partnerships.html +++ b/docs/ecosystem/partnerships.html @@ -5,13 +5,13 @@ Partnerships | Jackal Chain Docs - +

Partnerships

Blockchain and web3 native software engineering teams often wish to become core contributors through a partnership with the Jackal Foundation. In a partnership role, the team would be assigned direct tasks and held to a high standard of execution, professionalism, and accountability. If your team desires to partner with the Jackal Foundation, please reach out directly, we look forward to working with you.

- + \ No newline at end of file diff --git a/docs/intro.html b/docs/intro.html index 75b2b3c..0021070 100644 --- a/docs/intro.html +++ b/docs/intro.html @@ -5,13 +5,13 @@ Welcome to Jackal Wiki | Jackal Chain Docs - +

Welcome to Jackal Wiki

Welcome, explorer, to the Jackal Wiki, where you'll embark on a journey to discover a more secure, simple, and self-custodial digital world.

The Jackal Protocol, an open-source and community-driven innovation, fosters a transparent and trustless ecosystem. You've found the ultimate hub for all things Jackal: protocol insights, usage tips, infrastructure knowledge, and unique opportunities.

Our enthusiastic teams at Jackal Labs and the Jackal Foundation diligently maintain the Jackal Wiki. If you happen to spot outdated information, don't hesitate to reach out—your input helps us ensure accuracy for the entire community. Let's shape the future of digital experiences together!

- + \ No newline at end of file diff --git a/docs/nodes/install.html b/docs/nodes/install.html index 11d12bc..b86bee8 100644 --- a/docs/nodes/install.html +++ b/docs/nodes/install.html @@ -5,13 +5,13 @@ Setting Up | Jackal Chain Docs - +

Setting Up

Pre-Requisites​

There are a few things needed before installing.

While logged in as the 'root' or 'admin' user, we add a 'jackal' user and give them root privileges.

Enable Firewall Rules​

Enabling the firewall is important to ensure your hardware remains secure. The following commands will add rules required for access on both validators and providers:

sudo ufw allow 22
sudo ufw allow 80
sudo ufw allow 443

Additional ports are required if you are running a validator:

sudo ufw allow 26657
sudo ufw allow 26658

The only additional port required for a provider is 3333:

sudo ufw allow 3333

If you are running a combined validator/provider, you need to allow all of the above ports. After adding ports to the rules list, you will need to start the firewall:

sudo ufw enable

After starting the firewall, verify all of the required rules are in place by running:

sudo ufw status verbose

Your output should be similar to the following:

Status: active

To                         Action      From
--                         ------      ----
22                         ALLOW       Anywhere
80                         ALLOW       Anywhere
443                        ALLOW       Anywhere
1317                       ALLOW       Anywhere
3333                       ALLOW       Anywhere
26657                      ALLOW       Anywhere
26658                      ALLOW       Anywhere

Create Jackal user​

sudo adduser --gecos "" jackal
sudo usermod -aG sudo jackal

Log in as the jackal user to complete the below steps:

sudo su - jackal

Installing required tools​

This will install the necessary tools to build the jackal chain source, along with lz4 compression tool and jquery tool.

sudo apt update
sudo apt install build-essential lz4 jq

Installing Go​

Follow more in-depth instructions to install Go v1.19 or higher here.

On Ububtu you can install it with:

GOVER=$(curl https://go.dev/VERSION?m=text)
wget https://golang.org/dl/${GOVER}.linux-amd64.tar.gz
sudo rm -rf /usr/local/go && sudo tar -C /usr/local -xzf ${GOVER}.linux-amd64.tar.gz

Add the following golang path info to the current users ~/.profile.

Also add it to the skeleton profile so all new users have it. /etc/skel/.profile

# add environmental variables for Go
if [ -f "/usr/local/go/bin/go" ] ; then
    export GOROOT=/usr/local/go
    export GOPATH=${HOME}/go
    export GOBIN=$GOPATH/bin
    export PATH=${PATH}:${GOROOT}/bin:${GOBIN}
    export GO111MODULE=on
fi

Restarting the shell with youre profile settings or just rebasing them like so is required.

source ~/.profile
- + \ No newline at end of file diff --git a/docs/nodes/nodes/hardware.html b/docs/nodes/nodes/hardware.html index bbf98fd..f0a732a 100644 --- a/docs/nodes/nodes/hardware.html +++ b/docs/nodes/nodes/hardware.html @@ -5,13 +5,13 @@ Hardware | Jackal Chain Docs - +

Hardware

We recommend a minimum hardware requirement of:

  • 4 Cores (modern CPU's)
  • 32GB RAM
  • 1TB of storage (SSD or NVME)

We also recommend running an Ubuntu LTS OS as that is what the binaries have been tested against.

- + \ No newline at end of file diff --git a/docs/nodes/nodes/installation.html b/docs/nodes/nodes/installation.html index 7ab849c..8ddde93 100644 --- a/docs/nodes/nodes/installation.html +++ b/docs/nodes/nodes/installation.html @@ -5,13 +5,13 @@ Installing Canined | Jackal Chain Docs - +

Installing Canined

Pre-Requisites​

See Set-up.

Firewall Configuration​

Configure UFW to only accept traffic on ports we use.

ufw limit ssh/tcp comment 'Rate limit for openssh server'
ufw default deny incoming
ufw default allow outgoing
ufw allow 26656/tcp comment 'JACKAL - Cosmos SDK/Tendermint P2P'
ufw allow 26657/tcp comment 'JACKAL - Cosmos SDK/Tendermint P2P'
ufw enable
tip

Perform the next follow steps as your jackal user with 'sudo' permissions

Creating a Service​

You may want the daemon to run without you needing to supervise it. To turn the executable into a service follow these steps.

First create the service file /etc/systemd/system/canined.service

sudo nano /etc/systemd/system/canined.service

Copy and paste the follow into the service file: (you may need to edit it if you've set a custom home directory location)

[Unit]
Description=Jackal Validator
After=network.target

[Service]
Group=jackal
User=jackal
WorkingDirectory=/home/jackal
ExecStart=/home/jackal/go/bin/canined start
Restart=on-failure
RestartSec=3
LimitNOFILE=8192

[Install]
WantedBy=multi-user.target

Update systemd and enable the service file.

sudo systemctl daemon-reload
sudo systemctl enable canined.service

Building from Source​

Replace <VERSION> with the current running version.

git clone https://github.com/JackalLabs/canine-chain.git
cd canine-chain
git fetch -a
git checkout <VERSION>

make install

From there you will be able to use canined, ex:

canined version
- + \ No newline at end of file diff --git a/docs/nodes/nodes/mainnet.html b/docs/nodes/nodes/mainnet.html index 056d5f9..429a049 100644 --- a/docs/nodes/nodes/mainnet.html +++ b/docs/nodes/nodes/mainnet.html @@ -5,14 +5,14 @@ Joining Mainnet | Jackal Chain Docs - +

Joining Mainnet

tip

Perform the following as the jackal user.

After installing canined. You can join the mainnet by following these steps:

canined init "NODE_NAME" --chain-id=jackal-1

Then we want to replace our generated genesis file with the one used to start the network.

wget -O ~/.canine/config/genesis.json https://cdn.discordapp.com/attachments/1002389406650466405/1034968352591986859/updated_genesis2.json

SEEDS=$(wget https://raw.githubusercontent.com/JackalLabs/canine-mainnet-genesis/master/genesis/seeds.txt -q -O -)
PEERS=`curl -sL https://raw.githubusercontent.com/JackalLabs/canine-mainnet-genesis/master/genesis/peers.txt | sort -R | head -n $PEERCOUNT | awk '{print $1}' | paste -s -d, -`
GAS="0.002ujkl"

sed -i.bak -e "s/^seeds *=.*/seeds = \"$SEEDS\"/; s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" $HOME/.canine/config/config.toml

Backing up key files​

The created node_key.json and priv_validator_key.json cannot be recovered. These files must be backed up.

mkdir ~/key_backup
cp ~/.canine/config/node_key.json ~/key_backup
cp ~/.canine/config/priv_validator_key.json ~/key_backup

You should also keep an offline backup. Using a program like WinSCP, you can easily copy these files to your personal desktop for safe storage/backup.

Syncing to Current Height​

Snapshot method​

Get a snapshot here.

For the sake of this guide, the snapshot we download is named jackal.tar.lz4

If you plan on becoming a validator, before using the unsafe-reset-all flag, always besure to back up your priv_validator_state.json file. 

canined unsafe-reset-all --keep-addr-book
lz4 -c -d jackal.tar.lz4  | tar -x -C $HOME/.canine

Then start the chain again.

State Sync Method​

There are a couple of ways to go about doing state sync. First is the easier route. Visit Ping.pub for Jackals State Sync configuration settings.

Next, copy these settings from Ping.pub to your config.toml in the [statesync] section.

It should look similar to this:

#######################################################
###         State Sync Configuration Options        ###
#######################################################
[statesync]
# State sync rapidly bootstraps a new node by discovering, fetching, and restoring a state machine
# snapshot from peers instead of fetching and replaying historical blocks. Requires some peers in
# the network to take and serve state machine snapshots. State sync is not attempted if the node
# has any local state (LastBlockHeight > 0). The node will have a truncated block history,
# starting from the height of the snapshot.
enable = true

# RPC servers (comma-separated) for light client verification of the synced state machine and
# retrieval of state data for node bootstrapping. Also needs a trusted height and corresponding
# header hash obtained from a trusted source, and a period during which validators can be trusted.
#
# For Cosmos SDK-based chains, trust_period should usually be about 2/3 of the unbonding time (~2
# weeks) during which they can be financially punished (slashed) for misbehavior.
rpc_servers = "https://rpc.jackalprotocol.com:443,https://rpc.jackalprotocol.com:443"
trust_height = 333000
trust_hash = "1685850c2d115a86af9059bd3f36a4fbbb0e8ba7f37863d517b6d2f54116daca"
trust_period = "168h"  # 2/3 of unbonding time

# Time to spend discovering snapshots before initiating a restore.
discovery_time = "15s"

# Temporary directory for state sync snapshot chunks, defaults to the OS tempdir (typically /tmp).
# Will create a new, randomly named directory within, and remove it when done.
temp_dir = ""

# The timeout duration before re-requesting a chunk, possibly from a different
# peer (default: 1 minute).
chunk_request_timeout = "10s"

# The number of concurrent chunk fetchers to run (default: 1).
chunk_fetchers = "42"

State syncing can take up to a few minutes to complete. Watch the logs to ensure it's happening. When a snapshot is found, you will see output in your log that is similar to this:

1PM INF Discovered new snapshot format=1 hash="S.�h�F���\"\x1d6+\x1e���ޅ��`v@�ц�����" height=1810000 module=statesync

It will download, verify, and apply chuncks of blockchain data. When it finishes you will see it catching up to blocks

State Sync Method 2​

The follow commandline code will edit your config.toml with the proper information for state syncing to the most recent snapshot 3000 blocks and beyond.

STATE_SYNC_RPC=https://rpc.jackalprotocol.com:443
LATEST_HEIGHT=$(curl -s $STATE_SYNC_RPC/block | jq -r .result.block.header.height)
SYNC_BLOCK_HEIGHT=$(($LATEST_HEIGHT - 3000))
SYNC_BLOCK_HASH=$(curl -s "$STATE_SYNC_RPC/block?height=$SYNC_BLOCK_HEIGHT" | jq -r .result.block_id.hash)

sed -i.bak -e "s|^enable *=.*|enable = true|" $HOME/.teritorid/config/config.toml
sed -i.bak -e "s|^rpc_servers *=.*|rpc_servers = \"$STATE_SYNC_RPC,$STATE_SYNC_RPC\"|" \
  $HOME/.teritorid/config/config.toml
sed -i.bak -e "s|^trust_height *=.*|trust_height = $SYNC_BLOCK_HEIGHT|" \
  $HOME/.teritorid/config/config.toml
sed -i.bak -e "s|^trust_hash *=.*|trust_hash = \"$SYNC_BLOCK_HASH\"|" \
  $HOME/.teritorid/config/config.toml

When you state sync, you can start with the latest version of canined.

Versions for Sync​

block heightcanined version
453811.1.2
01.1.0

Starting the daemon​

Start the daemon and sync to the current height.

sudo systemctl start jackal
sudo journalctl -u jackal -f

Watch the logs and ensure you are either state syncing correctly, or are syncing up to the current height.

- + \ No newline at end of file diff --git a/docs/nodes/nodes/testnet.html b/docs/nodes/nodes/testnet.html index 5aa62ab..e17a7fc 100644 --- a/docs/nodes/nodes/testnet.html +++ b/docs/nodes/nodes/testnet.html @@ -5,13 +5,13 @@ Joining Testnet | Jackal Chain Docs - +

Joining Testnet

After installing canined. You can join the testnet by following these steps:

canined init <alias> --chain-id=<chain-id>
note

chain-id for testnet is currently lupulella-2.

Then we want to replace our generated genesis file with the one used to start the network. We also need to set our peers and seeds.

For an updated list of peers & seeds, please check this page.

wget -O ~/.canine/config/genesis.json https://raw.githubusercontent.com/JackalLabs/jackal-chain-assets/main/testnet/genesis.json

export SEEDS="84f520678ef59ea02f942fa6323ec562ca5a3249@45.79.161.178:26656,cecc087977336da1e9ccd2c50097cd9e7d5e1874@141.95.33.39:26656"
sed -i.bak -e "s/^seeds *=.*/seeds = \"$SEEDS\"/" ~/.canine/config/config.toml

As a validator, you'll need to set a minimum gas price like so:

GAS="0.002ujkl"
sed -i.bak -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"$GAS\"/" $HOME/.canine/config/app.toml
- + \ No newline at end of file diff --git a/docs/nodes/providers/building.html b/docs/nodes/providers/building.html index 734e68a..da4fa34 100644 --- a/docs/nodes/providers/building.html +++ b/docs/nodes/providers/building.html @@ -5,13 +5,13 @@ Creating Provider | Jackal Chain Docs - +

Creating Provider

Disclaimer​

This guide assumes you either have access to a full node over a network connection or are using the same machine as the full node.

Networking​

To allow your provider to be used by the Jackal Protocol Dashboard, please ensure you have a reverse proxy system setup and have a registered domain name pointing to your provider. We recommend using Nginx.

If you have UPNP enabled on your router, your provider will be open to the internet by default at port 3333. You can find the address it can be connected to by running canined network ip.

Setting up ZFS Without Mirroring​

Setting up ZFS allows us to combine multiple drives together, in this case we are merging two drives. We don't recommend you only merge drives with striping and instead we recommend mirroring. However mirroring is a longer process and different for each configuration. In our case, this machine is only running with 24TB across 2 drives. We are less concerned about a drive failing as that would wipe half our storage anyways.

List all drives with :

sudo fdisk -l

You should end up seeing something like this

...

Disk /dev/sda: 12.75 TiB, 14000519643136 bytes, 27344764928 sectors
Disk model: ST14000NM001G-2K
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 4DE192A1-7AFF-F64D-93D5-CA48B806DAA0

Disk /dev/sdb: 12.75 TiB, 14000519643136 bytes, 27344764928 sectors
Disk model: ST14000NM001G-2K
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: D2827F71-7F0A-EE4A-BB12-1B2172641DBE

...

Note down the Disk paths that you wish to use for your storage provider, in this case it is /dev/sdb and /dev/sda.

We install ZFS and create a new pool as follows:

sudo apt install zfsutils-linux

sudo zpool create {pool-name} /dev/sda /dev/sdb ...

sudo zpool status

This folder will now have the drives mounted at /{pool-name}. For more in-depth guides to using zfs, check out this page.

- + \ No newline at end of file diff --git a/docs/nodes/providers/setting_up.html b/docs/nodes/providers/setting_up.html index 99c2676..c80eb76 100644 --- a/docs/nodes/providers/setting_up.html +++ b/docs/nodes/providers/setting_up.html @@ -5,12 +5,12 @@ Setting Up JProvd | Jackal Chain Docs - +
-

Setting Up JProvd

Pre-Requisites​

See Set-up.

Installing​

tip

Check latest version here.

note

'Setting Up' instructions must be followed fully to add necessary golang path info to the current users ~/.profile. If these steps are skipped, 'make install' will not build jprovd--the provider daemon. Please ensure to perform the below steps as the 'jackal' user you previously made.

Install make and confirm installation. 

sudo apt update

sudo apt install make

make --version

Build jprovd and source the .profile to ensure your shell can find jprovd. Confirm installation. 

git clone https://github.com/JackalLabs/canine-provider.git

cd canine-provider 

git pull

git checkout {version}

make install

source ~/.profile

jprovd --version

If you used ZFS to make a zpool. Give ownership of the zpool to the jackal user. 


sudo chown -R jackal:jackal /{pool-name}

Initializing​

tip

Your keybase identity can be left as "" if you don't want to link your provider to keybase.

  1. Export the path to your storage pool 
export PHOME={path-to-pool-from-before}
  1. Generate your provider's private key 
jprovd client gen-key --home=$PHOME
  1. Configure the chain-id 
jprovd client config chain-id {chain-id} --home=$PHOME
  1. Configure the rpc node your provider will use to connect to the chain 
jprovd client config node {your node} --home=$PHOME

Some users may find it easier to complete steps 3 and 4 manually. Instructions for Ubuntu are below:

In your terminal, while inside of the PHOME directory, type 'nautilus'. This will open the nautilus file explorer. +

Setting Up JProvd

Pre-Requisites​

See Set-up.

Installing​

tip

Check latest version here.

note

'Setting Up' instructions must be followed fully to add necessary golang path info to the current users ~/.profile. If these steps are skipped, 'make install' will not build jprovd--the provider daemon. Please ensure to perform the below steps as the 'jackal' user you previously made.

Install make and confirm installation. 

sudo apt update

sudo apt install make

make --version

Build jprovd and source the .profile to ensure your shell can find jprovd. Confirm installation. 

git clone https://github.com/JackalLabs/canine-provider.git

cd canine-provider 

git pull

git checkout {version}

make install

source ~/.profile

jprovd version

If you used ZFS to make a zpool. Give ownership of the zpool to the jackal user. 


sudo chown -R jackal:jackal /{pool-name}

Initializing​

tip

Your keybase identity can be left as "" if you don't want to link your provider to keybase.

  1. Export the path to your storage pool 
export PHOME={path-to-pool-from-before}
  1. Generate your provider's private key 
jprovd client gen-key --home=$PHOME
  1. Configure the chain-id 
jprovd client config chain-id {chain-id} --home=$PHOME
  1. Configure the rpc node your provider will use to connect to the chain 
jprovd client config node {your node} --home=$PHOME

Some users may find it easier to complete steps 3 and 4 manually. Instructions for Ubuntu are below:

In your terminal, while inside of the PHOME directory, type 'nautilus'. This will open the nautilus file explorer. At the top right corner, make sure 'Show Hidden Files' is checked. Navigate to your '.jackal-storage' folder to access the config folder. Open the client.toml file to manually type in the 'chain-id' and 'node'. @@ -19,7 +19,7 @@ If you are not running your own tendermint RPC node, Jackal Labs is currently ho Testnet tokens can be obtained at https://testnet-faucet.jackalprotocol.com/ Mainnet tokens can be purchased on https://frontier.osmosis.zone/

  1. Initialize the provider 
jprovd init {FQDN} {STORAGE_IN_BYTES} {KEYBASE_IDENTITY} --home=$PHOME

example:

jprovd init "https://storagep1.chainstrategies.cloud" "9000" "" --home=$PHOME

Please note that 'https://' is required to be included in the FQDN or init will throw an error. Link for TB to Bytes converter: https://www.convertunits.com/from/TB/to/byte

  1. Start the provider 
jprovd start --home=$PHOME
- + \ No newline at end of file diff --git a/docs/nodes/validators/joining.html b/docs/nodes/validators/joining.html index dabaa65..efbd08d 100644 --- a/docs/nodes/validators/joining.html +++ b/docs/nodes/validators/joining.html @@ -5,13 +5,13 @@ Creating Validator | Jackal Chain Docs - +

Creating Validator

tip

This guide assumes you are using the same machine as the full node.

Perform the following steps as your jackal user.

Creating A Wallet​

We need to create a wallet and set the keyring password.

canined keys add WALLET_NAME --keyring-backend os

This wallet is used to claim rewards, commission and to vote as your validator.

You will see a similar output once created.

- name: WALLET_NAME
  type: local
  address: jkl1hjhglrzggqtdhsh3ag8jp0cckmva5pe976jxel
  pubkey: '{"@type":"/cosmos.crypto.secp256k1.PubKey","key":"Rnrlv1TNrt1cz3+pSq2UDNiJQZINNlgtkNousVlkugZ7"}'
  mnemonic: ""


**Important** write this mnemonic phrase in a safe place.
It is the only way to recover your account if you ever forget your password.

some words forming mnemonic seed will be placed here you have to write them down and keep them safe

Besure to back up the seed phrase of your validator wallet. It's also recommened to keep an offline copy along with your key files. Remember, your key files cannot be restored and must be backed up. See the installation page for instructions.

You should also backup your keyring files.

Change WALLET_NAME to the name of your wallet.

mkdir ~/keyring_backup
cp ~/.canine/WALLET_NAME.info ~/keyring_backup
cp ~/.canine/keyhash ~/keyring_backup

Setting Up​

Configure Gas Prices​

As a validator, you'll need to set a minimum gas price like so:

GAS="0.02ujkl"
sed -i.bak -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"$GAS\"/" $HOME/.canine/config/app.toml

Create Your Validator​

Before continuing, please note that commission-max-change and commission-max-rate cannot be changed once you set them. Your commission-rate may be changed once per day.

There are a few things you will need to alter in this command. amount needs to be changed to what you are starting your self bond as. from needs to be the name of your wallet you created earlier. The moniker, details, identity, website, and security-contact should all be filled with the appropiate information.

canined tx staking create-validator \
    --amount 1000000ujkl \
    --commission-max-change-rate 0.10 \
    --commission-max-rate 0.2 \
    --commission-rate 0.1 \
    --from WALLET_NAME \
    --min-self-delegation 1 \
    --moniker "YOUR_MONIKER" \
    --details="YOUR DETAILS" \
    --identity "PGP IDENTITY" \
    --website="https://example.com" \
    --security-contact="your-email@email.com" \
    --pubkey $(canined tendermint show-validator) \
    --chain-id jackal-1 \
    --gas-prices 0.02ujkl
- + \ No newline at end of file diff --git a/docs/official-links/jackal-foundation.html b/docs/official-links/jackal-foundation.html index 88f1d81..6aee328 100644 --- a/docs/official-links/jackal-foundation.html +++ b/docs/official-links/jackal-foundation.html @@ -5,13 +5,13 @@ Jackal Foundation Links | Jackal Chain Docs - +

Jackal Foundation Links

Here are the official website links for Jackal Foundation. Please use and bookmark these links to reduce the likelihood of cyber phishing threats.

Jackal Foundation​

Jackal Foundation Twitter

Website: Coming Soon

- + \ No newline at end of file diff --git a/docs/official-links/jackal-labs.html b/docs/official-links/jackal-labs.html index 6aa112c..70040e1 100644 --- a/docs/official-links/jackal-labs.html +++ b/docs/official-links/jackal-labs.html @@ -5,13 +5,13 @@ Jackal Labs Links | Jackal Chain Docs - +

Jackal Labs Links

Here are the official website links for Jackal Labs. Please use and bookmark these links to reduce the likelihood of cyber phishing threats.

Jackal Labs​

Jackal Labs Twitter

Website

- + \ No newline at end of file diff --git a/docs/official-links/jackal-protocol.html b/docs/official-links/jackal-protocol.html index 6d17f69..7b4fe18 100644 --- a/docs/official-links/jackal-protocol.html +++ b/docs/official-links/jackal-protocol.html @@ -5,13 +5,13 @@ Jackal Protocol Links | Jackal Chain Docs - +
- + \ No newline at end of file diff --git a/docs/overview/jackal-tldr.html b/docs/overview/jackal-tldr.html index 9ef13b7..a41e0dc 100644 --- a/docs/overview/jackal-tldr.html +++ b/docs/overview/jackal-tldr.html @@ -5,13 +5,13 @@ Discover the Jackal Protocol | Jackal Chain Docs - +

Discover the Jackal Protocol

The Jackal Protocol provides a decentralized infrastructure for secure and scalable data storage, enabling individuals, developers, and enterprises to protect their data privacy and improve their cybersecurity posture. It offers a platform for building decentralized applications, managing access control and ownership, transferring encrypted data, and maintaining self-custodial control over data, all without relying on centralized storage providers or intermediaries.

Jackal Protocol stands apart, utilizing both validators and storage providers, enabling developers to create decentralized applications with seamless access to all Jackal Protocol Modules, including storage contracts and file structures. Customize data ownership, share data with other Jackal users or smart contracts, and transfer encrypted data of any size, all without centralized storage providers or middleware. Your data remains self-custodial, ensuring that no one—not even the Jackal team—can access or view it.

Comprising seven interoperable modules — jklMint, lp, rns, wasm, storage, filetree, and dsig — the Jackal Protocol allows for the development of secure, scalable, and truly decentralized applications .

The Jackal Protocol is open source and community-driven, fostering a transparent and trustless ecosystem. Dive into this wiki to access comprehensive information on the protocol, usage, infrastructure, and opportunities.

Maintained by the dedicated Jackal Labs and Jackal Foundation teams, the Jackal Wiki is constantly updated to ensure accuracy. Should you discover anything out-of-date, don't hesitate to reach out, as we strive to keep our documentation impeccable for the community.

- + \ No newline at end of file diff --git a/docs/overview/jkl.html b/docs/overview/jkl.html index 2486adb..e1c37e6 100644 --- a/docs/overview/jkl.html +++ b/docs/overview/jkl.html @@ -5,13 +5,13 @@ What Is The JKL Token? | Jackal Chain Docs - +

What Is The JKL Token?

The JKL Token is the driving force behind the revolutionary Jackal Protocol. This versatile native token seamlessly integrates with the ecosystem, unlocking endless possibilities for users, developers, and enterprises alike.

What Does The JKL Token Do?​

Fueling dApps​

JKL Token plays a pivotal role in applications built on the Jackal Protocol, such as Jackal Storage and the RNS Marketplace. By harnessing the power of JKL, these applications can unlock new potentials and further enhance their utility.

Network Security​

At its core, the Jackal Protocol is a Proof-of-Stake (PoS) Cosmos L1 blockchain, relying on JKL delegation to validators for network security. Stake your JKL tokens and contribute to securing the network while earning rewards.

Affordable Transactions​

With JKL, transaction fees on the Jackal Protocol are incredibly cost-effective, ensuring that users have an affordable and seamless experience.

Governance​

Staked JKL tokens grant you the power to participate in on-chain governance within the Jackal Protocol. Make your voice heard by voting on text, software, spending, and other critical governance proposals.

Collateral​

The JKL token serves as versatile collateral for validators, storage providers, and various smart contract use cases, unlocking new possibilities for users and developers.

Liquidity​

Put your JKL tokens to work by allocating them into a liquidity pool and earn JKL rewards in return. Contribute to the ecosystem while reaping the benefits of your investment.

Data Storage​

The JKL token serves as the primary medium of exchange for accessing data storage within the Jackal Protocol, ensuring a smooth and efficient market for users and storage providers alike.

- + \ No newline at end of file diff --git a/docs/overview/why-jackal.html b/docs/overview/why-jackal.html index 65a7a6a..9c1f66d 100644 --- a/docs/overview/why-jackal.html +++ b/docs/overview/why-jackal.html @@ -5,13 +5,13 @@ Why Choose Jackal Protocol | Jackal Chain Docs - +

Why Choose Jackal Protocol

The Jackal Protocol offers various advantages for individuals, small businesses, and large enterprises seeking secure, decentralized data storage and management solutions.

Individuals​

Individuals choose the Jackal Protocol for several reasons:

Enhanced data privacy and security​

The decentralized nature of the Jackal Protocol ensures that your data is stored across multiple nodes, reducing the risk of data breaches and unauthorized access.

Self-custodial storage​

The Jackal Protocol allows individuals to retain full control over their data, ensuring that no third party, not even the Jackal team, can access or view it without the user's consent.

On-chain permissions​

The transparent and secure permissions system enables users to manage access to their data, granting, revoking, or modifying permissions as needed.

Small Businesses​

Small businesses benefit from the Jackal Protocol in various ways:

Cost-effective storage​

With the Jackal Protocol's decentralized storage model, businesses can benefit from competitive pricing, making it more affordable than traditional centralized storage solutions.

Scalability​

The Jackal Protocol is built to scale with your business, ensuring that your data storage capacity can grow as your organization expands.

Simplified compliance​

Jackal Protocol's immutable records of data access and modification make it easier to meet industry-specific regulatory requirements and simplify auditing processes.

Large Enterprises​

Large enterprises can leverage the Jackal Protocol for:

Improved data governance​

The on-chain permissions system allows for transparent and secure management of data access, ensuring that sensitive information remains protected and accessible only to authorized personnel.

Enhanced security​

By leveraging the decentralized infrastructure, Jackal Protocol offers an additional layer of security for enterprise data storage, reducing the risk of cyber-attacks and data breaches.

Customizable solutions​

The Jackal Protocol enables developers to build and deploy a wide range of decentralized applications (dApps) that can interact with user data, opening up new possibilities for services and products that prioritize user privacy and control.

- + \ No newline at end of file diff --git a/docs/protocol/encryption.html b/docs/protocol/encryption.html index 744b5f3..479e131 100644 --- a/docs/protocol/encryption.html +++ b/docs/protocol/encryption.html @@ -5,13 +5,13 @@ Encryption in Jackal Protocol | Jackal Chain Docs - +

Encryption in Jackal Protocol

The Jackal Protocol utilizes encryption techniques to ensure the privacy and security of user data. The two primary encryption models within the protocol are file encryption and file-entry encryption. File encryption secures the files themselves, while file-entry encryption focuses on securing the file entries on the blockchain.

File Encryption​

File encryption is essential for protecting the data stored on storage providers within the Jackal Protocol. Before transferring files to storage providers, the user's client encrypts the files using a randomly generated symmetric key. The Advanced Encryption Standard (AES-256) is used for this encryption process, resulting in a securely encrypted file.

File Encryption Process

The symmetric key's secure storage is equally crucial, as exposing it would compromise the file's encryption. The Jackal Chain's File Tree Module serves as a safe and immutable location for storing the encrypted symmetric key alongside the file's location.

Integrated Encryption Scheme​

The protocol uses an Integrated Encryption Scheme based on AES and the Elliptic Curve cryptography, which generates Bech32 addresses for secure key storage.

Integrated Encryption Scheme

To securely store the symmetric key, the protocol encrypts it with the user's public key. This process ensures that only the user with the corresponding private key can decrypt the symmetric key.

Symmetric Key Decryption

When decrypting a file, the user's private key is used to decrypt the symmetric key. Once the symmetric key is retrieved, it can be used to decrypt the file stored on the storage provider, resulting in the original uploaded file.

File Sharing and Access​

To share files with other users, the protocol first decrypts the symmetric key from the chain, then retrieves the external user's public key from the chain, and encrypts the symmetric key with the external user's public key. By appending the newly encrypted symmetric key to the file entry, the external user gains access to the file.

By leveraging encryption techniques for both files and file entries, the Jackal Protocol ensures the privacy, security, and integrity of user data throughout the storage and sharing processes.

- + \ No newline at end of file diff --git a/docs/protocol/modules/dsig.html b/docs/protocol/modules/dsig.html index c307c32..8eb1b84 100644 --- a/docs/protocol/modules/dsig.html +++ b/docs/protocol/modules/dsig.html @@ -5,13 +5,13 @@ dsig Module | Jackal Chain Docs - +
- + \ No newline at end of file diff --git a/docs/protocol/modules/filetree.html b/docs/protocol/modules/filetree.html index 1b2e0f9..069733a 100644 --- a/docs/protocol/modules/filetree.html +++ b/docs/protocol/modules/filetree.html @@ -5,13 +5,13 @@ Filetree Module | Jackal Chain Docs - +

Filetree Module

Overview​

The Jackal Filetree module is responsible for organizing and managing user files in a secure and user-friendly way. When a user uploads a file using the Storage module, the file is only accessible from the File ID (FID), which can be challenging to remember for every file uploaded to Jackal. Additionally, every single upload would be required to be public, or the user would need to keep track of every symmetric key used to encrypt the files and manually map them to the FIDs. To address this issue, the File Tree module implements a tree structure to store each file as an entry in the tree. Organizing this structure is also trivial as we can assign children to pseudo files that we call folders. Finally, to keep track of encryption keys, the protocol maps every file to its respective key, emphasizing the security and privacy posture that the File Tree module enables.

Protocol Overview

Folder Abstraction​

These, of course, are all abstractions of what's actually under the hood. The File Tree module doesn't actually handle any of the folder logic; the system believes it is storing files that act as metadata stores, which then update to reflect changes in folders. This gives the user experience the feeling that folders and files are separate entities in the tree, but in reality, they are identical.

File Entry Structure​

Storing file entries on-chain is a challenge since the chain itself is public. This requires the use of client-side encryption before uploading data to the chain itself. The main component of a file is location (Address), allowing users to query the rest of the data from the file. You can think of the location as a key in a traditional key-value store or a path in bucket-based storage. The address is hashed using SHA256 to ensure it is impossible to retrieve the plain-text representation of the file name while still being able to query the file using its given name.

Protocol Overview

The second most important data point in a file is the content of the file. This field is extremely versatile as it can store any string. Traditionally this is used to store a JSON list of FIDs to point to a file on the Storage Module; however, the protocol can also theoretically use it to store short bits of text like encrypted passwords for a private password manager. The owner tag is a hashed version of the owner, hiding what address owns each file. This field can be changed to reflect the transferral of ownership. When making changes to the file such as deletion, movement, or adding/removing viewers/editors, the owner field is consulted to determine permissions. The same applies to edit access; editors can update the contents but nothing else.

Encrypted Viewing Access​

For users to view files, they need access to the symmetric keys used to encrypt the files. To do this, the protocol has a map of hashed addresses with each user's respective version of the symmetric key encrypted with that address's corresponding public key. The protocol can then store that map in the file entry to act as an encryption key discovery layer. The addresses in this viewing list are only able to access files and decrypt the data in their client; they have no privileges over the modification of the file entry in any way. This approach ensures that the File Tree module maintains a strong security and privacy posture for user data.

- + \ No newline at end of file diff --git a/docs/protocol/modules/jklmint.html b/docs/protocol/modules/jklmint.html index 59c944e..90a1998 100644 --- a/docs/protocol/modules/jklmint.html +++ b/docs/protocol/modules/jklmint.html @@ -5,13 +5,13 @@ JKLmint Module | Jackal Chain Docs - +

JKLmint Module

The jklmint module is responsible for the management of the native JKL token within the Jackal Protocol. This module handles the issuance, distribution, and inflation of JKL tokens, ensuring a stable and secure token economy.

Overview​

The jklmint module manages the following aspects of the JKL token:

  1. Token Issuance: Determines the initial token supply and distribution.
  2. Inflation: Manages the annual inflation rate, maintaining a consistent token supply growth.
  3. Rewards Distribution: Handles the allocation of newly minted tokens as rewards for validators and delegators.

Parameters​

The jklmint module uses the following parameters to manage the JKL token economy:

  • inflation_rate: The annual percentage rate at which the token supply will grow.
  • inflation_min: The minimum annual inflation rate allowed.
  • inflation_max: The maximum annual inflation rate allowed.
  • goal_bonded: The desired percentage of the total token supply that should be staked by validators and delegators.
  • blocks_per_year: The estimated number of blocks produced in a year.
- + \ No newline at end of file diff --git a/docs/protocol/modules/lp.html b/docs/protocol/modules/lp.html index c4bd72b..4783e63 100644 --- a/docs/protocol/modules/lp.html +++ b/docs/protocol/modules/lp.html @@ -5,13 +5,13 @@ LP Module (Coming Soon) | Jackal Chain Docs - +

LP Module (Coming Soon)

The lp (Liquidity Provision) module is a vital part of the Jackal Protocol, enabling the creation and management of liquidity pools for trading and swapping tokens. This module provides a decentralized solution for users to contribute liquidity to the ecosystem and earn rewards in return.

Overview​

The lp module manages the following aspects of liquidity pools:

  1. Liquidity Pool Creation: Allows the creation of new liquidity pools for token pairs.
  2. Liquidity Provision: Facilitates users to add or remove liquidity from existing pools.
  3. Token Swaps: Enables decentralized trading and swapping of tokens within the liquidity pools.
  4. Rewards: Distributes rewards to liquidity providers proportionate to their contribution.

For a more detailed guide on the 'lp' module, please refer to the module documentation on GitHub.

- + \ No newline at end of file diff --git a/docs/protocol/modules/module-overview.html b/docs/protocol/modules/module-overview.html index d00c0a9..55c16eb 100644 --- a/docs/protocol/modules/module-overview.html +++ b/docs/protocol/modules/module-overview.html @@ -5,13 +5,13 @@ Module Overview | Jackal Chain Docs - +
- + \ No newline at end of file diff --git a/docs/protocol/modules/rns.html b/docs/protocol/modules/rns.html index 3576b57..5be9b8e 100644 --- a/docs/protocol/modules/rns.html +++ b/docs/protocol/modules/rns.html @@ -5,13 +5,13 @@ Name Service Module | Jackal Chain Docs - +

Name Service Module

The rns (Reverse Name Service) module is an essential component of the Jackal Protocol, providing a user-friendly naming system for blockchain addresses. The RNS module simplifies the process of interacting with complex addresses by mapping them to human-readable names. This module allows users to transfer tokens and permissions to files/folders stored on the Jackal Protocol using human readable names.

Overview​

The rns module manages the following aspects of the Reverse Name Service:

  1. Name Registration: Allows users to register unique names for their blockchain addresses.
  2. Name Management: Facilitates updating, renewing, and transferring RNS names.
  3. Name Resolution: Provides a mechanism for resolving RNS names to their corresponding addresses.
  4. Name Sales: Enables users to buy and sell RNS names through the RNS Marketplace.
  5. Name Transfers: Enables users to transfer RNS names.

For a more detailed guide on integrating the rns module into your application, please refer to the module documentation on GitHub.

- + \ No newline at end of file diff --git a/docs/protocol/modules/storage.html b/docs/protocol/modules/storage.html index f567746..8bdd57d 100644 --- a/docs/protocol/modules/storage.html +++ b/docs/protocol/modules/storage.html @@ -5,13 +5,13 @@ Storage Module | Jackal Chain Docs - +

Storage Module

The Jackal Protocol incorporates two crucial algorithms for decentralized storage: Jackal Proof-of-Persistence (JPOP) and Internal Detection Of Loss (IDOL) protocols. This document provides an overview of these algorithms, their functionalities, and their interaction with users and Storage Providers.

Jackal Proof-of-Persistence (JPOP)​

JPOP is a Proof-of-Storage algorithm that governs the relationship between the storage provider and the user. It operates through a series of contracts containing the Merkle Tree root hash of the file and information required to prove ownership. Storage Providers are responsible for posting Merkle Proofs within a challenge window determined by the blockchain.

The challenge windows require miners to post the raw data chunk and the required Merkle Hashes to prove the data belongs to the Merkle Root stored on the contract. The challenge indexes are chosen at random by the blockchain using a block-hash-based random number generator paired with a random data oracle.

Internal Detection Of Loss (IDOL) Protocol​

The IDOL protocol ensures that data remains available and accessible. When a Storage Provider successfully posts a Merkle Proof within the challenge window, and Validators verify the data, the Storage Provider is rewarded. The rewards are proportional to the file size associated with the contract relative to other active contracts on the network.

If a Storage Provider fails to provide a valid proof within the allotted timeframe, the contract is marked with a missed proof. After a certain number of missed proofs, the contract is burned, and the user is alerted the next time they query the contract. Storage Providers receive penalties for every contract burned due to missed proofs, which remain on their record for an adjustable period.

The IDOL protocol comes into play when contracts with missed proofs are moved to a new list where they can be claimed by other providers. The new provider downloads the file from one of the two online providers storing the same file, resumes the contract's proof action, and restores redundancy to 3x.

Interaction Outline​

  1. A user sends a file to an available Storage Provider. A list of Storage Providers can be found on the blockchain, and miners can deny any incoming request if they do not want to store new files.
  2. After receiving the entire file, the Storage Provider keeps the file in memory and posts a contract to the blockchain.
  3. If the contract is not signed by the sender within a certain number of blocks (configurable by the Storage Provider), the file is removed from memory, and the contract is burned.
  4. If the contract is signed by the user within the given number of blocks, the file is committed to the Storage Provider's hard storage, and the challenge windows start being created for the now active contract.

Client Query Commands​

The client query commands enable users to interact with and query the storage state. Examples of these commands include:

  • list-active-deals
  • show-active-deals
  • list-miners
  • show-miners
  • list-contracts
  • show-contracts
  • find-file
  • freespace
  • get-client-free-space
  • list-pay-blocks
  • show-pay-blocks
  • list-strays
  • show-strays
  • params
  • storage-payment-info

Transactions​

The transaction commands allow users to interact with the storage module. Examples of these commands include:

  • init-miner
  • set-miner-ip
  • set-miner-totalspace
  • sign-contract
  • post-contract
  • postproof
  • buy-storage
  • cancel-contract
  • upgrade-storage

By implementing the JPOP and IDOL protocols, the Jackal Protocol ensures secure, efficient, and reliable decentralized storage management. These protocols, along with the provided client query commands and transactions, enable users and Storage Providers to interact with the Jackal storage ecosystem seamlessly.

Please refer to the respective command documentation for detailed usage and parameters. The Jackal Protocol continues to evolve, and as new features are added, updates to this documentation will be provided accordingly.

- + \ No newline at end of file diff --git a/docs/protocol/modules/wasm.html b/docs/protocol/modules/wasm.html index 92428af..2ee9085 100644 --- a/docs/protocol/modules/wasm.html +++ b/docs/protocol/modules/wasm.html @@ -5,13 +5,13 @@ WASM Module | Jackal Chain Docs - +

WASM Module

The wasm module in the Jackal Protocol incorporates the CosmWasm smart contracting platform, which is designed specifically for the Cosmos Ecosystem. This module provides a secure and efficient environment for executing WebAssembly (WASM) smart contracts on the Jackal Protocol.

Overview​

The wasm module manages the following aspects of the CosmWasm platform:

  1. Smart Contract Deployment: Allows developers to deploy smart contracts written in Rust or other languages that compile to WASM.
  2. Smart Contract Execution: Facilitates the execution of smart contract functions on the blockchain.
  3. Smart Contract Interaction: Enables users and other smart contracts to interact with deployed smart contracts.

For a more detailed guide on integrating the wasm module into your application, please refer to the Jackal Protocol GitHub.

- + \ No newline at end of file diff --git a/docs/protocol/p-o-p.html b/docs/protocol/p-o-p.html index e29e939..739bc8d 100644 --- a/docs/protocol/p-o-p.html +++ b/docs/protocol/p-o-p.html @@ -5,13 +5,13 @@ Jackal Proof-of-Persistence Documentation | Jackal Chain Docs - +

Jackal Proof-of-Persistence Documentation

Overview​

Jackal Storage is powered by a Proof-of-Storage algorithm called Proof-of-Persistence (JPOP). JPOP is designed to ensure the secure and persistent storage of user data 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. In this documentation, we'll explain the core components and processes involved in the Jackal Proof-of-Persistence.

Building the Trees​

Merkle Trees are a core component of the JPOP mechanism, thus, it is important to outline how these trees are used to create efficient and trustworthy proofs. When saving a file for the first time, providers split each file into many 1kb chunks. Providers must also hash the entire file to create a folder to house every chunk, this is displayed by the following diagram.

File Tree

These chunks are used as leaves on the Merkle Tree defining each storage contract. Immediately after saving a file to disk, the storage provider builds a tree using each chunk. To create this tree, each chunk is hashed into a respective Hashed Chunk. These chunks are then recursively paired together and hashed until a single root node is created. This is called the Merkle Root, the only piece of data relative to a file that is saved directly on the blockchain itself.

Merkle Roots

In the diagram above, displays how each file is hashed together to create a single root node.

Proving Data Availability​

These nodes are essential as they only require the nodes below them to prove they are part of the tree. This means that we can create a proof claiming a single chunk belongs to the file using the Merkle Root saved on the chain. In the following diagram, we can see that only the blue nodes are required to build a successful proof. The green nodes represent information that we can generate given the blue nodes. Finally, we can compare the root generated from the proof to the root saved on the chain and determine if the chunk does belong to the contract we are proving. This results in small message sizes due to not needing to send the entire file every proof.

Merkle Roots Graphed

- + \ No newline at end of file diff --git a/docs/protocol/storageproviders/casual-build.html b/docs/protocol/storageproviders/casual-build.html index 2a8a901..c3bbb70 100644 --- a/docs/protocol/storageproviders/casual-build.html +++ b/docs/protocol/storageproviders/casual-build.html @@ -5,13 +5,13 @@ Casual Storage Build | Jackal Chain Docs - +

Casual Storage Build

You may be successful contributing to the network with an old computer you may have. If you are looking to purpose build a machine- here are the recommendations for casual a storage provider.

ComponentRecommendationUnits
CPUAMD Ryzen 5 5600G 3.9 GHz 6-Core Processor.1
MotherboardMSI B450 Tomahawk Max ATX AM4 Motherboard.1
MemoryG.Skill Ripjaws V 32 GB (2 x 16 GB) DDR4-3200 CL 16 Memory1
StorageSeagate EXOS Enterprise 14 TB 3.5 7200 RPM Internal Hard Drive2
StorageKingston NV1 1 TB M.2-2280 NVME Solid State Drive1
CaseCooler Master HAF XB EVO ATX Desktop Case1
Power SupplyEVGA SuperNOVA GA 650 W 80+ Gold Certified Fully Modular ATX Power Supply1
Total Cost Estimate$1061.92 USD
- + \ No newline at end of file diff --git a/docs/protocol/storageproviders/diy-serious copy.html b/docs/protocol/storageproviders/diy-serious copy.html index 570da77..ca0c2c4 100644 --- a/docs/protocol/storageproviders/diy-serious copy.html +++ b/docs/protocol/storageproviders/diy-serious copy.html @@ -5,13 +5,13 @@ DIY Serious Build | Jackal Chain Docs - +

DIY Serious Build

For DIY individuals looking to power web3 infrastructure and increase your ROI- here is the recommended system for serious individual storage providers.

ComponentRecommendationUnits
CPUAMD Ryzen 7 5700G 3.8 GHz 8-Core Processor1
MotherboardMSI B450 TOMAHAWK MAX II ATX AM4 Motherboard1
MemoryG.Skill Ripjaws V 64 GB (2 x 32 GB) DDR4-2666 CL18 Memory1
StorageKingston A400 960 GB 2.5" Solid State Drive1
StorageSeagate EXOS Enterprise 14 TB 3.5" 7200RPM Internal Hard Drive5
CaseCooler Master N400 ATX Mid Tower Case1
Power SupplyCorsair HX750 Platinum 750 W 80+ Platinum Certified Fully Modular ATX Power Supply1
Case FanNoctua S12B redux-700 33.49 CFM 120 mm Fan2
Total Cost Estimate$1814.08 USD
- + \ No newline at end of file diff --git a/docs/protocol/storageproviders/enterprise.html b/docs/protocol/storageproviders/enterprise.html index e5a6b61..3343f36 100644 --- a/docs/protocol/storageproviders/enterprise.html +++ b/docs/protocol/storageproviders/enterprise.html @@ -5,13 +5,13 @@ Enterprise Build | Jackal Chain Docs - +

Enterprise Build

For teams looking to build a large storage system of ~2.1 Petabytes of storage, the estimated base price of the box with drives is ~$70,000 USD. This does not account for variable expenses including the regional costs of:

  • Power
  • Internet
  • HVAC
  • Professionals

Those looking to build an enterprise storage provider, reach out to the team for recommendations and support.

- + \ No newline at end of file diff --git a/docs/protocol/storageproviders/overview.html b/docs/protocol/storageproviders/overview.html index 0f1b9aa..b8a36ef 100644 --- a/docs/protocol/storageproviders/overview.html +++ b/docs/protocol/storageproviders/overview.html @@ -5,13 +5,13 @@ Overview | Jackal Chain Docs - +

Overview

Want to power the storage infrastructure for web3?​

A Jackal Storage Provider is a dedicated web server optimized for data storage that accepts incoming files from users and creates contracts for the users to approve. These contracts last until the user either cancels them or the provider itself goes offline.

- + \ No newline at end of file diff --git a/docs/protocol/tokens.html b/docs/protocol/tokens.html index f7c89a1..0e918d2 100644 --- a/docs/protocol/tokens.html +++ b/docs/protocol/tokens.html @@ -5,13 +5,13 @@ JKL Token | Jackal Chain Docs - +

JKL Token

Overview​

The JKL token is an inflationary token that powers the Jackal Protocol. It has numerous use cases within the ecosystem, ensuring its utility and importance. In this documentation, we will outline the main use cases of the JKL token and explain its role in the Jackal Protocol ecosystem.

Use Cases​

dApps​

Applications built leveraging the Jackal Protocol, such as Jackal Storage and the RNS Marketplace, may choose to include the JKL token to expand its utility.

Securing the Network​

As the Jackal Protocol is a Proof-of-Stake (PoS) Cosmos L1 blockchain, JKL can be delegated to validators to secure the network and earn JKL rewards. Otherwise known as staking or bonded tokens.

Transaction Fees​

Transactions on the Jackal Protocol must be paid for using JKL. As the protocol is PoS, the cost of transactions is inexpensive.

Governance​

Staked tokens grant on-chain governance participation within the Jackal Protocol to vote on text, software, spend, and other governance proposals.

Collateral​

The JKL token can act as collateral for validators, storage providers, and other smart contract use cases.

Liquidity Provision​

JKL can be allocated into a liquidity pool to earn rewards.

Unique JKL Token Utility for Users and Storage Providers​

Users​

Users seeking storage solutions can leverage JKL tokens to pay for the storage services provided by storage providers within the Jackal Protocol. By utilizing JKL tokens as a medium of exchange, users can access a decentralized, secure, and censorship-resistant storage infrastructure.

Storage Providers​

Storage providers are incentivized to offer storage space and maintain a high level of service by earning JKL tokens. By receiving JKL tokens as payment for their services, storage providers can cover the costs of infrastructure, hardware, and bandwidth while potentially profiting from their participation in the ecosystem.

- + \ No newline at end of file diff --git a/docs/protocol/validators.html b/docs/protocol/validators.html index b7740a5..1671afa 100644 --- a/docs/protocol/validators.html +++ b/docs/protocol/validators.html @@ -5,13 +5,13 @@ Validators | Jackal Chain Docs - +

Validators

The Jackal Validators are secure web servers, dedicated machines that participate in the consensus protocol by broadcasting cryptographic signatures, or votes, to agree upon the next block. Voting power is determined by the amount of staking tokens delegated by non-validators and bonded as collateral to earn a reward. These non-validators, or delegators, incur the risk of getting punished (slashed) if the delegate validator gets hacked or violates the protocol.

To set up a validator and become a contributing part of the network, read the installation instructions here

- + \ No newline at end of file diff --git a/docs/using-jackal/dashboard.html b/docs/using-jackal/dashboard.html index 3ff716c..86b5a27 100644 --- a/docs/using-jackal/dashboard.html +++ b/docs/using-jackal/dashboard.html @@ -5,13 +5,13 @@ Jackal Dashboard Guide | Jackal Chain Docs - +

Jackal Dashboard Guide

The Jackal Dashboard is your one-stop destination for interacting with the Jackal Protocol and Cosmos ecosystem. This guide will walk you through the various features and capabilities available on the Jackal Dashboard.

1. File Management​

The Jackal Dashboard allows users to upload, download, delete, and share files securely and privately.

Uploading Files​

  1. Navigate to the "Storage" tab on navigation bar of the Jackal Dashboard.
  2. Click "Browse Files" and select the file(s) you want to upload. Users can also drag and drop files into the dashboard directly.
  3. Click "Encrypt & Upload" on the right side of the screen.
  4. Sign the transaction prompt for your Keplr wallet.

Downloading Files​

  1. In the "Storage" tab, locate the file you want to download.
  2. Click the "..." button relative to the file you wish to download.
  3. Click "Download".
  4. The file will be downloaded to your local device.

Sharing Files (Coming Soon)​

2. Buy Tokens​

  1. Navigate to the "Buy Tokens" tab on the Jackal Dashboard.
  2. You will be re-directed to the Osmosis Decentralized Exchange in another tab.

3. Name Service​

The Jackal Dashboard enables users to register and manage RNS names.

Registering RNS Names​

  1. Navigate to the "Name Service" tab on the Jackal Dashboard.
  2. Click "Register"
  3. Enter your desired name and how many years you wish to keep it for.
  4. Confirm the transaction in your connected wallet.

Managing RNS Names​

  1. In the "Name Service" tab, view your owned RNS addresses.
  2. Click on a "..." next to the name you wish to manage.

4. Name Service Marketplace​

The RNS Marketplace allows users to buy and sell RNS names.

  1. Navigate to the "RNS Marketplace" tab on the Jackal Dashboard.
  2. Browse available RNS names or search for a specific name.
  3. Click "Buy" to purchase an RNS name or "Sell" to list one of your RNS names for sale.

5. Hosting Static Websites (Coming Soon)​

6. Governance Participation​

The Jackal Dashboard provides an interface to participate in on-chain governance.

  1. Navigate to the "Governance" tab on the Jackal Dashboard.
  2. View active proposals and click on a proposal to review its details.
  3. Cast your vote by clicking "Vote" and selecting your preferred option and signing the transaction.

7. Delegating Tokens to Validators​

The Jackal Dashboard enables users to delegate tokens to validators, securing the network and earning rewards.

  1. Navigate to the "Validators" tab on the Jackal Dashboard.
  2. Browse the list of active validators and select one.
  3. Click "Delegate" and enter the amount of tokens you want to delegate.
  4. Confirm the transaction in your connected wallet.

Stay tuned for more exciting features and improvements coming to the Jackal Dashboard!

- + \ No newline at end of file diff --git a/docs/using-jackal/delegate.html b/docs/using-jackal/delegate.html index e30212b..c625a4b 100644 --- a/docs/using-jackal/delegate.html +++ b/docs/using-jackal/delegate.html @@ -5,13 +5,13 @@ How to Delegate JKL Tokens to a Validator | Jackal Chain Docs - +

How to Delegate JKL Tokens to a Validator

This guide will help you delegate your JKL tokens to a validator on the Jackal Protocol, which helps secure the network and earns you staking rewards.

Step 1: Set up a Keplr Wallet​

  1. Install the Keplr Wallet browser extension.
  2. Create a new wallet or import an existing one.
  3. Make sure you have some JKL tokens in your wallet.

Step 2: Choose a Dashboard​

  1. Jackal Dashboard
  2. Ping Pub

Step 3: Choose a Validator​

  1. Review the list of active validators and their details, such as commission, uptime, and self-delegation.
  2. Choose a validator that aligns with your preferences and click on "Delegate".

Step 4: Delegate JKL Tokens​

  1. Enter the amount of JKL tokens you want to delegate.
  2. Click "Delegate" and confirm the transaction in your Keplr Wallet.
  3. Once the transaction is complete, you will see your delegated JKL tokens and earned rewards in the "Staking" or "Delegations" tab on the dashboards.

Step 5: Monitor and Manage Your Delegation​

  1. You can redelegate your JKL tokens to another validator or undelegate (unbond) them if you want to withdraw your tokens. Note that there is a 14-day unbonding period during which your tokens are locked and not earning rewards.

Now you have successfully delegated your JKL tokens to a validator on the Jackal Protocol, contributing to the network's security and earning staking rewards.

Reminder​

If you possess JKL tokens, you can temporarily lock them away to secure the protocol, this is called staking or delegating. In exchange for securing the network with your tokens, you receive rewards and the ability to vote on the Protocol’s future. These rewards come from newly generated JKL tokens and transaction fees.

It should be noted that staking or delegating is not risk free, this is why it is important to learn about the risks and participate in sustainable staking practices.

To decrease risk, it’s recommended that you do research on validators and select one you trust as well as delegate to multiple validators.

Slashing by 0.01%​

Occurs if the validator you delegate to is offline for too long.

Slashing by 5%​

Occurs if the validator signs two different blocks at the same block height. This is often caused by bad validator operation practices or malicious intent by the validator.

- + \ No newline at end of file diff --git a/docs/using-jackal/fund.html b/docs/using-jackal/fund.html index 1a7cbf0..8452d13 100644 --- a/docs/using-jackal/fund.html +++ b/docs/using-jackal/fund.html @@ -5,13 +5,13 @@ Accessing JKL Tokens on Osmosis and Withdrawing to Jackal Protocol | Jackal Chain Docs - +

Accessing JKL Tokens on Osmosis and Withdrawing to Jackal Protocol

This guide will help you access JKL tokens on the Osmosis Decentralized Exchange (DEX) and withdraw them to the Jackal Protocol using Inter-Blockchain Communication (IBC).

Step 1: Set up a Keplr Wallet​

  1. Install the Keplr Wallet browser extension.
  2. Create a new wallet or import an existing one.
  3. Make sure you have some OSMO tokens in your wallet for transaction fees.

Step 2: Access the Osmosis DEX​

  1. Visit the Osmosis DEX website.
  2. Connect your Keplr Wallet by clicking "Connect Wallet" in the top right corner.

Step 3: Swap tokens for JKL on Osmosis​

  1. Click "Swap" in the Osmosis navigation bar.
  2. Select the token you want to swap for JKL, such as OSMO or ATOM.
  3. Enter the amount you want to swap and confirm the transaction in your Keplr Wallet.
  4. Once the transaction is complete, you will see the JKL tokens in your wallet.

Step 4: Withdraw JKL tokens to Jackal Protocol via IBC​

  1. Visit the Assets Page.
  2. Find the JKL asset and click "withdraw".
  3. Once you sign the transaction with your Keplr wallet, an IBC transfer has begun and your JKL tokens will be available on the Jackal Protocol shortly.

Now you have successfully accessed JKL tokens on the Osmosis DEX and withdrawn them to the Jackal Protocol using IBC.

- + \ No newline at end of file diff --git a/docs/using-jackal/wallet/keplr.html b/docs/using-jackal/wallet/keplr.html index 78abfb2..e0a23e6 100644 --- a/docs/using-jackal/wallet/keplr.html +++ b/docs/using-jackal/wallet/keplr.html @@ -5,14 +5,14 @@ Keplr Wallet | Jackal Chain Docs - +

Keplr Wallet

The Keplr browser extension is a wallet for accessing some Jackal applications in the Cosmos ecosystem. Keplr can be used to exchange/manage JKL and other Cosmos-based tokens, participate in governance from the Jackal Dashboard, and use Jackal Storage.

Set up Keplr​

More information about setting up a Keplr wallet can be found in the official Keplr Documentation.

Open the Keplr extension on your browser. If you are setting up Keplr for the first time, you can either create a new account or import an existing account.

Create a new account​

There are two ways to create a new Keplr account:

Most Secure

  • Mnemonic/seed phrase.

Easiest

  • One-click login.

Create an account with a Seed Phrase​

  1. In the initial pop-up window, choose Create New Account

    • If you have used Keplr before, click on the silhouette in the upper-right corner, then the blue box labeled Add Account, and select Create New Account.

  2. Choose to have a seed/mnemonic phrase of 24 words, and save the phrase.

  3. Enter a name for your account. This can be changed later.

  4. Once you have transcribed your 24 word seed/mnemonic phrase, click on Next

  5. To confirm the creation of the new account, click on the words on the right order in which they appear in your seed/mnemonic phrase, and press Register.

  6. If you have not used Keplr before, set a password for the Keplr extension, and click Confirm.

Import an existing account​

There are several ways to import an existing account:

  • via a mnemonic/seed phrase/private key.
  • via ledger.

Import with a Seed Phrase

  1. In the initial pop-up window, choose Import Existing Account If you have used Keplr before, click on the silhouette in the upper-right corner, then the blue box labeled Add Account, and select Import Existing Account.

  2. Enter your mnemonic/seed phrase/private key in the appropriate slot, seperating the words with spaces and make sure to check they are spelled correctly.

  3. Make sure you have imported the account with the correct derivation path, viewable by clicking on Advanced.

    • Normally, the derivation path should be m/44'/…’/0/0/0, but if you see that importing the account via mnemonic on Keplr, the Cosmos Mainnet address displayed is different than yours, it is possible the derivation path ends with 1 (or another number) instead of 0.

    • If this is the case, you just have to start the process over, and replace the last 0 with 1

    • Learn more in the Keplr FAQ

  4. If you have not used Keplr before, set a password for the Keplr extension, and click Confirm.

Import with Ledger

  1. In the initial pop-up window, choose Import Ledger.

    • If you have used Keplr before, click on the silhouette in the upper-right corner, then the blue box labeled Add Account, and select Import Ledger.

  2. To complete the connection with your Ledger Nano Hard Wallet, follow the steps described in the pop-up that appears. A detailed tutorial can be found here.

  3. If you have not used Keplr before, set a password for the Keplr extension, and click Confirm.

Connecting Keplr to the Jackal Protocol​

Once you are signed in to the Keplr extension, you can connect the wallet with the Jackal Protocol. Once on the Jackal Dashboard you will be prompted to connect your Keplr wallet.

- + \ No newline at end of file diff --git a/index.html b/index.html index a5cd22a..6f5af50 100644 --- a/index.html +++ b/index.html @@ -5,13 +5,13 @@ Jackal Chain Docs | Jackal Chain Docs - +
- + \ No newline at end of file diff --git a/markdown-page.html b/markdown-page.html index 2ed2c16..80a504c 100644 --- a/markdown-page.html +++ b/markdown-page.html @@ -5,13 +5,13 @@ Markdown page example | Jackal Chain Docs - +

Markdown page example

You don't need React to write simple standalone pages.

- + \ No newline at end of file