Introduction & Definitions

These Terms of Service (“Terms”) govern your access to and use of the Oraclizer services, including the Oracle State Machine, Oracle Caster, and all associated APIs, software, tools, and documentation (collectively, the “Services”) provided by Oraclizer (“we,” “us,” or “our”). By accessing or using our Services, you agree to be bound by these Terms.

Definitions

“Oraclizer” refers to the Oracle State Machine and its associated services, including but not limited to state synchronization technology, RWA tokenization solutions, and cross-chain integration protocols.

“Oracle State Machine” means our proprietary state synchronization technology that enables complete state synchronization between on-chain and off-chain (even non-blockchain) oracle segments.

“State Synchronization” refers to the process of maintaining consistent states across different systems, chains, and protocols through our L3 zkRollup infrastructure.

“RWA” (Real World Assets) means any physical or traditional financial assets that can be tokenized through our platform.

“Services” includes:

• The Oracle State Machine technology
• Oracle Caster RWA tokenization platform
• Oracle Interoperability Protocol (OIP)
• Associated APIs and development tools
• Documentation and technical resources
• Any other features, content, or applications offered by Oraclizer

“User,” “you,” or “your” refers to any individual or entity that accesses or uses our Services, including but not limited to developers, enterprises, financial institutions, and gaming companies.

“API” means the application programming interfaces provided by Oraclizer that allow users to integrate our Services into their applications.

“Regulatory Compliance Protocol (RCP)” refers to our standardized protocol that ensures regulatory compliance across tokenized capital markets.

“Documentation” means any technical and operational specifications, security protocols, APIs, or other documentation that we make available to you.

“Platform” refers to all websites, interfaces, and applications operated by Oraclizer through which the Services are provided.

By using our Services, you acknowledge that you have read, understood, and agree to be bound by these definitions and the entirety of these Terms. These Terms constitute a legally binding agreement between you and Oraclizer regarding your use of the Services.

Service Description

Core Services

Oracle State Machine

The Oracle State Machine represents our foundational technology, providing comprehensive state synchronization across diverse systems. The service:

• Enables bidirectional state synchronization between on-cha8in and off-chain systems
• Implements L3 zkRollup architecture for cost-efficient operations
• Ensures regulatory compliance through built-in RCP framework
• Maintains state consistency through decentralized sequencer design
• Provides automated state verification and validation mechanisms

Oracle Caster

Our RWA tokenization platform built on DAML ledger and CANTON protocol:

• Facilitates regulatory-compliant tokenization of real-world assets
• Supports both financial and gaming asset tokenization
• Implements complete state synchronization contracts
• Ensures privacy and security through zk-basis ID
• Enables seamless integration with external systems through standardized interfaces

Oracle Interoperability Protocol (OIP)

The OIP serves as the central nervous system of Oraclizer, providing:

• Cross-chain state synchronization between EVM and non-EVM systems
• Standardized protocol inheriting RCP specifications
• Complete asset mobility with traceability
• Privacy-preserving transaction management
• Regulatory enforcement mechanisms

Technical Infrastructure

L3 zkRollup Infrastructure

• Scalable operational strategy through modular design
• Optimized gas fee structure through double compression
• Decentralized sequencer implementation
• Enhanced security through multi-layered zk proof structure
• Efficient state transition verification

State Synchronization Mechanism

• Real-time state consistency maintenance
• Automated verification of state transitions
• Rollback mechanisms for regulatory enforcement
• Cross-chain message routing and validation
• Preemptive lock mechanisms for double-spending prevention

Security and Compliance

• Implementation of Regulatory Compliance Protocol (RCP)
• System-wide AML integration
• Privacy-preserving KYC mechanisms
• Regulatory enforcement capabilities
• Emergency intervention protocols

Service Limitations and Conditions

• Service availability subject to network conditions
• Processing times dependent on blockchain network congestion
• API rate limits and usage restrictions
• Regulatory compliance requirements
• Technical integration prerequisites

Oraclizer reserves the right to modify, suspend, or discontinue any aspect of the Services at any time. Users will be notified of significant changes through our official communication channels.

User Obligations

