Running Bitcoind – BitcoinWiki

IdealCash

IdealCash deal coin is a Decentralized Digital Currency based on an Open-Source Peer-To-Peer Internet Protocol. It provides Proof-of-Stake (PoS) Block Generation Methods with separated target limits, granting everyone a 30% floating coin return rate! Also, transaction fee’s are extremely low, it’s only 0.0001 to transfer 10000000.00 coins!
[link]

bitcoindark

[link]

Where is the bitcoin.conf file stored on Windows?

When running bitcoin-qt.exe for the first time where are the files supposed to be stored?
submitted by LightShadow to BitcoinABC [link] [comments]

Where is the bitcoin.conf file stored on Windows? /r/BitcoinABC

Where is the bitcoin.conf file stored on Windows? /BitcoinABC submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Where is bitcoin.conf file on Windows 0.11.0 install?

I want to add the commands to restrict transaction flooding for my node. But I can't find this file, nor where I should put it (if it is I need to create it).
submitted by allgoodthings1 to Bitcoin [link] [comments]

Bitcoin Fullnode Install Guide for Dummies ;-)

Bitcoin Fullnode Install Guide for Dummies ;-)
Feel free to stop at Level 0 or Level 1, which is fine. More advanced configs are offered to those with more tech savvy. This guide, obviously assumes a Windows 10 install, but other OSes work fine, just find a different guide. BTW, the "For Dummies" is a callback to a set of "tech" books in the 90's intended to be as easy as possible. It is in jest and not intended to insult the reader. Finally, if you dislike the formatting, a well formatted copy can be found here
There is a fairly small subset of Bitcoin users that run a full node. I think the idea of running a full node has gotten a bad rap over the years since there is so much talk about running on a Raspberry Pi, or getting zippy SSDs. Although all of this can be fun, it is often not really required at all. Here are some ways to run a full node starting with the very simple. I'll get into more complex configs, but these are all optional.

Tech Skill Level: 0 (the basics)

  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
In many cases, thats it. If your running a new machine with a fairly good internet connection, 8 or 9 hours will be enough to complete the "Initial Block Download" (IBD). This may fill up your drive a bit, but again, on most new machines, 300 GB of space isn't that hard to come by.

Tech Skill Level: 1 (encrypted wallet)

One thing we left out in the level-0 exercise is encrypting your wallet. It's easy enough to do well, but a bit more difficult to do right. The main challenge is that humans generate really poor passwords. If you want a good password, the best way is to use something called "diceware". Basically, you just grab 4 or 5 dice and each throw of the dice represents a certain word on a special list. The throw {1,4,5,3,1} for example would be the word camping on the EFF-diceware-wordlist. So you repeat this a few times until you have a list of 8 or so words which becomes the passphrase you use to encrypt your wallet. Write it down, it is always hard to remember at first. So at level-1 your list becomes:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Choose Encrypt Wallet from the Settings menu
  5. Enter your 8 word (or so) passphrase generated using the Diceware method

Wallet Encryption Dialog

Tech Skill Level: 2 (enable pruning if needed)

Though I said "300 GB of space isn't hard to come by", some times it actually is. If space is an issue, a simple way to fix it is to tell bitcoin to simple take less space. This is called "pruning" and can take that number from 300 GB down to below 5 GB. If you can't find 5 GB, then you'll have to read ahead to level-4 to add USB storage. But the good news is, enabling pruning is pretty easy, we just add another step to our working list:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Choose Options from the Settings menu
  6. Choose Prune block storage to: and select the max size for the blocks to use
  7. Exit and restart the bitcoin application for the changes to take effect

Pruning Dialog
Note, even setting this to 1 GB will still leave you with about a 4.5 GB install. The blocks take up a lot of space, but the chainstate and other folders eat up at least 3.5 GB and they can't be pruned. Also, be aware, to disable pruning requires you to perform the entire IBD again. While pruned some other functions my be disabled as well, so just know that pruning does limit some functionality.

Tech Skill Level: 3 (verify the installer)

Although this is arguably something that should be done at level-0, some find the intricacies of comparing hash (thumbprint) values to be tedious and beyond the scope of a beginner. You will find these types of hash compares suggested quite often as a way to prevent running tainted programs. Programs are often tainted by bad disk or network performance, but most often, taint is malicious code inserted by viruses or malware. This is a way to guard yourself against those types of attacks.
What I cover here is a very basic comparison on the certificate, but a more thorough verification advised by mosts uses a program called Gpg4Win, and is beyond the scope of this beginners guide. But regardless, most users should strive to do this minimum level of validation.
  1. Download Bitcoin Core
  2. Launch the downloaded installer
  3. When prompted "Do you want to allow..." click Show more details
  4. In the details section select Show information about the publisher's certificate
  5. In the certificate window select the Details tab
  6. In the Details tab Subject should start with "CN = Bitcoin Core Code Signing Association"
  7. Ensure Thumbprint in Details reads ea27d3cefb3eb715ed214176a5d027e01ba1ee86
  8. If the checks pass, click OK to exit the certificate window and Yes to allow the installer to run.
  9. Launch the installed "Bitcoin Core" app and let it run overnight
  10. Do the wallet encryption steps here if you wish
  11. Do the optional pruning steps here if you wish

Certification Validation Windows
Note: The certificate used to sign the current Bitcoin installer is only valid from March 2020 to March 2021. After that point the thumbprint on the certificate will change. This is by design and intentional. If your reading this post after March 2021, then it is understood that the thumbprint has changed.

Tech Skill Level: 4 (use secondary storage)

We glossed over the "new machine with fairly good internet" part. Truth be known many people do not have fairly new machines, and find the IBD to take longer than the "over night" best wishes. For most people the slowdown is the disk access when calculating what is called chainstate. This requires fast random reads and writes to the disk. If you have an SSD disk, this will be no problem, but if you have a non-SSD "spinning" disk, random writes are always slow. Though an SSD will speed things up, they are pricey, so a nice middle ground may be a simple high-end USB key drive. You can get some with 10 to 15 MB/s random writes for $20 on Amazon. This is usually a order of magnitude faster than a "spinning" disk. And with pruning (see level-2), a small USB drive should be fine.
Once you decide on a drive, the tricky part will be to enable external storage. It requires editing a configuration file and adding a line. First, we want to create a directory on the key drive. You will need to determine the drive letter of your USB key drive. For the sake of this example, we will assume it is D:, but you must determine this yourself and correct the example. Once you know the drive letter, create a blank folder on the drive called Bitcoin. So for this example, creating Bitcoin on drive D: will create the path D:\Bitcoin. Once done, assuming that D: is your drive, here are the new steps including the edit of the configuration file:
  1. Download Bitcoin Core
  2. Launch the installer, verify it, then run it
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Do the optional pruning steps here if you wish
  6. Launch "Notepad" by typing "Notepad.exe" in the windows search bar then click Open
  7. Type the line datadir=D:\Bitcoin (depending on your drive letter) in the blank file
  8. Choose Save from the File menu in notepad
  9. Type %APPDATA%\Bitcoin\bitcoin.conf (note the percent signs) in the File name box
  10. Select All Files from the Save as type dropdown
  11. Click the Save button and overwrite the file if prompted
  12. Exit and restart the bitcoin application for the changes to take effect

Save As Dialog
Now that you've reached this level of technical expertise, there are many new configuration options that you can begin to modify if you wish. Most configuration data is contained in the bitcoin.conf file and learning how to maintain it is a key step for a node operator.

Tech Skill Level: 5 (all other customizations)

Here's a short list of various things you can ADD to your bitcoin.conf file. You generally just add a new line for each configuration settings.
  • addresstype=bech32
  • changetype=bech32
The addresstype / changetype allows your wallet to use the native-segwit (bech32) format. This is the most efficient and inexpensive way to spend bitcoin, and is a recommended configuration. The default uses something called p2sh-segwit which is more compatible with older wallets, but more expensive to spend.
  • minrelaytxfee=0.00000011
Changing the minrelaytxfee setting allows you to help propagate lower fee transactions. It will require more memory but TXN memory is capped at 300 MB by default anyways, so if you have enough memory, it is a good setting to choose.
  • dbcache=2048
