callebtc

A Proof of Liabilities Scheme for Ecash Mints

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

RobinLinus

Covenants

Covenant-enabling Bitcoin Features

• BIP119: CHECKTEMPLATEVERIFY (CTV) by Jeremy Rubin
• BIP118: SIGHASH_ANYPREVOUT (APO) (aka SIGHASH_NOINPUT) by Christian Decker and Anthony Towns
• OP_CAT by Andrew Poelstra
• OP_CHECKSIGFROMSTACK (CSFS) + OP_CAT
• OP_TAPLEAF_UPDATE_VERIFY (TLUV) by Anthony Towns
• TXHASH + CHECKSIGFROMSTACKVERIFY (TXHASH + CSFS) by Russel O'Connor
• OP_EVICT by ZmnSCPxj

XSystem252

How To Set Up a Raspberry Pi 4 with Archlinux 64-bit (AArch64) and Full Disk Encryption (+SSH unlock), USB Boot (No SD-Card) and btrfs

Written by: XSystem
First published on: 20 Dec 2020
Last updated on: 20 Dec 2020

[0] Introduction

Overview

keilmillerjr

Creating an AUR Package

Maintainer: Keil Miller Jr

How to create and manage an AUR package.

The following link should be read:

• Creating packages
• AUR submission guidelines

laanwj

#!/usr/bin/env python3
# Distributed under the MIT software license
import binascii, struct, sys, io, argparse
from PIL import Image

IMG_WIDTH = 512 # could be made adaptive...
MIN_HEIGHT = 4 # minimum height of image; twitter won't let us upload anything smaller
BYTES_PER_PIXEL = 4 # RGBA, 8 bit

def div_roundup(x,y):

guilhermednt

# Today the twitter user @ayubio said he had received the private key for a Brazillian bank's HTTPS certificate:
#  - https://twitter.com/ayubio/status/994260981294469120
#  - https://twitter.com/ayubio/status/994262029929246722
#  - https://twitter.com/ayubio/status/994277992351391744
# To prove he actualy had the key, another user asked him to sign a message with such key and so he did:
#  - http://pastebin.xyz/p?q=bXllODA

# The commands bellow will check that signature

# Store the message in a file (tweet.txt) in the same way @ayubio did:

PaulSec

import certstream

keywords = ['paypal', 'paypol']

def extract_domains(domains):
    res = []
    for domain in domains:
        for keyword in keywords:
            if keyword in domain:
                res.append(domain)

mgravell

Objective: compare Task<T> vs ValueTask<T> in a scenario that should
be ideal for ValueTask<T> - non-trivial results, but usually (always)
already completed.

Hypothesis: ValueTask<T> should be more efficient, as it does not (in
the "already completed" case) involve allocation.

Methodology: create a test rig that computes a number using multiple
nested roll-up operations, comparing sync vs async-Task<T> vs async-ValueTask<T>;
use "async"/"await" for the rollups in the async cases. Run all tests using

jean-lourenco

public static void Main()
{
    var paraCadastrar = new []
    {
        new { Chave = "CSVDEFAULT", Descricao = "Descrição detalhada (ou não)" },
        new { Chave = "JSONDEFAULT", Descricao = "Descrição detalhada (ou não)" },
        new { Chave = "YAML", Descricao = "Descrição detalhada (ou não)" },
        new { Chave = "INIT", Descricao = "Descrição detalhada (ou não)" },
        new { Chave = "CONFIG", Descricao = "Descrição detalhada (ou não)" },
        new { Chave = "BSON", Descricao = "Descrição detalhada (ou não)" },

so0k

Kubectl output options

Let's look at some basic kubectl output options.

Our intention is to list nodes (with their AWS InstanceId) and Pods (sorted by node).

We can start with:

kubectl get no