Data directory - Bitcoin Wiki

Bitcoin Wallet

Everything about bitcoin wallets.
[link]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

How to run Bitcoin Core 0.20.0 on Ubuntu Server 20.04 LTS using a Raspberry Pi 4 (or Virtual Machine)

I was helping someone on twitter with this so I figured I'd share the information here as well so that other people would have an easier time than I did.
I'm going to explain how to do this setup on a Raspberry Pi, but note that this should work on a VM as well. You can also set up and run the node headless this way, but I will be explaining how to set up the node using a monitor that you can then later disconnect and access remotely once everything is setup.
Hardware:
-Raspberry Pi 4 (2GB RAM minimum) preferably 4GB RAM -Raspberry Pi 4 Heatsinks -Raspberry Pi 4 case -Micro HDMI cable -USB-C power cable and wall adapter -Monitor -Keyboard and mouse -Ethernet cable (Optional) -16GB or larger microSD card -500GB or larger external hard drive (SSD or portable)
Node Requirements: -50 KBps upload internet speeds (Most people should have this) -Unlimited or high data cap internet download/upload service -6 hours or longer per day dedicated run time
Okay, once you have the hardware its time to get started!
The first thing you'll need to do is install the Raspberry Pi imager, this is how we're going to install Ubuntu onto our Raspberry Pi. After your download and install finishes, open the imager.
  1. Click the "choose OS" box and from the list select Ubuntu, then select Ubuntu Server 20.04 LTS (Raspberry Pi 2/3/4).
  2. Insert your microSD card to your computer directly or via a USB converter. Click "choose SD card" and select your inserted microSD card.
  3. Click "Write" and wait for the imager to finish flashing the OS onto your card
