Deployment Guide

How do I deploy an asset tokenization platform?

Deploying an enterprise asset tokenization platform traditionally takes months and millions in development costs. With SettleMint's Asset Tokenization Kit, financial institutions and enterprises can launch production-ready tokenization platforms in under 30 minutes.

Who uses the Asset Tokenization Kit?

• Banks & Financial Institutions: Launching digital securities and CBDCs
• Asset Managers: Creating tokenized funds and investment products
• Corporations: Issuing digital bonds and tokenized equity
• Government Entities: Deploying digital currencies and bonds
• FinTech Startups: Building innovative tokenization solutions

What problems does rapid deployment solve?

Quick Start: How do I begin deployment?

What's the difference between development and production environments?

How do I scale my deployment?

Dynamic Scaling Options:

• Vertical Scaling: Upgrade CPU/RAM without downtime
• Horizontal Scaling: Add nodes for higher throughput
• Geographic Expansion: Deploy to new regions
• Auto-scaling: Automatic resource adjustment based on load

Scaling Triggers:

• Transaction volume exceeds 80% capacity
• Storage usage approaches limits
• Response time degradation
• Business growth requirements

How do I deploy the user interface for my tokenization platform?

The Asset Tokenization Kit includes a production-ready web interface that your users will interact with. This white-label solution can be customized with your branding and deployed in minutes.

What does the frontend interface include?

Issuer Portal Features:

• Asset creation and management dashboard
• Compliance and KYC management tools
• Real-time analytics and reporting
• Multi-signature transaction approval

Investor Portal Features:

• Portfolio management dashboard
• Trading and transfer interface
• Document vault and reporting
• Mobile-responsive design

Container Deployment Configuration

Deploy the frontend using our optimized container image:

How do I control access to the platform?

Access Control Options:

🌐 Public Access

• Use Case: Demo environments, public token sales
• Security: Rate limiting, DDoS protection
• Features: Read-only access to public data

🔒 Organization Members Only

• Use Case: Internal platforms, private securities
• Authentication: SSO integration (SAML, OAuth)
• Audit: Complete access logs for compliance

🎯 Custom Access Rules

• IP whitelisting for specific regions
• Multi-factor authentication (MFA)
• Role-based access control (RBAC)
• Time-based access windows

What environment variables do I need to configure?

Configure these secure environment variables for backend integration:

How do I set up a custom domain?

Custom Domain Configuration:

1. Choose Your Domain:

   • tokens.yourcompany.com (recommended)
   • digital-assets.yourbank.com
   • cbdc.centralbank.gov

2. SSL Certificate:

   • Automatic Let's Encrypt integration
   • Support for custom certificates
   • Wildcard certificates supported

3. DNS Configuration:

   Type: CNAME
   Host: tokens
   Target: your-deployment.settlemint.app
   TTL: 300

4. Propagation: Usually complete within 15 minutes

White-Label Customization Options:

• Custom logo and favicon
• Brand colors and typography
• Custom email templates
• Tailored legal disclaimers
• Multi-language support (25+ languages)

What are the key benefits of containerized deployment?

🚀 Rapid Deployment

• Launch new environments in 5 minutes
• Zero-downtime updates with rolling deployments
• Automatic rollback on failures

🔒 Enhanced Security

• Isolated runtime environments
• Immutable infrastructure
• Automated security patches
• Container scanning for vulnerabilities

📈 Scalability

• Handle 10x traffic spikes automatically
• Geographic load balancing
• CDN integration for global performance

💰 Cost Efficiency

• Pay only for resources used
• Automatic scaling down during low usage
• 70% cost savings vs traditional hosting

How do I set up local development for customization?

Local development enables you to customize the Asset Tokenization Kit to match your specific business requirements. Whether you're adding custom features or integrating with existing systems, our development environment provides everything you need.

Why develop locally?

