Miniscript is great, but:
- Can’t represent many wallet types inside descriptor (lightning wallet, multisigs re-using keys in different branches)
- Do not yet supports tapscript
- Still not stable, i.e. not durable enough for long storage of wallet descriptor backups
As of today, there is no standard way to write a descriptor covering all forms of UTXOs which may be present in bitcoin transactions. This standards aims to bridge that gap. It also defines a canonical form of a wallet descriptor, which is unique for each wallet and allows to commit to the wallet structure in a non-ambigous way, which may be important for wallet comparison, identification, especially in multi-party protocols.
On the 12th of April, 2022 I was "temporally suspended" by Andrew Poelstra from being a maintainer of rust-bitcoin repository. I was notified about this action by a letter from him without any prior discussion. The cause of the decision was my public expression of the statement that cases of plagiarism must not be tolerated and must be acted upon (thread starting from https://twitter.com/dr_orlovsky/status/1513555717218873355?s=21).
Andrew referenced to the fact that while rust-bitcoin is an anti-CoC community, he still considered my words as those which can't be acceptable for a maintainer of rust-bitcoin, since they may be read as a threat of physical violence. We had a mailing after, where I clarified that there were no threats of physical violence. I was surprised that ethic compatibility was a part of requirements for being rust-bitcoin maintainer, which was not what I expected from "anti-CoC" policy of the repo. Andrew agreed that this "anti-CoC" policy and requirements for maintainer conduct are in co
# This means derivation standard used. Here we use m/33/chain/org/unit/account/scope/index | |
use lnpbp derivation | |
# This defines organization units in derivation (see "unit" in the path above). | |
let board = unit 1 | |
# This defines account index used by all participants under the same org unit | |
# (see "account" in the path above). | |
let current = account 2 |
diff --git a/bitcoin/chainparams.c b/bitcoin/chainparams.c | |
index 5a79e7e8e..7e0501271 100644 | |
--- a/bitcoin/chainparams.c | |
+++ b/bitcoin/chainparams.c | |
@@ -80,9 +80,14 @@ const struct chainparams networks[] = { | |
.bip32_privkey_version = BIP32_VER_TEST_PRIVATE}, | |
.is_elements = false}, | |
{.network_name = "signet", | |
- .bip173_name = "sb", | |
+ .bip173_name = "tb", |
/// | |
/// The following charts represent possible relations between script types: | |
/// | |
/// ```text | |
/// [txout.pubkeyScript] | |
/// PubkeyScript --?--(P2PK, custom scripts)--> LockScript <--+-------+---+---------+ | |
/// | | | | | |
/// [txin.sigScript] | | | | | |
/// SigScript --+--?!----------(P2PKH: #=PubkeyHash)----------+ | | | | |
/// | | | | |
Transaction: [txid][@version]<inputs|outputs>[@timelock]
Inputs (same for outputs): input1,input2
(enumerated all inputs) or input1,input2,...,inputN,...
(some inputs are omitted)
Inputs order (same for outputs): ,
for strict sequential order, ;
for non-strict (arbitrary) order
Single input: #no(txid:vout-[nSeqence]-[[keys/signatures]]-[[unlocking-script]])
- Если у вас еще не установлен keybase, закачайте его и настройте свои identitites (см. https://keybase.io/)
- Вступите в группу freeai либо через GUI, либо с помощью команды
keybase team request-access freeai
- Выполните следующие команды в командной строке
git clone keybase://team/freeai/freeai-manifesto
cd freeai-manifesto
keybase pgp sign -i the_freeai_manifesto.txt -o signatures/`keybase status | grep 'Username:' | awk '{print $2}'`
I hereby claim:
- I am dr-orlovsky on github.
- I am dr_orlovsky (https://keybase.io/dr_orlovsky) on keybase.
- I have a public key ASDFNYhFyWfxGYRj-0Ilt_M-VmW7XCl3eWqHrFzEyozgwAo
To claim this, I am signing this object: