mmitech

var blockHash = bitcoreUtil.formatHashFull(block.calcHash());
  var check =  blockHash.substring(0, 4);
  if (check != '0000') {
      console.log("Scrypt block detected. Falling back to RPC");
    self.historicSync.start({forceRPC:1}, function(){
        sockets.broadcastSyncInfo(self.historicSync.info());
            self.log('[p2p_sync] Done resync.');
        });
  return;
  }

mmitech

/*
So you need to broadcast an alert...
... here's what to do:

1. Copy sendalert.cpp into your bitcoind build directory

2. Decrypt the alert keys
  copy the decrypted file as alertkeys.h into the src/ directory.

3. Modify the alert parameters in sendalert.cpp

mmitech

<?php

// Zcash daemon credentials
$rpcuser = "";
$rpcpass = "";
$rpchost = "";
$rpcport = "";

// Wallet addresses for shielding and clearing
$t_address = ""; //your t_coinbase address 

mmitech

// Sign CAlert with stored private key
bool SignAlert(CAlert &alert)
{
    // key in WIF format
    const char* pszPrivKey = "";

    // serialize alert data
    CDataStream sMsg(SER_NETWORK, PROTOCOL_VERSION);
    sMsg << *(CUnsignedAlert*)&alert;
    alert.vchMsg = std::vector<unsigned char>(sMsg.begin(), sMsg.end());

mmitech

Keybase proof

I hereby claim:

• I am mmitech on github.
• I am mmitech (https://keybase.io/mmitech) on keybase.
• I have a public key ASC_rgi1QLkJ1Ve5t5NTlmO-llXeBt6xKYgihac4Y9mVXgo

To claim this, I am signing this object:

mmitech

0x080F411222C9F010D9c8fA053cf4c350E49609F0

mmitech

Moved to git repository: https://github.com/denji/nginx-tuning

NGINX Tuning For Best Performance

For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.

Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.

You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.

mmitech

server { listen  80;
  server_name example.com;
  access_log /var/log/example.com/nginx.access.log;
  error_log  /var/log/example.com/nginx.error.log;
  root /var/www/apps/example.com/public;
  charset utf-8;

  location / {
    rewrite ^ https://$host$request_uri? permanent;
  }

mmitech

#!/bin/bash

#
# Adds Cloudflare IPV4 addresses to the Inbound rules of a AWS Security Group
#

## defining helper functions first

# show usage
show_usage() {

mmitech

Context:

• Let Alice be the seller of an item or service, and Bob the buyer

• Trent is a service operator, who has the role of an arbitrator

• Alice wants to deal in TetherUSD

• Bob's address is mkXZ1FYBNuvrqMEE2PLzJkS39T6w7CouFH, which is funded with TetherUSD