Oui je pense que c’est souhaitable sinon pour “survivre” à la fin des 5 certifications quasi simultanément, il en faut 5 de plus en décalé, soit le double.
Je pense qu’aucun utilisateur n’est conscient de cela.
Tu devrais l’implémenter dès le départ dans Durs amha.
Je suis de ton avis @vit, ça me préoccupe aussi.
@elois : étant donné que je ne veux plus trop m’investir dans les changements du protocole mais que celle-ci semble nécessaire, je propose que :
Dans les deux cas je souhaite d’abord remettre un peu Duniter sur pied en version 1.7.
Personnellement je préfère la solution 1), mais ton avis peut m’orienter vers l’autre solution sinon. Ou encore autre chose.
la solution 1) me conviens car pour la solution 2 je préfère qu’on prenne le temps de faire ça bien, avec des flags et tout, et ça me semble plus critique car ça change le format des blocks !
De plus, un déclenchement temporel me semble ne pas poser de problème ici dans le sens ou ce changement n’aura aucun impact avant le 1er mars 2019 sur la Ğ1 et qu’on peut donc prendre le temps de le tester sur g1-test avant pour être sur 
Alors l’idée est bien que le déclenchement se fasse avant Mars 2019 (le plus tôt possible, en fait).
Mais sinon, OK, je pars sur 1).
Bien vu. 
EDIT : J’ai mis en place un tgen entre 5 adresses qui enverra des tx toutes les 15 minutes normalement. On va essayer de faire vivre ce réseau pour une fois
@moul : silkaj ne permet pas de renouveler son adhésion ?
Non, c’est en projet.
Cool, si tu n’a pas encore codé la création du document Membership j’ai quelque chose qui pourra t’aider 
Bien vu.
EDIT : J’ai mis en place un tgen entre 5 adresses qui enverra des tx toutes les 15 minutes normalement. On va essayer de faire vivre ce réseau pour une fois
@moul : silkaj ne permet pas de renouveler son adhésion ?
Sur cesium, je ne vois pas les transactions pour inso2018 ? Vous avez le même problème ?
Ni pour les clés utilisées par tgen d’ailleurs : (par exemple EZKpPQAe6JinSoSaxSn6W2dnJ2j9qQH6s2Z69mUp8dqZ )
Ça semble avoir encore forké !
cgeek est tout seul sur ça branche.
Quand je demande les logs, j’ai ca :
<--- Last few GCs --->
[22255:0x1b7e548] 49034 ms: Mark-sweep 129.7 (161.5) -> 128.3 (168.0) MB, 371.2 / 0.1 ms allocation failure GC in old space requested
[22255:0x1b7e548] 49784 ms: Mark-sweep 128.3 (168.0) -> 128.3 (153.0) MB, 738.6 / 22.1 ms last resort GC in old space requested
[22255:0x1b7e548] 50509 ms: Mark-sweep 128.3 (153.0) -> 128.3 (153.0) MB, 708.3 / 6.0 ms last resort GC in old space requested
<--- JS stacktrace --->
==== JS stack trace =========================================
Security context: 0x59f1631d <JSObject>
2: DoJoin(aka DoJoin) [native array.js:1] [bytecode=0x59f536ad offset=212](this=0x417841a1 <undefined>,p=0x2d872081 <JSArray[459]>,q=459,E=0x41784209 <true>,A=0x41784279 <String[0]: >,z=0x41784249 <false>)
4: Join(aka Join) [native array.js:1] [bytecode=0x59f532e1 offset=71](this=0x417841a1 <undefined>,p=0x2d872081 <JSArray[459]>,q=459,A=0x41784279 <String[0]: >,z=0x41784249 <false>)
6: ...
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - JavaScript heap out of memory
Abandon
[/quote]
2eme tentative plus fructueuse au niveau du log, mais ca semble bien coincé.
[quote]
2018-11-29T14:36:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T14:36:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T14:36:42+01:00 - info: Next peering signal in 5 min
2018-11-29T14:41:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T14:41:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T14:41:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T14:41:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T14:41:42+01:00 - info: Next peering signal in 5 min
2018-11-29T14:44:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T14:44:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
2018-11-29T14:46:18+01:00 - info: WS2P: init: bundle of peers 1/1
2018-11-29T14:46:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T14:46:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T14:46:33+01:00 - info: WS2P: Could not connect to peer 3dnbnYY9 using `WS2P 88.174.120.187 20901: WS2P connection timeout`
2018-11-29T14:46:33+01:00 - info: WS2P: Could not connect to peer CgNMrGrg using `WS2P 88.174.120.187 20900: WS2P connection timeout`
2018-11-29T14:46:33+01:00 - info: WS2P: Could not connect to peer DpJse2t7 using `WS2P 83.204.200.142 20900: WS2P connection timeout`
2018-11-29T14:46:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T14:46:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T14:46:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T14:46:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T14:46:42+01:00 - info: Next peering signal in 5 min
2018-11-29T14:51:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T14:51:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T14:51:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T14:51:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T14:51:42+01:00 - info: Next peering signal in 5 min
2018-11-29T14:54:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T14:54:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
2018-11-29T14:56:18+01:00 - info: WS2P: init: bundle of peers 1/1
2018-11-29T14:56:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T14:56:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T14:56:33+01:00 - info: WS2P: Could not connect to peer 3dnbnYY9 using `WS2P 88.174.120.187 20901: WS2P connection timeout`
2018-11-29T14:56:33+01:00 - info: WS2P: Could not connect to peer CgNMrGrg using `WS2P 88.174.120.187 20900: WS2P connection timeout`
2018-11-29T14:56:33+01:00 - info: WS2P: Could not connect to peer DpJse2t7 using `WS2P 83.204.200.142 20900: WS2P connection timeout`
2018-11-29T14:56:33+01:00 - info: WS2P: Could not connect to peer CNGp7hxE using `WS2P 88.174.120.187 20903: WS2P connection timeout`
2018-11-29T14:56:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T14:56:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T14:56:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T14:56:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T14:56:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:01:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:01:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:01:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:01:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:01:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:04:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T15:04:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
2018-11-29T15:06:18+01:00 - info: WS2P: init: bundle of peers 1/1
2018-11-29T15:06:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T15:06:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T15:06:33+01:00 - info: WS2P: Could not connect to peer 3dnbnYY9 using `WS2P 88.174.120.187 20901: WS2P connection timeout`
2018-11-29T15:06:33+01:00 - info: WS2P: Could not connect to peer CgNMrGrg using `WS2P 88.174.120.187 20900: WS2P connection timeout`
2018-11-29T15:06:33+01:00 - info: WS2P: Could not connect to peer DpJse2t7 using `WS2P 83.204.200.142 20900: WS2P connection timeout`
2018-11-29T15:06:33+01:00 - info: WS2P: Could not connect to peer CNGp7hxE using `WS2P 88.174.120.187 20903: WS2P connection timeout`
2018-11-29T15:06:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:06:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:06:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:06:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:06:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:11:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:11:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:11:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:11:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:11:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:14:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T15:14:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
2018-11-29T15:16:18+01:00 - info: WS2P: init: bundle of peers 1/1
2018-11-29T15:16:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T15:16:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T15:16:33+01:00 - info: WS2P: Could not connect to peer 3dnbnYY9 using `WS2P 88.174.120.187 20901: WS2P connection timeout`
2018-11-29T15:16:33+01:00 - info: WS2P: Could not connect to peer CgNMrGrg using `WS2P 88.174.120.187 20900: WS2P connection timeout`
2018-11-29T15:16:33+01:00 - info: WS2P: Could not connect to peer DpJse2t7 using `WS2P 83.204.200.142 20900: WS2P connection timeout`
2018-11-29T15:16:33+01:00 - info: WS2P: Could not connect to peer CNGp7hxE using `WS2P 88.174.120.187 20903: WS2P connection timeout`
2018-11-29T15:16:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:16:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:16:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:16:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:16:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:21:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:21:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:21:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:21:43+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:21:43+01:00 - info: Next peering signal in 5 min
2018-11-29T15:24:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T15:24:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
2018-11-29T15:26:33+01:00 - info: WS2P: Could not connect to peer 3dnbnYY9 using `WS2P 88.174.120.187 20901: WS2P connection timeout`
2018-11-29T15:26:33+01:00 - info: WS2P: Could not connect to peer CgNMrGrg using `WS2P 88.174.120.187 20900: WS2P connection timeout`
2018-11-29T15:26:33+01:00 - info: WS2P: Could not connect to peer DpJse2t7 using `WS2P 83.204.200.142 20900: WS2P connection timeout`
2018-11-29T15:26:33+01:00 - info: WS2P: Could not connect to peer CNGp7hxE using `WS2P 88.174.120.187 20903: WS2P connection timeout`
2018-11-29T15:26:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:26:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:26:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:26:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:26:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:28:31+01:00 - info: worker 11575 died with code null and signal SIGKILL
2018-11-29T15:31:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:31:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:31:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:31:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:31:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:34:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T15:34:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
2018-11-29T15:36:18+01:00 - info: WS2P: init: bundle of peers 1/1
2018-11-29T15:36:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T15:36:18+01:00 - info: Block resolution: 0 potential blocks after current#283565...
2018-11-29T15:36:33+01:00 - info: WS2P: Could not connect to peer 3dnbnYY9 using `WS2P 88.174.120.187 20901: WS2P connection timeout`
2018-11-29T15:36:33+01:00 - info: WS2P: Could not connect to peer CgNMrGrg using `WS2P 88.174.120.187 20900: WS2P connection timeout`
2018-11-29T15:36:33+01:00 - info: WS2P: Could not connect to peer DpJse2t7 using `WS2P 83.204.200.142 20900: WS2P connection timeout`
2018-11-29T15:36:33+01:00 - info: WS2P: Could not connect to peer CNGp7hxE using `WS2P 88.174.120.187 20903: WS2P connection timeout`
2018-11-29T15:36:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:36:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:36:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:36:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:36:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:41:42+01:00 - info: Sibling endpoints: 0=BASIC_MERKLED_API 78.225.244.76 34522
2018-11-29T15:41:42+01:00 - info: BMA access: 78.225.244.76:34522
2018-11-29T15:41:42+01:00 - info: [DQZ2CANv] ⬇ PEER DQZ2CANv 283565-0
2018-11-29T15:41:42+01:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2018-11-29T15:41:42+01:00 - info: Next peering signal in 5 min
2018-11-29T15:44:03+01:00 - warn: Security trigger: proof-of-work process seems stuck
2018-11-29T15:44:03+01:00 - warn: Too high difficulty: waiting for other members to write next block
Il faut se resyncro sur cgeek du coup ?
Je viens de tester un revert de 5 blocks et restart. Le noeud recharge les blocs jusqu’au 283565 et s’arrête de nouveau… Je lancerai une synchro ce soir car pas moyen de là où je suis de garder une console distante ouverte suffisamment longtemps. (La commande sync ne semble faire que des synchros complètes)
@cgeek y a-t-il une option sur la commande sync qui permette de faire une synchro partielle ?
duniter -h
sync [source] [to] Synchronize blockchain from a remote Duniter node. [source] is [host][:port]. [to] defaults to remote current block number.
Une nouvelle synchro a fait l’affaire pour que le nœud ne reste plus bloqué.
Ah non, ça s’est de nouveau désynchronisé !
Ceux qui veulent se synchroniser de nouveau sur le réseau, ça tient. Mon nœud a trouvé des blocs.
@cgeek, peu être que tu peux baisser la puissance de ton nœud pour laisser de la place pour les autres identités car ça va vite avec une identité pour en placer une (un en l’occurrence).
Faut se sync sur quel noeud ?
Le nœud par officiel du projet.
Tu es sûr qu’il y a eu des désynchronisations ? Le réseau a l’air stable, avec 6 nœuds synchronisés.
J’ai baissé la puissance de mon nœud.
@Inso, est-ce que ton nœud calcule ? Je n’en ai pas l’impression.
Il nous faudrait au moins 3 nœuds membre pour pouvoir tester le déploiement de Duniter 1.7 et la bascule v10-v11.