Updating docs 🎉
This commit is contained in:
parent
aeafd56215
commit
77563156c7
|
@ -28,13 +28,13 @@ DOXYFILE_ENCODING = UTF-8
|
|||
# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
|
||||
# by quotes) that should identify the project.
|
||||
|
||||
PROJECT_NAME = Bitcoin
|
||||
PROJECT_NAME = Dogecoin
|
||||
|
||||
# The PROJECT_NUMBER tag can be used to enter a project or revision number.
|
||||
# This could be handy for archiving the generated documentation or
|
||||
# if some version control system is used.
|
||||
|
||||
PROJECT_NUMBER = 0.11.0
|
||||
PROJECT_NUMBER = 1.10.0
|
||||
|
||||
# Using the PROJECT_BRIEF tag one can provide an optional one line description
|
||||
# for a project that appears at the top of each page and should give viewer
|
||||
|
|
|
@ -3,7 +3,7 @@ Dogecoin Core 1.10
|
|||
|
||||
Setup
|
||||
---------------------
|
||||
[Dogecoin Core](http://dogecoin.com/ is the reference Dogecoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Dogecoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more.
|
||||
[Dogecoin Core](http://dogecoin.com/) is the reference Dogecoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Dogecoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more.
|
||||
|
||||
Running
|
||||
---------------------
|
||||
|
@ -35,7 +35,7 @@ Drag Dogecoin-Qt to your applications folder, and then run Dogecoin-Qt.
|
|||
* See the documentation at the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page)
|
||||
for help and more information.
|
||||
* Ask for help on [#dogecoin](http://webchat.freenode.net?channels=dogecoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net?channels=dogecoin).
|
||||
* Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Technical Support board](https://bitcointalk.org/index.php?board=4.0).
|
||||
* Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Dogecoin thread](https://bitcointalk.org/index.php?topic=361813.0).
|
||||
|
||||
Building
|
||||
---------------------
|
||||
|
@ -61,8 +61,8 @@ The Dogecoin repo's [root README](https://github.com/dogecoin/dogecoin/blob/mast
|
|||
- [Dnsseed Policy](dnsseed-policy.md)
|
||||
|
||||
### Resources
|
||||
* Discuss on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Development & Technical Discussion board](https://bitcointalk.org/index.php?board=6.0).
|
||||
* Discuss on [#dogecoin-dev](http://webchat.freenode.net/?channels=dogecoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=dogecoin-dev).
|
||||
* Discuss on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Dogecoin thread](https://bitcointalk.org/index.php?topic=361813.0).
|
||||
* Discuss on [#dogecoin-dev](http://webchat.freenode.net/?channels=dogecoin-dev) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=dogecoin-dev).
|
||||
|
||||
### Miscellaneous
|
||||
- [Assets Attribution](assets-attribution.md)
|
||||
|
|
|
@ -18,6 +18,6 @@ However, it downloads and stores the entire history of Dogecoin transactions;
|
|||
depending on the speed of your computer and network connection, the synchronization
|
||||
process can take anywhere from a few hours to a day or more.
|
||||
|
||||
See the bitcoin wiki at:
|
||||
https://en.bitcoin.it/wiki/Main_Page
|
||||
See the Dogecoin wiki at:
|
||||
https://www.reddit.com/r/dogecoin/wiki/dogecoincoreguide
|
||||
for more help and information.
|
||||
|
|
|
@ -51,4 +51,4 @@ situations but should be discussed in public in advance.
|
|||
|
||||
See also
|
||||
----------
|
||||
- [dogecoin-seeder](https://github.com/sipa/dogecoin-seeder) is a reference implementation of a DNS seed.
|
||||
- [dogecoin-seeder](https://github.com/langerhans/dogecoin-seeder) is a reference implementation of a DNS seed.
|
||||
|
|
|
@ -392,5 +392,4 @@ Uploading signatures
|
|||
---------------------
|
||||
|
||||
After building and signing you can push your signatures (both the `.assert` and `.assert.sig` files) to the
|
||||
[dogecoin/gitian.sigs](https://github.com/dogecoin/gitian.sigs/) repository, or if that's not possible create a pull
|
||||
request. You can also mail the files to Wladimir (laanwj@gmail.com) and he will commit them.
|
||||
[dogecoin/gitian.sigs](https://github.com/dogecoin/gitian.sigs/) repository, or if that's not possible create a pull request.
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
Multiwallet Qt Development and Integration Strategy
|
||||
===================================================
|
||||
|
||||
In order to support loading of multiple wallets in bitcoin-qt, a few changes in the UI architecture will be needed.
|
||||
In order to support loading of multiple wallets in dogecoin-qt, a few changes in the UI architecture will be needed.
|
||||
Fortunately, only four of the files in the existing project are affected by this change.
|
||||
|
||||
Two new classes have been implemented in two new .h/.cpp file pairs, with much of the functionality that was previously
|
||||
|
@ -12,7 +12,7 @@ some major retrofitting.
|
|||
|
||||
Only requiring some minor changes is bitcoin.cpp.
|
||||
|
||||
Finally, two new headers and source files will have to be added to bitcoin-qt.pro.
|
||||
Finally, two new headers and source files will have to be added to dogecoin-qt.pro.
|
||||
|
||||
Changes to class BitcoinGUI
|
||||
---------------------------
|
||||
|
@ -32,7 +32,7 @@ merges while reducing the risk of breaking top-level stuff.
|
|||
|
||||
Changes to bitcoin.cpp
|
||||
----------------------
|
||||
bitcoin.cpp is the entry point into bitcoin-qt, and as such, will require some minor modifications to provide hooks for
|
||||
bitcoin.cpp is the entry point into dogecoin-qt, and as such, will require some minor modifications to provide hooks for
|
||||
multiple wallet support. Most importantly will be the way it instantiates WalletModels and passes them to the
|
||||
singleton BitcoinGUI instance called window. Formerly, BitcoinGUI kept a pointer to a single instance of a WalletModel.
|
||||
The initial change required is very simple: rather than calling `window.setWalletModel(&walletModel);` we perform the
|
||||
|
|
|
@ -153,4 +153,4 @@ Note: check that SHA256SUMS itself doesn't end up in SHA256SUMS, which is a spur
|
|||
|
||||
- Add release notes for the new version to the directory `doc/release-notes` in git master
|
||||
|
||||
- Celebrate
|
||||
- To the moon!
|
||||
|
|
|
@ -1,5 +1,5 @@
|
|||
TOR SUPPORT IN BITCOIN
|
||||
======================
|
||||
TOR SUPPORT IN DOGECOIN
|
||||
=======================
|
||||
|
||||
It is possible to run Dogecoin as a Tor hidden service, and connect to such services.
|
||||
|
||||
|
|
Loading…
Reference in a new issue