Code Blockchain
At CodeB, we’re elated to present a novel addition to our popular “CodeB TOTP SMS” application – mobile digital signatures. Going beyond the realms of traditional text messaging, we have fused advanced SMS security with an inbuilt Time-based One-Time Password (TOTP) authenticator, rendering a comprehensive and user-friendly solution. In recognition of the growing necessity of … Read more
Online security has become a major concern for most people. Every day, we hear about hacks, breaches, and stolen data. With cybercriminals lurking on the internet, it’s essential to take every step necessary to protect yourself. Two-factor authentication (2FA) is one such step that you can take to safeguard your online accounts or your local … Read more
To use the SMS validation feature of the CodeB app, please follow these three steps: Firstly, after installing the app, configure and confirm your mobile number in the “Settings” menu by selecting “Own Number” and pressing “OK”. Secondly, configure your carrier’s CodeB Identity Node by selecting “CodeB Identity” in the “Settings” menu. The default setting … Read more
With the new feature “Authenticated Anonymity“ CodeB addresses the need for authenticated but anonymous communication. Required function as not only exposed in the messaging namespace of our Web Services Interfaces but are also abstracted into our CommandLine Interface. To send an anonymous message at least three parties (Self-Sovereign Identities) are involved. Sender SSI Recipient SSI … Read more
Received messages are automatically dumped into a mailbox on any node if the node hosts any of the recipients principal accounts. To enumerate received messages use function ListReceivedMessages. Parameters are: ChainAddress/ChainPassword Principal account credentials to decrypt a message. You can view any message in raw format via function RetrieveRawMessage. Retrieved messages can manually validated via … Read more
Messages created with CreateMSG2Group and CreateMSG2Address or viewed with RetrieveRawMessage can be validated with this function. Parameters are: JSONMessage The encrypted message in JSON format ChainAddress/ChainPassword The keypair to decrypt and validate the message.
With the functions CreateMSG2Group/SubmitMSG2Group and CreateMSG2Address/SubmitMSG2Address in the messaging namespace (for example https://coin.codeb.io/messaging.asmx) you can send anonymous, but authenticated messages, as broadcast to all members of the group or directly to one identity contract or principal identity. Note: Functions ending with “Group” are broadcasting to all members of a group while functions ending with “Address” … Read more
For the messaging subsystem to work a Key Distribution Identity Contract is required. This contract triggers the function CalculateZKPKeys. ZKPs are distributed to all principal accounts registered with RegisterKeyInMemberSSI in their identity contract. You find the function CalculateZKPKeys in the messaging namespace. For example on: https://coin.codeb.io/messaging.asmx The functionality is also abstracted into the CommandLine Interface. Parameters … Read more
For the messaging subsystem to work it is essential to register the Self-Sovereign identity contract holding the key material with the Key Distribution Identity Contract. You find the function UpdateGroupList in the messaging namespace. For example on: https://coin.codeb.io/messaging.asmx The functionality is also abstracted into the CommandLine Interface. Parameters for the function are: MyGroupID The secure messaging … Read more
Messaging Keys remain anonymous to the system unless registered with the function RegisterKeyInMemberSSI. The function can be found in the messaging namepace. For example on: https://coin.codeb.io/messaging.asmx The functionality is also abstracted into the CommandLine Interface. Parameters are: MemberSSIAddress The address of the Self-Sovereign Identity contract for which the key is being registered. ChainAddress / ChainPassword … Read more