Introduction

SafePulse is a trustless, non-custodial smart contract platform designed to power the next generation of digital agreements. It provides the infrastructure for automated, self-executing, on-chain collaborations—enabling users to manage payments, coordinate work, and verify data without ever surrendering control of their assets or private information.

In the modern digital economy, the systems that promise security and reliability often introduce the very risks they aim to solve. Banks, escrow providers, marketplaces, and centralized platforms sit between users and their agreements, imposing rigid rules, high fees, opaque decision-making, and custodial vulnerabilities. These intermediaries have become chokepoints—gatekeepers of value, data, and trust.

SafePulse presents a new paradigm: a world where agreements are borderless, collaboration is automated, and fraud becomes mathematically impossible. Here, sovereignty is restored to individuals and organizations. Here, the contract is not a PDF—the contract is the code.

SafePulse exists to replace fragile intermediaries with verifiable execution, enabling anyone, anywhere, to transact directly with confidence.

Vision

Our vision is to build a world of sovereign agreements—a global environment where interactions between individuals and enterprises are trustless, efficient, and fully programmable. Today, peer-to-peer work—whether freelance tasks, intellectual property transfers, or complex B2B collaborations—is constrained by manual processes, ambiguous terms, and reliance on traditional institutions.

SafePulse aims to make future universal. The logic of cooperation—once enforced by bureaucracy—will now be enforced by transparent, unstoppable code.

Why Now

The digital economy has grown beyond the capabilities of its analog legal frameworks. Remote work, AI, global talent markets, and borderless digital businesses are creating unprecedented demand for secure, programmable agreements.

But traditional systems cannot keep pace:

centralized platforms hold funds and data hostage,
intermediaries charge fees that outstrip transaction value,
cross-border payments remain slow and fragmented,
users depend on institutions that can censor or fail.

At the same time, decentralized technologies—cryptographic signatures, verifiable credentials, decentralized identity, and smart-contract infrastructure—have matured. What was once theoretical is now practical, accessible, and ready for mass adoption.

SafePulse bridges this gap, making advanced cryptographic security and automated agreements usable by anyone with a smartphone.

The Problem

Modern digital interactions—payments, cross-border deals, document verification, and identity—are plagued by structural weaknesses:

1. Fraud & irreversible loss

Crypto markets and digital transactions have seen billions in losses (2023–2025) from investment scams, phishing attacks, and wallet compromises. Users have little recourse once funds are gone.

2. Custody vulnerabilities

Exchange breaches and wallet exploits continue to produce large-scale losses. Models where platforms or apps control user assets create concentrated risk.

3. Slow, costly cross-border settlement

International transactions rely on chains of correspondent banks, compliance checks, and fragmented regulations—adding delays and unpredictable fees.

4. Expensive disputes & fragmented arbitration

Even small international business disputes can balloon into six- or seven-figure legal battles, draining resources and delaying outcomes.

5. Sanctions & AML exposure

Global regulatory frameworks require safe, compliant value transfer. Platforms that fail to prevent illicit use face serious enforcement or shutdown risk.

6. High operational and platform costs

Escrow, arbitration, financial platforms, and marketplaces introduce fees and administrative overhead that make small or cross-border deals impractical.

These problems persist because trust is centralized, execution is manual, and verification is weak.

The Solution

SafePulse is a decentralized, non-custodial smart contract platform designed for automated, programmable agreements. It transforms the way individuals and businesses collaborate by providing the tools to create and execute contracts without intermediaries.

1. Agreements Beyond Payments

Users can create conditional, progressive, revocable, or time-bound contracts—no coding required. Each agreement is fully automated and self-enforcing.

2. Your Keys. Your Assets. Always.

Funds never leave the user’s wallet unless conditions are cryptographically verified. Smart contracts act as neutral escrow agents that unlock assets only when the rules of the agreement are met.

3. Proofs, Not Promises

Users can attach verifiable documents and proofs of verifications and authenticity. The result is tamper-proof evidence tied directly into the agreement’s execution logic.

4. Global, Borderless, and Unrestricted

Anyone can transact using stablecoins or native cryptocurrencies, regardless of geography. There are no mandatory KYC barriers for core functionality and no minimum deal size.

SafePulse turns trust into math—automated, transparent, and unbreakable.

Mission

In an era shaped by digital uncertainty, SafePulse’s mission is to give individuals and organizations the ability to collaborate securely and autonomously. We offer the infrastructure and software application for a new social contract, where:

fairness is enforced by code,
transparency is inherent,
privacy is preserved, and
interactions require no permission from intermediaries.

Our goal is simple: enable people to transact with anyone, anywhere, under rules they choose and technology they trust.

Why SafePulse

SafePulse is built on principles that make it uniquely capable of supporting sovereign digital agreements:

1. Non-Custodial Funds

Users control their assets directly at all times. Payments use native tokens or stablecoins, and funds never pass through platform custody.

2. Non-Custodial Data Architecture

Users store their own files—on decentralized networks or their preferred centralized storage. SafePulse verifies proofs, guaranteeing privacy and autonomy.

3. On-Chain Verification

Every action is cryptographically signed and recorded, creating:

fraud-proof authenticity,
immutable history,
identity flexibility (with DID or full anonymity).

4. Blockchain-Backed Verifiable Credentials

Credentials originate from the user’s wallet and are validated against on-chain data, ensuring trust while preserving privacy.

5. Payments Bound to Agreements

Funds move only when verification proofs and conditions match the contract logic. Your wallet signature is your approval.

6. Progressive Execution

Agreements can be funds progressively in flexible way.

7. Time-Bound Logic

Contracts enforce deadlines, freezing assets or documents during disputes until parties meet their agreed terms.

8. Cost Efficiency

Automated execution removes intermediaries and reduces financial overhead, making global agreements accessible and predictable.

9. No KYC — Privacy by Default

Users may remain anonymous or pseudonymous. Trust is derived from cryptographic proofs, not identity documents.

10. Automated Deployment

With a few taps, anyone can deploy secure smart contracts without writing code—ideal for freelancers, creators, SMBs, and enterprises.

11. Jurisdiction & Responsibility

SafePulse is not a legal or financial intermediary. It provides tools, not adjudication:

users select their own jurisdictions,
disputes freeze assets automatically,
only the involved parties can resolve or complete contracts,
the platform operator has zero access to user funds or private data.

SafePulse stands as a foundational layer for the next generation of digital collaboration: autonomous, verifiable, and truly sovereign.

Concepts

DID

Overview

DID stands for Decentralized Identifier. A DID is a globally unique identifier that allows its controller to prove cryptographic control over it. The entity controlling a DID is called the controller. DIDs are not limited to humans—they can represent organizations, devices, data models, or any abstract entity.

A DID identifies any subject (e.g., person, organization, device, or data model) that the controller decides it identifies.

DIDs are persistent identifiers: even if the associated cryptographic material changes, the DID itself does not need to change. A single DID can have multiple keys, and these keys can be rotated independently. DIDs are typically shorter than the raw public keys they use, making them convenient as stable identifiers.

Each DID is associated with a DID Document, which describes:

The subject of the DID
Public keys (verification methods)
Authentication mechanisms
Authorized controllers
Service endpoints for interaction

DID Methods

A DID method defines how DIDs are created, resolved, and updated. It specifies:

The DID format
Supported operations (key rotation, adding controllers, etc.)
Cryptography and encoding

Here we focus on two DID methods: did:key and did:ethr (ERC‑1056).

did:key

did:key is a purely generative DID method. The DID is deterministically derived from a public key, so there is no registry or blockchain involved.

Syntax

did:key:<multibase-encoded-public-key>

Example:

did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK

The DID itself encodes the key using multicodec and multibase.
There is no need for transactions or on-chain storage.

DID Document

A did:key DID Document includes:

verificationMethod: public key(s) derived from the DID
authentication and assertionMethod: keys authorized for signing and verification
keyAgreement (optional): derived keys for encryption

Example:

{
  "@context": ["https://www.w3.org/ns/did/v1"],
  "id": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
  "verificationMethod": [
    {
      "id": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK#z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
      "type": "Ed25519VerificationKey2018",
      "controller": "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK",
      "publicKeyMultibase": "z<multibase-encoded-key>"
    }
  ],
  "authentication": [
    "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK#z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK"
  ],
  "assertionMethod": [
    "did:key:z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK#z6MkhaXgBZDvotDkL5257faiztiGiC2QtKLGpbnnEGta2doK"
  ]
}

Key points:

The DID is self-controlled (the key is its own controller).
There is no need for registration, and the DID Document can always be derived from the public key.

did:ethr (ERC‑1056)

did:ethr is a DID method anchored on Ethereum using the ERC‑1056 Lightweight Identity standard.

Overview

ERC‑1056 defines an on-chain identity registry that enables:

Adding/removing delegates for signing or key management
Adding attributes such as service endpoints or verification keys
Rotating keys or updating controllers
Tracking actions via Ethereum transactions

The DID method allows DIDs to be self-sovereign while anchored on Ethereum for verification and persistence.

Syntax

did:ethr:<ethereum-address>

Example:

did:ethr:0xAbC123456789abcdef123456789abcdef1234567

For testnets:

did:ethr:goerli:0xAbC123456789abcdef123456789abcdef1234567

DID Document

When resolved, the DID Document includes:

verificationMethod: keys/delegates registered on-chain
authentication: keys authorized for authentication
service: optional endpoints registered as attributes
controller: the Ethereum address or delegates controlling the DID

Example:

{
  "@context": ["https://www.w3.org/ns/did/v1"],
  "id": "did:ethr:0xAbC123456789abcdef123456789abcdef1234567",
  "controller": "did:ethr:0xAbC123456789abcdef123456789abcdef1234567",
  "verificationMethod": [
    {
      "id": "did:ethr:0xAbC123456789abcdef123456789abcdef1234567#delegate-1",
      "type": "EcdsaSecp256k1RecoveryMethod2020",
      "controller": "did:ethr:0xAbC123456789abcdef123456789abcdef1234567",
      "publicKeyHex": "02ab..."
    }
  ],
  "authentication": [
    "did:ethr:0xAbC123456789abcdef123456789abcdef1234567#delegate-1"
  ],
  "service": [
    {
      "id": "did:ethr:0xAbC123456789abcdef123456789abcdef1234567#linked-domain",
      "type": "LinkedDomains",
      "serviceEndpoint": ["https://example.com"]
    }
  ]
}

Key points:

The DID is anchored on-chain, allowing verifiable and auditable changes.
Only delegates or the Ethereum address itself can update keys, controllers, or service endpoints.
Updates require Ethereum transactions, which may incur gas costs.

Comparison: did:key vs did:ethr

