New feature: Post a mesagge - hash on CryptoDbSS Based blockchain
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:
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 type of transaction data.
This is a simplified example of how it has been restructured:
these new features open new possibilities to the scalability to the project,next, I will show some examples of use of the new features , Rock the future today lml.
Follow the updates and successes in development. You can also explore the potential and stay updated by checking out the repository on GitHub: github.com/Steeven512/CryptoDbSS
- 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 type of transaction data.
This is a simplified example of how it has been restructured:
Before:
if(typeTransaction == 0x0A || typeTransaction == 0x0A ){
if(typeTransaction == 0x0A){
msg = Transaction.substr(83,32);
} else{
msg = Transaction.substr(75,32);
}
}
after:
if(transactionStructure[typeTransaction].haveMsg){
msg = Transaction.substr(msgPos,msgLength);
}
these new features open new possibilities to the scalability to the project,next, I will show some examples of use of the new features , Rock the future today lml.
Follow the updates and successes in development. You can also explore the potential and stay updated by checking out the repository on GitHub: github.com/Steeven512/CryptoDbSS