<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Omar Baruzzo</title>
    <description>The latest articles on DEV Community by Omar Baruzzo (@omarbaruzzo).</description>
    <link>https://dev.to/omarbaruzzo</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3871271%2F50981d31-31ef-4f39-90a0-68f15adc1f24.png</url>
      <title>DEV Community: Omar Baruzzo</title>
      <link>https://dev.to/omarbaruzzo</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/omarbaruzzo"/>
    <language>en</language>
    <item>
      <title>Token je pravo, ne sama imovina</title>
      <dc:creator>Omar Baruzzo</dc:creator>
      <pubDate>Tue, 15 Sep 2026 11:24:27 +0000</pubDate>
      <link>https://dev.to/omarbaruzzo/token-je-pravo-ne-sama-imovina-28na</link>
      <guid>https://dev.to/omarbaruzzo/token-je-pravo-ne-sama-imovina-28na</guid>
      <description>&lt;p&gt;Tokenizirati imovinu je lak dio. Token je pravo, a pravo vrijedi onoliko koliko i obveza iza njega. Evo checkliste koju stvarno gledam kad je pregledavam.&lt;/p&gt;

&lt;p&gt;Binding: tko jamči da 1 token = 1 jedinica imovine, kroz vrijeme? Custodian, posebno društvo, pravni okvir — ne smart contract.&lt;/p&gt;

&lt;p&gt;Redemption: burn tokena, otpuštanje imovine. Tko je obvezan isporučiti i što kod neispunjenja obveze ili zamrzavanja prijenosa? To je put koji većina dizajna ostavi tankim.&lt;/p&gt;

&lt;p&gt;Proof-of-reserve: provjerljiv i potpisan po rasporedu, ne priopćenje.&lt;/p&gt;

&lt;p&gt;Permissioned transfer za reguliranu imovinu: allowlist, identitet, ograničenja upisana u token, ne bearer instrument.&lt;/p&gt;

&lt;p&gt;Smart contract je vidljivi vrh. Sustav je integracijski sloj oko njega: promatraj on-chain evente, usklađuj svaki token s off-chain zapisom, prati redemptione, zapisuj ondje gdje revizor može čitati. Obično integracijsko inženjerstvo, i tu odlaze mjeseci.&lt;/p&gt;

&lt;p&gt;Puna verzija: &lt;a href="https://www.omarbaruzzo.it/hr/blog/tokenizzare-non-e-possedere" rel="noopener noreferrer"&gt;https://www.omarbaruzzo.it/hr/blog/tokenizzare-non-e-possedere&lt;/a&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>enterprise</category>
      <category>tokenization</category>
    </item>
    <item>
      <title>Un token è un diritto, non il bene</title>
      <dc:creator>Omar Baruzzo</dc:creator>
      <pubDate>Tue, 15 Sep 2026 11:23:15 +0000</pubDate>
      <link>https://dev.to/omarbaruzzo/un-token-e-un-diritto-non-il-bene-3j26</link>
      <guid>https://dev.to/omarbaruzzo/un-token-e-un-diritto-non-il-bene-3j26</guid>
      <description>&lt;p&gt;Tokenizzare un asset è la parte facile. Il token è un diritto, e un diritto vale quanto l'obbligo che ha dietro. Ecco la checklist che guardo davvero quando ne rivedo uno.&lt;/p&gt;

&lt;p&gt;Legame: chi garantisce che 1 token = 1 unità del bene, nel tempo? Un custode, una società veicolo, un contratto — non lo smart contract.&lt;/p&gt;

&lt;p&gt;Riscatto: brucia il token, rilascia il bene. Chi è obbligato a consegnare, e cosa succede in caso di inadempienza o congelamento dei trasferimenti? È il percorso che quasi tutti lasciano sottile.&lt;/p&gt;

&lt;p&gt;Prova delle riserve: verificabile e firmata con una cadenza, non un comunicato.&lt;/p&gt;

&lt;p&gt;Permissioned transfer per i beni regolati: allowlist, identità, restrizioni scritte nel token, non uno strumento al portatore.&lt;/p&gt;

&lt;p&gt;Lo smart contract è la punta visibile. Il sistema è il layer di integrazione intorno: osserva gli eventi on-chain, riconcilia ogni token col record fuori catena, traccia i riscatti, scrivi dove il revisore può leggere. Ingegneria di integrazione ordinaria, e lì vanno i mesi.&lt;/p&gt;

