darosior

End of period 1, reducing the diff by 1.008431712962963.

End of period 2, reducing the diff by 1.9997885879775676.

End of period 3, reducing the diff by 2.4953826200260374.

End of period 4, reducing the diff by 2.6938205846144805.

End of period 5, reducing the diff by 2.767310059006725.

darosior

import json
import matplotlib.pyplot as plt
import numpy as np

from datetime import datetime

STARTING_BALANCE = 0

with open("bkpr_report.json", "r") as report:
    events = json.load(report)["income_events"]

darosior

(Contains input from many people, not my own ideas)

Notes

• Forbid multi, have a new multi_a itself forbidden in other contexts
• We now need to care about the maximum stack size (1000). With Taproot it's now also checked before executing the Script.
• We could have a new d: wrapper that is u because the MINIMALIF rule is consensus
• It doesn't look like there is interesting combinations of the new CHECKSIGADD opcode with existing fragment. Maybe we could have used it for thresh to save an OP_ADD if the sub was a CHECKSIG, but the arguments aren't in the right order for this.
• No need to check for the Script size anymore
• I don't think we need to take the sigop budget into account, as we can't create a Script that would duplicate the signatures.
• When calculating sizes, keep in mind the signature length is now 64

darosior

This is a list of all the possible use cases for the `rpc_command` hook, which I keep so that I don't feel so bad to have
contributed something which had to be fixed 3 times by Rusty and once by Christian :
- "one use case for the rpc_command hook is to always provide a close_to address for a channel" -- niftiney
- "https://github.com/fiatjaf/lightningd-gjson-rpc/tree/72f8541eea17e209eb21f3d2d82286a3242f7ba5/cmd/routetracker" -- fiatjaf
- " replace `getroute`." -- zmn
- "Or make it more powerful by letting it hook-chain as well." -- zmn

darosior

The doc is now part of C-lightning at https://lightning.readthedocs.io/PLUGINS.html#bitcoin-backend

darosior

A is funder B is fundee

A initiates the process but B doesn't want its outputs to be snooped easily. One solution could be to require A to provide signed and broadcastable transactions in order to know about B's utxos. This can be done with SIGHASH_SINGLE|SIGHASH_ANYONECANPAY which an input and the corresponding output, so A signs its funding to the channel and can be sure that the created output is the P2WSH multisig used to fund the channel.

One downside of this is that it doesn't allow for change on A's side. This can be solved by using a (segwit) transactions chain. A creates a first tx, let's call it txA1 containing an arbitrary number of its inputs and of change outputs:

darosior

Which one of your channels are you always failing to route through ?

for scid in $(lc listpeers |jq -r '.peers | map(.channels[].short_channel_id)[]');do echo "$scid failed $(lc listforwards |jq -r '.forwards | map(select(.status | contains("failed")).out_channel)' |grep $scid |wc -l) times";done

Which ones are often succeeding ?

darosior

.top-header {background-color: #fff;}
.top-header .timer-row__progress-bar {background:#ef8022;}
.top-header .timer-row {background: #ffc313;}
.close-icon {color:#000;}
.payment-tabs__slider {background: #ef8022;     }
.separatorGem {background: #ef8022;}
.action-button {color: #fff; background-color: #ef8022;border-color: #ef8022;}
.action-button:hover {background-color: #ffc313;}
.action-button:focus, .action-button.focus {color: #fff;background-color: #ef8022;
    border-color: #ef8022;}

darosior

#!/usr/bin/env bash

if [ "$#" -ne "1" ]; then
	echo "usage :"
	echo "	$0 <amd64|i386>"
elif ! [ "$1" = "amd64" ] && ! [ "$1" = "i386" ]; then
	echo "Bad architecture argument. First and only argument must be amd64 or i386."
else
	mkdir "tmplibdb" && cd "tmplibdb"
	if [ "$1" = "amd64" ]; then

darosior

LIGHTNING-CONNECT(7) Manual Page

lightning-connect - Command for connecting to another lightning node.

SYNOPSIS

connect id [host port]

DESCRIPTION