Author

Topic: [ANN][AMS] AmsterdamCoin™ | 100% PoS, Masternodes, Obfuscation, Seesaw - page 150. (Read 272323 times)

newbie
Activity: 31
Merit: 0
time to buy AMS waiting dump price 150 sat  Cheesy

It's very cheap to own some coins or making a masternode .
I will join this project and see what happens next?
For a masternode 100,000 AMS are needded, right ?
@500 sats each (if you buy 100,000 AMS in Yobit, price will pump over the current 300 sats), then 0.5 btc, right ?

And what is the return for these 0.5 btc ?

Yobit seems to be in maintenance again  Sad
What is wrong with the wallet or is it a foul of yobit again?
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
Who knows a good designer? I want to make a graphical overview of the roadmap.

keesdewit ...

how about fixing this issue before marketing - which seems to be a constant mate? ...

no matter how many times - and no matter what settings are used - we have a db error ...

initially i thought it was the different bdb versions ... but its not ... this coin has this same error - no matter what bdb version is used ...

the pool has finally finished sync - but is having a major spit when it comes to the stability of the db ... this is unacceptable for a pool - which could explain why a lot of pools have shut the doors ...

i will continue trying different settings ... but this is a severe issue ..

i hope its only on our end that its happening ... but it seems this is the only coin with this issue in our cwi-pools system ...

ill keep at it mate ...

update ... ok - seems that its NOT a database issue - but a RPC issue ... when a block is hit - the RPC connection gets dropped to the daemon ... this has happened several times while syncing also - and i originally thought it was due to lack of full sync but my gut instincts were that it must be a coding / connection issue ... my gut instincts were right ...

the stratum is still running - the miner is still running - but the rpc issue is still there ... which means errors will exits and kill the pool when this happens ...

any ideas mate? ...

btw - enableaccounts=1 IS set in the conf ... and the only way to resurrect this is to restart the daemon ... which is ALWAYS bad news ...

this pool will stay in alpha mode until we can resolve this issue ...

#crysx

We have other pools running and also I am able to solo mine using the daemon or wallet. No problem at all.

ok ...

for the last couple of hours - i watched ...

with pool disconnected and stratum not accessing - the daemon disconnected watch package - watching the daemon getinfo ... by itself ...

its STILL disconnected - and ive found this so far - as i write this ...

