This monorepo implements the classic Arbitrum optimistic rollup Layer-2 solution. The system consists of a custom Arbitrum Virtual Machine (AVM) written in C++, a Go-based node that provides an Ethereum-compatible RPC interface, sequencer/validator functionality, and Solidity smart contracts on L1 for bridge, rollup, challenge, and staking logic. Key data flows: the inbox reader ingests sequencer batches and delayed messages from L1, delivers them to the AVM for execution, and produces state updates and transaction results that are served via the RPC API. The architecture supports multiple node modes (forwarder, aggregator, sequencer, validator) with Redis-based lockout for sequencer exclusivity and optional Fireblocks integration for external signing. Despite being classified as 'classic' and superseded by the Nitro upgrade, the codebase continues to receive active maintenance and contains production-grade infrastructure for running Arbitrum nodes.
This repository is a curated Markdown knowledge base — an "awesome list" — cataloging 300+ externally hosted tools, articles, Twitter threads, dashboards, and educational resources for on-chain cryptocurrency investigations, blockchain forensics, and crypto OSINT. It is classified as data_research only as the closest available fit; in reality it is neither a software application nor a data pipeline. The repository contains zero source code, no ETL scripts, no notebooks, no APIs, and no tests. The entire substance lives in README.md, organized into sections: data-analysis tools, visualization tools, clusterizers (AML clustering), hacks databases, VR/3D visualizations, Monero resources, a knowledge hub of methodology articles, and a list of investigators to follow.
This repository serves as Flashbots' public research hub, coordinating MEV-related research proposals (FRPs) and maintaining a curated publication index. The codebase consists primarily of structured markdown files for research proposals (in various stages: active, completed, stagnant) and a Python script that regenerates publication listings in JSON, CSV, and Markdown from a hardcoded list. The `docs/` folder contains a static HTML site with search and filtering capabilities for publications. There is no application code, data pipeline, or notebook analysis; the repository is purely a documentation and process coordination tool for blockchain MEV research. While not a typical data research project, it effectively manages metadata and provides a clean, reproducible publication build process.
This is a multi-platform Solana trading bot designed for sniping newly created tokens on pump.fun and letsbonk.fun (Raydium LaunchLab). It listens for token creation events in real-time via multiple mechanisms (gRPC Geyser, WebSocket logs/block subscription, third-party PumpPortal feed), then automatically executes buy and sell trades using program instructions (v2 with full account lists). The codebase emphasizes a platform-agnostic architecture with abstract interfaces for address derivation, instruction building, event parsing, and curve management, allowing new platforms to be added without altering core trading logic. It includes optional 'extreme fast mode' for zero-RPC buys, configurable exit strategies (take-profit, stop-loss, time-based), priority fee management (fixed or dynamic), compute unit optimization, and an interactive cleanup manager. The repository is explicitly educational ('NOT FOR PRODUCTION') and ships with an extensive suite of standalone learning examples and verification scripts that offline-test edge cases such as v1/v2 transaction cutover, optional trailing arguments, price feed failures, and retry bounding. Despite its purpose as a demonstration, the code demonstrates solid engineering practices: abstraction layers, configuration-driven bots, a token bucket rate limiter, plugin-based fee engines, and generic Anchor IDL decoders.
This repository is a Hardhat-based template for developing Solidity smart contracts. It provides a pre-configured development environment with sensible defaults for compilation, testing, linting, and deployment. The core functionality is demonstrated through a simple `Lock` contract that implements a time-locked withdrawal mechanism, complete with custom errors, events, and comprehensive tests. The template integrates TypeChain for TypeScript bindings, Ethers.js for Ethereum interactions, and various tooling like Solhint, Prettier, and Solcover. It is not a production application but a starting point for new Solidity projects, emphasizing best practices and developer experience.
Mevlog-rs is a Rust-based, open-source alternative to commercial blockchain explorers like Dune Analytics, providing a comprehensive toolchain for indexing, storing, and querying EVM-compatible blockchain data. The core system downloads raw chain data from RPC endpoints, stores it in per-chain SQLite databases, and allows read-only SQL queries enriched with custom U256 arithmetic, formatting, and ENS resolution. It includes a CLI with 20+ subcommands, a web backend (Axum + React) for hosted exploration, a TUI (ratatui) for interactive browsing, and an MCP server for AI agent integration. The system is heavily oriented toward MEV (maximal extractable value) analysis, with coinbase transfer detection, state diffs, and call tracing via local revm replay or RPC. Key architectural patterns include a shared dependency initializer, a secure read-only SQL sandbox with progress limits, a config-driven custom table engine, and a reorg-aware indexing pipeline that handles chain reorganizations. While the codebase demonstrates strong craftsmanship and modularity, its large dependency surface, reliance on external services (ChainList, Pinata, cryo), and some commented-out tests indicate ongoing evolution and moderate maintenance risk.
This repository is the Tonhub Wallet, a non‑custodial mobile cryptocurrency wallet for the TON blockchain with additional Solana support. It is a full‑featured wallet that supports multi‑account management, token transfers (jettons), staking (liquid staking, native pools), hardware wallet integration (Ledger), a dApp browser using TonConnect v2, and financial products such as the Holders card program and Changelly exchange. The application also includes an AI chat assistant for transaction markup and operations, push notifications via Firebase, and deep‑link navigation for seamless URL handling. Built using React Native and Expo, the codebase is structured around a fragment‑based screen architecture, with custom hooks and React Query for data fetching, Recoil for state management, and a centralized query key factory. Despite its breadth, the codebase exhibits well‑defined separation of concerns with reusable UI components (e.g., ItemButton, RoundButton, WImage) and data patterns (e.g., batched metadata fetching, structural sharing for transaction lists). However, there are signs of technical drift, such as hardcoded endpoints, some deprecated library usage, and platform‑specific native modules that require ongoing maintenance.
This repository provides an HTTP API service for interacting with the TON (The Open Network) blockchain. It acts as an intermediary, translating HTTP requests into calls to the TON blockchain via the tonlib library. The service is built with FastAPI and uses a pool of worker processes to communicate with TON nodes, handling load balancing and failover. It supports caching of responses via Redis to reduce load on the blockchain nodes. The service exposes both REST and JSON-RPC endpoints for a wide range of blockchain operations, including querying account information, executing smart contract methods, and sending transactions.
The Filecoin Community repository serves as a central hub for community documentation, project showcases, and governance. It contains markdown files detailing community processes, calls, polls, and working group activities. The projects directory showcases applications and tools built by the community on Filecoin. The repository provides standardized templates for project submissions, meeting agendas, and notes, facilitating consistent community engagement. While it lacks executable code, it effectively coordinates the Filecoin ecosystem through structured documentation and resource sharing.
This is a Go-based blockchain node for the Mezon MainNet (MMN), implementing Proof-of-History (PoH) for transaction ordering, libp2p for peer-to-peer networking, gRPC and JSON-RPC for external APIs, and a leader-based consensus protocol with vote collection. The node supports three transaction types: Ed25519 key-based transfers, Groth16 ZK-proof transfers, and user content (social interactions). It uses either LevelDB or RocksDB as the persistent storage backend, with the latter bundled as vendored C headers. The codebase includes a CLI (init, bootnode, node, transfer), a client library, a stress-test tool with HTML reports, and a migration tool for importing user balances from CSV. The architecture is modular with clear interfaces for storage, mempool, events, and networking, making it a well-structured example of a modern blockchain validator node.
This repository implements the Dusk Network blockchain node (Rusk), a full Proof-of-Stake node with privacy-preserving transactions (Phoenix) and public transactions (Moonlight). The system is a Rust workspace containing a consensus engine (succinct attestation consensus with proposal/validation/ratification steps), a WebAssembly-based smart contract VM (Piecrust), a RocksDB/SQLite ledger, a mempool, an HTTP/GraphQL API server (Axum), and a CLI/TUI wallet. It also includes a JavaScript SDK (w3sper.js) for browser/Deno wallet interaction and a wallet-core library compilable to WASM. The architecture is modular: the node binary (rusk/src/bin/main.rs) composes services via a builder pattern (RuskNodeBuilder), supporting both full-chain and HTTP-only modes. Key data flows include transaction submission via RUES (Rusk Event System) or GraphQL, consensus message propagation over Kadcast P2P, block execution through the VM with hard-fork feature gating, and state persistence via RocksDB column families. External dependencies include dusk-plonk, dusk-poseidon, jubjub-schnorr, wasmtime, rkyv, and sqlx. The codebase demonstrates high craftsmanship in areas like deterministic committee sortition, zero-knowledge proof verification caching, and a reusable data-driver pattern for contract encoding/decoding.
The bnb-chain/bnb-chain.github.io repository serves as the source for the BNB Chain Knowledge Base, a static documentation website hosted at https://docs.bnbchain.org. Built with MkDocs and the Material theme, it provides comprehensive guides, tutorials, and references for the BNB Chain ecosystem, including BNB Smart Chain (BSC), opBNB, and BNB Greenfield. The site is deployed via GitHub Actions to GitHub Pages with a custom domain. Key technical components include custom JavaScript enhancements: an AI chatbot (SuperIntern) with SPA navigation support, a dynamically loaded footer menu with API fallback, MathJax for mathematical rendering, and external link handling. These components demonstrate reusable patterns for static site enhancement, particularly the chatbot's history API listener for SPA compatibility and the footer menu's resilient API integration. While the repository primarily functions as a documentation portal, its implementation as a static web application involves standard web development practices. The codebase exhibits good engineering in its frontend enhancements, though the core documentation content is Markdown-driven and the site architecture follows MkDocs conventions. Maintenance appears active based on recent commits and issue activity, though dependency pinning in the CI workflow presents a moderate technical drift risk.
Repository is a production Android application for Mixin Network, combining a cryptocurrency wallet with a messenger. It integrates with Mixin API (api.mixin.one) and Blaze messaging, supports transfers, swaps, web3 trades, perps, fiat money, and market analytics. The app is built with Kotlin, uses MVVM with ViewModels and Flows, Room for persistence, and a mix of Jetpack Compose and legacy View-based UI. A separate query-codegen Gradle module generates type-safe query code, and release automation includes Fastlane, Docker build box, and APK signature verification.
This is the Solana.Unity-SDK, a comprehensive Unity package for integrating Solana blockchain functionality into games and applications. It provides multiple wallet connection methods (in-game wallet, Web3Auth social login, Phantom/Solflare deep links, Mobile Wallet Adapter for Android, WebGL browser wallets), transaction signing, NFT minting via Metaplex Candy Machines (including a full editor toolchain for deployment), DEX swap aggregation (Jupiter), domain resolution (.skr), and cross-platform compatibility (Android, iOS, WebGL). The SDK bundles its own async infrastructure (UniTask 2.5.0) and includes sample UI screens for a wallet application. It is architectured around a central Web3 singleton, an abstract WalletBase class with concrete implementations, and platform-specific adapter classes. The codebase is well-structured with clear separation of concerns, but suffers from some monolithic classes (e.g., Web3Auth, CandyMachineController) and reliance on hardcoded endpoints and program IDs. The editor tools are fully functional but tightly coupled to the UnityEditor API. Overall, it is a professional-grade SDK with moderate reusability of its individual components.
This repository implements the Steem blockchain node (steemd), a Delegated Proof-of-Stake (DPoS) consensus platform with social media features. The system processes transactions, maintains chain state via shared-memory (chainbase) or RocksDB (MIRA) backends, and exposes a JSON-RPC API for querying accounts, blocks, market history, and social features like follows and tags. It includes a plugin architecture (appbase) for modular functionality, with plugins for witness production, P2P networking, resource credits (RC), account history, market history, and more. The codebase is written in C++17 and relies heavily on the custom fc library for asynchronous I/O, cryptography, serialization, and reflection. The architecture is a monolithic node daemon with a plugin system. Key entry points are the steemd binary (programs/steemd/main.cpp) and the CLI wallet (programs/cli_wallet/main.cpp). Data flows from P2P network messages through the chain plugin to the database, with operations evaluated by evaluators and state changes persisted via chainbase or MIRA. External dependencies include Boost, OpenSSL, RocksDB, and secp256k1-zkp. The repository also contains extensive Python test scripts for API regression and integration testing. While the codebase is well-structured and demonstrates advanced C++ patterns (static_variant, multi-index containers, reflection), it shows signs of technical drift: legacy plugins coexist with appbase plugins, conditional compilation for SMT and MIRA features, and several FC_TODO comments indicating incomplete migrations. The fc library itself is a reusable foundation but tightly coupled to the project's threading model.
This is the research archive for the Hyperspace P2P network, a distributed AGI system. The repository primarily contains documentation, leaderboards, trained model weights, and configuration files for autonomous research agents. It serves as a durable record of experiments run by agents across 5 research domains (machine learning, search, finance, skills, causes). The main outputs include a collaboratively trained language model (qwen2.5-0.5b-hyperspace-v1) trained by 32 anonymous nodes using DiLoCo + SVD compression, and live leaderboards updated via GitHub Actions. While the repo itself is mostly static artifacts, it references a larger codebase (the Hyperspace CLI and P2P stack) that is not included. The repository is hybrid: primarily a research data archive, but also includes a standalone CLI tool (agentboard) for a blockchain-based message board.
nOS Client is an Electron-based desktop application that serves as a wallet and decentralized application (dApp) browser for the NEO blockchain. It provides a virtual operating system metaphor with a built-in webview-based browser, account management, portfolio tracking, token transfers, and GAS claiming. The app integrates with the NEO network via neon-js, supports hardware wallets (Ledger) and mnemonic-based key management, and exposes a custom JavaScript API (NOS.V1) to dApps through a request processor. The codebase is organized as a standard React/Redux SPA with multiple feature modules (auth, browser, account, settings, appstore) and heavy use of higher-order components for state management. The application is feature-rich but shows its age: dependencies are heavily outdated (Electron 2.x, Webpack 3, React 16.8 with recompose), and some sections like Exchange and Favorites are incomplete placeholders. Despite this, the core wallet and dApp browsing functionalities are implemented with reasonable modularity, though the reliance on legacy patterns and unmaintained libraries makes it risky to reuse without modernization.
This repository is primarily a curated knowledge base and personal reference collection (a 'second brain') organized into dozens of markdown files across categories such as coding languages, blockchain, operating systems, trading, and general utilities. Each markdown file contains tables of contents and extensive lists of external links to tools, libraries, tutorials, and best practices. The repository also includes a small set of utility scripts (e.g., remark.js for auto-generating table of contents, wip-dedupe.js for deduplication, shell migration scripts, and code snippets) and an Obsidian vault configuration. While not a traditional application, the automation scripts add a thin layer of tooling around the curated content. The primary value is as a discovery index for developers and researchers, but the code itself is minimal and tightly coupled to personal workflow, limiting reuse.
This repository is a listing of 50 final-year project ideas covering machine learning, blockchain, web development, and cryptography. It contains only a README file that describes each project and provides links to YouTube tutorials. The actual source code, documents, and explanation videos are not included in the repository; instead, the README directs users to contact the author via email or WhatsApp to obtain the materials. The repository functions as a marketing page rather than a functional codebase. No code, data, or configuration files are present, making it impossible to evaluate architecture, reusability, or data lineage.