TuumiO Whitepaper

Version 1.0, September 26th, 2024

Table of Contents

1. Tuumio - Enabling Web3 and Digital Sovereignty.
2. Introduction to networks and their relevance to your digital existence
3. Most networks are centralized and why that matters
4. Decentralized networks are needed to achieve digital sovereignty
5. TummlO application networks addresses the problem
6. What would it take to build decentralized application networks ..
7. Achieving decentralized networks requires more than Blockchain
8. Building decentralized application networks needs to solve a few things first
9. A robust p2p application protocol
10. New primitives
11. A new user experience
12. TuumIO Primitives
13. TuumlO Protocol - A Peer-to-peer networked application protocol
14. Tuumio Protocol in Action
15. TuCard
16. TuCard in TuumlO Wallet
17. TuCard - a networked application object
18. TuNode
19. Role-Specific Nodes
20. Tuumio Wallet - Ultimate Web3 wallet for crypto and real-world apps.

Tuumio - Enabling Web3 and Digital Sovereignty

A Framework for transparent applications, decentralized compute and data Infrastructure

TuumlO introduces a groundbreaking compute paradigm coupled with a comprehensive Web3 infrastructure, designed to foster the development of decentralized, interoperable application networks. TuumlO empowers developers to create real world apps in form of app networks where data, compute, and identity are entirely user-owned and controlled.

TuumlO application networks not only enhances user privacy and data sovereignty but also paves the way for a new era of peer-to-peer digital interaction where users can trustfully connect and interact without intermediaries or centralized services.

Introduction to networks and their relevance to your digital existence

Networks can be computing networks, developer platforms, marketplaces, financial ecosystems, social networks, healthcare systems, or online communities that we use every day to access application on internet.

Developers, entrepreneurs, and everyday users have cultivated thousands of these networks, sparking an unparalleled wave of innovation and collaboration.

However, most networks are under the control of private entities. The core issue lies in the need for permission. The networks and applications are permissioned - In this model, the network retains control over users' data and dictates how information can be accessed and used.

Most networks are centralized and why that matters

When we discuss "centralized" applications and networks, it's important to understand that centralization refers to the concentration of control, not necessarily the technical architecture.

Take platforms like Wikipedia, Netflix, and X as examples. While these services operate on distributed infrastructures across multiple global data centers, their governance remains centralized. Decision-making power is concentrated within the hierarchical structure of the organizations that control these systems.

Despite the distributed nature of the underlying technology, authority, control, and access are consolidated, creating centralized power structures.

As a result, the internet has increasingly become a controlled environment dominated by a handful of major corporations acting as gatekeepers. This has led to the rise of centralized platforms, networks, and applications, where the flow of information and opportunities for innovation are tightly regulated.

Decentralized networks are needed to achieve digital sovereignty

The concept of decentralized networks is not a novel idea; it dates back to the early days of the internet. In the beginning, users would connect directly to each other to exchange data and resources using fundamental internet protocols. This peer-to-peer architecture embodied the original vision of the internet as a decentralized and open network, where information and services were shared directly between individuals without the need for centralized intermediaries.

However, as the internet evolved to accommodate a broader range of use cases and billions of users worldwide, the architecture shifted toward centralization. The client-server model emerged as the dominant framework, driven by the need to manage complex applications, scale services, and maintain control over data. In this model, services are hosted on centralized servers, controlled by a single entity, typically a corporation. Users, or clients, access these services based on permissions granted by the service provider, leading to an environment where control and ownership are concentrated in the hands of a few entities.

While the client-server architecture has enabled the rapid growth and widespread adoption of internet applications, it has also introduced significant challenges. Centralized control has led to concerns over privacy, data security, and the monopolization of digital resources. Users have become increasingly aware of the trade-offs involved in relying on centralized services, where their data and online activities are often commodified and exploited.

TummIO application networks addresses the problem

To address the challenges above, there is a growing need to return to the principles of decentralized networks. In this new paradigm, applications do not adhere to the traditional client-server model but instead operate on protocol governed decentralized application network where both the application logic and data are fully distributed across the network. In these networks, users retain full ownership and control over their data, and the network itself is governed by open protocols rather than by corporate entities.

