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 154
    • Issues 154
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards

Mise à jour effectuée, merci de nous signaler tout dysfonctionnement ! | Upgrade done, please let us know about any dysfunction!

  • clients
  • python
  • silkajsilkaj
  • Issues
  • #239

Closed
Open
Opened Jul 24, 2019 by Moul@moulOwner

Successive tx do not enter the blockchain: pendings wrongly calulated

Successive transactions made from same pubkey for the remuneration of Duniter developers.

First one passes, than, the other one are accepted by the network, but do not enter the blockchain.

Pending transactions is no longer well counted. There might be a deprecation during DuniterPy migration

@Insoleet comment:


Du coup je renvoie les tx. Ya vraiment un drole de bug avant/après sur la clé publique :

Do you confirm sending this transaction? [yes/no]: no
╒════════════════════════════╤══════════════════════════════════════════════╕
│ pubkey’s balance before tx │ 16490.61 Ğ1                                  │
├────────────────────────────┼──────────────────────────────────────────────┤
│ tx amount (unit)           │ 600.0 Ğ1                                     │
├────────────────────────────┼──────────────────────────────────────────────┤
│ tx amount (relative)       │ 59.5829 UD Ğ1                                │
├────────────────────────────┼──────────────────────────────────────────────┤
│ pubkey’s balance after tx  │ 15890.61 Ğ1                                  │
├────────────────────────────┼──────────────────────────────────────────────┤
│ from (pubkey)              │ 78ZwwgpgdH5uLZLbThUQH7LKwPgjMunYfLiCfUCySkM8 │
├────────────────────────────┼──────────────────────────────────────────────┤
│ to (pubkey)                │ 85VuNitZHjtoVUY9GZcPsq4EZrWf8VUeQQmobBvrM1jH │
├────────────────────────────┼──────────────────────────────────────────────┤
│ comment                    │ SERVER-07-2019                               │
╘════════════════════════════╧══════════════════════════════════════════════╛
Do you confirm sending this transaction? [yes/no]: yes
Generate Transaction:
   - From:    78ZwwgpgdH5uLZLbThUQH7LKwPgjMunYfLiCfUCySkM8
   - To:      85VuNitZHjtoVUY9GZcPsq4EZrWf8VUeQQmobBvrM1jH 
   - Amount:  600.0
Transaction successfully sent.
╒════════════════════════════╤══════════════════════════════════════════════╕
│ pubkey’s balance before tx │ 21651.61 Ğ1                                  │
├────────────────────────────┼──────────────────────────────────────────────┤
│ tx amount (unit)           │ 1080.0 Ğ1                                    │
├────────────────────────────┼──────────────────────────────────────────────┤
│ tx amount (relative)       │ 107.2493 UD Ğ1                               │
├────────────────────────────┼──────────────────────────────────────────────┤
│ pubkey’s balance after tx  │ 20571.61 Ğ1                                  │
├────────────────────────────┼──────────────────────────────────────────────┤
│ from (pubkey)              │ 78ZwwgpgdH5uLZLbThUQH7LKwPgjMunYfLiCfUCySkM8 │
├────────────────────────────┼──────────────────────────────────────────────┤
│ to (pubkey)                │ 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ │
├────────────────────────────┼──────────────────────────────────────────────┤
│ to (id)                    │ cgeek                                        │
├────────────────────────────┼──────────────────────────────────────────────┤
│ comment                    │ SERVER-07-2019                               │
╘════════════════════════════╧══════════════════════════════════════════════╛
Do you confirm sending this transaction? [yes/no]: 

La balance passe de 16490.61 Ğ1 à 21651.61 Ğ1 après envoi.

En regardant la balance de la clé :

silkaj balance 78ZwwgpgdH5uLZLbThUQH7LKwPgjMunYfLiCfUCySkM8
Blockchain:
-----------
Relative     = 1637.6 UD Ğ1
Quantitative = 16490.61 Ğ1

Pending Transaction:
--------------------
Relative     = 512.51 UD Ğ1
Quantitative = 5161.0 Ğ1

Total amount of: 78ZwwgpgdH5uLZLbThUQH7LKwPgjMunYfLiCfUCySkM8
----------------------------------------------------------------
Total Relative     = 2150.11 UD Ğ1
Total Quantitative = 21651.61 Ğ1
Total Relative to average money share = 5.38 × M/N
Total Relative to monetary mass       = 0.252 % M

On voit clairement le problème apparaître je crois : le montant calculé sur la blockchain est toujours à la valeur précédente, mais silkaj ajoute les sources retours qui sont sur la clé publique à ce montant. Il y a donc des sources qui sont dupliquées, faussant le calcul (et générant des sources à double dépense).

Edited Jul 25, 2019 by Moul
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
0.7.x
Milestone
0.7.x
Assign milestone
Time tracking
None
Due date
None
Reference: clients/python/silkaj#239