<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>apis on Referently.com</title>
    <link>https://referently.com/tags/apis/</link>
    <description>Recent content in apis on Referently.com</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 14 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://referently.com/tags/apis/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Blockchain API Tutorial</title>
      <link>https://referently.com/blockchain-api-tutorial/</link>
      <pubDate>Thu, 14 May 2026 00:00:00 +0000</pubDate>
      
      <guid>https://referently.com/blockchain-api-tutorial/</guid>
      <description>Blockchain API Tutorial: Architectures, Verification, Smart Contracts, and Distributed Systems Blockchain APIs are often introduced as simple interfaces for querying balances, sending transactions, or interacting with smart contracts. That framing is technically correct, but it misses the deeper reality. A blockchain API is not merely a gateway into a database — it is an interface into a distributed consensus system operating under adversarial conditions.
Traditional APIs expose mutable centralized state controlled by a single authority.</description>
    </item>
    
  </channel>
</rss>