Feature	`did:key`	`did:ethr` (ERC‑1056)
Storage	Fully off-chain	On-chain registry (Ethereum)
Cost	Free	Gas required for updates
Key Rotation / Delegation	Not possible (new key = new DID)	Supported via delegates and registry updates
Controller	Implicitly the key itself	Ethereum address or delegates
Service Endpoints	Derived or included in resolved DID	Stored as on-chain attributes
Trust / Decentralization	Fully decentralized	Dependent on Ethereum and registry contract

Summary

did:key is simple and deterministic, ideal for ephemeral or off-chain DIDs.
did:ethr is Ethereum-backed, supporting verifiable, auditable, and self-sovereign identities on-chain.
Both methods resolve to DID Documents that specify keys, controllers, authentication, and services.

Contract DID

Decentralized Identifiers (DIDs) are a cornerstone of identity in decentralized systems, enabling users, organizations, and digital assets to have self-sovereign, verifiable identities. In the context of smart contracts, SafePulse introduces Contract DIDs — a method of assigning globally unique identifiers to deployed contracts, registries, and other on-chain entities, while maintaining privacy and controlled access.

Contract DIDs serve as cryptographic handles that represent deployed contracts or registries on a blockchain. They allow users to reference, interact with, or verify these entities without exposing sensitive internal data.

Structure of Contract DID

A Contract DID is constructed in the following format:

did:ethr:<chain-id>:<contract-id-hex>[;key=<cipher-key-hex>]

did:ethr – Indicates that this is an Ethereum-compatible DID.
– The chain ID where the contract is deployed.
– The unique identifier of the deployed contract in hexadecimal format.
key= (optional) – A private cipher key used for securing contract data. This key must never be shared with unrelated parties, as possession allows decryption of sensitive contract information.

Example:

did:ethr:1:0x4b3c7a9e5f2d3a6b8c9d0e1f2a3b4c5d6e7f8a9b;key=0a1b2c3d4e5f67890123456789abcdef

In this example:

The contract is deployed on Ethereum mainnet (chain-id 1).
The contract’s address is 0x4b3c7a9e5f2d3a6b8c9d0e1f2a3b4c5d6e7f8a9b.
A private cipher key is associated to encrypt sensitive contract state.

Registry DID

Contracts often interact with registries — on-chain data structures that map, verify, or index other contracts, users, or assets. Registry DIDs are assigned in a simpler format to reference these registries:

did:ethr:<chain-id>:<32byte-hash-hex>

– Blockchain network where the registry resides.
<32bit-hash-hex> – A unique hash representing the registry or dataset.

Example:

did:ethr:5:0x9f8a7b6c5d4e3f2a1b0c1d2e3f4a5b6c7d8e9f0a1b2c3d4e5f6a7b8c9d0e1f2

Registries can store mappings of users to their Contract DIDs, smart contract metadata, or verifiable records, enabling tamper-proof lookup, automated verification, and secure referencing.

Usage and Privacy Considerations

Contract DIDs allow users to interact with contracts securely by referring to a permanent on-chain identifier without needing the raw contract address.
Sensitive data inside contracts or registries can be encrypted with the private key parameter (key=<cipher-key-hex>).
Only authorized parties should be given access to the cipher key; sharing it externally may compromise the security of encrypted contract data.
Users can query registries using Registry DIDs to discover or verify associated Contract DIDs, enabling decentralized discovery while maintaining privacy.

Key Benefits

Decentralized Reference: Provides a global, verifiable identifier for smart contracts and registries.
Secure Access Control: Optional cipher keys allow encrypted contract states to remain confidential.
Tamper-Proof Registry Mapping: Registry DIDs provide a verifiable method to index contracts and users.
Interoperability: Compatible with Ethereum and EVM-based chains, making Contract DIDs usable across multiple networks.

This structure ensures that SafePulse users can maintain self-sovereign identity for contracts and registries, interact securely with encrypted smart contracts, and trust the authenticity of registry data without relying on centralized services.

Elysium Protocol

The Elysium Protocol represents the premium Meta protocol within the SafePulse ecosystem. While SafePulse itself is designed as a fully non-custodial infrastructure, Elysium provides an exclusive high-tier environment for users who require maximum security, operational sovereignty, and access to advanced features.

Unlike standard SafePulse services, Elysium is reserved exclusively for Elysian Accounts, which are verified through the possession of Flarion Tokens. This architecture ensures that access, permissions, and operations are fully tied to token ownership, granting users unparalleled control over their interactions.

Elysian Accounts: The Flarion Token Access Standard

An Elysian Account is the designation for authenticated holders of Flarion Tokens (FLR). Flarion Tokens are:

Limited-supply ERC-20 tokens
Non-tradable and not listed on exchanges
Functionally exclusive, granting access to premium features

Key Features:

Transferable Access
- Ownership of a Flarion Token directly grants access to Elysium services.
- Transferring the token instantly transfers account privileges, making access fully token-based.
Access Standard
- To maintain an Elysian Account, a minimum threshold of tokens must be held.
- This ensures commitment to the ecosystem and manages access to the most advanced platform services.
Explicit Payment Control
- Flarion Tokens do not automatically pay for services.
- Users must explicitly approve any token usage for transactions, maintaining full control over assets.

Key Components of Elysium Protocol

Elysium extends the capabilities of SafePulse through a set of premium tools and infrastructure, designed to support high-security, high-value, non-custodial operations.

1. The Pledge Contract

A high-sovereignty smart contract system that ensures accountability through verifiable security stakes.
Directly integrates with the Verifiable Document Service to automate contract execution based on verified data.
Conditional execution ensures that asset or payment release is only triggered upon verified approval, reducing risk and enforcing trustless automation.

2. Verifiable Document Service

Provides advanced document integration and verification for Elysian Accounts.
Supports binding external legal documents and institutional credentials to smart contracts.
Ensures documents act as mandatory triggers for contract execution, enhancing control and cryptographic auditability.

3. Rune

Rune is a premium execution asset exclusive to Elysian Accounts.
Powers advanced services including: pledge contracts, document processing, and high-value interactions.
Enhances security, integrity, and tamper-proof execution for all premium operations.
Provides maximum user sovereignty, ensuring that users maintain full control over complex contracts.

Flarion Token (FLR)

Non-financial ERC-20 token
Serves as the access credential to Elysium services.
Intentionally non-tradable, ensuring that access is utility-focused, not speculative.
Grants access only; public users without FLR can still use open services but cannot access Elysium services.

Rune (RUNE)

Internal transactional and execution token for performing high-value on-chain actions.
Non-tradable, operates exclusively within the SafePulse ecosystem.
Only Flarion holders can use Rune to execute premium services, ensuring authenticated, secure, and auditable operations.

Rune Token

Rune (RUNE) is the execution token within the SafePulse Elysium ecosystem, used exclusively for performing premium on-chain operations. It powers high-security actions such as executing Pledge Contracts, processing Verifiable Documents, and other Elysium services. Unlike traditional tokens, Rune is non-tradable and confined to internal platform use, ensuring that its value is functional rather than financial.

RUNE acts as a transactional asset, providing a secure mechanism to perform critical operations while maintaining data integrity, cryptographic assurance, and tamper-proof execution. Access to Rune-powered services is limited to Flarion Token holders, ensuring that only verified users can engage in high-value interactions.

By separating access credentials (FLR) from execution capabilities (RUNE), SafePulse achieves a robust dual-token model. This design provides maximum user sovereignty, enabling individuals to control both who can access services and how their operations are executed, all without sacrificing security or trustless automation. RUNE ensures that premium transactions are authenticated, secure, and auditable, providing a foundation for high-stakes, non-custodial operations.

Flarion Token

The Flarion Token (FLR) is a non-financial, ERC-20 utility token that functions as the key to access Elysium Protocol’s services. Unlike typical blockchain tokens, FLR is not designed for trading or speculation. Instead, it serves purely as a access credential, ensuring that only authenticated users can access high-tier features within the SafePulse ecosystem.

FLR is issued in limited supply. Holding a Flarion Token designates the user as an Elysian Account, granting privileges such as access to Elysian section of ecosystem, the Pledge Contract system, the Verifiable Document Service, and the Rune execution suite.

The token provides transferable access: ownership of FLR directly correlates with Elysian Account privileges. When a token is transferred to another wallet, the new owner immediately receives full access rights, ensuring a flexible and user-sovereign access model. Importantly, FLR is not automatically consumed for payments. Users must explicitly approve its use for any transaction or service access within Elysium, giving them absolute control over their assets.

Through FLR, the SafePulse ecosystem ensures a secure, controlled, and high-value user experience, where access to the most sophisticated services is token-gated and permissioned, rather than open to public or speculative trading.

Decentralized Storage

Decentralized storage refers to a method of storing digital data across a distributed network rather than on centralized servers. By leveraging blockchain and peer-to-peer technologies, decentralized storage ensures data immutability, censorship resistance, and long-term availability, empowering users with full control over their data without relying on any single authority.

In the SafePulse ecosystem, decentralized storage plays a critical role in storing verifiable documents, smart contract references, and other high-value data assets, enabling secure and verifiable interactions between users, smart contracts, and third parties. Two of the most widely used decentralized storage protocols are Arweave and IPFS (InterPlanetary File System).

Arweave

Arweave is a permanent, blockchain-backed storage protocol designed for long-term, immutable data storage. Data uploaded to Arweave is stored in a distributed network and guaranteed to persist forever through a one-time upfront fee. Each piece of data stored is assigned a unique transaction ID (TxID).

The TxID serves as a permanent reference to the stored data, allowing it to be retrieved, verified, and referenced by smart contracts, applications, or users at any time. Arweave’s storage model ensures that once data is uploaded, it cannot be altered or deleted, providing tamper-proof auditability critical for legal, institutional, and contractual documents.

Arweave employs a blockweave structure, an evolution of traditional blockchain, which links data together using a combination of cryptographic proofs and consensus mechanisms. This ensures both data permanence and efficient network scalability.

IPFS (InterPlanetary File System)

IPFS is a peer-to-peer distributed file system that addresses data by its content hash rather than its location. Unlike centralized servers where files are located at a fixed URL, IPFS retrieves data from any node storing that content, making the system resilient and decentralized.

Every file or folder uploaded to IPFS is assigned a Content Identifier (CID), a cryptographic hash of the file’s contents. The CID ensures integrity, meaning any modification to the file results in a different CID. This makes IPFS ideal for verifiable, tamper-resistant references in decentralized applications.

IPFS operates with a distributed hash table (DHT) to locate nodes storing the requested content. When a user requests a file via its CID, the network identifies peers hosting the file and retrieves it efficiently from multiple sources, ensuring redundancy and fault tolerance. Unlike Arweave, IPFS data persistence depends on pinning services or active hosting, as files may not remain available unless intentionally preserved.

