Abstract: In this document, I will outline a proof-of-liabilities (PoL) scheme for ecash systems and Cashu specifically, which is a Chaumian ecash system for Bitcoin. The PoL scheme consists of three parts. First, a publicly auditable list of all issued ecash tokens in the form of mint proofs, and second, a publicly auditable list of all redeemed ecash tokens in the form of burn proofs, which are both regularly published by the mint operator. Third, a mint publicly commits to rotate its keys regularly once each epoch and allows all ecash in circulation to recycle from old epochs to the newest one. If clients remain vigilant and mints agree on a certain set of rules of operation which are publicly verifiable, users of a mint can detect whether a cheating mint has printed unbacked ecash during a past epoch, and, in many cases, provide public proofs of the mint engaging in this adversary behavior. Users achieve this by regularly checking t
Download Bitcoin core and install it whereever you prefer (C:\Bitcoin). It should have daemon, docs and bitcoin-qt with other files. daemon folder contains bitcoind and bitcoin-cli executables.
- We need to run at least two nodes to send/receive transactions. So let us start with first node setup.
- Create 'regtest1' folder at your prefered location (~\AppData\Roaming\Bitcoin).
- Create bitcoin.conf file in this newly created regtest1 folder.
- Add below configurations to this file:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"""Help you find users who unstared your repository | |
""" | |
import os | |
import sys | |
import requests_cache | |
import argparse | |
URL = "https://api.github.com/repos/{}/{}/stargazers?per_page=100&page={}" |