# faucets - Is there any where to get free testnet Bitcoins ...

• faucets - Is there any where to get free testnet Bitcoins ...
• Bitcoin Testnet Faucet
• Yet Another Bitcoin Testnet Faucet! Bech32!
• Bitcoin Testnet Faucet
• Testnet-Faucet - Free Testnet Coins!
##### P2P Bitcoin Derivative Trading Through the Blockchain: Equities, Bonds, Forex & Commodities

Research & ideas to use [Veritaseum's UltraCoin](http://ultra-coin.com/) **user programmable Bitcoin swaps** to trade exposures to cryptos, forex, equities, bonds & commodities through 45,000+ global tickers & up to 10,000x price leverage - peer-to-peer. Veritaseum's UltraCoin is a software concern that holds no client funds and is not a financial entity, hence presents you with no counterparty or default risk. [Download the client & tutorials](http://ultra-coin.com/index.php/download-beta)

##### New Bitcoin Testnet Faucet - Free testnet Bitcoins.

Hey everyone, as a developer I know how important testnet coins are. Therefore I have created a faucet to allow developers or anyone to obtain free coins once per day.
I'm also available for hire for any Bitcoin related website work, so get in touch if you need a hand.
I've also done this in order to strengthen the Bitcoin community and encourage Bitcoin development.
Check it out!
http://www.bitcointestnetfaucet.com/

##### How to sell xBricks for money (self post for mod approval)

Preface
I've written this guide with those that are unfamiliar with crypto in mind, however it's still a lengthy process. I'm going to try to present this in a way where you don't have to learn how the underlying crypto technology works, but I will add in links to relevant concepts in case you're curious. This process was a lot more complicated before but I made a web interface to simplify it.
At the time of writing this, FortniteBR BRICKs are worth 10 cents a piece. That makes 1000 bricks worth 100 bucks. The liquidity pool is about $14,000 at the time of writing, meaning that there's room in the market for you to hypothetically get$7,000 if you had a lot of BRICKs.
If at any point throughout this process you need help, DM me!
Misc. Resources That Might Be Helpful
What you need
You will need:
• A desktop computer with a modern browser
• A phone or phone emulator (so that you can run the reddit mobile app and collect your BRICKs)
Step 1: Setup
On your desktop computer, install MetaMask. This is an Ethereum Wallet which will allow you to interact with the Ethereum Network and its many sidechains. More on this later.
Follow the setup instructions in MetaMask. If you've never done this before, you'll need to create a new seed phrase. Video tutorial if you get stuck.
YOUR SEED PHRASE IS THE KEY TO YOUR WALLET. ANYONE WHO HAS ACCESS TO YOUR SEED PHRASE CAN TAKE YOUR FUNDS. IF YOU LOSE YOUR SEED PHRASE YOU HAVE NO WAY TO RECOVER YOUR FUNDS. WRITE IT DOWN AND STORE IT IN A SAFE PLACE!!! NEVER GIVE IT OUT TO ANYONE - ANYONE THAT ASKS FOR YOUR SEED PHRASE IS TRYING TO SCAM YOU! DON'T FALL FOR IT!
In the MetaMask interface, you'll see "Main Ethereum Network". This process uses two networks. One of them is the Rinkeby Testnet (where the BRICK tokens are natively) and one of them is the xDAI network which is where we will bridge the tokens to in order to exchange them for Dai, a token which is pegged to the price of the dollar.
From the dropdown, select Rinkeby Testnet. If you're in the assets tab, you should see a thing that shows your ETH balance. Below this, you should see an "add token" button. Click it. Go to "Custom Token" at the top. In "token contract address," paste in the following:
0xe0d8d7b8273de14e628d2f2a4a10f719f898450a
The other fields will autofill. Hit next. You'll now see your BRICK balance (which will be 0, you haven't transferred your bricks yet) in MetaMask if you've done everything right.
You'll need Rinkeby Ether to cover transaction fees. Since we're on a testnet, the Ether is worthless which means people hand it out for free. You can get this Ether from a variety of places:
• https://faucet.rinkeby.io/
• DM me
• Anyone who has Rinkeby Ether to spare: Make a comment below so that those who need it can ask you. Thanks :)
WARNING: ALL CRYPTO TRANSACTIONS ARE IRREVERSIBLE.
Your Ethereum address shows up under Rinkeby. It should be "0x" followed by a bunch of hex characters. Click on it to copy it to your clipboard. You now need to somehow get this to your mobile device. Email it to yourself, text it to yourself, whatever.
On your Reddit mobile app home screen, click on your profile icon and then go to vault. You'll need to set this up and claim your tokens if you haven't already. Be aware that this is also technically an Ethereum wallet. Keep your seed phrase safe.
Send however many BRICKs you want to sell to your MetaMask wallet. Check to make sure the addresses are the same, but don't worry too much about making a typo or whatever. The chances that you'd make a typo that would result in a valid Ethereum address are slim, if you get a character wrong it'll just tell you it's not a real Ethereum address and prevent you from sending.
It may show an error when you try to send. This is somewhat rare but pretty normal. They often run out of testnet Ether. Come back later and try again.
If it works properly, it'll take about a minute to go through. It may take longer than that.
Once the transaction goes through, you'll see that you have an absurd amount of BRICKs in MetaMask. No, there wasn't a glitch. The people who wrote the code for BRICKs made the decimals of precision weird for some reason. It's off by a factor of 1018. This isn't a big deal.
If you see Bricks and Ether (ETH) in your MetaMask wallet, proceed to the next step. If you're having issues, feel free to DM me.
Step 2: Getting Your BRICKs from Rinkeby to xDai
There's a LOT going on under the hood for this part (deets for those interested). Previously this required manually generating contract interactions, which is kind of a pain if you're new to Ethereum. I made a UI to make this easier (it generates the transactions for you, all you have to do is sign them with your wallet). This took way longer to do than you might guess, so feel free to help a homie out at:
0x4BCcC2569DD93C7dF43431A7b70db569dedB6187
Go to my tool. Hit connect. If you're on the Rinkeby network, it should show your balance in BRICKs. Enter the amount you want to bridge (probably all of them). If neither of us have made any mistakes, it should pop up with a request to spend your BRICKs. If there's any issue with this tool, DM me. This allows the TokenBridge contract to take your BRICKs and put them on the xDai network where you can sell them. This is the part where you'll get an error if you don't have any testnet ETH. Set the gas price to 1 (the suggested price is based on the Main Ethereum Network - it's way too high). After you approve that, it'll give you another thing to accept. This is the actual transaction where it'll bridge to xDai. Again, make sure the gas price is set to 1 and confirm the transaction.
Switch to the xDai network. We're going to add another token. Again, go to "add token" > "custom token" > "token contract address". Paste in:
0x2f9ceBf5De3bc25E0643D0E66134E5bf5c48e191
If the transactions have gone through, you should see your xBricks (the name for BRICKs that have been bridged to xDai) in MetaMask. If not, wait a bit for the transactions to go through. Sometimes there are slowdowns that cause bridging to take a while. Shouldn't take too long, though. Once that's done, you're ready for the next step.
Go to Honeyswap. Hit "select a token." You'll need to paste in the xBrick address again. Here it is:
0x2f9ceBf5De3bc25E0643D0E66134E5bf5c48e191
Click xBrick.

##### Need to claim 0.005 BTC. Where should I do that, which isn't Coinbase?

After reading things like this, CoinBase seems like it is a headache. I don't have a Bitcoin ID, but would like to obtain one to claim 0.005 BTC I got from a Faucet. The end goal is to get this into PayPal. I signed up for CoinBase but as soon as I logged in, it asked for my address, photo ID, social security number, etc (USA). Fuck that, is there somewhere else that isn't this invasive?

#### Update

I rewrote this post to clean it up a bit and add more context. The original can still be found here
With the last few drops of Electrum it's been much easier to use LN. I've played around with Electrum-desktop on testnet. Everything worked great, and it is a great way to learn about channel capacity and invoices without having to put real money at risk. Electrum has a "swap" button to adjust capacity but I think it may be broken on testnet presently. There are a few ways to adjust capacity / liquidity that I'll discuss below.

### Get Electrum running

1. Install Electrum 4.0.2 and run it on testnet enabling LN.
2. Get testnet BTC and send it to Electrum
3. Open a channel in Electrum with either a known entity, or use their channel suggestion
4. Wait an hour or so for the channel to open.
5. Perform a submarine-swap operation to give you a 50/50 capacity
6. Wait for the swap to complete

### Balance capacity

LN channels have a (local) sending capacity and a (remote) receiving capacity. To verify your local/remote capacity click on the channel and view "Details". New channels default to 100%/0% local/remote capacity, meaning you can send, but not receive. There is also some rule that requires you to be below 90% local before you can receive anything. So if you need to receive payments on LN before you spend 10% of your local capacity you will need to find a way to balance local/remote. As mentioned before, the easiest is just to spend, but if you don't have anything to spend on there are some other options
• Electrum Swap Button - Currently broken in testnet, but the intention is to provide an in-app ability to do a reverse_swap (LN to BTC) to allow you to pull some of your local capacity out of your channel giving you some balance. Normally you just hit the Swap button in the channel tab and follow instructions.
• Use third party Swap site - The Boltz Exchange has a testnet swap service that is pretty simple to use. You can also use them on mainnet, though you really should calculate the fees by hand to know what your in for. Other mainnet services like FixedFloat, or lighting-labs loop are also popular choices
• Push on Open Channel - If your opening a channel between nodes you own, you can use the electrum-cli to set a push_amt to push out of your channel to the remote node on open. This is the same as paying them some amount, just without an invoice. So make sure you only push to yourself, or those you actually owe money to.
• Move capacity between wallets - Some wallets like Eclair Mobile Testnet give you the ability to create inbound capacity on channel open. Or you can use custodial (*hiss*) wallets like HTLC.me (testnet) or Wallet of Satoshi (mainnet). Custodial (*hiss*) LN wallets generally will do the channel balancing for you giving you limitless receive capacity.

### Test Node Visibility

Once you free up some receive capacity, you also need to ensure that your node is reachable. In the default config your node will not be publicly visible. Electrum will handle the last hop for you, but your sender still need to at least be able to route to one of the nodes you have receive capacity on. This may occationally fail causing "Path not found" errots when sending, or when others send to you. In the Electrum preferences there are some options to run local watchtowers and keep the app resident. This will help since your wallet needs to be running for it to receive payments. But even if you enable all options sometimes you will just end up on an isolated node. If this happens, take care to ensure you connect to nodes that are highly connected to others.
If you want to test your visibility, just paste an invoice in this thread and hopefully someone can try to send you some tBTC-LN.

##### ⚡ Lightning Network Megathread ⚡

Last updated 2018-01-29
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!

# ⚡What is the Lightning Network? ⚡

## Lightning Network Experts on Reddit

• starkbot - (Elizabeth Stark - Lightning Labs)
• roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
• stile65 - (Alex Akselrod - Lightning Labs)
• cfromknecht - (Conner Fromknecht - Lightning Labs)
• RustyReddit - (Rusty Russell - Blockstream)
• cdecker - (Christian Decker - Blockstream)
• Dryja - (Tadge Dryja - Digital Currency Initiative)
• josephpoon - (Joseph Poon)
• fdrn - (Fabrice Drouin - ACINQ )

## Lightning Network Experts on Twitter

• @starkness - (Elizabeth Stark - Lightning Labs)
• @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
• @stile65 - (Alex Akselrod - Lightning Labs)
• @bitconner - (Conner Fromknecht - Lightning Labs)
• @johanth - (Johan Halseth - Lightning Labs)
• @bvu - (Bryan Vu - Lightning Labs)
• @rusty_twit - (Rusty Russell - Blockstream)
• @snyke - (Christian Decker - Blockstream)
• @JackMallers - (Jack Mallers - Zap)
• @tdryja - (Tadge Dryja - Digital Currency Initiative)
• @jcp - (Joseph Poon)
• @alexbosworth - (Alex Bosworth - yalls.org)

## Lightning on Testnet

#### Place a testnet transaction

• ZigZag - Disclaimer You must trust ZigZag to send to Target Address

## Lightning on Mainnet

Warning - Testing should be done on Testnet

## Lightning implementations

• LND - Lightning Network Daemon (Golang)
• eclair - A Scala implementation of the Lightning Network (Scala)
• c-lightning - A Lightning Network implementation in C
• lit - Lightning Network node software (Golang)
• lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
• lightning-integration - Lightning Integration Testing Framework
• ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]

