Replace Schema-based derivation of encoder / decoder with ZIO Schema Deriver-based derivation
Open-source bounty · GitHub (bounty labels) · open as of 17 Oct 2026
- Amount as listed
- —
- Platform
- GitHub (bounty labels)
- Kind of work
- Open-source bounty · Engineering
- Open to
- not stated by the platform
- Deadline
- not stated by the platform
- Status
- Open
- Checked
- 17 Oct 2026, 18:22 UTC
What the listing says
Currently, ZIO JDBC directly converts from Schema to encoders / decoders by generating the appropriate type class instances (JdbcEncoder, JdbcDecoder). This is not ideal, because it means a user does not have any ability to define a custom encoder / decoder for any part of their ADT. In order to solve this problem, we
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, 💎 Bounty
Open on GitHub (bounty labels) ↗
The work is offered, scoped and paid by GitHub (bounty labels) — not by GOAT Market. We record what they publish and link to it. Claiming, delivering and getting paid all happen on their site, under their terms.
More open on GitHub (bounty labels)
- [Feature] Implement Basic Anti-Cheat Protection $10,000
- [ Bounty $9k ] [ SDK ] Fix encoding.ts decodeParameter doesn't handle dynamic types — back... $9,000
- [ Bounty $9k ] [ Solidity ] Add gas sponsorship relay for agent transactions — security cr... $9,000
- [ Bounty $9k ] [ API ] Fix agents.py doesn't validate endpoint URL format — testnet findin... $9,000
- [ Bounty $9k ] [ SDK ] Fix rpc.ts doesn't handle JSON-RPC batch response ordering — backwa... $9,000