Skip to content

Instantly share code, notes, and snippets.

Avatar

Martin Habovštiak Kixunil

View GitHub Profile
@Kixunil
Kixunil / mkchlog.md
Last active Jan 27, 2022
mkchlog - a simple but flexible tool for generating changelogs, proposal
View mkchlog.md

Mkchlog

Abstract

This is a proposal to develop a changelog generator tool more suitable for user-facing changelogs and based on experiences of existing projects. The rationale is provided to explain why this is better then existing alternatives. The foundational axioms are:

  • Git history is not suitable as changelog because some commits are not important.
@Kixunil
Kixunil / quick_dive_rust_code.md
Last active Dec 29, 2021
WIP quick dive into a source code written in Rust
View quick_dive_rust_code.md

Quick dive into a source code written in Rust

Are you a Rust newbie who found some code written in Rust and wants to dive right into the code? You're at the right place! This quick guide is supposed to help you in exactly this situation. It's not meant to be a full Rust tutorial - there are beter sources of those!

Quick intro

Two basic things you should know before you start:

@Kixunil
Kixunil / efficient_reusable_taproot_addresses.md
Last active Jan 7, 2022
Efficient reusable Taproot addresses
View efficient_reusable_taproot_addresses.md

Reusable taproot addresses

Abstract

This document proposes a new scheme to avoid address reuse while retaining some of the convenience of address reuse, keeping recoverability purely from Bitcoin time chain and avoiding visible fingerprint. The scheme has negligible average overhead.

Motivation

@Kixunil
Kixunil / taproot_review.md
Created Sep 2, 2020
My review of the Taproot pull request by Pieter Wuille
View taproot_review.md

My review of the Taproot PR by Pieter Wuille

About

I have reviewed the Taproot PR and decided to write some notes. This is a combination of notes that may be useful for other (less experienced) reviewers to understand the code and possibly helpful for a bit wider technical audience to understand how Taproot works in better details. It's definitely not intended for general public.

Summary/conclusion

@Kixunil
Kixunil / beta-gpg-key.asc
Created Aug 11, 2020
Declaration of ownership of GPG key
View beta-gpg-key.asc
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I hereby declare that I'm the owner of GPG key with fingerprint
3D9E81D3CA76CDCBE768C4B4DC6B4F8E60B8CF4C
Which I use to sign beta-quality software.
This software should be mostly usable, but was not WIDELY tested.
It may contain bugs or even security vulnerabilities, as any other software.
View qubes_track_focus.sh
xprop -spy -root -notype _NET_ACTIVE_WINDOW | sed -ue 's/^.*# //' -e 's/,.*$//' | while read id; do focused_vm="`xprop -notype -id $id _QUBES_VMNAME 2>/dev/null | cut -d '"' -f 2`"; test "$focused_vm" = "_QUBES_VMNAME: not found." && focused_vm=dom0; test -n "$focused_vm" && echo "`date +%s` $focused_vm"; done
View declaration_of_maintenance.md

If you're reading this, it may mean you think my project is dead/unmaintained. Please read this before you dismiss it.

The short version is: please make sure to ask about a change you'd like before proceeding. It's likely I will reply an cooperate. A lack of updates often means that the code does what's intended.

Long verssion

So you see that there are no commits to my project for some time and maybe think it's not maintained. It's not that easy. Particularly in case of Rust crates. The primary reason for my project lacking changes is that I don't need the changes

@Kixunil
Kixunil / keysign_party.md
Last active May 26, 2019
A protocol for efficient key signing party
View keysign_party.md

Effiecient key signing party protocol

Disclaimer: this is a proof of concept, the protocol hasn't been reviewed yet! There might be undiscovered vulnerabilities!

However I tried hard to find any vulnerabilities and I don't know of any. I'm fairly confident the protocol is secure.

About

@Kixunil
Kixunil / ucsfa.md
Last active Jun 19, 2017
User coordination of soft fork activation
View ucsfa.md

User coordination of soft fork activation

Abstract

This document proposes a novel way to improve coordination of users who wish to activate a new soft fork in Bitcoin. The main idea is to use smart contracts to incentivize users to actually enforce the soft fork with lower risk of support being too low. At the same time the contract is in effect only if significant part of economy agrees to it. The contract also signals the intent to miners and other users in a way that would be otherwise expensive for sybil attackers. This proposal also suggests an interesting way to pay developers for the development of the soft fork code.

Acknowledgement

@Kixunil
Kixunil / bitcoin_multisig_payment_proto.mediawiki
Last active Sep 1, 2016
Bitcoin Multisig Payment Protocol
View bitcoin_multisig_payment_proto.mediawiki

  BIP: ?
  Title: Multisig Payment Protocol
  Author: Martin Habovštiak <martin.habovstiak@gmail.com>
  Status: Draft
  Type: ?
  Created: 2014-01-30

Abstract