## Payment Processors

• BTCPay - Next stable version will include Lightning Network

## IRC

• #lightning-dev (on Freenode) - Lightning protocol development
• #lnd - Channel for lnd development that also has a bot for github commits.

## ⚡ Lightning FAQs ⚡

If you can answer please PM me and include source if possible. Feel free to help keep these answers up to date and as brief but correct as possible
###### Is Lightning Bitcoin?
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
###### Is the Lightning Network open source?
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
###### Who owns and controls the Lightning Network?
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
###### I’ve heard that Lightning transactions are happening “off-chain”…Does that mean that my bitcoin will be removed from the blockchain?
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
###### Do I need a constant connection to run a lightning node?
Not necessarily,
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
###### Does Lightning require Segregated Witness?
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
###### Can I Send Funds From Lightning to a Normal Bitcoin Address?
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
###### Can I Make Money Running a Lightning Node?
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
###### What is the release date for Lightning on Mainnet?
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
###### Would there be any KYC/AML issues with certain nodes?
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
###### What is the delay time for the recipient of a transaction receiving confirmation?
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
###### How would the lightning network work between exchanges?
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
###### Does every user need to store the state of the complete Lightning Network?
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
###### Would I need to download the complete state every time I open the App and make a payment?
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
###### What needs to happen for the Lightning Network to be deployed and what can I do as a user to help?
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
###### Is there anyway for someone who isn't a developer to meaningfully contribute?
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
No -- Source
###### Do I need to run a full Bitcoin node to run a lightning node?
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
###### How does the lightning network stop "Cheating" (Someone broadcasting an old transaction)?
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
###### How many times would someone need to open and close their lightning channels?
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
###### When setting up a Lightning Network Node are fees set for the entire node, or each channel when opened?
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
###### Can Lightning routing fees be changed dynamically, without closing channels?
Yes but it has to be implemented in the Lightning software being used. -- Source
###### How can you make sure that there will be routes with large enough balances to handle transactions?
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source

