cuublemesh
and it’s capabilities
Built on a unique distributed peer-to-peer mesh web services engine and a unique smart multi node, multi chain signed digital credential database. Its operational functions allow the digital credential, multi node and chain system to be easily configured and tested for your applications and the digital credential chains to be validated for chain data content integrity.
Multi Node
Single node or peer-to-peer mesh multi node operation
Multi Chain
Each node can support the easy creation of multiple, named trusted digital signed credential chains
Multi Digital Credential (Block) Types
Multi credential types with three levels of legally applied digital signatures and configurable data schema allow for a wide range of trusted DLT applications where data provenence and trust is key.
Multi Token Types
Multi token type schema allows for a wide range of asset tokenising strategies
System & Personal
Allows for system wide and personally created and protected digitally signed credential chains
Token assignment
Allows for user selected token assignment to block chain information, media and event entries
High Performance
Has high performance search tools and indexing capabilities
Smart Contracts
On screen business and operational level smart contract creation and multi chain execution
Well Beyond a single purpose block chain – multi node, multi chain , multi credential types, full PKI and OSS – Telco Style Engineering
Many block chain entities
Cuublemesh goes beyond a single application block chain data technology for a dedicated ledger application between a few selected companies, possibly creating a costly process silo. Cuublemesh is a peer-to-peer web services (information) engine that enables many types of legally signed digital credential (block) chain entities (ledgers) for varied operational, business and trusted activity reasons. This is truly the Web 3.0 and the ZTA (Zero Trust Architecture) agenda being delivered.
Smart Contract Block
key features
A dynamically configurable block chain smart contract capability providing supply chains, health systems, legal services. Operationally these need the cuublemesh block chain management, routing, notification and status services, plus the ability to find transaction information fast over large data sets. Our Smart Contract block chain function includes these key features:
Decentralised
Decentralised Meshed Environment – allows for governance partitions and B2B style domains
Addressable
Addressable Nodes and Chains – allows chains to be identified and blocks routed to them and origination/destination data kept in the block itself
Multi Block Types
Multi Block Types – allows for application, commercial relationship or contract specific contexts
Multi Token Types
Multi Token Types – allows for application, commercial relationship or contract specific tokenisation and value contexts
Cross Mesh Search
Cross Mesh Search on Transaction Ids etc. – allows for a set of blocks relating to a transaction to be seen as a ordered set of blocks regardless of the node/chains/parties that transaction spanned
New Block Routing
New Block Routing – allows for a transaction on one chain to write the block data to another addressable chain – for that transactions next step of processing by another party in a different domain
Notification
Block Action Notification Services – allows for the users of the system to be notified when blocks are written by one party and the other party needs to know that
Activity Status
Block Activity Status Services – allows for a block – with a coupled status area to be updated as to how the block was acted upon
Managed Content
Transaction Block Sequence Managed Content – allows for the addition and removal of block content (supporting information) at each stage of the transaction sequence
Managed Smart Contracts
Transaction Block Sequence Managed Smart Contracts – allows for the updating of the smart contract parameters at each stage of the multi block transaction sequence. Noting the smart contract information is carried in the block as part of its hashed payload. And can be updated as e.g. the input block data is used as a template for the action’s output block data