Method and System for Cryptographically Verifying Digital Presence and Coordinated Participation Using Distributed Ledger Technology
The PresenceNet protocol addresses the lack of secure presence verification and coordination in decentralized networks by using Marks, Rituals, and WaveNames to enable scalable, privacy-preserving digital coordination and action execution on distributed ledgers.
Patent Information
- Application Number
- CA3272915
- Authority / Receiving Office
- CA · CA
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-06
- Publication Date
- 2026-11-07
AI Technical Summary
Conventional digital systems lack a universal, cryptographically secure method for verifying human presence and coordinating collective action across decentralized networks, and existing blockchain protocols do not support symbolic presence, time-bound coordination, or context-specific identities.
PresenceNet protocol, which uses Marks, Rituals, and WaveNames to cryptographically verify digital presence, coordinate participation, and trigger programmable actions on a distributed ledger network, supporting multi-party vaults, off-chain data referencing, and cross-ledger execution.
Provides a verifiable, trustless layer for digital coordination and memory, enabling scalable and privacy-preserving applications in governance, collaboration, and decentralized finance.
Abstract
Description
Background
[0001] The present invention relates to decentralized systems and distributed ledger technologies (DLTs), specifically methods for verifying individual and group presence, coordinating participation, and executing conditional actions using cryptographic proofs.
[0002] Conventional digital systems lack a universal, cryptographically secure method for verifying human presence and coordinating collective action across decentralized networks. Centralized platforms (e.g., social media, collaboration tools) rely on trusted intermediaries, introducing single points of failure, privacy risks, and lack of user sovereignty. Existing blockchain protocols (e.g., Bitcoin, Ethereum) provide trustless record-keeping for financial transactions but do not natively support symbolic presence, time-bound coordination, or context-specific identities. For example, decentralized identity systems like W3C’s Decentralized Identifiers (DIDs) enable self-sovereign identity but lack mechanisms for synchronized multi-party coordination or hierarchical sub-contexts. Multi-signature wallets and voting protocols exist but are not designed for general-purpose presence verification or ritual-based triggers.
[0003] There is a need for a scalable, privacy-preserving protocol that cryptographically verifies digital presence, coordinates participation, and triggers programmable actions in a trustless manner. The present invention addresses this technical challenge through a novel protocol, PresenceNet, introducing primitives called Marks, Rituals, and WaveNames. Summary of the Invention
[0004] The invention, PresenceNet, is a computer-implemented protocol for cryptographically verifying digital presence and coordinated participation on a distributed ledger network. Users generate signed presence signals (“Marks”) asserting intentional presence at a specific time, associated with predefined coordination structures (“Rituals”) specifying participation rules and time windows. Upon satisfying Ritual conditions, a Completion Mark triggers actions such as asset release, token issuance, or smart contract execution. Hierarchical identity structures (“WaveNames”) enable context-specific identities derived from a base handle. The protocol supports multi-party vaults, off-chain data referencing, and cross-ledger execution, ensuring scalability and privacy. Unlike conventional blockchain systems, PresenceNet provides a verifiable, trustless layer for digital coordination and memory, enabling applications in governance, collaboration, and decentralized finance. Detailed Description 1.0 Definitions
[0005] The following terms are used throughout the specification:● Mark: A cryptographically signed data structure comprising a user’s public key, a timestamp, a cryptographic signature (e.g., ECDSA), and an optional memo field, recorded as a transaction on a distributed ledger. ● Ritual: A predefined coordination structure identified by a unique ritual_id, defining a start and end time, participation rules (e.g., number of Marks, specific participants), and optional governance parameters. ● Completion Mark: A signed transaction recorded on the ledger upon Ritual condition satisfaction, triggering predefined actions (e.g., smart contract execution). ● WaveName: A WaveName is a hierarchical identity derived from a base handle (e.g., $tom), formatted as $base~context (e.g., $tom~family). It maps to a unique wallet address and is used to organize presence activity by context—such as governance, collaboration, or personal use—without fragmenting signing authority. All WaveNames remain cryptographically linked to the base handle, ensuring unified control across distinct domains of interaction. ● Vault: A multi-signature asset container requiring threshold signatures or Ritual completion for asset release. 1.1 Overview
[0006] PresenceNet is a protocol enabling cryptographically verified presence and coordinated participation on distributed ledger networks, as described in Claims 1–10. It addresses the technical problem of trustless, time-bound coordination across heterogeneous ledgers. The protocol operates on a distributed ledger (e.g., XRP Ledger, Ethereum) and includes a companion application for user interaction. References to Figures 1–5 illustrate key processes. 1.2 Marks
[0007] A Mark is a cryptographically signed presence signal asserting a user’s intentional presence at a specific time, as shown in Figure 1. A valid Mark includes: ● A cryptographic signature generated using the user’s private key (e.g., ECDSA with SHA-256 hashing). ● A unique identifier (e.g., public key or handle). ● A timestamp generated by the user device and verified by ledger consensus (e.g., within 5 seconds of network time). ● An optional memo field containing a ritual_id or hashed metadata (e.g., SHA-256 hash of IPFS content).
[0008] Marks are submitted to a distributed ledger node as transactions or messages. For example, on the XRP Ledger, a Mark is encoded as a dust transaction (minimum value, e.g., 10 drops) with a memo field. The ledger confirms the transaction, anchoring the Mark in time (Claim 1, steps a–b).
[0009] Verification: To ensure authenticity, the application layer may implement optional safeguards, such as biometric prompts or two-factor authentication, without relying on centralized providers. For privacy, Marks may reference off-chain data via hashed pointers (Claim 4) or obscure sender identity in public views usingzero-knowledge proofs.
[0010] Mutuality Logic: To prevent spam, the protocol enforces opt-in interactions. Users only receive Ritual invitations or Mark acknowledgments from parties they have previously interacted with or explicitly followed (Claim 3).
[0011] Edge Cases: If a Mark’s timestamp is invalid (e.g., outside ledger consensus time), the transaction is rejected. Duplicate Marks are prevented by unique transaction hashes. 1.3 Rituals
[0012] A Ritual is a coordination structure defining synchronized participation, as depicted in Figure 2. It includes but is not limited to: ● A unique ritual_id (e.g., 256-bit hash). ● A start and end time (e.g., UTC timestamps). ● Participation rules (e.g., minimum 3 Marks from distinct users, specific public keys). ● Optional governance parameters (e.g., 2 / 3 quorum for approval).
[0013] Users submit Marks within the Ritual’s time window. A smart contract or ledger node evaluates conditions using deterministic logic (e.g., counting valid Marks). Upon satisfaction, a Completion Mark is generated (Claim 1, steps c–e).
[0014] Example: A “Weekly Sync” Ritual requires 5 team members to submit Marks between 09:00 and 09:15 UTC. If conditions are met, a smart contract updates a shared dashboard.
[0015] Edge Cases: If the time window expires without meeting conditions, the Ritual fails, and no Completion Mark is issued. Participants are notified via companion app. 1.4 Completion Marks
[0016] A Completion Mark is a signed transaction recorded on the ledger upon Ritual completion, triggering actions such as: ● Smart contract execution (e.g., token minting). ● Asset release from a vault (Claim 1, step e). ● Logging for future Rituals.
[0017] For example, a Completion Mark on XRPL is a transaction with a memo field containing the ritual_id and outcome hash, verifiable by all nodes. 1.5 Vault Integration
[0018] Vaults are multi-signature asset containers, as shown in Figure 3. A Ritual may link to a vault, enabling asset release upon: ● Threshold signatures (e.g., 3-of-5). ● Verified Ritual completion (Claim 8).
[0019] Example: A DAO vault holds 1,000 tokens. A Ritual requires 4-of-7 committee members to submit Marks within 24 hours. Upon completion, a Completion Mark triggers automated release to a recipient wallet.
[0020] Edge Cases: If signatures are invalid or thresholds are not met, the vault remains locked. Disputes are resolved off-chain or via a governance Ritual (Claim 2). 1.6 WaveNames
[0021] While only the base handle (e.g., $alice) is authorized to issue signed Marks, associated WaveNames act as semantic context tags that route or categorize participation. This allows users to maintain distinct memory streams and visibility controls across governance, social, or functional spheres without fragmenting control or custody. All WaveNames remain cryptographically linked to the same root identity.
[0022] Example: A user may use $bob for general coordination, $bob~team for organizational rituals, and $bob~dao for governance-related participation. Each WaveName is linked to its own wallet address but ultimately controlled by the same sovereign identity ($bob). 1.7 Governance and Voting
[0023] Rituals may include governance rules, allowing participants to submit votes as signed Marks with hashed metadata (Claim 2). Votes are tallied on-chain using deterministic logic. Results determine Ritual outcomes or future parameters. 1.8 Off-Chain Memory
[0024] Marks and Completion Marks may reference off-chain data via SHA-256 hash pointers to IPFS or Arweave (Claim 4). This ensures integrity while minimizing on-chain storage. 1.9 Cross-Chain Execution
[0025] PresenceNet supports interoperability across ledgers, as shown in Figure 5. A Completion Mark on one ledger (e.g., XRPL) may trigger a Ritual on another (e.g., Hedera) via a trusted oracle verifying the Mark’s hash (Claim 5).
[0026] Example: A Completion Mark on XRPL contains a hash read by a Hedera smart contract, initiating a token mint. 1.10 Memory Architecture
[0027] PresenceNet creates a decentralized memory layer through: ● Chronological Trails: Marks form time-anchored sequences for personal or group history. ● Ritual Histories: Completed Rituals are verifiable capsules of shared events. ● WaveName Contexts: Sub-contexts organize memory streams under a unified identity. ● Off-Chain Extensions: Hashed links to external storage enable rich dataintegration. 1.11 Preferred Embodiment
[0035] In a preferred embodiment, PresenceNet is implemented on the XRP Ledger. Marks are dust transactions with memo fields encoding ritual_ids. The companion app enables Ritual creation and participation. WaveNames are mapped to XRPL addresses in a registry. Vaults use XRPL multi-signature accounts. Completion Marks trigger asset release or smart contract actions. 1.12 Alternative Embodiments
[0036] The protocol is adaptable to: ● Ethereum, using smart contracts for Ritual evaluation. ● Hedera Consensus Service, with Marks as consensus messages. ● Permissioned ledgers for enterprise use. 1.13 Edge Cases and Scalability
[0037] The protocol handles: ● Invalid Marks: Rejected by ledger consensus. ● Failed Rituals: Notified via the app, with no Completion Mark. ● Scalability: Off-chain referencing and dust transactions ensure low costs.
Claims
Claims 1. A computer-implemented method for cryptographically verifying digital presence and coordinated participation on a distributed ledger network, comprising: a) receiving, at a node of the distributed ledger, a signed presence signal (“Mark”) from a user device, the Mark including a cryptographic signature, a user identifier, and a timestamp; b) recording the Mark as a transaction on the distributed ledger; c) associating the Mark with a predefined coordination structure (“Ritual”) identified by a unique identifier, the Ritual defining a time window and participation rules; d) evaluating, by the node, whether the Ritual’s participation rules are satisfied based on Marks received within the time window; e) upon satisfaction of the participation rules, generating a completion signal (“Completion Mark”) recorded on the distributed ledger and triggering a predefined action, the action including execution of a smart contract or release of digital assets.
2. A system for cryptographically verifying digital presence and coordinated participation, comprising: a) a distributed ledger network comprising a plurality of nodes; b) a user device configured to generate a signed presence signal (“Mark”) including a cryptographic signature, a user identifier, and a timestamp; c) a processor configured to: i) receive the Mark at a node of the distributed ledger; ii) record the Mark as a transaction on the distributed ledger; iii) associate the Mark with a predefined coordination structure (“Ritual”) identified by a unique identifier, the Ritual defining a time window and participation rules; iv) evaluate whether the Ritual’s participation rules are satisfied based on Marks received within the time window; v) upon satisfaction of the participation rules, generate a completion signal (“Completion Mark”) recorded on the distributed ledger and trigger a predefined action, the action including execution of a smart contract or release of digital assets.
3. The method of claim 1, wherein the Mark includes a memo field containing semantic or contextual data, such as a ritual identifier or a hash of metadata.
4. The method of claim 1, wherein the Mark includes a hash pointer to an off-chain data object stored on a decentralized storage system, the hash pointer generated using a SHA-256 algorithm.
5. The method of claim 1, wherein the Completion Mark recorded on a first distributed ledger triggers a follow-up action on a second distributed ledger via a trusted oracle verifying the Completion Mark’s hash.
6. The method of claim 1, wherein the user identifier is a hierarchical identifier (“WaveName”) derived from a base handle, the WaveName being mapped to a unique wallet address, enabling context-specific categorization of presence activity while cryptographic signing authority remains with the base handle.
7. The method of claim 1, wherein the Ritual includes governance rules allowing participants to submit votes as signed Marks, with votes tallied on-chain to determine Ritual outcomes or future parameters.
8. The method of claim 1, wherein the predefined action includes releasing digital assets from a multi-signature vault upon verification of a threshold number of Marks or signatures.
9. The system of claim 2, wherein the user device implements mutuality logic, restricting Ritual invitations to parties with prior interactions or explicit consent. 10.The method of claim 1, wherein the timestamp is verified by the distributed ledger’s consensus mechanism to prevent manipulation.