# Special Thanks and Notes

• Many links found from awesome-lightning-network github
• Everyone who submitted a question or concern!
• I'm continuing to format for an easier Mobile experience!

##### Soo after almost 3 months of setting up I have my own LN full node running on RP3

 I have been eager to try LN mainnet since the very beginning of it. I've found out about lnd, eclair, zap and other wallets but every scenario I tried to use it failed because of critical issues: eclair does not really constitute a wallet, it's more like a credit card - you can send money but not receive it lnd is okay, but requires a server and tons of resources for maintaining a full node, can't be used securely, efficiently and mobily at the same time zap offers some cloud wallet (in testnet!) by default, this is a serious misunderstanding of my cryptoanarchy needs web wallets - ah, forget it So I've decided to use my Raspberry Pi with a very old laptop HDD attached (200GB so the pruning function has to be used) to create a backend wallet service and zap desktop (temporarily!) as my frontend control panel. https://preview.redd.it/0vcq147887q11.png?width=1024&format=png&auto=webp&s=7bb6eccdd4110a857e5af0400acc2d7e1ee7ee85 Setting up Pi is easy, lots of tutorials over the internet, not gonna discuss it here. Then I had to obtain bitcoind (current rel: bitcoin-0.17.0-arm-linux-gnueabihf.tar.gz) and lnd (lnd-linux-armv7-v0.5-beta.tar.gz), create a bitcoin technical user, deploy the tools, configure and install new systemd services and go through the configs. This is a tricky part, so let's share: # Generated by https://jlopp.github.io/bitcoin-core-config-generato # This config should be placed in following path: # ~/.bitcoin/bitcoin.conf # [core] # Set database cache size in megabytes; machines sync faster with a larger cache. Recommend setting as high as possible based upon machine's available RAM. dbcache=100 # Keep at most unconnectable transactions in memory. maxorphantx=10 # Keep the transaction memory pool below megabytes. maxmempool=50 # Reduce storage requirements by only storing most recent N MiB of block. This mode is incompatible with -txindex and -rescan. WARNING: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, greater than 550 = automatically prune blocks to stay under target size in MiB). prune=153600 # [network] # Maintain at most N connections to peers. maxconnections=40 # Use UPnP to map the listening port. upnp=1 # Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit. maxuploadtarget=5000 # [debug] # Log IP Addresses in debug output. logips=1 # [rpc] # Accept public REST requests. rest=1 # [wallet] # Do not load the wallet and disable wallet RPC calls. disablewallet=1 # [zeromq] # Enable publishing of raw block hex to . zmqpubrawblock=tcp://127.0.0.1:28332 # Enable publishing of raw transaction hex to . zmqpubrawtx=tcp://127.0.0.1:28333 # [rpc] # Accept command line and JSON-RPC commands. server=1 # Username and hashed password for JSON-RPC connections. The field comes in the format: :$. RPC clients connect using rpcuser=/rpcpassword= arguments. You can generate this value with the ./share/rpcauth/rpcauth.py script in the Bitcoin Core repository. This option can be specified multiple times. rpcauth=xxx:yyy$zzz  Whooaa, this online config generator is really helpful, but I still had to manually correct a few things. The last line is obviously generated by rpcauth.py, I disabled the wallet functionality as lnd is going to take care of my funds. ZMQ is not available to the network so only my LND can use it, RPC usage I still have to think through a little, in general I would like to have my own block explorer some day but also be safe from any hacking attempts (thus I would need at least 2 RPC ports/user accounts - one for lnd, one for block explorer frontend). No ports open on firewall at this time, only UPnP is active and gently opens 8333 for block/tx transfers. Now, synchronizing the blockchain took me time from mid-July to early September... The hard drive is really slow, also my external HDD drive has some trouble with its A/C adapter so Pi was getting undervoltage alerts all the time. Luckily, it is just downclocking when it happens and slowly but steadily synchronized the whole history. After all, I'm not paying even $5 monthly for a VPS, it is by design the cheapest hardware I could use to set up my LN wallet. When bitcoind was ready (I've heard some stories about btcd but I don't trust this software yet, sorry), it's time to configure lnd.conf: [Application Options] debuglevel=trace rpclisten=0.0.0.0:10009 externalip=X.X.X.X:9735 listen=0.0.0.0:9735 alias=X color=#XXXXXX [Bitcoin] bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind [Bitcoind] bitcoind.rpchost=127.0.0.1 bitcoind.rpcuser=X bitcoind.rpcpass=X bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333  Here I've had to XXX a little more fields, as not only the bitcoind RPC credentials are stored here, but also my node's public information (it should be illegal to run nodes without specifically selected color and alias!). It is public (and I had to open port 9735 on my firewall), but not necessarily connected to my reddit account for most of the adversaries, so let's keep it this way. In fact, I also see a security vulnerability here: my whole node's stability depends on the IP being static. I could swap it for a .tk domain but who can tell if the bad guys won't actively fight DNS system in order to prevent global economic revolution? As such, I would rather see node identification in LN based on a public key only with possible *hints* of last-known-ip-address but the whole discovery should be performed by the nodes themself in a p2p manner, obviously preventing malicious actors from poisoning the network in some way. For now, I consider the IP stability a weak link and will probably have to pay extra Bitcoin TX fees when something happens to it (not much of a cost luckily!). ​ https://preview.redd.it/hjd1nooo77q11.png?width=741&format=png&auto=webp&s=14214fc36e3edf139faade930f4069fc31a3e883 Okay then, lnd is up and running, had to create a wallet and give it a night for getting up to speed. I don't know really what took it so long, I'm not using Windows nor 'localhost' in the config so the issues like #1027 are not the case. But there are others like #1545 still open so I'm not going to ponder much on this. I haven't really got any idea how to automatically unlock the wallet after Pi restart (could happen any time!), especially since I only tried to unlock it locally with lncli (why would I enter the password anywhere outside that host?), but let's say that my wallet will only be as stable as my cheap hardware. That's okay for the beta phase. Finally, zap-desktop required me to copy tls.cert and admin.macaroon files to my desktop. If my understanding of macaroon (it's like an authentication cookie, that can later be revoked) is correct then it's not an issue, however it would be nice to have a "$50 daily limit" macaroon file in the future too, just to avoid any big issues when my client machine gets stolen. Thanks to this, I can ignore the silly cloud-based modes and have fully-secure environment of my home network being the only link from me to my money. https://preview.redd.it/11bw3dgw47q11.png?width=836&format=png&auto=webp&s=b7fa7c88d14f22441cbbfc0db036cddfd7ea8424 Aaand there it is. The IP took some time to advertise, I use 1ml.com to see if my node is there. The zap interface (ZapDesktop-linux-amd64-v0.2.2-beta.deb) lacks lots of useful information so I keep learning lncli syntax to get more data about my new peers or the routes offered. The transactions indeed run fast and are ridiculously cheap. I would really love to run Eclair with the same settings but it doesn't seem to support custom lnd (why?). In fact, since all I need is really a lncli wrapper, maybe it will be easy to write my own (seen some web gui which weighs 700MB after downloading all dependencies with npm - SICK!). Zap for iOS alpha test registration is DOWN so I couldn't try it (and I'm not sure if it allows custom lnd selection), Zap for Android doesn't even exist yet... I made a few demo transactions and now I will explore all those fancy t-shirt stores as long as the prices are still in "early investor" mode - I remember times when one could get 0.001 BTC from a faucet... https://preview.redd.it/42sdyoce57q11.png?width=836&format=png&auto=webp&s=7ec8917eaf8f3329d51ce3e30e455254027de0ee If you find any of the facts presented by me false, I am happy to find out more in the discussion. However what I did I did mostly for fun, without paying much attention to the source code, documentation and endless issue lists on github. By no means I claim this tutorial will work for you but I do think I shared the key points and effort estimations to help others decide if they want a full-node LN client too. I'm also interested in some ideas on what to do with it next (rather unlikely that I will share my lnd admin.macaroon with anyone!) especially if it gives me free money. For example, I can open 1000 channels and start earning money from fees, although I no longer have more Bitcoins than the LN capacity yields... I will probably keep updating the software on my Pi until it leaves beta phases and only then will pour more money inside. I'm also keen on improving the general security of my rig and those comments I will answer more seriously. submitted by pabou to Bitcoin [link] [comments]