When it is done, remove the SD card and reinsert it to access the files installed. You can choose the overclock the Raspberry Pi by editing the config file. To connect to the Raspberry Pi remotely, you'll need to create an SSH file. If you're on windows this is pretty easy. In the File Explorer, highlight the address bar at the top, erase the text and type cmd, press enter and the Command Prompt will pop up. Type the following:
echo\ssh
This will create an SSH file in your SD directory so that you can remote access the Rasberry Pi later. Now you can go ahead and eject the SD card from your computer.
Now we can set up the Raspberry Pi
Go ahead and connect all your peripherals to your Raspberry Pi, insert the microSD, and connect it to power to turn it on. Give it a moment to boot up, then when prompted enter "ubuntu" for the password. It will make you change the password. Afterward, it will print a bunch of information to the screen, write down the IPv4 address, this is the IP address you'll use to remote access the Raspberry Pi. Now, at any time you can remote access your Raspberry Pi by entering a terminal on another PC in your network and typing:
ssh [email protected](your IP address)
The next step is to install a desktop. There are plenty to choose from so feel free to use a different one than what I use, you can also choose to ignore this and to just work from in the terminal from this point forward.
You need to update all the repositories so type: (Note you'll either have to be connected by ethernet or have edited the network-config file to setup your wifi in advance)
sudo apt-get update
Once it's done updating type the following to upgrade your system:
sudo apt-get upgrade
Now that you're up-to-date, you can install the desktop using the command:
sudo apt-get install ubuntu-gnome-desktop
This will take a while to download and install so just sit back and let it do its thing. Once it's done downloading, restart your Raspberry Pi and log in with the password you changed earlier. Your first boot may take a while so just be patient, don't freak out if you see a single purple square in the center of the screen while it's loading. You should now have the Ubuntu desktop ready to go and now it's on to installing Bitcoin Core!
Installing Bitcoin Core 0.20.0
Since we're running Ubuntu Server 20.04 LTS, it should come preinstalled with the Snap Store. This makes installing apps very easy and works similar to pip install in Python. Simply open your terminal and type:
sudo snap install bitcoin-core
This will install Bitcoin Core into your Snap folder and will add the application to your system. Unfortunately, there are still a few steps left before we can begin downloading the blockchain. By default, Bitcoin Core doesn't have the removable-media Plug connected to the Socket. You can view this by typing:
snap connections bitcoin-core
This means when you try installing everything onto your external hard drive, Bitcoin Core won't be able to identify it or write to it even when passed the directory path. To fix this first locate your Snap folder, make a copy of the bitcoin-core folder inside, and paste it into your external drive.
NOTE: You must make a copy, you can't just move the snap file to the external drive.
Now, you can connect the removable-media Plug to the Socket by typing:
sudo snap connect bitcoin-core:removable-media :removable-media
This gives you the read/write permissions necessary to access the /media path. Finally, you can now launch Bitcoin Core and select "use a custom directory path" when prompted. Highlight the current directory path and replace it with the path to your external hard drive, it should look something like this:
/media/(external drive)/bitcoin-core/common/.bitcoin
This is why we had to make a copy of the bitcoin-core folder to the external drive earlier, the Bitcoin Core application will create the new data directory through ".bitcoin". Hit "Okay" and the application will begin synchronizing with the network! Once the synchronization is finished your very own node will be up and running!
EDIT: (08/01/2020) Bitcoin Core 0.20.01 has been released, I will update the tutorial soon with how to run the latest release.
submitted by Noblefire_62 to Bitcoin [link] [comments]

Problem with the first Initialization of my LN node, dial tcp my-external-ip:9735: connect: connection timed out

Background
I was following 402 Payment Required's LN video over here (https://www.youtube.com/watch?v=q0siLF9zmWo) and everything was good so far, until the moment of the first Initialization of my LN node, I got an (dial tcp my-external-ip:9735: connect: connection timed out) error. Your environment
I was starting the Initialization by the following way
lnd --externalip=X.X.X.X
And I've my lnd configuration file with the following attributes
alias= debuglevel=debug bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind
I created the file (before) I started the Initialization.
version of lnd: I don't know, I guess it's the latest version. which operating system (uname -a on *Nix): Ubuntu 18.04 version of btcd, bitcoind, or other backend: bitcoind 0.19.1 any other relevant environment details: My Ubuntu is running on a VM machine with a (bridged) internet connection 
Steps to reproduce
I don't know how to reproduce the problem but here is a log with my issue
2020-08-14 20:33:16.008 [INF] BTCN: Server listening on [::]:9735
2020-08-14 20:33:16.009 [INF] SRVR: Initializing peer network bootstrappers!
2020-08-14 20:33:16.009 [INF] SRVR: Creating DNS peer bootstrapper with seeds: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:16.010 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:16.022 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:16.426 [INF] DISC: Obtained 1 addrs to bootstrap network with
2020-08-14 20:33:19.428 [DBG] SRVR: Waiting 2s before trying to locate bootstrap peers (attempt #1)
2020-08-14 20:33:21.428 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:21.463 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:21.464 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:21.464 [DBG] SRVR: Waiting 4s before trying to locate bootstrap peers (attempt #2)
2020-08-14 20:33:25.464 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:25.504 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:25.504 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:25.504 [DBG] SRVR: Waiting 8s before trying to locate bootstrap peers (attempt #3)
2020-08-14 20:33:33.504 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:33.539 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:33.539 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:33.539 [DBG] SRVR: Waiting 16s before trying to locate bootstrap peers (attempt #4)
2020-08-14 20:33:49.540 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:49.540 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:49.578 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:49.578 [DBG] SRVR: Waiting 32s before trying to locate bootstrap peers (attempt #5)
2020-08-14 20:34:21.579 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:34:21.580 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:34:21.735 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:34:21.735 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #6)
2020-08-14 20:35:21.736 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:35:21.736 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:35:22.280 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:35:22.280 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #7)
2020-08-14 20:35:27.316 [ERR] SRVR: Unable to connect to ##################################################################@my-external-ip:9735: dial tcp my-external-ip:9735: connect: connection timed out
2020-08-14 20:36:22.280 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:36:22.347 [INF] CRTR: Pruning channel graph using block 0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57 (height=643720)
2020-08-14 20:36:22.349 [INF] CRTR: Block 0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57 (height=643720) closed 0 channels
2020-08-14 20:36:22.461 [DBG] NTFN: Filtering 3178 txns for 0 spend requests at height 643720
2020-08-14 20:36:22.523 [INF] NTFN: New block: height=643720, sha=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57
2020-08-14 20:36:22.523 [DBG] SWPR: New block: height=643720, sha=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57
2020-08-14 20:36:22.523 [INF] UTXN: Attempting to graduate height=643720: num_kids=0, num_babies=0
2020-08-14 20:36:22.524 [DBG] DISC: New block: height=643720, hash=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57
2020-08-14 20:36:22.757 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:36:22.758 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:36:22.758 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #8)
Expected behavior
I expected the Initialization would work normally without any issues.
Actual behavior
The first Initialization of the LN node didn't happen, stuck in the loop of trying to locate bootstrap peers
N.B. I'm a unix beginner, so please bare with me.
submitted by scottcarter2020 to Bitcoin [link] [comments]

subs

sites

http://redditlist.com/nsfw
https://www.reddit.com//SomeRandomReddit/wiki/sickandweirdsubreddits
https://www.reddit.com/NSFW411/wiki/index
https://redditgrid.com/[sub]
https://reddpics.com/[sub]
https://redditp.com/[sub]

subs

/2busty2hide
/2healthbars
/2me4meirl
/2meirl4meirl
/3Dprinting
/3dspiracy
/4chan
/4kmonitors
/4PanelCringe
/11foot8
/13or30
/AAMasterRace
/ABC_PORN
/ABoringDystopia
/AbruptChaos
/absolutechonkers
/absoluteunit
/AbsoluteUnits
/AccidentalComedy
/AccidentalRacism
/AccidentalRenaissance
/AccidentalSlapStick
/accidentalswastika
/ActualFreakouts
/actualsubreddits
/adorableporn
/AdPorn
/AdultEducation
/AdultsAreFuckinStupid
/AdviceAnimals
/AfterTheShot
/agedlikemilk
/AirplaneFood
/AirSwimming
/ALLTHEANIMALS
/ALSScan
/AltBlonde
/AmateurTeen_Porn
/Amd
/AmericanGifs
/amibeingdetained
/amplifiers
/Amry
/Anal_Babes
/AnalHD
/analog
/AnalVidz
/Androgynoushotties
/angryconfusion
/Angryupvote
/AnimalbeingEngineers
/AnimalsBeingAnimals
/AnimalsBeingBros
/AnimalsBeingDerps
/AnimalsBeingJerks
/AnimalsBeingLoveable
/AnimalsBeingPerfect
/animalsdoingstuff
/AnimalsMonching
/AnimalsWithoutNecks
/AnimalTextGifs
/animation
/Animemes
/announcements
/ANormalDayInAmerica
/ANormalDayInRussia
/antiassholedesign
/Anticonsumption
/antifeminists
/antiMLM
/AquaticAsFuck
/archmemes
/arduino
/ArduinoProjects
/AreTheStraightsOK
/AsABlackMan
/AsianCuties
/asianpeoplegifs
/AskElectronics
/AskEngineers
/AssBootyButt
/assholedesign
/AssPotatoCucumberDog
/ATAAE
/ATBGE
/AteTheOnion
/Audiomemes
/AwesomeAss
/awfuleverything
/awfuleyebrows
/aww
/awwtf
/Awww
/Bad_Cop_No_Donut
/badassanimals
/badgunanatomy
/BadMensAnatomy
/badUIbattles
/badwomensanatomy
/BannerIT
/bash
/BeagleBone
/BeAmazed
/BeautifulHardware
/BeforeNAfterAdoption
/bertstrips
/BestCamSluts
/BestSnapchatNudes
/bestxxxgifs
/BetterEveryLoop
/beyondwholesome
/bigfan
/BiggerThanYouExpected
/BigTitsButClothed
/Bitcoin
/blackhat
/blackmagicfuckery
/BlackOps
/blackpeoplegifs
/Blep
/blop
/blunderyears
/blursedimages
/BollywoodRealism
/BoneAppleTea
/bonehurtingjuice
/BonerAlert
/bongbeauty
/Bonsai
/BonsaiPorn
/books
/Boomerhumour
/booty_queens
/bootyshorts
/Bossfight
/Botchedsurgeries
/bptcg
/BrandNewSentence
/Break_Yo_Dick_Thick
/breathinginformation
/BreedingMaterial
/BrokeNotCrappy
/brushybrushy
/BuffFluff
/buildapc
/bulksupplements
/Buttcoin
/ButterflyWings
/C_Programming
/cableadvice
/cablefail
/CableManagement
/cableporn
/cade
/calculators
/CamSluts
/capitalism_in_decay
/carbage
/CasualJiggles
/CatastrophicFailure
/catpranks
/CatsAreAssholes
/CatsareFake
/CatSlaps
/CatsStandingUp
/CatTaps
/celebnsfw
/celebritymouths
/Celebs
/CentOS
/chadsriseup
/Chandler_Bailey
/ChavGirls
/chicas
/China_Flu
/chinesekitty
/Chinesium
/ChipCommunity
/Chonkers
/ChoosingBeggars
/circlebroke2
/ClassicInternetPorn
/cleanhandgang
/cleavage
/coding
/Coffee
/college
/combinedgifs
/ComedyCemetery
/comedyheaven
/comedyhomicide
/Commahorror
/CommentRemovalChecker
/compsci
/CompTIA
/ComputerEngineering
/computerscience
/computersciencehub
/ComputerSecurity
/confidentlyincorrect
/ConfusedBoners
/confusing_perspective
/ConfusingGravity
/consolerepair
/conspiracy
/conspiracyundone
/coolgithubprojects
/CoolPornPicks
/corgi
/Coronavirus
/CoronaVirus_2019_nCoV
/CoronavirusMa
/CoronavirusUS
/CorporateFacepalm
/cosplaygirls
/CouldveBeenWorse
/COVID19
/CovIdiots
/Cplusplus
/cpp
/cpp_questions
/CrackSupport
/CrapperDesign
/CrappyArt
/CrappyDesign
/crappyoffbrands
/CrazyIdeas
/crazystairs
/creepyasterisks
/creepydesign
/creepyPMs
/cringe
/cringepics
/Cringetopia
/cringtopia
/cromch
/crossfail
/CrossfitGirls
/crypto
/cryptography
/csbooks
/CuddlePuddle
/CuntCompanies
/curiousboners
/curledfeetsies
/cursedimages
/cute
/CuteButHorrifying
/Cuties4U
/cybersecurity
/damncute
/Damnthatsinteresting
/dancingdoggos
/dangerousdesign
/DangleAndJingle
/dankmemes
/darkmoney
/dashcamgifs
/data_irl
/DataHoarder
/dataisbeautiful
/dataismisleading
/dataisoffensive
/dataisugly
/datgap
/Death_By_SnuSnu
/debianinrandomplaces
/Deep_Anal
/DeepFriedMemes
/DeepIntoYouTube
/DeerAreFuckingStupid
/Defcon
/DeformedStarfish
/delusionalartists
/DemocraticSocialism
/DesignPorn
/DesirePath
/DesirePaths
/desnudas
/devkit
/didnteventry
/DidntKnowIWantedThat
/didntspecifyifhe
/digitalpiracy
/dislikedreplyingwith
/DIY
/diyelectronics
/DIYGear
/diyguitar
/diykits
/diypedals
/DnDIY
/Dogberg
/dogelore
/doggifs
/doggohate
/Doggystyle_NSFW
/DogReactions
/dogsinbooties
/DogSmiles
/dogssittinglikehumans
/dogswithjobs
/DoMyHomework
/dontdeadopeninside
/DontFundMe
/donthelpjustfilm
/dontputyourdickinthat
/douchey
/drumpfisfinished
/DSPDiscussion
/DWASBPEIF
/earwax
/eatsandwiches
/ECE
/ECEComponentExchange
/EDC
/EDCexchange
/edtech
/education
/eebooks
/ElectricalEngineering
/electricians
/electronics
/ElectronicsList
/emacs
/emergencymedicine
/engineering
/EngineeringPorn
/EngineeringStudents
/enginerdery
/engrish
/ENLIGHTENEDCENTRISM
/EnoughMuskSpam
/EntitledBitch
/entitledparents
/Entrepreneur
/eroticauthors
/Ersties
/esp32
/etymology
/everyfuckingthread
/excgarated
/excusememrwalrus
/Exonumia
/ExpectationVsReality
/explainlikeimfive
/EyeBelch
/Eyebleach
/facepalm
/FacialFun
/facingtheirparenting
/fakealbumcovers
/fakehistoryporn
/FanCentroBabes
/fatsquirrelhate
/Fedora
/Feic
/FellowKids
/FemaleDatingStrategy
/feminineboys
/Feminism
/FeminismStopsWhen
/ff7
/FFVIIRemake
/FieldNuts
/FiftyFifty
/Fighters
/fightinggamesvideos
/fightporn
/fightsticks
/FilthyLatinas
/FinalFantasy
/FinalFantasyVII
/financecirclejerk
/findareddit
/firefox
/Fitness
/flatpak
/Flipping
/florida
/FloridaMan
/FondantHate
/foodscam
/forbiddensnacks
/ForgottenNews
/forwardsfromgrandma
/ForwardsFromKlandma
/FoundTheAmerican
/foundthemobileuser
/fountainpens
/FPGA
/FreeEBOOKS
/freenas
/FreePopcorn
/friendlyarchitecture
/Frugal_Jerk
/Fuckgnome
/FuckStuartLittle
/fuckthesepeople
/FuckYouKaren
/FunBodybuilding
/functionalprints
/funny
/FunnyandSad
/Futurology
/GameDeals
/GamerGhazi
/gamesandtheory
/gaming
/gardening
/gatekeeping
/generalizedtools
/genewilder
/gentlemanboners
/gifs
/gifsthatendtoosoon
/gifsthatkeepongiving
/GifsThatStartTooLate
/git
/github
/gnome
/GnuPG
/GoCommitDie
/GoneMildPlus
/gonewilder
/gonwild
/goodboye
/GoodNsfwMorning
/GreenAndPleasant
/GuiltyDogs
/Guitar
/guitarcirclejerk
/guitarmod
/guitarpedals
/guitarpedalsjerk
/GymFails
/hackernews
/hacking
/HailCorporate
/hailhortler
/hairybuns
/hapas
/happygirls
/HappyWoofGifs
/hardcoreaww
/hats
/HaveWeMet
/HDsexvideos
/HeadlinesYouReadTwice
/HelicopterAddict
/HerCockHisAss
/heythatsneat
/highereducation
/HistoryMemes
/HitBoxPorn
/hitmanimals
/hittableFaces
/hmm
/hmmm
/hmmmgifs
/hoggit
/holdmybraincells
/holdmycosmo
/holdmyfeedingtube
/holdmyfries
/holdmyredbull
/HolUp
/homeautomation
/homedefense
/homelab
/HomemadeTools
/HomeworkHelp
/HostileArchitecture
/HostileBenches
/HotButts
/hottestgals
/howto
/HugePussy
/HumansBeingBros
/humblebrag
/humblebundles
/HydroHomies
/Hypocrisy
/i3wm
/iamatotalpieceofshit
/iamverybadass
/iamverysmart
/IDecidetheContext
/IdiotsFightingThings
/IdiotsInCars
/idiotsinhouses
/IdiotsNearlyDying
/Idiotswithguns
/idontunderstandsatire
/IFC
/ihadastroke
/ihavesex
/iiiiiiitttttttttttt
/im14andthisisdeep
/im14andthisiswoooosh
/imaginarygatekeeping
/Imapieceofshit
/Impracticaltools
/Impressiveasfuck
/imsorryjon
/InclusiveOr
/Incorgnito
/IncreasinglyVerbose
/indianpeoplefacebook
/inductionheaters
/InfowarriorRides
/Infuriating
/inoticed
/insaneparents
/InsanePeopleQuora
/Instagramreality
/instant_regret
/instantbarbarians
/instantkarma
/Instantregret
/INTELLECTUALPROPERTY
/interesting
/interestingasfuck
/internetofshit
/InternetStars
/ISO8601
/ITComputerSecurity
/itsaunixsystem
/JerkOffToCelebs
/jesuschristreddit
/JizzedToThis
/JobDoneBoss
/Journaling
/Julia
/justbootlickerthings
/JustBootThings
/justdependathings
/justforsocialmedia
/Justfuckmyshitup
/JustHotWomen
/JusticeServed
/JustLearnedTheFWord
/justneckbeardthings
/Justrolledintotheshop
/JustStemThings
/juxtaposition
/KamikazeByWords
/kde
/keming
/KenM
/KerbalSpaceProgram
/KidsAreFuckingSmart
/KidsAreFuckingStupid
/killthecameraman
/KittyPupperLove
/KneelingInBikinis
/KotakuInAction
/Kubuntu
/KylieRichardsXXX
/LadiesInBoyshorts
/LadyCocks
/LateStageCapitalism
/LaTeX
/latinas
/lawsuitdesign
/LearnEngineering
/learnlinux
/learnmath
/learnprogramming
/learnpython
/LeatherClassifieds
/lectures
/lefthandpoetry
/LeftHanging
/LegalTeens
/legs
/legsSpread
/Libertarian
/lifehacks
/Light_Fairy
/likeus
/LilGrabbies
/linux
/linux_cucks
/linux4noobs
/linuxadmin
/linuxaudio
/LinuxCirclejerk
/linuxmasterrace
/linuxmemes
/linuxmint
/linuxquestions
/LiveOverflow
/LivestreamFail
/LLLikeAGlove
/lmrcirclejerk
/lockpicking
/Locksmith
/lostredditors
/Loudgifs
/LoveWithFitness
/lowcostplay
/Luthier
/macbookpro
/MachineLuck
/MachinePorn
/MadeMeSmile
/madlads
/MakeMeSuffer
/MaliciousCompliance
/mallninjashit
/MandelaEffect
/ManjaroLinux
/masterhacker
/math
/mathbooks
/matheducation
/MathematicsMemes
/mathmemes
/matlab
/maxon3d00
/maybemaybemaybe
/maybemaybeoriginal
/McDonaldsEmployees
/me_irl
/meatcrayon
/mechanicalgifs
/MechanicalKeyboards
/mechanicalpencils
/mechmarket
/media
/MedicalGore
/medicase
/medicine
/medizzy
/meirl
/MemeGraveyard
/memes
/MEOW_IRL
/mercurial
/MetalZone
/MeTooThanks
/mexico
/michaelbaygifs
/microcomputing
/microgrowery
/mildlyinfuriating
/mildlyinteresting
/mildlypenis
/mildlyterrifying
/mildyinfuriating
/MilitaryPorn
/mindblowing
/minimalcatart
/MinimalWallpaper
/MiniPCs
/Miniworlds
/misleadingthumbnails
/mlem
/MonaLeslie
/Monitors
/Moronavirus
/MortalKombat
/MovieDetails
/MovieMistakes
/mramemes
/msaeachubaets
/MurderedByWords
/murdermittens
/MuscleConfusion
/MyPeopleNeedMe
/nalgonas
/NatureIsFuckingLit
/NCAAgirls
/NeckbeardNests
/Neverbrokeabone
/nevertellmetheodds
/NewChallenger
/NewOffensiveMemes
/NewProductPorn
/newsactors
/newsbloopers
/nextfuckinglevel
/Nibmeisters
/nicechips
/Nicegirls
/NightOutGirls
/NoahGetTheBoat
/NobodyAsked
/NonFunctionSlackFill
/nonnude
/nonono
/nononomaybe
/nononono
/nonononoaww
/nonononoyes
/nonononoyesno
/nonoyesyesnonononono
/nonprofit
/Nonprofit_Jobs
/nonprofitprojects
/normalinfuriating
/nosafetysmokingfirst
/NoStupidQuestions
/Notebook_share
/notebooks
/nothingeverhappens
/notinteresting
/NotKenM
/notlikeothergirls
/NotMyJob
/notreallyhe
/NSALeaks
/NSFW_Cams
/nsfw_gifs
/NSFWBOX
/nsfwcosplay
/NSFWFunny
/NSFWShitposts
/nsfwsports
/NSFWverifiedamateurs
/ntbdbiwdfta
/nycCoronavirus
/OddlyArousing
/oddlysatisfying
/ofcoursethatsathing
/OfficeScripts
/Ohlympics
/okbuddycapitalist
/okbuddylinux
/okbuddyretard
/OldSchoolCool
/olkb
/oneliners
/oneshotsubs
/onlyfanschicks
/OopsDidntMeanTo
/oopsec
/openbsd
/opendirectories
/OpenDirectoriesBot
/opensource
/openSUSE
/OperationsSecurity
/opsec
/OrangePI
/Organ_Eyes
/OSHA
/OutOfTheLoop
/PaidForWinRAR
/palest
/PanelGore
/paradolia
/Pareidolia
/ParentsAreFuckingDumb
/ParodyPornVideos
/patientgamers
/PBSOD
/pchelp
/pcmasterrace
/PCSleeving
/PedoGate
/pencils
/pens
/PeopleFuckingDying
/peopleofwalmart
/Perfectfit
/perfectlycutscreams
/PetsareAmazing
/PetTheDamnDog
/pettyrevenge
/PFSENSE
/photoshopbattles
/physec
/PiCases
/pics
/pihole
/Piracy
/PiratedGames
/Playboy
/playstupidgames
/PLC
/pocketpussy
/podman
/Pointless_Arguments
/PoliticalCompassMemes
/PoliticalHumor
/pop_os
/PopCultureGifs
/Porn2020
/PornCum
/Porndio
/PornHDvideos
/Pornheat
/PornhubComments
/PowerMoves
/PowerShell
/powerwashinggore
/powerwashingporn
/PraiseTheCameraMan
/PrayersToTrump
/Prematurecelebration
/printers
/Prisonwallet
/privacy
/privacytoolsIO
/Product_Hub
/ProgrammerHumor
/programming
/programmingcirclejerk
/programminghumor
/propaganda
/PropagandaPosters
/ProperAnimalNames
/ProRevenge
/PublicFreakout
/punchableface
/punchablefaces
/PunPatrol
/puppersheckingdying
/PuppySmiles
/PurplePillDebate
/PussyPass
/pussypassdenied
/PutYourDickInThat
/Python
/QuickMaffs
/quityourbullshit
/rage
/raisedbynarcissists
/rareinsults
/rarepuppers
/raspberry_pi
/RASPBERRY_PI_PROJECTS
/raspberrypi
/reallifedoodles
/RealTesla
/ReconstructionPorn
/RectalStickers
/redhat
/redneckengineering
/removalbot
/replywithasub
/RepurposedTools
/restofthefuckingowl
/RetroFuturism
/retrogaming
/RHCE
/rhcsa
/rhel
/righthanging
/rimjob_steve
/Roombaww
/royalporn
/RuinedMyDay
/sadcringe
/SafelyEndangered
/salty
/Satisfyingasfuck
/SavageGarden
/savedyouaclick
/sbubby
/SchizophreniaRides
/SchoolRevenge
/ScienceTeachers
/scriptedasiangifs
/ScriptedCaucasianGIFs
/scumoftheearth
/Secguards
/secondsketch
/secretcompartments
/security
/securityguards
/SelfAwarewolves
/Sexyly
/sexyshorts
/sffpc
/sfwpenis
/SFWporn
/ShadowPC
/ShamelesslyStolen
/sharepoint
/sheets
/SHHHHHEEEEEEEIIIITT
/shill
/ShitAmericansSay
/ShitMomGroupsSay
/Shitty_Car_Mods
/ShittyAnimalFacts
/shittyaskscience
/shittyfoodporn
/ShittyGroupMembers
/shittykickstarter
/shittykickstarters
/ShittyLifeProTips
/shittylpt
/shittymoviedetails
/shockwaveporn
/ShortShorts
/Showerthoughts
/ShowMeTheseTits
/Shrimping
/shutupandtakemymoney
/SighsUnzips
/sirensong
/Sissy_hot
/Skookum
/slammywhammies
/sleeving
/SlyGifs
/SnapChad
/Sneks
/snowden
/SocialEngineering
/softwaregore
/soldering
/SommerRay
/SourceOfPorn
/spacex
/specializedtools
/SpecialNeedsPuppers
/spiderbro
/sploot
/SportsDelights
/SquatWearingHeels
/StallmanWasRight
/starterpacks
/StartledCats
/stationery_jp
/stealth100
/steemhunt
/STEMdents
/stolendogbeds
/StonerEngineering
/StopEnoughMuskSpam
/StoppedWorking
/StraightGirlsPlaying
/StreetFighter
/StreetsIsWatchin
/strokewhilecommenting
/Stunning_Girls
/stupidpeople
/stupidtax
/Subliminal
/submechanophobia
/SubredditDrama
/SubredditHashtags
/subreddits
/SubsIFellFor
/subsithoughtifellfor
/subsithoughtwerefake
/SubsThatActuallyExist
/SubsYouFellFor
/suddenlynazi
/suddenlysexoffender
/SuddenlyTrans
/suicidebywords
/SuicideWatch
/SupermodelCats
/SuperThiccGirls
/supplychain
/suspiciouslyspecific
/SweatyPalms
/sysadmin
/systemcrash
/talesfromcavesupport
/TargetedShirts
/TaylorSwiftBreasts
/TaylorSwiftBum
/TaylorSwiftFace
/TaylorSwiftMidriff
/TaylorSwiftPictures
/TaylorSwiftsLegs
/Teachers
/teachingresources
/TechnicallyCorrect
/technicallythetruth
/technicallytrue
/techsupport
/techsupportmacgyver
/TechWar
/TeenHDporn
/TerminallyStupid
/teslamotors
/textbook_piracy
/Textbook_releases
/textbooks
/thanksihateit
/thanksiloveit
/ThanosCar
/thatescalatedquickly
/thathapp
/thatHappened
/ThatLookedExpensive
/ThatsInsane
/The_Dumbass
/the_elon
/The_Musk
/TheBluePill
/TheCuddlePuddle
/TheeHive
/theinternetofshit
/TheMightyPen
/TheNuclearOption
/theocho
/Theranos
/TheRedPill
/therewasanattemp
/therewasanattempt
/TheRightCantMeme
/thespoonyexperiment
/TheWayWeWere
/theydidthemath
/theydidthemeth
/theydidthemonstermath
/theydidthemonstermeth
/theyknew
/thick
/ThickGirlsTwerking
/ThickTaylorSwift
/thingsforants
/ThisButUnironically
/Thisismylifemeow
/thisismylifenow
/ThriftStoreHauls
/ThunderThots
/ti36xproMasterRace
/tight_shorts
/TightShorts
/TIHI
/Tinder
/tippytaps
/Tiresaretheenemy
/titlegore
/Tonedeafcelebs
/toofers
/tooktoomuch
/TopConspiracy
/toptalent
/torrents
/TouchThaFishy
/trashy
/TrashyButWholesome
/TronScript
/trypophobia
/TsundereSharks
/tuckedinkitties
/TwentyCharacterLimit
/twerking
/Twitch
/Ubuntu
/UbuntuAppDev
/umass
/UMassECEMemes
/UNBGBBIIVCHIDCTIICBG
/underbutt
/UnethicalLifeProTips
/Unexpected
/UnexpectedB99
/unexpectedbrooklyn99
/UnexpectedDannyDevito
/unexpectedidubbbz
/UnexpectedOuija
/unexpectedpawnee
/unexpectedstarwars
/UnexpectedThanos
/unexpectedthreefifths
/UnexpectedYoda
/United_Chads
/unixporn
/unRAID
/UnresolvedMysteries
/UnsleepingNsfw
/untrustworthypoptarts
/UpvotedBecauseButt
/usefulredcircle
/usefulscripts
/uselessredcircle
/UsernameChecksOut
/USGEC
/VaporwaveAesthetics
/Vastlystupid
/vaxxhappened
/VEDC
/Veronica_Victoria
/Vertical_NSFW
/VerticalGifs
/vexillology
/videos
/videosurveillance
/VikaBronova
/ViralSnaps
/vuejs
/VXJunkies
/wallpaper
/wallpaperdump
/wallpaperpacks
/wallpapers
/wallstreetbets
/WatchDoggoDieInside
/WatchDogsDieInside
/WatchDogsWoofInside
/Watchexchange
/WatchPeopleDieInside
/watchpeoplesurvive
/watchpuppersdieinside
/webdev
/Wellthatsucks
/wellthereshouldbe
/Wellworn
/whatcouldgoright
/Whatcouldgowrong
/whatisthisthing
/whatsinthebag
/whatsthisbug
/WhatsWrongWithYourDog
/wheredidthesoldergo
/whiteknighting
/whitepeoplegifs
/WhitePeopleReddit
/WhitePeopleTwitter
/wholesome
/wholesomegifs
/whoosh
/Why
/whybrows
/WhyWereTheyFilming
/WikiLeaks
/wildlyinfuriating
/windows
/Windows10
/WindowsMasterRace
/WinStupidPrizes
/woahdude
/wokekids
/womenEngineers
/woodworking
/woooosh
/woosh
/WorshipTaylorSwift
/wowthanksimcured
/wowthanksimrich
/WTF
/WTFwish
/Wuhan_Flu
/XXX_HD
/XxxHDVideos
/yesnoyesno
/yesyesyesdamn
/yesyesyesno
/yesyesyesomgyes
/yesyesyesyesno
/youareverysmart
/YourAnalBabes
/YourJokeButWorse
/youseeingthisshit
/youtubehaiku
/zfs
/Zoomies
/zsh
submitted by porn_account0001 to u/porn_account0001 [link] [comments]

Problem with the first Initialization of my LN node, dial tcp my-external-ip:9735: connect: connection timed out

Background
I was following 402 Payment Required's LN video over here (https://www.youtube.com/watch?v=q0siLF9zmWo) and everything was good so far, until the moment of the first Initialization of my LN node, I got an (dial tcp my-external-ip:9735: connect: connection timed out) error.
I was starting the Initialization by the following way
lnd --externalip=X.X.X.X
And I've my lnd configuration file with the following attributes
alias= debuglevel=debug bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind
I created the file (before) I started the Initialization.
Your environment
version of lnd: I don't know, I guess it's the latest version. which operating system (uname -a on *Nix): Ubuntu 18.04 version of btcd, bitcoind, or other backend: bitcoind 0.19.1 any other relevant environment details: My Ubuntu is running on a VM machine with a (bridged) internet connection 
Steps to reproduce
I don't know how to reproduce the problem but here is a log with my issue
2020-08-14 20:33:16.008 [INF] BTCN: Server listening on [::]:9735
2020-08-14 20:33:16.009 [INF] SRVR: Initializing peer network bootstrappers!
2020-08-14 20:33:16.009 [INF] SRVR: Creating DNS peer bootstrapper with seeds: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:16.010 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:16.022 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:16.426 [INF] DISC: Obtained 1 addrs to bootstrap network with
2020-08-14 20:33:19.428 [DBG] SRVR: Waiting 2s before trying to locate bootstrap peers (attempt #1)
2020-08-14 20:33:21.428 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:21.463 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:21.464 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:21.464 [DBG] SRVR: Waiting 4s before trying to locate bootstrap peers (attempt #2)
2020-08-14 20:33:25.464 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:25.504 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:25.504 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:25.504 [DBG] SRVR: Waiting 8s before trying to locate bootstrap peers (attempt #3)
2020-08-14 20:33:33.504 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:33.539 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:33.539 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:33.539 [DBG] SRVR: Waiting 16s before trying to locate bootstrap peers (attempt #4)
2020-08-14 20:33:49.540 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:33:49.540 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:33:49.578 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:33:49.578 [DBG] SRVR: Waiting 32s before trying to locate bootstrap peers (attempt #5)
2020-08-14 20:34:21.579 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:34:21.580 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:34:21.735 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:34:21.735 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #6)
2020-08-14 20:35:21.736 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:35:21.736 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:35:22.280 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:35:22.280 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #7)
2020-08-14 20:35:27.316 [ERR] SRVR: Unable to connect to ##################################################################@my-external-ip:9735: dial tcp my-external-ip:9735: connect: connection timed out
2020-08-14 20:36:22.280 [INF] DISC: Attempting to bootstrap with: BOLT-0010 DNS Seed: [[nodes.lightning.directory soa.nodes.lightning.directory] [lseed.bitcoinstats.com ]]
2020-08-14 20:36:22.347 [INF] CRTR: Pruning channel graph using block 0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57 (height=643720)
2020-08-14 20:36:22.349 [INF] CRTR: Block 0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57 (height=643720) closed 0 channels
2020-08-14 20:36:22.461 [DBG] NTFN: Filtering 3178 txns for 0 spend requests at height 643720
2020-08-14 20:36:22.523 [INF] NTFN: New block: height=643720, sha=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57
2020-08-14 20:36:22.523 [DBG] SWPR: New block: height=643720, sha=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57
2020-08-14 20:36:22.523 [INF] UTXN: Attempting to graduate height=643720: num_kids=0, num_babies=0
2020-08-14 20:36:22.524 [DBG] DISC: New block: height=643720, hash=0000000000000000000f09423cef42338b27f29244a99deed77411cf2e6edb57
2020-08-14 20:36:22.757 [INF] DISC: Attempting to bootstrap with: Authenticated Channel Graph
2020-08-14 20:36:22.758 [ERR] SRVR: Unable to retrieve initial bootstrap peers: no addresses found
2020-08-14 20:36:22.758 [DBG] SRVR: Waiting 1m0s before trying to locate bootstrap peers (attempt #8)
Expected behavior
I expected the Initialization would work normally without any issues.
Actual behavior
The first Initialization of the LN node didn't happen, stuck in the loop of trying to locate bootstrap peers
N.B. I'm a unix beginner, so please bare with me.
submitted by scottcarter2020 to lightningnetwork [link] [comments]

Running a Bitcoin node on a $11.99 SBC

Running a Bitcoin node on a $11.99 SBC
Just wanted to let you guys know that I'm successfully running a (pruned) Bitcoin node + TOR on a $11.99 single board computer (Rock Pi S).
The SBC contains a Rockchip RK3308 Quad A35 64bit processor, 512MB RAM, RJ45 Ethernet and USB2 port and I'm using a 64GB SDCard. It runs a version of Armbian (410MB free). There's a new version available that even gives you 480MB RAM, but I'm waiting for Bitcoin Core 0.19 before upgrading.
To speed things up I decided to run Bitcoin Core on a more powerful device to sync the whole blockchain to an external HDD. After that I made a copy and ran it in pruned mode to end up with the last 5GB of the blockchain. I copied the data to the SD card and ran it on the Rock Pi S. After verifying all blocks it runs very smoothly. Uptime at the moment is 15 days.
I guess you could run a full node as well if you put in a 512GB SDcard.
The Rock Pi S was sold out, but if anybody is interested, they started selling a new batch of Rock Pi S v1.2 from today.
Screenshot of resources being used
Bitcoin Core info
Around 1.5 GB is being transferred every day
---
Some links and a short How to for people that want to give it a try:
  1. This is the place where I bought the Rock Pi S.
  2. Here you find more information about Armbian on the Rock Pi S. Flash it to your SDCard. Follow these instructions.
  3. Disable ZRAM swap on Armbian. If you don't do this eventually Bitcoin Core will crash. nano /etc/default/armbian-zram-config ENABLED=false
  4. Enable SWAP on Armbian sudo fallocate -l 1G /swapfile sudo chmod 600 /swapfile sudo mkswap /swapfile sudo swapon /swapfile sudo swapon --show sudo cp /etc/fstab /etc/fstab.bak echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab
  5. Set up UFW Firewall sudo ufw default deny incoming sudo ufw default allow outgoing sudo ufw allow ssh # we want to allow ssh connections or else we won’t be able to login. sudo ufw allow 8333 # port 8333 is used for bitcoin nodes sudo ufw allow 9051 # port 9051 is used for tor sudo ufw logging on sudo ufw enable sudo ufw status
  6. Add user Satoshi so you don't run the Bitcoin Core as root sudo adduser satoshi --home /home/satoshi --disabled-login sudo passwd satoshi # change passwd sudo usermod -aG sudo satoshi # add user to sudo group
  7. Download (ARM64 version) and install Bitcoin Core Daemon
  8. Download and install TOR (optional). I followed two guides. This one and this one.
  9. Create a bitcoin.conf config file in the .bitcoin directory. Mine looks like this: daemon=1 prune=5000 dbcache=300 maxmempool=250 onlynet=onion proxy=127.0.0.1:9050 bind=127.0.0.1 #Add seed nodes seednode=wxvp2d4rspn7tqyu.onion seednode=bk5ejfe56xakvtkk.onion seednode=bpdlwholl7rnkrkw.onion seednode=hhiv5pnxenvbf4am.onion seednode=4iuf2zac6aq3ndrb.onion seednode=nkf5e6b7pl4jfd4a.onion seednode=xqzfakpeuvrobvpj.onion seednode=tsyvzsqwa2kkf6b2.onion #And/or add some nodes addnode=gyn2vguc35viks2b.onion addnode=kvd44sw7skb5folw.onion addnode=nkf5e6b7pl4jfd4a.onion addnode=yu7sezmixhmyljn4.onion addnode=3ffk7iumtx3cegbi.onion addnode=3nmbbakinewlgdln.onion addnode=4j77gihpokxu2kj4.onion addnode=5at7sq5nm76xijkd.onion addnode=77mx2jsxaoyesz2p.onion addnode=7g7j54btiaxhtsiy.onion ddnode=a6obdgzn67l7exu3.onion
  10. Start Bitcoin Daemon with the command bitcoind -listenonion
Please note that I'm not a professional. So if anything above is not 100% correct, let me know and I will change it, but this is my setup at the moment.
submitted by haste18 to Bitcoin [link] [comments]

Is installing and compiling libraries as extremely frustrating and impossible for others as it is for me?

I don't know if it's my unconventional programming setup (VirtualBox Ubuntu 18), but I have never been able to simply follow the steps to compile a project or application without major problems happening.
Here are all some examples from me trying to build openpose tonight. It's what prompted me to make this post:
  1. Cmake must be updated because, for some reason, the default apt-get cmake is still the version from 2017!
  2. I had to specifically install python3.7-dev instead of python 3.6-dev even though everyone builds openpose with python3.5-dev (which I couldn't install).
  3. I had to mix and match commands from three different tutorials because following just one of any of them resulted in errors.
  4. Openpose would not compile because there was a typo in one of the third-party libraries that I found out only after diving deep into github. I had to vim and manually edit the source code to fix this one.
This sounds a bit whiny, and it may just be only to whine. But is this really how major packages are dealt with?
This is just one example, a month ago I spent a whole day just to compile a library by Google called mediapipe. In between these examples have been dozens of other libraries and packages where following the instructions was not sufficient and I needed to dive deep into terminology way above my head to try and debug some stupid problems and it seems to not be getting easier with time.
It just seems like such a major headache and the solutions are so arcane that I can't fathom how anyone even came up with them? It just looks like: Oh, simply apt-get llldldlepellelpv=3.5 the lllldldldelep3.5.1 has the bug on line 3,884 and then copy it into this other directory and make sure it's not done past 2PM otherwise you also have to meet this dependency by sacrificing your 3rd most valued possession by chucking it out of the 4 story apartment (incompatible with non-4-story apartments). This result will then be the 5th post on stack overflow and the only one that works. The others just reiterate the exact things you've already tried in judgemental tones or just go off the deep end completely with some insane-tier fixes, including running overcomplicated batch scripts they made which who knows what they do other than probably remotely install a bitcoin miner.
Plus not to mention that I'm trying to code with some of my classmates and the outcome of each of our slightly different setups results in every possible combination of bugs. No single set of instructions will make a major library compile on all of our ubuntu setups.
The setup of libraries (not even talking about incorporating them into my own project so that mine will compile alongside them) is just an extremely frustrating process. What are the secrets to doing it right and being able to know which magic commands fix the bugs?
submitted by Ari2010 to learnprogramming [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year(only pc-miner)

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinMining [link] [comments]

Solve the "storage, mining pool and exchange centralization", and only generate 1G data every year

The blockheader has two segments with a total length of 64 bit0 (of which blocktime is 64 bits), which strongly prevents the collapse effect of the sha256 operation in the ASIC miner, so that the mining difficulty will not increase indefinitely. The centralization for the high hashrate of the mining pool is strongly restricted. Census and prune the transactions (at most 4 outputs per transaction) whose all outputs are spent,in the block below 1300 depth in batches(i.e. clear up the input and output at the same time, and only keep the version of all-outs-spent transaction on the disk,--not serialize vin and vout). 250 for each batch, 20 block files(one file per block) will be reconstructed for each block received from other nodes, that is to say, 5000 transactions will be pruned at a time. And special mechanism is used to make the synchronization of data from malicious nodes error free. Only 1G data is increased every year. The data it running for 1000 years will be no more than 1T. Block size is 2M, and only 1g data is increased every year without SPV, which strongly prevents the storage of a large number of block data reducing the number of nodes. At the same time, 'four outputs per tx' limit the settlement of the mining pool, and strongly prevent the centralization of the mining pool. For example, the settlement is sent to 4000 miners, which requires 1000 transactions. All currencies are locked in the maturity of 300 blocks (the input can only be used as prevout after 300 blocks), which strongly prevents the frequency of trading speculation, the crash from the online exchange, and prevent the centralization of the biggest online exchange in the world.
This has achieved "absolute decentralization".
At present, the tip height is only 600, and there is no pre-mined. The RPC is stable and reliable same as bitcoin 0.10.2. No segwit but P2SH, a little change based on 0.10.2. Usage: $ /download-directory/bitcoind -addnode =47.114.58.108 (same for Ubuntu) with bitcoin.conf configuration file
Detailed introduction,original text is as follows: github-holyangel250-bitsupercoin
submitted by DangerousDetail8 to BitcoinSerious [link] [comments]

Deployed (on server) Django 3 project doesn't sees static files

#Deployed #Django3 #not #loands #static #files Deployed (on server) Django 3 project doesn't sees static and css files(whole static folder), the local on development machine works perfectly.

The guide that I have followed is [this](https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-18-04).
- I have et up a Digital ocean droplet with ubuntu 18.04
- my static files can be found here
STATICFILES_DIRS = [os.path.join(BASE_DIR, 'mymainapp/static/')] #STATIC_ROOT = os.path.join(BASE_DIR, 'static') # Removed based [on](https://stackoverflow.com/questions/60354519/django-base-html-extended-to-homepage-html-static-images-appear-but-home-css-d) STATIC_URL = '/static/' MEDIA_ROOT = os.path.join(BASE_DIR, 'mymainapp/media') MEDIA_URL = '/media/' 
- Than all the other staff with Postgres, Nginx, and Gunicorn as in the [guide](https://www.digitalocean.com/community/tutorials/how-to-set-up-django-with-postgres-nginx-and-gunicorn-on-ubuntu-18-04)
- but the static files (image, SVG, css, files doesn't load in)
- I have my bootstrap CSS files downloaded to local directory
- The website is online and if I press F12 in chrome it puts out the following error messages (turning ```DEBUG = True``` does not deliver any more error messages or error page)
Failed to load resource: the server responded with a status of 404 (Not Found) homepage03_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) logo_03c_small.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) jquery.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) bootstrap.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) popper.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) tiktok_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) instagram_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) twitch_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) twitter_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) youtube_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) facebook_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) bootstrap.min.js:1 Failed to load resource: the server responded with a status of 404 (Not Found) mobile_features_large_compressed.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) creator_platforms_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) creator_sm_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) reoccuring_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) stripe_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) customerchat.php?app_id=&attribution=setup_tool&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D46%23cb%3Df2ca0722231e688%26domain%3D159.65.234.146%26origin%3Dhttp%3A%2F%2F159.65.234.146%2Ff167133a445f9a4%26relation%3Dparent.parent&container_width=0&locale=en_US&page_id=2172253486430236&sdk=joey:1 Failed to load resource: the server responded with a status of 500 () paypal_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) googleads1_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) googlepay_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) amazon_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) bitcoin_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) logo_02_Background.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) shirts_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) message_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) sopnsor2_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) socialmedia_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) combinedbarnad_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) applepay_f.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) check.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) feature_description_laptop_cut.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) self_image_comp.png:1 Failed to load resource: the server responded with a status of 404 (Not Found) reddit_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) linkedin_col.svg:1 Failed to load resource: the server responded with a status of 404 (Not Found) collie_2_comp.jpg:1 Failed to load resource: the server responded with a status of 404 (Not Found) bootstrap.min.css:1 Failed to load resource: the server responded with a status of 404 (Not Found) DevTools failed to parse SourceMap: chrome-extension://hnmpcagpplmpfojmgmnngilcnanddlhb/browser-polyfill.min.js.map DevTools failed to parse SourceMap: chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/include.preload.js.map DevTools failed to parse SourceMap: chrome-extension://hnmpcagpplmpfojmgmnngilcnanddlhb/browser-polyfill.min.js.map DevTools failed to parse SourceMap: chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/include.postload.js.map 
- I had the same errors before going thru the guide and just haveing a basic pulled git version of it and running with ```python3 manage.py runserver``` it loads the site but not the css and the static elements
- I have put the base ```/media``` and ```/static``` folders in to git ignore (these should be the one where collect static collets up the element). The original static is under the ```myowndjango-project/myowndjango/static``` and ```myowndjango-project/myowndjango/media```
- I have also set up the nginx as follows
... location /static/ { root /home/myserverusemyowndjango-project; } location /media/ { root /home/myserverusemyowndjango-project; } ... 
What I have tried to solve it
- look for server access log
- run ```/valog/nginx/access.log``` result: ```-bash: /valog/nginx/access.log: Permission denied```
- run ```sudo /valog/nginx/access.log``` result: ```sudo: /valog/nginx/access.log: command not found```
- changing nginx file
... location /static/ { root /home/myserverusemyowndjango-project/myowndjango/static; } location /media/ { root /home/myserverusemyowndjango-project/myowndjango/media; } ... 
- Running
python3 manage.py collectstatic 
(restarted nginx and gunicorn) and it still does the same error.

