Marlin (POND)

Overview

Marlin is a network infrastructure project with a native token called POND. Its original focus was helping computers on different blockchains share information faster. If a validator creates a block, other validators need to receive it before they can build on it. Marlin’s relay network was designed to move that data through a group of rewarded operators. The project calls this work “layer 0” because it takes place in the communication layer beneath blockchain applications. (docs.marlin.org)

Marlin has since expanded into off-chain computing. Its Oyster network lets developers run programs on outside computers and connect the results to blockchain applications. Kalypso is a related marketplace for generating zero-knowledge proofs. Together, these services address two common needs: moving data between participants and carrying out work that would be costly to run directly on a blockchain. POND helps coordinate participation in parts of this network. (docs.marlin.org)

History & Team

From networking to computing

Marlin appeared publicly in 2019 with a plan to improve peer-to-peer communication. That year, the project announced a $3 million fundraising round and named Binance Labs, Arrington XRP Capital, Electric Capital, and NGC Ventures among its supporters. The early idea was to reward nodes for forwarding blocks and transactions rather than depend only on volunteers to carry that traffic. (blog.marlin.org)

Siddhartha Dutta was identified as Marlin’s CEO in the project’s early announcements. Roshan Raghupathy was its head of engineering during its 2019 networking work. Marlin later described contributions from researchers and developers working on network design, incentives, and other parts of the protocol. Its work on Oyster and Kalypso shows how that initial interest in distributed infrastructure grew to include computing as well as communication. (blog.marlin.org)

In 2020, Marlin introduced POND and a second token, MPOND, alongside a distribution plan for operators, contributors, and participants from other blockchain communities. That plan tied ownership to the practical work of building and using the network. (blog.marlin.org)

Technology & How It Works

Relaying information

A blockchain network depends on messages reaching many computers. Marlin’s relay design uses groups of nodes to pass blocks from producers to receivers. Its documentation describes subscription fees paid by receivers and rewards for relayers that deliver data. This gives operators a reason to provide a useful service and creates records that help account for delivery. The design can serve different blockchains without requiring each one to create its own relay system from scratch. (docs.marlin.org)

Running programs off-chain

Oyster addresses a different task. A developer can rent a computer instance or send a job to a shared pool of machines. Oyster uses trusted execution environments, or TEEs. A TEE is a protected area of a computer that separates a program and its data from other software on the host. This lets applications use off-chain processing while giving them a way to check information about the environment where the code ran. Oyster supports both longer-running instances and serverless tasks that run when requested. (docs.marlin.org)

Kalypso focuses on zero-knowledge proofs. Such a proof can let another party check a result without repeating all the work used to produce it. In Kalypso’s design, an application requests a proof and a hardware provider offers to generate it. A matching system connects requests with providers based on factors such as price and completion time. Marlin describes that matching system as running on Oyster. TEEs and zero-knowledge proofs therefore serve different roles within the wider project. (blog.marlin.org)

Tokenomics & Utility

POND and MPOND

POND is Marlin’s transferable utility token. MPOND, short for MegaPOND, has a closer role in operating relay nodes and participating in governance. Marlin’s token design sets a 10 billion POND supply cap and a conversion rate of 1 MPOND for 1 million POND. The two forms are linked through a bridge, so their supply should be understood together rather than added as separate allocations. Converting POND into MPOND is immediate; converting MPOND back into POND takes place over about 182 days under the bridge rules described in Marlin’s documentation. (blog.marlin.org)

Operators can stake tokens, and holders can delegate POND or MPOND to relay operators. Rewards reflect the network’s incentive design, while MPOND holders can make or vote on governance proposals. Marlin’s original allocation set aside POND for staking rewards and ecosystem service providers, including validators and developers. Its FlowMint program was designed to distribute MPOND to participants from other blockchain communities. (blog.marlin.org)

POND also has a role beyond relaying. Oyster documentation identifies it as a staking token for parts of its computing network. At the same time, the Oyster instance marketplace identifies USDC as a payment token for compute jobs. That distinction matters: POND helps support participation and economic incentives, while a developer’s direct payment for a particular service may use another asset. (docs.marlin.org)

Ecosystem & Use Cases