The following diagram illustrate the fundamental difference between a centralized application network with client server architecture and a protocol governed decentralized application network.

Decentralized application networks are fundamentally different from their centralized counterparts. They are protocol-based, meaning that the rules governing the network are embedded in the protocol itself, ensuring that no single entity can exert control over the entire system. This shift from corporate control to protocol governance represents a significant departure from the current internet model and holds the potential to create a more equitable, transparent, and user-centric digital ecosystem.

• Every user wallet in the network is connected to a compute Node (TuNode). TuNode processes the events in an application.
• User's identity is a zero-knowledge wallet-based identity
• User can own the assets and data in their wallet, On-chain or any other decentralized storage
• In this model events are directly processed between Wallet users without the need for centralized services.
• Tuumio Protocols defines every aspect of an application network including the application objects and application flow

What would it take to build
decentralized application networks

Achieving decentralized networks requires more than Blockchain

Web3 and Blockchain technology have been heralded as the foundation of a user-owned internet — a decentralized world where individuals have control over their own data, identities, and online transactions. However, despite the promise of returning power to the users, the widespread adoption of Web3 solutions for real-world use cases has remained elusive.

The current landscape of Web3 is dominated by Blockchain networks, particularly at the Layer-1 and Layer-2 levels, where the focus is primarily on the distributed ledger technology that underpins these systems. While this has led to impressive innovations in areas such as decentralized finance (DeFi) and non-fungible tokens (NFTs), the broader enterprise and consumer applications have struggled to fully transition to Blockchain-based solutions. The core reason lies in the enduring challenges of the Blockchain trilemma—security, decentralization, and scalability—which has yet to be fully resolved.

Blockchain protocols, by design, are inherently slow due to the consensus mechanisms that ensure security and decentralization. This sluggishness, coupled with the high costs associated with transaction fees, often makes Blockchain networks prohibitively expensive for everyday use. Moreover, the public nature of most Blockchain networks raises concerns about privacy and confidentiality, particularly for enterprise applications that require stringent data protection and compliance measures.

For Web3 to achieve its full potential and drive real-world adoption, it must evolve beyond the current focus on distributed ledgers. A new generation of decentralized application networks requires —networks that are not only secure and decentralized but also fast, cost-effective, and capable of protecting user privacy. These networks should be designed to scale seamlessly, handling millions of transactions per second at minimal cost, without compromising on the core principles of decentralization and user ownership.

TuumlO's vison is to help bridge the gap between the idealistic vision of a decentralized web and the practical requirements of real-world applications.

Building decentralized application networks needs
to solve a few things first

• A robust p2p application protocol
  Decentralized application networks need a robust application specific protocol that can support a wide range of applications and use cases while ensuring that power and control remain protocol governed and is distributed among users
• New primitives
  Traditional client-server applications rely on server-side services, with client apps exchanging data through request-response or publish-subscribe design patterns.
  
  However, decentralized application networks require a new class of compute objects, or primitives, capable of securely operating in sync between peers in a distributed network.
• A new user experience
  Many users are accustomed to signing up for centralized services. To transition them to Web3, we need a transformative approach that enables them to connect their wallets, maintain self-custody of their data, and utilize zero-knowledge identity. This experience should be complemented by a user interface that feels familiar, allowing seamless access to decentralized applications (dApps)

TuumlO Primitives

TuumlO Primitives are specifically designed build decentralized application networks with self-custody of identity, data, compute, and permissionless network governance.

Here is a list of TuumlO Primitives, offering an effective alternative for transforming a centralized Web2 stack into a decentralized Web3 ecosystem.

TuumlO Protocol - A Peer-to-peer networked application protocol

TuumlO protocol powers decentralised application networks. TuumO Protocol is designed not only to power peer-to-peer (P2P) networks but also to serve as an application definition protocol. This means that every aspect of the network and its applications can be defined and governed within the protocol itself, providing a comprehensive framework for decentralized application networks.

The TuumlO protocol provides a comprehensive framework for defining an entire network application. Its structure is designed to facilitate the creation of full-scale application networks. With the TuumlO protocol, every aspect of both the network and the application itself can be defined within a single application definition.