Thank you for the help.
submitted by glassAlloy to djangolearning [link] [comments]

Groestlcoin 6th Anniversary Release

Introduction

Dear Groestlers, it goes without saying that 2020 has been a difficult time for millions of people worldwide. The groestlcoin team would like to take this opportunity to wish everyone our best to everyone coping with the direct and indirect effects of COVID-19. Let it bring out the best in us all and show that collectively, we can conquer anything.
The centralised banks and our national governments are facing unprecedented times with interest rates worldwide dropping to record lows in places. Rest assured that this can only strengthen the fundamentals of all decentralised cryptocurrencies and the vision that was seeded with Satoshi's Bitcoin whitepaper over 10 years ago. Despite everything that has been thrown at us this year, the show must go on and the team will still progress and advance to continue the momentum that we have developed over the past 6 years.
In addition to this, we'd like to remind you all that this is Groestlcoin's 6th Birthday release! In terms of price there have been some crazy highs and lows over the years (with highs of around $2.60 and lows of $0.000077!), but in terms of value– Groestlcoin just keeps getting more valuable! In these uncertain times, one thing remains clear – Groestlcoin will keep going and keep innovating regardless. On with what has been worked on and completed over the past few months.

UPDATED - Groestlcoin Core 2.18.2

This is a major release of Groestlcoin Core with many protocol level improvements and code optimizations, featuring the technical equivalent of Bitcoin v0.18.2 but with Groestlcoin-specific patches. On a general level, most of what is new is a new 'Groestlcoin-wallet' tool which is now distributed alongside Groestlcoin Core's other executables.
NOTE: The 'Account' API has been removed from this version which was typically used in some tip bots. Please ensure you check the release notes from 2.17.2 for details on replacing this functionality.