Marlin’s services fit together, but each serves a different user. Relay operators work with block and transaction delivery. Application developers use Oyster to run backends, scheduled tasks, or programs that need private inputs. Teams building with zero-knowledge technology can use Kalypso’s design to find computing resources for proof generation. (docs.marlin.org)

One possible Oyster application is an exchange backend that needs to process orders quickly while leaving settlement to a blockchain. Another is an automated program that reads outside data and responds to on-chain events. Marlin has also published technical work on hosting a verifiable website frontend with Oyster and on using its TEEs in an AI-agent validation design. These examples show the range of systems developers can build with the tools; each application still has its own code and operating needs. (marlin.org)

Kalypso can serve applications that need proofs but do not want to maintain dedicated proving machines. A marketplace lets hardware providers offer capacity across different requests. This is especially relevant when proof generation needs specialized equipment or when an application’s demand changes over time. (blog.marlin.org)

Advantages & Challenges

Marlin’s broad design is an advantage for developers working across chains. Its relay tools focus on communication, while Oyster offers more general computing options. Kalypso adds a way to coordinate proof generation. Operators can contribute different resources—network connections, protected computer environments, or proving hardware—depending on the service. The token system gives relay participants a way to stake and delegate rather than requiring every holder to run a node. (docs.marlin.org)

The same breadth makes the project harder to explain and develop. Relaying a block, running a program in a TEE, and producing a zero-knowledge proof are distinct jobs. They call for different software, hardware, and ways to check performance. TEEs rely on protected computer hardware, while proof marketplaces need enough providers with suitable machines. Bringing more developers and operators into each service remains central to how useful the ecosystem can become. (docs.marlin.org)

Where to Buy & Wallets

POND is available on Kraken and Binance. Supported purchase methods and token networks depend on the platform and the user’s location. POND can also be held in a self-custody wallet that supports tokens on its listed networks. Marlin publishes POND contract addresses for Ethereum, Arbitrum, and BNB Chain; its relay staking contracts are on Arbitrum. (kraken.com)

A wallet must be set to the same network as the POND being sent to it. For example, an Ethereum token address and an Arbitrum token address identify different deployments. Marlin documents the official Arbitrum bridge for moving POND or MPOND between those networks. That bridge has a different purpose from Marlin’s bridge for converting POND and MPOND into each other. (docs.marlin.org)

Regulatory & Compliance

Marlin’s token and services operate within rules that depend on where an exchange, operator, or user is located. In the European Union, the Markets in Crypto-Assets framework sets authorization requirements for businesses providing covered crypto-asset services. In the United States, FinCEN guidance distinguishes ordinary virtual-currency users from businesses that exchange or transmit virtual currency. These rules concern activities and service providers; they do not assign POND one universal legal status across jurisdictions. (esma.europa.eu)

Islamic finance raises a separate question. A Shariah assessment of Marlin would need to consider the token’s uses and the terms of any staking, payment, or exchange activity. Marlin’s documentation explains those mechanisms, but it does not establish a project-wide halal certification or ruling. Its halal status therefore depends on the particular activity being assessed and the judgment applied to it. (blog.marlin.org)

Future Outlook

Marlin’s future development centers on whether its services become useful tools for more applications. Faster relay delivery remains relevant to networks that need to share blocks and transactions. Oyster provides a platform for developers who want off-chain programs connected to blockchain systems, while Kalypso addresses demand for proof-generating hardware. Marlin’s published work on verifiable frontends and AI-agent infrastructure illustrates possible directions for that computing stack. (docs.marlin.org)

The most meaningful signs of progress will be practical ones: applications using the tools, operators supplying resources, and services that developers can fit into working products. POND’s continuing role follows from that activity through staking, delegation, and network incentives. (docs.marlin.org)

Summary

Marlin began with a network-layer goal: help decentralized computers communicate efficiently. It now also offers protected off-chain computing through Oyster and a proof marketplace through Kalypso. POND connects participants to the project’s incentive system, while MPOND supports relay operation and governance. Marlin’s place in the crypto ecosystem is as infrastructure for moving information and carrying out work that blockchain applications need beyond their own chains. (docs.marlin.org)