ASCAlejandro Saez CastellsBlockchain / Backend / Full-stack

Backend platform

Casper Ecosystem Platform

A Web3 platform for the Casper ecosystem combining blockchain data, GitHub project data, and cryptocurrency market data into a unified backend and frontend experience.

RoleBackend / Full-Stack Web3 Developer
Timeline2022-2024
FocusBackend platform
Current Casper ecosystem page

Problem, context, and constraints

Users in blockchain ecosystems often need information spread across multiple sources such as blockchain data, project activity, and market data.

A unified platform improves discoverability, ecosystem visibility, and access to real-time technical and market information.

Context
  • The original casperecosystem.io domain currently redirects to the Casper Network ecosystem page.
  • The portfolio describes Alejandro's contribution to a Casper ecosystem platform and avoids claiming that the currently visible page is exactly the original custom platform.
Constraints
  • External data sources have different update patterns and reliability constraints.
  • Market providers and GitHub APIs introduce rate limits and freshness tradeoffs.
  • The backend needed documentation discipline for long-term maintainability.

Solution

  • Built backend services with Node.js, TypeScript, and Express.
  • Generated API documentation with Swagger/OpenAPI.
  • Integrated blockchain-specific Casper ecosystem functionality.
  • Integrated GitHub API for repository updates and project stats.
  • Integrated CoinMarketCap for live crypto price data.
  • Used Amazon S3 for price history storage.
  • Supported a Gatsby/React frontend for access to real-time data.

Before

Fragmented ecosystem, GitHub, and market information.

After

One interface for blockchain, project, and market visibility.

Architecture

A service-oriented backend aggregated data from blockchain-specific sources, GitHub activity, and crypto market providers, then exposed that data through documented APIs consumed by a Gatsby/React frontend.

Casper Ecosystem Platform system architecture
01Frontend
  • Gatsby
  • React
  • JavaScript
02Backend
  • Node.js
  • TypeScript
  • Express
  • REST APIs
03Data
  • Dedicated database for price history
  • Amazon S3 storage
  • GitHub and market data aggregation
04Integrations
  • Casper blockchain ecosystem
  • GitHub API
  • CoinMarketCap API
  • Amazon S3

Key technical decisions

API-first backend
Context
The frontend needed structured access to blockchain, GitHub, and market data.
Choice
Build a documented REST API with Swagger/OpenAPI.
Tradeoff
This adds documentation discipline and API maintenance overhead, but improves developer usability and long-term maintainability.
External data aggregation
Context
Ecosystem users needed data from multiple independent sources.
Choice
Aggregate blockchain-specific data, GitHub repository data, and CoinMarketCap market data.
Tradeoff
This improved visibility but introduced rate limits, freshness constraints, and third-party reliability concerns.
Store price history with S3
Context
Historical market data needed to be persisted efficiently.
Choice
Use Amazon S3 for price history storage.
Tradeoff
Object storage can be cost-effective and simple, but requires careful design around data retrieval and update patterns.

Security, scaling, and reliability

  • Documentation and typed backend structure supported maintainability.
  • S3 used to persist price history efficiently.
  • Frontend optimized for fast access to dynamic data.
  • Needed to balance real-time freshness against rate limits and caching complexity.
  • Needed resilience around third-party API dependencies.

Testing

  • Possible test areas include API endpoint tests, integration tests for external providers, frontend smoke tests, and contract-like validation for API responses.

Impact

  • Unified multiple sources into one platform.
  • Improved access to blockchain, project, and market visibility for Casper ecosystem users and developers.
  • Created documented APIs for ecosystem data.

What I learned and would improve next

How to design backend services that balance real-time data, third-party integrations, and developer usability.

Coordinating multiple external data sources with different update patterns and reliability constraints.

  • Add stronger caching.
  • Add observability.
  • Add resilience around third-party API dependencies.
  • Improve public documentation and architecture diagrams.