ArbiSight is an open-source, modular, CLI-based monitoring and alerting toolkit designed specifically for developers building on Arbitrum Stylus. It provides real-time telemetry by capturing and parsing CLI command activity during the smart contract development and deployment lifecycle. The tool visualizes command usage patterns, error trends, and anomaly signals through an integrated logging and alert engine that can connect to platforms like Elastic/Kibana, Prometheus/Grafana, or even a unique Web UI. Building on the experience from my Stellar Community Fund project (Stellar Command Insights), ArbiSight adapts the proven real-time command analytics approach for Arbitrum’s Stylus workflows. Key Features: 🛠 CLI Parser: Captures and parses Arbitrum-specific CLI commands in real time. 📡 Log Forwarder: Sends structured data to developer-selected platforms (ElasticSearch, Grafana, Loki, or Web UI). 🚨 Alert Engine: Detects CLI errors, abnormal usage, and failed deployments, optionally triggering real-time alerts via Slack, Telegram, or webhook. 📊 Dashboards: Offers customizable dashboards for developers to monitor testnet/mainnet CLI activity with ready-to-use templates. ArbiSight bridges a crucial gap in the developer tooling landscape for Arbitrum, enhancing visibility during development and streamlining debugging processes. What innovation or value will your project bring to Arbitrum? What previously unaddressed problems is it solving? Is the project introducing genuinely new mechanisms.
ArbiSight introduces a novel layer of observability and operational intelligence for developers building on Arbitrum Stylus by offering a real-time CLI monitoring and alerting toolkit—something that has been notably absent in the ecosystem.
While Arbitrum has strong support for L2 performance and smart contract scalability, developer-facing infrastructure tooling at the CLI and command-line workflow level is still underdeveloped. ArbiSight solves this by enabling:
Real-time visibility into CLI command executions during deployment, testing, and debugging
Anomaly detection and failure pattern recognition at the command level
Alerting systems integrated with popular messaging platforms (Slack, Telegram) for fast response
Developer-centric dashboards built for Stylus workflows
This fills a critical gap in the DevEx (Developer Experience) layer of the Arbitrum ecosystem. Current observability tools mostly focus on on-chain data or frontend metrics, while ArbiSight introduces deep telemetry at the infrastructure & command level, tailored specifically for smart contract developers using Stylus.
It is one of the first open-source initiatives that treats the CLI as a data source for developer observability—offering insights previously invisible during local and testnet development. With this approach, ArbiSight helps Arbitrum developers debug faster, deploy safer, and iterate smarter.
What is the current stage of your project.
The project is currently in the early prototype and technical architecture phase, with working concepts and components validated through a previous implementation on the Stellar network (Stellar Command Insights).
While the Arbitrum-specific version is not yet deployed, the underlying architecture for CLI command parsing, real-time log forwarding, dashboard visualization, and alerting has already been developed and proven in production.
For ArbiSight, core modules such as:
Command parser logic
Log structuring format
Visualization pipelines (ELK / Grafana)
CLI integration framework
...have already been scoped and partially implemented in a modular and chain-agnostic manner.
I am ready to begin adapting and deploying this framework specifically for the Arbitrum Stylus CLI ecosystem.
Do you have a target audience? If so, which one.
Yes — our primary target audience is Arbitrum Stylus developers who interact with CLI tooling during the smart contract development, testing, and deployment lifecycle.
These include:
Developers deploying and debugging Stylus smart contracts on testnet/mainnet
Builders maintaining custom infrastructure, local nodes, or CI pipelines using Arbitrum CLI tools
Teams that need monitoring, alerting, and telemetry for internal developer operations
DevOps engineers integrating Arbitrum CLI tooling into broader observability platforms
By providing command-level visibility, error tracking, and anomaly detection, ArbiSight directly improves the DevEx (Developer Experience) for this segment—especially those working on complex deployments or maintaining production-grade dApps.
Do you know about any comparable protocol, event, game, tool or project within the Arbitrum ecosystem.
Currently, there are no CLI-native developer tools in the Arbitrum ecosystem that provide real-time telemetry, error detection, and alerting at the command level.
Most monitoring and analytics tools in the ecosystem focus on:
On-chain metrics (e.g., Dune dashboards, BlockScout-style explorers)
Application-level observability (e.g., frontend UX monitoring, smart contract state)
However, there is a gap when it comes to developer-side infrastructure visibility—particularly during the local development and deployment process.
Tools like Tenderly or Hardhat plugins provide partial visibility for Solidity dApps, but there is no dedicated solution tailored to the Stylus CLI workflow on Arbitrum. ArbiSight is designed to fill this gap by offering command-line level insights, structured logging, and developer alerts as part of the CI/CD toolchain.
Have you received a grant from the DAO, Foundation, or any Arbitrum ecosystem related program or conducted any IRL like a hackathon or workshop.
No, I have not previously received a grant or participated in a hackathon or workshop within the Arbitrum ecosystem. However, I was recently funded by the Stellar Community Fund (SCF29) for a CLI-based infrastructure project called Stellar Command Insights (SCI), which focused on real-time command analysis, logging, and alerting for Soroban smart contracts.
That experience demonstrated my ability to scope, build, and deploy production-ready developer tooling with measurable outcomes. I’m now looking forward to bringing those learnings to the Arbitrum ecosystem and contributing to its growing infrastructure layer.
Have you received a grant from any other entity in other blockchains that are not Arbitrum.
Yes — I received a grant from the Stellar Community Fund (SCF29) for my project Stellar Command Insights (SCI). It is an open-source CLI-based real-time monitoring and alerting tool designed for developers building on the Stellar network with Soroban smart contracts.
The project was successfully delivered on the Stellar mainnet and provided:
Command-line telemetry and analytics
Real-time error detection and logging
Visual dashboards for CLI activity
Open-source tooling for infrastructure-level observability
This grant experience helped me understand the full lifecycle of scoped development, milestone-based funding, public delivery, and community documentation. I’m now building upon that foundation with ArbiSight, tailored for the Arbitrum Stylus ecosystem.
What is the idea/project for which you are applying for a grant.
ArbiSight is an open-source CLI-native monitoring and alerting toolkit designed specifically for developers building and deploying smart contracts with Arbitrum Stylus. Its primary goal is to bring real-time observability to the command-line interface, enabling developers and DevOps teams to gain insight into deployment behavior, detect errors earlier, and automate notifications during the development lifecycle.
🔧 Core Components & Features CLI Command Parser:
Captures Stylus-related CLI commands locally during contract deployment, testing, and configuration.
Parses and structures commands, flags, arguments, and exit statuses into readable events.
Log Forwarding System:
Converts command execution data into JSON/log format and forwards it to external logging systems.
Supports popular DevOps stacks: ELK (ElasticSearch + Logstash + Kibana), Prometheus + Grafana, or Loki.
Alerting Engine:
Triggers alerts on error patterns, unexpected behaviors, or specific command failures.
Can be integrated with Slack, Telegram, Discord, or webhook-based alert systems.
Dashboard Templates:
Provides pre-built dashboards to visualize command success/failure rates, most used functions, average deployment times, and more.
Enables Stylus developers to monitor testnet and mainnet deployment activity from a single interface.
Modular CLI Wrapper (Optional):
Optional command wrapper to standardize logging for local and CI environments.
📍 Implementation Plan & Timeline Phase Description Timeline Phase 1 Design CLI parser and structure for Stylus CLI activity Week 1–2 Phase 2 Build initial parser module to capture and format commands Week 3–4 Phase 3 Implement log forwarding pipeline to ELK/Grafana-compatible format Week 5–6 Phase 4 Integrate alert engine (rule-based triggers + Telegram/Slack/webhooks) Week 7–8 Phase 5 Build developer dashboards for testnet deployment visualization Week 9–10 Phase 6 Final polish: docs, CLI installation script, video tutorials Week 11–12
💡 Why This Project Today, developers in the Arbitrum ecosystem lack observability tools focused on command-line workflows. Most existing tooling revolves around on-chain data or frontend analytics, leaving a critical blind spot in the infrastructure and deployment layer—especially for Stylus-based smart contract development.
ArbiSight directly addresses this gap by introducing a real-time monitoring and alerting layer for CLI activity. Developers get structured logs of their command usage, visibility into failed deployments or testing commands, and automated alerts for fast debugging.
This project enables:
Faster debugging and reduced downtime
Structured telemetry for Stylus CLI commands
Greater visibility into local/testnet deployment behavior
Adoption of standard DevOps workflows within Arbitrum
By combining real-time observability with developer tooling, ArbiSight aligns with the Arbitrum DAO’s strategic objectives to improve developer experience, reduce costs per deployment, and support scalable infrastructure that encourages long-term growth.
Outline the major deliverables you will obtain with this grant.
ArbiSight CLI Parser Module
A custom-built command-line parser that captures and processes Arbitrum Stylus CLI activity (e.g., deployment, testing, configuration commands)
Outputs structured logs (JSON format) with metadata: command, flags, exit code, timestamp
Includes basic error classification system (success, warning, failure)
Log Forwarding and Storage Integration
Converts structured logs into streams compatible with ELK Stack, Loki, or Prometheus
Setup of default log pipeline for local development and CI/CD usage
Dockerized setup included for quick bootstrapping
Real-Time Alerting System
Custom alert engine that monitors parsed logs and triggers notifications
Rule-based error pattern detection (e.g., repeated failures, abnormal latency)
Integrations with Slack, Telegram, Discord, and generic webhooks
Developer Dashboard Templates
Pre-built dashboard templates using Kibana and Grafana
Visualize most-used commands, success/failure rates, average deployment durations
Custom views for Stylus testnet activity and logs
Public GitHub Repository (MIT License)
Fully documented open-source repo with all code, setup instructions, and modular components
Ready-to-use CLI installation script (Bash or Node.js wrapper)
Includes README, contribution guidelines, and bug reporting system
Demo & Documentation
Live demo using Stylus testnet deployments
Step-by-step video walkthrough
Complete developer documentation and alert configuration guide
Please explain how your idea/project aligns with the Arbitrum ecosystem goals.
ArbiSight aligns with Arbitrum’s ecosystem goals by improving developer tooling and observability for Stylus-based workflows. It introduces a missing CLI-level monitoring layer that enhances developer experience, reduces friction during contract deployment, and supports scalable infrastructure. As an open-source tool, it can be widely adopted by solo builders, DAOs, and dev teams—accelerating growth and ecosystem expansion.
What is your requested grant.
8500$
Website.
N/A
Please provide a detailed breakdown of the budget in term of utilizations, costs and other relevant information.
✅ Detailed Budget Breakdown – Total: $15,000
Milestone 1: CLI Parser & Architecture Setup
1- Personnel/Team Costs
CLI parser design and implementation
Estimated Hours: 80 hours @ $50/hr
Resources: 1
Total Cost: $4,000
2- Infrastructure/Software Licenses
Development environment, test chains
Total Cost: Included above
3- Equipment/Materials
N/A 4- Marketing/Outreach
N/A 5- Other Expenses
N/A Total: $4,000
Milestone 2: Logging & Forwarding Engine
1- Personnel/Team Costs
Log forwarding pipeline (ELK/Grafana)
Estimated Hours: 70 hours @ $50/hr
Resources: 1
Total Cost: $3,500
2- Infrastructure/Software Licenses
Docker-based local testing setup
Total Cost: Included above
3- Equipment/Materials
N/A 4- Marketing/Outreach
N/A 5- Other Expenses
N/A Total: $3,500
Milestone 3: Alert Engine & Notifications
1- Personnel/Team Costs
Alert engine, Slack/Telegram/webhook integrations
Estimated Hours: 50 hours @ $50/hr
Resources: 1
Total Cost: $2,500
2- Infrastructure/Software Licenses
N/A 3- Equipment/Materials
N/A 4- Marketing/Outreach
N/A 5- Other Expenses
N/A Total: $2,500
Milestone 4: Dashboards, Documentation & Public Release
1- Personnel/Team Costs
Dashboard templates (Grafana/Kibana), technical docs, video tutorial
Estimated Hours: 55 hours @ $50/hr
Resources: 1
Total Cost: $2,750
2- Infrastructure/Software Licenses
N/A 3- Equipment/Materials
N/A 4- Marketing/Outreach
N/A 5- Other Expenses
N/A Total: $2,750
Completion & Adoption Report
1- Personnel/Team Costs
Final reporting and adoption metrics
Estimated Hours: 45 hours @ $50/hr
Resources: 1
Total Cost: $2,250
2- Infrastructure/Software Licenses
N/A 3- Equipment/Materials
N/A 4- Marketing/Outreach
N/A 5- Other Expenses
N/A Total: $2,250
Grand Total: $15,000
Provide a list of the milestones, with the USD amount of the grant associated to it, the deliverables that will be provided, and the estimated completion time.
✅ Milestone-Based Funding Plan – Total: $15,000
Milestone 1: CLI Parser & Architecture Setup Deliverables: – CLI parser module for Stylus command capture – Command structuring (JSON format) – Base log schema definition Estimated Time: Week 1–3 Funding: $4,000
Milestone 2: Logging & Forwarding Engine Deliverables: – Log forwarding pipeline – Modular forwarding system – Docker-based local testing setup Estimated Time: Week 4–6 Funding: $3,500
Milestone 3: Alert Engine & Notifications Deliverables: – Error/anomaly pattern matching logic – Alerting integrations (Slack, Telegram, webhook) – Alert configuration guide Estimated Time: Week 7–9 Funding: $2,500
Milestone 4: Dashboards, Documentation & Public Release Deliverables: – Pre-built dashboards – Full technical documentation and screencast – GitHub open-source release (MIT license) Estimated Time: Week 10–12 Funding: $2,750
Completion & Adoption Report Deliverables: – Final report summarizing project completion, adoption metrics, and user feedback – Survey results and GitHub stats (stars, forks) Estimated Time: Week 13-14 Funding: $2,250
Are milestones clearly defined, time-bound, and measurable with quantitative metrics where applicable? What are your reference KPI, if applicable, for each milestone.
✅ Milestones are clearly defined, time-bound, and measurable. Below are the key KPIs for each milestone (Total Duration: ~14 Weeks):
Milestone 1: CLI Parser & Architecture Setup – CLI parser captures ≥90% of Stylus-related command patterns – Generates structured JSON output with command metadata – Base schema validated with 20+ test command samples Timeframe: Week 1–3
Milestone 2: Logging & Forwarding Engine – Successfully forwards logs to at least 1 external systems – Docker-based local dev setup installs in <5 minutes – Processes at least 100 CLI events in internal tests Timeframe: Week 4–6
Milestone 3: Alert Engine & Notifications – Triggers alerts for ≥3 key error types (failed deploy, repeated reverts, etc.) – Integrates with ≥2 messaging platforms (Slack, Telegram, webhook) – Average alert trigger delay <3 seconds in test environment Timeframe: Week 7–9
Milestone 4: Dashboards, Documentation & Public Release – At least 3 pre-built dashboard views (command usage, success/failure, deployment duration) – Full technical documentation and 1 video walkthrough published – Public GitHub repo with MIT license and installation script Timeframe: Week 10–12
Milestone 5: Completion & Adoption Funding: $2,250 Timeframe: Week 13–14
Deliverables and KPIs: ✅ Project Completion Report: A detailed written report summarizing all technical achievements, milestones met, and learnings from the project. ✅ Community Adoption Metrics: – GitHub Stars: ≥ 50 stars – GitHub Forks: ≥ 10 forks – GitHub Issues: ≥ 5 issues (created by community users) – Demo Video Views: ≥ 50 unique views (project walkthrough) – Community Survey: ≥ 8 developers or teams provide structured feedback on usability, bugs, and feature requests ✅ Community Engagement & Education: – Minimum 3 community posts (e.g., Discord announcements, Twitter threads, Medium articles) summarizing project progress and learnings – 1 developer tutorial video showing installation, usage, and dashboard features ✅ Project Sustainability Plan: – Post-grant roadmap published on GitHub, outlining planned features, maintenance, and long-term support ✅ Showcase Integration: – Project demo successfully presented on Stylus testnet with live data examples (mock or real) – Clear instructions for how developers can install and use the toolkit independently
Success Criteria: – All metrics listed above achieved or surpassed (GitHub stars, forks, issues, demo views, survey responses). – Timely submission of all reports and documentation by the end of Week 14. – Clear demonstration of developer interest and community feedback (e.g., GitHub Issues, Discord/Telegram threads). – At least 1 project demo walkthrough (recorded video or live) published and shared with the community. – A documented roadmap and sustainability plan showing how ArbiSight will continue to serve the Arbitrum ecosystem after grant completion.
What is the estimated maximum time for the completion of the project.
14 weeks
How should the Arbitrum community measure the success of this grant.
Success can be measured by the adoption, usability, and impact of the ArbiSight toolkit within the Arbitrum Stylus developer community. Key indicators include:
Open-source release with full documentation and installation guide
Deployment of ArbiSight on Stylus testnet with real CLI event tracking
At least 3 pre-configured dashboards for command analysis, failure rates, and deployment duration
Functional alerting system integrated with messaging platforms
Community usage: tracked via GitHub stars, forks, and contributions
Feedback from developers using it in local or CI environments
Ultimately, success means Stylus developers spend less time debugging and have better visibility into their command workflows, leading to smoother deployment pipelines and stronger developer experience in the Arbitrum ecosystem.
What is the economic plan for maintaining operations or continuing the growth of your project after the grant period.
ArbiSight will be maintained as an open-source project under the MIT license, with a focus on community adoption and long-term sustainability. Following the grant period, I plan to:
Continue development based on community feedback and GitHub contributions
Explore integration with CI/CD pipelines and infrastructure services (e.g., Arbitrum Orbit tooling)
Expand compatibility with other chains (e.g., Ethereum L2s), enabling potential cross-ecosystem utility
Seek additional funding from ecosystem partners or retroactive public goods funding (e.g., Gitcoin, Optimism RetroPGF)
Offer enterprise support or optional managed hosting for teams requiring advanced monitoring
The goal is to position ArbiSight as a widely used infrastructure tool for Stylus developers and beyond, enabling sustainable growth through adoption and optional extensions.
Market Needs: For developers building apps and interfaces, what specific challenges or opportunities do they face in Arbitrum.
Developers building on Arbitrum—especially those using Stylus—face several challenges at the infrastructure and debugging layer. Unlike frontend applications or on-chain analytics, the CLI workflows used for contract deployment, configuration, and testing remain largely invisible and unmonitored. This lack of observability leads to longer debugging cycles, deployment errors, and reduced developer confidence.
At the same time, there is a growing opportunity to standardize DevOps practices in Arbitrum’s L2 environment. With the rise of Arbitrum Orbit and the Stylus framework, more developers are running local validators, automating deployments, and integrating smart contracts into complex backend systems. This shift opens up a critical need for CLI-native tooling that improves developer experience, increases transparency, and shortens feedback loops—which ArbiSight is purpose-built to address.
Composability: How can your proposed developer tooling (existing or new) facilitate seamless interaction between different protocols and tools built on Arbitrum, the Nova ecosystem and other Orbit chains.
ArbiSight is designed as a modular, chain-agnostic CLI monitoring layer that can integrate with any Arbitrum-based CLI tool, whether it's used on Arbitrum One, Nova, or custom-built Orbit chains.
By using structured logging formats (e.g., JSON), Docker-based deployment, and webhook-compatible alerting, ArbiSight enables seamless interaction with:
Custom validator scripts in Orbit chains
DevOps pipelines integrating Nova-specific workflows
Smart contract deployment tools across various Arbitrum environments
Logging, analytics, and security tools already used by developers
This composability makes ArbiSight suitable not only for Stylus developers, but for broader infra teams building cross-chain systems. It acts as a common telemetry layer that can plug into diverse protocol stacks without tight coupling.
Adoption: If your grant focuses on a Growth or Orbit Chain developer tool, how would you ensure its widespread adoption within the developer community.
To drive adoption of ArbiSight, I will focus on practical usability, community engagement, and developer onboarding. Here's how:
Open-source release under MIT license with clear documentation and CLI installation script to reduce friction
Pre-configured dashboard templates and sample configurations for Stylus and Orbit-based CLI workflows
Tutorial videos and real-world examples showing how to integrate ArbiSight into local and CI environments
Targeted outreach to Arbitrum Orbit builders and infrastructure DAOs via community forums, Discord, and Telegram
Collaborations with testnet initiatives or hackathons to encourage early adoption
Support GitHub issues and contributions, enabling community-driven improvement and visibility
By offering plug-and-play functionality, making onboarding simple, and actively engaging the developer community, ArbiSight aims to become a go-to DevOps tool within the growing Arbitrum ecosystem.
If working on Orbit Chain Onboarding and Tooling: How would you adapt your existing developer tooling (or propose a new tool) to simplify building applications on custom Arbitrum Layer 3 chains (Orbit Chains).
ArbiSight is inherently modular and CLI-native, making it well-suited for adaptation to Orbit Chains. To simplify onboarding and tooling for custom Arbitrum Layer 3s, I plan to:
Make the parser and logging system configurable so that Orbit-specific CLI tools, validators, or deployment scripts can be easily integrated
Ship Orbit-ready dashboard templates to visualize chain-specific deployment patterns, command failures, or node events
Support self-hosted deployments via Docker or Ansible, ideal for teams running private Orbit chains
Provide Orbit-specific installation modes with pre-set configs for Arbitrum Orbit’s toolchain and testnet environments
Collaborate with early Orbit builders to gather feedback and tailor the CLI insights to their onboarding workflows
By treating Orbit CLI workflows as first-class citizens in ArbiSight’s design, the tool can reduce debugging time, improve observability, and accelerate application development across custom Arbitrum Layer 3 ecosystems.
Instagram.
N/A
If applying for a growth oriented grant: Please provide success metrics for the grant with milestone-oriented disbursements.
✅ Milestone 1 – CLI Parser & Architecture Setup
CLI parser captures ≥90% of Stylus CLI commands Schema validated using 20+ test scenarios Success: Parser operational and generating structured logs locally
✅ Milestone 2 – Logging & Forwarding Engine
Logs successfully forwarded to at least 2 external systems (e.g., ELK, Grafana/Loki) Docker-based local dev setup installs in <15 minutes Logs processed from 100+ CLI events Success: Logs are visible on dashboards with real CLI inputs
✅ Milestone 3 – Alert Engine & Notifications
Alert engine detects ≥3 key error conditions Slack/Telegram/webhook notifications delivered in <3s Configurable alert rules tested across CLI error patterns Success: Real-time alerts triggered during testnet usage
✅ Milestone 4 – Dashboards, Documentation & Public Release
3 pre-built dashboards available (command usage, deploy success, failure rate) GitHub repo launched, full documentation and install guide published 1 tutorial video and onboarding walkthrough Minimum 20 GitHub stars and 5 unique users/teams testing ArbiSight Success: Public launch with measurable early adoption and community usage
✅ Completion & Adoption
Final report summarizing project completion and functionality Key usage metrics (GitHub stars, forks, contributors) Feedback from at least 5 developers/teams Short community survey results analyzing developer satisfaction Success: Verified adoption and usage by the developer community
LinkedIn.
N/A
Discord.
N/A
Others.
https://github.com/bytemaster333
Do you acknowledge that your team will be subject to a KYC requirement.
Yes
Do you acknowledge that, in case of approval, you will have to provide a report at the completion of the grant and, three months later, complete a survey about your experience.
Yes
Team experience and completeness.
This project is developed and maintained by a solo developer, Salih Toruner, an experienced Linux system administrator and infrastructure engineer with a background in electrical and electronics engineering. I specialize in CLI development, DevOps tooling, and blockchain infrastructure.
I previously built and launched Stellar Command Insights (SCI), a real-time CLI monitoring and visualization tool that was officially funded by the Stellar Community Fund (SCF29). SCI operates on the Stellar mainnet and has gained recognition within the ecosystem for providing logging, alerting, and error analysis for Soroban CLI commands.
I bring strong expertise in:
Bash scripting, CLI tool design
Monitoring stacks (ELK, Grafana, Prometheus)
Smart contract lifecycle tooling
Blockchain explorer data integration
As a solo builder, I’ve successfully shipped full-stack developer tooling solutions from concept to deployment, including full documentation and public releases.
GitHub: https://github.com/bytemaster333 Project reference (SCI): https://github.com/bytemaster333/Soroban-ELK
Category.
Developer Tooling