How to Upgrade?

Windows
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), then run the installer.
OSX
If you are running an older version, shut it down. Wait until it has completely shut down (which might take a few minutes for older versions), run the dmg and drag Groestlcoin Core to Applications.
Ubuntu
http://groestlcoin.org/forum/index.php?topic=441.0

Other Linux

http://groestlcoin.org/forum/index.php?topic=97.0

Download

Download the Windows Installer (64 bit) here
Download the Windows Installer (32 bit) here
Download the Windows binaries (64 bit) here
Download the Windows binaries (32 bit) here
Download the OSX Installer here
Download the OSX binaries here
Download the Linux binaries (64 bit) here
Download the Linux binaries (32 bit) here
Download the ARM Linux binaries (64 bit) here
Download the ARM Linux binaries (32 bit) here

Source

ALL NEW - Groestlcoin Moonshine iOS/Android Wallet

Built with React Native, Moonshine utilizes Electrum-GRS's JSON-RPC methods to interact with the Groestlcoin network.
GRS Moonshine's intended use is as a hot wallet. Meaning, your keys are only as safe as the device you install this wallet on. As with any hot wallet, please ensure that you keep only a small, responsible amount of Groestlcoin on it at any given time.

Features

Download

iOS
Android

Source

ALL NEW! – HODL GRS Android Wallet

