forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Marconi Pereira Soldate
committed
Jan 5, 2025
1 parent
6fa761f
commit a3b9405
Showing
1 changed file
with
15 additions
and
67 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,79 +1,27 @@ | ||
| Bitcoin Core integration/staging tree | ||
| Nióbio - A criptomoeda brasileira | ||
| ===================================== | ||
|
|
||
| https://bitcoincore.org | ||
| https://niobiocoin.com.br | ||
|
|
||
| For an immediately usable, binary version of the Bitcoin Core software, see | ||
| https://bitcoincore.org/en/download/. | ||
| Tecnicamente é um clone perfeito do Bitcoin. | ||
| Apenas as portas são diferentes (8333 no bitcoin ficam 8433 no nióbio) e os checkpoints iniciais. | ||
| As outras portas seguem o mesmo padrão, ou seja, apenas o primeiro '3' é substituído por '4'. | ||
|
|
||
| What is Bitcoin Core? | ||
| Porque um clone? | ||
| --------------------- | ||
|
|
||
| Bitcoin Core connects to the Bitcoin peer-to-peer network to download and fully | ||
| validate blocks and transactions. It also includes a wallet and graphical user | ||
| interface, which can be optionally built. | ||
| A tecnologia do Bitcoin se mostrou resiliente e aceita por todos de forma geral. | ||
| Criar uma nova moeda, uma nova tecnologia, é estar sujeito a centenas, talvez milhares de bugs. | ||
| Isso dificulta a listagem por exchanges e, portanto, a adoção da moeda pelas pessoas. | ||
|
|
||
| Further information about Bitcoin Core is available in the [doc folder](/doc). | ||
| Ao utilizar um clone perfeito do Bitcoin, as exchanges e usuários já sabem utilizar a tecnologia. | ||
| Além disso, para onde o bitcoin for, fica mais fácil segui-lo, basta usar os recusros do git para mantê-lo sempre atualizado. | ||
|
|
||
| License | ||
| ------- | ||
|
|
||
| Bitcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more | ||
| information or see https://opensource.org/licenses/MIT. | ||
|
|
||
| Development Process | ||
| ------------------- | ||
|
|
||
| The `master` branch is regularly built (see `doc/build-*.md` for instructions) and tested, but it is not guaranteed to be | ||
| completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created | ||
| regularly from release branches to indicate new official, stable release versions of Bitcoin Core. | ||
| Na pior das hipóteses, o nióbio servirá como aprendizado para as pessoas utilizarem o bitcoin, já que provavelmente será bem mais barato, tanto em termos de preço quanto de custo de transação. | ||
|
|
||
| The https://github.com/bitcoin-core/gui repository is used exclusively for the | ||
| development of the GUI. Its master branch is identical in all monotree | ||
| repositories. Release branches and tags do not exist, so please do not fork | ||
| that repository unless it is for development reasons. | ||
|
|
||
| The contribution workflow is described in [CONTRIBUTING.md](CONTRIBUTING.md) | ||
| and useful hints for developers can be found in [doc/developer-notes.md](doc/developer-notes.md). | ||
|
|
||
| Testing | ||
| TODO | ||
| ------- | ||
|
|
||
| Testing and code review is the bottleneck for development; we get more pull | ||
| requests than we can review and test on short notice. Please be patient and help out by testing | ||
| other people's pull requests, and remember this is a security-critical project where any mistake might cost people | ||
| lots of money. | ||
|
|
||
| ### Automated Testing | ||
|
|
||
| Developers are strongly encouraged to write [unit tests](src/test/README.md) for new code, and to | ||
| submit new unit tests for old code. Unit tests can be compiled and run | ||
| (assuming they weren't disabled during the generation of the build system) with: `ctest`. Further details on running | ||
| and extending unit tests can be found in [/src/test/README.md](/src/test/README.md). | ||
|
|
||
| There are also [regression and integration tests](/test), written | ||
| in Python. | ||
| These tests can be run (if the [test dependencies](/test) are installed) with: `build/test/functional/test_runner.py` | ||
| (assuming `build` is your build directory). | ||
|
|
||
| The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, | ||
| and that unit/sanity tests are run automatically. | ||
|
|
||
| ### Manual Quality Assurance (QA) Testing | ||
|
|
||
| Changes should be tested by somebody other than the developer who wrote the | ||
| code. This is especially important for large or high-risk changes. It is useful | ||
| to add a test plan to the pull request description if testing the changes is | ||
| not straightforward. | ||
|
|
||
| Translations | ||
| ------------ | ||
|
|
||
| Changes to translations as well as new translations can be submitted to | ||
| [Bitcoin Core's Transifex page](https://www.transifex.com/bitcoin/bitcoin/). | ||
|
|
||
| Translations are periodically pulled from Transifex and merged into the git repository. See the | ||
| [translation process](doc/translation_process.md) for details on how this works. | ||
| Para aumentar a segurança, talvez seja melhor alterar o algoritmo de mineração. | ||
| (Talvez trocar o duplo SHA-256 por um triplo, por exemplo) | ||
|
|
||
| **Important**: We do not accept translation changes as GitHub pull requests because the next | ||
| pull from Transifex would automatically overwrite them again. |