Introduction

Welcome to Permagit, a decentralized, permanent, and secure solution for your source code version control.

What is Permagit?

Permagit leverages the power of familiar Git workflows, the decentralized identity of the Solana blockchain, and the permanent data storage of Arweave. It is designed for developers, teams, and organizations who demand censorship-resistance, verifiable permanence, and true ownership of their code repositories.

Unlike traditional, centralized platforms where your data can be deleted, censored, or lost, Permagit ensures that your code, its history, and its collaboration logs are stored immutably on the permaweb.

---

Core Concepts & Features

Permagit combines several next-generation technologies to create a seamless and robust developer experience. Here is a high-level overview of the key features we will cover in this documentation:

• Solana-Based Authentication: Forget usernames and passwords. Permagit uses your Solana wallet (e.g., Phantom, Solflare) as your primary identity. Your public key is your username, and your signature is your login.

• Permanent Storage on Arweave: Permagit uses Irys (formerly Bundlr) to bundle and upload your Git repository data to the Arweave network. This makes your repository permanent, globally available, and immutable. Once it's uploaded, it can never be deleted.

• Wallet-Based Encryption: For private repositories, Permagit provides robust, end-to-end encryption. A unique, 1:1 encryption key is derived from your Solana wallet, ensuring that only you (or those you grant access to) can decrypt and read your private code.

• Seamless CLI Integration: We provide an easy-to-install NPM package that acts as a terminal interface. This tool integrates directly with your existing local Git repositories, allowing you to use familiar commands like git push permagit to sync your work to the permaweb.

• Decentralized Collaboration: Permagit is built for teams. By utilizing multi-sig (multisignature) wallets, teams can collaboratively manage repositories. Pushing updates to a shared repository requires a threshold of signatures from team members, providing decentralized and secure access control.

---

Who is this for?

• Open-Source Developers seeking to guarantee their work is permanently preserved and censorship-resistant.

• Web3 & dApp Teams who want to build on a fully decentralized stack, from identity to code storage.

• Organizations that require a verifiable, immutable audit trail for their source code.

• Any developer who believes in data ownership and wants to secure their intellectual property on-chain.