diff --git a/doc/README.md b/doc/README.md --- a/doc/README.md +++ b/doc/README.md @@ -84,7 +84,7 @@ - [Developer Notes](developer-notes.md) - [Release Notes](release-notes.md) - [Release Process](release-process.md) -- [Source Code Documentation (External Link)](https://dev.visucore.com/bitcoin/doxygen/) +- [Source Code Documentation (External Link)](https://www.bitcoinabc.org/doc/dev/) - [Translation Process](translation_process.md) - [Translation Strings Policy](translation_strings_policy.md) - [Unauthenticated REST Interface](REST-interface.md) diff --git a/doc/REST-interface.md b/doc/REST-interface.md --- a/doc/REST-interface.md +++ b/doc/REST-interface.md @@ -52,7 +52,7 @@ The getutxo command allows querying of the UTXO set given a set of outpoints. See BIP64 for input and output serialisation: -https://github.com/bitcoin/bips/blob/master/bip-0064.mediawiki + Example: ``` diff --git a/doc/translation_process.md b/doc/translation_process.md --- a/doc/translation_process.md +++ b/doc/translation_process.md @@ -108,4 +108,4 @@ ### Questions and general assistance The Bitcoin-Core translation maintainers include *tcatm, seone, Diapolo, wumpus and luke-jr*. You can find them, and others, in the Freenode IRC chatroom - `irc.freenode.net #bitcoin-core-dev`. -If you are a translator, you should also subscribe to the mailing list, https://groups.google.com/forum/#!forum/bitcoin-translators. Announcements will be posted during application pre-releases to notify translators to check for updates. +If you are a translator, you should also subscribe to the mailing list, . Announcements will be posted during application pre-releases to notify translators to check for updates. diff --git a/src/seeder/README.md b/src/seeder/README.md --- a/src/seeder/README.md +++ b/src/seeder/README.md @@ -17,7 +17,7 @@ REQUIREMENTS ------------ -$ sudo apt-get install build-essential libboost-all-dev libssl-dev + sudo apt-get install build-essential libboost-all-dev libssl-dev USAGE ----- @@ -26,17 +26,17 @@ need an authoritative NS record in example.com's domain record, pointing to for example vps.example.com: -$ dig -t NS dnsseed.example.com + dig -t NS dnsseed.example.com -;; ANSWER SECTION -dnsseed.example.com. 86400 IN NS vps.example.com. + ;; ANSWER SECTION + dnsseed.example.com. 86400 IN NS vps.example.com. On the system vps.example.com, you can now run dnsseed: -./bitcoin-seeder -host=dnsseed.example.com -ns=vps.example.com + ./bitcoin-seeder -host=dnsseed.example.com -ns=vps.example.com If you want the DNS server to report SOA records, please provide an -e-mail address (with the @ part replaced by .) using -mbox. +e-mail address (with the `@` part replaced by `.`) using `-mbox`. RUNNING AS NON-ROOT @@ -47,10 +47,10 @@ One solution is using an iptables rule (Linux only) to redirect it to a non-privileged port: -$ iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-port 5353 + iptables -t nat -A PREROUTING -p udp --dport 53 -j REDIRECT --to-port 5353 If properly configured, this will allow you to run dnsseed in userspace, using -the -port=5353 option. +the `-port=5353` option. Generate Seed Lists -------------------