Faruk Terzioğlu farukterzioglu

## call-then-sendtx-pattern.js
/*
In Ethereum, a contract can be written so that it returns a value for eth_call.
A Dapp can then check for success or error value of eth_call, before calling eth_sendTransaction,
to take advantage of eth_call effectively being a "preview" of the code flow that the transaction
will take.  In traditional client-server, clients can't ask servers beforehand what's going to
happen when the client makes a call; with Dapps contracts can be written so that clients can ask
for a "preview" of what is going to happen, before any funds/ethers are actually utilized
(eth_call does not cost any ethers).

Note: it is possible that in between eth_call and when eth_sendTransaction is actually mined,

## install-rabbitmq.sh
# AWS specific install of Docker
sudo yum update -y
sudo yum install -y docker
sudo service docker start
sudo usermod -a -G docker ec2-user

# exit the SSH session, login again

# Docker
docker run -d --hostname my-rabbit --name some-rabbit -p 4369:4369 -p 5671:5671 -p 5672:5672 -p 15672:15672 rabbitmq

## makefile

# Go parameters
GOCMD=go
GOBUILD=$(GOCMD) build
GOCLEAN=$(GOCMD) clean
GOTEST=$(GOCMD) test
GOGET=$(GOCMD) get
BINARY_NAME=mybinary
BINARY_UNIX=$(BINARY_NAME)_unix

## using_btcd_simnet.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                farukterzioglu
                / using_btcd_simnet.md
            
            
              Created
              September 19, 2018 08:35
                — forked from davecgh/using_btcd_simnet.md
            
              
                Using btcd's simnet to test changes on a private network
              
          
    Table of Contents


Overview
Getting Started


### 1. Overview
When developing bitcoin applications or testing potential changes, it is often extremely useful to have a test network where transactions are actually mined into blocks and difficulty levels are low enough to generate blocks as needed.
In order to facilitate these scenarios, btcd provides a simulation network (--simnet). The following is an overview of the most important properties that distinguish it from the main network:

  
## btcd_pull_request_management.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                farukterzioglu
                / btcd_pull_request_management.md
            
            
              Created
              September 20, 2018 19:43
                — forked from davecgh/btcd_pull_request_management.md
            
              
                Managing a btcd Pull Request for Code Contibutions
              
          
    Initial Preparation

The first step is to read the Code Contribution Guidelines documentation to get a good understanding of policies used by the project
Once that is done, the following commands illustrate a straight forward setup for submitting pull requests to the project:
One time setup


Fork btcd on github
Run the following command to obtain btcd, all dependencies, and install it (this has probably already been done):


## example_txscript_signaturescript.go
package main

import (
	"encoding/hex"
	"fmt"

	"github.com/btcsuite/btcd/btcec"
	"github.com/btcsuite/btcd/chaincfg"
	"github.com/btcsuite/btcd/txscript"
	"github.com/btcsuite/btcd/wire"

## example_txscript_step.go
package main

import (
	"encoding/hex"
	"fmt"
	"os"

	"github.com/btcsuite/btcd/chaincfg/chainhash"
	"github.com/btcsuite/btcd/txscript"
	"github.com/btcsuite/btcd/wire"

## simnetblksubmit.go
package main

import (
	"encoding/binary"
	"errors"
	"io/ioutil"
	"log"
	"math"
	"math/big"
	"path/filepath"

## example_txscript_signtxoutput.go
package main

import (
	"encoding/hex"
	"fmt"

	"github.com/btcsuite/btcd/btcec"
	"github.com/btcsuite/btcd/chaincfg"
	"github.com/btcsuite/btcd/txscript"
	"github.com/btcsuite/btcd/wire"

## btcdwstest.html
<!DOCTYPE html>

<html>
	<head>
		<meta charset="utf-8" />
		<title>WebSocket Test</title>
		<script language="javascript" type="text/javascript">
		var wsUri = 'wss://127.0.0.1:8334/ws';
		var rpcUser = "rpcuser";
		var rpcPass = "rpcpass";
	/*
	In Ethereum, a contract can be written so that it returns a value for eth_call.
	A Dapp can then check for success or error value of eth_call, before calling eth_sendTransaction,
	to take advantage of eth_call effectively being a "preview" of the code flow that the transaction
	will take. In traditional client-server, clients can't ask servers beforehand what's going to
	happen when the client makes a call; with Dapps contracts can be written so that clients can ask
	for a "preview" of what is going to happen, before any funds/ethers are actually utilized
	(eth_call does not cost any ethers).

	Note: it is possible that in between eth_call and when eth_sendTransaction is actually mined,
	# AWS specific install of Docker
	sudo yum update -y
	sudo yum install -y docker
	sudo service docker start
	sudo usermod -a -G docker ec2-user

	# exit the SSH session, login again

	# Docker
	docker run -d --hostname my-rabbit --name some-rabbit -p 4369:4369 -p 5671:5671 -p 5672:5672 -p 15672:15672 rabbitmq

	# Go parameters
	GOCMD=go
	GOBUILD=$(GOCMD) build
	GOCLEAN=$(GOCMD) clean
	GOTEST=$(GOCMD) test
	GOGET=$(GOCMD) get
	BINARY_NAME=mybinary
	BINARY_UNIX=$(BINARY_NAME)_unix
	package main

	import (
	"encoding/hex"
	"fmt"

	"github.com/btcsuite/btcd/btcec"
	"github.com/btcsuite/btcd/chaincfg"
	"github.com/btcsuite/btcd/txscript"
	"github.com/btcsuite/btcd/wire"
	package main

	import (
	"encoding/binary"
	"errors"
	"io/ioutil"
	"log"
	"math"
	"math/big"
	"path/filepath"
	<!DOCTYPE html>

	<html>
	<head>
	<meta charset="utf-8" />
	<title>WebSocket Test</title>
	<script language="javascript" type="text/javascript">
	var wsUri = 'wss://127.0.0.1:8334/ws';
	var rpcUser = "rpcuser";
	var rpcPass = "rpcpass";