Identifiers: Arweave TxID vs IPFS CID

Arweave TxID: A unique transaction identifier that permanently links to stored data on the Arweave network. Once uploaded, data associated with a TxID is immutable and guaranteed to persist indefinitely.
IPFS CID: A content-based cryptographic hash that identifies a file by its content. Changing the file changes its CID. Data availability depends on nodes hosting or pinning the content.

By combining Arweave and IPFS, SafePulse ensures both permanent and distributed storage options, allowing users to store critical documents securely, reference them in smart contracts, and verify them without relying on any centralized system. These protocols are essential for tamper-proof operations, verifiable credentials, and long-term digital record integrity.

Services

Payment & Agreement Layer

Introduction

The Payment & Agreement Layer is the foundation of SafePulse’s trustless financial ecosystem. It provides secure, automated, and transparent mechanisms for managing funds, contracts, and conditional agreements between parties — all without relying on intermediaries or custodians.

This layer is designed for a wide spectrum of users:

Individuals: Freelancers, gig workers, and peer-to-peer (P2P) payments
Businesses & Enterprises: Small B2B contracts, milestone-driven projects, and enterprise workflows

Every service in this layer leverages on-chain smart contracts to provide trust, security, and automation, ensuring that agreements execute exactly as defined and that funds are handled safely.

Layer Overview

Layer Name	Description	Services
Payment & Agreement Layer	Provides secure, automated escrow and contract-based payment mechanisms.	Escrow, Pledge Contracts

Key Objectives of the Layer:

Enable trustless, high-value transactions
Protect participants with automatic enforcement
Facilitate milestone-based and phased payments
Reduce reliance on intermediaries or centralized authorities

Services in the Payment & Agreement Layer

1. Escrow

Purpose: Escrow provides a trustless, non-custodial payment mechanism that securely holds funds until agreed-upon conditions are fulfilled. It is ideal for high-value transactions, protecting both buyers and sellers while remaining cost-effective compared to Pledge Contracts.

Key Features:

Flat deposit fee + 1% withdrawal fee
Supports revocable, time-bound, and rollback agreements
On-chain enforcement ensures transparency and trust
High-value capable, yet simpler and cheaper than Pledge Contracts
Managed fully via the SafePulse Wallet

How It Works:

Sender deposits funds into the Escrow smart contract
Funds remain locked until the recipient fulfills the agreement
Upon completion, buyer release funds and let seller to withdraw funds
Conditional rollback or cancellation is supported if obligations are unmet

Use Cases:

Freelance / Gig Work: Client deposits → Freelancer delivers → Funds released
P2P Item Purchases: Buyer deposits → Seller delivers → Buyer verifies → Funds released
High-Value B2B Transactions: Secure large payments for prototypes, consulting sessions, or licensing deals
Deposits, Reservations, and Rentals: Automatically refundable if conditions fail

Benefits:

Trustless transactions without intermediaries
Cost-effective for high-value and regular payments
Automated enforcement via smart contracts
Secure, transparent lifecycle

2. Pledge Contracts

Purpose: Pledge Contracts extend escrow functionality to larger, progressive, or complex agreements, making them ideal for enterprise-grade projects and high-value contracts requiring multiple payments on agreement, verification, or document linkage.

Key Features:

Milestones & partial payouts — flexible progressive payments, multiple payment linkage
Revocable & rollback options for flexible risk management
Document binding — sync with document, automated on-chain verification and authentication, ensures enforceability and auditability
One-time creation fee with 0% ongoing fees
Example: 33 Rune per contract deployment
Fully integrates with Verifiable Documents, syncing payout conditions with document status

How It Works:

Contractor deploy verifiable document contract and enter document contract DID for pledge contarct creation
Funds are deposited into the Pledge Contract smart contract
As each parties verify document, funds are released automatically
All contract terms, payments, and document interactions are on-chain and cryptographically secured and auditable

Note: Pledge contract is an sovereign contract and can operate without linking to verifiable document contract

Use Cases:

Enterprise Software Development: Payment released as each development milestone is completed
Licensing or Procurement: Funds unlocked when contractee verify document and approve delivery of service
Complex Freelance Projects: Large creative or consulting projects with multi-phase deliverables
Document-Linked Agreements: Synchronize payments with signed verifiable documents to ensure accountability
Cross-Border B2B Deals: Ensures high-value payments execute reliably across jurisdictions

Benefits:

Flexible agreements: Milestone-based, partial payouts, rollback support
Revocable & secure: Parties retain control, fully enforced on-chain
Document binding: Legal and audit-ready, linked to verifiable documents
Cost-efficient: One-time creation fee for long-term security
Ideal for heavy payments and complex workflows

Layer Benefits Summary

Service	Key Advantages
Escrow	Trustless, high-value capable, automated P2P payments, low fees
Pledge Contracts	Progressive, revocable, document-linked agreements, suitable for large payments

Overall Layer Benefits:

Trustless Payments: Reduces risk across all transaction sizes
Automation: Smart contracts manage enforcement automatically
Flexibility: Supports simple to complex agreements, individual to enterprise
Security & Transparency: Immutable, auditable on-chain contracts
Cost Efficiency: Cheaper and faster than traditional intermediaries

The Payment & Agreement Layer is the backbone of SafePulse’s ecosystem. Escrow for high-value payments and Pledge Contracts for flexible, milestone-driven agreements provides a secure, automated, and transparent financial infrastructure that empowers individuals, businesses, and enterprises to transact confidently across borders and industries.

Document & Verification Layer

Introduction

The Document & Verification Layer enables secure, tamper-proof, and verifiable document management within the SafePulse ecosystem. It empowers individuals, businesses, and enterprises to create, verify, and timestamp digital documents on-chain, ensuring authenticity, integrity, and enforceability.

This layer is ideal for:

Legal and compliance documentation
Intellectual property proof and timestamping
Smart-contract-linked document verification
Auditable, verifiable documents for enterprise workflows

All services in this layer leverage on-chain proof mechanisms and decentralized storage to guarantee security, transparency, and user control.

Layer Overview

Layer Name	Description	Services
Document & Verification	Provides secure, verifiable, and tamper-proof document management and on-chain proof services.	Verifiable Documents, Document Registry

Key Objectives of the Layer:

Ensure document authenticity and integrity
Provide revocable document options
Offer cost-effective proof of document existence
Integrate documents seamlessly with smart contract agreements

Services in Document & Verification Layer

1. Verifiable Documents

Purpose: Create secure, tamper-proof, revocable, and blockchain-backed document verification contract, with optional linking to smart contracts for automated enforcement.

Key Features:

Revocable and contract-linkable documents
Stored locally or in decentralized storage (IPFS, Arweave, or centralized hosts)
On-chain proof of authenticity
Automated On-chain cryptographic verification
Example deployment: 9 Rune per document

How It Works:

User strore thir document, enter identifier od document and creates a Verifiable Document contract.
Document metadata and proof are stored on-chain; content remain off-chain but verifiable.
Document can be linked to Pledge Contracts for automated verification and payment syncing.

Use Case Example:

A company issues a compliance document to a vendor. The document is manageable and verifiable on-chain, and can be used to trigger contract milestones or payment releases.

Benefits:

Tamper-proof and secure – Blockchain ensures integrity
Contract integration – Links directly to Pledge Contracts for automated verification and payment syncing
Revocability – Documents can be revoked by issuers and controllers of contract if needed

Drawbacks:

Requires management of decentralized storage
Deployment may incur Rune token costs

Related Services / Cross-links:

Pledge Contract: For milestone-based contracts linked to documents and secure payments tied to verified documents

2. Document Registry

Purpose: Provide low-cost, on-chain proof of document existence for timestamping, authorship claims, and IP verification.

Key Features:

Lightweight and public registry
Cost-effective solution compared to Verifiable Document contract
Immutable on-chain cryptographic proof and automated on-chain document verification

How It Works:

User store docuemnt and enter document identifier and registers the document.
Data will be registered in SafePulse document registry smart contract and will be verifiable and managable.
Anyone can verify the document’s existence and authenticity.

Use Case Example:

An author timestamps a manuscript’s hash to prove authorship. Later, if needed, they can show the timestamped hash to assert intellectual property rights.

Benefits:

Cost-effective – Minimal on-chain storage fees
Public verification – Anyone can verify existence and timestamp
Lightweight – Ideal for frequent document verification
Immutable proof – On-chain records cannot be tampered with

Drawbacks:

Does not store full document content
Limited functionality compared to Verifiable Documents

Layer Benefits Summary

Service	Key Advantages
Verifiable Documents	Tamper-proof, revocable, contract-linked documents
Document Registry	Lightweight, cost-effective, immutable proof of existence

Overall Layer Benefits:

Trustworthy Documents – On-chain verification ensures authenticity
Contract Integration – Documents can trigger or validate on-chain
Cost Efficiency – Public registry reduces overhead for proofs
Auditability – Immutable on-chain records support compliance and legal needs
Revocability – Documents can be suspended or revoked if necessary

The Document & Verification Layer provides SafePulse users with secure, verifiable, and blockchain-backed document services. By combining Verifiable Documents and a lightweight registry, this layer ensures trust, proof of authenticity, and enforceability, forming a reliable foundation for compliance, legal, and IP workflows.

Identity Layer

Introduction

The Identity Layer in SafePulse provides self-sovereign, blockchain-backed digital identity and credentials. It enables users, businesses, and organizations to verify identity and credentials securely, privately, and without reliance on centralized authorities.

This layer is designed for:

Individuals: managing personal identity and credentials
Organizations: verifying employee, partner, or vendor credentials
Developers: integrating decentralized identity and verifiable credentials into smart contract workflows

All services in this layer are built on open standards to ensure interoperability, privacy, and security.

Layer Overview

Layer Name	Description	Services
Identity Layer	Provides self-sovereign identity and verifiable credentials for secure, decentralized verification	Decentralized Identity (DID), Verifiable Credentials (VCs)

Key Objectives of the Layer:

Provide user-controlled, portable digital identities
Enable secure verification without centralized intermediaries
Support verifiable presentations for privacy-preserving data sharing
Integrate seamlessly with SafePulse’s contracts and document services

Services in Identity Layer

1. Decentralized Identity (DID)

Purpose: Enable lightweight, self-sovereign digital identity that is fully user-controlled, portable, and privacy-preserving.

Key Features:

Based on ERC-1056 Ethereum standard
Fully user-controlled – no centralized authority required
Portable
Compatible with W3C verifiable credentials v2.0
Secure and cryptographically verifiable

How It Works:

User creates a DID linked to their blockchain wallet.
The DID stores essential metadata and public keys/delegates on-chain.
Users control access to their identity data through wallet authorization.
Can be used for verifying agreements, documents, and interacting with services.

