 Show Posts
|
|
Pages: « 1 2 3 [4] 5 »
|
Well. People keep adding so much more hashing power and removing it all the time...Thus it brings us long blocks. If we stayed at 1 simple speed without it changing like 2-5+ times in just 1 week. It sucks a week or so ago. We were solving blocks like it was raining. Now. We solving them like turtles. Slow and Steadily.
I wonder if people will stop hopping and increasing/decreasing their hash power.
Who am i kidding..... Why would people stop... that would be to easy
Please read and understand Cris ! Thank You ! I dont understand why people always say that. It wouldnt be posted if i didnt read and understand it. just stating the obvious thats all. Than sadly you have those super critical people. Shit if you dont like the post or the wording. Dont comment.. simple as that. Instead of commenting to make a big deal about it Sorry my English is bad. I just wanted to emphasize that your theory is more than good! Minors must stop changing pool every 5 minutes when luck has left us for only a few hours .. |
|
|
|
Well. People keep adding so much more hashing power and removing it all the time...Thus it brings us long blocks. If we stayed at 1 simple speed without it changing like 2-5+ times in just 1 week. It sucks a week or so ago. We were solving blocks like it was raining. Now. We solving them like turtles. Slow and Steadily.
I wonder if people will stop hopping and increasing/decreasing their hash power.
Who am i kidding..... Why would people stop... that would be to easy
Please read and understand Cris ! Thank You ! |
|
|
|
|
Thank you for your answer , so I'll go to a seer =)
|
|
|
|
|
The price of bitcoin is not likely to drop?
|
|
|
|
It's beautiful for the smalls miners  |
|
|
|
|
Faut arrêter de croire au Père Noël les gars.
3,5x en 48h
|
|
|
|
Conclusion hâtive P4rker, attendons d'en voir un peut plus... http://www.bitcoin.fr/post/Bitcoin-%C3%A0-Cernay-l%C3%A8s-ReimsCertainement présent lors de cet event, je ne manquerais pas de venir vous en dire plus sur cette structure et ces initiatives. Si quelqu'un n'est pas trop loin je l'encourage à venir voir ce qu'il en est. Moi je suis curieux de voir ça et je ne suis pas trop loin. Je ne manquerais pas de signaler la description des produits, car il est vrai que... Et tu sembles avoir le même objectif que kev pour preuve ton premier message poster sur le forum est celui-ci :Bonjour, Ma découverte des cryptos remonte ... Bonne question! Mineur solitaire orientaté Altcoin, notamment le XMR. Besoin d’approfondir les choses et de participer plus, une pool de minage XMR est née. Maintenant ... Une pool en solitaire ça ne va pas trop bien ^^ Je viens en parler, partager ... Avec pour objectif de regrouper plusieurs mineurs autour d'une ou plusieurs pools privées (Fee 0%), un irc et pourquoi pas de temps en temps une petite conf skype. La pool est lancée, il n'y à plus qu'a tester. Dans le cas ou quelqu'un serais intéressée pour participer, envoyer moi un petit mp pour plus d'informations et faire connaissance. Bonne continuation à vous  Avec tes fameux petits points qui te trahissent.... |
|
|
|
Conclusion hâtive P4rker, attendons d'en voir un peut plus ... http://www.bitcoin.fr/post/Bitcoin-%C3%A0-Cernay-l%C3%A8s-ReimsCertainement présent lors de cet event, je ne manquerais pas de venir vous en dire plus sur cette structure et ces initiatives. Si quelqu'un n'est pas trop loin je l'encourage à venir voir ce qu'il en est. Moi je suis curieux de voir ça et je ne suis pas trop loin. Je serais ravi de me tromper, mais je ne pense pas qu'on est affaire à des gens très sérieux. Et pourquoi ma conclusion serait hâtive ? Regarde les éléments que je t’amène sur la table ! Ne serait-ce pas plutôt la publication officiel de ce projet qui est hâtive ? |
|
|
|
Pour la description de certains produits, j'avoue que la traduction n'est pas terrible...après l'entreprise se trouve dans un local à l'étage mais n'y a rien de marquer à l'extérieur c'est normal.
Ce que j'aimerais c'est un tuto qui m'explique comment creer un stratum bitcoin. Miner des bitcoins sur leur propre serveur à eux avec leur propre machine qui ont acheté mais aussi à ceux qui ont acheté des offres de cloud chez eux.
Pour l'instant ils ont déjà des programmes pour les monnaies en script (litecoin etc.) qui tourne mais ils n'ont pas pour bitcoin.
Votre société parait tordu, le site n'est pas du tout peaufiné, un stagiaire pour lancer une pool j'y crois que moyennement. Vous nous parlez d'un local à l'étranger ? Qui répond au numéro français dans ce cas là ? J'ai trouvé une offre d'emploi de Digital Currency sur vivastreet qui mentionne la domiciliation de votre entreprise à Cernay-Les-Reims : bonjour, Nous sommes spécialisé dans la vente de produit informatique et téléphonique ainsi que des contrats de placement produit … L'entreprise est situé a cernay les reims…. Pour plus d' information veuillez nous contacter a l'adresse mail suivante en y joignant un cv : contact@digital-currency.fr ou au 01.73.79.49.44 un recruteur se chargera de vous répondre. Vous pouvez consulter notre site web contact@digital-currency.frNous sommes a la recherche de commerciaux afin de monter une équipe sédentaire et téléphonique ….Pour les meilleurs d'entre eux, une prime sera versée en plus sur chaque vente Nous sommes a la recherche de personne motivé avec une facilité a communiquer avec le client … Quel entrepreneur sérieux rédige une offre d'emploi avec une annonce qui commence avec une minuscule, des phrases qui finissent par quatre points et plein de faute de grammaire et d'orthographe ? Quel entrepreneur sérieux n'a pas déclarer son entreprise au registre du commerce ? Je me demande même si cette offre d'emploi n'est pas là pour récupérer des documents réels afin de faire des usurpations. N'aider pas ce clown, c'est n'importe quoi. |
|
|
|
Sur le Whois du domaine digital-currency.fr : nic-hdl: WR629-FRNIC
type: PERSON
contact: Wadii Rachid
address: 2, rue Drouet d'Erlon
address: 51420 Cernay les Reims
country: FR
phone: +33 1 73 79 49 44 Je n'ai trouvé aucune société domiciliée à cette adresse, ni à ce nom là. A fuir comme la peste..... selon moi. |
|
|
|
Digital Currency.... Regarder la description des produits, ça fait peur : Un des mineurs les plus efficaces sur terre
Construit par une amende la fabrication d'une excellente réputation pour la qualité
Connexion réseau: Ethernet
453 Gh / s à 355 watts au mur avec une haute efficacité énergétique
Autonome, à l'exception du watt or PSU 600 recommandé (non inclus)
Il ya 4 connecteurs PCI-e pour entrée + 12V DC. Seulement deux sont nécessaires à moins que vous sur-horloge. (Nous ne recommandons pas trop horloge)
Le contrôleur de la carte avec une interface facile à utiliser l'interface graphique
Les dissipateurs de chaleur sur mesure montés sur les planches de hachage, une boîte sur S3 pour contrôler la circulation de l'air, deux ventilateurs montés sur les deux faces avant et arrière des fans moyennes sont capables de fonctionner à une vitesse inférieure à dissiper toute la chaleur facilement. Cette conception permet de la course S3 niveau de bruit beaucoup plus faible.
Facilité de configuration, il suffit d'entrer votre piscine et mineur nom et votre sur les rangs
Reliable- plus de 20 pour cent de la totalité de l'espace Bitcoin Mining est Antminers |
|
|
|
{
"version" : 2010006,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 4965.91932780,
"blocks" : 231756,
"timeoffset" : -57,
"connections" : 9,
"proxy" : "",
"difficulty" : 0.02496399,
"testnet" : false,
"keypoololdest" : 1416617725,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
}
That was it! I was in a hurry! Thank you again wgd |
|
|
|
New node : 37.187.115.196:48481  But i found 3 blocks and my balance is empty : ./whirlcoind getinfo
{
"version" : 2010006,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 230462,
"timeoffset" : -57,
"connections" : 10,
"proxy" : "",
"difficulty" : 0.06451013,
"testnet" : false,
"keypoololdest" : 1416617723,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
} Any idea ? Thank you |
|
|
|
Finaly after 4 or 5 hours my windows wallet crashes like wgd :
connection timeout
trying connection [2001:0:9d38:6abd:874:5f0:b1f4:d639]:7788 lastseen=227.2hrs
received block 00000000201daa3ea5acbdc1fa7e0c31d79f893fb8f0f5fabdfe60b8be0297ba
CheckSyncCheckpoint: nHeight=900272, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000000201daa3ea5acbdc1fa7e0c31d79f893fb8f0f5fabdfe60b8be0297ba height=900272 log2_work=52.847835 tx=1275838 date=2014-11-15 18:13:29 progress=1.000000
ProcessBlock: ACCEPTED
connection timeout
trying connection 208.84.132.253:7788 lastseen=8.2hrs
connection timeout
trying connection 193.167.41.1:7788 lastseen=35.5hrs
getblocks 900272 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 119.95.2.122:7788 lastseen=5997.4hrs
connection timeout
socket recv error 10054
disconnecting node 60.173.10.169:7788
trying connection 208.85.4.86:11973 lastseen=4.0hrs
connected 208.85.4.86:11973
send version message: version 70001, blocks=900272, us=82.238.153.195:7788, them=208.85.4.86:11973, peer=208.85.4.86:11973
socket recv error 10054
disconnecting node 208.85.4.86:11973
trying connection 208.84.132.253:7788 lastseen=8.2hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
connection timeout
trying connection 105.237.131.168:7788 lastseen=152.7hrs
connection timeout
trying connection 213.87.137.179:7788 lastseen=482.0hrs
connection timeout
trying connection 88.190.22.60:7788 lastseen=8.1hrs
connection timeout
trying connection 78.11.41.198:7788 lastseen=5.4hrs
received block 0000000148dffeb2e195d7dff3bc2fa58b164b2b46fac0c693e9fe41e588de47
CheckSyncCheckpoint: nHeight=900273, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000148dffeb2e195d7dff3bc2fa58b164b2b46fac0c693e9fe41e588de47 height=900273 log2_work=52.847835 tx=1275839 date=2014-11-15 18:14:31 progress=1.000000
ProcessBlock: ACCEPTED
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 178.221.145.66:7788 lastseen=63.3hrs
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 50.78.40.241:11973 lastseen=225.0hrs
connection timeout
trying connection 213.221.55.130:7788 lastseen=202.7hrs
connection timeout
trying connection 78.30.170.155:7788 lastseen=5876.0hrs
connection timeout
trying connection 125.43.4.89:7788 lastseen=294.8hrs
trying connection 5.9.56.229:7788 lastseen=365576.5hrs
connection timeout
trying connection 125.43.11.215:7788 lastseen=633.5hrs
connection timeout
trying connection 85.10.194.50:7788 lastseen=365576.5hrs
connection timeout
trying connection 67.198.77.55:11973 lastseen=7.3hrs
connection timeout
trying connection 199.233.239.54:7788 lastseen=365576.5hrs
connection timeout
trying connection 178.221.145.66:7788 lastseen=63.3hrs
connection timeout
trying connection 60.173.10.169:7788 lastseen=365576.5hrs
connected 60.173.10.169:7788
send version message: version 70001, blocks=900273, us=82.238.153.195:7788, them=60.173.10.169:7788, peer=60.173.10.169:7788
trying connection 2.85.185.9:7788 lastseen=365576.5hrs
received block 0000000102e046622a67ab2c69dc6ddc749e7a03a31b5dd9ee2ce3051616d2a3
CheckSyncCheckpoint: nHeight=900274, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000102e046622a67ab2c69dc6ddc749e7a03a31b5dd9ee2ce3051616d2a3 height=900274 log2_work=52.847836 tx=1275840 date=2014-11-15 18:15:23 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
connection timeout
connection timeout
trying connection [2001:0:9d38:6ab8:c4e:4de:8ea3:17b9]:7788 lastseen=230.2hrs
connection timeout
trying connection [2001:41d0:a:68c4::1]:7788 lastseen=28.3hrs
connection timeout
trying connection 88.190.22.60:7788 lastseen=8.1hrs
connection timeout
trying connection 120.59.195.33:11973 lastseen=7.4hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
received block 00000001e56dd96a98ae262566a03730e2da357260a89290df1dda3cd4fe94f1
CheckSyncCheckpoint: nHeight=900275, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000001e56dd96a98ae262566a03730e2da357260a89290df1dda3cd4fe94f1 height=900275 log2_work=52.847836 tx=1275841 date=2014-11-15 18:15:58 progress=1.000000
ProcessBlock: ACCEPTED
connection timeout
trying connection 94.70.53.77:7788 lastseen=174.8hrs
connection timeout
trying connection 112.226.219.132:7788 lastseen=2955.2hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
socket recv error 10054
disconnecting node 60.173.10.169:7788
connection timeout
trying connection 67.255.7.120:7788 lastseen=16.8hrs
connection timeout
trying connection 193.167.41.1:7788 lastseen=35.5hrs
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 128.199.223.65:7788 lastseen=555.7hrs
connection timeout
trying connection 183.213.155.91:12875 lastseen=5.6hrs
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 77.105.42.60:7788 lastseen=57.4hrs
received block 000000012018d8dfebe52b9ae17037339f6ecf605b6cda3a545cd62cd6676108
CheckSyncCheckpoint: nHeight=900276, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=000000012018d8dfebe52b9ae17037339f6ecf605b6cda3a545cd62cd6676108 height=900276 log2_work=52.847837 tx=1275842 date=2014-11-15 18:16:57 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 213.87.141.226:7788 lastseen=290.0hrs
connection timeout
trying connection 74.96.81.14:7788 lastseen=296.8hrs
connection timeout
trying connection 98.140.223.180:7788 lastseen=503.1hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
connection timeout
trying connection 87.97.46.245:11973 lastseen=447.7hrs
received block 00000001ce46853581df4daa327874fe741c0b22ffc5887ca47a27a6205ea95d
CheckSyncCheckpoint: nHeight=900277, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000001ce46853581df4daa327874fe741c0b22ffc5887ca47a27a6205ea95d height=900277 log2_work=52.847837 tx=1275843 date=2014-11-15 18:17:08 progress=0.999999
ProcessBlock: ACCEPTED
trying connection 5.9.56.229:7788 lastseen=365576.5hrs
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 208.84.132.253:7788 lastseen=8.2hrs
connection timeout
trying connection 85.10.194.50:7788 lastseen=365576.5hrs
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 199.233.239.54:7788 lastseen=365576.5hrs
connection timeout
trying connection 77.105.42.60:7788 lastseen=57.4hrs
connection timeout
trying connection 60.173.10.169:7788 lastseen=365576.5hrs
connected 60.173.10.169:7788
send version message: version 70001, blocks=900277, us=82.238.153.195:7788, them=60.173.10.169:7788, peer=60.173.10.169:7788
trying connection 2.85.185.9:7788 lastseen=365576.5hrs
connection timeout
trying connection 125.43.4.17:7788 lastseen=462.2hrs
connection timeout
connection timeout
received block 0000000093153117d7a4c9f6533432f889dee97f4baa8aef285e77fc38414d0b
CheckSyncCheckpoint: nHeight=900278, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
trying connection 78.11.41.198:7788 lastseen=5.4hrs
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000093153117d7a4c9f6533432f889dee97f4baa8aef285e77fc38414d0b height=900278 log2_work=52.847837 tx=1275844 date=2014-11-15 18:17:48 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection [2001:41d0:52:d00::9da]:7788 lastseen=24.8hrs
received block 00000002114a215b30ff35acabe8a48a8c801bf11de60ee5deb27bf5aa9ebcbe
ProcessBlock: ORPHAN BLOCK, prev=00000001765935db592becb59f51f252f978aeb6e22238c299e0473dbea0c105
received block 00000001765935db592becb59f51f252f978aeb6e22238c299e0473dbea0c105
CheckSyncCheckpoint: nHeight=900278, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
CheckSyncCheckpoint: nHeight=900279, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
REORGANIZE: Disconnect 1 blocks; 00000001ce46853581df4daa327874fe741c0b22ffc5887ca47a27a6205ea95d..
REORGANIZE: Connect 2 blocks; ..00000002114a215b30ff35acabe8a48a8c801bf11de60ee5deb27bf5aa9ebcbe
Committing 3 changed transactions to coin database...
SetBestChain: new best=00000002114a215b30ff35acabe8a48a8c801bf11de60ee5deb27bf5aa9ebcbe height=900279 log2_work=52.847838 tx=1275845 date=2014-11-15 18:17:51 progress=0.999999
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 173.13.48.70:7788 lastseen=5.1hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.3hrs
connection timeout
trying connection 2.85.186.21:7788 lastseen=1349.9hrs
connection timeout
trying connection 113.190.244.18:7788 lastseen=9.5hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.4hrs
connection timeout
Flushed 11816 addresses to peers.dat 83ms
trying connection 78.11.41.198:7788 lastseen=5.4hrs
socket recv error 10054
disconnecting node 60.173.10.169:7788
received block 00000002685167521d31e6afac45aa038dc3f4205a2dbc1e25bd81903a90c9b7
nActualTimespan = 819 before bounds
GetNextWorkRequired RETARGET
nTargetTimespan = 600 nActualTimespan = 819
Before: 1d021376 0000000213760000000000000000000000000000000000000000000000000000
After: 1d02d571 00000002d571b5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5
CheckSyncCheckpoint: nHeight=900280, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000002685167521d31e6afac45aa038dc3f4205a2dbc1e25bd81903a90c9b7 height=900280 log2_work=52.847838 tx=1275846 date=2014-11-15 18:18:38 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 36.69.214.187:7788 lastseen=698.8hrs
connection timeout
trying connection 74.116.207.170:11973 lastseen=32.9hrs
connection timeout
trying connection 178.221.145.66:7788 lastseen=63.4hrs
connection timeout
trying connection 125.43.0.74:7788 lastseen=667.5hrs
connection timeout
trying connection 113.190.244.18:7788 lastseen=9.5hrs
connection timeout
trying connection 173.13.48.70:7788 lastseen=5.1hrs
connection timeout
trying connection 113.190.244.18:7788 lastseen=9.5hrs
received block 000000023d6d9765ce01e5a4dc48274525b6c44bb0eddab52ef8721bd1565210
CheckSyncCheckpoint: nHeight=900281, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=000000023d6d9765ce01e5a4dc48274525b6c44bb0eddab52ef8721bd1565210 height=900281 log2_work=52.847838 tx=1275847 date=2014-11-15 18:19:17 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 173.13.48.70:7788 lastseen=5.1hrs
received block 0000000297a2dc34a18fb1fc839072942f963694bdda659f431590d120a566b6
CheckSyncCheckpoint: nHeight=900282, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000297a2dc34a18fb1fc839072942f963694bdda659f431590d120a566b6 height=900282 log2_work=52.847838 tx=1275848 date=2014-11-15 18:19:25 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 88.190.22.60:7788 lastseen=8.1hrs
connection timeout
trying connection 78.11.41.198:7788 lastseen=5.5hrs
connection timeout
trying connection 2.85.190.125:7788 lastseen=62.4hrs
connection timeout
trying connection 5.9.56.229:7788 lastseen=365576.6hrs
trying connection 208.84.132.253:7788 lastseen=8.3hrs Close and restart the wallet solve this problem.....
|
|
|
|
On my server, when i start getpeerinfo|grep subver : ***@***:/home/pqt/QubitCoin/src# ./QubitCoind getpeerinfo|grep subver
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.3.15/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.3.15/",
"subver" : "/Satoshi:0.8.3.15/",
"subver" : "/Satoshi:0.8.4.2/",
"subver" : "/Satoshi:0.8.4.2/",
"subver" : "/Satoshi:0.8.3.15/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.3.15/",
"subver" : "/Satoshi:0.8.4.2/",
"subver" : "/Satoshi:0.8.4.1/",
"subver" : "/Satoshi:0.8.4.2/",
"subver" : "",
And getinfo : ***@***:/home/pqt/QubitCoin/src# ./QubitCoind getinfo
{
"version" : 80401,
"protocolversion" : 70001,
"walletversion" : 60000,
"balance" : *,
"blocks" : 900055,
"timeoffset" : -36,
"connections" : 22,
"proxy" : "",
"difficulty" : 86.85659852,
"testnet" : false,
"keypoololdest" : 1415554595,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"errors" : ""
} In my log file for the same block : received block 0000000127a55a99697d786569e8a2ad38b280bef09baa9e38efce5a8eafcede
CheckSyncCheckpoint: nHeight=897937, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000127a55a99697d786569e8a2ad38b280bef09baa9e38efce5a8eafcede height=897937 log2_work=52.847152 tx=1273503 date=2014-11-14 23:19:05 progress=0.997261
ProcessBlock: ACCEPTED No error on my server ! |
|
|
|
good job P4rkeR, but we have a network of nodes that are making noise - every now and again stuck windows wallet. On linux network fortunately does not stop
This new node is on linux network |
|
|
|
|
New node : 37.187.115.196:7788
|
|
|
|
|
