Editorial Guidelines
Our Mission
Blockport provides technical reporting on blockchain infrastructure for engineers, developers, and technical decision-makers. We focus on what can be measured, verified, or reproduced – not on industry narratives. Our work reflects engineering reality and documented behavior, not promotional angles.
Editorial Independence
How We Separate Editorial and Business
Technical reviews are written independently of business partnerships. Engineers working on evaluations do not participate in advertising discussions and do not see partner lists.
In practice this means:
- All platforms go through the same testing workflow.
- Business relationships do not change test parameters or performance scoring.
- If an affiliate partner underperforms, their results are published without modification.
Affiliate Relationships
Some platforms have affiliate agreements with Blockport. These help fund our testing infrastructure, but they do not influence which products we review or how we score them. Platforms that are not partners receive the same technical evaluation. Any affiliate relationship is disclosed clearly.
Content Standards
Technical Verification
Every performance claim, specification, or architectural description is checked through hands-on testing or reliable technical documentation.
We verify through:
- Direct measurement: latency, throughput, API limits, stress tests
- Code review (for open-source components)
- Infrastructure testing: node deployments, validator behavior, load scenarios
- Documentation analysis to confirm consistency between claims and observed behavior
Source Hierarchy
We prioritize:
- Protocol documentation, open-source repositories, and our own measurements
- Third-party audits, academic papers, and vetted technical research
- Company claims – only after independent verification
- Community reports – treated as early signals, never as final evidence
Corrections and Updates
Technical issues are corrected as soon as they are found.
- Minor issues (typos, formatting) are fixed silently.
- Specification corrections include an editor’s note.
- Major inaccuracies get a dedicated correction notice.
Readers can report issues at [email protected]. Substantive reports are reviewed within 24 hours.
Content Categories
Technical Analysis
Our infrastructure assessments examine architecture, performance, security design, and operational behavior. Distinctions between expected and observed performance are documented clearly.
Protocol Reviews
Protocol reviews cover consensus design, validator requirements, upgrade paths, and real-world behavior. We verify claims independently and rely on long-term network observations where possible.
Security Assessments
We evaluate audit history, code quality, incident response, and available security guarantees. Marketing claims are disregarded unless backed by implementation details.
Performance Testing
Latency, throughput, availability, and load behavior are measured in controlled environments. Tests are documented so others can reproduce the results if needed.
Our Team
Blockport’s editorial staff includes engineers, infrastructure specialists, and security researchers. Team members run nodes, audit smart contracts, contribute to open-source projects, and maintain production workloads.
A Technical Editor oversees content quality and ensures adherence to engineering standards. Editorial and business operations remain separate.
External contributors must disclose relevant technical affiliations and comply with our verification rules.
Coverage Approach
We Cover
- Blockchain infrastructure and consensus mechanisms
- Smart contract platforms and execution environments
- Layer-2 systems and scaling technologies
- Developer tooling and APIs
- Security infrastructure and key-management systems
We Approach Critically
- Performance claims that cannot be reproduced
- Security marketing without implementation evidence
- Scalability claims based on theoretical maximums
We Do Not Cover
- Claims we cannot verify
- Closed-source critical components without transparency
- Pure marketing narratives
Conflict of Interest Policy
Team members may hold assets in protocols they do not directly cover.
Holdings in covered protocols must be disclosed, and editors recuse themselves when conflicts arise.
No trading is allowed based on unpublished findings.
Open-source contributions are disclosed when relevant. Consulting work requires full recusal.
Technical Standards
We document our testing environment and update it when infrastructure changes. Benchmarks include methodology details to enable reproduction.
Assessments specify protocol versions, client implementations, and network conditions. Updates identify when version changes affect earlier findings.
Platforms may contest results with evidence; verified counter-data is incorporated into updates.
Our Commitment
We prioritize technical accuracy ahead of marketing convenience. Blockchain infrastructure requires rigorous testing and honest reporting – and that is the standard we follow.
Last Updated: 20/11/2025
