Thanks to visit codestin.com
Credit goes to github.com

Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 3 additions & 10 deletions _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -13,20 +13,11 @@ author:

# Build settings
markdown: kramdown
theme: minima
plugins:
- jekyll-feed
- jekyll-seo-tag

# Minima color scheme
minima:
skin: classic

# Collections
collections:
posts:
output: true
permalink: /blog/:year/:month/:day/:title/
permalink: /blog/:title/

# Defaults
defaults:
Expand All @@ -50,3 +41,5 @@ exclude:
- vendor/gems/
- vendor/ruby/
- README.md


60 changes: 60 additions & 0 deletions _layouts/default.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,60 @@
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<title>{{ page.title }} | OWASP BLT</title>
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="{{ '/assets/css/style.css' | relative_url }}">
<link href="https://fonts.googleapis.com/css2?family=Inter:wght@400;500;600;700&display=swap" rel="stylesheet">
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.4.0/css/all.min.css">
</head>
<body>

<header class="top-nav">
<div class="nav-left">
<a href="{{ '/' | relative_url }}" class="logo-link">
<img src="{{ '/assets/images/owasp-blt-logo.svg' | relative_url }}"
alt="OWASP BLT"
class="blt-logo">
</a>
</div>

<div class="nav-right">
<button id="theme-toggle"
class="theme-toggle-btn"
aria-label="Toggle dark mode">
<i id="sun-icon" class="fas fa-sun sun-icon"></i>
<i id="moon-icon" class="fas fa-moon moon-icon"></i>
</button>
</div>
</header>

<main>
{{ content }}
</main>

<script>
const themeToggleBtn = document.getElementById('theme-toggle');
const htmlElement = document.documentElement;

// Check Local Storage or System Preference
if (localStorage.theme === 'dark' || (!('theme' in localStorage) && window.matchMedia('(prefers-color-scheme: dark)').matches)) {
htmlElement.classList.add('dark');
} else {
htmlElement.classList.remove('dark');
}

// Toggle Function
themeToggleBtn.addEventListener('click', () => {
if (htmlElement.classList.contains('dark')) {
htmlElement.classList.remove('dark');
localStorage.theme = 'light';
} else {
htmlElement.classList.add('dark');
localStorage.theme = 'dark';
}
});
</script>

</body>
</html>
81 changes: 81 additions & 0 deletions _layouts/home.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,81 @@
---
layout: default
title: Blog Posts
---

<section class="blog-hero">
<div class="blog-hero__container">

<h1 class="blog-hero__title">Blog Posts</h1>

<div class="hero-underline"></div>

<p class="blog-hero__description">
Discover the latest thoughts, tutorials, and updates from our community
</p>

<div class="blog-hero__search">
<div class="search-bar">
<input
type="text"
id="post-search"
placeholder="Search blog posts..."
class="search-bar__input"
>
<div class="search-bar__icon-wrapper">
<svg class="search-bar__icon" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor">
<path fill-rule="evenodd" d="M8 4a4 4 0 100 8 4 4 0 000-8zM2 8a6 6 0 1110.89 3.476l4.817 4.817a1 1 0 01-1.414 1.414l-4.816-4.816A6 6 0 012 8z" clip-rule="evenodd" />
</svg>
</div>
</div>
</div>

</div>
</section>

<section class="blog-grid-wrapper">
<div class="blog-grid">
{% for post in site.posts %}
<article class="blog-card">
<a href="{{ post.url | relative_url }}" class="blog-card__link"></a>

<div class="blog-card__image-wrapper">
{% if post.image %}
<img src="{{ post.image | relative_url }}" alt="{{ post.title }}" class="blog-card__image">
{% else %}
<div class="blog-card__placeholder">
<span>{{ post.title | slice: 0 }}</span>
</div>
{% endif %}

<span class="blog-card__badge">Article</span>

<div class="blog-card__author">
<div class="author-avatar">
{{ post.author | default: "O" | slice: 0 }}
</div>
<span class="author-name">{{ post.author | default: "OWASP BLT" }}</span>
</div>
</div>

<div class="blog-card__content">
<h2 class="blog-card__title">{{ post.title }}</h2>

<div class="blog-card__meta">
<svg fill="none" viewBox="0 0 24 24" stroke="currentColor">
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M8 7V3m8 4V3m-9 8h10M5 21h14a2 2 0 002-2V7a2 2 0 00-2-2H5a2 2 0 00-2 2v12a2 2 0 002 2z"/>
</svg>
{{ post.date | date: "%b %d, %Y" }}
<span class="dot">•</span>
<svg fill="none" viewBox="0 0 24 24" stroke="currentColor">
<path stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M12 6.253v13m0-13C10.832 5.477 9.246 5 7.5 5S4.168 5.477 3 6.253v13C4.168 18.477 5.754 18 7.5 18s3.332.477 4.5 1.253"/>
</svg>
5 min read
</div>

<span class="blog-card__read-more">Read more &rarr;</span>
</div>
</article>
{% endfor %}
</div>
</section>
29 changes: 29 additions & 0 deletions _layouts/post.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
layout: default
---

