⚖️ Resolvr ⚖️ - Week 9: Escrow Progress, Hard Nostr Lessons, and the Final Push
A decentralized bounty marketplace for the #FOSS community.
DLC 🔮 Escrow Desktop App
We’ve been quiet the last few weeks, but not idle. The first component of the MVP, a Nostr🦩 bounty-board with instant payouts and dispute resolution, is functionally complete. Users can post bounties, apply to bounties, and be paid p2p through zaps⚡ on the bitcoin (₿) lightning network. Try it out by signing up for the Alpha and logging in to the vercel site.
The last remaining piece of the puzzle for the hackathon MVP is escrow. We’re creating a bitcoin (₿) native, non-custodial escrow system that uses Discreet Log Contracts🔮. To contruct these smart-contracts, a series of communications between bounty-maker and bounty-taker is required, in addition to communication with the bitcoin network to broadcast the transactions. This complexity requires a manager app that syncs with bitcoin core. So we’re working on desktop app to complement the web client, which will manage and construct the Discreet Log Contracts🔮 necessary for escrowing bounty funds. For the hackathon MVP, this desktop app will be very experimental and run on a test-net to avoid loss of real sats.
Post-hackathon, the team plans to offer the web client as “Resolvr Lite,” desgined for low to medium value bounties that do not necessitate escrow, but that will still benefit from instant payouts and non-binding crowdsourced review of submissions. The desktop app will be “Resolvr Premium” and serve as both a Nostr🦩 client to post, discover, and apply for bounties (just like the web client), as well as the DLC manager and on-chain bitcoin (₿) wallet.
Nostr Wake-Up Call
We also received a wake-up call courtesy of JB55, the developer behind the popular Nostr🦩client Damus and steward of the largest nostr relay. On Novemeber 20, he deleted all the data on the relay.
Unfortunately, Resolvr noticed. For simplicity and consistency, our web client had been writing to a single relay – Damus. When Jb55 nuked his relay, Resolvr lost the bounty data it had created thus far, including live bounty posts (one from Nostr🦩 creator fiatjaf himself!)
But we’re grateful for this painful lesson, which fortunately occurred pre-release and with time to shift our Nostr🦩 design. Resolvr will be writing to multiple relays by default moving forward, and is exploring running its own backup relay. Nostr🦩 is architected to be redundant and censorship-resistant through the use of many relays. Apps must take advantage of that key attribute.
Next Up: DEMO AND PITCH
This will be the last progress update until Resolvr’s pitch and demo. Until then, join us on discord, stress test the web client, and contribute on GitHub!
And get your bounties ready!
Progress
-
Escrow (₿):
- Discreet Log Contracts🔮 manager running in testnet with CLI.
-
Nostr🦩 Bounty Board:
- exploring relay implementations and costs
Problems
-
Nostr🦩 Bounty Board:
- Bounty data lost during Damus relay purge
-
Escrow: Need to bridge decision of review panels to DLC oracle attestation.
Roadmap Revisions:
-
Moved design research with alpha testers to post-hackathon roadmap.
-
Added premium desktop client to post-hackathon roadmap.
Project Roadmap:
Hackathon
-
Build bespoke nostr🦩 bounty board that allows posting, solving, and reviewing bounties.
-
Implement DLCs🔮 for bitcoin (₿) escrow
-
Develop review system
-
Crowdsourced Human Developers
-
AI🤖
-
Post-Hackathon
-
Premium desktop client powered by nostr🦩 with mainnet DLC🔮
-
Finalize FROST🥶 integration with FediMint🔅
-
Deploy FediMint🔅 DLC🔮oracle
-
Conduct design research with alpha testers in all roles.
Links 🔗
-
alpha signup/newsletter: https://www.resolvr.io
-
Discord: https://discord.gg/DsqRw8My4m
-
Weekly Zap.Stream All-Hands Call (12/4/23 @ 1:00pm ET)
-
GitHub repo: https://github.com/Resolvr-io
-
“Advancing Dispute Resolution Beyond the State through Bitcoin”, Research paper explaining dispute resolution design theory underpinning Resolvr