No need for homebrew or anything like that. Works with https://www.git-tower.com and the command line.
gpg --list-secret-keys and look for sec, use the key ID for the next stepgit to use GPG -- replace the key with the one from gpg --list-secret-keys
| <?xml version="1.0" encoding="UTF-8"?> | |
| <opml version="1.1"> | |
| <head> | |
| <title> | |
| Feeder | |
| </title> | |
| </head> | |
| <body> | |
| <outline title="Stacker+News" text="Stacker+News" type="rss" xmlUrl="https://stacker.news/rss"/> | |
| <outline title="𝐁𝐂𝟏𝟗𝟖𝟒" text="𝐁𝐂𝟏𝟗𝟖𝟒" type="rss" xmlUrl="https://bc1984.com/rss/"/> |
Receive private payments from anyone on a single static address without requiring any interaction or extra on-chain overhead.
Update: This now has a BIP and WIP implementation
The recipient generates a so-called silent payment address and makes it publicly known. The sender then takes a public key from one of their chosen inputs for the payment, and uses it to derive a shared secret that is then used to tweak the silent payment address. The recipient detects the payment by scanning every transaction in the blockchain.
Due to unexpected failures of github's LaTeX parsing (which were not evident until I published this, but have persisted afterwards), and since the mathematical parts are important in this, I have migrated this proposal to a blog post with identical content, but correctly formatted equations.
Please continue to put any comments here.
| #!/bin/bash | |
| # Sends a health check ping to the Amboss API. | |
| # Docs: https://docs.amboss.space/api/monitoring/health-checks | |
| URL="https://api.amboss.space/graphql" | |
| NOW=$(date -u +%Y-%m-%dT%H:%M:%S%z) | |
| echo "Timestamp: ${NOW}" | |
| SIGNATURE=$(lightning-cli signmessage "$NOW" | jq -r .zbase) | |
| echo "Signature: ${SIGNATURE}" | |
| JSON="{\"query\": \"mutation HealthCheck(\$signature: String!, \$timestamp: String!) { healthCheck(signature: \$signature, timestamp: \$timestamp) }\", \"variables\": {\"signature\": \"$SIGNATURE\", \"timestamp\": \"$NOW\"}}" | |
| echo "Sending ping..." |
root@gpod:~ cat /etc/docker/daemon.json
{
"experimental": true
}
docker run --privileged --rm tonistiigi/binfmt --install all
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