1. Scope and acceptance
These Terms of Service govern access to oraclizer.io and the public research, specifications, documentation links, and project information presented on it. By using the website, you agree to these terms. If you do not agree, do not use the website.
Future software, APIs, networks, developer programs, commercial services, or test environments may be governed by separate terms. Nothing on this website grants access to any such service.
2. Research and project status
Oraclizer is a developing project. Materials may describe proposed standards, research models, planned components, test work, or architecture under development. A paper, specification, machine-checked model, test result, and deployed production system are different forms of evidence and must not be treated as interchangeable.
Roadmaps, planned features, working titles, and technical designs may change. Unless a page expressly states otherwise and provides a verifiable source, the website does not represent that a product is production-ready, audited, legally compliant, or generally available.
3. No professional advice
The website is provided for general technical and research information. It does not provide legal, regulatory, tax, accounting, financial, investment, or other professional advice. Regulatory frameworks and token standards discussed on the website do not certify compliance in any jurisdiction.
You are responsible for obtaining qualified advice and evaluating the legal, technical, security, and financial risks of any action you take.
4. Acceptable use
You may use the website only for lawful purposes. You must not:
- interfere with the operation or security of the website;
- attempt unauthorized access to systems or accounts;
- use automated traffic in a way that degrades availability;
- misrepresent Oraclizer research, affiliation, endorsement, or project status; or
- use the website to violate applicable law or the rights of another person.
5. Intellectual property and public artifacts
The website design, branding, and original site content are protected by applicable intellectual-property laws. Public repositories, papers, specifications, and third-party materials remain subject to the licenses and notices stated at their source.
A link to an open repository or paper does not replace its license. Where a repository license and these website terms differ, the repository license governs use of that repository’s materials.
6. Third-party links
The website links to documentation, research hosts, code repositories, standards discussions, social platforms, and other third-party services. Those services have their own terms and privacy practices. Oraclizer is not responsible for their availability, content, security, or policies.
A reference or link does not by itself imply partnership, sponsorship, approval, or endorsement.
7. Disclaimer
The website and its content are provided on an “as is” and “as available” basis. To the fullest extent permitted by law, no warranty is made that the website will be uninterrupted, error-free, complete, current, secure, or suitable for a particular purpose.
Technical descriptions may contain limitations, assumptions, or unresolved implementation work. You must independently verify any material before relying on it.
8. Limitation of liability
To the fullest extent permitted by applicable law, Oraclizer will not be liable for indirect, incidental, special, consequential, or punitive loss arising from use of, inability to use, or reliance on this informational website or a linked third-party service.
Some jurisdictions do not permit certain limitations. In that case, the limitation applies only to the extent permitted by law.
9. Changes
These terms may be updated to reflect changes to the website, applicable law, or the scope of the project. The date shown at the top identifies the current version. Continued use of the website after an update means you accept the updated terms.
10. Contact
General, technical, research, and standards inquiries may be sent through the contact form on the Oraclizer homepage.