This pattern implements a service for interaction with Solidity Smart Contracts, enabling the user to read and write to a deployed contract instance. Additionally, the pattern includes a deployment playground for configuring and deploying custom smart contracts.
The pattern requires the web3-blue nodes installed in the Node-RED environment.
This pattern can be used for the generation of asymmetric keypairs, signing of data payloads and verifying payload signatures. The keys for each of the sign and verify function must be provided alongside the payload being signed or verified. In the test injectors, the keys are stored in the Node-RED context, but in a real application scenario these should be kept safe in a secure manner.
The pattern requires the crypto-blue nodes installed in the Node-RED environment.
Pattern Expected Payload:
The Contracts node can be utilized to interact with Solidity Smart Contracts. The node offers functions for deploying a Smart Contract to an RPC network, performing call and send operations and also transacting and sending ETH to Smart Contracts.
The Accounts node can be used to create web3 accounts, recover them by using their private key, import them into an RPC provider, lock / unlock them, sign data or transactions and recovering signers from signatures and signed transactions.
The RPC node can be used to start/stop and interact with an RPC server. This is done by deploying detached Ganache Instances that can run as background processes. The node offers utilities for getting the RPC's accounts, blocks and transactions. It also offers capabilities for performing a transaction on the RPC node.
The PKI node is used to generate Ed25519 key-pairs, sign message payloads and verify payload signatures. The following properties can be configured for the node:
Function: The node's functions, choices include:
Private Key (string): The private key to use in the signing process, must be in hex format. This can also be configured through the msg.privateKey field of an injected message.
The Cipher node uses the AES algorithm for encrypting and decrypting message payloads. The following properties can be configured for the node:
Function: The node's functions, choices include:
Algorithm: The algorithm mode to use in the node, the options included are the following: AES-CBC, AES-ECB, AES-CFB, AES-OFB, AES-CTR, AES-GCM
IV (string): The initialization vector to use, must be in hex format. This can also be configured through the msg.iv field of an injected message.
IV Size: The size of the initialization vector, options include 128 bit, 192 bit and 256 bit.
The PKDF node is used for generating and recreating encryption keys. The following properties can be configured for the node:
Iterations (number): Define the number of iterations to perform for the key derivation function. This can also be configured through the msg.iterations field of an injected message.Key Size: The key size to generate, options include 128 bit, 192 bit, 256 bit.Salt Size: The size of the salt to use, options include 128 bit, 192 bit, 256 bit.Salt (string): The salt to use for the key derivation function, must be in hex format. This can also be configured through the msg.salt field of an injected message.Password (string): The password to use in the key derivation function. This can also be configured through the msg.password field of an injected message.
The Hasher node is used to generate SHA payload hashes and hashed message authentication codes. The following properties can be configured for the node:
Function: The node's functions, choices include:
Hash Size: The output hash size can be configured in the node's edit dialog, options include 256 bit (SHA256), 384 bit (SHA384) and 512 bit (SHA512).This flow implements capabilities for hashing user provided data using Secure Hash Algorithm.