Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
silkaj
silkaj
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 165
    • Issues 165
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • clients
  • python
  • silkajsilkaj
  • Issues
  • #327

Closed
Open
Created Jun 30, 2020 by matograine@matograineMaintainer

limit recipients number for 0.8 (discussion)

For 0.8, we plan to release the feature "multiple recipients". However, this feature introduces a possible bug (#281 (closed)). With max 40 inputs, the created transaction document may be too big if there are more than 15 outputs = 14 receivers + 1 backchange. This bug is not harmful, no money is sent when it happens.

max_outputs = 100 - 3 - 2 x SENDERS - 2 x MAX_OUTPUTS = 100-3-(2x1)-(2x40) = 15

Should we :

  • leave this bug open (it never happened with the developpers funding account, which seems to be the only one exceeding the limit of 15)
  • add a MAX_RECEIVERS = 14 limit, with an error message telling the user to spend the money with littler receivers list.

Since 0.8 is to be released in Debian repos, I would rather add the MAX_RECEIVERS limit to avoid this bug ; and go on fixing it on 0.8.x if we have time, or 0.9+ if not.

Edited Jul 01, 2020 by matograine
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
0.8.x
Milestone
0.8.x
Assign milestone
Time tracking
None
Due date
None