nodes issueshttps://git.duniter.org/groups/nodes/-/issues2017-11-28T16:49:16+01:00https://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/866Sign releases2020-04-30T22:10:23+02:00Cédric MoreauSign releasesThe releases should be signed + have a checksum to verify their integrity.
However this supposes to have our own building machines + a way to reproduce them on our own environement, so any allowed developer of Duniter organization cou...The releases should be signed + have a checksum to verify their integrity.
However this supposes to have our own building machines + a way to reproduce them on our own environement, so any allowed developer of Duniter organization could make a build.
Maybe we could use Vagrant or something to build the environement, then building scripts.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/867Fix the value of `percentRot` parameter2017-11-28T16:49:17+01:00Cédric MoreauFix the value of `percentRot` parameterCurrently this is an initial parameter from block#0. But for some reason this value could have an interest to be changed: for example in ĞTest we've put a wrong value which leads to an effective 50% PoW exclusion, instead of the 33% expe...Currently this is an initial parameter from block#0. But for some reason this value could have an interest to be changed: for example in ĞTest we've put a wrong value which leads to an effective 50% PoW exclusion, instead of the 33% expected.
This 33% rule could be hard coded. So percentRot would always equal 33%.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/868Have an harder personal handicap2017-11-28T16:49:17+01:00Cédric MoreauHave an harder personal handicapToday the handicap is defined as:
PERSONAL_HANDICAP = FLOOR(LN(1 + PERSONAL_EXCESS) / LN(1.189))
So this is a purely linear difficulty augmentation: if our computer is 16 times stronger than the co-calculators, our difficulty w...Today the handicap is defined as:
PERSONAL_HANDICAP = FLOOR(LN(1 + PERSONAL_EXCESS) / LN(1.189))
So this is a purely linear difficulty augmentation: if our computer is 16 times stronger than the co-calculators, our difficulty will go through:
* `PERSONAL_EXCESS = 1` => 18% harder than normally
* `PERSONAL_EXCESS = 2` => 41% harder than normally
* `PERSONAL_EXCESS = 3` => 68% harder than normally
* `PERSONAL_EXCESS = 4` => 100% harder than normally
With this algorithm, the difficulty increases with a delay, and may never handicap us to our have a difficulty corresponding to our effective superiority.
To reach it more quickly, we could simply use an exponential:
PERSONAL_HANDICAP = FLOOR(LN(1 + PERSONAL_EXCESS) / LN(1.189))*2
The result would be:
* `PERSONAL_EXCESS = 1` => 41% harder than normally
* `PERSONAL_EXCESS = 2` => 100% harder than normally
* `PERSONAL_EXCESS = 3` => 182% harder than normally
* `PERSONAL_EXCESS = 4` => 300% harder than normally
Have to study a bit more this before release.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/871Bug on money management?2017-11-28T16:49:17+01:00Cédric MoreauBug on money management?*Created by: M5oul*
```bash
2017-03-04T10:48:48+01:00 - info: Will pull blocks from the network in 0 min 20 sec
2017-03-04T10:48:53+01:00 - info: Transaction 2B2D20EA1D2FA145EEB597495F2A2E1028EF5A23AA2E6B4DC056A86F25C2A2BB added to bl...*Created by: M5oul*
```bash
2017-03-04T10:48:48+01:00 - info: Will pull blocks from the network in 0 min 20 sec
2017-03-04T10:48:53+01:00 - info: Transaction 2B2D20EA1D2FA145EEB597495F2A2E1028EF5A23AA2E6B4DC056A86F25C2A2BB added to block
2017-03-04T10:48:53+01:00 - error: Error: It cannot exist 2 identical sources for transactions inside a given block
at Error (native)
at /opt/duniter/sources/app/lib/rules/local_rules.js:327:13
at next (native)
at onFulfilled (/opt/duniter/sources/node_modules/co/index.js:65:19)
at /opt/duniter/sources/node_modules/co/index.js:54:5
at co (/opt/duniter/sources/node_modules/co/index.js:50:10)
at Object.checkTxSources (/opt/duniter/sources/app/lib/rules/local_rules.js:317:30)
at /opt/duniter/sources/app/lib/rules/local_rules.js:416:24
at next (native)
at onFulfilled (/opt/duniter/sources/node_modules/co/index.js:65:19)
at process._tickCallback (internal/process/next_tick.js:103:7)
2017-03-04T10:48:53+01:00 - error: Error: It cannot exist 2 identical sources for transactions inside a given block
at Error (native)
at /opt/duniter/sources/app/lib/rules/local_rules.js:327:13
at next (native)
at onFulfilled (/opt/duniter/sources/node_modules/co/index.js:65:19)
at /opt/duniter/sources/node_modules/co/index.js:54:5
at co (/opt/duniter/sources/node_modules/co/index.js:50:10)
at Object.checkTxSources (/opt/duniter/sources/app/lib/rules/local_rules.js:317:30)
at /opt/duniter/sources/app/lib/rules/local_rules.js:416:24
at next (native)
at onFulfilled (/opt/duniter/sources/node_modules/co/index.js:65:19)
at runMicrotasksCallback (internal/process/next_tick.js:58:5)
at _combinedTickCallback (internal/process/next_tick.js:67:7)
at process._tickCallback (internal/process/next_tick.js:98:9)
2017-03-04T10:48:53+01:00 - error: Error: It cannot exist 2 identical sources for transactions inside a given block
```Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/874Node didn't resync after restart2017-11-28T16:49:17+01:00Cédric MoreauNode didn't resync after restart*Created by: M5oul*
I started my node after a night turned off, and it didn't retrieved new blocks from the network.
I had to restart the node and it retrieved blocks from the network and was sync.
The fact there is two nodes using sa...*Created by: M5oul*
I started my node after a night turned off, and it didn't retrieved new blocks from the network.
I had to restart the node and it retrieved blocks from the network and was sync.
The fact there is two nodes using same pubkey could be explain why this happen.
Similar to https://github.com/duniter/duniter/issues/683.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/880wotb module don't have the full inventory of certifications2017-11-28T16:49:17+01:00Cédric Moreauwotb module don't have the full inventory of certificationsI see 486 links un wotb, whereas 551 were written.
I see 486 links un wotb, whereas 551 were written.
Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/886BMA Network: listen on all interfaces (and with the interface name)2017-11-28T16:49:17+01:00Cédric MoreauBMA Network: listen on all interfaces (and with the interface name)*Created by: Tortue95*
Hi,
can you add the possibility to listen on all interfaces
and at the same time the possibility to listen on one interface name (not the IP)*Created by: Tortue95*
Hi,
can you add the possibility to listen on all interfaces
and at the same time the possibility to listen on one interface name (not the IP)https://git.duniter.org/nodes/typescript/duniter/-/issues/888The main entry of the PowerClearRequest is not found2017-11-28T16:49:17+01:00Cédric MoreauThe main entry of the PowerClearRequest is not found*Created by: Patator65*
Hi,
I have an issue when i try to start Duniter.
This is the error message i get (i do my own translation fr to en of this message) :
The main entry of the PowerClearRequest is not found in the lib of dynamic ...*Created by: Patator65*
Hi,
I have an issue when i try to start Duniter.
This is the error message i get (i do my own translation fr to en of this message) :
The main entry of the PowerClearRequest is not found in the lib of dynamic links KERNEL32.dll.
Hope it is correctly translanted :)
My PC works with Vista x64.https://git.duniter.org/nodes/typescript/duniter/-/issues/890Dynamic IP: detect the public IP changing2018-12-07T14:10:25+01:00Cédric MoreauDynamic IP: detect the public IP changingSee https://forum.duniter.org/t/noeud-qui-pedale-dans-la-choucroute/2176See https://forum.duniter.org/t/noeud-qui-pedale-dans-la-choucroute/2176Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/891Node kept UP if a web server is running at same address and the node is down2017-11-28T16:49:17+01:00Cédric MoreauNode kept UP if a web server is running at same address and the node is down*Created by: M5oul*
I turned off my node on my YunoHost instance, and the node on my desktop keep staying the other one is still running:
```bash
2017-03-14T17:10:13+01:00 - info: Sibling endpoints: 0=BMAS duniter.moul.re 443, 1=BMAS ...*Created by: M5oul*
I turned off my node on my YunoHost instance, and the node on my desktop keep staying the other one is still running:
```bash
2017-03-14T17:10:13+01:00 - info: Sibling endpoints: 0=BMAS duniter.moul.re 443, 1=BMAS duniter.moul.re 78.227.107.45 2a01:e34:ee36:b2d0:83:6ff:fe43:6546 443
2017-03-14T17:10:13+01:00 - info: External access: desktop.moul.re:10901
```
In fact, there is still an http server running behind this address, but not a duniter node.
How is checked the fact there is a running node?
Only by checking if the address answer or if it could get something for the BMA?
I wasn't able to found how the check is done on the [crawler](https://github.com/duniter/duniter-crawler/blob/master/lib/crawler.js).
Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/898snap package2017-11-28T16:49:17+01:00Cédric Moreausnap package*Created by: Thatoo*
I wanted to try to install duniter on my ubuntu phone but for that I understood I needed a snap package, not a deb package.
I had a look at how to make a snap package out of github repository thanks to
https://...*Created by: Thatoo*
I wanted to try to install duniter on my ubuntu phone but for that I understood I needed a snap package, not a deb package.
I had a look at how to make a snap package out of github repository thanks to
https://snapcraft.io/docs/build-snaps/ci-integration
With the help of RavanH, I think we managed to do all except making the snapcraft.yaml file that need to be added to github for the packaging to work.
Here are instruction how to make this file :
https://snapcraft.io/docs/build-snaps/your-first-snap
If someone can make that file, I think we'd have the snap package ready here and update automatically anytime github repo is updated : https://code.launchpad.net/~duniter/+snap/duniter
An other thing I don't know is what to tick in this list of processor (it's optional so I let the default stuff) :
+ AMD x86-64 (amd64)
ARM ARMv8 (arm64)
+ ARM ARMv7 Hard Float (armhf)
+ Intel x86 (i386)
PowerPC (powerpc)
PowerPC64 Little-Endian (ppc64el)
IBM System z (s390x
Edit : I ticked also ARM ARMv7 Hard Float for Rasp Pi 3
I found also that page that might help for making snapcraft.yaml file :
https://snapcraft.io/docs/build-snaps/syntaxhttps://git.duniter.org/nodes/typescript/duniter/-/issues/901Desktop: after a resync, PoW blocks are not shared2017-11-28T16:49:17+01:00Cédric MoreauDesktop: after a resync, PoW blocks are not shared> (18:15:42) jytou: re passage en coup de vent: je confirme que tant que je n'ai pas redémarré mon nœud après une syncho, il trouvait des blocs mais n'arrivait pas à les publier, pas d'erreur apparente dans les logs mais plein de « found...> (18:15:42) jytou: re passage en coup de vent: je confirme que tant que je n'ai pas redémarré mon nœud après une syncho, il trouvait des blocs mais n'arrivait pas à les publier, pas d'erreur apparente dans les logs mais plein de « found » sans publication, et hop je suis reparti
(18:20:43) cgeek: jytou: tu parles de la version desktop ?
(18:22:18) bruno a quitté le salon (Disconnected: closed)
(18:24:22) jytou: cgeek: ouiHorizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/902Scaling up the certifications pools with a DHT2017-11-28T16:49:16+01:00insoScaling up the certifications pools with a DHTAs we can see, since it takes a long time for one to become a member, the data pools are filled up and it is stucking the entrance of new members.
Here, I'm suggesting an evolution to be able to scale up the pools. We already discusse...As we can see, since it takes a long time for one to become a member, the data pools are filled up and it is stucking the entrance of new members.
Here, I'm suggesting an evolution to be able to scale up the pools. We already discussed it on the chat some time ago, but I wanted to trace the idea.
The certifications are blocked because, for one new member, you need 5 certifications.
The nodes can locally only have locally the MS+IDTY documents and a partial view of the certifications. Thus, we only need to distribute the certifications on the DHT.
The overall idea is :
- The nodes have the identities and memberships in their pools. They don't necessary have all the identities or all the memberships.
- The nodes are distributing throught a DHT the certifications documents
- The nodes use the DHT to discover which identity can become a member when forging new blocks
## The DHT
I suggest to use Kademlia DHT, for example using KAD framework for node js : https://github.com/kadtools/kad.
The format of the keys could be :
```
CERT:[PUBKEY_TO]
```
- [PUBKEY_TO] corresponds to the pubkey being certified
The format of the values would be the raw certification documents valid and writable for the given timestamp target.
## The forging of blocks
- During the computation of block "N", the node would check which identity could become a member in block "N+1".
- For all Identities+Membership in the pool, if they don't have enough certifications locally, they would ask the network for valid certifications about this identity and membership.
- When block "N" is computed, the node would start computing block "N+1" with the data received by the network during the computation of block "N" .
## Duniter plugins required for Kad
- A middleware using pubkey of peers to protect the network against classic sybil attacks
- A middleware to append data to keys when receiving documents throught BMA
https://git.duniter.org/nodes/typescript/duniter/-/issues/903Tests failed with YunoHost app at sync with sqlite issue2017-11-28T16:49:16+01:00Cédric MoreauTests failed with YunoHost app at sync with sqlite issue*Created by: M5oul*
Tests failed on YunoHost-Apps test, install in this case:
```bash
Warning: yunohost.hook <lambda> - [925.1] 2017-03-20T22:32:36+00:00 - debug: 15000
Warning: yunohost.hook <lambda> - [925.1] 2017-03-20T22:32:37+00...*Created by: M5oul*
Tests failed on YunoHost-Apps test, install in this case:
```bash
Warning: yunohost.hook <lambda> - [925.1] 2017-03-20T22:32:36+00:00 - debug: 15000
Warning: yunohost.hook <lambda> - [925.1] 2017-03-20T22:32:37+00:00 - debug: Trying to close SQLite...
Warning: yunohost.hook <lambda> - [925.1] 2017-03-20T22:32:37+00:00 - error: Error: SQL error "SQLITE_CONSTRAINT: NOT NULL constraint failed: b_index.udTime" on query "INSERT INTO b_index (`version`,`bsize`,`hash`,`issuer`,`time`,`number`,`membersCount`,`issuersCount`,`issuersFrame`,`issuersFrameVar`,`issuerDiff`,`avgBlockSize`,`medianTime`,`dividend`,`mass`,`massReeval`,`unitBase`,`powMin`,`udTime`,`udReevalTime`,`diffNumber`,`speed`) VALUES
Warning: yunohost.hook <lambda> - [925.1] (10,0,'000053A3F6C2C3C35AB624F1AE49CBBED6BDA40EA6EBE149971FE4F51EBBC6AB','CSjgcGguFJe3ghBBjjGyNVdvC3rqtXE7rSxUaLzjxBhR',1489942686,14750,40,6,31,0,null,0,1489938240,2654,'10559063383','10558001783',1,73,null,null,14760,0.0032520325203252032),
Warning: yunohost.hook <lambda> - [925.1] (10,0,'000041DB796E71D13287CB6519E9C4A5B4E632A1E602ADF4C82BD79DBF1BA636','2pyPsXM8UCB88jP2NRM4rUHxb63qm89JMEWbpoRrhyDK',1489942812,14751,40,6,31,0,null,0,1489938615,2654,'10560124983','10559063383',1,73,null,null,14760,0.003124023742580444),
Warning: yunohost.hook <lambda> - [925.1] (10,0,'00006A384B40303A2E8F6E10C2700F9C1C2807671BFA030814E4C3911A28C28E','HnFcSms8jzwngtVomTTnzudZx7SHUQY8sVE1y8yBmULk',1489943040,14752,40,6,31,0,null,0,1489938990,2654,'10561186583','10560124983',1,73,null,null,14760,0.002999400119976005),
Warning: yunohost.hook <lambda> - [925.1] (10,0,'000041901D989F8E3D9D51BEFE9B9403445FB83676E0FAD5778E5EC4F7DAAC47','77mfxsDcX8JZKHD9fBC9wNtM1R7Yj3WA27DsY7kyrePX',1489944337,14753,40,6,31,0,null,0,1489939343,2654,'10562248183','10561186583',1,73,null,null,14760,0.0028960324355632784),
Warning: yunohost.hook <lambda> - [925.1]
```
The CI host is on LXC.
- [Full logs](https://ci-apps.yunohost.org/jenkins/job/duniter%20(Community)/lastBuild/consoleFull).Horizonhttps://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 :)https://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/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/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/943Encrypt the keypair2020-10-04T18:53:25+02:00Cédric MoreauEncrypt the keypairSee #882.
Now that the keypair is stored, we could add encryption/decryption features.See #882.
Now that the keypair is stored, we could add encryption/decryption features.2.0