Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Wiki
  • Home

Last edited by Mark Brooker Jan 07, 2020
Page history

Home

Welcome to the Crown Core Development homepage!

This source code can also be found on our public GitHub page here: https://github.com/Crowndev

Please read the Code of Conduct before contributing!

Weekly Developer Meeting video call can be accessed on Zoom:

  • Thursday, 1 PM UTC, 15-30 min.

Content

  • Community
  • Developers
  • InSource Community Job Board
  • Builds
  • Training Videos
  • Announcement Responsibilities
  • Quality Assurance
  • Documents
  • Coding style guide
  • Research
  • Documents and Drawings
  • Superblock generation
  • Instant Send
  • Governance Competition Analysis
  • Release Management
  • Pre-release & post-release tasks

Development

When describing a bug please include following information: (needs to be updated to match the Bug template file)

  • Issue summary - an issue header which outlines the actual defect to be solved
  • Product - for example Desktop Wallet x64, Windows 10
  • Build Found In - for example 0.13.4.0; this is very important as you may be using an old build and the issue may already have been resolved.
  • Steps to reproduce - the steps to recreate exactly how the error occurred when you found the issue
  • Expected behaviour - what you would expect to see instead of the issue; this can be useful as it may trigger a conversation between yourself and the developer (or the team) about a better fix or possible solutions.
  • Actual behaviour - describe the symptoms of the bug and what happened before and after.

Bounties

Crown core developers are working hard on bug fixes, platform enhancements, and new product features. Some of these tasks may be completed by talented community members through the bounty program. Bounties are posted to this wiki on the Bounties page and can be picked up by anyone who wants to submit new code to the project repository.

If you're interested in working on any bounty issues please contact us in Discord.

Clone repository
  • 19.01.18 Testnet Fork Report
  • Credentials for electrumx servers
  • How to turn on off enforcement
  • Quality Assurance
  • Quality Assurance
    • Instant Send Testing
    • documents
  • Seed nodes
  • bounties
  • code of conduct
  • coding style guide
  • communications & marketing
  • community
  • community
    • Announcement Responsibilities
    • Developers
    • community built
View All Pages