The following illustrations shows the major network and application properties that can be defined t build a unique application network

The future of Web3 lies in the solutions that combine the best of Blockchain with application specific decentralized networks and other complementary technologies, such as off-chain processing, zero-knowledge proofs, and decentralized identity frameworks.

To fully realize the potential of deploying applications on a distributed permissionless peer-to-peer network, TuumlO protocol extends beyond mere networking and consensus and can achieve the following:

Define application objects directly within the protocol definition

By embedding application logic and workflows into the protocol, we can develop systems that are not only secure and decentralized but also enable user-owned applications (dApps) to communicate and process events in a truly decentralized manner.

Secure Peer-to-Peer Networked applications

Tuumio Protocol is designed to handle peer-to-peer events and data streams, offering a permissionless, protocol-driven application flow and behaviour. Unlike traditional client-server models, Tuumio protocol is designed to process the data and application in a peer-to-peer network model

Wallet Identity

Tuumio protocol is designed to support a wallet based identity as a participant in the network. Every participant in the Tuumio network is identified with zero knowledge wallet identity

User owned Data, Event and Compute

Tuumio protocol is designed around making the application logic to function at the user end rather than servers. This enabled users to owns the data and directly process data and event streams between peers (other users) facilitating seamless application flows without relying on any centralized intermediary servers.

Web2-like Scalability and User Experience

Despite its decentralized nature, the Tuumio network offers scalability and user experiences comparable to traditional Web2 applications

As an application definition protocol, TuumlO protocol defines the entire application's network, integrating the application network layer as a core component.

The following diagram illustrates the difference between typical blockchain protocols, which are centered on consensus and transaction management, and the Tuumlo Protocol, which elevates the architecture with a robust application network layer.

A typical Blockchain Protocol
(Designed for distributed ledger)

TuumIO Protocol
(Designed for an application network)

Tuumio Protocol in Action

In an active application network TummlO Protocol governs event, data and application journey flow between wallet users. For example in the following diagram when two users (Wallet based users) interact in a Network, The Tuumio protocol in a secure session ensures that:

• All the application logic (event handlers and TuCards), application flow (journey) are embedded in the Protocol itself
• Wallet users are able to discover and connect securely (based on verifiable credentials on Blockchain)
• Every Wallet user is also connected to TuNode. (All the Wallets users and their respective node this forming the network)
• Based on application TuCard and journey definitions in the protocol the wallet is able to perform actions defined on TuCards
• Protocol is securely able to send an event handler to respective TuNode to execute
• A Wallet user is able to read and write self-custody data either on Wallet app or any decentralized storage

TuCard

TuCard, is a fundamental building block in Tuumio networks. Through the Tuumio protocol, these TuCard can securely communicate and process data and compute across a peer-to-peer network, allowing wallet users to interact without intermediaries, thus achieving true decentralization.

TuCard is an encapsulated object model, serving as a foundational information block within Tuumio Networks. Similar to a data collection or table, TuCard encapsulates various data types and functionalities. It is a structured object that includes multiple data types, permission properties, encryption, and interfaces linked to specific events.

From HyperCards to TuCard
In 1987, Bill Atkinson introduced HyperCard at Apple, a concept that eventually led to the development of HTML (from HyperCards to Hypertext). HyperCard was an innovative way to build applications using "stacks" of virtual "cards," which held data much like a Rolodex system.

This marked the creation of the first successful hypermedia systems, which predated the World Wide Web. The cards communicated with each other using Hyper Talk, a foundational idea behind Hypertext, HTML, and the WWW.

Atkinson later reflected that had he recognized the potential of networked stacks rather than focusing on local stacks within a single machine, HyperCard could have evolved into the first web browser.

TuCard extends this groundbreaking idea into a decentralized, networked stack model, where cards can communicate and execute between users in a peer-to-peer fashion.

A TuCard on Tuumio Wallet is like an OOP Class. When any other interface calls this object, it can either produce a view to interact with or be used simply as an Object model that contains well defined data. A TuCard can be defined with the following interfaces:

TuCard Data Model