Code:
2017-05-14 10:18:14 ProcessBlock: ORPHAN BLOCK 316, prev=e353d63121135f5f728275688e997018e0496e4abecea44c440af278b17d9d88
2017-05-14 10:18:34 ProcessBlock: ORPHAN BLOCK 317, prev=eae7d843bb84e8248f4bf39cb06132543b742b389e0d7afbab85c74540de7987
2017-05-14 10:18:40 ProcessBlock: ORPHAN BLOCK 318, prev=13642cba7fedb57cb2df82ebeec2e4b76d79c2775047e2ab97fa22bd5b538123
2017-05-14 10:18:44 ProcessBlock: ORPHAN BLOCK 319, prev=14aaac18cd70f654054c86de598977227b6736803cb8ef228bc81fe9bcd812ac
2017-05-14 10:19:05 ProcessBlock: ORPHAN BLOCK 320, prev=da6be945ede97eaa8f15fcf00609d7bbc13a1c01c903b32584455dbf9dc07adf
2017-05-14 10:19:36 ProcessBlock: ORPHAN BLOCK 321, prev=62d58eb902735ac3386d79d7f152dc6f61dd31513de2af5f6e4691f6db625215
2017-05-14 10:20:33 ProcessBlock: ORPHAN BLOCK 322, prev=bf82969272e67ee8415f48821db59bf71882b5e9e3ed0123093620931c2a474a
2017-05-14 10:21:26 ProcessBlock: ORPHAN BLOCK 323, prev=b7a232bbe46a82f0e37c545038b39f9e8d249790b4ff5c1a3ba8aec2ae6a45a3
2017-05-14 10:22:26 ProcessBlock: ORPHAN BLOCK 324, prev=7cddb0b1fbd2813d4a64816fc53afd531f9105132fd8e178788d933b0d9c986a
2017-05-14 10:22:47 ProcessBlock: ORPHAN BLOCK 325, prev=ed74dbb6cf46f440930d5db425cc17c8557f112eaccea0e5b70a00a596af8fdd
2017-05-14 10:23:10 ProcessBlock: ORPHAN BLOCK 326, prev=08e40f202c9bf55a81b372d8877fc68b681eb2afcd849037979ac003858c8867
2017-05-14 10:24:02 ProcessBlock: ORPHAN BLOCK 327, prev=b8431885f42bbbaab669392813c7070405147f66bed1a61cd7a25e4442a1cba0
2017-05-14 10:24:07 receive version message: version 61403, blocks=1059053, us=62.210.206.140:61510, them=[2001:0:9d38:6abd:1c45:c8d5
:35af:26da]:61510, peer=202.80.217.37:56558
2017-05-14 10:24:39 ProcessBlock: ORPHAN BLOCK 328, prev=4ada9b08ebdf1d775efc99edcd7ee2316f979ff3be57dd57d521d7c77c2c88a6
2017-05-14 10:25:00 ProcessBlock: ORPHAN BLOCK 329, prev=cf8d29d69a92d2db2c0d45e14f450e3ad94511ee17d5d13e0bc5822962bd10ce
2017-05-14 10:25:33 ProcessBlock: ORPHAN BLOCK 330, prev=27bf1dd9036ee5356c12a071d85862a0765a191daee855f9dccb64d6c696416a
2017-05-14 10:25:55 ProcessBlock: ORPHAN BLOCK 331, prev=3b3056f817655f986f268989cdeb971d7484309064b0bc149779d0cbf570fde5
2017-05-14 10:26:28 ProcessBlock: ORPHAN BLOCK 332, prev=f6193b6865b5052e2aae6cb69d3123a1559f151449f40b29558b7cbf56b3a92e
2017-05-14 10:26:48 ProcessBlock: ORPHAN BLOCK 333, prev=75f6cbf2bd924836f7fea9658868485e53a5f85dee4a40ddc18227cfe132f031
2017-05-14 10:27:02 ProcessBlock: ORPHAN BLOCK 334, prev=cd30011e1f7ef8444c00f22d4eb5b4b113febb7e9a54009afeaf717a4d2d61c1
2017-05-14 10:27:23 ProcessBlock: ORPHAN BLOCK 335, prev=64e8c458cecc06a3509b5388a04a0415af03009239f37356026c0dc5d87eb9f4
2017-05-14 10:27:46 ProcessBlock: ORPHAN BLOCK 336, prev=1bf4297d65fe3e169d17069a45e562c6ff54cfe22f7e7b9550ed5439b19765a3
2017-05-14 10:27:49 ProcessBlock: ORPHAN BLOCK 337, prev=e6c139d5d0226594036263d235f6668565661cf5d1c80891f68bccda9c25df64
2017-05-14 10:28:23 receive version message: version 61403, blocks=1058596, us=62.210.206.140:61510, them=[2001:0:9d38:953c:308f:badc
:4d86:5903]:61510, peer=178.121.166.252:47742
2017-05-14 10:28:23 Added time data, samples 28, offset +48 (+0 minutes)
2017-05-14 10:29:06 ProcessBlock: ORPHAN BLOCK 338, prev=82bed0e3c0ae741c7581ec23707a4b6e10fe42327c5dab95cf3a0edb5f53fdb4
2017-05-14 10:29:27 ProcessBlock: ORPHAN BLOCK 339, prev=2612914c58ce667f9e5acf6e71beb125b2a29832c477d114aa0f914d2d152df6
2017-05-14 10:29:38 ProcessBlock: ORPHAN BLOCK 340, prev=da51818e80ec0ad8ca4d2be1db9c600037382f98e46b6a3b6f1cbf1399e6a261
2017-05-14 10:30:02 ProcessBlock: ORPHAN BLOCK 341, prev=a3d8268ad231bf55266d42d4c49ffb8f4714d7dd88d6b01f0c5155753093b12c
2017-05-14 10:30:10 ProcessBlock: ORPHAN BLOCK 342, prev=208cbc9a162ad842f24cca61c2bf7d5940e879e06e8a30ea1c022f2b6ecbcef6
2017-05-14 10:30:17 receive version message: version 61403, blocks=1066787, us=62.210.206.140:61510, them=95.164.12.36:61510, peer=95
.164.12.36:49920
2017-05-14 10:30:26 ProcessBlock: ORPHAN BLOCK 343, prev=c57f6dd5257a5e2c9f9bfafe32e5aab28d870d695465fef6307752bb688de447
2017-05-14 10:32:26 ProcessBlock: ORPHAN BLOCK 344, prev=681a4881e6c9691302bb09b6450bc0b976d6602917ee5a7c22b0529fcfca999e
2017-05-14 10:32:26 ProcessBlock: ORPHAN BLOCK 345, prev=23a57f20c485ca1868a930cb7d9a236f389d9e4395cf490f3f29e64431294b6b
2017-05-14 10:32:26 ProcessBlock: ORPHAN BLOCK 346, prev=ed017e5f1743ea076e065798209eedffc1d64a00b09188f2abe0f329c7b576bb
2017-05-14 10:32:26 ProcessBlock: ORPHAN BLOCK 347, prev=b9b79ebd39f794b6f28253c0204157988c2e9d8b10e7eebb469311a7314c575f
2017-05-14 10:33:03 ProcessBlock: ORPHAN BLOCK 348, prev=33a17c948baeff90ca0d4716107825230739b0e10587c8e511b083b6e4635cff
2017-05-14 10:33:51 socket recv error 110
2017-05-14 10:34:26 ProcessBlock: ORPHAN BLOCK 349, prev=cdb7ee320488cca1c595d4e48b725ce0ff84e4c3d5b594077c9c68de9c46bcdb
2017-05-14 10:35:26 ProcessBlock: ORPHAN BLOCK 350, prev=c5e1465077665c3a5624664e3fdbc56e2f778aea97b1074d9171c51192a4370c
2017-05-14 10:35:27 ProcessBlock: ORPHAN BLOCK 351, prev=97c38cc3f3de9b165f01a3f8e7eb5cb9c6bedc801d6a06900364f5fb05fff318
2017-05-14 10:35:30 ProcessBlock: ORPHAN BLOCK 352, prev=daabb096870ce0d4cecc70d2dcde2064eb6c3e22091bb680060fa6d38cee8d2e
2017-05-14 10:36:37 ProcessBlock: ORPHAN BLOCK 353, prev=b81d6fb3db3173f23c3b5ca85392163009eb8aefaf3a5f61bbbc179a03f09234
2017-05-14 10:36:50 ProcessBlock: ORPHAN BLOCK 354, prev=cd170995a00415e9dae18ad06baeb680ec86a7f396bc3fdd8a0a131af8cfbb7b
2017-05-14 10:37:37 ProcessBlock: ORPHAN BLOCK 355, prev=47fb1e8040229e6c4718f96a9992b9502262982ba88c22913837527161b706ad
2017-05-14 10:38:19 ProcessBlock: ORPHAN BLOCK 356, prev=282610f588dbc2f1bc032c492519c4e5928755175fc66e1a1f4ba9dd3693c43d
2017-05-14 10:38:43 ProcessBlock: ORPHAN BLOCK 357, prev=f7a3eb532498a0e73b7e904738a299f367a76a1911b6771272f0b53870299584
2017-05-14 10:40:02 receive version message: version 61403, blocks=10017, us=62.210.206.140:61510, them=108.180.37.52:61510, peer=108
.180.37.52:59396
2017-05-14 10:40:34 ProcessBlock: ORPHAN BLOCK 358, prev=ea39dd374e8be243c236425504747d0ee8aa7048e584736a897572847e9fe9fe
2017-05-14 10:40:51 ProcessBlock: ORPHAN BLOCK 359, prev=c3cab15f774b86780685cfe66b72b4b1b097dc2bd5afc3162ffbcc6346656b8a
2017-05-14 10:41:37 ProcessBlock: ORPHAN BLOCK 360, prev=3170d093ebf68df78a7e87d7f8c121b89bafc4038847a7c1bd01e81d19676223
2017-05-14 10:41:53 ProcessBlock: ORPHAN BLOCK 361, prev=40d2aec960b844c78c8ec1236a6f85d2680c6b61d0186ba43f49c57b7a21854d
2017-05-14 10:41:54 ProcessBlock: ORPHAN BLOCK 362, prev=40d2aec960b844c78c8ec1236a6f85d2680c6b61d0186ba43f49c57b7a21854d
2017-05-14 10:43:05 ProcessBlock: ORPHAN BLOCK 363, prev=24cded5fb7027539136cae6a8275295b6c3ea6dbd7d78f7b937f30416d12fd24
2017-05-14 10:43:11 ProcessBlock: ORPHAN BLOCK 364, prev=5be7a23ad946e0bfe2b773ac4fac424c3331a2845ae78f8fbaf9bca226c6a77f
2017-05-14 10:43:38 ProcessBlock: ORPHAN BLOCK 365, prev=adf7c955fc00f0e2c8f960aa9039b8dbf38bd044bc1032c68b1714efd96b7da1
2017-05-14 10:44:02 ProcessBlock: ORPHAN BLOCK 366, prev=86d8e2bf1742017937e42985d613c256da656876e1a57dea921207a16f018cfd
2017-05-14 10:45:31 ProcessBlock: ORPHAN BLOCK 367, prev=8b933001427bdc2a98f034efb118750fe5dce08dba0d9852ad5f731ba4a89156
2017-05-14 10:45:58 ProcessBlock: ORPHAN BLOCK 368, prev=3841f60f85a771f0d2b9ed3124a1e5bf4171572d0da3753acdae013cb7bd46e4
2017-05-14 10:46:05 ProcessBlock: ORPHAN BLOCK 369, prev=782e0745515fa0b92dd01d6a00e8b1988ba987c6c4a66fe6063869b82df9181f
2017-05-14 10:46:47 ProcessBlock: ORPHAN BLOCK 370, prev=7a276c12194b5a0e95022f3d4fdb362e151be86d55ea2657931fbde8b6546339
2017-05-14 10:46:49 ProcessBlock: ORPHAN BLOCK 371, prev=9cc6a74fb62a239754842797b7ad6a11f30c23bd6da00dd822bcad3e1a477198
2017-05-14 10:46:57 ProcessBlock: ORPHAN BLOCK 372, prev=b030cbe1eccec91b687f3ff9c01d24eaea6bf6a18b6c7d5b4469e23528142ce9
2017-05-14 10:47:14 ProcessBlock: ORPHAN BLOCK 373, prev=73c188e568db9377640cd67d119ccea4436665c74f5c6c2b83fcd5769e82093c
2017-05-14 10:48:06 ProcessBlock: ORPHAN BLOCK 374, prev=c0f5818e22ccf01c663c1225831bf75362e0c2dfa31ca6d5d47d94b28860c881
2017-05-14 10:48:06 ProcessBlock: ORPHAN BLOCK 375, prev=b45c06c5b5934d74fe0191cb3775fc4e31d1a8332383d91338445eadab87c793
2017-05-14 10:48:54 ProcessBlock: ORPHAN BLOCK 376, prev=4c69a6c07e7909ca2d2e21df0ee20ea24402687a71f0339e6bfee5f002bb9b0f
2017-05-14 10:48:59 ProcessBlock: ORPHAN BLOCK 377, prev=4c69a6c07e7909ca2d2e21df0ee20ea24402687a71f0339e6bfee5f002bb9b0f
2017-05-14 10:50:58 ProcessBlock: ORPHAN BLOCK 378, prev=55a46c16bfba0aabf0e89076f51c19bc1bffbeefc8e4b97f3aebc164e86e5b4f
2017-05-14 10:51:35 ProcessBlock: ORPHAN BLOCK 379, prev=c66214d478347e2253ed1c43a091f9ac3007366873882ae53600f6523844b337
2017-05-14 10:51:45 socket recv error 110
2017-05-14 10:52:05 ProcessBlock: ORPHAN BLOCK 380, prev=bb125d944eac704c0fba98c97e6c3cd7d0b95b26f9351797515a411c38bea039
2017-05-14 10:52:23 ProcessBlock: ORPHAN BLOCK 381, prev=4d0c18df40681964852a300f0a0709ab1bd142a13b1da7c47abbd92303e3d9b4
2017-05-14 10:52:47 receive version message: version 61403, blocks=1060752, us=62.210.206.140:61510, them=[2001:0:9d38:6abd:1c45:c8d5
:35af:26da]:61510, peer=202.80.217.37:29359
2017-05-14 10:53:22 ProcessBlock: ORPHAN BLOCK 382, prev=c92ad54b4139d24f687cc8bc5c3e59814464876e5e3d2c23cd067d3c31ec97fa
2017-05-14 10:53:30 ProcessBlock: ORPHAN BLOCK 383, prev=c92ad54b4139d24f687cc8bc5c3e59814464876e5e3d2c23cd067d3c31ec97fa
2017-05-14 10:53:52 ProcessBlock: ORPHAN BLOCK 384, prev=dc1a816766b48f339980e77f9255e748871a8f49f3c7b2c3d57e2f8c741f0947
2017-05-14 10:54:08 ProcessBlock: ORPHAN BLOCK 385, prev=525e520dc58a06fd307d132fbeddc4528686a80aad6b4ea156563a6a4f127d10
2017-05-14 10:54:11 ProcessBlock: ORPHAN BLOCK 386, prev=4b9aca866a828daebd5f3f170b64a03f8942fe9fbb39201bcd2a1505f9a98832
2017-05-14 10:55:30 ProcessBlock: ORPHAN BLOCK 387, prev=7185b0a38703fc91293d3282ecbb2896728812ad364e17ddba02857720caf9dd
2017-05-14 10:56:28 ProcessBlock: ORPHAN BLOCK 388, prev=5a0f2ac257e8e5db870cc03e8754aaf5f04c2321f0751b7b8af92042a809b496
2017-05-14 10:56:29 ProcessBlock: ORPHAN BLOCK 389, prev=55602cd25af818a7e89e3a9e1ee410166a166ffd1b1f33694c207f04baa31dc9
2017-05-14 10:56:34 ProcessBlock: ORPHAN BLOCK 390, prev=a06c8901cc74dffe718834d183497de59fd33df085cfe24e0a97acfc28f96bd2
2017-05-14 10:56:51 ProcessBlock: ORPHAN BLOCK 391, prev=b20135115f37cd48a626521622f64199ff7066741279d765aa07688f762e4f81
2017-05-14 10:57:06 ProcessBlock: ORPHAN BLOCK 392, prev=29d7408c65e2e8026c567bd25567cce5d8ed354a2f5cef4ca6a6c078900b4ffe
2017-05-14 10:57:45 ProcessBlock: ORPHAN BLOCK 393, prev=fa84dadbc3ce0d3faee139cb503115a0a832d67abf5344dab944648112bb2e8a
2017-05-14 10:57:50 ProcessBlock: ORPHAN BLOCK 394, prev=74f7ca8b4f59c12f5ca8f162296ddad18189ee2e7760b5c1d9c168441dba5278
2017-05-14 10:58:04 ProcessBlock: ORPHAN BLOCK 395, prev=4e187cd44c065b5e832cbe0fec6501123206a0af183f42fcb626db634dfc77fe
2017-05-14 10:58:10 ProcessBlock: ORPHAN BLOCK 396, prev=06abf31c0c14a541a38f8b7c3e8aa60543a3eafd4244b2a75630e20ee5710d13
2017-05-14 10:58:26 ProcessBlock: ORPHAN BLOCK 397, prev=37295751fd02fa457cda4ca5939f8645616fd9daf07f4f62e89c91afdb71c2f3
2017-05-14 10:59:26 ProcessBlock: ORPHAN BLOCK 398, prev=61e4616cadd1c0cb3c02ec4357169324177222680921a286b2ec762081be77af
2017-05-14 10:59:51 ProcessBlock: ORPHAN BLOCK 399, prev=fd0814c15f8c6ff549cae4cb60661a8160b6cebbb6542a472c7745bb3a1539d1
2017-05-14 11:00:47 ProcessBlock: ORPHAN BLOCK 400, prev=a04d55cb45bb0af0ebfc3427cea92a7dc5397779531a204a2bf514a10604c912
2017-05-14 11:00:48 receive version message: version 61403, blocks=1062955, us=62.210.206.140:61510, them=100.75.126.67:61510, peer=1
91.237.170.168:2880
2017-05-14 11:01:11 ProcessBlock: ORPHAN BLOCK 401, prev=11e0f673c27c9e114712ec2a9246acdc94040392fce29cc65dabc5538ef9dfa1
2017-05-14 11:01:22 ProcessBlock: ORPHAN BLOCK 402, prev=f9b834e6aaf006e09d30b2dee3136c28159504f1078a8e071fec640c096ff047
2017-05-14 11:01:45 ProcessBlock: ORPHAN BLOCK 403, prev=13b9bcdd230e12c6aa61f8e71b47da03ff4aa3b33beb855ca9a61ac9f5ebbd5b
2017-05-14 11:01:52 ProcessBlock: ORPHAN BLOCK 404, prev=394f636396b9b61bd1858decca6d070ffb2d86c9bda0af11b5dc795572ba46fe
2017-05-14 11:01:54 ProcessBlock: ORPHAN BLOCK 405, prev=bfd2e132ec4b93c5b51c5dfb489758fa43cc0a73ba844fde91383d7c6f660b0c