HODL GRS connects directly to the Groestlcoin network using SPV mode and doesn't rely on servers that can be hacked or disabled.
HODL GRS utilizes AES hardware encryption, app sandboxing, and the latest security features to protect users from malware, browser security holes, and even physical theft. Private keys are stored only in the secure enclave of the user's phone, inaccessible to anyone other than the user.
Simplicity and ease-of-use is the core design principle of HODL GRS. A simple recovery phrase (which we call a Backup Recovery Key) is all that is needed to restore the user's wallet if they ever lose or replace their device. HODL GRS is deterministic, which means the user's balance and transaction history can be recovered just from the backup recovery key.

Features

Download

Main Release (Main Net)
Testnet Release

Source

ALL NEW! – GroestlcoinSeed Savior

Groestlcoin Seed Savior is a tool for recovering BIP39 seed phrases.
This tool is meant to help users with recovering a slightly incorrect Groestlcoin mnemonic phrase (AKA backup or seed). You can enter an existing BIP39 mnemonic and get derived addresses in various formats.
To find out if one of the suggested addresses is the right one, you can click on the suggested address to check the address' transaction history on a block explorer.

Features

Live Version (Not Recommended)

https://www.groestlcoin.org/recovery/

Download

https://github.com/Groestlcoin/mnemonic-recovery/archive/master.zip