• Static and event data models - Define a static data or a data model for event transactions. Data can be viewed/processed/read/written with consent and private keys of the wallet holder
• Event Hooks - Object definition that can connect to an Event Handler to get/send data to and from the card

TuCard Ul Model

• Card Ul and tiles -TuCard can Ul can be simply defined using standard Ul tiles. Tiles can be static and dynamic with place holder for data coming from various sources.

TuCard Actions interface

• Read write actions - Actions that can be defined to read and write data from events
• Navigation actions - Actions that interact with navigation for example navigate to another card or access a Tuumio Wallet function
• Communication interfaces - Interface with other Tuumio Wallet and primitives
• Actions that capture data, validate an input data (On Ul Layer)

TuCard Interoperability

• TuCard object model is interoperable between Tuumio Networks. TuCard object can be received, sent and read by various Tuumio primitives based on the right access permissions governed by Tuumio Protocol and based on TuCard Holder's on chain Consent

TuCard in TuumIO Wallet

TuCard functions as a decentralized application (dApp) within the TuumlO Wallet. The TuumlO Wallet is capable of interpreting and executing the TuCard object model. This model encapsulates various elements such as the data model, user interface (Ul) model, and actionability. These components are interpreted by the TuumlO Wallet to provide both the user interface and the logic required by the application.

The diagram below further illustrates the structure of the TuCard model, offering a visual representation inside a TuCard.

TuCard - A networked application object

The TuCard is designed for execution within a peer-to-peer (P2P) network session, enabling direct interaction between peers without reliance on a centralized server.

Unlike the traditional client-server architecture, where clients request information and computations occur on the server, the TuCard facilitates event execution directly between participants. This decentralized approach eliminates intermediaries, allowing for more secure and transparent interactions.

For example, an action initiated by Wallet User-1 in a peer-to-peer session can be executed seamlessly, with the resulting execution state being made available directly to Wallet User-2. This shared execution model enhances trust and efficiency within decentralized networks. The event can be routed through a wallet connected node in the application network. Please see the diagram below to understand

• Being foundational building block for applications within Tuumio Networks TuCards can exchange data and consent directly with other users, facilitating seamless interaction across the network.
• Leveraging the Tuumio Protocol, TuCards securely transfer events to TuNode, allowing them to consume and publish data according to their designated roles within the network.

TuNode

TuNode introduces a revolutionary computing paradigm aimed at replacing the traditional client-server architecture. As the digital twin of the TuumlO Wallet within the application network, TuNode facilitates seamless user-owned verifiable compute.

Each TuumlO Wallet is permanently paired with a TuNode in every network it joins. This immutable wallet-node pairing is securely registered on-chain using verifiable credentials, ensuring traceable and tamper-proof interactions across the network.

TuNode has three major modules:

Interfaces - The TuNode interface enables wallets and other nodes to discover, securely connect, and exchange events. It operates through two primary interfaces:

• Wallet Connect Interface - Ensures a secure connection between the wallet app and the node, facilitating seamless wallet-to-node mapping
• Node Controller Interface - Provides access to events and data on the node, allowing for secure interaction and data exchange. This interface also connects the TuNode to other on-chain networks such as Blockchain network

Verifiable Compute - This module ensures secure, self-custodied computation for wallet users. TuNode supports both built-in functions and Python-based event handlers. Each computation is verifiable as defined in TuumlO protocol, with all processed event data recorded as transactions on the blockchain in the form of an event ledger

Self custody Data - This storage module on TuNode allows users to synchronize their owned data from devices or other storage networks. The self-custody data module manages various data-specific operations, including tracking reference data and providing interfaces to connect with multiple data sources.

To meet the demands of real-world applications at the scale and speed of Web2 enterprises, TuNode offers always-available, decentralized compute power.

This ensures that applications can operate efficiently, delivering the performance and responsiveness required for enterprise-grade solutions, while remaining fully user-controlled and decentralized.

TuNode connects seamlessly to TuumlO Wallet and other nodes to facilitate the exchange and execution of events. It processes incoming events, executes the corresponding event handlers, and generates subsequent events, effectively driving the entire application workflow.