• Custom Features: Add industry-specific functionality
• Integration Testing: Connect with your existing systems
• Compliance Customization: Implement jurisdiction-specific rules
• UI/UX Modifications: Match your brand guidelines perfectly

Development Setup Options

Access our open-source codebase: GitHub - Asset Tokenization Kit

Choose your development approach:

Quick Start: Predeployed Setup (5 minutes)

Perfect for teams who want to start building immediately without deploying contracts:

# Step 1: Install dependencies (30 seconds)
bun install

# Step 2: Authenticate with SettleMint (1 minute)
bunx settlemint login
bunx settlemint connect

# Step 3: Setup and launch the application (2 minutes)
cd kit/dapp
bun codegen:settlemint  # Generate TypeScript types
bun addresses           # Configure contract addresses
bun dev                 # Start development server

What's included in predeployed setup?

• ✅ Smart contracts deployed on Polygon Mumbai testnet
• ✅ Pre-configured Graph Protocol indexing
• ✅ Sample tokens for testing (USDC, ETH, BTC)
• ✅ Test wallets with funds
• ✅ Complete API documentation

Access your local platform: http://localhost:3000

Advanced: Full Customization Setup (30 minutes)

For teams building custom tokenization logic or integrating with existing smart contracts:

What can you customize?

• Smart Contracts: Add custom token standards, compliance rules
• Business Logic: Implement industry-specific workflows
• Integration: Connect with existing ERP/CRM systems
• Compliance: Add jurisdiction-specific requirements
• UI/UX: Complete frontend redesign

Prerequisites & Installation

Required Tools:

1. Foundry (Smart Contract Development)

   # Install latest version (v0.3.0+)
   curl -L https://foundry.paradigm.xyz | bash
   foundryup

   Documentation: Foundry Book

2. Node.js (v20.18.1 or higher)

   # Install via fnm (recommended)
   curl -fsSL https://fnm.vercel.app/install | bash
   fnm install 20
   fnm use 20

   Alternative: fnm GitHub

Step-by-Step Deployment Process

bun install                    # Install all dependencies
bun settlemint login          # Authenticate with platform
bun settlemint connect        # Connect to your blockchain

cd kit/contracts
bun deploy:remote             # Deploy to selected network
# ✅ Contracts deployed to: 0x123...abc

cd ../subgraph
bun deploy:remote             # Deploy Graph Protocol subgraph
# ✅ Subgraph available at: https://api.thegraph.com/...

cd ../../
bun codegen                   # Generate type-safe interfaces

cd kit/dapp
bun addresses                 # Set contract addresses
bun db:push                   # Initialize database schema

bun dev                       # Start on http://localhost:3000

Deployment Checklist:

• Smart contracts verified on block explorer
• Subgraph syncing correctly (check status)
• Database migrations completed
• Admin account created
• Test transaction successful

How do I customize the database schema?

The Asset Tokenization Kit uses a flexible database architecture that can be extended for your specific needs:

Common Database Customizations

Adding Custom Fields:

• KYC/AML data (verification levels, documents)
• Business-specific metadata (credit scores, collateral details)
• Regulatory fields (tax IDs, jurisdiction data)
• Integration IDs (ERP references, banking details)

Database Modification Process

# Navigate to database schema
cd kit/dapp/src/lib/db

# Edit schema files with your custom fields
# Example: Add accreditation status to users

cd kit/dapp
bun db:push                    # Update database structure

settlemint hasura track -a     # Track new tables/columns

bun codegen --force           # Update TypeScript definitions

bun dev                       # Verify in development

Authentication Schema Customization

Extending User Profiles:

When modifying authentication-related tables (user, session, account, verification):

1. Update additionalFields in kit/dapp/src/lib/auth/auth.ts:

   additionalFields: {
     accreditedInvestor: boolean,
     kycLevel: 'none' | 'basic' | 'enhanced',
     jurisdiction: string,
   }

2. Clear browser cookies and re-authenticate to see changes

3. Reference: Better Auth Core Schema

Production Database Considerations