The dbcache setting controls how many MB of memory the program will use for the chainstate database. Since this is a key bottleneck in the IBD, setting this value high (2048 MB) will greatly speed up the IBD, assuming you have the memory to spare
  • blocksdir=C:\Bitcoin
  • datadir=D:\Bitcoin
In level-4 we discussed moving the datadir to a fast external storage, but the majority of the space used for bitcoin is the blocks directory (blocksdir). Although you should always use for fastest storage for datadir, you are free to use slow storage for blocksdir. So if you only want to consume a small amount of your SSD (assumed D:) then you can keep your blocks on your slow "spinning" drive.
  • upnp=1
One of the harder challenges you may face running a node, is to get incoming connections. If you are lucky, you may find that your firewall and network HW support the uPnP protocol. If they do, this setting will allow bitcoin to configure uPnP to allow incoming connections to your node. Other methods exist to make your node reachable, but they are well beyond the scope of this guide.
submitted by brianddk to Bitcoin [link] [comments]

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]

Anatomy of the Bitcoin Node filesystem

There are man explanations like this, but this one is mine.
Just in case anyone was curious. I dug up some good posts on this and thought I'd distill it as best I could. I'll be using Windows file separators, but fee free to change them in your head.
If you name a -datadir argument, this is what will land there. If one is not named it defaults to %APPDATA%\Bitcoin
If you name a -blocksdir argument, this is what will land there. If one is not named it defaults to
If you name a -walletdir argument, this is what will land there. If one is not named it defaults to \wallets or just if the wallets subdirectory doesn't exist.
  • \wallet.dat - The wallet file with private keys and UTXOs
  • \db.log - Database log of access to wallet
Note that -datadir, -blocksdir and -walletdir can all point to different storage. The things you need to keep in mind:
  1. -datadir should be your FASTEST storage
  2. -blocksdir should be your LARGEST storage
  3. -walletdir should be your most SECURE storage
As a footnote, -testnet will throw a testnet3\ in everything, and -walletdir would be assumed to refer to test.walletdir
submitted by brianddk to Bitcoin [link] [comments]

Hice nmap en imss.gob.mx. Esta mas abierto que el OXXO. Ni siquiera funciona el SSL es una burla

PLS no me baneen

Aqui para los curiosos