now im no newbie kees - and im certainly NOT against the coin or your coding 'skills' ... in fact - im excited about it - mainly because of the coin 'fetaures' and the algo - my fav Smiley ...

but facts are facts ... this coin is the ONLY one doing this in our entire system - and its built on the SAME framework - the SAME os - the SAME systems and method its built ...

other pools? ... ok - and they have NO issues? ...

why is it that even the ams block explorer built on iquidus - that is used for many many many other coins also - is locked at block 1065918? ... rpc call drop also possibly? ... time to restart the daemon me thinks Wink ...

https://www.amsterdamblockchain.info/ ...

there is something inherently wrong with the rpc code here mate - and if you wish to just shrug it off and not take my word for it - then this coin has a bleak future indeed ...

im mentioning this to you as a highly experienced 'crypto guy' from ( almost ) the beginning of crypto - and you are disregarding what im mentioning and warning you about ...

apart from all this - it begs the question also ... so if these pools and others are not having ANY issues - why are there so LITTLE - if ANY - running now? ...

i bet i know the answer to that - if this is the way you are shrugging my concerns off as just rubbish ...

#crysx
sr. member
Activity: 810
Merit: 444
@dev.
What about signature campaign : is there a public data sheet for the monitoring ?
When is the end ? The payment ?
sr. member
Activity: 810
Merit: 444
time to buy AMS waiting dump price 150 sat  Cheesy

It's very cheap to own some coins or making a masternode .
I will join this project and see what happens next?
For a masternode 100,000 AMS are needded, right ?
@500 sats each (if you buy 100,000 AMS in Yobit, price will pump over the current 300 sats), then 0.5 btc, right ?

And what is the return for these 0.5 btc ?
newbie
Activity: 32
Merit: 0
time to buy AMS waiting dump price 150 sat  Cheesy

It's very cheap to own some coins or making a masternode .
I will join this project and see what happens next?
copper member
Activity: 1024
Merit: 513
txbit.io - cryptocurrency exchange
Who knows a good designer? I want to make a graphical overview of the roadmap.

keesdewit ...

how about fixing this issue before marketing - which seems to be a constant mate? ...

no matter how many times - and no matter what settings are used - we have a db error ...

initially i thought it was the different bdb versions ... but its not ... this coin has this same error - no matter what bdb version is used ...

the pool has finally finished sync - but is having a major spit when it comes to the stability of the db ... this is unacceptable for a pool - which could explain why a lot of pools have shut the doors ...

i will continue trying different settings ... but this is a severe issue ..

i hope its only on our end that its happening ... but it seems this is the only coin with this issue in our cwi-pools system ...

ill keep at it mate ...

update ... ok - seems that its NOT a database issue - but a RPC issue ... when a block is hit - the RPC connection gets dropped to the daemon ... this has happened several times while syncing also - and i originally thought it was due to lack of full sync but my gut instincts were that it must be a coding / connection issue ... my gut instincts were right ...

