So far in August, I have managed to setup / do:

✅ Bitcoin Node
✅ Bitcoin Transactions (In / Out)
✅ Lightning Node
✅ Lightning Transactions (In / Out)

Next step is to figure out how fees work in Lightning. C-lightning implementation not really helpful so far, I will keep digging or try LND.

Lightning incoming payment (from Yalls) achieved. The problem before was that I had no capacity to receive payment. One needs to either spend first or to have an incoming channel. Thanks @orionwl for providing the latter and also helping fix some setup issues.

It got traction quicker than I expected so I asked for the equivalent of a $1 as pay out. I had to learn to create an invoice. Easy apart for the mSatoshis part which increases mental calculations especially when the rest of the setup in c-lightning is in Satoshis. Got the invoice created and pasted it to Yalls but payment couldn't get through. Error message not helpful. I think it's probably because of either no incoming channels to my node or no route. I will keep trying.

Next step was to try and receive a ⚡ payment. Yalls to the rescue again. I wrote an article there ( mainnet.yalls.org/articles/97d ) and then waited to get some traction so I can ask for a pay out of the rewards.

After channels were in place, I decided to make my first ⚡ payments and went to Alex Bosworth's mainnet.yalls.org/ to read a couple of articles and pay for them. It was almost instant despite the fact that my node was not directly to Yalls and very lightly connected overall.

@cryptonomicon so, everything considered, the full descriptor for your node is:
023[email protected]pzfsmtyqfgjj3j5wyzqruaim3qqrlccbiju34qoek6l77ydmiiupmmyd.onion:9737

First steps with Lightning was to use 1ml.com/ to find some nodes to connect to and then I opened a couple of channels. No problems initially. One channel though disappeared (I think) and I experienced the brilliance of HTLC (?) as I got the BTC back on-chain after a day or something.

I hadn't realised Node id is also needed for the channel opening so here it is: 0232a7544f1f966fbaa3f486d1dd9fae73c572fe715f63e3bc9fe4c437d0a625de

For Lightning on Raspberry Pi, I have gone with c-lightning, following @meeDamian's post medium.com/@meeDamian/c-lightn . All up and running now, but I am light on incoming channels. Any connections welcome :) pzfsmtyqfgjj3j5wyzqruaim3qqrlccbiju34qoek6l77ydmiiupmmyd.onion:9735

Bitcoin node up and running and now on Tor as well. Next step is Lightning.

@meeDamian I think there's an error on a line of code on your Bitcoin Through Tor On RPB3 post on Medium. "gpg --keyserver keys.gnupg.net --recv A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89" should be "gpg --keyserver keys.gnupg.net --recv 886DDD89"

@cryptonomicon @meeDamian
Side loading is a must, or you'll wait about a week.

Limit your dbcache once synced. I use 50 (you can use considerably less.)

I like using a large mempool because I want to relay all valid transactions.

Just put the blocks directory on your external drive.

Give chainstate it's own dedicated USB.

Putting swap on a dedicated USB helps speed as well.

Just what I've learned.

I've got a one shot script to do it all, need to update it and comment it.

🎤 Listening to @vortex on What Bitcoin Did podcast. He is very genuine and excited which is refreshing. Even more so at a play speed of 1.6x

Syncing a node was what really made me understand the value of not increasing the block size limit. I was on that side of the argument after reading a lot about the history and the debates but it hadn't really clicked till I set up my node.

Beginning of August, I have a Raspberry Pi lying around so I buy a 1TB external HDD and get started on setting up a Bitcoin node. Best advice was to sync on the laptop (took a couple of weeks) and then move the HDD to the Pi. I follow the tutorial from @meeDamian at medium.com/@meeDamian/bitcoin-

Thanks for the attention all, this was a quick ⏩ intro on my side, catching you up on my short (for now) journey to embracing and understanding Bitcoin. I will now revert to 1x life mode (aka real-time)

It's now August, The Bitcoin Standard book (goodreads.com/book/show/364485) has arrived, the $BTC price is going up and down (but i am checking Blockfolio only half a dozen times a day), and I have enrolled to another course: Bitcoin and Cryptocurrency Technologies (coursera.org/learn/cryptocurre)

I can now say 'crypto means cryptography' and actually know what cryptography means!

Back to educating myself, I need to take it to the next level. Coursera is the solution, back to the founding blocks (pun intended): Cryptography I (coursera.org/learn/crypto).

Decided to go with hardware wallet (Ledger Nano S) and a seed phrase stored in USBs encrypted with Veracrypt and stored on different locations to the wallet. Still need to think and implement multi-sig as an additional layer. Probably need a new wallet for that. Paying close attention to @nvk's efforts with Coldcard wallet.

Show more
Bitcoin Mastodon

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!