##### An Introduction

Hello and welcome to Tangrams !
If you are already part of our community and found your way here from Discord, good to see you. We hope you'll enjoy our brand new subreddit.
In case you are new to Tangram, first of all we are very glad to have you onboard! Please read on to get gain some further information.

# What is Tangram?

Tangram is a DAG (Directed Acyclic Graph) privacy-focused cryptocurrency. Tangram aims to be a private and anonymous digital currency, a platform for near instant and feeless exchange of value which allows users to securely manage personal and financial information.
Our mission is to create the most private distributed ledger technology the world has ever seen, one that is provably impervious to re-identification attacks. It must be fast, feeless, and infinitely scalable. Tangram will function as a true cryptocurrency, while supporting other capabilities such as smart contracts, data storage, and communications. Tangram is a startup focused on cutting-edge engineering, compelling user experience, irresistible branding, and a vibrant community, all built from scratch. Tangram will be the end-to-end solution you know you can trust to safeguard your identity, your data, your business, and your rights in a world of prying eyes. Privacy by Design.
It is currently in development, with the testnet and mainnet planned for the short to middle term. (More information regarding various expected deadlines can be found here )

# Where can I find more information on the technical aspects of Tangram?

• The first page of our Bitcointalk thread contains a lot of details about the aims of Tangram, its inbound architecture and technology, and summaries of the additions and improvements made in the various alphas (current version: alpha 0.5)
• One of our community managers, kochtrane, has written a few articles about the project and its progress on Medium
• A bunch of more general information will soon be available on our website (currently being updated)
A little rundown of what's been released so far, and what to expect from the near future alpha releases:
Released
View the roadmap for further details.

