Alexei Papou
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    --- tags: Research --- # Industry Peers' Marketing and Content ## What Is This About? To better understand how the media and content are developing in the cryptospace, we decided to answer three questions about our colleagues in the blockchain industry: * What kind of content are they creating? * Who are they creating this content for? * Why are they creating this content? For the analysis we chose five colleagues from the industry: [Binance Smart Chain (BSC)](https://www.binance.org/en/smartChain), [Polygon](https://polygon.technology/), [Arbitrum](https://arbitrum.io/), [Optimism](https://optimism.io/), and [Matter Labs](https://matter-labs.io/). We chose BSC and Polygon as sidechain solutions, while Arbitrum, Optimism, and Matter Labs represent L2 solutions. This was made to test an assumption that the marketing strategies are different across various approaches. To answer the first question we examined the topics and type of content of the five peers. To answer the second question we studied the target audience of their posts. To answer the third question we tried to identify the messaging they were putting into their posts. The analysis started with Twitter posts but went far beyond, as the projects are constantly tweeting links to other content platforms (Medium, YouTube, blog, etc.). We examined about 100 posts of each project around their Mainnet pre-launch or launch stage. ## What Peers Are Posting The most popular topic our peers create content about is tech development. This is basically the only topic that is extensively covered by all five projects. Unsurprisingly, everyone loves to share their tech achievements in this open source environment. Below is the chart of the topics covered. ![Content Topic](https://i.imgur.com/NP9WKMq.png) Everyone creates a lot of content about engineering and development. Matter Labs are really excited about zero-knowledge proof methods and like to share their thoughts about it. It is worth mentioning that in the past month BSC increased the amount of gaming/NFT content to 23% of total content, which is not reflected in this chart. Optimism and Matter Labs virtually don’t post about DeFi. Are we all that nerdy about technologies? Yes, actually, which is cool. This is the developers’ sphere, after all. However, Optimism stand out in terms of the entertaining content they are posting. They like to share memes, funny photos of their team working in the office, or even don’t mind doing a freestyle rap about Plasma chains. Then we explored the type of content the five projects were creating. We expected that blog posts would take the most of their effort. The chart below shows the types of media platforms the projects were using the most. ![Content Type](https://i.imgur.com/KcWSBs2.png) Expectedly, blog and Medium posts take a substantial amount of content space for each project. Interestingly, Polygon is rather active creating videos and live sessions. About one third of those live sessions were related to the Gaming and NFTs topic, and another third covered DeFi. BSC really likes infographics and animation, mostly creating data visualizations of their achievements and ecosystem growth. Arbitrum did the most AMAs as a percentage of their total posts, answering the questions about technology, DeFi, as well as covering general topics. ## Who Are They Posting For? We identified five broad categories of audiences each project was targeting. * By **traders** we meant all posts about crypto trading and DeFi. In this research there was no differentiation between crypto whales, speculators and DeFi degens. * **Developers** included engineers who might be interested in all kinds of tech topics. * **Gamers, artists and users** are pretty self explanatory: people who care about blockchain gaming, NFTs, DApps on social networking, recruiting, etc. * **Community** is a broader category where the projects didn’t target any specific type of their audience, but rather addressed the community in general. * **Validators** category is obviously related to staking, but it is only relevant for BSC in this context. ![](https://i.imgur.com/yPanuBm.png) As we can see in the chart, the focus of Matter Labs on developers stands out. Again, they are really excited about the ZK-SNARKs and ZKP-secured rollups, and we appreciate their effort to share the excitement with all of us. Polygon seems to be the most diversified in terms of their target audience. Also, it was the only project which cared about gamers and artists around their mainnet launch. Meanwhile, Optimism paid the most attention to the community. We remember that they like entertaining content, which is obviously community-driven rather than addresses any specific audience. ## Why Are They Posting It? We tried to capture the message of every post or tweet each project was delivering, which is not a trivial task. However, the qualitative analysis revealed that there was one single message that absolutely every blockchain colleague was trying to communicate. > We are growing. Well, this message can be attributed to any new project announcement and project update, so it naturally evolves in this fast developing industry. Other common messages included > We support developers and/or > We support traders. It would be more interesting to identify a unique message each team was conveying, wouldn’t it? Well, luckily each project has its distinguishing features and approach to creating content. Here’s what we got. **Polygon**: > We promote mass adoption. Polygon mentioned the term mass adoption multiple times in the context of their contribution to it. Great aspiration, we fully support that idea! **BSC** > We promote security. Binance Smart Chain created a fair amount of content about safety and security, anti-fraud, flash loan attacks, etc. Besides that, BSC likes to ask open-ended questions to the community in their Twitter, showing that they are interested in community opinion. **Arbitrum** > We care about your questions. Arbitrum’s focus on AMAs showed how much they care about educating the community and answering questions. It's nice to be aware of what your followers want to know! **Optimism** > We are open to community. Optimism’s random photos and short videos of their work process and office discussions really tells everybody how open they are to the community. **Matter Labs** > We are smart. Not in a haughty, but rather in an educative way, Matter Labs shared their achievements in winning multiple prizes at hackathons, their progress with polynomial commitment schemes, and explained how they evaluated L2 scaling solutions, emphasizing why zkRollups were the best of them. ## Final Note It was extremely interesting to dive into our blockchain peers’ marketing tactics and content strategy. We wish that we could analyse the engagements (likes + retweets) for different audiences and topics to see what worked best for everyone. However, while likes and retweets are easily accessible, we do not have access to the number of followers at each particular time. This would distort the results, because every post that is published at a later stage naturally gets more engagemenets, as the nubmer of followers increases. Anyway, there are some interesting insights that we hope will help everyone to grow even faster. Obviously, many of the topics which the projects covered were dictated by the partnerships they were entering at that time. Our colleagues followed slightly different strategies, whilst there also were noticeable similarities in their approaches. Everyone likes to build and cares about developers. Everyone loves the blockchain community. Every project chooses topics, messaging and communication channels that most fit their particular ecosystem. We are glad to be in the industry with such great projects and strive to contribute to Web3 growth along with them. [BSC Twitter](https://twitter.com/BinanceChain) [Polygon Twitter](https://twitter.com/0xPolygon) [Arbitrum Twitter](https://twitter.com/arbitrum) [Optimism Twitter](https://twitter.com/optimismPBC) [Matter Labs Twitter](https://twitter.com/the_matter_labs)

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully