| dt { | |
| font-weight: bold; | |
| float: left; | |
| min-width: 200px; | |
| text-align: right; | |
| } | |
| dt:after { | |
| content: ':'; | |
| margin-right: 10px; |
| package main [33/492] | |
| import ( | |
| "fmt" | |
| "strings" | |
| "golang.org/x/crypto/openpgp" | |
| ) | |
| func main() { |
| 31/12/2022 | |
| 1. homicídios por ano | |
| 2. mulheres mortas pelos companheiros | |
| 3. fim do foro privilegiado | |
| 4. desemprego | |
| 5. pib | |
| 6. inflação | |
| 7. taxa de desmatamento | |
| 8. estupros |
| export const providers = { | |
| alias: { | |
| desc: 'Alias for a existing remote', | |
| options: [ | |
| { | |
| name: 'remote', | |
| desc: | |
| 'Remote or path to alias.\nCan be "myremote:path/to/dir", "myremote:bucket", "myremote:" or "/local/path".', | |
| required: true | |
| } |
| venv | |
| *.swo | |
| *.swp | |
| __pycache__ |
| import hashlib | |
| import json | |
| from flask import Flask, jsonify, request | |
| app = Flask(__name__) | |
| BASE_URL = 'https://myservice.com' | |
| @app.route('/lnurl-one') | |
| def lnurl_one(): | |
| return jsonify({ |
Musically, some prefer Tristan and Isolde, but in the matter of dramatic power and richness of meaning, Wotan’s final aria in The Valkyrie, “Leb Wohl” (Farewell), is doubtless the pinnacle of Richard Wagner’s work. What does that have to do with Christmas? Hold on a while, and let me recall the scene.
Pressured by his wife Fricka, who urges him to fulfill his duties as maintainer of the cosmic order, Wotan, the Germanic counterpart of Zeus, unwillingly promises to punish by death his grandson Siegmund—guilty of adultery and incest with his sister Sieglinde. To achieve this goal, Wotan sends his dearest daughter, Brünnhilde, to the place where Sieglinde’s husband will fight a duel with Siegmund, to ensure that Siegmund, deprived of all divine assistance, is killed in the duel. At the decisive moment, Brünnhilde allows herself to be overcome with compassion for Siegmund, and disobeying the order she received, attempts to protect him. Wotan has to intervene personally, breaking Si
| +------+ +-------+ +---------+ | |
| +-------> | | +-------------------------> | | - - - - - - - - - - - - - - -> |potential| | |
| | BMM | | BMM | | BMM | | |
| |block | | block | | block | | |
| | | | | - - - - - -> | | +---- - - - | |
| +------+ +-------+ | +---------+ | | |
| tx A | |
| | | | |
| v | |
| HTLCs below the dust limit are not possible, because they're uneconomical. | |
| So currently whenever a payment below the dust limit is to be made Lightning peers adjust their commitment transactions to pay that amount as fees in case the channel is closed. That's a form of reserving that amount and incentivizing peers to resolve the payment, either successfully (in case it goes to the receiving node's balance) or not (it then goes back to the sender's balance). | |
| SOLUTION | |
| I didn't think too much about if it is possible to do what I think can be done in the current implementation on Lightning channels, but in the context of Eltoo it seems possible. | |
| Eltoo channels have UPDATE transactions that can be published to the blockchain and SETTLEMENT transactions that spend them (after a relative time) to each peer. The barebones script for UPDATE transactions is something like (copied from the paper, because I don't understand these things): |