Skip to content

Commit

Permalink
Klimatas upgrade to latest PIVX version
Browse files Browse the repository at this point in the history
  • Loading branch information
CryptoDev-Project committed Mar 2, 2019
1 parent 3f45fd2 commit b989de7
Show file tree
Hide file tree
Showing 1,721 changed files with 214,154 additions and 1,300,338 deletions.
20 changes: 10 additions & 10 deletions CONTRIBUTING.md
@@ -1,7 +1,7 @@
Contributing to Klimatas Core
Contributing to KTS Core
============================

The Klimatas Core project operates an open contributor model where anyone is
The KTS Core project operates an open contributor model where anyone is
welcome to contribute towards development in the form of peer review, testing
and patches. This document explains the practical process and guidelines for
contributing.
Expand Down Expand Up @@ -57,12 +57,12 @@ the pull request affects. Valid areas as:

- *Consensus* for changes to consensus critical code
- *Docs* for changes to the documentation
- *Qt* for changes to trttium-qt
- *Qt* for changes to kts-qt
- *Minting* for changes to the minting code
- *Net* or *P2P* for changes to the peer-to-peer network code
- *RPC/REST* for changes to the RPC or REST APIs
- *Scripts and tools* for changes to the scripts and tools
- *Tests* for changes to the trttium unit tests or QA tests
- *Tests* for changes to the kts unit tests or QA tests
- *Trivial* should **only** be used for PRs that do not change generated
executable code. Notably, refactors (change of function arguments and code
reorganization) and changes in behavior should **not** be marked as trivial.
Expand Down Expand Up @@ -157,10 +157,10 @@ where possible keep them short, un-complex and easy to verify.
"Decision Making" Process
-------------------------

The following applies to code changes to the Klimatas Core project, and is not to be
confused with overall Klimatas Network Protocol consensus changes.
The following applies to code changes to the KTS Core project, and is not to be
confused with overall KTS Network Protocol consensus changes.

Whether a pull request is merged into Klimatas Core rests with the project merge
Whether a pull request is merged into KTS Core rests with the project merge
maintainers and ultimately the project lead.

Maintainers will take into consideration if a patch is in line with the general
Expand All @@ -174,7 +174,7 @@ In general, all pull requests must:
- be well peer reviewed;
- follow code style guidelines;

Patches that change Klimatas consensus rules are considerably more involved than
Patches that change KTS consensus rules are considerably more involved than
normal because they affect the entire ecosystem and so must be preceded by
extensive discussions and clear detailing. While each case will be different,
one should be prepared to expend more time and effort than for other kinds of
Expand Down Expand Up @@ -214,7 +214,7 @@ higher in terms of discussion and peer review requirements, keeping in mind that
mistakes could be very costly to the wider community. This includes refactoring
of consensus critical code.

Where a patch set proposes to change the Klimatas consensus, it must have been
Where a patch set proposes to change the KTS consensus, it must have been
discussed extensively on the forums and Slack, be accompanied by a widely
discussed Proposal and have a generally widely perceived technical consensus of being
a worthwhile change based on the judgement of the maintainers.
Expand Down Expand Up @@ -254,7 +254,7 @@ about:
Release Policy
--------------

The project leader is the release manager for each Klimatas Core release.
The project leader is the release manager for each KTS Core release.

Copyright
---------
Expand Down
4 changes: 1 addition & 3 deletions COPYING
@@ -1,8 +1,6 @@
Copyright (c) 2009-2015 Bitcoin Developers
Copyright (c) 2014-2015 Dash Developers
Copyright (c) 2015-2017 The PIVX Developers
Copyright (c) 2018 The Klimatas Developers

Copyright (c) 2015-2019 KTS Developers

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
Expand Down
6 changes: 3 additions & 3 deletions INSTALL
@@ -1,4 +1,4 @@
Building Trttium
Building KTS

Use the autogen script to prepare the build environment.

Expand All @@ -8,6 +8,6 @@ Use the autogen script to prepare the build environment.

Always verify the signatures and checksums.

See doc/build-*.md for instructions on building trttiumd,
See doc/build-*.md for instructions on building ktsd,
the intended-for-services, no-graphical-interface, reference
implementation of Trttium.
implementation of KTS.
21 changes: 0 additions & 21 deletions LICENSE

This file was deleted.

0 comments on commit b989de7

Please sign in to comment.