General Obligations

Compliance Requirements

• Adhere to all applicable laws and regulations in your jurisdiction
• Comply with Oraclizer’s Regulatory Compliance Protocol (RCP) standards
• Maintain necessary licenses and permissions for your intended use
• Implement required regulatory controls and reporting mechanisms
• Follow all prescribed KYC and AML procedures

Technical Requirements

• Maintain secure and up-to-date integration environments
• Properly implement all required security protocols
• Follow provided technical specifications and guidelines
• Regularly update to supported versions of APIs and SDKs
• Monitor and maintain adequate system resources

Use Restrictions

Users shall not:

• Attempt to circumvent or disable any security features
• Reverse engineer or decompile any part of the Services
• Access the Services through unauthorized interfaces
• Exceed prescribed API rate limits or usage quotas
• Share access credentials or API keys
• Create unauthorized derivative works
• Attempt to bypass state synchronization mechanisms

Integration Obligations

Implementation Requirements

• Follow official implementation guidelines
• Use only documented APIs and interfaces
• Maintain proper error handling mechanisms
• Implement appropriate fallback procedures
• Regular testing of integration points
• Maintain adequate technical documentation

State Synchronization Responsibilities

• Proper implementation of state transition logic
• Accurate handling of synchronization events
• Maintenance of state consistency
• Proper implementation of rollback mechanisms
• Regular verification of state accuracy

Security Obligations

• Secure storage of access credentials
• Protection of API keys and sensitive data
• Regular security audits of implementations
• Prompt reporting of security incidents
• Implementation of required encryption standards

Operational Requirements

Monitoring and Maintenance

• Regular monitoring of service integration
• Timely response to system alerts
• Maintenance of adequate logs
• Regular backup of critical data
• Performance monitoring and optimization

Incident Response

• Prompt reporting of service issues
• Cooperation in incident investigations
• Maintenance of incident response procedures
• Documentation of significant events
• Implementation of prescribed remediation measures

Communication Requirements

• Maintain current contact information
• Respond to service-related communications
• Provide notice of significant changes
• Report compliance-related matters
• Participate in required security assessments

Financial Obligations

Service Usage

• Payment of applicable service fees
• Maintenance of valid payment methods
• Compliance with pricing terms
• Proper handling of transaction fees
• Timely resolution of payment issues

Liability

• Responsibility for unauthorized use
• Acceptance of specified service limits
• Compliance with indemnification terms
• Maintenance of required insurance
• Acceptance of liability limitations

Failure to comply with these obligations may result in service suspension or termination. Oraclizer reserves the right to modify these obligations with reasonable notice to users.

API Usage Terms

Access and Authentication

API Key Management

Users granted access to Oraclizer APIs are responsible for the secure management of their API credentials. This includes maintaining the confidentiality of API keys and access tokens, implementing secure storage practices, and promptly reporting any potential security breaches. API keys must not be shared, published, or otherwise exposed to unauthorized parties.

Rate Limiting and Resource Usage

Oraclizer implements rate limiting and resource usage restrictions to ensure service stability and fair usage across all users. These limits are monitored and enforced at both the account and IP address levels. Users must implement appropriate handling of rate limit responses and maintain their usage within prescribed boundaries. Excessive or abusive usage patterns may result in temporary or permanent suspension of API access.

Service Level Commitments

While Oraclizer strives to maintain high availability and performance of our APIs, we provide our API services on an “as is” and “as available” basis. Users should implement appropriate error handling and retry mechanisms in their applications. We reserve the right to modify, suspend, or discontinue any API functionality with appropriate notice to users.

Integration Requirements

Implementation Standards

Users integrating with Oraclizer APIs must adhere to our implementation guidelines and best practices. This includes proper error handling, maintaining appropriate timeout configurations, implementing exponential backoff strategies for retries, and following our recommended security practices. Users must ensure their implementations can appropriately handle API updates and version changes.

State Synchronization Integration

When implementing state synchronization through our APIs, users must:

• Properly handle state transition events
• Implement complete error handling for synchronization failures
• Maintain appropriate logging of synchronization activities
• Follow prescribed patterns for state conflict resolution
• Implement proper rollback mechanisms where required