# How will Tangram be distributed?

The token metrics of Tangram are as follows:
Maximum Token Supply: 183,744,990
• Public: 65%
• Contributors: 10%
• Founders: 7.84%
• Development Fund: 10%
• Community Fund 7.16%
• Token Distribution Method: Faucet Distribution
Once mainnet launches, everyone is going to have the opportunity to participate in the token distribution process. The details of which method(s) will be implemented are currently being discussed and will be finalized soon. As you can see above, 65% of the total supply ( 119,434,243.5 SNKs) are reserved for public distribution.

# How can I get involved in the project?

We are a community-centered project and welcome all, especially those that wish to contribute to our growth and improvement. If you believe you have some spare time and skills to dedicate, feel free to fill out our Community Talent Pool Form!
Alternatively, if you just want to get involved more generally in our vibrant community and have access to development in real time, we recommend joining our Discord. Most of the fun happens there! If you have any questions or queries, do not hesitate to come by the Discord where you are sure to get a quick response.

# FAQ

• When will main-net for Tangram be live?
TBC
• What is Tangrams mission?
See Manifesto. https://medium.com/@getsneak/a-sneak-manifesto-163eb38e00ea
• Is Tangram a fork of Bitcoin, Ethereum, Monero or Nano?
No.
• What is the distribution allocations?
Public: 65% Contributors: 10% Founders: 7.84% Development Fund: 10% Community Fund: 7.16%
• How will public distribution occur?
Through lending your computation power for research and development against finding a cure (diseases such as Alzheimer’s disease, Huntington’s disease, cystic fibrosis, BSE (Mad Cow disease), an inherited form of emphysema, and even many cancers). Find out more here: https://foldingathome.org/ How it works in Tangram public free distribution: https://medium.com/@getsneak/f-h-faucet-alpha-0-1-testing-d179568d1f40
• When will the public faucet distribution occur?:
When Tangram goes main-net (end of December 2018).
• 10% of supply is allocated to Contributors – who are they and why?
Contributors donated a combination of Monero, Nano, Bitcoin, and Ethereum to the developers to support the development throughout the early stages. These donations allowed Matthew Hellyer to move to developing the Tangram platform full-time.
• 5% of supply is allocated to the Community Fund – who are they and why?
The Community Fund is for those who have provably donated to a privacy DAG project prior to February 28th that turned out to be a scam. Contact the devs to receive Tangrams in return for your scammed donations at a rate of half the dollar value of your donation the day it was sent. 26% of the Community Fund has already been claimed.
• Will there be any transparency in regards to the Developer’s Fund?
• How can I become an alpha-tester?
Testing is open to all. See here: https://medium.com/tangram-tgm/test-net0-release-ac5ad5d691ae
• Are there any current bug bounties?
TBC - Currently the only bug bounty available would be associated with the faucet: https://medium.com/@getsneak/f-h-faucet-alpha-0-1-testing-d179568d1f40 (Please see Rules & Rewards section). When main-net has launched and Tangram is open-sourced further bug bounties will be defined.
• What is max supply?
183,744,990
• What will be the language of Tangram and its smart contracts?
C#
• When will the white paper be released?
See here for technical introduction: https://tangrams.io/wp-content/uploads/2018/12/Tangram_An_Introduction-2018-12-19-03-27.pdf
• Will Tangram have fees?
No, transactions will be fee-less
• When will smart contract functionality be implemented?
TBC (Better estimate will be provided 3 months after main-net)
• Will there be exchange listings?
This is not a primary focus. We will provide documentation that allows any 3rd party to develop and integrate with Tangram.
• Once main-net is live, how many Tangrams will I receive per [email protected] work unit?
Not yet decided, we are finalising the faucet models and their distribution mechanism which in turn affects the amount received.
No. The [email protected] work unit will calibrate to your CPU.
• Will there be any security audits of the Tangram code base?
Yes. The name of the 3rd party security audit firm will be released once a contract has been signed.
• Why is the GitHub currently private?
Tangram’s codebase is built from scratch. To protect the integrity of the project before main-net and prior to a security audit by a reputable firm. Following main-net there will be discussions and post made to define the properties in which need to be met for open-source.
• Will Tangram be open-source?
Yes.
• How can we be sure of the max supply of Tangram?
The view key of the genesis block will be made available for all once main-net is live.
• Will there be a testnet for Tangram?
Yes, prior to main-net.
• Will there be documentation provided for development on Tangram?
Yes.
• Will there be any incentives for running a node?
There are no monetary incentives for running a node. Will nodes be private? Yes.
• Does Tangram need developer’s once main-net is live?
YES! Come poke around, join the crew, pingpong doesn’t bite.
• How long will the public distribution take?
TBC - Current estimations are 3 month – 8 months.
• Does any of the Tangram team endorse any exchange or OTC trading?
No. You will not find any exchange or OTC channel supported in the Tangram server by team members.
• Is there a roadmap for Tangram?
https://trello.com/b/x02K9WgV
• Why are their mentions of Sneak everywhere in regards to Tangram?
Sneak was the code name of Tangram before the current name was chosen.
• Does Tangram utilize ring signatures in its structure at all?
No.
• Has Tangram underwent any stress test during Alpha-phases? How did it perform?
Current live channels include: Discord: https://discord.gg/GhX6nUC Reddit: https://www.reddit.com/Tangrams/ (not live - pending website) Telegram: https://t.me/Tangrams See the #resource channel in Discord to see all articles and references to Tangram
• How will Tangram achieve consensus?
See here:
https://medium.com/tangram-tgm/breaking-down-tangrams-consensus-mechanism-part-1-ba4857539eb
https://medium.com/tangram-tgm/breaking-down-tangrams-consensus-mechanism-part-2-6d88b435bef7
• Is there a website for Tangram?
https://tangrams.io
• Will there be a rich list for Tangram?
No.
• Does Tangram have a BitcoinTalk thread?
Yes, although pre-announcement. Official announcement will be made once we have prepared main-net. https://bitcointalk.org/index.php?topic=3022248.0
• What environment will be required to run Tangram nodes?
Nodes can run on Windows, Linux, Mac, Raspberry Pi or any Linux distro