Use Case Example:

A freelancer registers a DID to authenticate themselves on multiple platforms, providing a verifiable, tamper-proof identity without relying on centralized providers.

Benefits:

Self-sovereignty – full user control of identity
Interoperability – compatible with decentralized apps and smart contracts
compliance – uport integration
Security – cryptographic proof of identity, self identifying with EOA's

2. Verifiable Credentials (VCs)

Purpose: Provide wallet-first, blockchain-backed digital credentials that are tamper-proof, privacy-preserving, and verifiable.

Key Features:

Compliant with W3C Verifiable Credentials v2.0
Blockchain-backed and tamper-proof
Supports verifiable presentations
Can represent education certificates, licenses, compliance documents, or professional credentials

How It Works:

Credential issuer creates a verifiable credential for a user.
Credential metadata and proof are recorded on-chain.
User stores credentials in their wallet and selectively shares informations and proofs with third parties.
Recipients can verify authenticity without needing direct access to the issuer.

Use Case Example:

A university issues a blockchain-backed diploma to a graduate. The graduate can present proof to employers without exposing sensitive information, and employers can independently verify its authenticity.

Benefits:

Trustless Verification – verifiable without a central authority
Privacy-Preserving Sharing – selective disclosure for sensitive data
Tamper-Proof – blockchain ensures integrity and immutability

Layer Benefits Summary

Service	Key Advantages
Decentralized Identity (DID)	Self-sovereign, portable, secure identity
Verifiable Credentials (VCs)	Blockchain-backed credentials with selective disclosure

Overall Layer Benefits:

User-Controlled Identity – Full autonomy over personal or organizational identity.
Secure Verification – Blockchain ensures authenticity and prevents tampering.
Privacy & Selective Sharing – Share only what is necessary.
Integration with SafePulse Services – Identity and credentials can seamlessly interact with payment, document, and content layers.
Standardized & Interoperable – Built on ERC-1056 and W3C standards for broad compatibility.

The Identity Layer empowers users with trustworthy, self-sovereign digital identity and credentials, enabling secure, verifiable interactions across SafePulse’s ecosystem. By combining DIDs with verifiable credentials, SafePulse supports privacy-preserving, interoperable, and blockchain-backed identity solutions suitable for individuals, businesses, and developers alike.

Tutorials

Verifiable Document

Overview

Verifiable Documents allow users to create tamper-proof, document verification contract that let documents be stored locally or on decentralized storage networks, such as IPFS or Arweave. Each document can be anchored on-chain, providing an immutable proof of authenticity. Documents can also be linked to Pledge Contracts, enabling automated enforcement.

All operations are executed via the SafePulse Wallet, ensuring self-sovereign, local execution.

Purpose / Context

Problem: Organizations and individuals often require tamper-proof documents for legal, compliance, or intellectual property purposes. Centralized solutions carry the risk of modification, loss, or lack of verifiability.

Solution: SafePulse’s Verifiable Document service allows users to:

Anchor documents on-chain for immutability
Link to Pledge contracts for enforceable workflows
Maintain full self-sovereign control over document storage and access

This ensures documents are trustworthy, verifiable, and usable in automated payment or contract workflows.

Features

Decentralized storage options: IPFS, Arweave, or centralized host with direct download
Revocable documents: Documents can be suspended or revoked if needed
Linked to Pledge Contracts: Automatically enforceable within
On-chain anchoring: Ensures tamper-proof on-chain verification of authenticity

Step-by-Step Tutorial

Prerequisites

SafePulse Wallet installed
Active EOA (Externally Owned Account) with subscription plan or usage credit
Issuer/Creator DID: an key DID (did:key) or an ERC-1056 DID with issuer key as its Delegate
Network tokens (e.g., Rune) to pay deployment fees

Steps

Upload your file to one of:
- IPFS
- Arweave
- Centralized host (direct download link)
Tap Verifiable Document
Copy the file link/IPFS-CID/Arweave Transaction Id
Fill in the creation form:
- Paste the refrence identifier (file link/IPFS-CID/Arweave Transaction Id)
- Choose blockchain network
Tap Create (top of screen)
Confirm the on-chain transaction
After minting, go to History
Locate the document history record
From More, select Initialize and Setup and confirm initialization transaction
Share the Verifiable Document DID with relevant parties

Use Cases / Examples

Education Certificates: Universities issue tamper-proof diplomas verifiable by employers
Contract Enforcement: Attach documents to a Pledge Contract to enforce milestone payments
Intellectual Property: Timestamp creative works or research papers to prove authorship
Legal Agreements: Ensure critical agreements are immutable and verifiable by all parties

Benefits & Drawbacks

Benefits:

Tamper-proof and auditable
Integrates with SafePulse contracts for automated enforcement
Full control over document storage and access

Drawbacks:

Requires management of decentralized storage
Deployment may incur Rune token costs (can be created only by elysium members/elysian accounts)

Pledge Contract: For milestone-based contracts linked to documents/secure payments tied to verified documents

Notes & Tips

Confirm your document is uploaded correctly before creating a Verifiable Document
Keep a local backup in addition to decentralized storage
Always link documents to contracts where verification is required for automated enforcement

Pledge Contract

A hybrid physical–digital contract framework with flexible milestone enforcement, verifiable documents, and on-chain guarantees.

Overview

A Pledge Contract is a decentralized agreement between two parties where all obligations, milestones, and deliverables are digitally anchored. It serves as a self-executed contract where every participant signs with their private key, ensuring integrity, accountability, and traceability without relying on centralized intermediaries.

A Pledge Contract may optionally include:

Milestones multiple Pledge Contracts can be linked to one document *can use diffrent coins for payments, *using different parties for each payments from parties and controllers at Verifiable Document
Verifiable Documents for document verifiacation and authentication and document binding
Auto-updating statuses triggered by contract actions

Context & Problem

The Problem

Traditional contracts lack:

Automatic enforcement
Transparency across parties
Immutable records of milestone progress
Easy verification of terms or deliverables
Integrated payment guarantees

They often require third-party mediators, which increases cost, reduces trust, and slows execution.

The Solution

SafePulse’s Pledge Contract provides:

Immutable, on-chain agreements verified by participants' cryptographic signatures
Linked deliverables, such as Verifiable Documents
Flexible Milestone-based workflows for structured work delivery and progressive payments
Automated status updates to reduce manual coordination

This creates a trustless contracting system suitable for digital commerce, services, creative work, licensing, and more.

Key Features

1. Multi-party Signing

Each participant signs the contract with their private key, ensuring authenticity and non-repudiation.

2. Document Integration

Attach Verifiable Documents as deliverables, guidelines, licenses, terms, or specifications.

3. Milestone Enforcement

Be used as Flexible milestones for progressive payments.

4. Multiple Payments on One Document

One Verifiable Document can be used for multiple Pledge Contracts, with diffrent parties and multiple payment process.

5. Full Status Lifecycle

Automatically transitions through states such as:

Pending
Active
Executed
Disputed
Completed
Canceled

6. Wallet-First Operation

Everything is controlled in the SafePulse Wallet — no external software required.

Step-by-Step Tutorial

Prerequisites

SafePulse Wallet installed
Active subscription or usage credits
Issuer/Creator DID: an key DID (did:key) or an ERC-1056 DID with issuer key as its Delegate
Network tokens for contract deployment
A Verifiable Document for document-bound payments

A. Creating a Pledge Contract

Tap Pledge Contract
Fill in contract details:
- Seller/Contarctor/Issuer DID
- Contractee/buyer address
- Network and Token
- Enter Verifiable Document Contract DID (optional)
Tap Create and Approve transaction
After minting, go to History
Locate the document history record
From More, select Initialize and Setup and confirm initialization transaction

Notes:

oposite the Escrow, Pledge Contract should be created by seller and its DID should be shared with parties, whole process will be done on pledge contracts.
Important Note: before initialization contract controller stays empty so INITIALIZE CONTRACT QUICKLY AFTER DEPLOYMENT

Go to History
Find Issue record related to your contract
On More tap on "Show Transaction Info"
Copy DID

Pledge Contract Status Guide

Status	Meaning
Pending	Contract created but not yet Accepted by Seller
Active	Seller Accepted agreement
Executed	Terms fulfilled
Completed	All deliverables + linked workflows finished, Buyer approve fulfillment
Disputed	A party flagged an issue requiring resolution, funds won't release
Canceled	Contract voided before activation or execution, seller rejected the agreement

Pledge Contract Status Guide

1. `pending`

Meaning: Service is initialized but not started yet.

Entered by: Default state.
Who can act: Seller (issuer).
Transitions to:
- active → seller starts service
- canceled → seller cancels before starting
Permissions:
- ✅ Rollback → buyer
- ✅ Cancel → seller
- 🚫 Withdraw

2. `active`

Meaning: Service has started and is ongoing.

Entered by: Seller starts service.
Who can act: Seller (execute), Buyer (dispute).
Transitions to:
- executed → seller executes service
- disputed → buyer disputes service
Permissions:
- 🚫 Rollback (unless expired)
- 🚫 Cancel
- 🚫 Withdraw

3. `executed`

Meaning: Seller marked service as delivered.

Entered by: Seller executes service.
Who can act:
- Buyer → confirm (completed)
- Buyer → dispute (disputed)
- Seller → withdraw after 5 days post-expiration (if no dispute)
Transitions to:
- completed → buyer confirms delivery
- disputed → buyer disputes service
Permissions:
- 🚫 Rollback
- ✅ Withdraw (after 5 days if no dispute)
- 🚫 Cancel

4. `disputed`

Meaning: Buyer raised a dispute.

Entered by: Buyer disputes service.
Who can act:
- Buyer → complete it
- Seller → cancel it
Transitions to:
- completed → by buyer
- canceled → by seller
Permissions:
- 🚫 Rollback
- 🚫 Withdraw
- 🚫 Cancel

5. `completed`

Meaning: Buyer confirmed delivery and acceptance.

Entered by: Buyer completes service.
Who can act: Seller → withdraw.
Permissions:
- ✅ Withdraw (seller)
- 🚫 Rollback
- 🚫 Dispute
- 🚫 Cancel

6. `canceled`

Meaning: Seller canceled service before completion.

Entered by: Seller cancels.
Who can act: Buyer → rollback.
Permissions:
- ✅ Rollback (buyer)
- 🚫 Withdraw
- 🚫 Execute/Complete

📌 Notes

Dispute only possible from active or executed.
Rollback allowed only when:
- State is not active, or expired
- State is not executed, completed, or disputed
Withdraw allowed only when:
- State is completed, or
- State is executed and 5 days passed with no dispute
No transitions allowed from completed, disputed, or canceled unless manual.
🔐 Funds are locked until customer approves completion.

