Topics of Crypto World

HANA is the native governance and utility token of the Hana Network ecosystem. Its core design binds on-chain coordination, incentive distribution, and long-term value capture into a single asset, ensuring that social finance, casual earning, and user growth are no longer dependent on centralized platform traffic subsidies but are continuously driven by the protocol-level token mechanism. With a total supply of 1 billion tokens and no additional inflationary issuance (subject to official disclosure), HANA will gradually enter circulation after TGE, serving as the value hub connecting Hanafuda, Hana Gateway, Reunion, and future products such as Capsule Shop and Dipsy.

Gitlawb and GitHub are both used for code hosting and development collaboration, but they differ clearly in their underlying architecture and collaboration model. GitHub is a centralized code hosting platform that manages repositories through account systems and centralized servers. Gitlawb, by contrast, uses DID identity, IPFS storage, and the libp2p network to build a decentralized Git collaboration system that does not require centralized servers. Compared with traditional Git platforms, Gitlawb places greater emphasis on AI Agent native collaboration, autonomous identity, and multi node synchronization.

A Gitlawb code push includes DID identity signing, Git object uploads to IPFS, Ref update Certificate broadcasting, libp2p network synchronization, and several other steps. Unlike traditional Git platforms, Gitlawb does not rely on a single centralized server. Instead, decentralized nodes jointly maintain repository state and code history. This mechanism allows both AI Agents and developers to collaborate on code and synchronize repositories without relying on platform based hosting.

Gitlawb (GITLAWB) is a decentralized Git collaboration network designed for AI Agents and developers. It combines a DID identity system, IPFS content storage, the libp2p P2P network, and UCAN capability-based authorization to create a code collaboration system that does not depend on centralized servers. Unlike traditional Git platforms, Gitlawb treats AI Agents as native participants in the network, allowing them to directly own repositories, submit code, open PRs, run automated tasks, and synchronize and verify code through decentralized nodes.

Block Street and Ondo are both on-chain financial infrastructure projects, but their core priorities are not the same. Ondo places greater emphasis on RWA asset mapping and on-chain Treasury products, while Block Street focuses more on stablecoin yield collaboration and on-chain financial operating structures.

BSB is the core utility token in the Block Street ecosystem. It is used to connect on-chain yield, ecosystem incentives, and financial collaboration structures. Block Street uses BSB to coordinate stablecoin assets, yield mechanisms, and the operation of its on-chain financial ecosystem.

Block Street is a Web3 platform built around stablecoin yield, on-chain asset management, and financial infrastructure. It is designed to connect on-chain yield, capital collaboration, and the BSB ecosystem. At its core, Block Street uses on-chain structures to coordinate stablecoin assets, yield strategies, and financial service systems.

Phoenix is an on-chain perpetual futures trading protocol running on Solana. Its risk control system mainly includes margin mechanisms, a risk engine, funding rates, an Oracle price system, and forced liquidation. Because perpetual futures trading involves leverage, Phoenix needs to continuously monitor account risk levels and dynamically adjust position risk during market volatility. Compared with traditional centralized exchanges, Phoenix’s risk management logic runs on-chain, and all positions, liquidations, and market states can be publicly verified.

Phoenix uses a Fully On-Chain Order Book architecture to complete order matching. After a user submits an order, the system carries out margin checks, order book matching, price confirmation, position updates, and on-chain settlement in sequence. Compared with the AMM model, which relies on liquidity pools, Phoenix is closer to the central limit order book, or CLOB, mechanism used in traditional financial markets. This allows it to provide lower slippage, greater order precision, and a market structure better suited to high frequency trading.

Phoenix is a decentralized perpetual futures trading protocol built on the Solana blockchain. It allows users to trade with leverage in a non-custodial way through an on-chain order book. Unlike traditional AMM based derivatives protocols, Phoenix uses a Fully On-Chain Central Limit Order Book, or CLOB, architecture, deploying order matching, risk management, and settlement processes on-chain to improve transparency and trading efficiency. Built on Solana’s high throughput and low latency, Phoenix aims to offer the on-chain derivatives market a trading experience close to that of centralized exchanges, while preserving the verifiability and composability of DeFi.

Phoenix and Drift are both on-chain perpetual futures protocols built on Solana, but they use different market structures and liquidity models. Phoenix places greater emphasis on a Fully On-Chain Order Book architecture, using a central limit order book, or CLOB, to support low slippage and high frequency trading. Drift, by contrast, uses hybrid liquidity and a vAMM mechanism, with a stronger focus on on-chain capital efficiency and open liquidity design. Both protocols aim to improve the on-chain derivatives trading experience, but they differ clearly in price discovery, market making methods, risk management, and target users.

Phoenix and Hyperliquid are both important protocols in the on-chain perpetual futures trading sector, but they follow different technical paths and market structures. Phoenix is built on Solana and uses a Fully On-Chain Order Book architecture, emphasizing on-chain transparency and Solana’s high frequency trading capabilities. Hyperliquid, by contrast, has built a dedicated high performance Layer 1 network and uses a custom execution environment to deliver a low latency trading experience close to that of centralized exchanges. Both protocols aim to solve liquidity, matching efficiency, and trading performance challenges in the on-chain derivatives market, yet they differ clearly in their underlying infrastructure, risk management, trade execution, and ecosystem positioning.

sBTC, Stacks, and Zest Protocol are key components of the Bitcoin DeFi, or BTCFi, ecosystem. Stacks provides Bitcoin with smart contract functionality and Layer2 scaling capabilities. sBTC brings BTC into a programmable on-chain environment, while Zest Protocol builds BTC lending markets and on-chain financial protocols on top of this infrastructure. Together, the three help Bitcoin evolve from a pure store-of-value asset into a financial asset system that can participate in lending, yield, and on-chain liquidity.

The core use case of Warden Protocol is to support AI Agents in automatically completing on-chain tasks while helping users handle multi-chain interactions, DeFi automation and asset management. Through its Intent system and Solver network, Warden Protocol lowers the barrier to complex on-chain operations.

Warden Protocol supports AI Agents in automatically completing on-chain actions through its Intent system and Solver network. It also helps AI Agents handle multi-chain execution, asset interactions and automated tasks. The core focus of Warden Protocol is to turn complex on-chain operations into goal-oriented execution flows.