From 956bf98c27606d46e98c89115da9428389c41db0 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Mon, 9 Sep 2024 11:06:35 +0200 Subject: [PATCH 1/4] fix typo --- .../governance/proposals/blockchain-node-upgrade.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hypersign-identity-network/governance/proposals/blockchain-node-upgrade.md b/hypersign-identity-network/governance/proposals/blockchain-node-upgrade.md index 7fc2f5a..1e0db80 100644 --- a/hypersign-identity-network/governance/proposals/blockchain-node-upgrade.md +++ b/hypersign-identity-network/governance/proposals/blockchain-node-upgrade.md @@ -44,4 +44,4 @@ mkdir -p /cosmovisor/upgrades//bin cp /cosmovisor/upgrades//bin ``` -* At the the proposed height, the upgrade would take place automatically. +* At the proposed height, the upgrade would take place automatically. From 56aa2c4a9962abe83681e79a546ecb5c94525eb9 Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Mon, 9 Sep 2024 11:08:22 +0200 Subject: [PATCH 2/4] fix typos --- .../setting-up-local-hid-node-tutorial/transfer-funds.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hypersign-identity-network/developers/setting-up-local-hid-node-tutorial/transfer-funds.md b/hypersign-identity-network/developers/setting-up-local-hid-node-tutorial/transfer-funds.md index 1369876..8023c56 100644 --- a/hypersign-identity-network/developers/setting-up-local-hid-node-tutorial/transfer-funds.md +++ b/hypersign-identity-network/developers/setting-up-local-hid-node-tutorial/transfer-funds.md @@ -26,11 +26,11 @@ List all accounts. mnemonic: "" ``` -`node1` is the first account which has balance and be used as a sender of the the transaction. +`node1` is the first account which has balance and be used as a sender of the transaction. ### Send amount from one account to other -Create a new account called `my-account1`and lets send balance from account `node1` to `my-account1` and then finnally check balances. +Create a new account called `my-account1`and lets send balance from account `node1` to `my-account1` and then finally check balances. ```bash hid-noded tx bank send --keyring-backend test --chain-id hidnode From 4795bac2fefd49a8b1ca29eb545c03b777a0fa7c Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Mon, 9 Sep 2024 11:10:38 +0200 Subject: [PATCH 3/4] fix typos --- .../developers/hid-node.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/hypersign-identity-network/developers/hid-node.md b/hypersign-identity-network/developers/hid-node.md index 5a45b00..b128b5c 100644 --- a/hypersign-identity-network/developers/hid-node.md +++ b/hypersign-identity-network/developers/hid-node.md @@ -99,7 +99,7 @@ The generation of Golang code is done by the script `scripts/protogenc.sh`. The ### DID Document -The [DID-Core](https://www.w3.org/TR/did-core/) W3C Specification has been followed to frame the structure of a DID Document. It's proto representation is mentioned in `proto/ssi/v1/did.proto`. The message `DidDocumentState` is stored on chain. +The [DID-Core](https://www.w3.org/TR/did-core/) W3C Specification has been followed to frame the structure of a DID Document. Its proto representation is mentioned in `proto/ssi/v1/did.proto`. The message `DidDocumentState` is stored on chain. ``` // proto/ssi/v1/did.proto @@ -148,7 +148,7 @@ message Credential { ## `x/ssi` Module -In Cosmos SDK, every operations related to blockchain such as staking, delegation, token trasfer, etc are handled by different modules. They are defined in the `x` directory of Cosmos SDK (See [here](https://github.com/cosmos/cosmos-sdk/tree/main/x)). For instance, `x/bank` module handles the functionality of token transfer. `x/ssi` module lets you store documents such as Decentralised Identifiers (DID), Schema Document and Verifiable credential Status on chain. +In Cosmos SDK, every operation related to blockchain such as staking, delegation, token trasfer, etc are handled by different modules. They are defined in the `x` directory of Cosmos SDK (See [here](https://github.com/cosmos/cosmos-sdk/tree/main/x)). For instance, `x/bank` module handles the functionality of token transfer. `x/ssi` module lets you store documents such as Decentralised Identifiers (DID), Schema Document and Verifiable credential Status on chain. **Quick Overview** @@ -156,13 +156,13 @@ In Cosmos SDK, every operations related to blockchain such as staking, delegatio `x/ssi/keeper`: Interaction with the state of blockchain -`x/ssi/genesis.go`: - Initialising and Exporting of genesis variables of `x/ssi` module, such as `chain_namespace`. - For public mainnet chain, `chain_namespace` should be empty. In case of testnet, the name of the testnet should be assigned. If you are running a private network, you can specify your own chain namepsace. +`x/ssi/genesis.go`: - Initialising and Exporting of genesis variables of `x/ssi` module, such as `chain_namespace`. - For public mainnet chain, `chain_namespace` should be empty. In case of testnet, the name of the testnet should be assigned. If you are running a private network, you can specify your own chain namespace. `x/ssi/modules.go`: Defines the interface for `ssi` module ### Keeper -Keepers provides an abstraction to interact with the state of the blockchain. The store is a data structure which persists the state. The `Get` and `Set` methods of the store are handled by the Keeper. There are Keeper functions defined for each of the RPCs. Transaction-based RPCs share a similar workflow, while Query-based share different workflow similarity among themeselves. +Keepers provides an abstraction to interact with the state of the blockchain. The store is a data structure which persists the state. The `Get` and `Set` methods of the store are handled by the Keeper. There are Keeper functions defined for each of the RPCs. Transaction-based RPCs share a similar workflow, while Query-based share different workflow similarity among themselves. **Transaction Based Keepers** @@ -202,7 +202,7 @@ func (k msgServer) CreateDID(goCtx context.Context, msg *types.MsgCreateDID) (*t didDocument <- get the DID Document from `msg` arg signature <- get the signature information from `msg` arg - // Verfication of Document // + // Verification of Document // err = ValidateDidDocumentElements(didDocument) if err != nil { return nil, err @@ -572,7 +572,7 @@ The `50uhid` is deduced from the **Identity Provider** account The cross-chain transfer of tokens between Cosmos-based chains is possible using Inter-Blockchain Communication (IBC) Protocol. Refer the IBC Documentation [here](https://ibc.cosmos.network/main/ibc/overview.html). -Run the following to transfer tokens between two accounts located on seperate chains +Run the following to transfer tokens between two accounts located on separate chains ``` hid-noded tx ibc-transfer transfer --from @@ -590,11 +590,11 @@ This node stores the complete state of blockchain. However, it does not actively #### Validator Node -It is a full node, which has a significant stake in the network and activately takes part in the validation process. +It is a full node, which has a significant stake in the network and actively takes part in the validation process. #### Seed Node -It's purpose is to introduce newly connected nodes, to other nodes in the network, and disconnects after doing so. +Its purpose is to introduce newly connected nodes, to other nodes in the network, and disconnects after doing so. In order to run in seed mode, set `pex = true` and `seed_mode = true` in `/config/config.toml` From 6c1cf105dd419482ca3a8a420a9781a959d1772a Mon Sep 17 00:00:00 2001 From: omahs <73983677+omahs@users.noreply.github.com> Date: Mon, 9 Sep 2024 11:12:48 +0200 Subject: [PATCH 4/4] fix typos --- .../hypersign-decentralized-identifier-dids.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/hypersign-identity-network/developers/hid-ssi-sdk/hypersign-decentralized-identifier-dids.md b/hypersign-identity-network/developers/hid-ssi-sdk/hypersign-decentralized-identifier-dids.md index 1fb0271..214e7c5 100644 --- a/hypersign-identity-network/developers/hid-ssi-sdk/hypersign-decentralized-identifier-dids.md +++ b/hypersign-identity-network/developers/hid-ssi-sdk/hypersign-decentralized-identifier-dids.md @@ -6,13 +6,13 @@ description: A Javascript based SDK for DID Operations Hypersign Decentralized Identifiers (Hypersign DID) comply [W3C DID specification](https://www.w3.org/TR/did-core/) and is built on top of [Hypersign Identity Blockchain Network](https://explorer.hypersign.id/hypersign-testnet). It implements [Hypersign DID scheme (`did:hid`)](https://docs.hypersign.id/self-sovereign-identity-ssi/decentralized-identifier-did). -Note: `did:hid` DID scheme is yet to be offcially registered on [W3C DID registry](https://www.w3.org/TR/did-spec-registries/). +Note: `did:hid` DID scheme is yet to be officially registered on [W3C DID registry](https://www.w3.org/TR/did-spec-registries/). Read [decentralized-identifier-did](../../../core-concepts/decentralized-identifier-did/ "mention") section for more details. ## Hypersign DID SDK -Is a javascript library for DID related operation (generate, sign, verify etc). It also provides APIs to store/update/retrive DID and DID Documents to/from the [Hypersign DID Registry](https://docs.hypersign.id/self-sovereign-identity-ssi/decentralized-identifier-did/did-registry) on the Hypersign Blockchain network easily. +Is a javascript library for DID related operation (generate, sign, verify etc). It also provides APIs to store/update/retrieve DID and DID Documents to/from the [Hypersign DID Registry](https://docs.hypersign.id/self-sovereign-identity-ssi/decentralized-identifier-did/did-registry) on the Hypersign Blockchain network easily. ## Table of Contents @@ -51,7 +51,7 @@ import { HypersignDID } from 'hs-ssi-sdk'; ```javascript const hypersignDID = new HypersignDID(); -// OR initialize by passing a namepace. Default 'testnet' +// OR initialize by passing a namespace. Default 'testnet' // More complex way to initialize this class can be found in this documentation later const namespace = 'testnet'; const hypersignDID = new HypersignDID({ namespace }); @@ -150,7 +150,7 @@ Sing a DID Document and generated proof ```javascript sign(params: { didDocument: object; // A DID Document to signed - privateKeyMultibase: string; // private key mulibase of type ED25519 + privateKeyMultibase: string; // private key multibase of type ED25519 challenge: string; // Random challenge domain: string; // Domain name did: string; // DID, if passed then DID will be resolved and `didDocument` parameter will not be used @@ -232,7 +232,7 @@ Verifies a signed DID Document. ```javascript verify(params: { - didDocument: object; // Signed did documen + didDocument: object; // Signed did document verificationMethodId: string; // The verification method challenge: string; // Random challenge domain?: string // The domain name @@ -305,7 +305,7 @@ const hypersignDid = new HypersignDID({ namespace: 'testnet', // OPTIONAL namespace of did, Default '' }); -// OR Just initalize with offlineSigner +// OR Just initialize with offlineSigner const hypersignDid = new HypersignDID({ offlineSigner })