On 12 November the Janzeer repositories started paying for work. Five days later, outside contributors had shipped a Windows package manifest, a Homebrew formula, typed API wrappers in three SDKs and three new examples, and every payment for it is public on the chain. This is what happened, including the parts that did not go well.
How the bounties work
A bounty is an ordinary GitHub issue with an amount in its title, for example [50 JNZ] Homebrew formula for macOS. The rules fit on one page, BOUNTIES.md, the same in the CLI and the five SDK repositories:
- 20 JNZ for an example or a guide, 50 JNZ for a small API addition, a package or a translation, 100 JNZ for a larger API addition. Bug reports are paid 20 to 100 JNZ depending on what they find.
- Comment on the issue to claim it; a claim holds for seven days. Then open a pull request.
- Payment is made after the merge , in JNZ, to a Janzeer address the contributor posts in the pull request. Nothing has to be agreed beforehand and there is nothing to sign up for.
- The programme pays at most 1,000 JNZ a month.
Every payment comes from the project's ecosystem account and the transaction is posted in the pull request, so anyone can check it in the explorer.
What got built
- Scoop manifest:
jzon Windows (janzeer-cli): 50 JNZ - Homebrew formula:
jzon macOS, tested on a real Mac (janzeer-cli): 50 JNZ - Example: follow new blocks over the WebSocket (janzeer-sdk-ts): 20 JNZ
- Typed RPC wrappers for tokens, transactions by address, raw transactions, the method list and the genesis document (janzeer-sdk-go): 100 JNZ
-
getGenesis()and tests for every typed node method (janzeer-sdk-dart): 100 JNZ -
getGenesis()and its coroutine variant (janzeer-sdk-kotlin): 50 JNZ - Example: follow new blocks over the WebSocket (janzeer-sdk-dart): 20 JNZ
- Example: follow new blocks over the WebSocket (janzeer-sdk-kotlin): 20 JNZ
That is 410 JNZ paid in eight transactions to two contributors, plus 20 JNZ waiting for an asyncio guide in the Python SDK, merged on 12 November, until its author posts an address. The work went out as six releases on 15 and 16 November: Dart 0.1.10 and 0.1.11, Go v0.1.6, Kotlin 0.1.9 and 0.1.10, and TypeScript 0.1.9.
How a pull request gets merged
Every bounty pull request goes through the same steps:
- Read the diff against the code , not against the description. The description says what the author meant; the diff says what will ship.
-
Run the project's own checks on our side:
gofmt,go vetandgo test -racefor Go;dart analyze --fatal-infosanddart testfor Dart;./gradlew buildwith the public-API check for Kotlin; tests and lint for TypeScript. - Call the new code against the live mainnet node. Unit tests run against fake answers that the author wrote; the node is the only judge of what the answers really look like.
- Merge with the author's commits kept , release, and post the payment.
Step 3 is the one that mattered most this week.
What the reviews found
Token amounts are not coin amounts. The first version of the Go wrappers typed a token's cap, supply and balances as Amount, the SDK's type for JNZ. On mainnet, janzeer_listTokens answers "decimals": 2, "cap": 20000000: whole numbers in the token's own units. Amount would have scaled them by 10⁸. They are now *big.Int, as the TypeScript SDK uses bigint.
The genesis call returns a document, not a block. Three of the new getGenesis methods first decoded the answer as a genesis block. The live node returns the genesis document: network id, signer key, anchors and their balances. All three were changed to return the document as JSON.
Two Go names collided with existing ones. A new Token model clashed with the token transaction builder, and a new Methods() method was hidden by a field of the same name on the client. Neither compiled. Both were caught by running the tests rather than reading the pull request text, and both were fixed by the contributor in under an hour.
The worst bug was ours. While checking the genesis question, we called the published TypeScript SDK's getGenesis() against mainnet. It threw on every call: since the method was added in October, it had expected a block. An outside pull request led us straight to a bug in our own code. TypeScript 0.1.9 fixes it, and all five SDKs now return the same thing.
Two of our issues were wrong. The Dart issue listed eight missing methods when seven already existed, and the Kotlin issue told contributors to return the block model. The contributor who took the Dart issue noticed, added the one real method plus tests for the other seven, and said so. Both bounties were paid in full: when an issue is wrong, that is the project's mistake, not the contributor's.
What was not merged
Six pull requests were closed without a merge, each with a comment saying why:
- two that added only a
SOLUTION.mdfile describing a change instead of making it; - two that deleted existing public API, including most of a models file and the SDK's own
sendmethods, which would not have built; - one that rewrote a manifest that was already merged and paid, and removed changelog entries;
- one that rewrote a README with wrong descriptions and asked for payment in another currency.
Three more were closed on 16 November because another pull request for the same issue was merged first: the contributor who had commented on the issue got there before them.
Most of the six came from one account that answers bounty issues with the same template; the same account also had a pull request merged and paid once it was fixed. The rules handle them without arguing: the first pull request merged for an issue is the one that is paid, payment is in JNZ only, and nothing is agreed in comments. Every closing comment points at the exact problem, so a real contributor can fix it and come back.
What comes next
New bounty issues go up this week, from packages (.deb, Nix) to examples each SDK still lacks and Arabic translations of the SDK guides. They are all listed with the bounty label: open bounties across the Janzeer repositories. If you write Go, Dart, Kotlin, Python or TypeScript, one of them takes an evening.
The amounts, blocks and releases here are from the live chain and the public repositories, and the text is mine. JNZ is the network's unit, it is not listed anywhere, and nothing here is financial advice.
Top comments (0)