Source

ALL NEW! – Vanity Search Vanity Address Generator

NOTE: NVidia GPU or any CPU only. AMD graphics cards will not work with this address generator.
VanitySearch is a command-line Segwit-capable vanity Groestlcoin address generator. Add unique flair when you tell people to send Groestlcoin. Alternatively, VanitySearch can be used to generate random addresses offline.
If you're tired of the random, cryptic addresses generated by regular groestlcoin clients, then VanitySearch is the right choice for you to create a more personalized address.
VanitySearch is a groestlcoin address prefix finder. If you want to generate safe private keys, use the -s option to enter your passphrase which will be used for generating a base key as for BIP38 standard (VanitySearch.exe -s "My PassPhrase" FXPref). You can also use VanitySearch.exe -ps "My PassPhrase" which will add a crypto secure seed to your passphrase.
VanitySearch may not compute a good grid size for your GPU, so try different values using -g option in order to get the best performances. If you want to use GPUs and CPUs together, you may have best performances by keeping one CPU core for handling GPU(s)/CPU exchanges (use -t option to set the number of CPU threads).

Features

Usage

https://github.com/Groestlcoin/VanitySearch#usage

Download

Source

ALL NEW! – Groestlcoin EasyVanity 2020

Groestlcoin EasyVanity 2020 is a windows app built from the ground-up and makes it easier than ever before to create your very own bespoke bech32 address(es) when whilst not connected to the internet.
If you're tired of the random, cryptic bech32 addresses generated by regular Groestlcoin clients, then Groestlcoin EasyVanity2020 is the right choice for you to create a more personalised bech32 address. This 2020 version uses the new VanitySearch to generate not only legacy addresses (F prefix) but also Bech32 addresses (grs1 prefix).