##### TESTNET Preparation

Ravencoin was launched on January 3, 2018, as a free, open source platform forked from the Bitcoin codebase. Since that time, Ravencoin has operated as a fully functional network based on the Bitcoin UTXO model. All coins have been fairly mined by a decentralized network of miners using the ASIC-resistant X16r algorithm.
Since the launch, developers have been actively working to add additional asset creation functionality to the Ravencoin core wallet client, as contemplated by Phase 2 (asset support) of the Ravencoin roadmap here.
The Ravencoin community is now able to run the current core Ravencoin client in testnet mode, in order to generate addresses that will be able to receive testnet RVN. On July 30, new asset layer features will be added to the core wallet client for use on Ravencoin’s test network. These features are expected to include additional capabilities that will facilitate the native creation, issuance and transfer of asset tokens. A revised version of the core client software will be made available for download on GitHub. This will allow for rigorous community testing of the native asset layer functionality — including the creation and issuance of testnet assets — in contemplation of the anticipated launch of this functionality on the mainnet in October.
This testnet network will be a completely independent secondary blockchain for testing purposes only, in which all tokens will have no intrinsic value and will not be traded on exchanges. The purpose of a testnet is to test features and functionality before introducing those features and functionality to the main blockchain. It is a playground to experiment and test different features with almost no cost to transact or mine blocks. During this testing phase, the Ravencoin blockchain itself will continue to maintain the same operation and functionality it has today.
To run your current wallet in testnet mode:
1. First shutdown your current full client wallet.
2. Create a shortcut to your raven-qt.exe with this in the target field: C:\Users\Path\to\executable\raven-qt.exe" –testnet
3. Open the wallet by clicking on the shortcut you just made, and let the blockchain sync fully
Don't worry, this will not interfere with your regular Raven wallet, just make sure both wallets are not running at the same time. For those who are technically inclined, running in testnet mode does not overwrite any of the blockchain data or wallet files of Ravencoin’s main network. Instead, it will create a subfolder named testnet3 inside your data folder where all testnet related data and wallets reside. If you would prefer to err on the side of caution, consider running your testnet wallet on a different computer.
There are currently a couple of tools available to assist you with testnet testing.
After this testing period, it is anticipated that the community will consider adoption of the new asset-aware code. Activation will occur through the BIP9 consensus mechanism. More information on the activation process can be found here.

##### My Bitcoin tip-bot is currently undergoing testing for Segwit. Please donate some time to test it.

My reddit bitcoin tip-bot, TipBit is currently utilizing web APIs to check balances, complete transactions, etc... and that is not ideal. Because none of the web APIs had Segwit support, my bot couldn't handle withdrawal to a Segwit wallet, and nothing was done using Segwit internally either.
This didn't seem right... especially with me being a huge advocate for Segwit implementations... it's only right that I learn Bitcoin Node RPC calls and implement them into my own work.
So I updated my bot...
I have finally completed a version of the bot that uses Bitcoin RPC calls to handle everything, including giving all users a Segwit address and a legacy address, and handling all internal storage of funds in a Segwit wallet, and allowing for Segwit wallet withdrawals on top of the legacy withdrawals. Nothing is done with a web API, and the only one I'll be adding back in is the Web API check of the bitcoin price.
I'd like to thoroughly test this new version of the bot before I move it from Testnet to Mainnet, and I need testers for that purpose. I would appreciate it if anyone here could donate a bit of their time to go to the thread about the new bot and utilize the bot in any way you can think of, to make sure it works.
It follows the same rules as the original bot, so you should be able to register, do a sweep deposit, do a normal deposit, check balance, and tip your coins around. If you need free testnet coins to try out the bot, either go to this testnet faucet or just PM me and I'll deposit some into your test bot account once you're registered.
I can answer any questions below.

##### How can lightning network ever scale on a planetary level if in order to use it, we need to embark everyone with an on-chain transaction?