📎 Linked Document Rules

If linked to a Verifiable Document:

For executed → seller must sign on-chain in the Document Contract.
For completed → buyer must sign on-chain in the Document Contract.
For canceled → Document Contract must be in suspended or revoked status.

Real-World Use Cases

1. Freelance or Service Agreements

Designer and client define milestones
Verifiable Document details requirements
Client deposits funds in escrow
Each milestone is approved before payment is released

2. Licensing & Intellectual Property

A creator issues rights via a Verifiable Document
Licensee accepts terms through contract signing
Usage rights become provable on-chain

3. B2B Supplier Agreements

Milestones tied to shipment or delivery phases
Locks funds and payments till conditions met
Each step verified for transparency

Benefits & Drawbacks

Benefits

Proven authenticity through cryptographic signatures
Protects both parties via escrow-secured terms
Transparent progress tracking
Immutable record of obligations and deliverables
Zero reliance on centralized intermediaries

Drawbacks

Requires users to understand decentralized storage
On-chain actions incur gas fees
All parties must use SafePulse Wallet for consistency

Verifiable Documents — attach deliverables, terms, proofs, secure payment workflows linked to contract milestones,timestamp documents referenced by contract

Tips & Best Practices

Always attach a Verifiable Document describing scope and expectations
Break work into seperated milestones contracts with required tokens to reduce disputes
Use escrow for high-value or high-risk agreements
Keep communication in-app to maintain transparency

Escrow

A trustless, non-custodial payment safeguard for peer-to-peer and high-value transactions.

Overview

SafePulse Escrow is a trustless, non-custodial onchain escrow service that securely locks funds until both parties meet agreed-upon conditions. Designed for buyers, sellers, freelancers, enterprises, and service providers where trust and protection are critical.

With transparent fees and guaranteed neutrality, SafePulse Escrow eliminates fraud risks and intermediaries — delivering a secure, automated environment for global payments of any size.

Context & Problem

The Problem

Digital agreements — whether between individuals or businesses — frequently face:

Payment fraud
Delivery disputes
Chargebacks
Unenforceable promises
Lack of trusted middlemen
High cost of middlemen
No protection for large-value deals
Opaque transaction processes

Centralized escrow alternatives exist, but they introduce:

High fees (often 2–10%+)
Custodial risk (fund freezing, loss, shutdowns)
Slow and costy dispute resolution
Geographic restrictions
Risk of platform censorship

For large-value or cross-border transactions, these risks become even more severe.

The Solution

SafePulse Escrow replaces intermediaries with automation, transparency, and cryptography:

Smart contracts hold funds securely
Neither SafePulse nor any third party can access funds
Status is always transparent to both parties
Options for rollback, cancellation, and freeze under safe conditions and only by parties

This makes it suitable for everything from small digital engagements to high-value deals.

Use Cases

1. High-Value Transactions

Manufacturing orders, consulting retainers, licensing fees

Securely holds large sums
Prevents fraud or late delivery

2. Freelance / Gig Work

Design, development, marketing, writing, auditing

Client deposits funds in escrow
Freelancer completes work
Payment released on approval

3. P2P Item Purchases

High-value goods, collectibles, hardware, digital assets

Buyer locks payment
Seller delivers
Buyer verifies and releases

4. Deposits, Rentals, Prepayments

Real estate, equipment rentals, agency pre-bookings

Supports refundable deposits
Automatically rolls back if conditions fail

5. Content & Digital Sales

Protects both sellers and buyers

Key Features

1. Trustless, Non-Custodial Fund Holding

Funds are locked in smart contracts — not controlled by SafePulse or any third party.

2. Safe for High-Value Transactions

Smart contracts guarantee:

No third-party access
No interference
No misappropriation

3. Revocable, Time-Bound, and Rollback Support

Automated safety mechanisms for any agreement size.

4. Simple Fee Structure

Flat deposit fee (pays in network native token)
1% withdrawal fee
No subscriptions or access token required

Cheaper and safer than centralized escrow — even for high-value deals.

5. Complete Status Transparency

Escrow lifecycle:

Open
Freeze
Release
Cancel

Every party always knows the exact state.

6. Wallet-First, On-Device Execution

All actions happen through the SafePulse Wallet — intuitive, secure, and verifiable.

Escrow Lifecycle (Status Guide)

Status	Meaning
Open	token deposited, waiting for release/freeze/cancel
Freeze	Funds locked securely inside smart contract until expiration time
Release	Funds released and allow recipient to withdraw
Cancel	Allow sender/buyer/contractee to refund

Step-by-Step Tutorial

Prerequisites

SafePulse Wallet installed
Gas tokens available
Payment token approved for use

A. Approving Tokens for Escrow

Open the escrow record
Tap Approve Token
Confirm the transaction

Once approved, the deposit can be made.

B. Creating an Escrow Deposit

At organize section onder title of escrow Tap Approve
Enter:
- Recipient address
- Amount
- expiration date
Select network and token
Tap Deposit
Escrow appears in History
Share Deposit DID with your party

C. Releasing or Canceling

Release

Used when obligations are met:

Work delivered
Product received
Agreement fulfilled

User taps Release → Confirm.

Cancel

Used when:

Conditions fail
Deadlines pass
Mutual cancellation occurs

Funds are returned to the sender.

Escrow Contract Status Guide

1. `open`

Meaning: Funds deposited, escrow active.

🚫 Withdraw
✅ Rollback → allowed 5 days after expiration

2. `freeze`

Meaning: Escrow blocked.

🚫 Withdraw
🚫 Rollback

3. `release`

Meaning: Escrow released to seller.

✅ Withdraw (seller)
🚫 Rollback

4. `cancel`

Meaning: Escrow canceled.

🚫 Withdraw
✅ Rollback (buyer)

Real-World Examples

1. High-Value Contract Payment

$50,000 locked → Developer delivers → Company verifies → Funds released.

2. Hardware Purchase

Buyer deposits → Seller ships → Buyer confirms → Funds released.

3. Security Deposit

Tenant deposits → No issues → Deposit returned upon cancellation.

Benefits

Safe for high-value and cross-border payments
Non-custodial and censorship-resistant
Transparent and automated lifecycle
Eliminates fraud and trust issues
Simple and predictable costs
Integrates with Pledge Contracts and Paywalls

Drawbacks

Requires blockchain familiarity
Both parties must manage wallets
No centralized party can force a resolution

Document Registry

A lightweight, low-cost, onchain proof-of-existence system for timestamping documents, research, IP, and digital work.

Overview

The Document Registry provides a fast, cost-efficient and immutable method to prove that a document existed at a specific point in time. Instead of storing the full file onchain, SafePulse only records the hash, making the process cost-efficient while maintaining strong cryptographic guarantees.

This service is ideal for protecting intellectual property, research, legal documents, design drafts, code, and any other material where authorship and existence must be provably timestamped.

A trustless, permanent anchor for any file that need to be verified.

Context & Problem

The Problem

Traditional document notarization methods suffer from:

High costs for official notary services
Slow processing
Geographic limitations
Risk of altered or missing records
Dependence on centralized institutions

Organizations and creators need a way to prove authorship, establish priority, and timestamp content without revealing the full document or relying on third parties.

The Solution

SafePulse Document Registry creates an immutable onchain proof that a specific document, identified by its hash, existed at a given moment. This proof is:

Cryptographically verifiable
Public or private document identifier
Permanent and censorship-resistant
Quick and inexpensive

This allows creators, researchers, and businesses to validate authorship or existence whenever needed.

Use Cases

1. Intellectual Property Protection

Artists timestamp digital artwork
Writers record novel drafts
Developers anchor new code or smart contracts
Designers secure product sketches

2. Research & Innovation

Recording first publication dates
Protecting proprietary formulas
Proving original authorship of research papers
Documenting experiments or iterations

3. Legal and Compliance

Timestamping agreements before signature
Anchoring evidence documents
Recording immutable audit logs

4. Enterprise Workflows

Documenting internal policies
Securing confidential revisions off-chain
Establishing chain-of-custody events

Key Features

1. Fast and Low-Cost

Designed as a lightweight alternative to Verifiable Documents.

2. Non-custodial Data management

File stays off-chain by user/issuer, we verify.

3. Immutable and Permanent

Records cannot be deleted or modified, ensuring trustworthiness.

4. Flexible Storage Options

Users can store files:

Locally
IPFS
Arweave
Any private or centralized host

5. No Initialization Required

Unlike Verifiable Documents, the record exists immediately after registration.

Step-by-Step Tutorial

Prerequisites

SafePulse Wallet installed
Native token balance for registration fees
Issuer/Creator DID: an key DID (did:key) or an ERC-1056 DID with issuer key as its Delegate
File prepared and hashed automatically by the app

A. Registering a Document

Upload your file to one of:
- IPFS
- Arweave
- Centralized host (direct download link)
Tap Document Registry
Copy the file link/IPFS-CID/Arweave Transaction Id
Fill in the creation form:
- Paste the refrence identifier (file link/IPFS-CID/Arweave Transaction Id)
- Choose blockchain network
Tap Register (top of screen)
Confirm the on-chain transaction
After minting, go to History
Locate the document history record
Share the Verifiable Document DID with relevant parties

Real-World Examples

Example 1: Protecting Creative Work

A designer registers a new product sketch. Months later, if questioned about authorship, the onchain timestamp validates they created it first.

Example 2: Academic Research Timestamp

A scientist anchors early drafts of a paper before journal submission, proving that research was conducted earlier than similar publications.

Example 3: Internal Company Evidence

A compliance officer anchors a log of policy updates to prove the timeline of organizational changes.

Benefits

Extremely low-cost proof registration
Works instantly with minimal user steps
Does not expose or upload the actual file
Immutable and verifiable forever
Provides strong authorship protection
No dependency on centralized notaries

Drawbacks

Does not support revocation
Does not support multiple controller
Cannot attach signatures
Cannot filter/limit verifiers

For these advanced features, Verifiable Documents are recommended.

Best Practices

Save the original file securely — the hash depends on exact content
Use decentralized storage (IPFS/Arweave) for long-term preservation
Register drafts and versions frequently if working iteratively
Combine registry entries with Pledge Contracts for deliverable verification
For legal agreements, convert to Verifiable Documents if signatures are needed

DID

A self-sovereign, portable, Ethereum-based identity standard for secure, user-controlled interaction across SafePulse services.

Overview

SafePulse’s Decentralized Identity (DID) system is built on the ERC-1056 identity standard, allowing users to create a self-sovereign digital identity that is:

User-controlled (no central authority)
Portable across services and networks
Privacy-preserving, with no forced disclosure
Compatible with Verifiable Credentials and onchain contracts

