Why we built Gitbank around gitAssets, not regular wallets.
With a regular wallet, one wrong address and your funds are gone. One malicious token approval and a bot drains everything overnight. Bridges get exploited. Private keys leak. People lose funds not because they did anything reckless but because the system was designed to let that happen.
Gitbank works differently.
When you deposit USDC or WETH into your vault, you receive gitUSDC or gitWETH in return. These are not regular ERC-20 tokens. They are soul-bound to your GitHub account. Non-transferable. Non-approvable. No contract, no bot, no phishing site can move them on your behalf because the transfer and approve functions simply do not exist in the contract.
Your GitHub ID is the anchor. Not your username, which can be renamed, but your permanent numeric GitHub ID, an immutable integer that cannot be spoofed or transferred. It is baked into your vault address on Base L2 at deployment time. No one else can claim your vault.
Even if your private key is compromised, your gitAssets cannot be moved. There is no function to call, no approval to exploit, no signature to forge. The soul-bound mechanism makes the private key irrelevant to the safety of your funds.
Funds move only in two cases. You explicitly command @gitbankbot in a GitHub issue or PR, or a PR merge triggers an auto-payout that you already configured. That is it. There is no other path.
For transfers between vaults, Gitbank uses a two-step commit-reveal: initTransfer locks a hash commitment on-chain, finalizeTransfer verifies a signature before releasing. Front-running is structurally impossible.
Summary of what becomes impossible with gitAssets:
- Sending to a wrong address by accident
- Approval exploit draining your vault
- Phishing site requesting unlimited token approvals
- Private key leak emptying your balance
- Any third party moving your funds without an explicit GitHub comment from you
- Your USDC is still your USDC. Your WETH is still your WETH. They just cannot move without your GitHub identity confirming it.
Try it on the playground: https://t.co/w7qKjt60QS
Install on your repo: https://t.co/7ggGXrO8Uk
Docs: https://t.co/3Mc1Ld1FvA
Go to the Gitbank playground on GitHub. Comment anything:
@gitbankbot help
@gitbankbot balance
@gitbankbot deposit 1 USDC
That's it. Your GitVault deploys automatically on your first command a smart contract on Base mainnet, permanently anchored to your GitHub user ID. The bot replies in seconds with a receipt and a Basescan link so you can verify everything on-chain yourself.
The only thing you need beforehand is USDC or WETH on Base mainnet. If you're already on Base, skip straight to commenting. If not, bridge in 60 seconds via Coinbase Bridge or Superbridge.
From that point forward, your vault is live. Deposit, withdraw, swap, send to other contributors, create project budgets, assign bounties all by commenting in GitHub Issues, Pull Requests, or Discussions. The bot handles the transaction. The deployer pays your gas. You just write.
This is what frictionless on-chain finance actually looks like.
https://t.co/w7qKjt6yGq
Your tokens go in. Soul-bound GitTokens come out. Nothing can touch them.
When you deposit USDC or WETH into Gitbank, something important happens at the contract level that most people don't think about.The moment your ERC-20 transfer lands at your vault address on Base Mainnet, the bot detects the on-chain event automatically. You don't send a command. You don't click anything.
The deposit poller catches the transfer, the contract validates the signature, deducts the protocol fee, and mints an equivalent amount of soul-bound GitTokens locked inside your vault 1:1 net of fee.Those GitTokens have no transfer function. No approve function. No way for a malicious site, a compromised key, or a phishing attack to move them. The underlying asset cannot leave your vault until you explicitly call gitUnshield. That's not a policy. That's the contract.
The fee is straightforward: 0.10% of the deposit amount, with a $0.05 minimum. Send 100 USDC, receive 99.90 gitUSDC. Send 0.5 WETH, receive 0.499500 gitWETH. For deposits under $50, the flat $0.05 minimum applies. The fee is deducted from your input never added on top.
Every deposit emits a FeePaid and Locked event on Base Mainnet.
The bot replies to your GitHub thread with a full receipt: transaction hash, new balance, and a Basescan link to verify everything yourself.
This is what it means to hold assets you actually control.
gitShield. Deposit once. Phishing-proof forever. $Gitbank
GitBank $GITBANK is now live!
0xC21dd0eE043930711C2a3e55F39C7d3144d09B07
GitBank connects GitHub with smart contracts on Base L2.
Repository funding, issue bounties, autonomous contributor payouts, terminal-native treasury management, and AI agent execution directly inside developer workflows.
An operating layer for developers and agents.
https://t.co/9oOoAyzVrP
Batarya Değişim Zamanı Gelince, Sizle Görüşeceğiz 😱😱😱😱
Diyen Sevgili Arkadaşlar 👇👇👇
8 Yıl Garantili Tesla Model Y Jüniperin Bataryası 389.000
Renault megan,duster,clio 1.3 tce aracın sandık motoru 398.000
Fıkra bu kadar 😉 @TeslaClubTurkey
🔴 | Ankara Mamak'ta evden kaçan poodle cinsi bir köpeği, başıboş köpekler parçalayarak telef etti.
Mamak Belediye Başkanı @veligunduzsahin, nefes alan her canlıya saldırarak yok eden bu canavarları toplamak için neyi bekliyorsunuz? @AliYerlikaya
"hiç beklenmedik yerden bile para gelmesini ve banka hesabınızın parayla dolmasını" istiyorsanız bu görseli duvar kağıdınız yapın, bir süredir deneyimliyorum inanılmaz çalışıyor
#kzbgy 8 ayda h1 hedefimiz gerçekleşmiş 😎 Net olarak %101 kazanç sağladı. Ücretsiz eğitim veriyoruz asla ama asla yatırım tavsiyesi değildir. Kendi hayal ürünümdür. Beğeni sayısı 100 ü geçmezse bundan sonra paylaşım yapmayacağım bunca başarılı analiz desteklenmeyecekse bırakırım