BIP: ?? Layer: Applications Title: SNICKER - Simple Non-Interactive Coinjoin with Keys for Encryption Reused Author: Adam Gibson <[email protected]> Comments-Summary: No comments yet. Comments-URI: - Status: Proposed Type: Informational Created: -
This work is released under a Creative Commons Attribution-NoDerivatives 4.0 International License.
"OpenPGP" refers to the OpenPGP protocol, in much the same way that HTML refers to the protocol that specifies how to write a web page. "GnuPG", "SequoiaPGP", "OpenPGP.js", and others are implementations of the OpenPGP protocol in the same way that Mozilla Firefox, Google Chromium, and Microsoft Edge refer to software packages that process HTML data.
Last updated: 16 March 2019
Hi! This article now lives at https://jonatack.github.io/articles/how-to-compile-bitcoin-core-and-run-the-tests where I will continue to update it. Cheers.
This is a simplified compilation of the various docs in https://github.com/bitcoin/bitcoin/tree/master/doc. Don't hesitate to read them for more information.
All steps are to be run from your terminal emulator, i.e. the command line.
// Usage: | |
// getByteCount({'MULTISIG-P2SH:2-4':45},{'P2PKH':1}) Means "45 inputs of P2SH Multisig and 1 output of P2PKH" | |
// getByteCount({'P2PKH':1,'MULTISIG-P2SH:2-3':2},{'P2PKH':2}) means "1 P2PKH input and 2 Multisig P2SH (2 of 3) inputs along with 2 P2PKH outputs" | |
function getByteCount(inputs, outputs) { | |
var totalWeight = 0 | |
var hasWitness = false | |
var inputCount = 0 | |
var outputCount = 0 | |
// assumes compressed pubkeys in all cases. | |
var types = { |
### new ubuntu 18.04 server | |
### Be sure to run | |
# sudo apt-get update && sudo apt-get -y upgrade && sudo reboot | |
### For security updates | |
### Then run this script with passwordless sudo account ubuntu (default for ubuntu AWS EC2): | |
# CERTDOMAIN=something.yourdomain.com [email protected] ./thisScript.sh | |
# Install Bitcoin 0.17.0 etc. | |
sudo add-apt-repository -y ppa:bitcoin/bitcoin &>/dev/null | |
sudo apt-get update &>/dev/null |
const ElectrumClient = require('electrum-client') | |
const peers = require('electrum-host-parse').getDefaultPeers('BitcoinSegwit').filter(v => v.ssl) | |
const getRandomPeer = () => peers[peers.length * Math.random() | 0] | |
let mainClient = false | |
const main = async () => { | |
const peer = getRandomPeer() | |
console.log('begin connection:', JSON.stringify(peer)) | |
mainClient = new ElectrumClient(peer.ssl, peer.host, 'ssl') |
/** | |
* Google Drive | |
* created by [email protected] | |
*/ | |
import React, { Component } from 'react'; | |
import { | |
Platform, | |
StyleSheet, | |
Text, |
Q: Are there plans to support a web worker based rendered in React Core ? Angular2 has support for it in core - axemclion
A: right now we're not considering web workers in depth because it's difficult to carve off pieces that can be parallelized independently -- simply moving React to a separate thread while executing DOM operations on the main thread would free up the main thread but likely wouldn't improve responsiveness overall. so instead we're looking more at how we can do concurrent work on the main thread and cancel in-progress updates if new high-priority input arrives
we might experiment a little more with threads/workers on React Native, but that would likely be more along the lines of running parts of Relay in a separate thread since it's still hard to split up the component tree
Q: did you ever think you’d be learning about fibers and coroutines to implement a JavaScript UI library? 😃 - iamdustan
A: can't say I ever considered it, but I suppose I didn't expect that I wou