A DID is the foundational element powering all advanced workflows in SafePulse, including:

Verifiable Credentials
Document verification
Pledge Contract authorization
Escrow interactions
Asset Paywall access

Your DID enables you to prove who you are cryptographically, without giving up personal data, documents, or reliance on centralized identity providers.

Context & Problem

The Problem

Most modern digital identity systems suffer from:

Centralized control (Google, Apple, government IDs)
Limited portability across platforms
High privacy exposure
Risk of surveillance or data misuse
Fragmented identity silos

Users need a secure identity they can use across agreements, documents, services, and contracts without depending on third parties.

The Solution

SafePulse implements ERC-1056 Decentralized Identity, giving users:

A cryptographic identity bound to their wallet
A globally resolvable DID Document
Self-sovereign control of keys
Maximum privacy with minimum data sharing
Full integration with the onchain ecosystem

Your DID becomes your trust anchor across all services.

Key Features

1. Self-Sovereign Control

You create your identity locally on your device. No admin, no provider, no central manager.

2. Portable & Cross-Platform

Your DID can be used across multiple networks, dapps, and verification systems.

3. Privacy-First

DIDs do not require linking to names, emails, or personal data.

4. Verifiable & Tamper-Proof

Each DID has an onchain DID Document describing:

Public keys
Verification methods
Authentication methods
Delegates (optional)

5. Works With Verifiable Credentials

Your DID can issue, verify, and receive:

Certificates
Licenses
Compliance proofs
Identity attestations

6. Required for Self Identification

Issuers need to identify themselves by DID (Public Key DID or ERC-1056)

Use Cases

1. Freelance Work & Payments

A freelancer uses a DID to identify themselves in a Pledge Contract — no email or passport needed.

2. Enterprise Compliance

Companies issue DID-backed credentials to employees, proving compliance or training certifications.

3. Education & Certification

Schools issue DID-bound certificates that can be verified anywhere.

4. Secure Document Management

Documents are signed using the DID’s verification keys.

5. Content Distribution

Asset Paywall access can be tied to a user’s DID, proving rights and preventing unauthorized sharing.

Step-by-Step Tutorial

A. Creating Your DID

Open the SafePulse Wallet
Navigate to Identifiers
Tap Create DID and choose DID type (Public Key DID or ERC-1056)
The wallet generates DID string as decentralized identifier of EOA as user identifier
Confirm transaction
Your DID is now active and visible under Identifiers

B. Managing Your DID

Inside the DID details page, you can:

View DID Document
View delegates
Add/Remove delegates (optional)
Rotate keys for security
Export DID metadata

All sensitive operations stay local on your device unless explicitly broadcast onchain.

SafePulse applies the ERC-1056 standard, ensuring maximum interoperability.

Real-World Examples

Example 1 — Talent Marketplace

A freelancer uses their DID to authenticate in a contract without revealing personal identity. The buyer verifies the DID and contract execution onchain.

Example 2 — Employee ID System

A company issues VCs tied to employee DIDs. Employees prove qualifications without exposing private data.

Example 3 — Anonymous Research Publication

A researcher anchors findings under a pseudonymous DID, later proving authorship without revealing identity at submission time.

Benefits

Fully decentralized identity
No personal data exposure
Secure and key-controlled
Interoperable with global standards
Works seamlessly across SafePulse services
Ideal for anonymous or pseudonymous workflows

Drawbacks

User is responsible for securing private keys
Identity recovery requires proper key backups
Cross-network DID document updates require gas fees

Verifiable Credentials

Wallet-first, privacy-preserving credentials compliant with W3C VC v2.0 and anchored to SafePulse DIDs.

Overview

SafePulse’s Verifiable Credentials (VCs) provide a secure, decentralized way to issue, verify, and present proofs of:

Skills & achievements
Education & training
Compliance & licenses
Membership & identity attributes
Business records or attestations

VCs are:

Tamper-proof (cryptographically verifiable)
Self-sovereign (stored in the user’s wallet)
Portable across networks and platforms
Privacy-preserving via selective disclosure & verifiable presentations
Built on W3C Verifiable Credential v2.0

A VC is signed by the issuer’s DID, held by the subject’s wallet, and verifiable by any third party.

Context & Problem

The Problem

Traditional credentials (certificates, licenses, IDs) have challenges:

Easy to forge or manipulate
Hard to verify internationally
Require centralized authorities
Reveal too much personal data
Slow manual verification processes
Not portable across platforms

Users and organizations need trusted, private, standardized digital credentials that work anywhere.

The Solution

SafePulse VCs:

Are verified via blockchain + DID signatures
Require no central authority
Support selective disclosure (only reveal what’s necessary)
Allow flexible proof presentations
Can represent any type of claim — academic, corporate, legal, or personal

VCs integrate deeply with SafePulse’s identity and document ecosystem, powering secure B2B and P2P verification workflows.

Use Cases

1. Education & Certification

Schools issue degrees or certificates as VCs
Training centers issue completion badges
Students share credentials without revealing full identity

2. Enterprise Compliance

Employees receive compliance certifications (e.g., AML/KYC training)
Contractors prove qualifications before engagement
Auditors verify digital proof instantly

3. Talent & Freelancing

Freelancers present verified work history or skill credentials
Clients validate identity attributes without exposing personal details

4. Legal & Regulatory

Businesses issue licenses or compliance documents
Individuals prove age or residency using selective disclosure
Lawyers validate document issuance via VCs

5. Web3 & Onchain Reputation

Proof-of-contribution credentials
DAO participation records
Reputation scoring anchored to DID

Key Features

1. W3C VC v2.0 Compliant

Ensures global compatibility with web3 wallets, institutions, and verifiers.

2. Self-Sovereign Storage

Credentials stay in the payer’s device — no platform custody.

3. Selective Disclosure

Users reveal only the needed fields to a verifier.

4. DID-Based Signing

Both issuer and holder use their Decentralized Identity (DID).

5. Blockchain Anchoring

Credential hashes or metadata can be anchored onchain for immutability.

6. Revocation Support

Issuers can revoke credentials using their DID keys (if issued with revocation registry).

Credential Structure (Simplified Example)

{
  "@context": ["https://www.w3.org/2018/credentials/v2"],
  "type": ["VerifiableCredential", "EducationCertificate"],
  "issuer": "did:ethr:0xABC...",
  "credentialSubject": {
    "id": "did:ethr:0x123...",
    "name": "John Doe",
    "course": "Blockchain Development"
  },
  "proof": {
    "type": "EcdsaSecp256k1Signature",
    "created": "2025-01-01T00:00:00Z",
    "proofPurpose": "assertionMethod",
    "verificationMethod": "did:ethr:0xABC#owner",
    "signatureValue": "0x..."
  }
}

Step-by-Step Tutorial

A. Receiving a Credential

Open the SafePulse Wallet
Navigate to Identity → Credentials
Tap Receive VC
Scan QR code / paste credential payload
Wallet verifies:
- Issuer DID
- Signature
- Expiration & revocation (if applicable)
Accept and store the VC locally

Your VC is now available for presentations or sharing.

B. Issuing a Credential

Prerequisites

Your DID must be initialized
You must have issuer permissions in your workflow
(Optional) Verifiable Document to attach additional files

Steps

Navigate to Issue Credential
Fill in the credential fields:
- Type (certificate, membership, license…)
- Subject DID
- Data fields
(Optional) Attach Verifiable Document
Tap Issue
Wallet signs VC using issuer’s DID
Share VC with subject via:
- QR Code
- Direct import
- Encrypted message

C. Presenting a Credential (“Verifiable Presentation”)

A presentation allows the holder to share only the required parts of the credential.

Open the credential
Tap Present
Select fields to reveal
Wallet generates:
- A zero-knowledge / selective disclosure proof
- Holder’s DID authentication
Share the presentation with verifier

This preserves maximum privacy.

D. Revoking a Credential (Optional)

Open Issued Credentials
Select credential
Tap Revoke
Confirm DID-signed revocation

Verifiers will see the credential as revoked in future checks.

Real-World Examples

Example 1 — Digital Degree

A university issues VCs instead of PDFs. Employers verify authenticity instantly without contacting the school.

Example 2 — Driver License Check

User presents only “Over 18” instead of full identity details. Selective disclosure protects privacy.

Example 3 — Corporate Compliance

An employee presents a “Certified AML Officer” credential to a financial institution. The institution verifies:

DID of employee
DID of the issuing company
Integrity of the credential

Example 4 — DAO Reputation

A DAO issues contribution-based VCs to members. Tools read VC reputation to grant roles or voting rights.

Benefits

Trustless, verifiable credentials
Self-sovereign, not platform-controlled
Portable across apps, companies, and chains
Supports privacy and selective disclosure
Compatible with global W3C standards
Works seamlessly with DID and Document Contracts

Drawbacks

Users must safeguard wallet and credentials
Revocation requires issuer DID control
Some platforms still rely on centralized credential formats

Best Practices

For Issuers

Use stable, persistent DIDs
Anchor revocation lists onchain
Avoid including unnecessary personal data
Use credential types aligned with global schemas (e.g., W3C)

For Holders

Make secure encrypted backups of credentials
Use selective disclosure whenever possible
Keep DID keys rotated and secure

For Verifiers

Always check DID signature and timestamp
Verify revocation status
Use VC-compliant parsers for best interoperability

Asset Paywall

Decentralized content monetization with onchain access control, multi-payment support, and DID-authenticated delivery.

Overview

The Asset Paywall service allows creators, businesses, and developers to register an digital content delivery contract. It is designed to support:

Digital content sales (media, PDFs, files, videos, audio, images)
Knowledge & research monetization
Premium memberships
One-time or tiered access models
Onchain payment validation
DID-authenticated access

The Asset Paywall integrates deeply with the SafePulse ecosystem, using:

DIDs for identity/authorship

It works fully wallet-first, ensuring users retain local control while publishers remain sovereign owners of their content. Issuers wont share ownership, they register an content delivery contract, customers approve the contract by payment and receive content identifier.

Context & Problem

The Problem

Most content monetization platforms:

Require central hosting
Control creator accounts
Can censor, block, or shadowban
Offer weak content protection
Depend on fragile credential-based logins

Creators need trustless payment and ownership without relying on intermediaries.

The Solution

SafePulse’s Asset Paywall:

Uses smart-contract payments
Deliver content identifier after payment
Stores protected assets via decentralized links or secure URLs
Uses DID, not centralized accounts
Runs entirely from the user's wallet (no platform custody)

Key Features

💸 1. Multi-Asset Payments

Publishers can charge:

Stablecoins
Other chain-native assets (where supported)

🎫 2. Flexible Access Models

One-time purchase means approve contract

