📔
Blockchain API guides
  • Welcome to Data123 Documents!
  • Quick Start
  • Reference
    • API Reference
      • Aleo
        • RPC Methods
          • Latest Height
          • Latest Hash
          • Latest Block
          • Latest State Root
          • Get Block
          • Get Blocks
          • Get Block Transactions
          • Get Transaction
          • Get Confirmed Transaction
          • Get Memory pool Transactions
          • Get Progrem
          • Get Mapping Names
          • Get Mapping Value
          • Get State Path For Commitment
          • Find Block Hash
          • Find Transaction ID From Program ID
          • Find Transaction ID From Transition ID
          • Find Transition ID
          • Get Environment Info
          • Transaction Broadcast
      • Drand
        • JSON-RPC Methods
      • Filecoin
        • JSON-RPC Methods
      • Ethereum
        • JSON-RPC Methods
      • Starknet
Powered by GitBook
On this page
  1. Reference
  2. API Reference

Filecoin

PreviousJSON-RPC MethodsNextJSON-RPC Methods

Last updated 1 year ago

Filecoin is a peer-to-peer network that stores files, with built-in economic incentives and cryptography to ensure files are stored reliably over time.

Filecoin is built on top of the same software powering protocol, which is a peer-to-peer distributed storage network that leverages to allow permanent references to the data, and avoids relying on specific devices or cloud servers for addressing the content. Filecoin is different from IPFS because it has an incentive layer on top to incentivize contents to be reliably stored and accessed.

In order for your Web3 application to interact with Filecoin — either by reading blockchain data or sending transactions to the network — it must connect to a Filecoin node. Developers interact with the blockchain using the methods provided by the API.

The API interaction follows the which is a stateless, light-weight remote procedure call (RPC) protocol. It defines several data structures and the rules around their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over HTTP, or in other message-passing environments. It uses JSON (RFC 4627) as data format.

IPFS(opens in a new tab)
content addressing(opens in a new tab)
JSON-RPC(opens in a new tab)