Starting Nmap 7.60 ( https://nmap.org ) at 2020-09-01 03:06 CDT
Nmap scan report for imss.gob.mx (45.223.23.206)
Host is up (0.060s latency).
Other addresses for imss.gob.mx (not scanned): 45.223.17.206
Not shown: 740 filtered ports
PORT STATE SERVICE
53/tcp open domain
80/tcp open http
81/tcp open hosts2-ns
82/tcp open xfer
83/tcp open mit-ml-dev
84/tcp open ctf
85/tcp open mit-ml-dev
88/tcp open kerberos-sec
89/tcp open su-mit-tg
90/tcp open dnsix
99/tcp open metagram
389/tcp open ldap
443/tcp open https
444/tcp open snpp
445/tcp open microsoft-ds
500/tcp open isakmp
554/tcp open rtsp
555/tcp open dsf
587/tcp open submission
631/tcp open ipp
636/tcp open ldapssl
777/tcp open multiling-http
800/tcp open mdbs_daemon
801/tcp open device
843/tcp open unknown
880/tcp open unknown
888/tcp open accessbuilder
990/tcp open ftps
995/tcp open pop3s
999/tcp open garcon
1000/tcp open cadlock
1002/tcp open windows-icfw
1024/tcp open kdm
1025/tcp open NFS-or-IIS
1028/tcp open unknown
1080/tcp open socks
1111/tcp open lmsocialserver
1234/tcp open hotline
1433/tcp open ms-sql-s
1443/tcp open ies-lm
1455/tcp open esl-lm
1494/tcp open citrix-ica
1521/tcp open oracle
1935/tcp open rtmp
1971/tcp open netop-school
1972/tcp open intersys-cache
1974/tcp open drp
1984/tcp open bigbrother
2000/tcp open cisco-sccp
2001/tcp open dc
2006/tcp open invokator
2020/tcp open xinupageserver
2022/tcp open down
2048/tcp open dls-monitor
2049/tcp open nfs
2065/tcp open dlsrpn
2068/tcp open avocentkvm
2100/tcp open amiganetfs
2200/tcp open ici
2222/tcp open EtherNetIP-1
2557/tcp open nicetec-mgmt
3000/tcp open ppp
3001/tcp open nessus
3003/tcp open cgms
3005/tcp open deslogin
3006/tcp open deslogind
3007/tcp open lotusmtap
3011/tcp open trusted-web
3013/tcp open gilatskysurfer
3017/tcp open event_listener
3030/tcp open arepa-cas
3052/tcp open powerchute
3071/tcp open csd-mgmt-port
3077/tcp open orbix-loc-ssl
3306/tcp open mysql
3333/tcp open dec-notes
3389/tcp open ms-wbt-server
3404/tcp open unknown
3551/tcp open apcupsd
3580/tcp open nati-svrloc
4000/tcp open remoteanything
4001/tcp open newoak
4002/tcp open mlchat-proxy
4343/tcp open unicall
4443/tcp open pharos
4444/tcp open krb524
4445/tcp open upnotifyp
4449/tcp open privatewire
4848/tcp open appserv-http
5000/tcp open upnp
5001/tcp open commplex-link
5002/tcp open rfe
5003/tcp open filemaker
5004/tcp open avt-profile-1
5009/tcp open airport-admin
5050/tcp open mmcc
5051/tcp open ida-agent
5060/tcp open sip
5061/tcp open sip-tls
5080/tcp open onscreen
5100/tcp open admd
5120/tcp open barracuda-bbs
5222/tcp open xmpp-client
5225/tcp open hp-server
5226/tcp open hp-status
5269/tcp open xmpp-server
5280/tcp open xmpp-bosh
5440/tcp open unknown
5500/tcp open hotline
5544/tcp open unknown
5555/tcp open freeciv
5900/tcp open vnc
5901/tcp open vnc-1
5902/tcp open vnc-2
5903/tcp open vnc-3
5904/tcp open unknown
5906/tcp open unknown
5907/tcp open unknown
5910/tcp open cm
5911/tcp open cpdlc
5915/tcp open unknown
5987/tcp open wbem-rmi
5988/tcp open wbem-http
5989/tcp open wbem-https
5998/tcp open ncd-diag
5999/tcp open ncd-conf
6000/tcp open X11
6001/tcp open X11:1
6002/tcp open X11:2
6003/tcp open X11:3
6004/tcp open X11:4
6005/tcp open X11:5
6006/tcp open X11:6
6007/tcp open X11:7
6009/tcp open X11:9
6100/tcp open synchronet-db
6510/tcp open mcer-port
6543/tcp open mythtv
6565/tcp open unknown
6580/tcp open parsec-master
6666/tcp open irc
6699/tcp open napster
6779/tcp open unknown
6789/tcp open ibm-db2-admin
7000/tcp open afs3-fileserver
7001/tcp open afs3-callback
7002/tcp open afs3-prserver
7004/tcp open afs3-kaserver
7007/tcp open afs3-bos
7070/tcp open realserver
7100/tcp open font-service
7443/tcp open oracleas-https
7777/tcp open cbt
7778/tcp open interwise
7999/tcp open irdmi2
8000/tcp open http-alt
8001/tcp open vcom-tunnel
8002/tcp open teradataordbms
8007/tcp open ajp12
8008/tcp open http
8009/tcp open ajp13
8010/tcp open xmpp
8011/tcp open unknown
8021/tcp open ftp-proxy
8022/tcp open oa-system
8031/tcp open unknown
8042/tcp open fs-agent
8045/tcp open unknown
8080/tcp open http-proxy
8081/tcp open blackice-icecap
8082/tcp open blackice-alerts
8083/tcp open us-srv
8084/tcp open unknown
8085/tcp open unknown
8086/tcp open d-s-n
8087/tcp open simplifymedia
8088/tcp open radan-http
8089/tcp open unknown
8090/tcp open opsmessaging
8093/tcp open unknown
8099/tcp open unknown
8100/tcp open xprint-server
8180/tcp open unknown
8181/tcp open intermapper
8192/tcp open sophos
8193/tcp open sophos
8194/tcp open sophos
8200/tcp open trivnet1
8222/tcp open unknown
8300/tcp open tmi
8333/tcp open bitcoin
8383/tcp open m2mservices
8402/tcp open abarsd
8443/tcp open https-alt
8500/tcp open fmtp
8600/tcp open asterix
8701/tcp open unknown
8800/tcp open sunwebadmin
8873/tcp open dxspider
8888/tcp open sun-answerbook
8899/tcp open ospf-lite
9000/tcp open cslistener
9001/tcp open tor-orport
9002/tcp open dynamid
9003/tcp open unknown
9009/tcp open pichat
9010/tcp open sdr
9011/tcp open unknown
9040/tcp open tor-trans
9050/tcp open tor-socks
9071/tcp open unknown
9080/tcp open glrpc
9081/tcp open unknown
9090/tcp open zeus-admin
9091/tcp open xmltec-xmlmail
9099/tcp open unknown
9100/tcp open jetdirect
9101/tcp open jetdirect
9102/tcp open jetdirect
9103/tcp open jetdirect
9110/tcp open unknown
9111/tcp open DragonIDSConsole
9200/tcp open wap-wsp
9207/tcp open wap-vcal-s
9220/tcp open unknown
9500/tcp open ismserver
9943/tcp open unknown
9998/tcp open distinct32
9999/tcp open abyss
10000/tcp open snet-sensor-mgmt
10001/tcp open scp-config
10002/tcp open documentum
10003/tcp open documentum_s
10004/tcp open emcrmirccd
10009/tcp open swdtp-sv
10010/tcp open rxapi
10012/tcp open unknown
10024/tcp open unknown
10025/tcp open unknown
10082/tcp open amandaidx
11110/tcp open sgi-soap
12174/tcp open unknown
12265/tcp open unknown
12345/tcp open netbus
15002/tcp open onep-tls
16000/tcp open fmsas
16001/tcp open fmsascon
16012/tcp open unknown
16016/tcp open unknown
16018/tcp open unknown
16080/tcp open osxwebadmin
18040/tcp open unknown
18101/tcp open unknown
20000/tcp open dnp
30000/tcp open ndmps
31337/tcp open Elite
50000/tcp open ibm-db2
50001/tcp open unknown
55055/tcp open unknown
60443/tcp open unknown

Nmap done: 1 IP address (1 host up) scanned in 3.34 seconds

En serio de milagro nadie les ha hecho nada
submitted by phi_array to mexico [link] [comments]

PSA: Enable Tor as a simple way to make your node reachable.

Become one of the 10% of node operators that receive incoming connections.
Installing bitcoin core is easy, and with pruning it really isn't the space sink it is characterized as. Even a modest computer can complete the initial block download (IBD) and become a full node. But what some users (90%) find a bit more challenging, is how to become a listening node. Listening nodes are an important part of the network, and are simple enough to enable. I can think of 4 ways to do it:
  1. Operate on an OS and Network that support uPnP, allowing bitcoin to open the ports for you.
  2. Subscribe to a VPN that allows you to open ports through their service.
  3. Manually configure your OS and network to forward port 8333 and 18333.
  4. Run Tor and direct bitcoin to listen through it.
I'll discuss #4. Obviously #1 or #2 are easier, but require a VPN subscription or uPnP enabled HW. And if you live in a dorm or don't control the network, Tor may be the only free option available.
As a bit of background, bitcoin supports three networks that your node can listen on:
Obviously, the more you enable, the better, but here are the basic steps for Tor in broad strokes. If you have any questions post them here and I'll see if we can't help you out:
  1. Download, verify1 and install Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch and Admin command console in the directory containing tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor.exe --service stop && tor.exe --service start
  9. Record the hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. (Optional) Activate the bitnodes crawler at https://bitnodes.io/nodes/-8333/
It may take a while for your node to show up on bitnodes. I've found the check button sometimes has trouble with onions. Of course you don't need to do it, but it can provide a simple way to check status once your on the list.

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log

Bridges may be needed if the Gov't shuts down Tor exit nodes. Get Bridges by

emailing [email protected] from Gmail (only) and uncomment as follows:

Bridge obfs4 : cert= iat-mode=

HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 Cert: {Subject: Intevation GmbH; SHA1: c13a65963ad53e78694dd223d518007791a05fe4}
  • 2 PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to Bitcoin [link] [comments]

[ Bitcoin ] Anatomy of the Bitcoin Node filesystem

Topic originally posted in Bitcoin by brianddk [link]
There are man explanations like this, but this one is mine.
Just in case anyone was curious. I dug up some good posts on this and thought I'd distill it as best I could. I'll be using Windows file separators, but fee free to change them in your head.
If you name a -datadir argument, this is what will land there. If one is not named it defaults to %APPDATA%\Bitcoin
If you name a -blocksdir argument, this is what will land there. If one is not named it defaults to
  • \blocks\blk*.dat - The raw block data
  • \blocks\rev*.dat - The Undo files. List of spent UTXOs for each block
If you name a -main.walletdir argument, this is what will land there. If one is not named it defaults to \wallets or just if the wallets subdirectory doesn't exist.
  • \wallet.dat - The wallet file with private keys and UTXOs
  • \db.log - Database log of access to wallet
Note that -datadir, -blocksdir and -main.walletdir can all point to different storage. The things you need to keep in mind:
  1. -datadir should be your FASTEST storage
  2. -blocksdir should be your LARGEST storage
  3. -main.walletdir should be your most SECURE storage
As a footnote, testnet will through a testnet3\ in everything, and would require a -test.walletdir switch to set the wallet directory.
brianddk your post has been copied because one or more comments in this topic have been removed. This copy will preserve unmoderated topic. If you would like to opt-out, please send a message using [this link].
[deleted comment]
submitted by anticensor_bot to u/anticensor_bot [link] [comments]

Fun with Dynamic DNS services and bitcoind

I realize that bitcoind has this capability built in, but thought it might be fun to configure it manually. As some background, most people look at their network and they have some address like 192.168.1.105. That is a private network address. Sites like WhatIsMyIpAddress.com will tell you what your EXTERNAL IP address is. When your running a bitcoin node, people will connect to your external IP.
Problem is... your ISP may cycle that IP address every week or so. bitcoind has a nice feature baked in called discover which will do the work of guessing your external IP as it changes. But if you are doing anything where you need to expose your RPC API externally (*danger*) then it would be nice to have some FQDN to go after to do the IP translation.
Originally, I had always solved this by exposing my node as an onion node. Since onion nodes traverse NATs and firewalls fairly effortlessly this was an easy option. But previously I had played around with Dynamic DNS service. I've used noip.com but there are likely dozens of services out there that will get the job done.
Once you have enabled a NoIP hostname, you can name it in your bitcoin.conf using the externalip=coolbtcnode.ddns.net. Then, assuming you setup all the RPC auth and port forwarding, you could access your node via RPC at coolbtcnode.ddns.net
As I said... it's a redundancy, since discover=1 does most of this for you, but still thought someone might enjoy the tip.
References:
submitted by brianddk to Bitcoin [link] [comments]

Where does the Bitcoin-QT options dialog store options

When running Bitcoin-QT, there is an options dialog you can get to in the GUI under Settings. I've played with some of these settings and they don't store where I would expect. I've run some tests, on Windows 10, and it they are not housed in the bitcoin.conf file. What's more the settings persist if you change named conf files.
Is it housed in the registry or some other file on the filesystem?
submitted by brianddk to Bitcoin [link] [comments]

[ANN][ANDROID MINING][AIRDROP] NewEnglandcoin: Scrypt RandomSpike

New England
New England 6 States Songs: https://www.reddit.com/newengland/comments/er8wxd/new_england_6_states_songs/
NewEnglandcoin
Symbol: NENG
NewEnglandcoin is a clone of Bitcoin using scrypt as a proof-of-work algorithm with enhanced features to protect against 51% attack and decentralize on mining to allow diversified mining rigs across CPUs, GPUs, ASICs and Android phones.
Mining Algorithm: Scrypt with RandomSpike. RandomSpike is 3rd generation of Dynamic Difficulty (DynDiff) algorithm on top of scrypt.
1 minute block targets base difficulty reset: every 1440 blocks subsidy halves in 2.1m blocks (~ 2 to 4 years) 84,000,000,000 total maximum NENG 20000 NENG per block Pre-mine: 1% - reserved for dev fund ICO: None RPCPort: 6376 Port: 6377
NewEnglandcoin has dogecoin like supply at 84 billion maximum NENG. This huge supply insures that NENG is suitable for retail transactions and daily use. The inflation schedule of NengEnglandcoin is actually identical to that of Litecoin. Bitcoin and Litecoin are already proven to be great long term store of value. The Litecoin-like NENG inflation schedule will make NewEnglandcoin ideal for long term investment appreciation as the supply is limited and capped at a fixed number
Bitcoin Fork - Suitable for Home Hobbyists
NewEnglandcoin core wallet continues to maintain version tag of "Satoshi v0.8.7.5" because NewEnglandcoin is very much an exact clone of bitcoin plus some mining feature changes with DynDiff algorithm. NewEnglandcoin is very suitable as lite version of bitcoin for educational purpose on desktop mining, full node running and bitcoin programming using bitcoin-json APIs.
The NewEnglandcoin (NENG) mining algorithm original upgrade ideas were mainly designed for decentralization of mining rigs on scrypt, which is same algo as litecoin/dogecoin. The way it is going now is that NENG is very suitable for bitcoin/litecoin/dogecoin hobbyists who can not , will not spend huge money to run noisy ASIC/GPU mining equipments, but still want to mine NENG at home with quiet simple CPU/GPU or with a cheap ASIC like FutureBit Moonlander 2 USB or Apollo pod on solo mining setup to obtain very decent profitable results. NENG allows bitcoin litecoin hobbyists to experience full node running, solo mining, CPU/GPU/ASIC for a fun experience at home at cheap cost without breaking bank on equipment or electricity.
MIT Free Course - 23 lectures about Bitcoin, Blockchain and Finance (Fall,2018)
https://www.youtube.com/playlist?list=PLUl4u3cNGP63UUkfL0onkxF6MYgVa04Fn
CPU Minable Coin Because of dynamic difficulty algorithm on top of scrypt, NewEnglandcoin is CPU Minable. Users can easily set up full node for mining at Home PC or Mac using our dedicated cheetah software.
Research on the first forked 50 blocks on v1.2.0 core confirmed that ASIC/GPU miners mined 66% of 50 blocks, CPU miners mined the remaining 34%.
NENG v1.4.0 release enabled CPU mining inside android phones.
Youtube Video Tutorial
How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 1 https://www.youtube.com/watch?v=sdOoPvAjzlE How to CPU Mine NewEnglandcoin (NENG) in Windows 10 Part 2 https://www.youtube.com/watch?v=nHnRJvJRzZg
How to CPU Mine NewEnglandcoin (NENG) in macOS https://www.youtube.com/watch?v=Zj7NLMeNSOQ
Decentralization and Community Driven NewEnglandcoin is a decentralized coin just like bitcoin. There is no boss on NewEnglandcoin. Nobody nor the dev owns NENG.
We know a coin is worth nothing if there is no backing from community. Therefore, we as dev do not intend to make decision on this coin solely by ourselves. It is our expectation that NewEnglandcoin community will make majority of decisions on direction of this coin from now on. We as dev merely view our-self as coin creater and technical support of this coin while providing NENG a permanent home at ShorelineCrypto Exchange.
Twitter Airdrop
Follow NENG twitter and receive 100,000 NENG on Twitter Airdrop to up to 1000 winners
Graphic Redesign Bounty
Top one award: 90.9 million NENG Top 10 Winners: 500,000 NENG / person Event Timing: March 25, 2019 - Present Event Address: NewEnglandcoin DISCORD at: https://discord.gg/UPeBwgs
Please complete above Twitter Bounty requirement first. Then follow Below Steps to qualify for the Bounty: (1) Required: submit your own designed NENG logo picture in gif, png jpg or any other common graphic file format into DISCORD "bounty-submission" board (2) Optional: submit a second graphic for logo or any other marketing purposes into "bounty-submission" board. (3) Complete below form.
Please limit your submission to no more than two total. Delete any wrongly submitted or undesired graphics in the board. Contact DISCORD u/honglu69#5911 or u/krypton#6139 if you have any issues.
Twitter Airdrop/Graphic Redesign bounty sign up: https://goo.gl/forms/L0vcwmVi8c76cR7m1
Milestones
Roadmap
NENG v1.4.0 Android Mining, randomSpike Evaluation https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/NENG_2020_Q3_report/NENG_2020_Q3_report.pdf
RandomSpike - NENG core v1.3.0 Hardfork Upgrade Proposal https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2020Q1_Report/Scrypt_RandomSpike_NENGv1.3.0_Hardfork_Proposal.pdf
NENG Security, Decentralization & Valuation
https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/2019Q2_report/NENG_Security_Decentralization_Value.pdf
Whitepaper v1.0 https://github.com/ShorelineCrypto/NewEnglandCoin/releases/download/whitepaper_v1.0/NENG_WhitePaper.pdf
DISCORD https://discord.gg/UPeBwgs
Explorer
http://www.findblocks.com/exploreNENG http://86.100.49.209/exploreNENG http://nengexplorer.mooo.com:3001/
Step by step guide on how to setup an explorer: https://github.com/ShorelineCrypto/nengexplorer
Github https://github.com/ShorelineCrypto/NewEnglandCoin
Wallet
Android with UserLand App (arm64/armhf), Chromebook (x64/arm64/armhf): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.5
Linux Wallet (Ubuntu/Linux Mint, Debian/MX Linux, Arch/Manjaro, Fedora, openSUSE): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.3
MacOS Wallet (10.11 El Capitan or higher): https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0.2
Android with GNUroot on 32 bits old Phones (alpha release) wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.4.0
Windows wallet: https://github.com/ShorelineCrypto/NewEnglandCoin/releases/tag/v1.3.0.1
addnode ip address for the wallet to sync faster, frequently updated conf file: https://github.com/ShorelineCrypto/cheetah_cpumineblob/mastenewenglandcoin.conf-example
How to Sync Full Node Desktop Wallet https://www.reddit.com/NewEnglandCoin/comments/er6f0q/how_to_sync_full_node_desktop_wallet/
TWITTER https://twitter.com/newenglandcoin
REDDIT https://www.reddit.com/NewEnglandCoin/
Cheetah CPU Miner Software https://github.com/ShorelineCrypto/cheetah_cpuminer
Solo Mining with GPU or ASIC https://bitcointalk.org/index.php?topic=5027091.msg52187727#msg52187727
How to Run Two Full Node in Same Desktop PC https://bitcointalk.org/index.php?topic=5027091.msg53581449#msg53581449
ASIC/GPU Mining Pools Warning to Big ASIC Miners Due to DynDiff Algo on top of Scrypt, solo mining is recommended for ASIC/GPU miners. Further more, even for mining pools, small mining pool will generate better performance than big NENG mining pool because of new algo v1.2.x post hard fork.
The set up configuration of NENG for scrypt pool mining is same as a typical normal scrypt coin. In other word, DynDiff on Scrypt algo is backward compatible with Scrypt algo. Because ASIC/GPU miners rely on CPU miners for smooth blockchain movement, checkout bottom of "Latest News" section for A WARNING to All ASIC miners before you decide to dump big ASIC hash rate into NENG mining.
(1) Original DynDiff Warning: https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708 (2) New Warning on RandomSpike Spike difficulty (244k) introduced in RandomSpike served as roadblocks to instant mining and provide security against 51% attack risk. However, this spike difficulty like a roadblock that makes big ASIC mining less profitable. In case of spike block to be mined, the spike difficulty immediately serve as base difficulty, which will block GPU/ASIC miners effectively and leave CPU cheetah solo miners dominating mining almost 100% until next base difficulty reset.
FindBlocks http://findblocks.com/
CRpool http://crpool.xyz/
Cminors' Pool http://newenglandcoin.cminors-pool.com/
SPOOL https://spools.online/
Exchange
📷
https://shorelinecrypto.com/
Features: anonymous sign up and trading. No restriction or limit on deposit or withdraw.
The trading pairs available: NewEnglandcoin (NENG) / Dogecoin (DOGE)
Trading commission: A round trip trading will incur 0.10% trading fees in average. Fees are paid only on buyer side. buy fee: 0.2% / sell fee: 0% Deposit fees: free for all coins Withdraw fees: ZERO per withdraw. Mining fees are appointed by each coin blockchain. To cover the blockchain mining fees, there is minimum balance per coin per account: * Dogecoin 2 DOGE * NewEnglandcoin 1 NENG
Latest News Aug 30, 2020 - NENG v1.4.0.5 Released for Android/Chromebook Upgrade with armhf, better hardware support https://bitcointalk.org/index.php?topic=5027091.msg55098029#msg55098029
Aug 11, 2020 - NENG v1.4.0.4 Released for Android arm64 Upgrade / Chromebook Support https://bitcointalk.org/index.php?topic=5027091.msg54977437#msg54977437
Jul 30, 2020 - NENG v1.4.0.3 Released for Linux Wallet Upgrade with 8 Distros https://bitcointalk.org/index.php?topic=5027091.msg54898540#msg54898540
Jul 21, 2020 - NENG v1.4.0.2 Released for MacOS Upgrade with Catalina https://bitcointalk.org/index.php?topic=5027091.msg54839522#msg54839522
Jul 19, 2020 - NENG v1.4.0.1 Released for MacOS Wallet Upgrade https://bitcointalk.org/index.php?topic=5027091.msg54830333#msg54830333
Jul 15, 2020 - NENG v1.4.0 Released for Android Mining, Ubuntu 20.04 support https://bitcointalk.org/index.php?topic=5027091.msg54803639#msg54803639
Jul 11, 2020 - NENG v1.4.0 Android Mining, randomSpike Evaluation https://bitcointalk.org/index.php?topic=5027091.msg54777222#msg54777222
Jun 27, 2020 - Pre-Announce: NENG v1.4.0 Proposal for Mobile Miner Upgrade, Android Mining Start in July 2020 https://bitcointalk.org/index.php?topic=5027091.msg54694233#msg54694233
Jun 19, 2020 - Best Practice for Futurebit Moonlander2 USB ASIC on solo mining mode https://bitcointalk.org/index.php?topic=5027091.msg54645726#msg54645726
Mar 15, 2020 - Scrypt RandomSpike - NENG v1.3.0.1 Released for better wallet syncing https://bitcointalk.org/index.php?topic=5027091.msg54030923#msg54030923
Feb 23, 2020 - Scrypt RandomSpike - NENG Core v1.3.0 Relased, Hardfork on Mar 1 https://bitcointalk.org/index.php?topic=5027091.msg53900926#msg53900926
Feb 1, 2020 - Scrypt RandomSpike Proposal Published- NENG 1.3.0 Hardfork https://bitcointalk.org/index.php?topic=5027091.msg53735458#msg53735458
Jan 15, 2020 - NewEnglandcoin Dev Team Expanded with New Kickoff https://bitcointalk.org/index.php?topic=5027091.msg53617358#msg53617358
Jan 12, 2020 - Explanation of Base Diff Reset and Effect of Supply https://www.reddit.com/NewEnglandCoin/comments/envmo1/explanation_of_base_diff_reset_and_effect_of/
Dec 19, 2019 - Shoreline_tradingbot version 1.0 is released https://bitcointalk.org/index.php?topic=5121953.msg53391184#msg53391184
Sept 1, 2019 - NewEnglandcoin (NENG) is Selected as Shoreline Tradingbot First Supported Coin https://bitcointalk.org/index.php?topic=5027091.msg52331201#msg52331201
Aug 15, 2019 - Mining Update on Effect of Base Difficulty Reset, GPU vs ASIC https://bitcointalk.org/index.php?topic=5027091.msg52169572#msg52169572
Jul 7, 2019 - CPU Mining on macOS Mojave is supported under latest Cheetah_Cpuminer Release https://bitcointalk.org/index.php?topic=5027091.msg51745839#msg51745839
Jun 1, 2019 - NENG Fiat project is stopped by Square, Inc https://bitcointalk.org/index.php?topic=5027091.msg51312291#msg51312291
Apr 21, 2019 - NENG Fiat Project is Launched by ShorelineCrypto https://bitcointalk.org/index.php?topic=5027091.msg50714764#msg50714764
Apr 7, 2019 - Announcement of Fiat Project for all U.S. Residents & Mobile Miner Project Initiation https://bitcointalk.org/index.php?topic=5027091.msg50506585#msg50506585
Apr 1, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50417196#msg50417196
Mar 27, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50332097#msg50332097
Mar 17, 2019 - Disclosure on Large Buying on NENG at ShorelineCrypto Exchange https://bitcointalk.org/index.php?topic=5027091.msg50208194#msg50208194
Feb 26, 2019 - Community Project - NewEnglandcoin Graphic Redesign Bounty Initiated https://bitcointalk.org/index.php?topic=5027091.msg49931305#msg49931305
Feb 22, 2019 - Dev Policy on Checkpoints on NewEnglandcoin https://bitcointalk.org/index.php?topic=5027091.msg49875242#msg49875242
Feb 20, 2019 - NewEnglandCoin v1.2.1 Released to Secure the Hard Kork https://bitcointalk.org/index.php?topic=5027091.msg49831059#msg49831059
Feb 11, 2019 - NewEnglandCoin v1.2.0 Released, Anti-51% Attack, Anti-instant Mining after Hard Fork https://bitcointalk.org/index.php?topic=5027091.msg49685389#msg49685389
Jan 13, 2019 - Cheetah_CpuMiner added support for CPU Mining on Mac https://bitcointalk.org/index.php?topic=5027091.msg49218760#msg49218760
Jan 12, 2019 - NENG Core v1.1.2 Released to support MacOS OSX Wallet https://bitcointalk.org/index.php?topic=5027091.msg49202088#msg49202088
Jan 2, 2019 - Cheetah_Cpuminer v1.1.0 is released for both Linux and Windows https://bitcointalk.org/index.php?topic=5027091.msg49004345#msg49004345
Dec 31, 2018 - Technical Whitepaper is Released https://bitcointalk.org/index.php?topic=5027091.msg48990334#msg48990334
Dec 28, 2018 - Cheetah_Cpuminer v1.0.0 is released for Linux https://bitcointalk.org/index.php?topic=5027091.msg48935135#msg48935135
Update on Dec 14, 2018 - NENG Blockchain Stuck Issue https://bitcointalk.org/index.php?topic=5027091.msg48668375#msg48668375
Nov 27, 2018 - Exclusive for PC CPU Miners - How to Steal a Block from ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48258465#msg48258465
Nov 28, 2018 - How to CPU Mine a NENG block with window/linux PC https://bitcointalk.org/index.php?topic=5027091.msg48298311#msg48298311
Nov 29, 2018 - A Warning to ASIC Miners https://bitcointalk.org/index.php?topic=5027091.msg48324708#msg48324708
Disclosure: Dev Team Came from ShorelineCrypto, a US based Informatics Service Business offering Fee for service for Coin Creation, Coin Exchange Listing, Blockchain Consulting, etc.
submitted by honglu69 to NewEnglandCoin [link] [comments]

Test

Test
There is a fairly small subset of Bitcoin users that run a full node. I think the idea of running a full node has gotten a bad rap over the years since there is so much talk about running on a Raspberry Pi, or getting zippy SSDs. Although all of this can be fun, it is often not really required at all. Here are some ways to run a full node starting with the very simple. I'll get into more complex configs, but these are all optional.

Tech Skill Level: 0 (the basics)

  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
In many cases, thats it. If your running a new machine with a fairly good internet connection, 8 or 9 hours will be enough to complete the "Initial Block Download" (IBD). This may fill up your drive a bit, but again, on most new machines, 300 GB of space isn't that hard to come by.

Tech Skill Level: 1 (encrypted wallet)

One thing we left out in the level-0 exercise is encrypting your wallet. It's easy enough to do well, but a bit more difficult to do right. The main challenge is that humans generate really poor passwords. If you want a good password, the best way is to use something called "diceware". Basically, you just grab 4 or 5 dice and each throw of the dice represents a certain word on a special list. The throw {1,4,5,3,1} for example would be the word camping on the EFF-diceware-wordlist. So you repeat this a few times until you have a list of 8 or so words which becomes the passphrase you use to encrypt your wallet. Write it down, it is always hard to remember at first. So at level-1 your list becomes:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Choose Encrypt Wallet from the Settings Menu
  5. Enter your 8 word (or so) passphrase generated using the Diceware method

Wallet Encryption Dialog

Tech Skill Level: 2 (enable pruning if needed)

Though I said "300 GB of space isn't hard to come by", some times it actually is. If space is an issue, a simple way to fix it is to tell bitcoin to simple take less space. This is called "pruning" and can take that number from 300 GB down to below 5 GB. If you can't find 5 GB, then you'll have to read ahead to level-3 to add USB storage. But the good news is, enabling pruning is pretty easy, we just add another step to our working list:
  1. Download Bitcoin Core
  2. Launch the downloaded installer and install the app
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Choose Options from the Settings Menu
  6. Choose Prune block storage to: and select the max size for the blocks to use
  7. Exit and restart the bitcoin application for the changes to take effect

Pruning Dialog
Note, even setting this to 1 GB will still leave you with about a 4.5 GB install. The blocks take up a lot of space, but the chainstate and other folders eat up at least 3.5 GB and they can't be pruned. Also, be aware, to disable pruning requires you to perform the entire IBD again. While pruned some other functions my be disabled as well, so just know that pruning does limit some functionality.

Tech Skill Level: 3 (verify the installer)

Although this is arguably something that should be done at level-0, some find the intricacies of comparing hash (thumbprint) values to be tedious and beyond the scope of a beginner. You will find these types of hash compares suggested quite often as a way to prevent running tainted programs. Programs are often tainted by bad disk or network performance, but most often, taint is malicious code inserted by viruses or malware. This is a way to guard yourself against those types of attacks. What I cover here is a very basic comparison on the certificate, but a more thorough comparison advised by mosts uses a program called Gpg4Win, and is beyond the scope of this beginners guide. But regardless, most users should strive to do this minimum level of validation.
  1. Download Bitcoin Core
  2. Launch the downloaded installer
  3. When prompted "Do you want to allow..." click Show more details
  4. In the details section select Show information about the publisher's certificate
  5. In the certificate window select the Details tab
  6. In the Details tab Subject should start with "CN = Bitcoin Core Code Signing Association"
  7. Also ensure Thumbprint reads ea27d3cefb3eb715ed214176a5d027e01ba1ee86
  8. If the checks pass, click OK to exit the certificate window and Yes to allow the installer to run.
  9. Launch the installed "Bitcoin Core" app and let it run overnight
  10. Do the wallet encryption steps here if you wish
  11. Do the optional pruning steps here if you wish

Certification Validation Windows
Note: The certificate used to sign the current Bitcoin installer is only valid from March 2020 to March 2021. After that point the thumbprint on the certificate will change. This is by design and intentional. If your reading this post after March 2021, then it is understood that the thumbprint has changed.

Tech Skill Level: 4 (use secondary storage)

We glossed over the "new machine with fairly good internet" part. Truth me known many people do not have fairly new machines, and find the IBD to take longer than the "over night" best wishes. For most people the slowdown is the disk access when calculating what is called chainstate. This requires fast random reads and writes to the disk. If you have an SSD disk, this will be no problem, but if you have a non-SSD "spinning" disk, random writes are always slow. Though an SSD will speed things up, they are pricey, so a nice middle ground may be a simple high-end USB key drive. You can get some with 10 to 15 MB/s random writes which is usually a order of magnitude faster than a "spinning" disk. And with pruning (see level-2), a small USB drive should be fine.
Once you decide on a drive, the tricky part will be to enable external storage. It requires editing a configuration file and adding a few lines. The configuration file needs to be in both the default directory, and USB key drive, but before we do that, we want to create a directory on the key drive. You will need to determine the drive letter of your USB key drive. For the sake of this example, we will assume it is D:, but you must determine this yourself and correct the example. Once you know the drive letter, create a blank folder on the drive called Bitcoin. So for this example, creating Bitcoin on drive D: will create the path D:\Bitcoin. Once done, assuming that D: is your drive, here are the steps to edit the two configuration files:
  1. Download Bitcoin Core
  2. Launch the installer, verify it, then run it
  3. Launch the installed "Bitcoin Core" app and let it run overnight
  4. Do the wallet encryption steps here if you wish
  5. Do the optional pruning steps here if you wish
  6. Launch "Notepad" by typing "Notepad.exe" in the windows search bar then click Open
  7. Type the line datadir=D:\Bitcoin (depending on your drive letter) in the blank file
  8. Choose Save from the File menu in notepad
  9. Type %APPDATA%\Bitcoin\bitcoin.conf (note the percent signs) in the File name box
  10. Select All Files from the Save as type dropdown
  11. Click the Save button and overwrite the file if prompted
  12. Exit and restart the bitcoin application for the changes to take effect

Save As Dialog
Now that you've reached this level of technical expertise, there are many new configuration options that you can begin to modify if you wish. Most configuration data is contained in the bitcoin.conf file and learning how to maintain it is a key step for a node operator.

Tech Skill Level: 5 (all other customizations)

Here's a short list of various things you can ADD to your bitcoin.conf file. You generally just add a new line for each configuration settings.
  • addresstype=bech32
  • changetype=bech32
The addresstype / changetype allows your wallet to use the native-segwit (bech32) format. This is the most efficient and inexpensive way to spend bitcoin, and is a recommended configuration. The default uses something called p2sh-segwit which is more compatible with older wallets, but more expensive to spend.
  • minrelaytxfee=0.00000011
Changing the minrelaytxfee setting allows you to help propagate lower fee transactions. It will require more memory but TXN memory is capped at 300 MB by default anyways, so if you have enough memory, it is a good setting to choose.
  • dbcache=2048
The dbcache setting controls how many MB of memory the program will use for the chainstate database. Since this is a key bottleneck in the IBD, setting this value high (2048 MB) will greatly speed up the IBD, assuming you have the memory to spare
  • blocksdir=C:\Bitcoin
  • datadir=D:\Bitcoin
In level-4 we discussed moving the datadir to a fast external storage, but the majority of the space used for bitcoin is the blocks directory (blocksdir). Although you should always use for fastest storage for datadir, you are free to use slow storage for blocksdir. So if you only want to consume a small amount of your SSD (assumed D:) then you can keep your blocks on your slow "spinning" drive.
  • upnp=1
One of the harder challenges you may face running a node, is to get incoming connections. If you are lucky, you may find that your firewall and network HW support the uPnP protocol. If they do, this setting will allow bitcoin to configure uPnP to allow incoming connections to your node.
submitted by brianddk to brianddk [link] [comments]

Bitcoin Tor

Subject: PSA: Make your node reachable by using Tor
There is usually a post every few months with someone asking for tips on how to make their node reachable. It's always a hard question to answer since its impossible to know what type of routers and firewalls they are going to have to punch through. This is especially difficult in college dorms. One cheap (and easy) way around it is to to just jump through a few extra steps to make your bitcoin node a bitcoin onion node. Tor is great about traversing routers and firewalls like a hot knife through butter.
  1. Download, verify1, install and initialize Gpg4win
  2. Download, verify2, install, and launch Tor Browser
  3. Download, verify3, install, and launch Bitcoin Core
  4. Launch an Admin command console in the directory with tor.exe
  5. Install the Tor service: tor.exe --service install
  6. CD to service dir: cd %windir%\ServiceProfiles\LocalService\AppData\Roaming\tor
  7. Create and edit a file called torrc with the contents suggested below
  8. Restart tor: tor --service stop && tor --service start
  9. Record your onion hostname: type .\HiddenService\hostname as
  10. Add the bitcoin.conf options suggested below
  11. Restart the bitcoin-qt program
  12. Verify node connectivity at https://bitnodes.io/nodes/-8333/

torrc file: (replace c:\windows with the proper path as needed)

```

Change to C:\Windows\ServiceProfiles\LocalService\AppData\Roaming

Log notice file \tor\service.log HiddenServiceDir \tor\HiddenService HiddenServiceVersion 2 HiddenServicePort 8333 127.0.0.1:8333 HiddenServicePort 18333 127.0.0.1:18333 ```

bitcoin.conf file: (entries to be ADDED)

```

Change to what you recorded earlier

onion=127.0.0.1:9050 listen=1 externalip= discover=1 ```
Footnotes:
  • 1 - Cert-Subject: "Intevation GmbH"  ;  Cert-SHA1: c13a65963ad53e78694dd223d518007791a05fe4
  • 2 - PGP Signing Key: 0xEF6E286DDA85EA2A4BA7DE684E2C6E8793298290
  • 3 - PGP Signing Key: 0x01EA5486DE18A882D4C2684590C8019E36C2E964
submitted by brianddk to brianddk [link] [comments]

When BTC moon rockets stuck at launch pad again and again. Bitcoin Cash have created a whole new world waiting for us. I paid BCH and get my digital content every 10 seconds. No registration, no more waiting, only enjoying your purchase. This is real P2P electronic cash Satoshi expecting

When BTC moon rockets stuck at launch pad again and again. Bitcoin Cash have created a whole new world waiting for us. I paid BCH and get my digital content every 10 seconds. No registration, no more waiting, only enjoying your purchase. This is real P2P electronic cash Satoshi expecting

Instant Buy Continuously
This is not a visual special effects. This is real P2P digital cash use-case. Like using physical cash, we paid with cash then we got commodities. No more hassles.
I have created a digital P2P market which allows creators selling their digital artworks without registration and high service-fee, and peoples can buy what they want item by item. No registration, no subscription, no personal information required. Pick the images, music, video, documents and file you love, then buy it and download it. That's all.
Let's see more examples:Buy images https://youtu.be/6my6CeFUzzs https://wall.cash/List-Image
Buy Video https://youtu.be/SPYLDzMcYno https://wall.cash/List-Video
Buy Music https://youtu.be/5lw--YcQmC0 https://wall.cash/List-Music
Buy Document https://youtu.be/HgKf-iEADOI https://wall.cash/CashPort-314
You can check it by yourself.
It releases the power of real P2P electronic cash, such as instantly 0-conf purchase, https://bitcointalk.org/index.php?topic=423.msg3836#msg3836 small casual payment, https://bitcoin.org/bitcoin.pdf peer-to-peer, worldwide and more~
This website, CashBay, is still under testing, if you are interested you can check it at http://cashbay.cash/ or https://wall.cash/ However, there will be bugs I still need to fix them all.
The Pizza Day is coming, I will officially launch CashBay on Pizza Day, the day make Bitcoin as Cash. More innovative features of CashBay, such as PayWindow and CamCashifier are comming. Please wait and see.
Disclaimer: The demo videos are from Bitcoin.com. The receiving address is controlled by Bitcoin.com used for CashFusion Security Audit Fund. If you paid, your BCH will go directly to Bitcoin.com.
submitted by DiemosChen to btc [link] [comments]

How To Stake/Mine Coinevo

EVO Staking/Evo mining

Evo uses Proof of Stake consensus mechanism, which is different from Bitcoin's PoW (Proof of Work). Evo mining process in PoS system is called staking. The block producer will get 6.5EVO, as well as the transaction fees and gases as block reward. So the real reward is usually more than 6.5 evo in total.
Basic requirements for staking:
  1. Run a Coinevo fullnode, and keep online (Since Coinevo is using PoS, we don't need any mining machine, just PC or even Raspberry Pi can run a fullnode);
  2. Have some EVO in the wallet (fullnode)(Any amount of EVO can be used for staking, more EVO means higher possibility to stake).
If you have no EVO yet, please get some from market before you doing following staking settings.
Currently, Coinevo Core wallet is the only wallet that support Coinevo PoS staking. Note that other wallets like mobile wallet and Evo Electrum are not able to stake for the time being.
Two ways to stake:
Either way works in the same way for staking, so you can choose either method you like.

Method 1:Staking with evod (command line)

1. Run evod

Follow the guidance to run evod :
./evod -daemon 
Staking is default on for evod, so no need for other options if you only want to stake.

2. Send some EVO to your wallet

First you can generate a new address with:
./evo-cli getnewaddress 
This will generate a new address with Prefix '1'. You can send some EVO to this new generated address for staking. You can generate as many addresses as you like, and send arbitrary EVO as you like for staking.
Note:The coin should wait for 500 blocks before being able to stake, i.e. about 17 to 24 hours to MATURE..
After the EVO node syncing to the latest block, you can check current balance with ./evo-cli getbalance or get utxo list with./evo-cli listunspent
Please do following steps after your coin is mature.

3. Check staking info

Check current staking info with:
./evo-cli getstakinginfo 
You might get the result like this:
{ "enabled": true, "staking": true, "errors": "", "currentblocktx": 0, "pooledtx": 0, "difficulty": 3693409.779133397, "search-interval": 1577, "weight": 309584575558555, "netstakeweight": 1948540143266404, "expectedtime": 805 } 
enabled means if your wallet have enabled staking, it should be true by default. staking means if your wallet is currently staking (mining). weight stands for the amount of EVO that is staking right now, with unit 10^-8EVO, here in the example, we have 0.532EVO staking. expectedtime stands for the expected time that you will get a reward, the unit is second.

4. How to stake if the wallet is encrypted?

If your wallet is not encrypted, you can skip this section. However, for security, we recommand you encrypt your wallet.
Coinevo wallet can be encrypted with encryptwallet . However, staking will be stopped when it is encrypted. For example, ./evo-cli getstakinginfo for a encrypted wallet:
{ "enabled": true, "staking": false, "errors": "", "currentblocksize": 1000, "currentblocktx": 0, "pooledtx": 94, "difficulty": 5788429.670171153, "search-interval": 0, "weight": 53206430, "netstakeweight": 2438496688951881, "expectedtime": 0 } 
See staking turns to false , which means wallet is not staking.
You can use walletpassphrase to unlock wallet for staking:
./evo-cli walletpassphrase "" 99999999 true 
After unlocking, you can double check getstakinginfo , it should look the same with previous unlocked result, staking become true.

Method 2: Staking with evo-qt wallet (official PC wallet)

Current supported platform: Mac/Linux/Windows.

1. Open Evo qt wallet

Launch the wallet.

2. Send some EVO to your wallet

If you already have some EVO in your wallet, you might skip this step.
Note:The coin should wait for 500 blocks before being able to stake, i.e. about 17 to 24 hours to MATURE..

3. Check staking status

The flash sign at the bottom of wallet shows staking info :
Solid black flash means it is staking now. For more information, you can put your mouse on the flash, e.g.:
Hollow flash measn it is not staking
Possible reasons for not staking:
No flash sign means staking is disabled

About block reward

The block producer will get more than 6.5 EVO rewards, something to keep in mind:

How to disable staking?

Staking is by default enabled for Coinevo wallet. If you need to disable staking for some reason (for example exchanges are always recommanded to disable staking), you might following anyone of the 3 ways below:
1 Add -staking=false when running Coinevo node:
./evod -staking=false -daemon 
For qt wallet, it is like:
./evo-qt -staking=false 
2 Add config staking=false in evo.conf;
3 Encrypt wallet, since encrypted wallet will automatically stop staking.
submitted by coinevo to u/coinevo [link] [comments]

Connecting Eclair to Bitcoin Core | Code: -5 error

Hello
I am having trouble getting eclair to connect to my full node.
im running eclair 0.3.4 and bitcoin core 0.19.1 (i was running 0.19.01 but updated when i saw the "Current number of transactions" said N/A in the information window)
I launch eclair-node-gui while bitcoin core is running (core is synced and has been running for an hour so mempool will be filled)
Core says transactions are about 6k and memory usage is ~12MB
However, I get error code: -5 on eclair:
Error: NO such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions.
I have txindex=1 in the conf of core. ( can show my configs if it helps, i got them right from the gethub)
I entered gettransaction into the core Console but im not sure if it really does anything
https://imgur.com/a/P39yIFU
Im not a coder by any means, so bear with me. Also when i updated Bitcoin Core from 0.19.01 to 0.19.1, i ran the setup exe downloaded from bitcoin.org and it recognized and is using the blocks destination folder that 0.19.01 was running off of, if that makes a difference.
I also posted this in lightningnetwork
Thanks!
submitted by wumbis to Bitcoin [link] [comments]

Connecting Eclair to Bitcoin Core | Code: -5 error

Hello
I am having trouble getting eclair to connect to my full node.
im running eclair 0.3.4 and bitcoin core 0.19.1 (i was running 0.19.01 but updated when i saw the "Current number of transactions" said N/A in the information window)
I launch eclair-node-gui while bitcoin core is running (core is synced and has been running for an hour so mempool will be filled)
Core says transactions are about 6k and memory usage is ~12MB
However, I get error code: -5 on eclair:
Error: NO such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions.
Couldnt find any info on this in the eclair gethub
I have txindex=1 in the conf of core. ( can show my configs if it helps, i got them right from the gethub)
I entered gettransaction into the core Console but im not sure if it really does anything
https://imgur.com/a/P39yIFU
Im not a coder by any means, so bear with me. Also when i updated Bitcoin Core from 0.19.01 to 0.19.1, i ran the setup exe downloaded from bitcoin.org and it recognized and is using the blocks destination folder that 0.19.01 was running off of, if that makes a difference.
If there is somewhere better for this post please let me know. I also posted on bitcoin
Thanks!
submitted by wumbis to lightningnetwork [link] [comments]

I found a $600k BCH theft that has gone unnoticed

Hello all, I'm (among other things) a graduate student getting a master's degree in cybersecurity. This last quarter for one of my classes, I was tasked to examine and recreate an exploit. For the actual exploit I was examining the "anyone can spend" segwit addresses on the BCH chain, and in my research I found a $600k theft that seems to have gone completely unnoticed.
You all might recall this $600k theft of segwit addresses, but it happened again in mid-February 2018 and there has been zero news about it.
BCH block 517171 contains solely segwit-stealing transactions. If you look at any given transaction, the inputs are all segwit program hashes spending a P2SH segwit output. I only caught it by accident, as I was originally going to talk about the publicized November attack.
The interesting thing I discovered about this was that it's harder to have stolen that segwit money than most people think. Both Unlimited and ABC nodes do not relay segwit-spending transactions, and Bitcoin ABC hard-coded in fRequireStandard, so you couldn't even force-relay them with a conf option. On top of that, miners keep their node IPs private for obvious avoiding-ddos-and-sybil-attack reasons, which means it's impossible to directly send transactions to miners. This means that the only way to actually execute this attack was to setup one's own mining pool running on a custom-modified client to allow non-standard transactions. Then you'd have to get enough hash power to mine a block yourself. I estimated the cost of renting enough hash power to do this at the time as around $30k-$60k to have a greater than 90% chance of mining a block within a 3 month window.
In order to simulate the attack, I spun up BTC, LTC, and BCH nodes in Docker, and wrote a Python script. The Python script started at segwit activation on BTC and LTC and it scanned every transaction in every block looking for P2SH segwit inputs as well as native segwit outputs, since these are the necessary hash pre-images to spend P2SH segwit money on the BCH chain. The script then also scanned the BCH chain for any native segwit outputs, as well as recording all P2SH outputs. (This was all saved in a MySQL database.) Then, at any point in time, I could simply query for BCH unspent native segwit outputs as well as P2SH outputs for which I had a known segwit hash pre-image. (If this was an attack I was doing real-time, I would probably also have a large mempool on each node and monitor unconfirmed tx's for useful info as well, but since this was after the fact, I just queried blocks sequentially.)
For the mining node that runs the pool, it would need to be firewalled behind (i.e. only connected to) an unmodified node in blocks-only mode, so that the segwit hash pre-images aren't transmitted out to the network, and so that no other unconfirmed transactions are transmitted in to the mining node. (The mining node should only be filling its block with segwit tx's in order to maximize the gain from the attack.)
Then a script should run continuously to grab segwit utxos from the MySQL database and construct high-fee transactions to send directly to the mining node. Unlike the November attack, each input should be spent in its own individual transaction, so that in the event it is individually spent, I don't negate a tx with other inputs. The overhead on having different transactions for each input is only about 8 extra bytes (the tx version and the locktime), so I think this is a good trade-off.
Then, the attacker simply rents hashing power and points it at his secret pool.
By the time February rolled around and the attack happened, my MySQL database had about 40 million BCH P2SH outputs and each query took about 3 minutes to execute. This of course would have been fine in the 10-minute block world of Bitcoin and BCH, but it means that I stopped my Python script after that time, so I don't know about any possible other attacks that happened before the clean stack rule was hard-forked into BCH.
It was pretty interesting to work through how this attack must have happened, and it was significantly harder to execute than I thought it would be given that all the money was "anyone can spend".
However, the most interesting thing about all this is that nobody has noticed. There is literally no news or mention of block 517171 or any of the transactions in it. My theory is that it is money that nobody misses -- i.e. misprogrammed custom wallet software for BTC nodes accidentally also sent out BCH transactions to the same address, given that BTC and BCH shared the same history until August 2017. And whatever person or entity is running those nodes is only thinking about BTC money and is completely oblivious to its misprogrammed problem of shipping BCH to segwit P2SH addresses.
Obviously, that's just a theory, but I think it's pretty reasonable. Given the intense community divide, I think it's very possible that a number of BTC users simply ignored money on the BCH chain, even though it's "free money" for them, simply out of ideological hatred.
Whatever the case, nobody has posted anywhere complaining of money stolen in that block. It seems to have gone completely unnoticed. (Which is why I'm posting this.) It was an interesting case study and I'd be curious to hear if anybody has any addition information or thoughts about it. I believe this was a different person than the November theft, because the way it was done was different -- the November theft had all the money in one transaction, but this February theft was done with separate individual transactions. Additionally worth noting is that the address which received the bulk of the money is still active, which means they're still out there.
Anyway, I thought this was interesting and worth posting.
submitted by exmachinalibertas to btc [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 configure cgminer - Windows mining tutorial - YouTube MultiMiner for Cryptocurrencies on Windows [BFGMiner ... MultiMiner for Cryptocurrencies on Windows BFGMiner Bitcoin Weekly Show GUIMiner Installation and configuration bitcoin-cli and bitcoind - Breaking Down Bitcoin Ep. 2

Note that for Windows the location of the configuration folder where bitcoin.conf is located is saved in the registry. Its default path is indeed C:\Users\<username>\AppData\Roaming\Bitcoin but if that location was changed then in order to find the current folder you will have to look in HKEY_CURRENT_USER\Software\Bitcoin\Bitcoin-Qt at the REG_SZ strDataDir . Bitcoin.conf Configuration File. All command-line options (except for -conf) may be specified in a configuration file, and all configuration file options may also be specified on the command line. Command-line options override values set in the configuration file. The configuration file is a list of setting=value pairs, one per line, with optional comments starting with the '#' character. The ... Next in save as type choose All Files (*.*) and the filename should be coinname.conf. Note: It is .conf and not .conf.txt or .config or .cnf or .cng. That’s it! Your config file is ready! Now you need to place this file into the relevant wallet data directory where you’ll find files and folders such as: wallet.dat, peers.dat, debug, blocks ... Bitcoind – a daemon program that implements the Bitcoin protocol, is controlled through the command line. It is one of the main components of the Bitcoin network node software. Bitcoin software exists in two forms: a GUI application and a background application (daemon on Unix, service on Windows). Platform Config for Windows. Windows; Linux; Mac OS; expand_more Bitcoin Core. Basic parameters regarding Bitcoin Core node operation. Alert Notification Execute command when an alert (or long fork) is received (%s in cmd is replaced by message) Block Filter Index Disable compact filters. Disable; Enable All; Basic Filters; Block Notification Execute command when the best block changes (%s in ...

[index] [24560] [18073] [18222] [17287] [30116] [7297] [46073] [10570] [33538] [7919]

How to configure cgminer - Windows mining tutorial - YouTube

MultiMiner for ALL cryptocurrencies! LATEST VERSION: 3.0.1 ----- Bitcointalk: https://bitcointalk.org/index.... We cover chapter 3 of Andreas Antonopoulos' book Mastering Bitcoin. Featured are examples of bitcoin-cli commands, and simple Python scripts to interact with the bitcoin blockchain. Referenced links: Newbie guide for those who want to try solo bitcoin and litecoin mining, using bfgminer and cgminer. The config files shown in the video are available in the... In this video I show you how to start mining Bitcoins with CGMiner and an account at your favorite miningpool. Get CGMiner at: https://bitcointalk.org/index.... BFGMiner on Windows Setup Guide for Bitcoin Users + ASIC Miner Setup Bitcoin Weekly Show - Duration: 6:54. cxboy 84,814 views. 6:54. Guide on using the BBT Multi-Miner v5.6.1 Anyone can mine ...

#