<div class="post-outer-container">

<article class="post-card">

<header class="post-header">
<h1 class="post-title">{{ page.title }}</h1>

<div class="post-meta-data">
By <span class="post-author">{{ page.author | default: "OWASP BLT Team" }}</span>
on {{ page.date | date: "%b. %d, %Y" }}
</div>
</header>

<div class="post-content">
{{ content }}
</div>

{% if page.image %}
<div class="post-footer-image-wrapper">
<img src="{{ page.image | relative_url }}" alt="{{ page.title }}" class="post-footer-image">
</div>
{% endif %}
</article>

</div>
42 changes: 42 additions & 0 deletions _posts/2025-02-22-Introducing-BACON.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,42 @@
---
layout: post
title: "Introducing BACON: The First Open Source Security Token Built on Bitcoin Runes"
date: 2025-02-22
author: krrish__sehgal
image: /assets/images/bacon.png
---

Bringing Blockchain-Based Incentives to Open Source Security
The open-source ecosystem thrives on collaboration, innovation, and shared knowledge. Yet, contributors often work tirelessly without direct financial incentives. At OWASP BLT, we believe that security and open-source contributions deserve recognition and rewards. That’s why we are introducing BACON, a new Bitcoin-based token built on the Runes protocol, to incentivize security research and open-source development.

Why BACON?
BACON is one of the first tokens leveraging the Runes protocol, a groundbreaking innovation in the Bitcoin ecosystem that enables fungible tokens without relying on additional layers like Ethereum or BRC-20. By adopting this cutting-edge technology within a year of its release, OWASP BLT is positioning itself as a pioneer in integrating Bitcoin-native incentives for open-source security work.

We have minted 1 trillion BACON tokens, which will be used to reward contributions such as:

Reporting and fixing security vulnerabilities.
Enhancing security research and development.
Contributing code, documentation, and improvements to OWASP BLT.
Engaging in bug bounty programs.
The Power of Bitcoin Runes
Unlike traditional blockchain tokens, Runes provides an efficient and scalable way to create and manage tokens directly on Bitcoin's UTXO model. This ensures:

Security: As a Bitcoin-native protocol, Runes benefits from the highest level of security and decentralization.
Simplicity: No smart contracts or sidechains—Runes operates purely on Bitcoin transactions.
Efficiency: A lightweight implementation that minimizes network congestion and fees.
How BACON Will Be Distributed
To ensure fair and meaningful adoption, BACON will be distributed through merit-based incentives rather than speculation. Some of the key ways to earn BACON include:

Bug Bounties: Security researchers who identify vulnerabilities in OWASP BLT and related projects will be rewarded in BACON.
Open Source Contributions: Developers contributing valuable code, documentation, or security improvements will earn BACON.
Community Engagement: Active participation in discussions, testing, and education initiatives will be recognized.
The Future of BACON and OWASP BLT
With BACON, we are not just launching a token—we are establishing a new model for incentivizing open-source security. Our goal is to make OWASP BLT one of the first open-source organizations to integrate a Bitcoin-based incentive mechanism for developers, researchers, and contributors.

As the Bitcoin ecosystem evolves, we see BACON as an opportunity to redefine how security and open-source development are rewarded, ensuring a more sustainable and secure future for all.

Join us in shaping this revolution—contribute to OWASP BLT, earn BACON, and be part of the future of open-source security on Bitcoin!




Original file line number Diff line number Diff line change
@@ -0,0 +1,55 @@
---
layout: post
title: "🌟 Introducing the New GSoC Leaderboard for Top Contributors for GSoC 2025 Projects"
date: 2025-03-09 18:53:00 +0000
categories: announcements
author: nitin_awari
image: /assets/images/leadrboard1.png
---


