
Deploy lsp-indexer
A template for the LSP Indexer. Get data availability right now.
lsp-indexer
Just deployed
Just deployed
Data Connector Agent
Just deployed
Just deployed
/var/lib/postgresql/data
Deploy and Host lsp-indexer on Railway
The LSP Indexer is an open-source tool that monitors the LUKSO blockchain, capturing key events like DataChanged, UniversalReceiver, and Transfer. It extracts and indexes data such as LSP3Profile and LSP4Metadata for easy querying and analysis, supporting developers and applications in the LUKSO ecosystem.
About Hosting lsp-indexer
Hosting lsp-indexer on Railway involves cloning the repository, installing dependencies with pnpm, and configuring environment variables like DB_URL, RPC_URL, and IPFS_GATEWAY. Build the project with pnpm build, apply database migrations, and start the indexer with pnpm start. Railway simplifies deployment by managing infrastructure, scaling, and database connectivity, ensuring seamless operation. A PostgreSQL database is required for data storage, and proper rate-limiting (RPC_RATE_LIMIT) prevents RPC overload. The monorepo structure, managed by pnpm workspaces, organizes packages for efficient event processing and indexing.
Common Use Cases
- Real-time Event Monitoring: Track LUKSO blockchain events like
Follow,Unfollow, orTransferfor live analytics or notifications. - Data Analysis for DApps: Index LSP3Profile and LSP4Metadata to power decentralized applications with structured blockchain data.
- Smart Contract Interaction Tracking: Monitor
ExecutedandUniversalReceiverevents to analyze contract interactions and user activity.
Dependencies for lsp-indexer Hosting
- Node.js: Required for running the indexer and managing pnpm dependencies.
- PostgreSQL: Stores indexed blockchain data, configured via
DB_URL. - pnpm: Manages the monorepo and dependencies across
abi,indexer, andtypeormpackages.
Deployment Dependencies
- LSP Indexer GitHub Repository
- Railway Documentation
- LUKSO RPC Endpoint
- Subsquid Gateway
- IPFS Gateway
Implementation Details
To deploy on Railway, set up a new project, link the GitHub repository, and configure environment variables as per .env.example. Example .env setup:
DB_URL=postgresql://postgres:password@host:5432/postgres
RPC_URL=https://rpc.lukso.sigmacore.io
SQD_GATEWAY=https://v2.archive.subsquid.io/network/lukso-mainnet
IPFS_GATEWAY=https://api.universalprofile.cloud/ipfs/
RPC_RATE_LIMIT=10
FINALITY_CONFIRMATION=75
FETCH_LIMIT=10000
FETCH_BATCH_SIZE=1000
FETCH_RETRY_COUNT=5
Run pnpm build, pnpm migration:generate, and pnpm migration:apply during deployment setup. Railway automates scaling and database provisioning.
Why Deploy lsp-indexer on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying lsp-indexer on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
lsp-indexer
chillwhales/lsp-indexerData Connector Agent
hasura/graphql-data-connector:v2.46.0