I am not responsible, directly or indirectly for the loss of funds using these commands. Use at your own risk.
alias lrecv="lncli listchannels | jq '[ .channels | .[] | select(.total_satoshis_received|tonumber>0) ]'"
| # MOVED: | |
| # To enable better collboration, I've moved the shell.nix to https://github.com/0xB10C/nix-bitcoin-core. | |
| # Older revisions remain avaiable here. | |
| # https://gist.github.com/0xB10C/1fd0d4a68bf96914775b1515340926f8/revisions | |
| # | |
| # | |
| # | |
| # | |
| # | |
| # |
| #!/bin/bash | |
| POST_INIT_SYNC_DELAY=60 | |
| POLL_DELAY=60 | |
| STALL_THRESHOLD=5 | |
| if [ -z `pidof btcd` ]; then | |
| echo "Starting btcd" | |
| nohup btcd & | |
| sleep $POST_INIT_SYNC_DELAY |
This is based on Poelstra's ideas as summarised in https://download.wpsoftware.net/bitcoin/wizardry/mw-slides/2017-05-milan-meetup/slides.pdf ; also see the earlier outline in https://lists.launchpad.net/mimblewimble/msg00086.html.
Note that the details here are just my thoughts, so if you come to this randomly, don't take it as some kind of well established protocol!
We'll use || for concatenation and capitals for elliptic curve points and lower case letters for scalars.
| #!/bin/bash | |
| # compiled from https://docs.docker.com/engine/installation/linux/debian/#/debian-jessie-80-64-bit | |
| sudo apt-get update | |
| sudo apt-get dist-upgrade -y | |
| sudo apt-get install apt-transport-https ca-certificates -y | |
| sudo sh -c "echo deb https://apt.dockerproject.org/repo debian-jessie main > /etc/apt/sources.list.d/docker.list" | |
| sudo apt-key adv --keyserver hkp://p80.pool.sks-keyservers.net:80 --recv-keys 58118E89F3A912897C070ADBF76221572C52609D |
| import logging | |
| import quickfix as fix | |
| def _str(msg): | |
| ''' Convert a FIX message to a readable string. ''' | |
| return msg.toString().replace('\x01', '@') |
When working with Git, there are two prevailing workflows are Git workflow and feature branches. IMHO, being more of a subscriber to continuous integration, I feel that the feature branch workflow is better suited, and the focus of this article.
If you are new to Git and Git-workflows, I suggest reading the atlassian.com Git Workflow article in addition to this as there is more detail there than presented here.
I admit, using Bash in the command line with the standard configuration leaves a bit to be desired when it comes to awareness of state. A tool that I suggest using follows these instructions on setting up GIT Bash autocompletion. This tool will assist you to better visualize the state of a branc