We are thrilled to announce the launch of a new GSoC 2025 Aspiring Contributors Leaderboard on the OWASP BLT (Bug Logging Tool) project! 🎉 This is an exciting opportunity for all contributors aiming to participate in Google Summer of Code (GSoC) 2025.
<br>
🔗 Check out the leaderboard here: [gsoc leaderboard](https://blt.owasp.org/gsoc/)
#### 🌱 What is the GSoC Aspiring Contributors Leaderboard?
The GSoC 2025 Aspiring Contributors Leaderboard is designed to recognize and motivate those individuals who are preparing to apply for GSoC 2025 with OWASP organisation. This leaderboard is a pre-GSoC initiative aimed at encouraging contributors to engage early, collaborate with mentors, and build their portfolios ahead of the official GSoC program.
#### 🎯 Key Features
🧵 **project listing** user can easily find out the owasp projects that are participating in gsoc 2025
<br>
🏆 **Rankings of aspiring contributors** based on their activity and contributions.
<br>
📈 **Tracking of GitHub contributions** and engagement with OWASP BLT repositories.
<br>
🔄 **Dynamic updates** reflecting recent pull requests, issues, and contributions to discussions.
<br>
🧑‍💻 **Clickable profiles** that direct to GitHub accounts, showcasing their work and progress.
<br>
🎨 **User-friendly design** for easy navigation and access to real-time stats.
<br>
#### 📅 Why This Leaderboard Matters
-The leaderboard is a great way for aspiring GSoC contributors to stand out and demonstrate their commitment to the project. Here’s how it can help:
🌟 **Visibility:** Mentors can easily spot active contributors who are passionate about OWASP projects and its goals.
🏁 **Motivation:** Tracking progress on the leaderboard gives contributors a sense of achievement and encourages them to keep engaging.
📚 **Skill-building:** By contributing early, aspiring students gain valuable experience that strengthens their GSoC applications.
🌍 **Community:** Joining the leaderboard fosters a sense of community, where like-minded contributors can collaborate and learn from each other.
#### 🙌 How Can You Participate?
If you’re an aspiring GSoC 2025 contributor and want to get involved, here’s what you can do:
<br>
**Fork the OWASP projects repository:** Start by forking the OWASP projects GitHub repository and begin exploring the issues.
<br>
**Contribute:** Work on open issues, make pull requests, and engage in discussions. The more active you are, the higher your ranking on the leaderboard!
<br>
**Collaborate with Mentors:** Connect with mentors and fellow contributors to learn and grow as a part of the OWASP community.
<br>
**Check Your Progress:** Track your contributions on the GSoC 2025 leaderboard to see where you stand.
<br>
#### 🌐 Get Ready for GSoC 2025
The GSoC 2025 season is still a few months away, but getting a head start by participating in the Aspiring Contributors Leaderboard can give you a competitive edge when it’s time to apply.
#### 🎉 Join Us!
This initiative is all about building a strong foundation for GSoC 2025, and we encourage all aspiring contributors to engage early and showcase their skills. Whether you’re new to OWASP BLT or have been following the project for some time, now is the perfect time to dive in!
<br>
💬 **Ready to get started?** Fork the OWASP repository and begin contributing today!
<br>
📣 **Spread the Word:**
<br>
Share the leaderboard and invite others to participate in this exciting pre-GSoC phase. Together, we can make the journey to GSoC 2025 even more impactful!
Original file line number Diff line number Diff line change
@@ -0,0 +1,43 @@
---
layout: post
title: "How to Deploy a Fungible Token on Bitcoin Ordinals"
date: 2025-08-26 05:23:00 +0000
categories: announcements
author: krrish__sehgal
image: /assets/images/bitcoin_ordials.png
---


My Journey Deploying the Bacon Token on Bitcoin Ordinals and Solana
When I first started exploring Bitcoin Ordinals and Solana, my goal was simple: understand how tokens can be created and deployed on two very different blockchain ecosystems. What began as curiosity turned into a full learning journey when I deployed BLT's token — Bacon — on both Bitcoin Ordinals and Solana.

Why Bitcoin Ordinals and Solana?
Bitcoin Ordinals opened up a new frontier, letting developers inscribe unique data (like NFTs or tokens) directly onto Bitcoin’s smallest units, satoshis. The challenge is that Bitcoin wasn’t originally designed for token deployments, so working around those limitations was both exciting and educational.
Solana on the other hand, is built with scalability and speed in mind. Deploying a token here is straightforward compared to Bitcoin, but it introduces its own set of concepts around smart contracts, accounts, and transaction fees.
By working with both ecosystems, I could compare the differences in token standards, deployment complexity, and community tooling.

My Process
On Bitcoin Ordinals: I had to start from scratch — syncing a Bitcoin Core node, setting up the Ordinals and Runes infrastructure, and inscribing data to represent the token. This was more about patience and infrastructure readiness than writing code.
On Solana: I used the Solana CLI and Token Program to deploy Bacon. This required understanding wallets, the SDK, and the basics of Solana’s programmatic token creation system.
Lessons Learned
Running a Bitcoin node is resource-heavy but essential for trustless token operations.
Solana’s ecosystem is developer-friendly, but comes with trade-offs in decentralization and reliance on RPC providers.
Security is key in both cases — from handling private keys safely to ensuring proper validation of transactions.
What This Blog Covers
In my full step-by-step guide on Medium, I break down exactly how I:

Set up the Bitcoin and Solana environments
Synced Bitcoin Core for Ordinals
Deployed the Bacon token on Solana using the CLI
Tested, verified, and interacted with the token
You can read the complete guide here and also see my work on Bitcoin Ordinals, including the actual Bacon inscription:
🔗 How to Deploy Runes and Ordinals on Bitcoin
🔗 Bacon Inscription

Further Developments for Bacon in BLT
Beyond deploying Bacon on Bitcoin and Solana, I am also actively contributing to BLT by building features around Bacon, including:

Streamlining of the UI: GitHub PR #4368
AI-Based Reward System: GitHub PR #4398
Staking Feature: GitHub PR #4461
I hope my journey inspires other developers to experiment with cross-chain token creation. If you’ve been curious about Ordinals, Runes, or Solana, this guide will give you the steps to deploy your own token from scratch.
Loading