Kryptokrona is a decentralized blockchain from the Nordic based on CryptoNote, which forms the basis for Monero, among others. CryptoNote is a so-called “application layer” protocol further developed by TurtleCoin that enables things like: private transactions, messages and arbitrary data storage, completely decentralized.
The kryptokrona payment processor is written in node.JS. Its used to implement simple XKR payments to websites
- Web: https://kryptokrona.org
- Docs: https://docs.kryptokrona.org
- Mail: techy@novastack.org
- GitHub: https://github.com/kryptokrona/kryptokrona-payment-processor-js
- Discord: https://discord.gg/VTgsTGS9b7
- Twitter: https://twitter.com/TechyGuy17
Are you having trouble with Kryptokrona payment processor? We want to help!
-
If you are upgrading, read the release notes for upgrade instructions and "new and noteworthy" features.
-
Ask a question we monitor stackoverflow.com for questions tagged with kryptokrona-payment-processor-js. You can also chat with the community on Hugin or Discord.
-
Report bugs with Kryptokrona payment processor at https://github.com/kryptokrona/kryptokrona-payment-processor-js/issues.
Kryptokrona payment processor uses GitHub’s integrated issue tracking system to record bugs and feature requests. If you want to raise an issue, please follow the recommendations below:
-
Before you log a bug, please search the issue tracker to see if someone has already reported the problem.
-
If the issue doesn’t already exist, create a new issue.
-
Please provide as much information as possible with the issue report. We like to know the Kryptokrona payment processor version, operating system, and node version you’re using.
-
If you need to paste code or include a stack trace, use Markdown. ``` escapes before and after your text.
-
If possible, try to create a test case or project that replicates the problem and attach it to the issue.
If you would like to contribute to this project there is two ways:
- Send a pull request
- Donate to XKR address
We appreciate all contributions whether it be small changes such as documentation of source code to major improvement of code. The easiest way is to make a fork and then make a pull request into our develop branch.
To make the PR go through make sure to include this information:
What does this PR do?
Why are these changes required?
This PR has been tested using (e.g. Unit Tests, Manual Testing):
Extra details?
NOTE: Remember to update existing diagrams if there is some bigger improvements of code so it's up to date with the implementation.
XKR: SEKReTq5Qoi3tch2zi3AD35xmhzrv6iBxVcPnfrqHv6PdHKEN3cdBm5aGxn7HLUq3d8xC2ZENrxCkQhT7mp2rjEdeqBMzjLup7x
The following contributors have either helped to start this project, have contributed code, are actively maintaining it (including documentation), or in other ways being awesome contributors to this project. We'd like to take a moment to recognize them.
The 3-Clause BSD License.
