If you have truly no idea how to do any of this, or you're having problems:
Email me at dev@fitti.io or shoot me a message on Telegram, Keybase, or Twitter! (I take longer to notice messages on Twitter)
Want to accept Bitcoin donations on Twitch? This will allow you to not only accept Bitcoin, but also have those donations show up in your Streamlabs alerts!
And the best part: While it supports on-chain payments, it's lightning-first!
To enable this, LNbits is utilized, for which I wrote a special extension.
It's open source all the way down!
For this to work, you need to have git, python, and its virtualenv module installed.
This will only work on Linux, and should preferably run on an always-on machine.
You can run this on Windows, using WSL, and run it on your streaming PC while you're live.
When using ngrok, keep in mind that your URL will change every time you restart it.
If you want to run it on Windows via WSL, I recommend installing Ubuntu, and running sudo apt update ; sudo apt upgrade ; sudo apt install python3-venv git.
- Clone the repo and
cdinto it (git clone https://github.com/Fittiboy/bitcoin-on-twitch ; cd bitcoin-on-twitch) - Get an lntxbot wallet.
If you have a different backend that you would like to use, you can just hit enter without typing anything when you are later asked for the lntxbot API key.
Keep in mind that you will have to manually set the backend inlnbits/.env, as explained here - Get an API key from lntxbot by messaging it
/api full. - Run
python initial_setup.pyand follow the instructions. When it asks whether or not you want to use "ngrok," you have to make a decision: The ngrok extension in LNbits will allow you to host it publicly and for free.
You can read the "How it works" section here for more information. If you want to use this, simply type "y" and hit enter, otherwise "n".
If you need help with web hosting, you can send me an email at dev@fitti.io! I might be able to help you out. - You should now be able to run
. ./start_lnbits.sh, which should launch
LNbits in the background, making it reachable at http://localhost:5000/
Issues will be recorded in a file calledlnbits.log - In LNbits, create a wallet.
This should bring you to a url that ends in this format :/wallet?usr=XXXXXXXXXX&wal=YYYYYYYYYYYYY.
Keep the XXXX and YYYY (yours will look like random text and numbers) secret, but copy the FULL URL somewhere safe.
Visiting this URL is essentially how you log in to LNbits, and so anyone who knows this URL, or the XXXX and YYYY could access your wallet.
For added security, you can move your funds to a different wallet after every stream! - Right now, anyone with access to the URL could create new wallets and use your LNbits. To prevent this, do the following:
copy just the XXXXXXXXXX from the url (usr=XXXXXXXXXX&wal=...) and run
python whitelist_user.py. Paste your user ID when prompted.
Now you can restart LNbits (. ./kill_lnbits.sh ; . ./start_lnbits.sh), and you should now get an error when trying to create a new login! - Follow the extension guide.
- When you publicly host this, go ahead and open your wallet through your public URL (for example, the URL shown in the ngrok extension).
To access your wallet on this public URL, simply add the/wallet?usr=XXXXXXXXXX&wal=YYYYYYYYYYYYYpart from the URL you saved.
Then, navigate to the Stream Alerts extension again and there you can get the donation page link, as described in the guide in the previous step.
You can try sending yourself a test donation afterwards.
If everything worked, you should see the donation pop up here (remember to refresh).
If something went wrong, please submit an issue or send me an email at dev@fitti.io!
To stop LNbits (and ngrok if it's running), run . ./kill_lnbits.sh, but be aware that this will kill all processes that have "lnbits" and "ngrok" in their name.
If for whatever reason you have other processes running that have those names in them, kill LNbits (and potentially ngrok) manually.
I want this to be a project that allows streamers on Twitch to integrate Bitcoin donations
into their on-stream alerts with as little setup as possible.
Things you can help with:
- Clarifying steps in the guide, or linking to/writing more detailed guides to get non-technical users up to speed
- Writing scripts that would make this run on Windows (in case a streamer opts for self-hosting on Windows)
I'm not at all used to maintaining projects with other contributors, so I don't know, just follow the
common etiquette or whatever if you wanna help :)
I would especially appreciate help with just making things cleaner and more efficient (I'm not a professional),
as well as potentially integrating services other than Streamlabs (not sure if there are any
that are widely used like Streamlabs and actually have an API for this).