Comment se fait-il que mon noeud calcule sans cesse toute la journée sans jamais obtenir de bloc même lorsqu’il matche 5 zeros ?
2019-04-15T17:08:58+02:00 - info: WS2P: established incoming connection from 6HawP53V 77.136.120.230:51170
2019-04-15T17:08:59+02:00 - info: Matched 3 zeros 0002DBE1E4BA85AD9F2574751D5A0A523869F3A409CEEFD33EC084209E0BE717 with Nonce = 10200000005583 for block#212563 by ChU8ca
2019-04-15T17:09:00+02:00 - warn: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2019-04-15T17:09:02+02:00 - info: Matched 3 zeros 0003F25F1BD780170AED5F5CF40D3B455D854CF3790B68037281BF6699FB0CBC with Nonce = 10300000006505 for block#212563 by ChU8ca
2019-04-15T17:09:02+02:00 - info: Matched 3 zeros 0001692227DD6B9DCC927B7672094D65BEEC1C38C327DF94CAEF7BDC60933259 with Nonce = 10300000006514 for block#212563 by ChU8ca
2019-04-15T17:09:03+02:00 - info: Matched 5 zeros 00000F415D005A38AD95490E8BFB002D553CCB275D5598E27BC502F0C9780751 with Nonce = 10400000006832 for block#212563 by ChU8ca
2019-04-15T17:09:04+02:00 - info: Matched 4 zeros 0000595972803A8A6FEC1CBF915D01CB4E50D96D0B370CDDE1CD4C461BB57425 with Nonce = 10100000007505 for block#212563 by ChU8ca
2019-04-15T17:09:05+02:00 - info: Matched 3 zeros 00017449E0D0E5E945DD09E10E8DD491C9E01ACC20760E01BC9680B2240D2870 with Nonce = 10100000007734 for block#212563 by ChU8ca
2019-04-15T17:09:07+02:00 - warn: WS2P: cannot connect to incoming WebSocket connection: WS2P connection timeout
2019-04-15T17:09:07+02:00 - info: WS2P ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S: new incoming connection from 151.80.40.148:53530!
2019-04-15T17:09:07+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:68413b67-e2c0-4ca2-be8d-79f2e039e6b2dfead5e9-f7c3-4ddb-8eab-d46cb51c519f
2019-04-15T17:09:07+02:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:4fHMTFBMo5sTQEc5p1CNWz28S4mnnqdUBmECq1zt4n2m:5ca4ac7e-5ed9-4c81-941c-78d8e873a62e8ef8f182-b421-4d02-8423-a7e8e55c7594
2019-04-15T17:09:07+02:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:5ca4ac7e-5ed9-4c81-941c-78d8e873a62e8ef8f182-b421-4d02-8423-a7e8e55c7594
2019-04-15T17:09:08+02:00 - info: Matched 3 zeros 000107AAE5F9460683D6B749B0C3A215C7FC597B43DDE6CD9AB272F480298CA6 with Nonce = 10300000008423 for block#212563 by ChU8ca
2019-04-15T17:09:09+02:00 - info: WS2P ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S: new incoming connection from 78.193.40.205:38649!
2019-04-15T17:09:09+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:38815c84-ec23-42ab-b455-55eaf2a3be836876e555-b3d3-47e3-8e8c-8fb82715543f
2019-04-15T17:09:09+02:00 - info: WS2P: Could not connect to peer GfKERHnJ using `WS2P duniter.moul.re 443: WS2P connection timeout`
2019-04-15T17:09:09+02:00 - error: WS2P >>> >>> WS ERROR: REJECTED_PUBKEY_OR_INCORRECT_ASK_SIGNATURE_FROM_REMOTE
2019-04-15T17:09:10+02:00 - info: WS2P: Could not connect to peer 5jfUpXPW using `WS2P 2.8.197.215 20900: WS2P connection timeout`
2019-04-15T17:09:10+02:00 - info: WS2P: Could not connect to peer AmDcZSEB using `WS2P 91.161.185.155 20900: WS2P connection timeout`
2019-04-15T17:09:10+02:00 - debug: WS2P: init: failed connection
2019-04-15T17:09:10+02:00 - debug: WS2P: init: failed connection
2019-04-15T17:09:10+02:00 - info: WS2P: Could not connect to peer 82NdD9eE using `WS2P 78.251.5.57 20900: WS2P connection timeout`
2019-04-15T17:09:10+02:00 - info: WS2P: Could not connect to peer 8t6Di3pL using `WS2P duniter.normandie-libre.fr 443: WS2P connection timeout`
2019-04-15T17:09:10+02:00 - info: WS2P: Could not connect to peer 5cnvo5bm using `WS2P g1.duniter.inso.ovh 443: WS2P connection timeout`
2019-04-15T17:09:10+02:00 - debug: WS2P: init: failed connection
2019-04-15T17:09:10+02:00 - debug: WS2P: init: failed connection
2019-04-15T17:09:10+02:00 - debug: WS2P: init: failed connection
2019-04-15T17:09:10+02:00 - info: WS2P: init: bundle of peers 3/9
2019-04-15T17:09:10+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:2cf9209c-2cab-4a43-9f3f-5852d76703dda5b6c9ae-cf3d-4f7d-9c17-7555be3fd086
2019-04-15T17:09:10+02:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:BDv28pi7c1GCbfZqcdEdXuMwubTjswepR1mAZW7YS9vt:abb6973b-d690-445c-aafc-528c63e0215329100de9-6dc7-459d-9fc7-b8c911aa5dea
2019-04-15T17:09:10+02:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:abb6973b-d690-445c-aafc-528c63e0215329100de9-6dc7-459d-9fc7-b8c911aa5dea
2019-04-15T17:09:10+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:22048df7-3f61-43ae-841f-e2771bbc7534612f1f61-9d4f-4732-876e-f5aa9ced7415
2019-04-15T17:09:10+02:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:FEcfFyZuAMuCeqANo4U1iRdbwcr8BP2C5nfh42FP6GGG:d202a2d6-c4d1-489d-9dc6-8248df1cc73b97366752-e356-463b-997c-d4d2f2b34edf
2019-04-15T17:09:10+02:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:d202a2d6-c4d1-489d-9dc6-8248df1cc73b97366752-e356-463b-997c-d4d2f2b34edf
2019-04-15T17:09:10+02:00 - trace: WS2P >>> sendCONNECT >>> WS2P:CONNECT:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:dd6dc78d-c7dd-40e5-ac4c-026348b0c2cdd73facca-8328-42ad-b928-bf9ecba3b2ac
2019-04-15T17:09:10+02:00 - trace: WS2P >>> registerCONNECT >>> WS2P:CONNECT:g1:CRBxCJrTA6tmHsgt9cQh9SHcCc8w8q95YTp38CPHx2Uk:caf09eb2-1cc1-455f-aeb0-e5d97687c1a5633927f1-d593-4678-9137-2d03f5655036
2019-04-15T17:09:10+02:00 - trace: WS2P >>> sendACK >>> WS2P:ACK:g1:ChU8caZaN1gZMD48C5XvrdFY2sWvgi4cmuNciPkqjF2S:caf09eb2-1cc1-455f-aeb0-e5d97687c1a5633927f1-d593-4678-9137-2d03f5655036
Moul
15 April 2019 15:22
2
La difficulté minumum du hash requise est suppérieur à ce qui a été obtenu :
Common Proof-of-Work difficulty level: 90, hash starting with `00000[0-5]*`
Le F n’est pas dans [0-5].
Moul
15 April 2019 16:48
4
Avec :
grep Done $HOME/.config/duniter/duniter_default/duniter.log
ou :
grep "Matched 5 zeros "$HOME/.config/duniter/duniter_default/duniter.log
tu devrais avoir une réponse à tes questions. Tu peux remplacer par 6 (zéros) la dernière commande.
Je plusse. Je me demandais s’il ne serait finalement pas plus efficace que tout le monde soit en “low-tech”, sur des raspi, ainsi le niveau serait le même pour tout le monde et la conso serait sacrément diminuée. Calcul plus lent, certes, mais plus équitablement distribué, une sorte de DU des calculs de blocs…
1 Like
Minons sur des Arduino Uno !
Il y a un truc que je ne comprends pas : à quoi sert la difficulté personnalisée si finalement il y a une difficulté commune ?
Oui ça j’ai compris et c’est tout à fait logique, ce qui est bizarre c’est cette difficulté commune qui a l’air d’empêcher la difficulté personnalisée de jouer son rôle.
Moul
15 April 2019 18:01
12
Il y a eu une proposition d’amélioration du protocole proposant preuve de travail encore moins énergivore, mais rien n’a été implémenté depuis.
3 Likes
jytou
15 April 2019 18:24
13
Si tu veux consommer moins d’électricité, tu peux diminuer ta difficulté personnalisée en diminuant la puissance de ton nœud (le % de CPU utilisé). Tu peux lire https://duniter.org/fr/wiki/duniter/preuve-de-travail/ et ce qui va t’intéresser, c’est la notion de « handicap ».
1 Like
ça vaut le coup avec un Pi ?