- Install Git for Windows
- Install Node
- Install Python 2.7.3
- Install Microsoft Visual Studio 2015 Community
- Open the command prompt as Administrator, run the following commands, then close the command prompt (a new prompt is required before the new environment variables will be available)
- npm install -g npm
- (Upgrades to npm v3, which no longer nests dependencies indefinitely. No more "maximum path length exceeded" errors due to the 260 character path limit in Windows, or needing to delete node_modules with rimraf.)
- setx PYTHON C:\Python27\python.exe /m
- (May need to change path to your custom install directory.)
- npm install -g npm
- Open a new command prompt and run the following commands. If these install without errors, you have bypasse
// You must have node and npm downloaded on your computer | |
// Download bitcoinjs library | |
npm install bitcoinjs-lib | |
// Require bitcoinjs-lib | |
var bitcoin = require("bitcoinjs-lib"); | |
// Make variable for keyPair | |
var keyPair = bitcoin.ECPair.makeRandom(); |
GitHub Pages "Normal" Setup for User & Organization Pages
Let’s say your GitHub username is “alice”. If you create a GitHub repository named alice.github.com, commit a file named index.html into the master branch, and push it to GitHub, then this file will be automatically published to http://alice.github.com/... The same works for organizations.
Read more here: http://pages.github.com/
However... the downside of this is that anyone that forks this repo won't get it as a GitHub Pages repo when they are working on it... because they have a different GitHub "username" (or "organisation name").
So the trick is to not use a master
branch as the documentation tells you... rather, use a gh-pages
branch, as you would for your other "Project Pages".
Setup One: Buy a Mac if you don't have one.
Setup Two: Install Homebrew
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
Setup Three:
{ | |
"initial_timestamp": "2018-06-08T08:08:08.888", | |
"initial_key": "EOS7EarnUhcyYqmdnPon8rm7mBCTnBoot6o7fE2WzjvEX2TdggbL3", | |
"initial_configuration": { | |
"max_block_net_usage": 1048576, | |
"target_block_net_usage_pct": 1000, | |
"max_transaction_net_usage": 524288, | |
"base_per_transaction_net_usage": 12, | |
"net_usage_leeway": 500, | |
"context_free_discount_net_usage_num": 20, |
/** | |
* Example to refresh tokens using https://github.com/auth0/node-jsonwebtoken | |
* It was requested to be introduced at as part of the jsonwebtoken library, | |
* since we feel it does not add too much value but it will add code to mantain | |
* we won't include it. | |
* | |
* I create this gist just to help those who want to auto-refresh JWTs. | |
*/ | |
const jwt = require('jsonwebtoken'); |
#protonmail #centos #fedora #linux
Currently protonmail bridge for linux is distributed as part of an open beta program, but soon it will be made public (https://protonmail.com/bridge/install).
Consider that the bridge linux client requires a paid protonmail account to work.
Geth (Go-Ethereum) as of January 2022 takes about 500 GiB of space on a fast/snap sync, and then grows by ~ 10 GiB/week. This will fill a 1TB SSD in ~6 months, to the point where space usage should be brought down again with an offline prune.
Happily, Geth 1.10.x introduces "snapshot offline prune", which brings it back down to about its original size. It takes roughly 4 hours to prune the Geth database, and this has to be done while Geth is not running.
Caveat that while several folx have used offline pruning successfully, there is risk associated with it. The two failure modes we have seen already are:
- There is 25 GiB or less of free disk space
pragma solidity ^0.4.18; | |
contract QuickSort { | |
function sort(uint[] data) public constant returns(uint[]) { | |
quickSort(data, int(0), int(data.length - 1)); | |
return data; | |
} | |
function quickSort(uint[] memory arr, int left, int right) internal{ |
#protonmail #debian #linux
Currently protonmail bridge for linux is distributed as part of an open beta program, but soon it will be made public (https://protonmail.com/bridge/install).
Consider that the bridge linux client requires a paid protonmail account to work.