mirandacoin

Created: 2014-05-19 18:31
Updated: 2014-06-04 18:35
License: mit

README.md

PesetaCoin integration/staging tree

http://www.pesetacoin.info

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers Copyright (c) 2014 PesetaCoin Developers

Que es PesetaCoin?

ESPECIFICACIONES

  • Algoritmo Scrypt (POW)
  • Número total de monedas: 166,386,000 PTCs
  • 166(.386) monedas por bloque (bajando a la mitad cada año)
  • Block target: 1 minuto
  • Cambio de dificultad: Dinamico con Kimoto Gravity Well
  • Con soporte para Merged Mining
  • RPC Port: 16638
  • P2P Port: 16639

Compilación sin entorno gráfico:

Ejecutar:

cd src
make -f makefile.unix (makefile.osx para mac o makefile.mingw para windows)

Compilación con entorno gráfico:

ejecutar:

qmake-qt4 -makefile -Wall USE_QRCODE=1
make 

License

PesetaCoin is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Litecoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Litecoin.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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 for new code, and to submit new unit tests for old code.

Unit tests for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro
make -f Makefile.test
./pesetacoin-qt_test
Cookies help us deliver our services. By using our services, you agree to our use of cookies Learn more