&lt;p&gt;Versione completa: &lt;a href="https://www.omarbaruzzo.it/it/blog/tokenizzare-non-e-possedere" rel="noopener noreferrer"&gt;https://www.omarbaruzzo.it/it/blog/tokenizzare-non-e-possedere&lt;/a&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>enterprise</category>
      <category>tokenization</category>
    </item>
    <item>
      <title>A token is a claim, not the asset</title>
      <dc:creator>Omar Baruzzo</dc:creator>
      <pubDate>Tue, 15 Sep 2026 11:21:20 +0000</pubDate>
      <link>https://dev.to/omarbaruzzo/a-token-is-a-claim-not-the-asset-2in</link>
      <guid>https://dev.to/omarbaruzzo/a-token-is-a-claim-not-the-asset-2in</guid>
      <description>&lt;p&gt;Tokenizing an asset is the easy part. The token is a claim, and a claim is only worth the obligation behind it. Here is the checklist I actually care about when I review one.&lt;/p&gt;

&lt;p&gt;Binding: who guarantees 1 token = 1 unit of the asset, over time? A custodian, an SPV, a legal wrapper — not the contract.&lt;/p&gt;

&lt;p&gt;Redemption: burn the token, release the asset. Who is obligated to deliver, and what happens on a default or a transfer freeze? This is the path most designs leave thin.&lt;/p&gt;

&lt;p&gt;Proof-of-reserve: verifiable and signed on a schedule, not a press release.&lt;/p&gt;

&lt;p&gt;Permissioned transfer for regulated assets: allowlists, identity, restrictions encoded in the token itself, not a free-floating bearer instrument.&lt;/p&gt;

&lt;p&gt;The smart contract is the visible tip. The system is the integration layer around it: watch on-chain events, reconcile each token against the off-chain record, track redemptions, write it where auditors can read it. Ordinary integration engineering, and where the months go.&lt;/p&gt;

&lt;p&gt;Full version: &lt;a href="https://www.omarbaruzzo.it/en/blog/tokenizzare-non-e-possedere" rel="noopener noreferrer"&gt;https://www.omarbaruzzo.it/en/blog/tokenizzare-non-e-possedere&lt;/a&gt;&lt;/p&gt;

</description>
      <category>blockchain</category>
      <category>enterprise</category>
      <category>tokenization</category>
    </item>
    <item>
      <title>Free Open Source IdentityServer for .NET 10: Getting Started with IdentityServer10</title>
      <dc:creator>Omar Baruzzo</dc:creator>
      <pubDate>Fri, 10 Apr 2026 08:22:16 +0000</pubDate>
      <link>https://dev.to/omarbaruzzo/free-open-source-identityserver-for-net-10-getting-started-with-identityserver10-44d3</link>
      <guid>https://dev.to/omarbaruzzo/free-open-source-identityserver-for-net-10-getting-started-with-identityserver10-44d3</guid>
      <description>&lt;h1&gt;
  
  
  Why we need a free IdentityServer for .NET 10
&lt;/h1&gt;

&lt;p&gt;With the evolution of the .NET ecosystem, many developers are looking for a &lt;br&gt;
community-driven, open-source solution for OIDC and OAuth2.&lt;/p&gt;

&lt;h2&gt;
  
  
  Introducing IdentityServer10 by Omar Baruzzo
&lt;/h2&gt;

&lt;p&gt;IdentityServer10 is a direct port of IdentityServer4, updated and &lt;br&gt;
fully compatible with &lt;strong&gt;.NET 10&lt;/strong&gt;. It provides a free alternative for &lt;br&gt;
those who want to stay on the latest LTS version of .NET.&lt;/p&gt;

&lt;h3&gt;
  
  
  Key Features:
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;Full support for &lt;strong&gt;.NET 10&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;Open Source and Community maintained&lt;/li&gt;
&lt;li&gt;Easy migration from IdentityServer4&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Get Started
&lt;/h3&gt;

&lt;p&gt;You can find the source code, documentation, and samples here:&lt;br&gt;
👉 &lt;a href="https://github.com/omarbaruzzo/IdentityServer10" rel="noopener noreferrer"&gt;https://github.com/omarbaruzzo/IdentityServer10&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Installation
&lt;/h3&gt;

&lt;p&gt;You can pull the packages directly from NuGet:&lt;br&gt;
&lt;code&gt;dotnet add package OmarBaruzzo.IdentityServer10 --version 10.0.1&lt;/code&gt;&lt;/p&gt;

</description>
      <category>dotnet</category>
      <category>csharp</category>
      <category>opensource</category>
      <category>identityserver</category>
    </item>
  </channel>
</rss>
