Proxima
  • 🎉Introduction
    • Welcome to Proxima
  • 🌊Streams
    • Overview
    • Quick start
    • Using streams
    • Our streams
      • Block headers
      • New tokens/collections
      • DEX events
      • Exchange rates
      • Private streams
        • Mangrove
        • All ERC20 events
        • All ERC721 events
        • Raw Uniswap events
      • Smart contract's events
    • Understanding streams
    • Architecture
  • 💾Data APIs
    • APIs
      • Fungible tokens
      • Decentralized exchanges
      • Account balances
  • 🚧Maru
    • Introduction
    • Programming Model
    • How Maru works
      • Architecture
      • Dataflow
      • Economics
      • Domain Specific Language
      • Arrangements
      • Open Problems
    • Background Knowledge
      • Multiset Hashes
      • Plonky2
    • Use Cases
      • Lifting Expensive Computation Off-Chain
      • Social Graph Database
      • Indexer
Powered by GitBook
On this page
  • Prerequisites
  • Steps
  • What's next?
  • Rate limiting
  1. Streams

Quick start

PreviousOverviewNextUsing streams

Last updated 1 year ago

The simplest way to consume the stream is using one of the clients. This example will walk you through the process of using a TypeScript client to start consuming a stream.

Prerequisites

  • You have npm or yarn installed on your computer.

  • You can extract data from ZIP archives.

Steps

  • Navigate to the .

  • Choose any stream with a "JSON" label. For example, proxima.eth-main.blocks.1_0

  • Click on it to get to the .

  • Under "Details" click the "Download Consumer App" button. It will download a zip archive with a sample TypeScript application that uses our client to read the chosen stream.

  • Unzip the downloaded archive into a separate folder and cd to it.

  • Run npm install or yarn install

  • Run npm run build or yarn build

  • Run npm run start or yarn start

You should see a bunch of stream events printed to your console as the client reads them.

What's next?

Rate limiting

You can investigate the code of the application and change the way it handles the events. It's really simple. For example, try to come app with an application that counts how many Ethereum blocks were mined by the miner 0xfeebabe6b0418ec13b30aadf129f5dcdd4f70cea (don't forget to ).

By default, you are using an anonymous quota for requests which is really small. In order to increase the limit you should create your own API key in the and use it in the client.

🌊
Stream Registry
stream page
User Portal
handle undo events