Version Management

Users are required to maintain compatibility with supported API versions and migrate to newer versions within communicated deprecation timeframes. While we strive to maintain backward compatibility where possible, users should be prepared to update their implementations as required to maintain service functionality.

Security Requirements

Data Protection

Users must implement appropriate security measures to protect any data transmitted through or received from our APIs. This includes implementing encryption for data in transit, secure storage of received data, and appropriate access controls within their applications.

Compliance Integration

Users implementing regulatory compliance features through our APIs must:

• Correctly implement all required compliance checks
• Maintain appropriate audit trails of compliance-related activities
• Properly handle and store compliance-related data
• Follow prescribed procedures for regulatory reporting
• Implement required monitoring and alerting systems

Incident Reporting

Users must promptly report any security incidents or vulnerabilities discovered in our APIs through appropriate channels. This includes potential exploits, unexpected behaviors, or security weaknesses that could impact the integrity or security of the service.

Usage Restrictions

Users of Oraclizer APIs shall not:

• Attempt to bypass or modify any security measures
• Use the APIs in any way that could damage or overload our systems
• Implement functionality that could compromise the integrity of state synchronization
• Create unauthorized derivative services
• Use the APIs for any illegal or prohibited purpose
• Share or redistribute API access without authorization
• Attempt to reverse engineer API functionality

Oraclizer reserves the right to monitor API usage and suspend access for violations of these terms. We may modify these API Usage Terms at any time, with updates being effective upon posting to our documentation or direct notification to users.

Limitation of Liability

Scope of Liability

Oraclizer, while striving to provide reliable and secure services, expressly limits its liability as follows:

Service Performance

We provide our services, including the Oracle State Machine, Oracle Caster, and associated APIs, on an “as is” and “as available” basis. While we implement robust technology including L3 zkRollup architecture and state synchronization mechanisms, we cannot guarantee uninterrupted, error-free operation. We are not liable for any delays, inaccuracies, errors, or service interruptions that may occur.

State Synchronization

Despite implementing comprehensive verification and validation mechanisms, Oraclizer cannot be held liable for:

• Losses arising from state synchronization delays or failures
• Consequences of network congestion or blockchain network issues
• Damages resulting from state inconsistencies beyond our direct control
• Issues arising from external system integrations
• Losses due to regulatory compliance verification delays

Financial and Economic Losses

Users acknowledge and agree that Oraclizer shall not be liable for:

• Direct, indirect, or consequential financial losses
• Lost profits or business opportunities
• Damages resulting from market conditions or volatility
• Losses from trading or investment decisions
• Costs associated with system integration or migration

Technical Integration

We accept no liability for:

• Issues arising from improper implementation of our APIs
• Damages resulting from misuse of our services
• Losses due to inadequate security measures on the user’s part
• Problems arising from failure to maintain current software versions
• Consequences of exceeding API rate limits or usage quotas

Maximum Liability

If, despite the limitations above, Oraclizer is found liable for damages, our total aggregate liability shall not exceed:

• The amount paid by the user for our services in the twelve months preceding the incident, or
• In the case of free services, the equivalent of $100 USD

Force Majeure

Oraclizer shall not be liable for any failure or delay in performance caused by circumstances beyond our reasonable control, including but not limited to:

• Network or blockchain infrastructure issues
• Regulatory changes or enforcement actions
• Cyber attacks or security breaches
• Natural disasters or acts of God
• Global market disruptions
• Changes in laws or regulations affecting blockchain technology

Indemnification

Users agree to indemnify and hold harmless Oraclizer, its officers, directors, employees, and agents from any claims, damages, losses, or expenses arising from:

• Violation of these Terms
• Improper use of our services
• Breach of regulatory requirements
• Infringement of third-party rights
• Integration with external systems or services

Disclaimer of Warranties

Except as expressly stated in these Terms, Oraclizer makes no warranties, express or implied, regarding our services, including but not limited to:

• Merchantability
• Fitness for a particular purpose
• Non-infringement
• Accuracy of data
• Regulatory compliance outcomes

This limitation of liability section shall apply to the fullest extent permitted by applicable law.

Regulatory Compliance

Regulatory Framework

Oraclizer has developed and implements the Regulatory Compliance Protocol (RCP), which standardizes regulatory requirements from global financial regulatory authorities. Users of our services acknowledge and agree to operate within this comprehensive regulatory framework.

Compliance Standards

Through RCP integration, users must adhere to:

• All applicable financial regulations in their jurisdictions
• Cross-border transaction requirements
• Anti-Money Laundering (AML) regulations
• Know Your Customer (KYC) requirements
• Data privacy and protection standards
• Asset-specific regulatory requirements

Financial Regulatory Compliance

Our services incorporate regulatory compliance mechanisms for:

• Asset tokenization processes
• Cross-chain state synchronization
• Transaction monitoring and reporting
• Regulatory reporting requirements
• Emergency regulatory interventions
• Compliance audit requirements

Built-in Compliance Mechanisms

State Machine Compliance

The Oracle State Machine implements:

• Automated compliance verification
• Regulatory-aware state transitions
• Compliant cross-chain operations
• Auditable state synchronization
• Regulatory enforcement capabilities

RWA Tokenization Compliance

Oracle Caster ensures:

• Regulatory-compliant asset tokenization
• Compliant token issuance procedures
• Proper asset classification
• Required regulatory disclosures
• Ongoing compliance monitoring

Cross-Chain Compliance

Our services maintain regulatory compliance across:

• Multiple blockchain networks
• Different jurisdictions
• Various asset classes
• Different regulatory frameworks
• Cross-border transactions

User Compliance Obligations

Documentation Requirements

Users must maintain:

• Complete transaction records
• Compliance documentation
• Audit trails
• Required regulatory filings
• Incident reports

Reporting Obligations

Users are required to:

• Report suspicious activities
• Maintain required compliance logs
• Submit regulatory reports as required
• Cooperate with compliance audits
• Provide regulatory documentation upon request

Compliance Updates

Users must:

• Stay informed of regulatory changes
• Implement required compliance updates
• Maintain current compliance standards
• Adapt to new regulatory requirements
• Update compliance procedures as needed

Regulatory Enforcement

Enforcement Mechanisms

Oraclizer maintains the right to:

• Enforce regulatory requirements
• Suspend non-compliant operations
• Implement emergency stops
• Report violations to authorities
• Terminate service for non-compliance

Automated Enforcement

Our systems implement:

• Automated compliance checks
• Real-time monitoring
• Violation detection
• Automated reporting
• Emergency intervention protocols

Compliance Modifications

Oraclizer reserves the right to modify compliance requirements as needed to:

• Meet new regulatory requirements
• Implement enhanced compliance measures
• Adapt to regulatory changes
• Improve compliance mechanisms
• Address emerging regulatory concerns

Users acknowledge that compliance with these requirements is mandatory for continued use of our services.

Intellectual Property Rights

Ownership and Rights

Oraclizer Intellectual Property

Oraclizer retains all rights, title, and interest in:

• The Oracle State Machine technology and architecture
• All proprietary algorithms and protocols
• The L3 zkRollup implementation
• The Regulatory Compliance Protocol (RCP)
• All software, APIs, and documentation
• All related patents, trademarks, and trade secrets
• All improvements and derivative works

Protected Materials

Our intellectual property includes:

• Source code and object code
• Technical documentation and specifications
• API designs and implementations
• Architecture diagrams and workflows
• Research papers and technical publications
• User interfaces and designs
• Branding and marketing materials

Permitted Use

License Grant

Users are granted a limited, non-exclusive, non-transferable license to:

• Access and use our services as provided
• Implement our APIs according to documentation
• Integrate our services into their applications
• Use our documentation for implementation
• Display our trademarks as authorized

Restrictions

Users may not:

• Modify or create derivative works
• Reverse engineer our technology
• Remove or modify any proprietary notices
• Transfer or sublicense access rights
• Use our IP for competing services
• Patent any features based on our technology

User-Generated Content

User Rights

Users retain ownership of:

• Their original implementation code
• Custom integrations
• Original documentation
• Custom configurations
• Application-specific modifications