Features

Download

Source

Remastered! – Groestlcoin WPF Desktop Wallet (v2.19.0.18)

Groestlcoin WPF is an alternative full node client with optional lightweight 'thin-client' mode based on WPF. Windows Presentation Foundation (WPF) is one of Microsoft's latest approaches to a GUI framework, used with the .NET framework. Its main advantages over the original Groestlcoin client include support for exporting blockchain.dat and including a lite wallet mode.
This wallet was previously deprecated but has been brought back to life with modern standards.

Features

Remastered Improvements

Download

Source

ALL NEW! – BIP39 Key Tool

Groestlcoin BIP39 Key Tool is a GUI interface for generating Groestlcoin public and private keys. It is a standalone tool which can be used offline.

Features

Download

Windows
Linux :
 pip3 install -r requirements.txt python3 bip39\_gui.py 

Source

ALL NEW! – Electrum Personal Server

Groestlcoin Electrum Personal Server aims to make using Electrum Groestlcoin wallet more secure and more private. It makes it easy to connect your Electrum-GRS wallet to your own full node.
It is an implementation of the Electrum-grs server protocol which fulfils the specific need of using the Electrum-grs wallet backed by a full node, but without the heavyweight server backend, for a single user. It allows the user to benefit from all Groestlcoin Core's resource-saving features like pruning, blocks only and disabled txindex. All Electrum-GRS's feature-richness like hardware wallet integration, multi-signature wallets, offline signing, seed recovery phrases, coin control and so on can still be used, but connected only to the user's own full node.
Full node wallets are important in Groestlcoin because they are a big part of what makes the system be trust-less. No longer do people have to trust a financial institution like a bank or PayPal, they can run software on their own computers. If Groestlcoin is digital gold, then a full node wallet is your own personal goldsmith who checks for you that received payments are genuine.
Full node wallets are also important for privacy. Using Electrum-GRS under default configuration requires it to send (hashes of) all your Groestlcoin addresses to some server. That server can then easily spy on your transactions. Full node wallets like Groestlcoin Electrum Personal Server would download the entire blockchain and scan it for the user's own addresses, and therefore don't reveal to anyone else which Groestlcoin addresses they are interested in.
Groestlcoin Electrum Personal Server can also broadcast transactions through Tor which improves privacy by resisting traffic analysis for broadcasted transactions which can link the IP address of the user to the transaction. If enabled this would happen transparently whenever the user simply clicks "Send" on a transaction in Electrum-grs wallet.
Note: Currently Groestlcoin Electrum Personal Server can only accept one connection at a time.

