Posts

CryptoDbSS / Ethereum - Bridge interoperability

Image
a strong scability point is interoperability, How a software can work with another to increase its functionalities and users, CryptoDbSS has worked hard on this aspect, that is why Ethereum and its great ecosystem have been kept in view, one of the most notable is the implementation of its own EVM and smart contracts, these allow users to program decentralized applications within their blockchain, and a lot of unimaginable things, this article will demonstrate the implementation of these through the use of CryptoDbSS own software together with Ethereum, achieving interoperability between the two. This package is divided into 3 essential modules, the user layer that interacts with the bridge's dapp The Ethereum vendor Smart Contract the bridge-core engine Starting from the top, The User Layer . For a user to be able to use the app, it is necessary to provide a graphical interface, This is served via HTTP, and uses Web3.js to be able to integrate with...

CryptoDBSS with IPFS/Web3 implementation

Image
CryptoDbss allows short messages to be published on the blockchain as a transaction. This can be annotated to be linked as metadata, for example, the SHA of a data or document. In this case, an example of its use with IPFS will be given. What is IPFS? Interplanetary File System, as its acronym IPFS , is a decentralized network protocol that allows its users to share any file, or data between connected nodes. It can also be called Web3 protocol, therefore anyone running a node can share or download what others share, without the need for a centralized server. These files, in turn, can be in directories, which allows for more orderly and precise indexing, to access them, it is necessary to know the CID (content identifier). This is generated when the file is uploaded. Each CID for each file and directory is unique, so there is only one unique one for each one, just like a hash, which is generally represented in base58. Many decentralized apps and DAO's that use the term w...

CryptoDbSS Client Light

The first CryptoDbSS lightweight client has been written in C++ as a CLI app. It allows you to interact with CryptoDbSS-based blockchains. Its lightweight and simple library enables independent calls to its methods, facilitating the creation of derivative applications. The client allows to add and save wallets securely with an encryption password. make transactions. index account balances. index transactions by block number or hash and other metadata. index blocks. The repo is on the CryptoDbSS GitHub. github.com/CryptoDbSS/CryptoDbSS-Client-API-RPC keep following the updates and news and check the github, thanks for read.

New feature: Post a mesagge - hash on CryptoDbSS Based blockchain

Image
the new udate has arrived CryptoDbSS brings new features that debut in this update A new type Of transaction , which stores 32bytes provided by the sender, can be use for multiple purposes such as: links metadata by hash reference be used as CID Ipfs Linking transaction blocks links to a smart contract address post a custom mensagge The algorithm structure now has been simplified in the code to improve readability and maintenance, and it is easier to add future features such as new transaction types. also the data structure of the transaction types is now defined by structs. This largely eliminates most dependencies in future algorithm modifications. Only the definition of transaction type elements needs to be added to the structure. The algorithm's behavior will then depend on reading these transaction data structure definitions. In essence, these definitions will instruct the algorithm on how to proceed according to the established logic for each ty...

Upcoming Update: Interoperability with Ethereum, External Chain Data Index with IPFS and Support for Federated Learning AI

Image
The next update for CryptoDbSS will introduce significant enhancements aimed to coming up interoperability between Ethereum and Introduce a new type of transaction for storage externad data reference bringing with it support for Federated Learning AI and data privacy. Key features of this update include: presentation of a new type of transaction new type of transaction relies on high extenal storage of data utilizing SHA (Secure Hash Algorithm) for reference it on the blockchain, using a protocol as IPFS , This will bring many practical uses, one focus of this will be the support Federated Learning AI. Interoperability with Ethereum This implementation will include a CryptoDbSS client configured through a Smart Contract on an Ethereum-based network with an end-point node. This setup will serve as a bridge between Ethereum and CryptoDbSS, enabling users to exchange funds across both network-chains seamlessly. Support for Federated Learning The update will al...

DB Architecture and Storage - Transacs and Block Structure

transactions structure the transactions in CryptoDbSS have the following format in their structure, each data is written in sequence and is represented by a byte string: Element Size Transaction Type ID 1 byte Issuing Address 64 bytes Amount of Issuing Address 8 bytes Receiving Address 64 bytes Amount of Receiving Address 8 bytes Transaction Number ID 2 bytes Feed 4 bytes Signature 64 bytes ID Blockchain 32 bytes SHA of Node Matchmin 32 bytes Block Header 32 bytes Total 311 bytes the total length of this is reduced by compression alg...

Consensus: MatchMin

Image
Matchmin      A fundamental aspect in the blockchain area, if not the most important, is the consensus of the network of participants. It constitutes the basis of what is permissive and what is not in the network, which must be taken into account for the correct verification of the data, and how to act accordingly following a logic and algorithm through a common agreement between the participants. The Matchmin scheme is the following: the network is made up of 2 types of participants, Validators and Clients , each node is identified with a unique ID that the rest of the participants know, this is a cryptographic public key which it itself derived before joining the network and who only knows and uses its private key . further to recognizing each other within the network, the key is used to sign and corroborate the data that is sent between nodes and certify the authenticity of the sender . If someone tried to falsify data in advance, they would not be able...