License to Oraclizer

Users grant Oraclizer a license to:

• Use feedback for service improvement
• Incorporate suggested features
• Use usage data for optimization
• Share anonymized performance metrics
• Document implementation examples

Third-Party Rights

Third-Party Technology

Users acknowledge that our services may incorporate:

• Open-source components
• Licensed third-party technology
• Industry standard protocols
• Public blockchain technology
• External APIs and services

Compliance Requirements

Users must:

• Respect third-party intellectual property rights
• Comply with open-source license terms
• Maintain required attributions
• Adhere to usage restrictions
• Report any potential violations

Enforcement

IP Protection

Oraclizer reserves the right to:

• Enforce its intellectual property rights
• Investigate potential violations
• Take legal action when necessary
• Terminate access for violations
• Require removal of infringing content

Cooperation Requirements

Users agree to:

• Promptly report IP violations
• Assist in violation investigations
• Implement required remediation
• Maintain required records
• Cooperate with enforcement actions

DISCLAIMER

General Disclaimer

No Warranties

TO THE MAXIMUM EXTENT PERMITTED BY LAW, ORACLIZER AND ITS SERVICES ARE PROVIDED “AS IS” AND “AS AVAILABLE” WITHOUT WARRANTIES OF ANY KIND, WHETHER EXPRESS, IMPLIED, OR STATUTORY. ORACLIZER SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES OF:

• MERCHANTABILITY
• FITNESS FOR A PARTICULAR PURPOSE
• TITLE
• NON-INFRINGEMENT
• ACCURACY
• SYSTEM INTEGRATION
• QUIET ENJOYMENT

Technology Risks

Users explicitly acknowledge and accept:

• Blockchain technology risks
• Cryptographic technology risks
• Smart contract risks
• Network and connectivity risks
• Protocol and consensus risks
• Regulatory and compliance risks

Specific Disclaimers

Service Performance

Oraclizer does not warrant that:

• Services will be uninterrupted
• State synchronization will be instantaneous
• All operations will be successful
• Systems will be error-free
• All bugs will be corrected
• Data will never be lost

Financial and Economic

We make no representations regarding:

• Investment outcomes
• Economic benefits
• Market performance
• Asset valuations
• Trading results
• Financial returns

Technical Integration

We do not guarantee:

• Compatibility with all systems
• Perfect integration outcomes
• Optimal performance
• Zero downtime
• Complete security
• Universal protocol compatibility

Risk Acknowledgment

Blockchain Risks

Users acknowledge inherent risks in:

• Blockchain technology
• Cryptographic systems
• Distributed networks
• Consensus mechanisms
• Smart contract execution
• Cross-chain operations

Regulatory Risks

Users understand:

• Regulatory frameworks may change
• Compliance requirements may evolve
• New regulations may emerge
• Regulatory actions may occur
• Legal interpretations may vary

No Professional Advice

Not Financial Advice

Our services and documentation do not constitute:

• Investment advice
• Financial recommendations
• Trading guidance
• Asset management advice
• Economic consulting
• Professional financial services

Not Legal Advice

We do not provide:

• Legal counsel
• Regulatory advice
• Compliance consulting
• Policy recommendations
• Legislative interpretation

Modifications to Terms

Changes to Terms

Oraclizer reserves the right to modify these Terms at any time. Changes will be effective upon posting to our website or direct notification to users. Modifications may be made to:

• Reflect service changes
• Accommodate new features
• Address regulatory requirements
• Improve clarity
• Update security requirements

Notice of Changes

• Material changes will be communicated directly to users
• Updates will be posted with clear revision dates
• Change notifications will include summary of modifications
• Users will be given reasonable time to review
• Critical updates may require immediate implementation

Continued Use

Your continued use of Oraclizer services after changes become effective constitutes acceptance of the modified Terms. If you do not agree to the modified Terms, you must discontinue use of our services.

Contact Information

Official Communications

For formal notices related to these Terms:

Technical Support

For technical issues and support: [dev@oraclizer.io]

General Inquiries

For general questions and information: [biz@oraclizer.io]