Skip to content

Instantly share code, notes, and snippets.

View m1sterc001guy's full-sized avatar

Justin Moeller m1sterc001guy

View GitHub Profile
@m1sterc001guy
m1sterc001guy / KeybaseVerification
Created January 27, 2021 02:35
Keybase Verification
### Keybase proof
I hereby claim:
* I am m1sterc001guy on github.
* I am jumoell (https://keybase.io/jumoell) on keybase.
* I have a public key whose fingerprint is 9677 181B 6F6C 3BB4 5777 3DAB E59C D948 AB1D 0664
To claim this, I am signing this object:
2023-07-24T18:09:01.246013Z INFO consensus: Starting config gen
2023-07-24T18:09:01.249038Z INFO net::api: Starting api on ws://0.0.0.0:80
2023-07-24T18:10:30.921462Z INFO connection{remote_addr=172.20.0.2:48174 conn_id=0}: jsonrpsee_server::server: Accepting new connection 1/10
2023-07-24T18:10:31.213817Z INFO connection{remote_addr=172.20.0.2:48176 conn_id=1}: jsonrpsee_server::server: Accepting new connection 2/10
2023-07-24T18:10:44.275643Z INFO connection{remote_addr=172.20.0.2:52966 conn_id=2}: jsonrpsee_server::server: Accepting new connection 1/10
2023-07-24T18:10:44.565477Z INFO connection{remote_addr=172.20.0.2:52982 conn_id=3}: jsonrpsee_server::server: Accepting new connection 2/10
2023-07-24T18:10:48.189171Z INFO connection{remote_addr=172.20.0.2:52988 conn_id=4}: jsonrpsee_server::server: Accepting new connection 3/10
2023-07-24T18:10:56.370871Z INFO connection{remote_addr=172.20.0.2:48710 conn_id=5}: jsonrpsee_server::server: Accepting new connection 2/10
2023-07-24T18:10:56.635619Z IN
@m1sterc001guy
m1sterc001guy / resolvr_fedimint_module.md
Last active March 12, 2024 17:26
Resolvr Fedimint Module

Motivation

The goal of the Resolvr project is to enable an open-source dispute resolution system. We have discussed in the past that part of the solution could include a Fedimint module that orchestrated the unlocking of a "bounty". How to do this has remained an open question. In this post, I will propose two possible implementations. Both implementations use FROST/ROAST to produce a signature that allows the bounty to be unlocked.

Requirements and Assumptions

  • "Reviewers" can be assigned to a "bounty". This bounty is paid out in Bitcoin (on-chain, lightning, or ecash).
  • The "Reviewers" are assumed to have a Nostr Public Key (npub) associated with their identity. This proposal does not attempt to solve the problem of public key discovery or trustworthness of nostr npubs. It is assumed that reputation will be