The TuNode runtime operates in alignment with the TuumlO Protocol, identifying roles, relationships, events, and their respective handlers. Within a protocol-driven network, TuNode validates events using on-chain verifiable credentials, and triggers the next step in the application flow, ensuring security and correctness at every stage.

Role-Specific Nodes

TuNode in a TuumlO application network is assigned distinct user roles such as patient, doctor, employee, or employer nodes. Depending on its assigned role, TuNode processes, executes, and stores events in line with the permissions and responsibilities tied to that role, ensuring the proper execution of actions within the network's governance structure.

This diagram illustrates how a Tunode functions in a TuumlO network

A - TuumlO Wallet connects to Blockchain network to access the assets, and verifiable credentials to connect to Node on TuumlO network

B - TuumlO Network is an application network comprising of TuNodes. Each Wallet has one to one mapping with a TuNode. TuNode is also connected to Blockchain to process any event with verifiable credentials on Blockchain

C - Represents the interfaces available in a TuNode. A TuNode has secure interfaces to connect to Wallet and other interfaces to send, receive and execute the event on a network

D - Represents Compute module inside TuNode. It can compute functions defined in TuumlO protocol or a Python based event handlers that are defined and linked in TuumIO protocol

E - Represents ephemeral data on TuNode. Wallet user's is able to mount the self-custody data on TuNode from any storage network. There are two kind of data - Definition data is the definition about the event, and transactional data. Vault data is the mounted user's data for processing as per the application logic (Event handler)

Tuumio Wallet - Ultimate Web3 wallet for crypto and real-world apps

TuumlO Wallet is the wallet app to browse and use application networks. Like a web browser in Web2 world, TuumlO wallet let a user access the networks and TuCards (dApps) in the wallet app.

The TuumlO Wallet is an application container that empowers users to access network functionalities through TuCards (dApps). It allows users to store their data and identity in self-custody. Unlike Web2, where apps and web browsers access client-side functionalities through traditional web interfaces, the dApps on TuumlO Wallet connects seamlessly with other Wallets and TuNode, enabling direct peer-to-peer processing of events and data exchange with other users.

Crypto wallets are primarily designed to store your private keys, which are essential for accessing your digital assets on the blockchain. Unlike a physical wallet that holds cash and cards, a crypto wallet doesn't actually store your digital assets. Instead, all digital assets reside on the blockchain, and your private keys- stored in your crypto wallet — are what give you ownership and control over them, enabling you to make transactions.

Wallet apps like MetaMask and Trust Wallet often serve as the first entry point for users into the blockchain ecosystem. They provide means to manage private keys, allowing users to interact with the blockchain, own assets, and perform transactions.

Tuumio Wallets extends this idea of a basic crypto Wallet and enables it to hold more than private keys and ability to do basic transactions. Tuumio Wallet is like a real-world wallet where users can hold the application, identity, data and compute.

Tuumio wallet is a revolutionary idea to bring existing web2 users to web3. This wallet app let's user join a real-world application network (Tuumio Network) and contain and run dApps seamlessly that is indistinguishable from Web2.0 experience.

Tuumio Wallet is not just a crypto wallet but is a gateway to access application networks on multiple chains. It can store not just the private keys but user's decentralized profile, identity, assets and applications. It provides runtime for decentralized applications to execute on Wallet app itself.

A - A Crypto wallet connects to Blockchain to read or write a transaction using private key

B - TuumlO Wallet connects to blockchain On Blockchain TuumlO Wallet works like a standard crypto wallet to manage assets, identity, consent and its role on a Tuumlo network

C - TuumlO Wallet is a self-custody wallet with private key generated on the device itself

D - Tuumio Wallet holds TuCards -the networked dApps that are part of a Tuumlo network. TuCards could be applications, identity, profile or a data and Ul definition

E - TuumlO wallet provides standard APIs such as camera, location, payments, and lot devices over Bluetooth. Any TuumlO network can use these APIs via TuCards.

F - TuumO wallet is connected to a TuNode on Tuumio network. Tuumio wallet and TuNode pairing is linked using verifiable credentials on chain.

G - TuNode on TuumlO network are also connected to Blockchain to write application network events, process payments and use verifiable credentials on blockchain for compliance and verifying event handlers.