Partner Code of Conduct
Purpose
This Partner Code of Conduct establishes technical and operational standards for organizations working with Blockport, including infrastructure providers, exchanges, protocol developers, security auditors, and service providers.
Blockport’s credibility depends on partnerships with organizations meeting documented technical standards, security requirements, and operational transparency. This document defines minimum acceptable standards.
Scope
The Code applies to all partner relationships: advertising partners, affiliate arrangements, data providers, and platforms featured in technical reviews. Partnership implies agreement to these standards and cooperation with verification procedures.
Core Principles
Technical Accuracy
Partners must represent technical specifications, performance characteristics, and security architecture accurately. Claims about throughput, latency, security properties, or protocol capabilities must be verifiable through testing or documentation.
Infrastructure Reliability
Partners must maintain documented uptime standards, implement proper monitoring and alerting, disclose maintenance windows appropriately, and respond to incidents with technical transparency.
Security Standards
Partners must implement industry-standard security practices, undergo regular third-party audits, disclose vulnerabilities responsibly, and maintain documented incident response procedures.
Operational Transparency
Partners must document technical architecture, publish clear API specifications, maintain accurate status pages, and disclose material infrastructure changes affecting users or integrations.
Specific Requirements for Infrastructure Providers
Technical Documentation
Platforms must provide comprehensive API documentation with versioning, example implementations, rate limit specifications, error code documentation, and SDK availability where applicable. Documentation must remain current with actual implementation.
Performance Standards
Advertised performance metrics (throughput, latency, confirmation times) must be reproducible under documented conditions. Partners must specify testing conditions, provide baseline benchmarks, document performance under load, and disclose limitations affecting real-world performance.
Security Architecture
Infrastructure providers must implement and document key management practices, access control mechanisms, network security architecture, backup and disaster recovery procedures, and security monitoring systems. Third-party security audits should be published when available.
Operational Monitoring
Partners must maintain public status pages showing real-time system health, historical uptime data, planned maintenance schedules, and incident post-mortems. Monitoring must cover critical path dependencies and provide programmatic access to status information.
Requirements for Trading Platforms
Architecture Transparency
Exchanges must document order matching algorithms, custody architecture (hot/cold wallet ratios), database infrastructure and redundancy, API rate limits and throttling policies, and disaster recovery capabilities.
Performance Verification
Trading platforms must support independent verification of order execution latency, trade settlement times, API response times, system behavior under load, and WebSocket/streaming data reliability.
Security Implementation
Platforms must implement multi-signature cold storage for the majority of assets, hardware security modules for key operations, withdrawal authorization workflows, IP whitelisting and access controls, and regular penetration testing with published results.
Marketing Standards
Technical Claims
Marketing materials must accurately represent technical capabilities without overstating performance. Benchmark results must specify testing conditions. Uptime claims must be verifiable against historical data. Security claims require supporting evidence. Comparisons must use consistent methodology.
Prohibited Marketing
Partners cannot misrepresent technical specifications, claim capabilities not yet implemented, imply endorsement beyond stated partnership, present theoretical performance as production reality, or use Blockport brand assets without approval.
Disclosure Requirements
Marketing must disclose material limitations, version-specific information, dependency requirements, network or geographic restrictions, and beta or experimental status where applicable.
Data Standards
Data Accuracy
Partners providing market data, network statistics, or analytics must implement validation procedures, document data collection methodology, maintain historical accuracy, disclose latency in real-time feeds, and correct errors promptly when identified.
API Standards
APIs must maintain consistent data formats, implement proper error handling, provide rate limit information, support standard authentication methods, and maintain backward compatibility or provide migration paths.
Security Incident Response
Disclosure Requirements
Security incidents affecting users or system integrity must be disclosed within documented timeframes. Disclosures should include incident timeline and affected systems, user impact assessment, remediation steps taken, and measures preventing recurrence.
Coordinated Disclosure
Partners must follow responsible disclosure practices for vulnerabilities, coordinate with affected parties before publication, and provide reasonable time for fixes before public disclosure (except for active exploitation).
Compliance Verification
Technical Audits
Blockport may verify compliance through anonymous testing of public endpoints, performance benchmarking, security assessment, documentation review, and monitoring of public incident reports.
Continuous Monitoring
We monitor technical forums and issue trackers, network performance metrics, status page accuracy, API reliability, and security disclosure channels. Significant technical issues may trigger partnership review.
Reporting Technical Issues
How to Report
Technical concerns or specification misrepresentations can be reported to [email protected] with the subject “Partner Technical Concern.”
Include:
- Partner name and product
- Specific technical claim in question
- Evidence (test results, documentation inconsistencies, reproduction steps)
- Impact on users or technical assessments
- Contact information (can be anonymous)
Investigation Process
Reports receive acknowledgment within 48 hours. Technical claims are verified through testing. Partners receive the opportunity to provide counter-evidence. Findings are published if they affect assessments. The reporter receives feedback when possible.
Consequences of Non-Compliance
Technical Issues
Minor specification discrepancies result in documentation correction requests and re-testing after updates. Moderate issues lead to rating adjustments, published technical errata, and monitoring period for corrections. Severe misrepresentations result in partnership termination, public technical disclosure, and removal from recommendations.
Severe Violations
The following trigger immediate action:
- Intentional misrepresentation of security architecture
- Concealment of critical infrastructure failures
- Fabrication of performance benchmarks
- Undisclosed single points of failure
- Suppression of security vulnerability information
Partner Responsibilities
Technical Disclosure
Partners must notify Blockport within 24 hours of critical infrastructure incidents, security vulnerabilities affecting users, major architecture changes, API deprecations, and planned maintenance affecting availability.
Documentation Maintenance
Partners must keep technical documentation current, update API specifications with implementation changes, maintain accurate performance claims, and publish security audit results promptly.
Amendment and Review
This Code undergoes annual technical review and updates reflecting evolving security standards, infrastructure best practices, protocol developments, and industry technical requirements. Changes are communicated with reasonable notice.
Last Updated: 20/11/2025
Next Review: expected
Our Commitment
Blockport maintains the same technical standards for our own infrastructure that we require from partners. We commit to transparent enforcement based on verifiable technical criteria and fair treatment during dispute resolution.
Questions? Contact [email protected]
