Blog

Türkiye'de son yıllarda yaşanan büyük ölçekli veri sızıntıları, vatandaşların kişisel bilgilerinin ne kadar savunmasız olduğunu gözler önüne serdi. Bu sızıntıların ortak noktası: merkezi sistemlerde depolanan milyonlarca vatandaş bilgisinin tek seferde çalınması. Peki bu felaket senaryolarının tamamı Öz Kimlik (Self-Sovereign Identity - SSI) teknolojisi ile önlenebilir miydi?

İnternetin gelişimiyle birlikte dijital kimlik yönetimi, basit kullanıcı adı-şifre sistemlerinden günümüzdeki karmaşık sistemlere doğru büyük bir evrim geçirdi. Ancak mevcut merkezi sistemlerin güvenlik açıkları ve gizlilik sorunları, yeni bir yaklaşıma olan öz kimlik (Self-Sovereign Identity - SSI) teknolojisine olan ihtiyacı ortaya çıkardı.

We've explored how AI agents establish their identities through Know Your Agent (KYA) systems and manage credentials via MCP identity wallets. But there's a paradigm shift happening that goes far beyond agents simply serving humans: AI agents are beginning to form their own social networks. Welcome to the era of personal social graphs for agentic AI – where agents don't just work for us, they work with each other.

Building on the foundational concept of Know Your Agent (KYA), let's dive into how this vision is already becoming reality through a powerful combination: Model Context Protocol (MCP) servers functioning as identity wallets for AI agents. This isn't just theoretical anymore – the infrastructure exists today to give AI agents their own secure digital identities and credential management systems.

While established DID methods like did:ion, did:ethr, did:key, and did:web have pioneered the decentralized identity landscape, they each carry inherent limitations that become apparent at scale. Enter did:scid—a new DID method specifically designed to maximize the benefits of Self-Certifying Identifiers (SCIDs) while addressing the core challenges that have constrained earlier implementations.

OpenID for Verifiable Presentations (OIDC4VP) 1.0 represents a significant advancement in standardizing verifiable credential presentation protocols. Built as an extension to OAuth 2.0, this specification addresses the critical gap in interoperable credential presentation mechanisms within the self-sovereign identity ecosystem.

Know Your Agent (KYA) emerges as a crucial framework built on self-sovereign identity principles, offering a practical solution for managing AI agent credentials before we actually need them.

As we navigate through countless online platforms and services, our digital identities have become fragmented, scattered across numerous databases and systems that we neither control nor fully understand. This fragmentation isn't just an inconvenience – it's a fundamental flaw in how we manage our digital presence.

Verifiable Presentation (VP) exchange protocols ensure that digital credentials are verified and exchanged in a manner that maintains privacy and security. Among the various protocols available, OpenID Connect for Verifiable Presentations (OIDC4VP) stands out as a superior option.

Self-Sovereign Identity (SSI) is a digital identity management concept that enables individuals to have greater control and ownership over their personal data. It operates independently of third-party public or private actors and is based on decentralized technological architectures.

I recently switched to a new Mac, and I realized remembering all these things to set it up properly can be very challenging. So, I decided to create a guide to follow for the next time, I hope it will be handy for you as well.

Following up on my commitment from the previous blog post, I'm diving deeper into blockchain use-cases that hold significant potential for businesses. In today's discussion, we're going to explore the intriguing application of using NFTs as proof of authenticity certificates in more detail.

In this blog post, we will be diving into an exciting topic that's close to my professional heart: web3 in the enterprise world. As a principal product manager in the web3 space, I've seen firsthand how this technology is not just a buzzword or a trend, but a real game-changer for businesses around the world.

If you're looking to access your Raspberry Pi securely from anywhere in the world, you've come to the right place (I recently solve that problem, so I am writing it down to not forget it in the future). Often, we need remote access to our devices, whether for monitoring a home system, managing a server, or working on various projects.

Verifying credentials that can actually be verified and presentations that are also verifiable has become a major part of how Self-Sovereign Identity (SSI) systems work. So, what does this mean? Usually, it means identifying the DID document of whoever is issuing the credential or both the person holding and issuing the verifiable presentation. This is done to get access to their public key, essentially a unique identifier. While a lot of the popular ways to do this use a type of technology called Distributed Ledger Technology (DLT) or blockchain to link the DID document and make it available for everyone to see, there are problems with trust when it comes to data that's collected this way.

Decentralized Identifiers (DIDs) are a key component in the realm of decentralized identity. To understand this revolutionary space better, consider the comparison between four of the most popular DID methods, did:ion, did:ethr, did:key, and did:web

I personally don't like NFTs (at least the trading/owning an artwork part), but I really like Ethereum Name Service (ENS). I have both ENS domain and my profile picture as NFT, which I minted a while ago to test things out. Today, we can try to link them together to get rid of standard avatar.

If you are reading this post, I assume you are already heard of Self-Sovereign Identity (SSI) concept and Decentralized Identifier (DID). In this post, I will show you how to create a DID and publish it using one of the most basic DID method available, did:web.

In order to access a remote server from your personal computer, you will need to upload your SSH public key to the authorized keys of the server.

"qroxy" name is originated from concatenating "qr code" and "proxy" words, it will hopefully give idea of the project overview. In plain English, it is a dynamic QR code generator REST API with a connected mongoDB to store routes.

Last year, it was an eye-opening experience for me to start working on Self-Sovereign Identity field. Currently, I am managing the Identity and Access Management product in Energy Web, and it gives me lots of insights on the concept and real-world use-cases. In this post, I covered centralized and federated identity models.

Eski yazılarımı derlerken Temmuz 2017 yılında (tam 5 sene önce) yayınlamış olduğum Ethereum hakkında yazdığım bu Medium makelesini buldum ve birkaç edit ile tekrar yayınlamaya karar verdim.

When you decide to go deeper with your blockchain integration, you have to setup a blockchain node. By node, we generally think of a full node, but what if you have another alternative that you can run even on your IoT devices?

mosh is a very powerful ssh extender, especially when you are accessing your VPS over mobile network or different public access points. I will only cover how to install it on a Ubuntu VPS and how to use it effectively.

Elektrik şebekesini kısaca üretim, iletim, depolama ve tüketim elemanlarını sürekli olarak birbirine bağlayan dinamik bir ağ olarak nitelendirebiliriz. Bu şebekenin sağlıklı bir şekilde işlevselliğini koruyabilmesi için tahmin edebileceğiniz üzere arz ve talebin dengede olması gereklidir. Enerji şebekeleri hayatımıza girdikleri ilk anda enerji ihtiyacımızın tamamı merkezi ve kontrol edilebilir bir üretime (termik, hidroelektrik, vs.) dayandığı için sistem esnekliği kavramı pek bir öneme sahip değildi.

When trying to reach an API or service from localhost can be really painful due to CORS policies.

Lee Robinson made a fantastic job for creating this fantastic frontend code made with Next.js and Tailwind CSS. He also made some great integrations with Github, Youtube, Spotify using their APIs. When I try to edit his frontend I really like the Spotify Now Playing add-on on the footer. So, I decided to keep it. I will try to explain how to get a Refresh Token for using this API.