clarkmoody

npub15n94rarp3n7dz6edx9cugeshn0kcuxtugwu9nzprkpx7yekw7ygqplqru4

luke-jr

--- a/src/script/interpreter.cpp
+++ b/src/script/interpreter.cpp
@@ -504,6 +504,14 @@ bool EvalScript(std::vector<std::vector<unsigned char> >& stack, const CScript&
                     return set_error(serror, SCRIPT_ERR_MINIMALDATA);
                 }
                 stack.push_back(vchPushValue);
+                if ((flags & SCRIPT_VERIFY_DISCOURAGE_UPGRADABLE_NOPS) && opcode == OP_FALSE) {
+                    auto pc_tmp = pc;
+                    opcodetype next_opcode;
+                    valtype dummy_data;

travisbrown

metasikander

This is a very basic guide, just to understand what's needed to set it up.
If you have any questions you can find me at https://nostr.com/8355095016fddbe31fcf1453b26f613553e9758cf2263e190eac8fd96a3d3de9

Prerequisite

• a webserver with a domain under your control
• nostr account with private and public key setup on https://nostr.com, preferably set up with nos2x: https://github.com/fiatjaf/nos2x

Setup static file on server

Create a file that resolves to <domain>/.well-known/nostr.json, and fill it out like this (enter the name you want to use, and input your own public key, make sure its the HEX-key):

{

manosv

TorThisTx() {
    # Rename "TorThisTx() to whatever you want the command to be
    # Broadcast raw hex transaction over blockstreams TOR API with curl
    curl --socks5-hostname localhost:9050 -d $1 -X POST http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion/api/tx
}

21isenough

For context: https://twitter.com/21isenough/status/1255182788686462983?s=20

TorThisTx() {
    # Rename "TorThisTx() to whatever you want the command to be
    # Broadcast raw hex transaction over blockstreams TOR API with curl
    curl --socks5-hostname localhost:9050 -d $1 -X POST http://explorerzydxu5ecjrkwceayqybizmpjjznk5izmitf2modhcusuqlid.onion/api/tx
}

wiz

-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFw8N4EBEADDv38WWb4+IDku5NxpDGyhX9Of0/KfSCATdNVnjsa8yriNBB5B
V3U3Nu+zZQF/Yd54h2GfO+JgeMP2XIqJ26+OaWvhVCpJ6oZbHPCl1FutebSFOc+x
I2d3Ki1BYoiLtWCkdfyKQUH3+7JTV2uCQZQZ+of6l35i71sj5T59HolpmUp8ZYx/
ztNQOxJH02GEvyoK8yUDu0gPGECJ/UtCdysy+V36h/Np5XNIKdd62hh/YAeopvCg
Mf+0dr6Es72sBXWMTzyOLE/L8KJUaIjupq4TkD1sbtLHW+7ocuJ+JUZ/12ouNrNf
lVuEA8z9udkm5p0GMv+Gu24YBLCNESjIHPd2uRrNnAz5qUG8lWK1rXDqFOMimhKS
rtdoPEmIxZxLj2TN64cFCk2e7HNJRjFOTxoDgPyrdW/CRBiCWcTQ8e92ukrLVep0
6m+/U2p+HIDwZyy63t6U2m01GoF97qEaRpXOM6vUSlund3i5M6DdAAyd/AaiP3Nt

Belial-public

Blockchain Rule Update Process

We recently rolled out two changes to the Bitcoin block acceptance rules (BIP16 and BIP30); this document records the lessons learned and makes recommendations for handling future blockchain rule changes.

Note: there are "soft" rule changes and "hard" rule changes. "Soft" changes tighten up the rules-- old software will accept all the blocks and transactions created by new software, but the opposite may not be true. "Soft" changes do not require the entire network of miners and merchants and users to upgrade or be left behind.

"Hard" changes modify the rules in a way that old, un-upgraded software consider illegal. At this point it is much, much more difficult (some might say impossible) to roll out "hard" changes, because they require every miner and merchant and user to upgrade.

Lessons Learned

jeffrade

#!/bin/bash

# Just a simple wrapper to start bitcoind.
#
# If using systemd, simply create a file (e.g. /etc/systemd/system/bitcoind.service) 
# from example file below and add this script in ExecStart.
# https://raw.githubusercontent.com-/bitcoin/bitcoin/76deb30550b2492f9c8d9f0302da32025166e0c5/contrib/init/bitcoind.service
#
# Then run following to always start:
# systemctl enable bitcoind

alexbosworth

LND backup script for channel.backup using inotify

Install inotify

sudo apt install inotify-tools

Create script to watch for changes and copy on change