duniter issueshttps://git.duniter.org/nodes/typescript/duniter/-/issues2019-09-10T12:58:03+02:00https://git.duniter.org/nodes/typescript/duniter/-/issues/1385CPU and memory leaks2019-09-10T12:58:03+02:00vincentrouCPU and memory leaksI observe cpu and memory leaks on my duniter node.
![memory_leak](/uploads/344dfd0c699eb7b3db5b55ab60cf0e9d/memory_leak.png)
![cpu_leak](/uploads/0ee9fdc3cf155331c5c01ea432956ee8/cpu_leak.png)
The memory leak is quite slow but the cpu...I observe cpu and memory leaks on my duniter node.
![memory_leak](/uploads/344dfd0c699eb7b3db5b55ab60cf0e9d/memory_leak.png)
![cpu_leak](/uploads/0ee9fdc3cf155331c5c01ea432956ee8/cpu_leak.png)
The memory leak is quite slow but the cpu leak made the server crash after a month and half. The command was to be at 40% of the cpu for the PoW.https://git.duniter.org/nodes/typescript/duniter/-/issues/1371Replacing naclb by node-sodium2019-05-07T22:08:29+02:00Cédric MoreauReplacing naclb by node-sodiumNaclb was a handmaid port dependency for fast, native C++ execution of Nacl (speed needed for PoW).
Today, it exists [node-sodium](https://github.com/paixaop/node-sodium) which seems to do this exact job and be maintained actively and b...Naclb was a handmaid port dependency for fast, native C++ execution of Nacl (speed needed for PoW).
Today, it exists [node-sodium](https://github.com/paixaop/node-sodium) which seems to do this exact job and be maintained actively and bases on stantard C++ libs.
Maybe we could replace naclb by node-sodium.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/1353An identity with its membership which just expires proceed block calculation2020-10-04T18:34:17+02:00MoulAn identity with its membership which just expires proceed block calculation> Cf: https://forum.duniter.org/t/g1-test-dans-les-choux/4192/316?u=moul
It is not happening when launching pow with an already expired membership identity.
But, it happen, when an member identity is calculating, then loose its members...> Cf: https://forum.duniter.org/t/g1-test-dans-les-choux/4192/316?u=moul
It is not happening when launching pow with an already expired membership identity.
But, it happen, when an member identity is calculating, then loose its membership and keep calculate.
There is no further check at each block if the identity is still member. A mechanism should handle that.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1314Zombies PoW processes2019-09-10T12:01:34+02:00MoulZombies PoW processesThere is many zombies PoW processes which are left running by duniter main process:
![Ekrankopio_de_2018-11-17_14-15-01](/uploads/33094dda63f49c9323f5160feaa89931/Ekrankopio_de_2018-11-17_14-15-01.png)
Sometimes, theses processes are ta...There is many zombies PoW processes which are left running by duniter main process:
![Ekrankopio_de_2018-11-17_14-15-01](/uploads/33094dda63f49c9323f5160feaa89931/Ekrankopio_de_2018-11-17_14-15-01.png)
Sometimes, theses processes are taking a bit of CPU, around 5%.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1281Improve block generation speed2020-10-04T18:41:55+02:00Cédric MoreauImprove block generation speedThe block generation is becoming slower and slower on Ğ1 due to the increasing activity on it, notably the WoT documents.
It is particularly handicaping for modest configurations like Raspberry PIs.The block generation is becoming slower and slower on Ğ1 due to the increasing activity on it, notably the WoT documents.
It is particularly handicaping for modest configurations like Raspberry PIs.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1239Change the proof of work algorithm2018-12-07T14:22:42+01:00Cédric MoreauChange the proof of work algorithmAs discussed here: https://mastodon.xyz/web/statuses/99174770035035196
It seems that the current PoW chain (`SHA256(Ed25519_sign(SHA256("InnerHash:...Nonce: <nonce>")))`) is still ASIC compliant, in that an ASIC could still handle this ...As discussed here: https://mastodon.xyz/web/statuses/99174770035035196
It seems that the current PoW chain (`SHA256(Ed25519_sign(SHA256("InnerHash:...Nonce: <nonce>")))`) is still ASIC compliant, in that an ASIC could still handle this computation.
@aeris suggests to either use ARGON2 or scrypt currently, because these functions introduce a tradeoff between CPU and memory.
I'm not an expert, so I can just believe this assertion right now.
Anyway, as long as the number of ASIC powered member nodes is low compared to the number of non-ASIC powered member nodes, it won't be a big problem. But it would still be annoying, even more later if Ğ1 growth.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1208Key delegated to block computing2017-12-15T04:20:38+01:00ÉloïsKey delegated to block computinghttps://forum.duniter.org/t/idee-cle-deleguee-au-calcul-de-blocs/2698/1
The idea of the delegated key is to be able to delegate the computation of blocks to a subkey, in order to put the main keychain in safety.
This subkey has the...https://forum.duniter.org/t/idee-cle-deleguee-au-calcul-de-blocs/2698/1
The idea of the delegated key is to be able to delegate the computation of blocks to a subkey, in order to put the main keychain in safety.
This subkey has the ability to revoke the associated member account.
The member may at any time declare a new delegated Key that cancels and replaces the previous delegated Key.
To avoid spam it will be necessary to add a parameter preventing to declare a new delegated key before `x` seconds.2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1207Planning the improvement of DUP protocol for duniter 2.02017-12-05T14:28:51+01:00ÉloïsPlanning the improvement of DUP protocol for duniter 2.0## Approved developments
- [ ] Pay to pubkey hash #1002
- [ ] Add function P2SH : Pay to script hash #1165
- [ ] Change handicap formula : replace the median by second tiercile #1169
## Developments under discussion
- [ ] Key ...## Approved developments
- [ ] Pay to pubkey hash #1002
- [ ] Add function P2SH : Pay to script hash #1165
- [ ] Change handicap formula : replace the median by second tiercile #1169
## Developments under discussion
- [ ] Key delegated to block computing #1208
2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1199pow : refine calibration of cpu rate2020-10-04T18:45:18+02:00Éloïspow : refine calibration of cpu ratehttps://forum.duniter.org/t/duniter-powcluster-js-utilise-mes-8-coeurs-a-100/3608/51?u=eloishttps://forum.duniter.org/t/duniter-powcluster-js-utilise-mes-8-coeurs-a-100/3608/51?u=elois2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1169Change handicap formula : replace the median by second tiercile2017-12-11T21:03:02+01:00ÉloïsChange handicap formula : replace the median by second tiercilehttps://forum.duniter.org/t/noeud-raspberry-pi-toujours-suffisant-pour-calculer/3514/6?u=eloishttps://forum.duniter.org/t/noeud-raspberry-pi-toujours-suffisant-pour-calculer/3514/6?u=elois2.0https://git.duniter.org/nodes/typescript/duniter/-/issues/1130PoW stopped2017-11-28T16:49:17+01:00Cédric MoreauPoW stopped*Created by: M5oul*
Node v1.6.6 stops calculating blocks and display `Out of fork window` warning:
```bash
2017-09-29T12:57:29+00:00 - info: ✘ PEER 5fPevx21
2017-09-29T12:57:29+00:00 - error: httpCode=400, ucode=2023, message=Peer d...*Created by: M5oul*
Node v1.6.6 stops calculating blocks and display `Out of fork window` warning:
```bash
2017-09-29T12:57:29+00:00 - info: ✘ PEER 5fPevx21
2017-09-29T12:57:29+00:00 - error: httpCode=400, ucode=2023, message=Peer document already known
2017-09-29T12:57:29+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:30+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:30+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:31+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:31+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:32+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:33+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:33+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:34+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:34+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:35+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:35+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:36+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:36+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:37+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:38+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:38+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:39+00:00 - warn: ESOCKETTIMEDOUT
2017-09-29T12:57:39+00:00 - info: Peer DJQjWdkUB9YWzGRPTjPCdGgC5pBx6CA24Dghu6NNvpuH unreachable: now considered as DOWN.
2017-09-29T12:57:39+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:39+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:40+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:40+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
2017-09-29T12:57:41+00:00 - warn: httpCode=400, ucode=2501, message=Out of fork window
```
The node is well on current window as its HEAD is late of one block from network pool HEAD.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/1031Stop PoW if the network's connection is down2017-11-28T16:49:17+01:00Cédric MoreauStop PoW if the network's connection is down*Created by: M5oul*
When there is a connection loss, Duniter could try to found that the connection have been lost.
Currently, nodes are set as `DOWN` then `UP`:
```bash
2017-07-11T21:42:49+02:00 - info: POST Peer GfKERHnJTY#34444...*Created by: M5oul*
When there is a connection loss, Duniter could try to found that the connection have been lost.
Currently, nodes are set as `DOWN` then `UP`:
```bash
2017-07-11T21:42:49+02:00 - info: POST Peer GfKERHnJTY#34444
2017-07-11T21:42:50+02:00 - info: Peer Do99s6wQR2JLfhirPdpAERSjNbmjjECzGxHNJMiNKT3P unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer Be1eVp7etVfA7cT6er6dcJ9d5KxGJVY2tzCGGCAz3yG unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer t5RR5eVeE7jRhKcREvC3kfGtDTdkxmvW6WeJ9q9keHG unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer D9D2zaJoWYWveii1JRYLVK3J4Z7ZH3QczoKrnQeiM6mx unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 4fHMTFBMo5sTQEc5p1CNWz28S4mnnqdUBmECq1zt4n2m unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 2ny7YAdmzReQxAayyJZsyVYwYhVyax2thKcGknmQy5nQ unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 82NdD9eEbXSjRJXeJdqf56xkpu6taTfTeEqtAtmtbyXY unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 6fFt4zdvtNyVcfJn7Y41mKLmMDizyK3nVeNW3qdDXzpc unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 5dzkzedBWdeqTFCaD7AkKPMPusfRUL1XyFNJWWGYQ9f1 unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 8KTEFQS78HwEz1NK627rNsYwENxNXJyvtyMAyfKPXZRB unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 2mk6dyG8vJCQHzRRNMiL1zgCSUqDzxjTpgyq86L4H43j unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer HEEzgSFqXevmjqMTAKLcG7ugAPoadARCLJxjP4Mn39uL unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 4364zZpziQqW4EfSPKE8E3vjNzkwYdagnhGZpQaJVepD unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer TENGx7WtzFsTXwnbrPEvb6odX2WnqYcnnrjiiLvp1mS unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 4tF8g32eRjNyXWhW3d4j2TfA7fXsNEPpE1ar1X3zCMB5 unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer 3AF7bhGQRt6ymcBZgZTBMoDsEtSwruSarjNG8kDnaueX unreachable: now considered as DOWN.
2017-07-11T21:42:50+02:00 - info: Peer M0_GfKERHnJTYzKhKUma5h1uWhetbA8yHKymhVH2raf2aCP unreachable: now considered as DOWN.
2017-07-11T21:42:57+02:00 - info: POST Peer 3AF7bhGQRt#34443
2017-07-11T21:42:59+02:00 - info: POST Peer TENGx7WtzF#34443
2017-07-11T21:43:00+02:00 - warn: ESOCKETTIMEDOUT
2017-07-11T21:43:00+02:00 - info: Peer 4tF8g32eRjNyXWhW3d4j2TfA7fXsNEPpE1ar1X3zCMB5 unreachable: now considered as DOWN.
2017-07-11T21:43:05+02:00 - info: Node HEEzgS (51.255.197.83:10902) is UP!
2017-07-11T21:43:05+02:00 - info: Node 8KTEFQ (167.114.232.189:8999) is UP!
2017-07-11T21:43:05+02:00 - info: Node Be1eVp (88.161.154.41:47925) is UP!
2017-07-11T21:43:05+02:00 - info: Node D9D2za (g1.elois.org:80) is UP!
2017-07-11T21:43:05+02:00 - info: Node 4fHMTF (duniter.help-web-low.fr:8999) is UP!
2017-07-11T21:43:05+02:00 - info: Node 2ny7YA (g1.cgeek.fr:80) is UP!
2017-07-11T21:43:05+02:00 - info: Node Do99s6 (g1.citiz-network.org:16262) is UP!
2017-07-11T21:43:05+02:00 - info: Node 2mk6dy (g1.monnaielibreoccitanie.org:443) is UP!
2017-07-11T21:43:05+02:00 - info: Node 4364zZ (duniter.silibre.com:80) is UP!
2017-07-11T21:43:05+02:00 - info: Node 6fFt4z (duniter.aquilenet.fr:10901) is UP!
2017-07-11T21:43:05+02:00 - info: Node GYEtpP (duniter.laurent-st-math.fr:80) is UP!
2017-07-11T21:43:05+02:00 - info: Node 5dzkze (duniter.vincentuc.fr:80) is UP!
2017-07-11T21:43:06+02:00 - info: Node t5RR5e (duniter.floth.fr:80) is UP!
2017-07-11T21:43:06+02:00 - info: Node 82NdD9 (78.251.5.57:61650) is UP!
```
I don not know if it could be interesting to implement such a feature.Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/958PoW processes stopped four times when receiving a new block2017-11-28T16:49:17+01:00Cédric MoreauPoW processes stopped four times when receiving a new block*Created by: M5oul*
When receiving a new block, Proof-of-work seems to be stopped four times:
```bash
2017-04-13T13:15:57+02:00 - info: Matched 3 zeros 000D2981C35C4D40364BDA668459980B09E26FE1E1B16F0014D3A5EFECAEA765 with Nonce = 2020...*Created by: M5oul*
When receiving a new block, Proof-of-work seems to be stopped four times:
```bash
2017-04-13T13:15:57+02:00 - info: Matched 3 zeros 000D2981C35C4D40364BDA668459980B09E26FE1E1B16F0014D3A5EFECAEA765 with Nonce = 20200000063340 for block#9976 by GfKERH
2017-04-13T13:15:59+02:00 - info: Matched 3 zeros 0006A207B47A7F3B6005F651AB28480179C19417B5A6F00F7251E05E0B24BF4D with Nonce = 20300000063629 for block#9976 by GfKERH
2017-04-13T13:16:04+02:00 - info: Matched 3 zeros 00041CB5FFF2F5BB520B617CC8506CB2A2A292AED734FC000C819B4E1BC592FB with Nonce = 20300000064152 for block#9976 by GfKERH
2017-04-13T13:16:16+02:00 - info: Block #9976 added to the blockchain in 442 ms
2017-04-13T13:16:16+02:00 - info: Stop proof-of-work worker #1
2017-04-13T13:16:16+02:00 - info: Stop proof-of-work worker #2
2017-04-13T13:16:16+02:00 - info: Stop proof-of-work worker #3
2017-04-13T13:16:16+02:00 - info: Stop proof-of-work worker #4
2017-04-13T13:16:16+02:00 - info: POST Block block#9976
2017-04-13T13:16:17+02:00 - warn: connect EHOSTUNREACH 192.168.0.12:8999
2017-04-13T13:16:17+02:00 - info: Peer 2yN8BRSkARcqE8NCxKMBiHfTpx1EvwULFn56Myf6qRmy unreachable: now considered as DOWN.
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #1
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #2
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #3
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #4
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #1
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #2
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #3
2017-04-13T13:16:17+02:00 - info: Stop proof-of-work worker #4
2017-04-13T13:16:17+02:00 - info: GIVEN proof-of-work for block#9976 with 5 leading zeros followed by [0-9A]! stop PoW for GfKERH
2017-04-13T13:16:17+02:00 - warn: The proof-of-work generation was canceled: Proof-of-work computation canceled because block received
2017-04-13T13:16:20+02:00 - info: Generating proof-of-work with 5 leading zeros followed by [0-9A]... (CPU usage set to 35%) for block#9977 GfKERH
2017-04-13T13:16:20+02:00 - info: Stop proof-of-work worker #1
2017-04-13T13:16:20+02:00 - info: Stop proof-of-work worker #2
2017-04-13T13:16:20+02:00 - info: Stop proof-of-work worker #3
2017-04-13T13:16:20+02:00 - info: Stop proof-of-work worker #4
2017-04-13T13:16:21+02:00 - info: Matched 3 zeros 000A7DAD4E62819708765268CD1AE4F612A04A6D752ED709BDE001D8DE7AD6AE with Nonce = 20300000000263 for block#9977 by GfKERH
```Horizonhttps://git.duniter.org/nodes/typescript/duniter/-/issues/957PoW launched during resync2020-10-04T18:52:59+02:00Cédric MoreauPoW launched during resync*Created by: M5oul*
Resync sometimes launch PoW:
```bash
2017-04-12T10:22:54+02:00 - info: Block #9626 added to the blockchain in 398 ms
2017-04-12T10:22:55+02:00 - info: POST Block block#9626
2017-04-12T10:22:55+02:00 - info: Block #96...*Created by: M5oul*
Resync sometimes launch PoW:
```bash
2017-04-12T10:22:54+02:00 - info: Block #9626 added to the blockchain in 398 ms
2017-04-12T10:22:55+02:00 - info: POST Block block#9626
2017-04-12T10:22:55+02:00 - info: Block #9627 added to the blockchain in 401 ms
2017-04-12T10:22:55+02:00 - info: POST Block block#9627
2017-04-12T10:22:55+02:00 - info: Block #9628 added to the blockchain in 406 ms
2017-04-12T10:22:56+02:00 - info: POST Block block#9628
2017-04-12T10:22:56+02:00 - info: Block #9629 added to the blockchain in 486 ms
2017-04-12T10:22:56+02:00 - info: Peer 4Uz7X27jQMAf3jqL2fr75ckZ6Jgi9TZL9fMf9TR9vBvG unreachable: now considered as DOWN.
2017-04-12T10:22:56+02:00 - info: Will pull blocks from the network in 0 min 20 sec
2017-04-12T10:22:56+02:00 - warn: Pulling done. Continue proof-of-work loop.
2017-04-12T10:22:56+02:00 - info: POST Block block#9629
2017-04-12T10:22:59+02:00 - info: Generating proof-of-work with 5 leading zeros followed by [0-9A-C]... (CPU usage set to 35%) for block#9630 GfKERH
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #1
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #2
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #3
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #4
2017-04-12T10:22:59+02:00 - info: Block #9630 added to the blockchain in 2947 ms
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #1
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #2
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #3
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #4
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #1
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #2
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #3
2017-04-12T10:22:59+02:00 - info: Stop proof-of-work worker #4
2017-04-12T10:23:00+02:00 - info: POST Block block#9630
2017-04-12T10:23:00+02:00 - warn: Waiting for the end of pulling...
2017-04-12T10:23:00+02:00 - info: Block #9631 added to the blockchain in 573 ms
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #1
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #2
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #3
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #4
2017-04-12T10:23:00+02:00 - info: POST Block block#9631
2017-04-12T10:23:00+02:00 - info: Block #9632 added to the blockchain in 377 ms
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #1
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #2
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #3
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #4
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #1
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #2
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #3
2017-04-12T10:23:00+02:00 - info: Stop proof-of-work worker #4
2017-04-12T10:23:00+02:00 - info: GIVEN proof-of-work for block#9630 with 5 leading zeros followed by [0-9A-C]! stop PoW for GfKERH
2017-04-12T10:23:00+02:00 - warn: The proof-of-work generation was canceled: Proof-of-work computation canceled because block received
2017-04-12T10:23:00+02:00 - info: POST Block block#9632
2017-04-12T10:23:01+02:00 - info: Block #9633 added to the blockchain in 402 ms
2017-04-12T10:23:01+02:00 - info: POST Block block#9633
2017-04-12T10:23:01+02:00 - info: Block #9634 added to the blockchain in 423 ms
2017-04-12T10:23:01+02:00 - info: POST Block block#9634
2017-04-12T10:23:01+02:00 - info: Block #9635 added to the blockchain in 437 ms
2017-04-12T10:23:02+02:00 - info: POST Block block#9635
2017-04-12T10:23:02+02:00 - info: Block #9636 added to the blockchain in 368 ms
```
The timeout before computing block should be bigger.2.0https://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/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/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/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/846Have a minimal proof-of-work level2018-03-07T21:15:45+01:00Cédric MoreauHave a minimal proof-of-work levelWe noticed that during a hard-fork event there is a strong time acceleration which makes the PoW easier and easier as new blocks comes in, to a point where the difficulty become so easy that a block is issued within few seconds leading t...We noticed that during a hard-fork event there is a strong time acceleration which makes the PoW easier and easier as new blocks comes in, to a point where the difficulty become so easy that a block is issued within few seconds leading to breaking the synchronization of the nodes.
A minimal proof-of-work level could avoid such situations.Horizon