Home

CapSign is a platform for creating and managing tokenized real-world assets (RWAs), enabling secure, compliant, and efficient digital representation of physical and financial assets.

Table of Contents

• Overview

• Key Features

• For Developers

  • Getting Started

  • API Documentation

  • Architecture

• For Users

  • Platform Access

  • User Guide

Overview

CapSign provides a robust infrastructure for the tokenization of real-world assets including real estate, commodities, securities, and other traditional financial instruments. Our platform bridges traditional finance with blockchain technology, offering a suite of tools for RWA issuance, management, and transfer within a secure and compliant framework.

Key Features

• Real-World Asset Tokenization: Convert traditional assets like real estate, securities, and commodities into digital tokens

• Compliance Framework: Built-in regulatory compliance tools designed specifically for RWA requirements

• Security: Enterprise-grade security protocols for protecting high-value asset representations

• Interoperability: Seamless integration with existing financial systems and asset management platforms

• Scalability: Designed to handle high transaction volumes across diverse asset classes

• Transparency: Auditable transaction history for all tokenized assets

For Developers

CapSign smart contracts are currently in private preview. To request early access, email [e-mail].

Getting Started

1. Prerequisites

   • Foundry development environment

   • Ethereum wallet and Base Sepolia ETH
   • Familiarity with Solidity and blockchain concepts

2. Installation

   git clone https://github.com/capsign/protocol.git capsign
   cd capsign
   forge install

3. Integration

   We recommend using our Node.js SDK for interacting with CapSign contracts:

   npm install @capsign/sdk

   // Example SDK usage
   const CapSign = require("@capsign/sdk");
   
   // Initialize connection to CapSign contracts
   const capsign = new CapSign.Client({
     network: "base-sepolia",
     privateKey: process.env.PRIVATE_KEY,
   });
   
   // Interact with tokenized assets
   const myAssets = await capsign.assets.getAll();

API Documentation

Comprehensive API documentation is available at docs.capsign.com/api-reference.

Note: CapSign currently only supports the Base Sepolia testnet. Mainnet support coming soon.

Architecture

Capsign is built on a trustless, self-custodial architecture:

• 100% On-Chain Operations: All asset management and transactions occur on-chain

• Self-Custodial Design: Users maintain complete control of their assets

• Decentralized ID Attestation: The only component with an off-chain element, providing secure identity verification

• Smart Contract Layer: Secure and audited contracts for asset tokenization and management

For Users

Platform Access

Visit app.capsign.com to access the user interface.

User Guide

Our User Guide provides detailed instructions for:

• Tokenizing real-world assets

• Managing asset lifecycle events (dividends, voting, etc.)

• Setting compliance parameters for regulated assets

• Executing compliant transfers and transactions

• Reporting and analytics for portfolio management

Regulatory Considerations

Capsign is designed with regulatory compliance as a foundational principle for real-world asset tokenization:

• KYC/AML Integration: Built-in support for Know Your Customer and Anti-Money Laundering protocols required for regulated assets

• Jurisdictional Flexibility: Configurable rulesets to adapt to different regulatory environments across global markets

• Audit Trails: Comprehensive record-keeping for regulatory reporting and asset provenance

• Compliance Documentation: Compliance framework documentation for regulators

Licensing

This project uses multiple licenses for different components:

1. Root License: The default license for the project, located in the root LICENSE file.

2. AGPL-3.0 License:

   • Files in the ./src/AssetManagement directory (excluding the ./Strategies subfolder) are licensed under the AGPL-3.0 license.

   • Any modifications to these files must comply with the AGPL-3.0 license, including providing source code access for networked use.

   • See ./src/AssetManagement/LICENSE for details.

3. Strategies Subfolder: Files in ./src/AssetManagement/Strategies are licensed under the Root Project License and are independent works.

Refer to file headers and directory-level README.md files for more details.

Support and Community

• Documentation: docs.capsign.com
• Community Forum: forum.capsign.com
• Technical Support: [e-mail]
• Discord: Join our Discord

Contributing

We welcome contributions from the community. Please see our Contributing Guidelines for more information.

Security

If you discover a security vulnerability, please follow our Security Policy for responsible disclosure.