📍 3. Onchain Proof of Purchase

Proofs are stored as lightweight logs and anchored to the buyer’s DID.

Use Cases

1. Content Creators & Educators

Paid course videos
Premium guides and PDFs
Photography, digital art, designs
Locked newsletters or research papers

3. Media & Journalism

Pay-per-article
Premium investigations
Subscriber-only content

4. Businesses & Enterprises

Shared documents
Monetized research reports

Step-by-Step Tutorial

A. Creating a Paywalled Asset

Upload or host file on an centralized or decentralized storage

Open the wallet
Tap Asset Paywall
Choose the asset type
Choose your payment configuration
- Issuer DID
- Network and token
- Price
- Asset Name
Confirm onchain deployment
Asset Paywall contract is deployed
Share the asset DID

B. User Purchasing Access

Open wallet
Scan Paywall QR or paste DID
View content preview + price
Tap Purchase
Wallet executes payment contract
On success, wallet receives access token bound to DID
Content unlocks automatically

C. Managing Asset

At Contract organization there is options for freeze/unfreeze asset, collect payments or delete asset.

Real-World Examples

Example 1 — Paid PDF Guide

A researcher sells a 200-page PDF on IPFS via paywall. After paying, users get a DID-bound decryption key.

Example 2 — Video Course

Teacher uploads course videos behind a paywall with 30-day access.

Example 3 — Premium Article

A journalist publishes a pay-per-article story with a one-time purchase.

Example 4 — Photography Pack

A designer distributes a set of high-resolution files, protected by the paywall.

Benefits

For Creators

1% platform fees
No censorship
Automated payments
Privacy first, no KYC

For Users

No centralized accounts
Portable access
Verifiable proof of purchase
Zero-knowledge access control

For Businesses

Internal distribution
Contract-based licensing
Easy integration

Drawbacks / Considerations

Requires gas fees on deployment
Content hosting costs depend on storage provider
Price changes may require redeployment (contract-defined)
Users must protect local wallet keys for access retention

Best Practices

Always encrypt sensitive files before uploading
Offer low-cost preview content to improve user trust

Services

Execution Asset

Overview

SafePulse’s tokenomics are intentionally designed to avoid speculation and instead strengthen the integrity, security, and usability of the platform. The ecosystem revolves around RUNE, a non-tradable internal utility token used exclusively to deploy certain types of smart contracts.

RUNE is not a currency, not a tradable asset, and not a revenue instrument. It is a functional fuel that powers creatable agreements across the SafePulse network.

Purpose of RUNE

RUNE exists to guarantee:

Fair access to contract creation
Spam resistance
Decentralized execution integrity
Resource accountability in contract deployment
A stable, predictable unit of work inside SafePulse

By tying contract creation to an internal, fixed-supply token, SafePulse avoids volatility and ensures that the cost of deploying agreements stays stable across time and market cycles.

Where RUNE Is Used

RUNE is required for deploying all creatable contracts, including:

Pledge Contracts
Verifiable Document Contracts

These contracts form the backbone of enterprise workflows, compliance systems, and automated agreements inside SafePulse.

Access to RUNE

RUNE is exclusive to Flarion holders. This creates a premium access layer for users who need:

High-volume contract creation
Enterprise-grade workflows
Long-term, predictable operational scaling

It also ensures responsible use, preventing contract spamming and maintaining network health.

Design Principles

1. Non-Tradeable, Utility-Only

RUNE cannot be traded or sold on public markets. This eliminates speculation and ensures token utility remains stable and predictable.

2. Anti-Spam and Cost Control

Contract creation consumes RUNE, ensuring users deploy only meaningful agreements.

3. Predictable Economics

RUNE is supplied to Flarion holders and via subscription rewards, giving users a structured, clear cost model for repeated deployments.

SafePulse’s ecosystem tokens built for functionality and real value as an execution asset, not hype. RUNE powers the system with predictable, transparent, and fair access to smart contract creation—ensuring SafePulse remains sustainable, scalable, and trustless.

Pay-As-You-Go Model

Overview

The Pay-As-You-Go (PAYG) model is designed for individual users and small teams who need flexible access to SafePulse without subscriptions.

Users pay only for what they use, using native chain tokens (ETH, POL, etc.).

It is the simplest and most accessible model for casual usage.

Who It Is For

Freelancers
Crypto-native individuals
Small businesses
Occasional document certifiers
One-time escrow users
Creators paywalling individual digital assets

Users with low or inconsistent contract volume benefit most from the PAYG model.

Where PAYG Applies

PAYG covers all non-creatable contracts, including:

1. Escrow

Flat deposit fee
1% withdrawal fee
Ideal for one-time agreements

2. Document Registry

Low-cost registration
Instant on-chain timestamps

3. Asset Paywall

Pay-per-access publication
Monetize digital assets instantly

All fees are paid using native network tokens, keeping the user experience simple and familiar.

Key Benefits

1. No upfront commitment

Perfect for infrequent use.

2. Transparent micro-fees

Costs remain predictable and easy to understand.

3. Accessible to all users

No Flarion token or subscription required.

4. Non-custodial and trustless

Users stay in control of all assets and data.

Fee Examples

Escrow: 0.00067 ETH deposit fee (prevent abuse) + 1% withdraw
Document Registry: 0.0019 ETH per entry
Asset Paywall: 0.029 ETH deployment

(Chain-specific numbers may vary.)

PAYG provides affordable access to SafePulse’s core services with no commitments, enabling casual users to leverage trustless agreements whenever needed.

Subscriptions

Overview

SafePulse offers subscription plans designed for teams, enterprises, and organizations that require consistent, high-frequency contract creation.

Subscriptions unlock predictable monthly or yearly operational capacity, reduced costs, and bonus RUNE rewards.

Who Subscriptions Are For

Legal and compliance teams
HR onboarding pipelines
Procurement departments
Large-scale certifiers and credential issuers
Agencies and organizations running recurring workflows
Any user needing predictable cost structures

Subscriptions convert SafePulse into an integral operational tool rather than pay-per-use tooling.

What Subscriptions Provide

✔ Creatable Contract Deployments

Subscriptions cover:

Pledge Contracts
Verifiable Document Contracts

Each tier includes a specific number of deployments.

✔ Lower Per-Contract Cost

Discount rates range from 25% to 40% depending on the plan.

✔ RUNE Rewards

Every plan provides bonus RUNE to support future workflow expansion.

✔ Multi-Period Options

Plans are available at:

1 month
3 months
6 months
12 months

Longer commitments unlock deeper discounts.

Subscription Tiers

Tier	Contracts / Month	Discounts	RUNE Rewards	Duration Options
Prime	8 Pledge / 12 Docs	25%	66 RUNE	1 months
Nexus	20 Pledge / 30 Docs	30%	165 RUNE	3 months
Elite	40 Pledge / 60 Docs	35%	264 RUNE	6 months
Vertex	100 Pledge / 200 Docs	40%	363 RUNE	12 months

Prices differ per chain (Arbitrum / Polygon), but the structure and value remain identical.

Benefits of Subscription

1. Predictable Costs

No surprises — budgeting becomes easy.

2. Workflow Scalability

High-volume teams can automate agreements without worrying about per-use limits.

3. Increased Efficiency

Subscriptions remove friction and enable enterprise-wide adoption.

4. Access Control

Only Flarion holders can subscribe, ensuring ecosystem integrity.

SafePulse’s subscription system empowers medium-to-large users with predictable, scalable, and cost-efficient contract deployment capacity. It is the backbone for enterprise automation within the SafePulse ecosystem.

Target Market

Overview

SafePulse serves a diverse global user base across individuals, creators, professionals, and institutions. The platform is designed for anyone who needs secure, trustless, automated agreements or verifiable data flows.

Our target market spans consumer-level use cases all the way to enterprise-grade automation.

1. Crypto-Native Individuals & Freelancers

These users value:

Privacy
Financial sovereignty
Non-custodial tooling
Peer-to-peer agreements
Censorship resistance

Use Cases

Freelance gig payments
Peer-to-peer escrow
Simple service agreements
Automation without intermediaries

SafePulse provides tooling perfectly aligned with their ethos.

2. Enterprises & Institutions

Large organizations need scalable trust infrastructure across departments.

Teams That Benefit

Legal
Procurement
HR
Compliance
Operations

Use Cases

Pledge-based procurement logic
Employee verification
Credential issuance
Contractual automation
Cross-border settlement

SafePulse serves as a programmable infrastructure layer for digital trust.

3. Content Creators, Researchers & Educators

These groups require tamper-proof verification and monetization tools.

Use Cases

Intellectual property proofs
Research authenticity verification
Certificate issuance
Selling gated assets or digital files
Timestamped document publications

The Document Registry and Asset Paywall are especially valuable to them.

4. Borderless & Privacy-Focused Users

A rapidly growing segment driven by:

Exclusion from banking systems
High global mobility
Desire for anonymity
Need for stablecoin payments

Use Cases

Anonymous agreements
Pseudonymous contracting
Global access to stable settlement
Cross-border operations without banks

SafePulse empowers these users with secure, privacy-respecting financial tools.

SafePulse’s target market includes anyone needing trustless agreements, verifiable documents, and non-custodial settlement. From individual freelancers to large enterprises, SafePulse delivers infrastructure that replaces intermediaries with automated, decentralized logic.

Privacy Policy

Last updated: 20 Dec 2025

By using SafePulse (“SafePulse”, “the Platform”, “we”, “us”, “our”), you agree to the practices described in this Privacy Policy. If you do not agree, you must not use the Platform.

1. Introduction

SafePulse is committed to protecting your privacy and ensuring that you maintain full control over your data.

The Platform is designed with:

Data minimalism
Local-first identity
Non-custodial architecture
User-controlled smart contract interactions

This Privacy Policy explains how SafePulse handles information, what is (and is not) collected, and your responsibilities as a user.

2. Zero Personal Data Collection

SafePulse collects no personal information whatsoever.

We do not collect, store, or process:

Names, email addresses, phone numbers
Government IDs, documents, or biometric data
Wallet private keys, seed phrases, or sensitive financial details
Location-linked identity or IP-linked profiles
Personal behavioral tracking
KYC information or verification data

SafePulse performs no KYC, no identity verification, and no account creation with personal data.

3. Local Device Control of Identity and Keys

All cryptographic materials—including identity keys, DID keys, private keys, credential keys, and signing keys—are generated and stored exclusively on your device.

SafePulse:

Does not access, store, back up, or transmit your keys
Does not retain credential-related information

You are solely responsible for securing your keys, recovery phrases, and devices. If keys are lost, SafePulse cannot recover them, reset them, or restore access.

4. No Cloud Backups & No Cloud Recovery

SafePulse does not provide:

