You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
-106Lines changed: 0 additions & 106 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,112 +8,6 @@ Kryptokrona is a decentralized blockchain from the Nordic based on CryptoNote, w
8
8
9
9
This is a project to convert the legacy C/C++ code of Kryptokrona into Rust.
10
10
11
-
## Table of Contents <!-- omit in toc -->
12
-
13
-
-[Development Resources](#development-resources)
14
-
-[Getting Help](#getting-help)
15
-
-[Reporting Issues](#reporting-issues)
16
-
-[Versioning](#versioning)
17
-
-[Checklist before release](#checklist-before-release)
18
-
-[Help and Support](#help-and-support)
19
-
-[Copypasta for license when adding new files](#copypasta-for-license-when-adding-new-files)
20
-
-[Contributors](#contributors)
21
-
-[License](#license)
22
-
23
-
## Development Resources
24
-
25
-
- Web: kryptokrona.org
26
-
- Docs: https://docs.kryptokrona.org
27
-
- GitHub: https://github.com/kryptokrona
28
-
- Hugin: Kryptokrona group on Hugin Messenger `33909fb89783fb15b5c2df50ff7107c112c3b232681f77814c024c909c07e932`r
29
-
- It is HIGHLY recommended to join our board on Hugin Messenger if you want to contribute to stay up to date on what is happening on the project.
30
-
- 𝕏: https://x.com/kryptokrona
31
-
32
-
## Getting Help
33
-
34
-
Are you having trouble with Kryptokrona? We want to help!
35
-
36
-
- Read through all documentation on our Wiki: https://docs.kryptokrona.org
37
-
38
-
- If you are upgrading, read the release notes for upgrade instructions and "new and noteworthy" features.
39
-
40
-
- Ask a question we monitor stackoverflow.com for questions tagged with kryptokrona. You can also chat with the community on Hugin or Discord.
41
-
42
-
- Report bugs with Kryptokrona at https://github.com/kryptokrona/kryptokrona-rs/issues.
43
-
44
-
- Join the Discussion and be part of the community at Discord: https://discord.gg/VTgsTGS9b7
45
-
46
-
## Reporting Issues
47
-
48
-
Kryptokrona 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:
49
-
50
-
- Before you log a bug, please search the issue tracker to see if someone has already reported the problem.
51
-
52
-
- If the issue doesn’t already exist, create a new issue.
53
-
54
-
- Please provide as much information as possible with the issue report. We like to know the Kryptokrona version, operating system, and JVM version you’re using.
55
-
56
-
- If you need to paste code or include a stack trace, use Markdown. ``` escapes before and after your text.
57
-
58
-
- If possible, try to create a test case or project that replicates the problem and attach it to the issue.
59
-
60
-
## Versioning
61
-
62
-
Kryptokrona uses [Semantic Versioning Standard 2.0.0](https://semver.org/).
63
-
64
-
Given a version number MAJOR.MINOR.PATCH, increment the:
65
-
66
-
- MAJOR version when you make incompatible API changes
67
-
- MINOR version when you add functionality in a backwards compatible manner
68
-
- PATCH version when you make backwards compatible bug fixes
69
-
70
-
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
71
-
72
-
## Checklist before release
73
-
74
-
1. Edit versions in `Cargo.toml` files.
75
-
2. Create PR and wait for review + merge.
76
-
3. Create a tag on master `git tag v*.*.*`
77
-
4. Push the changes `git push origin <tag_name>` to trigger a new build and to publish to various package managers.
78
-
79
-
## Help and Support
80
-
81
-
For questions and support please use the channel #support in [Kryptokrona](https://discord.gg/mkRpVgDubC) Discord server. The issue tracker is for bug reports and feature discussions only.
82
-
83
-
## Copypasta for license when adding new files
84
-
85
-
Hi Kryptokrona contributor, thanks for forking and sending back Pull Requests. Extensive docs about contributing are in the works or elsewhere. For now this is the bit we need to get into all the files we touch. Please add it to the top of the files, see `src/wallet_api/main.rs` for an example.
86
-
87
-
```
88
-
// Copyright (c) 2025, The Kryptokrona Project
89
-
//
90
-
// All rights reserved.
91
-
//
92
-
// Redistribution and use in source and binary forms, with or without modification, are
93
-
// permitted provided that the following conditions are met:
94
-
//
95
-
// 1. Redistributions of source code must retain the above copyright notice, this list of
96
-
// conditions and the following disclaimer.
97
-
//
98
-
// 2. Redistributions in binary form must reproduce the above copyright notice, this list
99
-
// of conditions and the following disclaimer in the documentation and/or other
100
-
// materials provided with the distribution.
101
-
//
102
-
// 3. Neither the name of the copyright holder nor the names of its contributors may be
103
-
// used to endorse or promote products derived from this software without specific
104
-
// prior written permission.
105
-
//
106
-
// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
107
-
// EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
108
-
// MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
109
-
// THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
110
-
// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
111
-
// PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
112
-
// INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
113
-
// STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
114
-
// THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
0 commit comments