the stratum is still running - the miner is still running - but the rpc issue is still there ... which means errors will exits and kill the pool when this happens ...

any ideas mate? ...

btw - enableaccounts=1 IS set in the conf ... and the only way to resurrect this is to restart the daemon ... which is ALWAYS bad news ...

this pool will stay in alpha mode until we can resolve this issue ...

#crysx

We have other pools running and also I am able to solo mine using the daemon or wallet. No problem at all.
copper member
Activity: 1024
Merit: 513
txbit.io - cryptocurrency exchange
Who knows a good designer? I want to make a graphical overview of the roadmap.

I think I can arrange that. Free of cost Smiley

Vegas

Cool, how could I forget to ask my friend  Wink
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
Who knows a good designer? I want to make a graphical overview of the roadmap.

keesdewit ...

how about fixing this issue before marketing - which seems to be a constant mate? ...

no matter how many times - and no matter what settings are used - we have a db error ...

initially i thought it was the different bdb versions ... but its not ... this coin has this same error - no matter what bdb version is used ...

the pool has finally finished sync - but is having a major spit when it comes to the stability of the db ... this is unacceptable for a pool - which could explain why a lot of pools have shut the doors ...

i will continue trying different settings ... but this is a severe issue ..

i hope its only on our end that its happening ... but it seems this is the only coin with this issue in our cwi-pools system ...

