bGitX

bGitX · built on bWalletX

Your code,
on b.

Connect your GitHub. Give each repo a room, the people who work on it, and terms everyone signed. Kintsugi fixes and builds by opening pull requests. Nothing merges without your OK.

Connect your repos Get bWalletX

Connecting repos and repo rooms work today. Encrypted on-chain snapshots are coming.

  1. Connect
  2. Mint
  3. Room
  4. Invite
  5. Terms
  6. Kintsugi

How it works

Six steps from repo to shipped.

Your code stays yours. bGitX adds a room, the people, the terms and a builder that asks before it merges.

  1. Connect your GitHub

    Pick the repos b can see. Nothing else is touched. You can disconnect any time.

    Live

  2. Mint your repo

    A snapshot of the repo is sealed on chain, encrypted to your keys. It is private by default. Showing it to anyone is a separate step you choose.

    Coming

  3. Open a room for it

    Each repo gets its own room in bChatX. Talk about the code where the code lives.

    Live

  4. Invite collaborators

    Bring in the people who work on it. A repo token records who owns and worked on the code, and gives access to the room.

    Testing

  5. Agree terms with bSignX

    Who did what, who can merge, who gets access. Written down and signed by everyone in the room before work starts.

    Testing

  6. Kintsugi fixes and builds

    Report a bug or ask for a feature. Kintsugi works in a branch and opens a pull request. You review it. Nothing merges without your OK.

    Live

Your OK, every time

A builder that asks first.

Kintsugi is the repair engine behind b. It does the work. You keep the say.

  • Pull requests, not pushes. Every change arrives as a pull request on a branch. You read the diff and the test results before anything lands.
  • Nothing merges without your OK. No silent commits to main. No surprise deploys.
  • Narrow access. Kintsugi sees only the repos you pick. It holds no production secrets, no deploy rights and no wallet keys.
  • No passwords in chat. We never ask for your passwords or keys. Secrets stay in your hosting, set by you.
  • Private by default. A minted snapshot is encrypted to your keys. Making it public is a separate, deliberate step.
  • Security reports stay private. They skip the queue and are never shown in a room.

Part of the b*X family

Works with the rest of b.

bWalletXYour keys, your signatures, your minted snapshots. Where you say OK. bChatXA room for every repo. Talk to your collaborators and to Kintsugi. bSignXTerms for the repo, signed by everyone in the room.

Status

Live, testing, and coming.

Items move to Live when you can use them.

  • Live

    Connect your repos to Kintsugi. Report bugs and ask for features; Kintsugi opens pull requests. www.bchatx.com/user/kintsugi

  • Live

    Repo rooms in bChatX. One room per repo, with its collaborators. bChatX

  • Testing

    Repo tokens. A record of who owns and worked on the code, and access to the room.

  • Testing

    Contributor splits. Worked out from the repo's history, agreed in bSignX.

  • Coming

    Encrypted on-chain repo snapshots, private by default.

  • Coming

    GitLab import.

  • Coming

    bDojoX.

Start here

Bring your code on b.

Connect your repos to Kintsugi in bChatX. Get bWalletX to sign and approve.

Connect your repos Get bWalletX