Build TauGet paid.
The Tau Bounty Program pays developers to ship real work on the Tau network. Every bounty is a scoped GitHub issue with a fixed USD denominated reward, paid once your work is merged.
Work that moves the network forward
We post bounties where outside builders can make the biggest difference. Each round focuses on one area of the protocol.
From pull request to payout
Current round: payments on Tau
Three bounties that let rules start payments, show which rules are in force, and let senders and receivers set conditions on how money moves.
01 Programmable paymentsOpen#34 #35 #63critical $9,460
02 Clear view of active rulesOpen#42critical $1,700
03 Recipient controlsOpen#47 #76 $640
What each bounty delivers
Programmable payments
Standing instructions the network carries out while the wallet is offline, such as monthly rent, “save 20% of what I receive” and royalty payouts. It also covers conditions the sender attaches to the money: spending limits, time locks, refunds of unspent funds, or any mix of these in one payment.
Rules can only allow or block a payment today. They can’t start one or shape what happens after it arrives. This unlocks rent, savings, payroll, escrow, allowances, vesting and grants.
designSafety designDecide who pays the network fee when a rule sends money, which events can trigger a payment, and how to stop rules from triggering each other in an endless loop.
Recurring payments (#34)Send a set amount on a schedule, such as rent on the 1st of every month, without the owner signing each time.
Auto-split incoming funds (#35)Split money as it arrives, for example moving 20% of every payment received into savings.
Payouts calculated by a rule (#63)Pay an amount a rule works out, such as a 5% royalty on each sale or releasing escrow once conditions are met.
designHow periods are measuredDefine what a period is (a day, a week, a month) and track how much each recipient has spent in it.
Spending limitCap how much Bob can spend from Alice’s funds in each period, for example $500 a week.
Custom spending allowanceLet Alice set a different cap for each recipient or for each payment she sends.
Recurring limitsReset the cap automatically at the start of each period, so the allowance renews without Alice doing anything.
designHow rules tell the timeTime-based rules need to know the current date and time. Decide where that comes from: the time recorded on each block of the blockchain, or a trusted outside clock (#62).
Locked fundsFunds can’t be spent until a set date, such as a gift that unlocks on a birthday or tokens that vest next year.
Scheduled availabilityFunds can only be spent on days or hours Alice chooses, for example weekdays only for business spending.
Temporary restrictionsFunds stay unavailable for a set time after they arrive, for example 48 hours, then become spendable.
designRefund triggers and feesDecide which conditions start a refund and who covers the network fee for sending it back.
Automatic refundIf Bob hasn’t spent the funds within a set period, whatever is left returns to Alice.
Expiration dateFunds expire on a set date, and any unspent balance returns to Alice.
designHow conditions combineDecide how several conditions on one payment work together, and which one wins if two of them conflict.
Several conditions on one paymentLet one payment carry any mix of spending limits, time locks and refunds.
Working example: Alice sends Bob $5,000A full demo on the testnet. Bob can spend at most $500 a week, only from December 1, and anything he hasn’t spent by the deadline returns to Alice.
Clear view of active rules
A way for wallets and apps to ask the network which rules are active on an account right now, and get a correct answer.
One user’s rule was accepted, confirmed and charged a fee, yet never took effect. Wallets can’t honestly say “your protection is on”, and both sides of a payment need to see which conditions are in force.
designPlan how it worksPropose how the network should keep track of the rules on each account so they can be looked up. Send us your plan and wait for our approval before you start building.
Build the rule lookupBuild the approved plan, so any wallet can show its user which rules are protecting their account, and both sides of a payment can see the conditions that apply.
Recipient controls
An account can refuse payments from unknown senders, and can require payments to arrive instantly with no recall window.
Shops need “paid” to mean final. Today only the sender’s rules are checked, so the receiver has no say.
Inbound allow-list (#47)An account only accepts payments from senders it has approved, and refuses the rest.
Maximum hold time (#76)A receiver can require payments to arrive instantly, with no recall window for the sender, so “paid” means final.
What you agree to when you submit work
By submitting work for a bounty, you accept these terms. They apply to every bounty in the program.
Fixed in USD, paid on merge
Every reward is set in US dollars before work starts. We pay it in $AGRS or stablecoins.
Questions builders ask
Can’t find your answer? Email Contactus@tau.net or ask in our Telegram development channel.
Anyone, anywhere. Before payout we may verify your identity, so make sure you can receive crypto to a wallet in your name.
No. Critical bounties change rules every node must agree on, so if you’re new, start with a smaller one such as Recipient controls to learn the codebase.
Yes. Bounties are open to everyone, so you can work on as many as you like at the same time.
You can still submit. Anyone can open a pull request for any open bounty, and we choose which one to merge based on code quality, correctness and what’s best for Tau. Before you start, check the open pull requests and comment on the GitHub issue to let others know you’re working on it.
Yes. You’re accountable for every line you submit. Work you haven’t tested and checked yourself will be closed.
Pick a bounty. Ship it on GitHub.
Comment on the issue to let others know you’ve started. Questions? Ask in our Telegram development channel.