ill keep at it mate ...

update ... ok - seems that its NOT a database issue - but a RPC issue ... when a block is hit - the RPC connection gets dropped to the daemon ... this has happened several times while syncing also - and i originally thought it was due to lack of full sync but my gut instincts were that it must be a coding / connection issue ... my gut instincts were right ...

the stratum is still running - the miner is still running - but the rpc issue is still there ... which means errors will exits and kill the pool when this happens ...

any ideas mate? ...

btw - enableaccounts=1 IS set in the conf ... and the only way to resurrect this is to restart the daemon ... which is ALWAYS bad news ...

this pool will stay in alpha mode until we can resolve this issue ...

#crysx
legendary
Activity: 1524
Merit: 1001
NOBT - WNOBT your saving bank◕◡◕
What is the normal price per AmsterdamCoin?

What is normal these day's?


We will soon see what the real value of AmsterdamCoin is, you decide...
We represent the early immigrants to the New World, this is the world of cryptocurrencies by its own laws.this is a virgin world and no law has yet been established for this world. 
member
Activity: 130
Merit: 10
What is the normal price per AmsterdamCoin?

What is normal these day's?


We will soon see what the real value of AmsterdamCoin is, you decide...
hero member
Activity: 628
Merit: 500
No banking,Only Bitcoin!
What is the normal price per AmsterdamCoin?
sr. member
Activity: 1918
Merit: 268
20BET - Premium Casino & Sportsbook
I've received bounty just that wallet has not worked well on yobit a few days ago so price is down, i think for the price will go again on 1k satoshi
legendary
Activity: 1610
Merit: 1003
"Yobit pump alert software" Link in my signature!
Who knows a good designer? I want to make a graphical overview of the roadmap.