Features

Download

Windows
Linux / OSX (Instructions)

Source

UPDATED – Android Wallet 7.38.1 - Main Net + Test Net

The app allows you to send and receive Groestlcoin on your device using QR codes and URI links.
When using this app, please back up your wallet and email them to yourself! This will save your wallet in a password protected file. Then your coins can be retrieved even if you lose your phone.

Changes

Download

Main Net
Main Net (FDroid)
Test Net

Source

UPDATED – Groestlcoin Sentinel 3.5.06 (Android)

Groestlcoin Sentinel is a great solution for anyone who wants the convenience and utility of a hot wallet for receiving payments directly into their cold storage (or hardware wallets).
Sentinel accepts XPUB's, YPUB'S, ZPUB's and individual Groestlcoin address. Once added you will be able to view balances, view transactions, and (in the case of XPUB's, YPUB's and ZPUB's) deterministically generate addresses for that wallet.
Groestlcoin Sentinel is a fork of Groestlcoin Samourai Wallet with all spending and transaction building code removed.

Changes

Download

Source

UPDATED – P2Pool Test Net

Changes

Download

Pre-Hosted Testnet P2Pool is available via http://testp2pool.groestlcoin.org:21330/static/

Source

submitted by Yokomoko_Saleen to groestlcoin [link] [comments]

How to install OKcash wallet (Ubuntu) Beginner's Guide to the Bash Terminal - YouTube Ultra Safe - Bitcoin Paper Wallet How to restore your Litecoins into the LTC Wallet in Linux [Ubuntu] MPI Tutorials 04 - NFS Shared Folder Setup in Virtual Machines (Ubuntu, VirtualBox, MPICH2)

In this step-by-step guide we will show you 'How to install blockchain on Ubuntu Blockchain.' Blockchain is, quite literally, a chain of blocks that contain and distribute digital information (the block) stored in a public database (the chain). The blocks store different types of information. Say, for instance, blockchain is being used to store customers’ information. Start Bitcoin, now you will see all the files are created in the new data directory. Linux. By default Bitcoin will put its data here: ~/.bitcoin/ You need to do a "ls -a" to see directories that start with a dot. If that's not it, you can do a search like this: find / -name wallet.dat -print 2>/dev/null Mac. By default Bitcoin will put its data here: ~/Library/Application Support/Bitcoin ... I recently upgraded my Lenovo PC (16-GB RAM; 2TB-HD) from Ubuntu 18.04 to 20.04. I had saved the ".bitcoin" directory (and subdirectories and files) to an external hard disk drive. Since then I have ... Copy the Bitcoin Data Directory . Having found the default data directory, we can now copy it. Be sure that Bitcoin Core has been shut down and is no longer running. The software occasionally takes a minute or two to completely exit. Begin by renaming the Bitcoin Core data directory. Use the name bitcoin-backup. Don’t move the renamed folder. This allows recovery of the original data ... 3. Setting up Bitcoin Configuration. A. Creating .bitcoin folder in root directory. Run the following command to check if you are in the root directory: cd ~ Then run the following command to create the .bitcoin directory. For starters: mkdir stands for make directory. And and dot folder means it is a hidden folder. You can not view the folder ...

[index] [44988] [2885] [22109] [22698] [32871] [3438] [37787] [1395] [48887] [28418]

How to install OKcash wallet (Ubuntu)

Ubuntu -2 Setting up .bitcoin folder Commands, cd ~/ mkdir .bitcoin cd .bitcoin nano bitcoin.conf server=1 daemon=1 testnet=0 rpcuser=UNIQUE_RPC_USERNAME rpcpassword=UNIQUE_RPC_PASSWORD. this video explain how you build the compile environment on windows to create altcoin ~ cryptocoin Windows QT `s Compile Depencies ~ complete deps folder included to download . Depencies : https ... Upgrading to Bitcoin Core v0.18.0 in Ubuntu 1. Download latest release from bitcoincore.org (Linux tgz file) 2. Download the digital signatures file SHASUM.asc (PGP signed) 3. Use the fingerprint ... Now just extract the files in another folder of your choice For this example we'll just extract them to our desktop Now that we have the files let's start it There's a librarie missing let's get ... NFS Shared Folder Setup - MPI Tutorials in Virtual Machines (Ubuntu, VirtualBox, MPICH2) Master Node with Ubuntu 13.10 and Slave node on mini.iso Within Windows 8 on Dell PowerEdge C6100 48GB RAM ...

#