I've tried out lightning network on the bitcoin testnet (i recommend you'd do it too!). I've tried these steps:
Ran it with this lnd config
debuglevel=info bitcoin.active=1 bitcoin.testnet=1 neutrino.active=1 neutrino.connect=btcd0.lightning.computer:18333 autopilot.active=1
• Tried sending some free tBTC from this lightning enabled web wallet.
• It didn't work out, because i had no established channels.
• Funded my segwit wallet from this faucet
• Waited 1 block for confirmation
• Tried establishing a channel to the lightning-network faucet
• Established two channels, one requested from my, one requested from their website
• After i established the channels, the first transaction, the one from htlc.com cleared.
So it seems everyone would need some bitcoin and a channel open to a hub (eventually their own hub) in order to be able to use the lightning network, which otherwise works very fast. This isn't really what i expected, but it's still a major improvement. I'm really awaiting a block size increase next.
Later edit: From the bitcoin.it wiki
Lightning is block-size neutral. It requires one on-chain transaction to open a channel between a hub and a client, and one on-chain transaction to close a channel.[54] In between it can support an unlimited number of transactions between anyone on the Lightning network.
Using the numbers from the Lightning presentation[62], if people open and close a plausible two channels a year, Lightning can support about 52 million users with the current one-megabyte limit—and each user can make an unlimited number of transactions. Currently, assuming people make an average of only two Bitcoin transactions a day, basic Bitcoin can support only 288,000 users.
Presumably, if around 30 million people are using Bitcoin via Lightning so that capacity is called into question, it will not be difficult to find consensus to double the block size to two megabytes and bring user capacity up to 105 million. The same goes for later increases to 200 million (4MB), 400 million (8MB), 800 million (16MB), 1.6 billion (32 MB), 3.2 billion (64MB), and all 7 billion living humans (133MB). In each case, all Lightning network participants get unlimited transactions to the other participants.
For basic Bitcoin to scale to just 2 transactions a day for 7 billion people would require 24-gigabyte blocks.

##### My Bitcoin tip-bot is currently undergoing testing for Segwit. Please donate some time to test it.

My reddit bitcoin tip-bot, TipBit is currently utilizing web APIs to check balances, complete transactions, etc... and that is not ideal. Because none of the web APIs had Segwit support, my bot couldn't handle withdrawal to a Segwit wallet, and nothing was done using Segwit internally either.
This didn't seem right... especially with me being a huge advocate for Segwit implementations... it's only right that I learn Bitcoin Node RPC calls and implement them into my own work.
So I updated my bot...
I have finally completed a version of the bot that uses Bitcoin RPC calls to handle everything, including giving all users a Segwit address and a legacy address, and handling all internal storage of funds in a Segwit wallet, and allowing for Segwit wallet withdrawals on top of the legacy withdrawals. Nothing is done with a web API, and the only one I'll be adding back in is the Web API check of the bitcoin price.
I'd like to thoroughly test this new version of the bot before I move it from Testnet to Mainnet, and I need testers for that purpose. I would appreciate it if anyone here could donate a bit of their time to go to the thread about the new bot and utilize the bot in any way you can think of, to make sure it works.
It follows the same rules as the original bot, so you should be able to register, do a sweep deposit, do a normal deposit, check balance, and tip your coins around. If you need free testnet coins to try out the bot, either go to this testnet faucet or just PM me and I'll deposit some into your test bot account once you're registered.
I can answer any questions below.

##### Metaco unleashes Fiat on Testnet Blockchain ! (Open Asset Protocol)

Hey, I am Nicolas Dorier and as the CTO of Metaco, I am happy to announce the first testnet release of our ambitious goal: bringing traditional currencies to your bitcoin wallet aside of your bitcoins, and with integrated trading!
Metaco is effectively a colored coins broker bringing traditional financial institutions to the Blockchain, and making the market to provide liquidity. In other words, you will be able to trade bitcoins for EUR, USD and other assets without the need for a bank account, directly from your Bitcoin wallet. Trades take place directly on the Blockchain -- we do not own your private keys.
We provide a full fledged trading API for third-party Blockchain apps that need on-blockchain trading features -- either for hedging / investing, or for their own clients. We are effectively a broker / liquidity provider. At this time, we only release a beta version of our trading web app in order to get your feedbacks. It is a typical app relying on our trading API (hoping to open source that !). Please do not hesitate to play with it and contact us with any suggestions you might have.
Once we release our platform to the mainnet, we will announce our partnerships with licensed issuers as well as Bitcoin wallets integrating our trading technology (you will have the joy to fill up KYC/AML forms so you don't launder yourself by mistake ;-) ). Thanks to the Open Assets specification, you'll be able to transfer your assets between compatible wallets like Coinprism as easily as usual bitcoins, and trade them without exposing your private key and without counter-party risk.
We look forward to see you experiment with monopoly-securities trading until we release the mainnet version with actual securities.
Since it is on testnet, you will need some free testnet bitcoin which you can find in several faucet like : http://tpfaucet.appspot.com/ (search bitcoin testnet faucet on google)
n.b.: minor edits

##### My Bitcoin tip-bot is currently undergoing testing for Segwit. Please donate some time to test it.

My reddit bitcoin tip-bot, TipBit is currently utilizing web APIs to check balances, complete transactions, etc... and that is not ideal. Because none of the web APIs had Segwit support, my bot couldn't handle withdrawal to a Segwit wallet, and nothing was done using Segwit internally either.
This didn't seem right... especially with me being a huge advocate for Segwit implementations... it's only right that I learn Bitcoin Node RPC calls and implement them into my own work.
So I updated my bot...
I have finally completed a version of the bot that uses Bitcoin RPC calls to handle everything, including giving all users a Segwit address and a legacy address, and handling all internal storage of funds in a Segwit wallet, and allowing for Segwit wallet withdrawals on top of the legacy withdrawals. Nothing is done with a web API, and the only one I'll be adding back in is the Web API check of the bitcoin price.
I'd like to thoroughly test this new version of the bot before I move it from Testnet to Mainnet, and I need testers for that purpose. If anyone here could donate a bit of their time to go to the thread about the new bot and utilize the bot in any way you can think of, to make sure it works.
It follows the same rules as the original bot, so you should be able to register, do a sweep deposit, do a normal deposit, check balance, and tip your coins around. If you need free testnet coins to try out the bot, either go to this testnet faucet or just PM me and I'll deposit some into your test bot account once you're registered.
I can answer any questions below.

##### New Lightning project: lightningpixels.com

Hi! I'm Malcolm Rose and I run RoseCrypto, an educational site about Bitcoin. I decided to teach myself about the Lightning network by creating a project that uses it. Thus, I've developed a Reddit "Place" clone by modifying the open source code from pxls space. Basically this is an online canvas where you can spend one satoshi via the lightning network to paint one pixel.
I found out that a project like this already exists, but I was halfway through coding this and figured I'd go ahead and finish. There are some differences, of course - check them out for yourself.
Some more notes:
1) This is currently running on testnet, not mainnet. That means you can use something like htlc.me to paint for free for now. Think of it as an incentive to learning a bit about LN. I will be switching over to mainnet in a little while - maybe a week - and writing some articles/tutorials on RoseCrypto with some more information on how to get started.
2) The lightning team's community resources were pretty useful for getting started with this. This page had almost everything I needed to get started, albeit with some minor hiccups that I'm hoping I can help get resolved.
3) This thing is basically held together with sticks and glue. Expect it to be buggy, barebones, and prone to crash for awhile as I work out the kinks. In particular I haven't been able to figure out why lnd just sort of stops accepting transactions after awhile. Maybe roasbeef or somebody more knowledgeable about LN can come to my rescue on this.
4) Invoices are currently set to 500 satoshis by default, but you can send less or more and the system will (should?) pick up on this and credit your account. I did this because htlc.me doesn't seem to be able to support setting your own payment amount yet, and it's the easiest (I think) way to use the LN testnet right now.
Let me know your thoughts, and feel free to contact me here or elsewhere if you have any comments or concerns!

