Git3 @TryGit3

Bringing Git onchain for true ownership and x402 monetization git3.io Git Joined October 2025

Tweets

37
Followers

144
Following

12
Likes

122

Git3 @TryGit3

7 months ago

We're live on @tokensdotfun ! tokens.fun/coin/0x64A723c…

1 0 1 199 1

View Details

Git3 @TryGit3

7 months ago

@YIHEEEEEEEE Yes, we are!

0 0 0 20 0

View Details

We're still here. We're building. The protocol we're building on just became infrastructure-level. The pieces are falling into place — on-chain code ownership, AI agents paying royalties automatically, x402 as the payment standard for machine-to-machine transactions. This is early. The builders who show up now are the ones who'll matter. Join the Telegram if you want to follow the build in real time.

1 0 1 173 0

View Details

Git3 @TryGit3

7 months ago

@lesn343 @futarddotio last 5 hrs.

1 0 1 28 0

View Details

SrMessi.sol 🇦🇷 @0xSrMessi

7 months ago

Git3 just dropped: Git repos onchain as NFTs on Irys! True ownership, zero censorship, permanent history + monetize clones via x402. Vampire attack on GitHub, seamless Actions integration, no workflow change. AI agents + Code as an Asset = next $500B wave

1 1 9 634 0

View Details

Git3 @TryGit3

8 months ago

@KazarHQ @futarddotio @mycorealms LFG🔥

0 0 2 39 0

View Details

Git3 @TryGit3

8 months ago

futard.io/launch/6JSEvdU…

0 0 1 156 0

View Details

Git3 @TryGit3

8 months ago

@bharathshettyy @futarddotio LFG🔥

0 0 0 14 0

View Details

Git3 @TryGit3

8 months ago

Be ready: futard.io/launch/6JSEvdU…

0 0 2 145 0

View Details

Git3 @TryGit3

8 months ago

@IvanBullish @futarddotio @metaproph3t Let’s go

0 0 0 34 0

View Details

Git3 @TryGit3

8 months ago

@papitoweb @futarddotio @metaproph3t We must make it 🔥

0 0 0 44 0

View Details

Git3 @TryGit3

8 months ago

x.com/i/article/2031…

2 1 10 357 0

View Details

Git3 @TryGit3

8 months ago

@beeman_nl @0xSrMessi @solx_ar @irys_xyz See you at the ICO ser!

0 0 2 24 0

View Details

Git3 @TryGit3

8 months ago

Yeah, that’s a valid statement. Currently, we are in the MVP state, and the tooling, including the GitHub Action, is not fully open sourced yet, as the priority has been on validating the architecture and the end-to-end flow with Irys. Hopefully if we manage to close the round, the overall tooling, especially the new CLI, will be open and auditable. The pipeline is deterministic in nature, read repo state, build bundle, sign, and push to Irys. So, when the CLI is available under a permissive license, anyone will be able to run the publishing process locally or in their CI without depending on the GitHub Action.

1 1 2 125 0

View Details

Git3 @TryGit3

8 months ago

@sacha @futarddotio @trygit3 soon on @futarddotio

0 0 1 17 0

View Details

Git3 @TryGit3

8 months ago

@BR4ted Future code ownership

0 0 0 13 0

View Details

Git3 @TryGit3

8 months ago

Yes, that's correct for the current MVP. Currently, @TryGit3 runs through a GitHub Action that processes the repository state and uploads the resulting data to Irys; therefore, the workflow relies on GitHub as the execution environment. However, this is merely an orchestration layer and not a core requirement of the architecture. The plan is to add a CLI that does the same locally; therefore, the CLI will read the Git repository state from the .git directory, deterministically create the repository snapshot or object bundle for the commit, sign the upload transaction with the user's key, and upload the resulting data directly to Irys using its SDK/API. The fact that the process is deterministic and relies only on the repository state and the signing key means that the CLI can run locally or in any CI environment; therefore, GitHub will not be required.