Media Contact

For press inquiries, interview requests, or media partnership opportunities related to Bitroot, please reach out to our team.

Email: [email protected]

When reaching out, please include your name, publication or organization, and a brief description of your request so we can route it to the right person.

We welcome inquiries about: in-depth technical coverage and product walkthroughs, ecosystem partnerships and joint events, speaking invitations for summits, podcasts, and AMAs, and technical briefings on topics like the three-engine architecture or the Bitroot Foundation's grant programs.

Response time: we aim to respond to media inquiries within 2-3 business days. For requests tied to a specific event or publication deadline, please note the deadline in your subject line so we can prioritize accordingly.

Preparing your request: if your coverage involves specific performance figures (TPS, gas fees, finality, and similar), let us know the time range and context you need, and we'll provide the most current, verifiable numbers along with a description of the test environment they came from, so figures aren't quoted out of date or out of context.

Spokespeople and authorization: for consistency, any statement on official positions, the roadmap, or financial matters should be treated as official only when it comes through a written response via this page's contact channel; individual comments from community members or moderators on Discord, Telegram, and similar channels do not represent Bitroot's official position.

Official announcement channels: product updates, security notices, and event information are published first through the official social media accounts linked in the footer. Treat those accounts as the source of truth, and watch out for impersonator accounts posing as official Bitroot channels.

What's typically in a press kit request: journalists writing about Bitroot for the first time often ask for the same starting set of material — a short project description, the three-engine architecture explained at a non-technical level, current network statistics, logo files, and a contact for technical fact-checking. Mentioning in your first email which of these you already have and which you still need helps us get you the rest faster.

Fact-checking technical claims: if a draft references specific numbers — throughput, finality time, gas cost, or EVM compatibility — we're glad to review that section before publication to confirm the figures are current and correctly attributed to their test conditions. This isn't editorial input on your piece, just a check on the technical accuracy of numbers that trace back to us.

Background briefings: for reporters who want context before a launch or a broader feature rather than a quote for a specific story, we can arrange a background conversation with someone from the team, on terms agreed in advance (on the record, on background, or not for attribution, as you prefer).

Conference and event coverage: if you're covering an event where Bitroot has a speaking slot, a booth, or team members attending, reach out ahead of time via this page so we can help arrange interview time on-site rather than trying to coordinate during the event itself.

Language and translation: our team can typically support press inquiries in Chinese and English. If your outlet publishes in another language, let us know and we'll do our best to accommodate, though response times for other languages may be longer.

Community versus press: if your goal is a quick community-facing question rather than a press inquiry — for example, confirming whether a specific announcement is genuinely from Bitroot — the fastest answer usually comes from the official social channels linked in the footer, since our community moderators are online in those channels more continuously than this inbox is monitored outside business hours.

What we generally can't share: to keep information consistent across outlets, we typically don't provide advance access to unannounced roadmap dates, unpublished financial or funding figures, or comment on rumors about the project. If a request falls into one of these categories, we'll let you know rather than leaving it unanswered.

Corrections: if you've already published something about Bitroot and later find that a figure or claim in it has become outdated — for instance, a performance number that has since improved, or a roadmap item that has shipped or changed — we're happy to send an updated figure with sourcing so you can decide whether a correction or update note is warranted on your end.

Analyst and research inquiries: if you're not press but a market researcher, analyst, or academic looking for background on Bitroot's architecture for a report or paper, the same contact channel applies — just note in your message that the request is for research rather than publication, since the kind of detail useful for a technical writeup can differ from what fits a news article.

One more note on turnaround: response times above are a general expectation, not a guarantee, and can run longer around major releases or public holidays; if you haven't heard back within the window noted above, a polite follow-up to the same address is the right move rather than assuming the request was missed.

For brand and logo usage, please see the Bitroot Brand Assets page.