##### Datum

In order to store data on the Datum Network, a Datum Identity (that also creates a keystore) must have been generated. To act in the network sufficient balance of DAT tokens is needed. Use the DAT Faucet service in the testnet to get free DAT for testing, see the example below. After requesting free DATs, you should be able to see your updated account balance in the block explorer /datum or /datumnetwork bitcoin, ethereum, ethtrader, icocrypto, cryptocurrency, btc , altcoin , CryptoMarkets

##### Who wants to open a lightning channel (on testnet) with me??

Downloaded Eclair, looking to open some channels and try out the future!
For anyone who hasn't tried it out yet, download Eclair (I believe it is on Android only). If you need some testnet bitcoins, you can get some (for free) from the faucet here: https://testnet.manu.backend.hamburg/faucet
Node id to request a channel: 0297fe6032ba4e29c3cba23d7bb53cf83d87183442bc3550f6dd7a1888dac96be8

##### Volunteers for testnet testing of 0.2.0 version

There's a new protocol (technical description here) with a few changes. The main change is making commitments to utxos using proof of discrete log equivalence as described e.g. here and in other places. There are a few other changes, the most obvious being using multiple IRC servers simultaneously.
If you feel like helping out you could do so considerably by running a yield generator bot in the testing pit, so we can test out different scenarios (including the snooping on utxos scenario which is the main motivation for the upgrade).
If you're going to do this, keep an eye on the updates and update when the code changes. You might want to hang out in our IRC channel #joinmarket on freenode too.
Steps:
(a) Optional: start a testnet bitcoind daemon - otherwise, just use blockr.
(b) Clone the 0.2.0 branch from the joinmarket repo.
(c) Choose IRC servers. I am currently running my bots on Cgan (the current joinmarket IRC server) and irc.rizon.net and chat.freenode.net. Only the first of those 3 supports Tor (but this is testnet of course, up to you). More bots across multiple servers will help the tests. If anyone can find another Tor-supporting server that works, please let us know.
(d) If you have an existing joinmarket.cfg file in the place you've installed this, please remove it and start a bot to recreate a default version. There are some new settings in POLICY that are needed, and for now please just leave them at default. AND: don't forget to set the network to testnet !
(e) To reflect your IRC server choices above, you need to edit the MESSAGING section. For example, for 3 servers I have:
host = irc.cyberguerrilla.org, chat.freenode.net, irc.rizon.net channel = joinmarket-pit2, joinmarket-pit2, joinmarket-pit2 port = 6697, 6697, 6697 usessl = true, true, true socks5 = false, false, false socks5_host = localhost, localhost, localhost socks5_port = 9150, 9150, 9150
(Obviously this comma separated style is clunky, there are obscure/uninteresting reasons there isn't a better way of setting it yet).
Note the channel name is joinmarket-pit2 which will translate to a channel on the actual server of #joinmarket-pit2-test (same for each IRC server of course).
(f) to run a yg-bot you'll need testnet coins of course. You can use the faucet https://kuttler.eu/en/bitcoin/btc/faucet/ (uses JM under the hood!) or http://tpfaucet.appspot.com/ , or hit us up on IRC for some. For setting up a wallet, testnet is (can be) different on joinmarket. You can just use a "brainwallet" style phrase like this: python wallet-tool.py thisismydumbpassword display, which will show all the coins stored in the bip32 wallet generated using the hash of that phrase as the master secret. No wallet file is involved this way, you can extract an address from that list and pay in to it.
(g) Run any yg-algo you like. Have it as long-running as is feasible, but note the point about "updates" above. Feel free to try out a sendpayment if you like too, although I don't mind if it's just me doing that for now.
There are 4 bots in the pit from 2 people at the moment. I'd like to get that up to 10-15 ideally for good realistic testing scenarios.
Thanks!

The following post by codedaway is being replicated because the post has been silently removed.
The original post can be found(in censored form) at this link:
The original post's content was as follows:
Hi Everyone,
I'm trying to create a post that can be stickied with regards to the Lightning Network. This post should be used to provide as many links to as many resources as organized as possible. This is obviously a large task and I've tried to start it in hopes that I can crowdsource this in the comments to keep adding content to this post. Feel free to recommend any additions but please provide sources for your information. Also please correct myself or anything that appears up here that seems incorrect and I'll do my best to edit quickly.

# What is the Lightning Network? ?

## Lightning implementations:

• LND - Lightning Network Daemon (Golang)
• eclair - A Scala implementation of the Lightning Network (Scala)
• lit - Lightning Network node software (Golang)
• c-lightning - A Lightning Network implementation in C
• lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
• lightning-integration - Lightning Integration Testing Framework
• ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]

## IRC

• #lightning-dev (on Freenode) - Lightning protocol development
• #lnd - Lightning only version of #bitcoin-commits

• #li...