Cryptocurrency News

Clarification on sharing false spot Bitcoin ETF news

aa1373ce e0ee 4341 84fa efb0ca1dc1aa

Dear Cointelegraph readers,

We are incredibly grateful for the support and trust you have placed in our publication over the last 10 years. We strive to deliver the most thoughtful, engaging and impactful news affecting the cryptocurrency space.

Earlier today, during routine coverage, Cointelegraph’s social media team posted a message on X without prior editorial approval stating that the United States Securities and Exchange Commission had approved BlackRock’s iShares spot Bitcoin exchange-traded fund, or ETF. This was false, the result of misinformation. The news lead originated from an unconfirmed screenshot posted by an X user who claimed it was from the Bloomberg Terminal.

Cointelegraph did not ultimately publish an article with this incorrect information, but we deeply regret posting this in error on X and the impact it has caused. An internal investigation revealed that our standard procedure for posting breaking news on social media, wherein sources are required to be verified before posting to social media, was not followed.

The timeline of events is as follows:

13:17:30 UTC: The editorial team was alerted to the rumored news through a Telegram channel that Cointelegraph employees use to discover stories that might be of interest to readers (Figure 1). The full conversation is shared below.

4e99ef14 84ab 41e4 88a9 2e3764030e89
Figure 1
50377b55 5b14 45d1 a089 c7773dd3169e
Figure 2

13:19:27 UTC: Employee 1 reposted the text of the lead shared by a Telegram account that has since been deleted (Figure 2) to an internal Slack channel (Figure 3).

856964f4 07c2 40ba b314 a354cbba4d01
Figure 3, Figure 4

13:24:16 UTC: In an effort to publish the developments as soon as possible, Employee 2 posted the report to X without prior confirmation of the source’s veracity from the editor. This violates Cointelegraph’s social media process, in which source confirmation and editorial approval are required before posting (Figure 4).

13:48:38 UTC: Readers reported the issue to Cointelegraph via social media channels (Figure 5).

7f77a7a7 3efd 4c7e a719 18aa5c9bdc29
Figure 5

13:52:19 UTC: In an internal Cointelegraph chat, Employee 1 flagged that the source could not be located (Figure 6).

2a297611 86f7 428c 9411 5fe98a324587
Figure 6

13:54:14 UTC: Employee 3 from Cointelegraph edited the message on X to clarify that the information was unconfirmed (Figure 7).

770f3036 5fde 49db 9df4 243acb26d5c0
Figure 7

14:03:42 UTC: Cointelegraph reached out to BlackRock and the Bloomberg Terminal and removed the post (Figure 8).

b369f0bf bda2 4ac2 a11c 3ceeaf104551
Figure 8

14:32:23 UTC: After receiving confirmation from BlackRock that the report was incorrect, Cointelegraph retracted the initial tweet and issued the following statement (Figure 9):

9a5e3e02 eb84 4f92 87e5 8d41d8b44ff8
Figure 9

To ensure that something like this does not happen again, the Cointelegraph team is thoroughly auditing and reviewing our social media management processes, especially around the authentication of breaking news before a post can be published. We are having conversations with all of the employees involved, and we will make all necessary structural changes.

This incident reminds the Cointelegraph team that our actions have serious ramifications across the cryptocurrency community. We are committed to learning from these mistakes and adhering to the highest standards of journalism.


The Cointelegraph team

Source link

Rate this post

Leave a Reply

Your email address will not be published. Required fields are marked *