forked from raspiblitz/raspiblitz
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dev rootz to Dev nyx #9
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Just a mention referring to the issue so that newbies don't waist time with this and get disappointed.
Little note warning that Channels Autopilot triggers a reboot which can be confusing for newbies and frustrating for demos.
I feel the update makes it clearer, feel free to accept/reject whichever way you think is best.
Changed waist of time to waste of time in line 528
partion -> partition
* Fix Typos * Fix Typos * Update blitz.copyblockchain.sh
* build_sdcard.sh: prepare for the 64bit RaspberryOS * build_sdcard: don't ping and trust microsoft * build_sdcard: make sure the pi user is present * build_sdcard: add the archive.raspberrypi.org repo * build: improve recognition of the base image * build: don't stop at installing dependencies * build: fix locales on all raspi images
As discussed in: #1993 (comment)
When the mempool fills up to around 500MB, this causes the mempool.space backend to crash on RPI due to OOM. Additionally, raising this above 300MB on a local RPI node arguably isn't a good idea anyway, because: * If you have a 512MB mempool and all your peers have 300MB, you'll broadcast transactions that fit in your mempool but are rejected by all of your peers * If you connect an SPV wallet to your node, your wallet will think the TX is "in the mempool" despite actually being purged from the entire Bitcoin P2P network, and never attempt to rebroadcast the purged TX * In any case, the RPI has very limited RAM, so no point in wasting RAM on having such a large sized mempool for bitcoind
* adding spacing line * prepare v1.7RC3 * fix lnbits macaroon write after reset * add IP2Tor renew info * fixing info * remove debug info * #2157 LNbits needs https for local * more info * reboot on macaroon reset * fix blocking LIT install * set correct fonts * set font for lcd * #2198 add connect Info * fix syntax * fix text layout * layout text * fix text layout * more install info * fix text layout * text layout * text layout * fix restart lnd * force lnd RPC/REST standard & open on boot * #2198 fix fully noded connection * #2198 deactivate Zap-Android from menu
* new path of "vcgencmd" at raspiblitz v1.7.0RC2 * whitespaces + rename raspiblitz_ip_info -> ipinfo * add mempool info via bitcoincli Co-authored-by: Patrick Scheich <patrick.scheich@syscovery.de>
* unlock LND after Bitcoin Core install if ready * bitcoin.update: improve output and comments
This is important, normally nginx fails and this is not shown.
please correct this before v1.7 @rootzoll
Give some alternatives if the mentioned display is sold out on Amazon
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.