I think I can arrange that. Free of cost Smiley

Vegas
legendary
Activity: 1316
Merit: 1145
any nodes my wallet stuck at block 1057296
or maybe any new bootstrap?

addnode=108.180.149.143:61510
addnode=134.90.155.150:61510
addnode=136.144.133.21:61510
addnode=167.114.103.43:61510
addnode=178.158.146.102:61510
addnode=178.62.204.185:61510
addnode=213.108.119.84:61510
addnode=24.160.59.242:61510
addnode=31.6.102.146:61510
addnode=45.63.101.182:61510
addnode=46.119.158.143:61510
addnode=68.71.58.226:61510
addnode=73.10.255.44:61510
addnode=77.130.253.156:61510
addnode=81.169.178.19:61510
addnode=83.162.211.100:61510
addnode=85.175.216.200:61510
addnode=85.214.152.3:61510
addnode=89.165.247.173:61510
addnode=91.224.235.73:61510
addnode=94.181.80.211:61510

You can also try to restart the wallet.

still stuck, now i delete all chace except wallet.dat and running it with bootstrap, hope can running perfectly.
i will update it if i succes instal it
copper member
Activity: 1024
Merit: 513
txbit.io - cryptocurrency exchange
Who knows a good designer? I want to make a graphical overview of the roadmap.
hero member
Activity: 1638
Merit: 518
time to buy AMS waiting dump price 150 sat  Cheesy
legendary
Activity: 2912
Merit: 1091
--- ChainWorks Industries ---
any nodes my wallet stuck at block 1057296
or maybe any new bootstrap?

