Mergit
Developer bounties paid out by escrow once an agent confirms the pull request is merged and its tests pass; running on GIWA testnet
Developer bounties are locked up front in an escrow on GIWA Chain. When a pull request is merged and its CI tests pass, an agent confirms it from GitHub and the escrow pays the developer straight away. The pitch is that the merge is the invoice: no committee, application form or invoice in between.
As checked on 2026-09-24, a source-verified MergitEscrow contract is on GIWA Sepolia testnet, with four bounties posted and paid since 2026-07-31. All four were posted by the address that deployed the contract and paid to the same developer address, so they are the team's own tests; no outside bounty has been posted yet. The site replays one of them, a demo pull request merged on 2026-09-19 and paid 20 seconds later, and says 98.5% of each bounty goes to the developer.
Its site says it was submitted to GASOK 2026 Track 04 (AI/Web3). On 2026-09-22 it posted a screenshot of a GIWA email dated 2026-09-17 selecting it to present at the KBW 2026 Showcase on October 1.
Description from: mergit.xyz · @MergitonGIWA ↗ · the project's own description
Note: The evidence is a screenshot the team posted on X of a GIWA email (support@giwa.io, 2026-09-17) selecting it to present at the KBW Showcase. Neither the email nor the post says 'Phase 3', GIWA has not named the team publicly, and the X account was opened on 2026-09-19.
This list mixes projects' own announcements, tips from others and our own research, and its accuracy is not guaranteed. Being listed is not a recommendation or endorsement, nor does it mean a project is safe from shutdowns, hacks or rug pulls. Check for yourself before taking part.
Developer bounties locked on GIWA Chain, released by an agent that verifies the merged pull request and its CI.
The project's own Open Graph image and text.
About on X
@MergitonGIWAAn AI agent verifies merged pull requests and pays developer bounties on GIWA Chain. Merged, tested, paid in seconds. Building in public.
- Followers
- 9
- Following
- 1
- Posts
- 11
GASOK Phase 3
- Status
- Selected
- Track
- AI/Web3
- Evidence tier
- Selection email
- Evidence
- View source ↗
Based on a public statement by the project itself or a credible third party. GIWA has never published an official roster. Phase 3 is also an ongoing stage, so this means admission to it rather than completion.
What is GASOK Phase 3?
GASOK is Dunamu and Upbit's builder program for GIWA, an incubation running seven months or more. Phase 3 (Aug–Nov 2026) is the "market readiness & launch" stage, aiming at testnet user metrics and a private mainnet deployment. There are five tracks: DeFi/RWA, Consumer/Social, GIWA-Native, AI/Web3, and Mass Adoption.
What teams admitted to GASOK Phase 3 receive
- Engineering and productization support from the GIWA team, plus industry advisors
- Seoul office space if needed, and press and media support
- A shot at the KBW 2026 Showcase (the top team in each track, five in all)
- A $20K grant if picked at the Finalist Demo Day (date not yet announced), then up to $80K more tied to KPIs
The evidence is a screenshot the team posted on X of a GIWA email (support@giwa.io, 2026-09-17) selecting it to present at the KBW Showcase. Neither the email nor the post says 'Phase 3', GIWA has not named the team publicly, and the X account was opened on 2026-09-19.
Latest updates
This is how a repository is wired to Mergit. One workflow file that calls odiseo159-beep/mergit@v1, and one secret holding the verifier key. The pull request carries a bounty id. The agent reads the merge and the CI. The escrow pays on @GIWA_by_Upbit testnet. https://t.co/o0Y8tDHpFY
Every payment carries the evidence behind it. The agent hashes what it inspected: repository, PR, head commit, merge commit, every CI check. That hash goes on chain with the payment. Anyone can recompute it and see why the money moved. https://t.co/WWSEbFWKRL
MergitEscrow has no owner, no pause and no upgrade path. The agent names who gets paid. It cannot change the amount, pay twice, pay after the deadline or touch any other bounty. If software is going to release money, that is the only shape it should have. https://t.co/AD4PD5NrLG
Mergit is live at https://t.co/amjFvHd9f5 Lock a bounty on-chain. Merge the pull request. An agent checks it and the escrow pays the developer. The site replays the real one: merged 00:49:36, paid 00:49:56. https://t.co/BAZ5RJF95z
Something wrong or missing on this project? Tell us on Telegram ↗ Partnership enquiries reach us the same way.
Projects in the same category
A non-custodial AI layer that plans and simulates onchain jobs from plain words, leaving the signing to you
Evidence tier: Self-announced
An on-chain media guardian that seals AI-media verification evidence onto GIWA
Evidence tier: Self-announced
Cross-dApp contribution and rights score layer
Evidence tier: Self-announced