duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2017-11-26T13:55:24+01:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1161Nœud isolé du réseau avec multiples erreurs2017-11-26T13:55:24+01:00Cédric MoreauNœud isolé du réseau avec multiples erreurs*Created by: LeoBoudet*
**Par ordre chronologique :**
- Sans aucune intervention préalable de ma part, j'ai d'abord eu de nombreux “Wrong endpoint” (à chaque vérification nodulaire), tous soldés par un échec ("error"). Cela a fait su...*Created by: LeoBoudet*
**Par ordre chronologique :**
- Sans aucune intervention préalable de ma part, j'ai d'abord eu de nombreux “Wrong endpoint” (à chaque vérification nodulaire), tous soldés par un échec ("error"). Cela a fait suite à un enchaînement de “Too high difficulty” après calcul d’un bloc.
Ce qui semble avoir entraîné une déconnexion du réseau (et donc arrêt de calcul de blocs) pendant deux jours.
-> Je remarque que les problèmes ont commencé à l’apparition d’un nouveau fichier de logs (que j'ai toujours actuellement).
Visiblement ma clé publique ou ma signature numérique a commencé à être rejetée :
**> WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE**
Les logs ne correspondaient d’ailleurs pas à ceux qui apparaissaient dans les logs en temps réel de l’interface.
- Et j’ai également ensuite eu ce message d’erreur :
**>WS2P OUT => Document detected 2 times: "version":10,"currency":"g1","status":"UP"...**
Après réinitialisation complète du nœud (qui m'a été automatiquement demandée au redémarrage du nœud, peut-être afin de rattraper tout le retard accumulé) et quelques bidouilles sur l’interface :
- enregistrement de ma clé seulement prise en compte après redémarrage de l'ordinateur (Duniter continuait d'utiliser la clé par défaut obtenue à l'installation).
- après un calcul dans le vide sans peer connecté, j'ai ouvert la BMA, cela a semble-t-il permis de connecter des nœuds. Un message d'erreur est cependant apparu m'indiquant que je n'étais plus visible sur le réseau (alors qu'à mon sens, il s'agissait du contraire), un simple clic sur "Automatic configuration" l'a fait disparaître tout en fermant la BMA mais en gardant la connexion aux nœuds.
... depuis mon nœud semble fonctionner normalement.
À noter que dans la version précédente, un bloc de plus avait été considéré comme calculé (16 au lieu de 15 après réinitialisation).
Désolé pour la forme, je ne sais pas ce qui a pu se passer, je manque de maîtrise de Duniter sur ce sujet.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1183Champs inutilisés en base de données2017-11-28T16:49:16+01:00Cédric MoreauChamps inutilisés en base de donnéesÀ la lecture du [Chapitre 7 - Base de données](https://duniter.org/fr/wiki/duniter/tutoriel-dev/chapitre-7-bdd/) du tuto de dev, on s'aperçoit qu'il y a plusieurs champs des tables de piscine qui ne sont plus exploitées.
Ces champs ne...À la lecture du [Chapitre 7 - Base de données](https://duniter.org/fr/wiki/duniter/tutoriel-dev/chapitre-7-bdd/) du tuto de dev, on s'aperçoit qu'il y a plusieurs champs des tables de piscine qui ne sont plus exploitées.
Ces champs ne servent plus, ils peuvent être supprimés.
Il faut tout de même vérifier avec les tests que cela est bien vrai (j'ai moi-même fait des recherches avant de noter l'inutilité de ces champs), mais ensuite il faut les retirer et mettre à jour le Chapitre 7 en conséquence.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1102WS2P: prevent JSON injection2017-11-28T16:49:16+01:00Cédric MoreauWS2P: prevent JSON injectionWS2P parses received JSON. We need to take a big care on the received JSON because it could carry invalid content.WS2P parses received JSON. We need to take a big care on the received JSON because it could carry invalid content.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/945Allow to pass level argument to logs sub-command2017-11-28T16:49:16+01:00Cédric MoreauAllow to pass level argument to logs sub-command*Created by: M5oul*
Like:
```bash
duniter logs --loglevel trace
```*Created by: M5oul*
Like:
```bash
duniter logs --loglevel trace
```Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/789Rewrite tests for duniter-bma2017-11-28T16:49:16+01:00Cédric MoreauRewrite tests for duniter-bma2 test files are commented and needs to be rewritten to pass2 test files are commented and needs to be rewritten to passHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/944Move wiki documentation on git repository2017-11-28T16:49:16+01:00Cédric MoreauMove wiki documentation on git repository*Created by: M5oul*
…on `doc` folder.
Then close `Wiki` on the settings.
This could avoid loss of documentation.*Created by: M5oul*
…on `doc` folder.
Then close `Wiki` on the settings.
This could avoid loss of documentation.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/813Network problems in duniter-desktop-0.90.4 & -0.90.62017-11-28T16:49:16+01:00Cédric MoreauNetwork problems in duniter-desktop-0.90.4 & -0.90.6*Created by: Fatsie*
I'm still having network problems in duniter desktop.
My config:
* running in a container with local ip address 10.0.7.2 port 8999, this IP is not routable on the internat only on the LAN.
* have firewall with IP...*Created by: Fatsie*
I'm still having network problems in duniter desktop.
My config:
* running in a container with local ip address 10.0.7.2 port 8999, this IP is not routable on the internat only on the LAN.
* have firewall with IPv4 address 178.238.229.211 with NAT port forwarding of 8999 to 10.0.7.2:8999; firewall does not support UPnP
* container has no IPv6 network config (yet)
* This is in conf.json:
> "port": 8999,
> "ipv4": "10.0.7.2",
> "upnp": false,
> "remotehost": null,
> "remoteipv4": "178.238.229.211",
> "remoteport": 8999,
Server seems to be running: http://178.238.229.211:8999/network/peering
Duniter says network is not reachable:
![home_2017-01-28_12-05-36](https://cloud.githubusercontent.com/assets/11200448/22396159/a5eb4cb6-e552-11e6-8b54-e255a577fec5.png)
Network settings seem to be OK in GUI:
![netsettings_2017-01-28_12-07-15](https://cloud.githubusercontent.com/assets/11200448/22396166/b709bfe6-e552-11e6-8d92-6698edbfd34b.png)
Cesium can't show currency information:
![currency_2017-01-28_12-07-46](https://cloud.githubusercontent.com/assets/11200448/22396170/c6ab6e40-e552-11e6-81f8-c2681d53f55a.png)
nor 'My Account':
![cesiummyaccount_2017-01-28_12-08-30](https://cloud.githubusercontent.com/assets/11200448/22396187/087a75c8-e553-11e6-883e-b3083adfa694.png)
This is a node upgraded from 0.80.x after 'Full reset of the node' in Settings->DATA from the GUI.
https://git.duniter.org/nodes/typescript/duniter/-/issues/1100Allow certification cancelling2017-11-28T16:49:16+01:00Cédric MoreauAllow certification cancellingThe discussion is here: https://forum.duniter.org/t/annulation-de-certification/3233
It is still being discussed.The discussion is here: https://forum.duniter.org/t/annulation-de-certification/3233
It is still being discussed.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/928gtest and g1 nodes communicating2017-11-28T16:49:16+01:00insogtest and g1 nodes communicatingHello,
I just saw the following logs in sakia :
```
DEBUG:network:handle_new_node:Stacking new peer document : 77mfxsDcX8JZKHD9fBC9wNtM1R7Yj3WA27DsY7kyrePX
DEBUG:network:discovery_loop:New node found : 77mfx
DEBUG:network:disco...Hello,
I just saw the following logs in sakia :
```
DEBUG:network:handle_new_node:Stacking new peer document : 77mfxsDcX8JZKHD9fBC9wNtM1R7Yj3WA27DsY7kyrePX
DEBUG:network:discovery_loop:New node found : 77mfx
DEBUG:network:discovery_loop:Error : Node is working for gtest currency, but should be g1
```
What do you think about it ?https://git.duniter.org/nodes/typescript/duniter/-/issues/859Systematically error + dumped2017-11-28T16:49:16+01:00Cédric MoreauSystematically error + dumped*Created by: galuel*
J'ai toujours un plantage sous Ubuntu 64 bits, lors du premier lancement de duniter-desktop, depuis tout le temps je crois bien. J'y ai pas trop porté d'attention, car au deuxième lancement ça fonctionne généralemen...*Created by: galuel*
J'ai toujours un plantage sous Ubuntu 64 bits, lors du premier lancement de duniter-desktop, depuis tout le temps je crois bien. J'y ai pas trop porté d'attention, car au deuxième lancement ça fonctionne généralement...
$ duniter-desktop
2017-03-01T12:36:23+01:00 - debug: Plugging file system...
2017-03-01T12:36:23+01:00 - debug: Loading conf...
2017-03-01T12:36:24+01:00 - debug: Configuration saved.
2017-03-01T12:36:24+01:00 - debug: Opening SQLite database "/home/galuel/.config/duniter/duniter_default/duniter.db"...
2017-03-01T12:36:24+01:00 - debug: Upgrade database...
2017-03-01T12:36:24+01:00 - info: Duniter server listening on http://192.168.0.77:30118
2017-03-01T12:36:24+01:00 - info: UPnP: configuring...
2017-03-01T12:36:24+01:00 - trace: UPnP: mapping external port 30118 to local 30118...
2017-03-01T12:36:24+01:00 - info: Crawling the network...
2017-03-01T12:36:24+01:00 - info: Pulling blocks from the network...
2017-03-01T12:36:25+01:00 - trace: Checking if node DZRR5W is UP... (88.190.82.70:30118)
2017-03-01T12:36:25+01:00 - info: Sibling endpoints:
2017-03-01T12:36:25+01:00 - trace: Try with 90.9.227.204:8999 7iBkcy
2017-03-01T12:36:25+01:00 - info: Crawling done.
2017-03-01T12:36:25+01:00 - info: External access: 88.190.82.70:30118
2017-03-01T12:36:25+01:00 - debug: Generating server's peering entry based on block#8697...
2017-03-01T12:36:26+01:00 - error:
Abandon (core dumped)
- deuxième lancement :
$ duniter-desktop
2017-03-01T12:36:44+01:00 - debug: Plugging file system...
2017-03-01T12:36:45+01:00 - debug: Loading conf...
2017-03-01T12:36:45+01:00 - debug: Configuration saved.
2017-03-01T12:36:45+01:00 - debug: Opening SQLite database "/home/galuel/.config/duniter/duniter_default/duniter.db"...
2017-03-01T12:36:45+01:00 - debug: Upgrade database...
2017-03-01T12:36:45+01:00 - info: Duniter server listening on http://192.168.0.77:30118
2017-03-01T12:36:45+01:00 - info: UPnP: configuring...
2017-03-01T12:36:45+01:00 - trace: UPnP: mapping external port 30118 to local 30118...
2017-03-01T12:36:45+01:00 - info: Crawling the network...
2017-03-01T12:36:45+01:00 - info: Pulling blocks from the network...
2017-03-01T12:36:46+01:00 - info: Crawling done.
2017-03-01T12:36:46+01:00 - debug: Will check that node DZRR5W (88.190.82.70:30118) is UP in 1440 min...
2017-03-01T12:36:46+01:00 - info: Sibling endpoints:
2017-03-01T12:36:46+01:00 - trace: Try with 90.9.227.204:8999 7iBkcy
2017-03-01T12:36:46+01:00 - info: External access: 88.190.82.70:30118
2017-03-01T12:36:46+01:00 - debug: Generating server's peering entry based on block#8698...
2017-03-01T12:36:46+01:00 - info: Changing conf to: {"prefix":10} on engine#1
2017-03-01T12:36:46+01:00 - info: Changing conf to: {"prefix":10} on engine#2
2017-03-01T12:36:46+01:00 - info: Next peering signal in 10 min
2017-03-01T12:36:46+01:00 - warn: Waitinghttps://git.duniter.org/nodes/typescript/duniter/-/issues/717PB Installation de duniter-desktop sous debian 64 virtualisé virtualbox sous ...2017-11-28T16:49:16+01:00Cédric MoreauPB Installation de duniter-desktop sous debian 64 virtualisé virtualbox sous windows*Created by: bou2fil*
Problème instal sur noeud duniter-desktop sur vm virtualbox debian jessie 64bit, machine hote : windows 10 64 bit
Après avoir installé le paquet Duniter 0.50.2 avec gdebi sous root, j'ai lancé en tapant : dunite...*Created by: bou2fil*
Problème instal sur noeud duniter-desktop sur vm virtualbox debian jessie 64bit, machine hote : windows 10 64 bit
Après avoir installé le paquet Duniter 0.50.2 avec gdebi sous root, j'ai lancé en tapant : duniter-desktop
, il y a la fenetre graphique qui bloque sur du noir et le terminal affiche des trucs ci-dessous :
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
2016-11-17T17:10:04+01:00 - debug: Opening SQLite database "/home/fil/.config/duniter/duniter_default/duniter.db"...
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171004:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
[1739:1739:1117/171005:ERROR:gles2_cmd_decoder.cc(2291)] [.RenderWorker-0x7fa67753a4f0]GL ERROR :GL_INVALID_VALUE : ScopedTextureBinder::dtor: <- error from previous GL command
2016-11-17T17:10:05+01:00 - debug: Upgrade database...
Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/926Prune sandboxes on incoming data2017-11-28T16:49:16+01:00Cédric MoreauPrune sandboxes on incoming dataSee https://forum.duniter.org/t/noeud-specialise-pour-visualiser-salle-dattente-des-futurs-membres-g1/2230/69See https://forum.duniter.org/t/noeud-specialise-pour-visualiser-salle-dattente-des-futurs-membres-g1/2230/69Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1099Have a dynamic stock of certifications2017-11-28T16:49:16+01:00Cédric MoreauHave a dynamic stock of certificationsThe discussion is here: https://forum.duniter.org/t/stock-de-certifications-dynamique/3232
For now this is still an under discussion feature.The discussion is here: https://forum.duniter.org/t/stock-de-certifications-dynamique/3232
For now this is still an under discussion feature.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/921Fast sync restarting a node with too much blocks missing2017-11-28T16:49:16+01:00Cédric MoreauFast sync restarting a node with too much blocks missing*Created by: M5oul*
When a node have been stopped for a long time.
It would be great that a mechanism detects that the node have too much blocks late.
Instead of trying to sync slowly.
It would be great that the fast sync could be la...*Created by: M5oul*
When a node have been stopped for a long time.
It would be great that a mechanism detects that the node have too much blocks late.
Instead of trying to sync slowly.
It would be great that the fast sync could be launched from current local blockchain state.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1101Difficulties not updated with HEAD2017-11-28T16:49:16+01:00Cédric MoreauDifficulties not updated with HEAD*Created by: M5oul*
I noticed that the ID of the HEAD block issued by this ID is not displayed on `/blockchain/difficulties` when this ID was not on the current window. *Created by: M5oul*
I noticed that the ID of the HEAD block issued by this ID is not displayed on `/blockchain/difficulties` when this ID was not on the current window. Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/857Sync may lead to empty BINDEX2017-11-28T16:49:16+01:00Cédric MoreauSync may lead to empty BINDEXUnder certain circumstances, after a full sync and then a start, the BINDEX is empty.
I suspect this has some link with the block number being a multiple of the chunk, or something related.Under certain circumstances, after a full sync and then a start, the BINDEX is empty.
I suspect this has some link with the block number being a multiple of the chunk, or something related.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1009Network & sync issues since 1.3.92017-11-28T16:49:16+01:00Cédric MoreauNetwork & sync issues since 1.3.9https://forum.duniter.org/t/duniter-version-1-3/2684/13
https://forum.duniter.org/t/duniter-version-1-3/2684/13
1.3.10https://git.duniter.org/nodes/typescript/duniter/-/issues/1095UPnP ports are opened during automated tests2017-11-28T16:49:16+01:00Cédric MoreauUPnP ports are opened during automated testsI could see several ports opened during unit tests using UPnP.
That should not occur, it is a bug in the tests.I could see several ports opened during unit tests using UPnP.
That should not occur, it is a bug in the tests.https://git.duniter.org/nodes/typescript/duniter/-/issues/852Do not launch PoW engines if not a member2017-11-28T16:49:16+01:00Cédric MoreauDo not launch PoW engines if not a memberHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/907Prioritize transaction's integration2017-11-28T16:49:16+01:00Cédric MoreauPrioritize transaction's integration> (14:54:45) inso: du coup on a rien conclut pour le moment pour limiter les tx "spam" ? :)
(14:55:47) inso: Dans bitcoin on notera que les noeuds ont des règles anti spam : https://en.bitcoin.it/wiki/Spam_transactions
(15:03:47) Moul ...> (14:54:45) inso: du coup on a rien conclut pour le moment pour limiter les tx "spam" ? :)
(14:55:47) inso: Dans bitcoin on notera que les noeuds ont des règles anti spam : https://en.bitcoin.it/wiki/Spam_transactions
(15:03:47) Moul [moul@moul.re/cab338c8-e743-424c-a0d7-b8247b43dfb6] a rejoint le salon.
(15:05:39) mamygeek a quitté le salon (Disconnected: closed)
(15:10:59) inso: Un truc tout simple pour l'anti spam : "Specifically, it looks for the age of the transaction outputs that are being spent. If you are transferring coins that were previously transfered a short time before, the priority goes down,"
(15:11:35) mamygeek [mamygeek@im.apinc.org/Julie] a rejoint le salon.
(15:12:55) Tortue a quitté le salon (Disconnected: timeout during receiving)
(15:12:57) cgeek: inso: oui c'est une bonne idée ça
(15:13:10) inso: Et qui suffit à régler un grand nombre de cas (quelqu'un qui chercherait à spammer le réseau pourrait consommer tout ses outputs, puis ça s'arrêterait puisque ses nouveaux outputs seraient trop récents)
(15:14:28) inso: Ce qui est intéressant c'est que des tx sans fees sont faisable dans bitcoin si elles respectent des conditions assez proche de ce qu'on fait dans DUniter :) http://bitcoin.stackexchange.com/a/37233
(15:14:39) inso: It is smaller than 1,000 bytes.
All outputs are 0.01 BTC or larger.
Its priority is large enough
(15:15:42) inso: Un petit point auquel je pense avec le problème de l'age des outputs - le chaining de transactions ne serait plus possible (ou apparaitre comme du spam)
(15:15:48) inso: Il faudrait l'implémenter différement
(15:25:09) inso: en fait non, les tx de change n'apparaitraient pas comme du spam
(15:25:19) inso: car on passerait de 44 inputs à 1 output
(15:25:33) inso: donc on détruit des outputs -> cette transaction est raisonnable
(15:25:57) inso: donc la priorité serait un facteur de l'age de l'output mais aussi de son origine (le nombre d'input détruit pour créé cette output)
(15:27:04) cgeek: oui d'accord, privilégier d'abord celles qui diminuent les outputs, puis celle à nombre égal priorisées par age, puis celles qui augmentent le nombre triées par augmentation et age
(15:28:46) inso: ca me parait correct :)