Bounties
As of January 13, we’ve wrapped up all three Reactive bounty programs and what a run it’s been! Across these challenges, builders pushed Reactive Contracts in different directions, explored new automation patterns, and shipped a lot of genuinely impressive code. Today, we’re excited to share the two
Bounties
Our third bounty has drawn to a close so it's now time to announce the winners of our second bounty! The results of judging for the third bounty will be announced in one week, on January 12. Second bounty winners There was a mismatch between the deadline time
Bounties
The subscription model is standard in Web2, but reproducing it on-chain has been difficult. Traditional recurring payments depend on centralized processors and off-chain scheduling, none of which map cleanly to blockchain execution. NFT SUB addresses this by expressing subscriptions as verifiable on-chain events. Implemented as a TypeScript SDK, NFT SUB
Bounties
Our bounty program keeps rolling, on Sunday we closed submissions for the first challenge, a Cross-Chain Oracle. We received 23 submissions, and we’ll be reviewing them over the coming week. Huge thanks to everyone who submitted a build, it’s great to see so many engaged hackers and a
Developers
Keeping Reactive Contracts (RCs) funded is a constant maintenance task. If a contract runs out of tokens, it stops executing. Thus, missed calls, stalled logic, and broken integrations follow. For developers working with RCs that fire on frequent events, this becomes a persistent operational load. Most builders end up watching
Developers
Reactive Network is kicking off Reactive Bounties 2.0