Stevie Zollo szollo

## aws.sh
#!/bin/bash
# bash functions to autenticate and assume roles in aws federated accounts
# required tools on $PATH - aws, date, curl, jq, libxml2-utils

# requried environment variables:
export AWS_CLI=`which aws`

# optional environment variable, to automatically assume a specific role when calling assume()
# AWS_ASSUME_ROLE=arn:aws:iam::369407384105:role/cross-account-federated-role

## keybase.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                szollo
                / keybase.md
            
            
              Created
              January 27, 2018 07:16
            
          
    Keybase proof

I hereby claim:

I am szollo on github.
I am szollo (https://keybase.io/szollo) on keybase.
I have a public key ASBtGIyFvQmd8O469gYPeA0Nw5O1ImC2Hd3_Sx9kuO82FAo

To claim this, I am signing this object:

  
## lnmainnet.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                szollo
                / lnmainnet.md
            
            
              Last active
              February 5, 2018 06:35
            
              
                Set up a LN node on mainnet using bitcoind and lightningd
              
          
    Run a Lightning Network node on mainnet

Disclaimer

Please note that running LN on mainnet is NOT deemed safe for mainnet yet - all testing should be done on testnet. Be aware of the risks and only send bitcoins you are willing to lose.
This quick gist uses bitcoind and lightningd to run a LN node on mainnet, and it assumes the following:

Ubuntu Linux (16.04.3 on this walkthrough)
some spare bitcoins you are willing to lose

Install all prerequired software


## CE80FDD7744B05B4.asc
-----BEGIN PGP PUBLIC KEY BLOCK-----

mQINBFpsHr0BEAC8pHd4weJU3xHM2HAm7zt/R7XVHbsY3qk/N6rBvvujuHhFg38r
/5tiMoZenE0Pvp+5I31w8lNDjlZ8U3qBtvAE0Qz1OOWSgRdhUrkKacyxmQ9j0Yy3
p4EMjZ6w16tlR6VATPbYrQo8kXcs28i3zBl49TDVe5bNN/vl+gr5zCCzP7pKotvK
C7IWAtpDl1Ui/0NzBA1bvdeJOU5p+htlMA/c8/5+1+CivPKViHwgV2kCM3OJc84k
qA3GJCCRJP1PHKb6sWwpvJk9w14MOR/eriC6Vv0jg/yD949eQ4lIIZcPokiHShUv
0kowW7D8eOyR6kfj44lW8woS7UTB2s7VYXWh4/WLurdhM4AdnpCc83NsB4c63COm
aWsn+SXL0n/9VBZWyJDnSppN4oDNxmjjYYLg9PetsMhaj5fHO19vw1HwIguIpdhg
+EQQcoFNTXRow6PRWFvWjWXBCsjJUjl+w65rlphLMQLE1gaq9how36p/8AI6eR9g
	#!/bin/bash
	# bash functions to autenticate and assume roles in aws federated accounts
	# required tools on $PATH - aws, date, curl, jq, libxml2-utils

	# requried environment variables:
	export AWS_CLI=`which aws`

	# optional environment variable, to automatically assume a specific role when calling assume()
	# AWS_ASSUME_ROLE=arn:aws:iam::369407384105:role/cross-account-federated-role
	-----BEGIN PGP PUBLIC KEY BLOCK-----

	mQINBFpsHr0BEAC8pHd4weJU3xHM2HAm7zt/R7XVHbsY3qk/N6rBvvujuHhFg38r
	/5tiMoZenE0Pvp+5I31w8lNDjlZ8U3qBtvAE0Qz1OOWSgRdhUrkKacyxmQ9j0Yy3
	p4EMjZ6w16tlR6VATPbYrQo8kXcs28i3zBl49TDVe5bNN/vl+gr5zCCzP7pKotvK
	C7IWAtpDl1Ui/0NzBA1bvdeJOU5p+htlMA/c8/5+1+CivPKViHwgV2kCM3OJc84k
	qA3GJCCRJP1PHKb6sWwpvJk9w14MOR/eriC6Vv0jg/yD949eQ4lIIZcPokiHShUv
	0kowW7D8eOyR6kfj44lW8woS7UTB2s7VYXWh4/WLurdhM4AdnpCc83NsB4c63COm
	aWsn+SXL0n/9VBZWyJDnSppN4oDNxmjjYYLg9PetsMhaj5fHO19vw1HwIguIpdhg
	+EQQcoFNTXRow6PRWFvWjWXBCsjJUjl+w65rlphLMQLE1gaq9how36p/8AI6eR9g