Предыдущая версия справа и слеваПредыдущая версияСледующая версия | Предыдущая версия |
en:startpage [2023/08/04 06:17] – anel | en:startpage [2024/04/30 06:52] (текущий) – anel |
---|
====== Start page ====== | ====== H2K Wiki ====== |
==== Connectivity Options==== | |
| ===== Knowledge base ===== |
| |
| **H2K service ** is a [[en:h2k:terms#Custodial wallet| crypto custodial wallet]] that utilizes a [[en:h2k:terms#Multisignature| multi-sig mechanism]] to ensure the security and authorization of transactions. |
| |
| H2K includes a unique technology with a well-thought-out security system that corresponds to [[en:h2k:terms#AES| AES]]. |
| |
Our team has successfully developed both a web version and a mobile application of the H2K service, providing clients with the flexibility to utilize these tools based on their level of experience in blockchain technologies. | Our team has successfully developed both a web version and a mobile application of the H2K service, providing clients with the flexibility to utilize these tools based on their level of experience in blockchain technologies. |
| |
|**[[en:h2k|The mobile application H2K Pro]]**|**[[en:lite|The web version H2K Lite]]**| | |**[[en:h2k|The mobile application H2K Pro]]**|**[[en:lite|The web version H2K Lite]]**| |
|Encompasses the full functionality of the service and is tailored for more experienced clients who have prior familiarity with multisignature and custodial wallets.|Offers a simple and intuitive interface, catering to users who seek convenient management of their multisignature wallets.| | |Encompasses the full functionality of the service and is tailored for more experienced clients who have prior familiarity with multi-signature and custodial wallets.|Offers a simple and intuitive interface, catering to users who seek convenient management of their multi-signature wallets.| |
| |
---- | ---- |
| |
**H2K service ** is a [[en:h2k:terms#Custodial wallet| crypto custodial wallet]] that utilizes a multi-sig mechanism to ensure the security and authorization of transactions. | **Service Components**: |
| - Electronic document flow for conducting and processing payments. |
| - A fully functioning backend that includes the software complex "Black Box + Safina API." |
| |
**H2K** consists of: | **[[en:h2k:terms#Black Box|Black Box ]]** - is the core of the information system for managing crypto-assets. It consists of subsystems for encryption and key storage, defining rules for working with secret keys, and interacting with the blockchain. |
- **[[en:h2k:terms#Black Box|Black Box ]]** - this is a control server with cryptographic signing capabilities to interact with the blockchain. | |
- **[[en:h2k:terms#Multi-Signature Wallet|The multi-signature wallet]]** – is the same as a regular blockchain wallet, but users do not need to interact directly with the blockchain. It can be seen as an online payment processing system, as H2K's server handles managing the wallet's private key and transaction processing. | **[[en:h2k:terms#API| Safina API]]** - is an application server that facilitates the interaction of Black Box with external networks. |
- **[[en:h2k:terms#API| API]]** – for businesses to connect to the multi-signature wallet. | |
With the help of the API, companies can send requests to Safina to create multi-signature wallets and conduct transactions using them. | |
| |
---- | ---- |
| |
====== The relevance ====== | The solution significantly expands the capabilities of smart contracts, providing access to real-world data and autonomous computations while maintaining the security and reliability guarantees inherent to blockchain technology. |
| |
- Increasing interest in working with crypto assets; | Service clients have the ability to verify the funds in their wallets without the need for obligatory interaction with us. |
- Transition of many financial services to crypto assets; | **We do not have access to clients' funds.** Only wallet owners and authorized wallet signatories have control over their assets. |
- Need for conducting cross-border payments. | |
| |
Due to the spread of crypto assets, new solutions are required for easy access to the blockchain and secure transaction processing. | |
| |
| |
In the modern world of crypto assets, there are **2 main** issues that stand out: | |
* Preserving the [[en:h2k:terms#private key| secret key]] from loss; | |
* Distributing access to the secret key among potential wallet owners. | |
| |
---- | ---- |
| |
The project's Hidden Keys (hereinafter referred to as H2K) know-how is a fast and secure [[en:h2k:terms#blockchain|blockchain]] technology that functions as a [[en:h2k:terms#Multi-Signature Wallet|multi-signature]] wallet. It includes a unique technology with a well-thought-out security system that corresponds to [[en:h2k:terms#AES| AES]]. | =====Functionality of H2K===== |
| |
The solution significantly expands the capabilities of smart contracts, providing access to real-world data and autonomous computations while preserving the security and reliability guarantees inherent in blockchain technology. | ^ Functionality of H2K ^^^ |
| | Supported Blockchains and Tokens: H2K provides full coverage of the Bitcoin (BTC) blockchain, Polygon and supports the TRON and ETH blockchains, including tokens such as TRX, ETH, MATIC and USDT (TRC-20, ERC-20). In the near future, we plan to add support for other tokens.| Convenience: We offer wallet import functionality, the creation of multi-signature wallets (up to 9 signatories), and the ability to create multiple wallets for a single user.|Multi-signature Wallets:We offer a unique offline method for creating, signing, and verifying transactions.| |
| |
[[en:h2k:terms#Black Box| Black Box]] (BB) - the core of the service. | **Signature verification and collection** |
| |
{{ :en:концептуальная_карта_-_1-2.png?1000 |}} | In H2K, the wallet's private key is stored centrally in a Black Box instead of being distributed among the wallet signatories and owner in separate parts. To conduct a transaction, all participants of the wallet provide electronic signatures generated by H2K, which identify them. Then, based on the verification of these signatures, the server automatically signs the transaction with the private key. |
| |
To create a transaction, wallet participants must provide their signature. In our case, the signature can be of two types: | To create a transaction, wallet participants must provide their signature. In our case, the signature can be of two types: |
- A generated BB key pair using the elliptic curve method, with the public key shared with the participant. | - A generated BB key pair using the elliptic curve method, with the public key shared with the participant. |
| |
---- | {{ :en:enc.png?600 |}} |
======Functionality of H2K====== | |
| |
^ Functionality of H2K ^^^ | The signing sequence is as follows: first, wallet co-signers provide their signatures. Once the minimum number of signatures is reached, the owner of the wallet's signature is also checked. Next, a manager from the H2K document management system adds their signature. It's important to note that all signatures from participants in the signing process have the same status. If any of the signatures are missing (or the minimum number of co-signer signatures is not obtained), the transaction will not be sent to the network. |
| Supported Blockchains and Tokens: H2K provides full coverage of the Bitcoin (BTC) blockchain and supports the TRON and ETH blockchains, including tokens such as TRX, ETH, and USDT (TRC-20, ERC-20). In the near future, we plan to add support for other tokens.| Convenience: We offer wallet import functionality, the creation of multi-signature wallets (up to 9 signatories), and the ability to create multiple wallets for a single user.|Multi-signature Wallets:We offer a unique offline method for creating, signing, and verifying transactions.| | |
| |
---- | **Security** |
| |
===Signature verification and collection=== | |
| |
The [[en:h2k:terms#Managing Server|management server ]]is responsible for collecting signatures. It passes the collected signatures to BB, which, in the case of codes, verifies the received signatures against the generated ones. In the case of key signing, BB verifies the participants' keys against those specified during the wallet creation. | **The main security principle** is the complete isolation of processes involving wallet creation, wallet key generation, and signature verification from external threats. |
After successful verification by BB, the transaction is sent to the network. | |
| |
Successful verification criteria: | **The key system and security** revolve around the secure isolated data storage of Black Box. It is located in the DMZ (Demilitarized Zone) and operates according to the established rules set during its creation. This server is responsible for creating wallets, storing their private keys, signing transactions with them, and sending them to the blockchain. |
| |
- The minimum required number of signatures is collected. | The H2K server in the DMZ has tightly restricted access privileges, preventing employees from stealing private wallet keys. |
- The signature of the wallet owner matches. | Electronic signatures from wallet participants are generated by the Safina application server and then transmitted to Black Box for inclusion in wallet parameters. |
| |
---- | ---- |
| |
* [[en:h2k:token|CH2K token]] | |
| |
* [[en:h2k:doc|Documentation]] | |
| |
* [[en:h2k:dao|H2K DAO]] | |
| |
---- | |
| |
[[https://h2k.me/|H2K Website]] | [[https://h2k.me/|H2K Website]] |
| |
[[https://my.h2k.me|H2K web version]] | [[https://my.h2k.me|H2K web version]] |
| |
[[https://www.linkedin.com/company/h2k-hidden-key|Linkenin H2K]] | |
| |
[[https://t.me/test_h2kbot|H2K Mobile's Chatbot (powered by ChatGPT)]] | [[https://t.me/test_h2kbot|H2K Mobile's Chatbot (powered by ChatGPT)]] |
| |
[[https://t.me/public_h2k_app|H2K's telegram channel]] | |
| |
[[https://h2k.me/suggestions_ru|The feedback form]] | [[https://h2k.me/suggestions_ru|The feedback form]] |
| |
[[https://www.youtube.com/@OrisLab|Videoinstructions on YouTube]] | |
| |
| |
| |