Cloud backup or cloud key storage
SRP-based backups
Server-side identity storage
Remote account restoration

All recovery is performed locally by the user using their own passphrase or recovery materials.

5. No Traditional Authentication Services

SafePulse does not use or rely on:

OAuth, email/password, phone verification
Firebase Authentication or centralized login systems
Third-party identity providers

Authentication and identity generation occur entirely on-device and are self-sovereign.

6. Optional Diagnostic Analytics

SafePulse may collect non-personal diagnostic data solely to improve:

Stability
Performance
Security
Crash detection

This data:

Is anonymous and cannot identify users
Contains no personal or behavioral information
Can be disabled at any time in settings

Analytics may include device type, error logs, and crash traces—only for performance improvement.

7. No Tracking Technologies

SafePulse does not use:

Cookies, web beacons, or fingerprinting
Targeted advertising identifiers
Cross-site tracking or behavioral analytics

No data is sold, shared, or monetized.

8. Third-Party Integrations

Interactions with third-party services (e.g., blockchain RPCs, event loggers, error trackers) are:

Optional and user-initiated
Separate from SafePulse systems
Governed by the third-party’s privacy policies

SafePulse does not control or store data from third-party services.

9. Smart Contract Interactions

Smart contract interactions may appear on public blockchains.

Transactions are irreversible
Blockchain records are public by default
SafePulse cannot delete or alter blockchain data
Users must understand the immutable nature of blockchain systems

Smart Contract Upgrades:

SafePulse may release updates or improvements
Users may choose whether or not to adopt updates, at their own discretion
The Platform provides no guarantees regarding performance, compatibility, or outcomes of upgraded contracts

10. Intellectual Property & Platform Ownership

All components of SafePulse—smart contracts, dApps, ABIs, APIs, algorithms, documentation, and UI/UX—are the sole property of Hassan Qasemi, under copyright and the Contract Foundry Project, and are patent pending
Users must not reverse engineer, decompile, copy, modify, or create derivative works of any platform components
Users must not connect unauthorized third-party proxies or clients to SafePulse smart contracts

11. Content Restrictions & User Responsibility

Users must ensure that their usage:

Complies with local laws and regulations
Does not involve illegal, abusive, harmful, or exploitative content
Respects platform restrictions against prohibited misuse

Users are responsible for their cryptographic materials and account security.

12. Age Restriction

SafePulse is intended for users 22 years of age or older. No personal or non-personal data is knowingly collected from minors.

SafePulse:

Does not share, sell, or monetize data
Does not profile users
Does not integrate ad networks
Analytics remain local and anonymous

All user activity remains private on your device.

14. Security Measures

SafePulse uses:

Local encryption and self-sovereign identity mechanisms
Decentralized architectures and secure cryptographic standards

However, no system is perfectly secure. Users must:

Protect devices and backups
Use strong passphrases
Understand the risk of key loss

SafePulse cannot recover lost keys or compromised devices.

15. Updates to This Privacy Policy

SafePulse may update this Privacy Policy to reflect:

Changes in technology
Security improvements
New platform features
Updates in decentralized identity or smart contract standards

Continued use constitutes acceptance of the updated policy.

16. Contact Information

For privacy questions or administrative matters: info@florune.net

Terms & Conditions

Last updated: 20 Dec 2025

By using SafePulse (“SafePulse”, “the Platform”, “we”, “us”, “our”), you agree to comply with these Terms & Conditions. If you do not agree, you must not use the Platform.

1. Introduction

SafePulse is an independently operated decentralized software platform providing non-custodial services for blockchain-based agreements ecosystem.

SafePulse:

Operates as a decentralized software service.
Does not recognize or submit to foreign or external jurisdictions by default.
Includes proprietary smart contracts, cryptographic systems, protocols, and software components that are patent pending and protected by the Contract Foundry Project.

By using SafePulse, you acknowledge and accept these Terms & Conditions.

2. “As-Is” and “As-Available” Disclaimer

SafePulse and all related components—including smart contracts, APIs, ABIs, and UI—are provided strictly:

“AS IS”
“AS AVAILABLE”
“WITH ALL FAULTS”

We make no guarantees regarding:

correctness or completeness
uninterrupted or bug-free operation
security or immunity from exploits
suitability for any purpose
compatibility with any system or jurisdiction

You use the Platform entirely at your own risk.

3. No Legal Advice or Dispute Resolution

SafePulse does not provide:

legal advice
financial advice
tax advice
compliance guidance
regulatory guidance
arbitration or dispute resolution

Users are solely responsible for consulting independent legal counsel and resolving any disputes. SafePulse does not intervene, mediate, or enforce any agreements or external jurisdictional decisions.

4. No Guarantee of Court Recognition

SafePulse does not guarantee that any court, arbitration body, or authority will accept or recognize:

blockchain data
smart contract states
cryptographic proofs
timestamps
digital agreements
decentralized identifiers

Acceptance of such materials is outside SafePulse’s control.

5. Non-Custodial Design & No Cloud Recovery

SafePulse is a fully non-custodial platform.

SafePulse does not:

store private keys
store passphrases
store account seeds
store encrypted backups
provide cloud key recovery
provide cloud SRP recovery
store wallet secrets in any form

The only way to recover your keys is through your locally stored passphrase or recovery phrase.

If you lose your keys or SRP:

SafePulse cannot restore access
SafePulse cannot reset accounts
access may be permanently lost

Users are fully responsible for secure storage and backup.

6. Privacy & Data Protection (No KYC, No Personal Data)

SafePulse collects no personal information:

names, email addresses, phone numbers, IDs, biometric data, wallet keys, IP-linked identity, or location
no KYC or tracking of user behavior

Authentication

Identity keys are generated and stored locally
SafePulse does not use third-party authentication, OAuth, Firebase, email/password, or phone verification

Analytics

Only non-personal diagnostic data may be collected for crash reports or performance monitoring
Analytics do not contain personal data and can be disabled

7. User Responsibilities

By using SafePulse, you agree to:

Secure your private keys, passphrases, and devices
Maintain your own backups
Comply with local laws in your jurisdiction
Understand that blockchain transactions are irreversible
Accept that smart contract data cannot be modified by SafePulse

You assume full responsibility for your digital assets.

8. Smart Contracts & Upgrades

SafePulse provides smart-contract ecosystem.

However:

SafePulse does not mediate disputes
SafePulse cannot modify smart contract states
P2P Agreement Payments and Escrows may lock until all parties reach agreement
Locked funds cannot be released without action of parties

Smart Contract Upgrades:

SafePulse may release updates or improvements to smart contracts
Users may choose whether or not to adopt updates at their own discretion
The Platform provides no guarantee regarding outcomes, performance, or compatibility of upgraded contracts

9. Limitations of Use & Intellectual Property

Ownership & Protection:

All components of SafePulse™, including smart contracts, dApps, ABIs, APIs, algorithms, documentation, and UI/UX, are the sole property of Hassan Qasemi, under copyright and the Contract Foundry Project, and are patent pending

User Obligations: By using SafePulse, you agree that you will not:

Modify, copy, prepare derivative works of, decompile, or reverse engineer any materials or software
Remove, alter, or obscure copyright, patent, trademark, or other proprietary notices
Transfer, distribute, or mirror materials to any other server, platform, or person
Abuse, disrupt, or interfere with SafePulse services
Connect unauthorized third-party proxies, clients, or external systems to SafePulse smart contracts or dApps

10. Prohibited Uses

Users may not use SafePulse for:

Illegal, harmful, or abusive activity
Fraud, deception, or money laundering
Exploitation or hacking attempts
Bypassing technical restrictions

Violations may lead to restrictions within the technical limits of the Platform.

11. Age Restriction

SafePulse is intended for users 22 years of age or older. Access by individuals under this age is prohibited.

12. Jurisdiction

SafePulse is governed exclusively by the laws applicable to its operational jurisdiction. The Platform does not recognize external jurisdiction except where legally required. SafePulse does not provide legal, regulatory, or dispute resolution services; users are solely responsible for resolving disputes.

13. Limitation of Liability

SafePulse is not liable for:

Lost private keys, access, or assets
Smart contract exploits
Downtime or system failures
Transaction errors
Indirect, direct, incidental, or consequential damages

Use of the Platform is entirely at your own risk.

14. Amendments

SafePulse may update these Terms at any time due to:

Technical changes
Legal changes
New features
Security improvements

Continued use of the Platform constitutes acceptance of updated Terms.

15. Contact Information

For legal or administrative inquiries: info@florune.net

Frequently Asked Questions (FAQ)

1. What is SafePulse?

SafePulse is a decentralized Web3 platform that empowers you to manage your digital identity, verify documents, and conduct secure transactions without intermediaries—giving you full control over your data and assets.

2. How do I create and manage my digital identity?

Your digital identity and cryptographic keys are generated and stored locally on your device. This ensures only you have access—SafePulse never stores or controls your private keys.

3. Does SafePulse collect my personal data?

No. We do not collect or store sensitive personal information. Some minimal data (like your email) may be handled by third-party authentication providers, but SafePulse itself does not access or keep this data.

4. How secure is my data on SafePulse?

Very secure. All your keys and credentials stay on your device. We do not track you, use cookies, or share your information. Plus, every transaction is cryptographically secured on the blockchain.

5. What payment options are available?

You can pay for services either by topping up your account with ETH for pay-as-you-go or by choosing one of our subscription plans tailored for professionals, creators, agencies, or enterprises.

6. Are there any fees besides the subscription or service charges?

Yes. Ethereum network gas fees apply to on-chain transactions. These fees are set by the Ethereum network and are paid directly from your wallet. SafePulse does not mark up or control gas fees.

7. Can I cancel my subscription or account?

Yes, you can cancel anytime. After cancellation, all your subscription benefits and remaining balances will be terminated and cannot be recovered.

8. What happens if I lose my cryptographic keys?

If you lose your keys, they cannot be recovered. It’s critical to back up your keys securely, as they control access to your identity and assets on SafePulse.

9. How does SafePulse handle disputes in escrow contracts?

SafePulse does not mediate disputes. When there is a disagreement, relevant contract functions such as fund withdrawal are paused until all parties reach an agreement.

10. Who can use SafePulse?

SafePulse is intended for users aged 22 and older, including individuals, creators, freelancers, businesses, and enterprises looking for secure, decentralized identity and transaction solutions.

📬 Contact Us

We’d love to hear from you! If you have questions, feedback, or need support, you can reach us through the following channels:

Telegram Channel → @floruneapp
Bluesky → @florune.net
X (formerly Twitter) → @florune_dapp

✨ Tip: Join our Telegram channel to stay updated on announcements, new features, and community discussions.

Keyboard shortcuts

SafePulse Docs