Blockchain Service-Specific Terms

1.1 Pre-Deployment Requirements

Before deploying any smart contract through our platform:

Standard Requirements:

• Security audit required for mainnet deployments over $10,000 value
• Gas optimization must achieve "Acceptable" rating in our analyzer
• Documentation including function descriptions and risk disclosures
• Testing on testnet with minimum 95% test code coverage on smart contracts

Securities-Specific Requirements:

• Security audit of the master codebase used to deploy for ALL tokenized securities deployments
• Legal opinion on token classification (to be provided through Jones Day or a legal council of the client's choosing, to be approved by Nomyx)
• SEC filing documentation (Form D, Reg A/A+ qualification, or Reg S certification) or equivalent e.g. AIFM(EU) or VARA (GCC)
• GAAP audit reports (for Reg A offerings)
• Transfer agent agreement (if applicable as regulation requires)
• Investor communication protocols
• Compliance rule implementation verification

1.2 Our Responsibilities

• Provide deployment tools and templates
• Estimate gas costs (not guaranteed)
• Verify contract compilation
• Submit transactions to network
• Provide Diamond Proxy (ERC-2535) upgrade mechanisms
• Integrate compliance rule libraries via Nomyx ID & Persona

1.3 Your Responsibilities

• Ensure workflows provided by deployed contracts are correct (correct data flows are your responsibilities alongside approval of our deployed codebase)
• Fund gas fees post deployment for any investor or admin transaction costs
• Comply with all applicable laws
• Monitor and maintain transactions on deployed contracts
• Implement required compliance rules
• Maintain current SEC filings
• Update fund valuations as required

1.4 Deployment Limitations

• Maximum contract size per facet: 24KB (Ethereum limit)
• Batch deployments: 1 diamond contract with multiple facets per transaction
• High-value deployments require additional verification
• Securities tokens require compliance review
• Certain contract types prohibited (see Acceptable Use)

1.5 Post-Deployment

• Contracts are immutable once deployed (except Diamond Proxy upgrades)
• We retain no control over your contracts
• Upgrade patterns must be implemented pre-deployment
• You're responsible for all contract outcomes
• Compliance monitoring remains your obligation including investor onboard/offboarding/flagged investors monitoring

2.1 Token Standards Supported

• ERC-20: Fungible tokens (with permission controls)
• ERC-721: Non-fungible tokens (NFTs with permission controls)
• ERC-1155: Multi-token standard w/ permission controls
• Custom standards: With prior approval
• Diamond Proxy (ERC-2535): For upgradeable implementations

2.2 Compliance Requirements

You represent and warrant that:

• Tokens don't constitute unregistered securities
• You've obtained necessary legal opinions
• KYC/AML procedures are implemented
• Marketing complies with regulations
• All required SEC filings are current
• Transfer restrictions are properly implemented

2.3 Token Features

Available features (vary by plan):

• Minting controls and caps
• Pause/unpause functionality
• Burn mechanisms
• Access control (roles/permissions)
• Snapshot capabilities
• Compliance rule enforcement
• Transfer restrictions
• Investor whitelist management
• Automated distribution mechanisms

2.4 Restrictions

You may not create tokens for:

• Unregistered securities offerings
• Ponzi or pyramid schemes
• Money laundering purposes
• Sanctions evasion
• Any illegal activities
• Non-compliant fund structures

2.5 Fund Tokenization Specific Requirements

• Dual token structure: ERC-721 for fund assets, ERC-20 for investor shares
• Mandatory compliance rule embedding at minting or project setup
• Integration with approved identity providers
• 12-month lockup enforcement between Reg A offerings and other regulatory limitations
• Automated fee distribution
• NAV updates required annually with audit verification
• Investor cap management per SEC regulations

3.2 Supported Networks

Current networks (subject to expansion):

• Ethereum (Mainnet, Goerli, Sepolia)
• Polygon (Mainnet, Mumbai)
• Arbitrum One
• Optimism
• Base
• Binance Smart Chain
• Avalanche C-Chain
• Plume
• XDC
• Kadena EVM chain
• Trusted Smart Chain (TSC)

Note: Native USDC support required for securities transactions

3.3 Network Limitations

• We don't control network performance
• Congestion may delay transactions
• Fork handling per network consensus
• No guarantee of transaction inclusion
• TSC-specific features may not be portable

4.1 Gas Estimation

• Estimates provided for guidance only
• Actual costs may vary significantly
• Network conditions affect pricing
• You're responsible for sufficient funding
• Securities transactions may require higher gas limits

Gas costs are only facilitated by Nomyx on Nomyx Deployed and Audited contracts for L2s; users are responsible for all gas fees on Ethereum.

4.2 Gas Payment Options

• Direct Payment: You provide ETH/native tokens
• Gas Tank: Pre-fund account for automatic payment
• Meta-transactions: Available on supported networks
• Sponsored Transactions: For qualified securities offerings

4.3 Gas Policies

• Unused gas refunded to your wallet
• Failed transactions still incur gas costs
• Price spikes not our responsibility
• Emergency gas loans not available

5.1 Data Services Provided

• Real-time transaction monitoring
• Historical blockchain data access
• Event log indexing and search
• Custom data webhooks
• Analytics dashboards (GF2.0)
• Compliance reporting tools
• Investor activity tracking (GF2.0)
• Fund performance metrics (GF2.0)

5.2 Data Accuracy

• We index public blockchain data
• Reorganizations may affect data
• Finality varies by network
• You should implement confirmations
• Securities data requires additional verification

5.3 Data Retention

• Real-time data: 24 hours
• Indexed data: 2 years
• Archived data: By request
• Custom retention: Available
• Securities compliance data: 7 years minimum

6.2 Storage Limits

7MB per file limit with an upper cap of 10GB for all metadata per org on the enterprise plan.

6.3 Content Policies

• No illegal content
• No malware or exploits
• Copyright compliance required
• Adult content restricted
• Securities documents must be encrypted

7.1 Blockchain Risks

You understand and accept:

• Permanence: Blockchain transactions cannot be reversed
• Public visibility: All on-chain data is public on public blockchains; private blockchain deployments available on request
• Network dependency: We don't control blockchain networks
• Economic risks: Token values may fluctuate dramatically
• Technical risks: Smart contracts may have zero-day bugs
• Regulatory risks: Laws may change rapidly
• Integration risks: Third-party services may fail

7.2 No Custody or Control

We explicitly:

• Don't hold private keys
• Can't recover lost keys
• Don't control your assets
• Can't reverse transactions
• Won't act as custodian
• Don't manage investor funds
• Can't guarantee exchange listings

7.3 Forks and Network Changes

In case of network forks:

• We'll follow majority consensus
• No obligation to support minority chains
• You may lose access to forked assets
• Service interruption possible
• Securities may require re-registration

8.1 Available Tools

• Transaction screening
• KYT/AML at Wallet level (through DFNS)
• Sanctions list checking
• Travel rule compliance
• Regulatory reporting templates
• Investor verification (Persona integration)
• Accreditation checking (Persona)
• Transfer restriction enforcement

8.2 Tool Limitations

• You remain responsible for compliance
• Tools provide assistance, not guarantee
• False positives possible
• Regular updates required
• Third-party service dependencies

9.1 Uptime Targets

• API availability: 99.9%
• Dashboard access: 99.5%
• Support response: Per plan
• Third-party integrations: Best effort

9.2 Exclusions

SLA doesn't cover:

• Blockchain network issues
• Gas price spikes
• Network congestion
• Fork-related downtime
• Scheduled maintenance
• Third-party service outages

10.1 Prohibited Activities

Don't use our services for:

• Mixer/tumbler services
• Wash trading or market manipulation
• Flash loan attacks
• MEV exploitation (harmful)
• Spam token creation
• Unregistered securities offerings
• Non-compliant fund structures

10.2 Rate Limits

Abuse prevention limits:

• 2 deployments per day per domain
• 20 active fund/deal tokens per account (additional funds available on request)
• 1M API calls per day
• Custom limits available
• Securities tokens: Additional review required

11.1 Required Integrations

For securities tokenization, you must use:

• DFNS: For MPC wallet infrastructure
• Bridge.xyz/HiFi: For fiat on/off ramps
• MTN: For tokenized deposit based transactions
• Persona: For identity verification backend
• 1Transfer: For transfer agent services (where applicable)

11.2 Integration Support

• API documentation provided
• Sandbox environments available
• Technical support included
• Custom integration assistance (Enterprise only)