addnode=108.180.149.143:61510
addnode=134.90.155.150:61510
addnode=136.144.133.21:61510
addnode=167.114.103.43:61510
addnode=178.158.146.102:61510
addnode=178.62.204.185:61510
addnode=213.108.119.84:61510
addnode=24.160.59.242:61510
addnode=31.6.102.146:61510
addnode=45.63.101.182:61510
addnode=46.119.158.143:61510
addnode=68.71.58.226:61510
addnode=73.10.255.44:61510
addnode=77.130.253.156:61510
addnode=81.169.178.19:61510
addnode=83.162.211.100:61510
addnode=85.175.216.200:61510
addnode=85.214.152.3:61510
addnode=89.165.247.173:61510
addnode=91.224.235.73:61510
addnode=94.181.80.211:61510

You can also try to restart the wallet.

our pool wallet is about 70% the way there ...

we have built it so that it is a node also - so if you add it as a node - it will work ...

when it syncs - we will be looking for miners to hash on the lodiff ( low difficulty ) and hidiff ( high difficulty ) ports to test and see how it runs ...

if you want to add it as a node now - just add the following into your amsterdamcoin.conf file ...

Code:
addnode=pool.chainworksindustries.com

this goes for all the supported pools we have running ... though the address is bound to change later when we separate the stratum and pool into separate servers ...

#crysx
member
Activity: 130
Merit: 10
any nodes my wallet stuck at block 1057296
or maybe any new bootstrap?

addnode=108.180.149.143:61510
addnode=134.90.155.150:61510
addnode=136.144.133.21:61510
addnode=167.114.103.43:61510
addnode=178.158.146.102:61510
addnode=178.62.204.185:61510
addnode=213.108.119.84:61510
addnode=24.160.59.242:61510
addnode=31.6.102.146:61510
addnode=45.63.101.182:61510
addnode=46.119.158.143:61510
addnode=68.71.58.226:61510
addnode=73.10.255.44:61510
addnode=77.130.253.156:61510
addnode=81.169.178.19:61510
addnode=83.162.211.100:61510
addnode=85.175.216.200:61510
addnode=85.214.152.3:61510
addnode=89.165.247.173:61510
addnode=91.224.235.73:61510
addnode=94.181.80.211:61510

You can also try to restart the wallet.
sr. member
Activity: 810
Merit: 444
What is the reward for a masternode ?
legendary
Activity: 1316
Merit: 1145
any nodes my wallet stuck at block 1057296
or maybe any new bootstrap?
Jump to: