Build

Register your login. Get paid there.

The escrow pays a wallet, so it has to know which wallet is yours. You record on-chain that a GitHub account belongs to you and point at a proof only that account could publish. From then on, a bounty for your merged work pays the wallet you registered, not an address someone else wrote in a file. Mergit never sees a key: your wallet signs, and the only thing it signs is this record.

Publish the proof first

Put this line in a public gist, or in the README of the repository named after you. It is what makes the record true, and anyone can re-read it later:

Fill in your GitHub login and your address, and this line is ready to copy.

Why on-chain

The contract cannot read GitHub, so it does not check the proof: it records the login, its date and where the proof lives. Anyone can then re-check it, and the agent does exactly that before paying. A record whose proof does not hold is not paid, and the agent never falls back to a file.

Already registered?

Type your login and press Check the proof: if the login is taken, the page tells you by whom. To move a login to another wallet, the current one releases it first.