[wildcard] Make FFI claims proof-carrying: verify boundary contracts against the linked Rust artifact
Open-source bounty · GitHub (bounty labels) · open as of 18 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
- 18 Oct 2026, 12:04 UTC
What the listing says
The idea, in a paragraph Stop treating a hand-written descriptor as evidence that a Rust export is safe to call. Make every Hybrid/Rust export carry a machine-checkable boundary contract generated from the exact Rust artifact that will be linked: concrete C-ABI signature and layout, ownership mode, may-retain/may-callb
Excerpt we recorded when we checked: Etiketten: 💎 Bounty, 💎 Bounty, wildcard
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