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
  • Issues
  • #88

Closed
Open
Created Dec 13, 2017 by Artem B@artemOwner3 of 3 tasks completed3/3 tasks

Use InstantSend by default to validate transactions

Motivation

We want to push using the InstantSend feature. It's the first step in the direction of the new distributed consensus mechanism.

Proposal

  • Research. Analyze transactions fee policy. We need to agree on fair InstantSend transaction fee. It must not be too high, and not too low at the same time to provide security and Masternodes incentive. 2 d.
  • Set using InstantSend by default. 8 d.
  • See if split out debug text from InstantSend feature to go to it's own debug log.

Links/references

Possible solutions

Edited May 01, 2018 by Ashot
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking