警告:您可能成为了企图假冒本网站内容的目标。 我们检测到该网站被IFRAME包裹,这意味着与EOS Canada无关的人试图向您展示他们的内容与我们的内容相关,可能为了让您相信他们与EOS Canada有关。 我们与任何试图这样做的组织都没有联系,它也没有受到我们的认可



WARNING: you may have been the target of an attempt to misrepresent the content of this site. We detected that the site was wrapped in an IFRAME, which means that someone else, not associated with EOS Canada, attempted to show you their content combined in some way with ours, possibly to make you believe they are associated with EOS Canada. We are not associated with, and do not endorse, any organization attempting to do this.
background-flotant-top-right-01

Blog: EOS Block Producer Tips & News

background-flotant-top-left-01

EOS Canada is Shutting Down its EOS Mainnet Block Producer Operations to Focus on dfuse

April 24, 2020 / by EOS Canada

Today is a historical day in the history of EOS Canada. We have decided to shut down our Block Producer operations on EOS Mainnet, to solely focus on the development of dfuse, the open source blockchain data stack. We signed the unregprod action in this transaction, dated April 24th 2020, 11:57am.

As we look back on the nearly two years since the EOS mainnet launch, we feel a sense of accomplishment regarding our achievements and contributions to the ecosystem. From orchestrating the EOS-BIOS boot stages with hundreds of aspiring Block Producers, contributing important pieces of open source code to the community (eos-go, eosc, eos-bios, eosio.forum, pitreos), building our powerful block explorer eosq, herding cats on Zoom calls, to being the #1 Block Producer when the EOS Mainnet was launched and activated.

 

EOS Canada is shutting down

 

This is not the end of the journey for our team as we will now focus 100% on expanding the dfuse platform, the most powerful blockchain data stack in the industry. After starting initially as an internal solution for the EOS Mainnet, dfuse has now been deployed on many EOSIO and Ethereum chains, with other protocols under active development. dfuse provides the massively scalable infrastructure needed for hundreds of public and private deployments, including exchanges, trading operations, interactive games, social media platforms, supply chain solutions, and high throughput regulated environments. We have recently announced open sourcing dfuse for EOSIO, with Block.one integrating it into EOSIO, and we have released it into the hands of developers everywhere!

All developers, please note: In approximately 48 hours from this post being published, the public API and peer-to-peer endpoints offered by EOS Canada will be taken offline. We encourage you, if you haven't already, to take a look at our offering through dfuse to provide your backend with the most robust and reliable APIs available. If you would like to speak to us about migrating to dfuse, we would be thrilled to help you. Please reach out in the dfuse EOS Telegram group and we'll help to get you switched over to ensure a smooth and seamless transition for your application. To avoid any possible confusion, we want to specify that the dfuse API offering will not be effected.

All the great content we’ve contributed since 2018 will remain available on the EOS Canada website. This includes our open source contributions, educational blog posts, funny and informative videos, the ABC of EOS, and much more. While we will maintain our EOS Canada social media presence, we encourage you to follow us on our dfuse social media channels for the latest from the EOS Canada team (Telegram, Twitter)! Make sure to also show your love of dfuse by starring the dfuse for EOSIO repository.

We want to take this opportunity to please remind everyone who is currently voting for eoscanadacom to revisit their votes and consider many of the incredible teams who are working so hard as Block Producers.

Topics: Block Producer, EOS Mainnet, dfuse

EOS Canada

Written by EOS Canada

dfuse - Template Blog Post Thumbnail-5

Building on EOSIO?

Develop your project with dfuse, the most powerful blockchain API.

BUILD NOW

cubes-solid

ABCs of EOS

A glossary of terms that every EOS user should know.

MORE