Seems to be down again.  |
|
|
|
|
Interested in adding Boost to coinwallet.co - however I cannot seem to find the source..?
|
|
|
|
Cannot sync on:
"version" : "v3.5.4.9-g-research",
Any extra active nodes?
Here are some nodes from my peerinfo, hope it helps you. addr" : "51.254.201.68:32749", "addr" : "188.228.30.3:32749", "addr" : "174.52.67.250:32749", "addr" : "24.129.215.34:32749", "addr" : "75.185.117.254:32749", "addr" : "31.168.88.197:32749", "addr" : "174.95.106.239:32749", Thanks, however I still cannot get the Gridcoin client synced. Just get endless errors: 12/21/15 15:03:20 connect() failed after select(): Connection refused 12/21/15 15:05:41 connect() failed after select(): Connection refused 12/21/15 15:08:02 connect() failed after select(): Connection refused 12/21/15 15:10:23 connect() failed after select(): Connection refused 12/21/15 15:12:44 connect() failed after select(): Connection refused 12/21/15 15:15:05 connect() failed after select(): Connection refused 12/21/15 15:17:26 connect() failed after select(): Connection refused 12/21/15 15:19:47 connect() failed after select(): Connection refused 12/21/15 15:22:08 connect() failed after select(): Connection refused etc.. |
|
|
|
Thanks, it is strange. Because of some problems i removed the data folder and started to synchronize from block 1 on. But i still get the sign "no connections" :/
Here are some active nodes: addnode=204.11.237.233 addnode=138.91.64.21 addnode=144.76.239.66 addnode=108.91.74.25 addnode=2602:306:c5b4:a190:941:98aa:b07:c9c0 addnode=195.200.244.73 addnode=101.165.90.37 ref: http://www.blocktree.io/peers/XAI/ |
|
|
|
|
Cannot sync on:
"version" : "v3.5.4.9-g-research",
Any extra active nodes?
|
|
|
|
Why do they treat their most loyal, long term customers like this?
I assume not because they want to but because something is seriously not right over at Cryptsy. What that could be I don't know, but can't wait to find out. |
|
|
|
If you look at the block explorer it seems that stakes are generated by the deposit addresses at C-CEX. Do those stakes get credited to the deposit address or does C-CEX get the stakes as an exchange?
It doesn't matter they cost nothing. @DuckYeah! lost his interest as any kid and Fantom will die soon. Give the guy a chance, his last post was only a day and a half ago or something.  |
|
|
|
resynching now.
Waiting to see what will happen, but, I think, I'll lost all coins.
Coins never disappear. If you sent coins to an address on the wrong block chain they did not actually go anywhere, in terms of the correct block chain. Its just your wallet thinks they were sent. Worst case scenario, dump your private keys and import into a new wallet and your coins will 'auto-magically' reappear. |
|
|
|
I have nothing against you, you have your own interests to take care and CLAM rules allowed you to dig and sell whenever you want.
Revealing your existence and the number of coins you own, in addition to your selling pressure, has probably been crucial for this price dump.
But the main question is what now? Where do we go from now? Cause if this the whole plan, you digging and dumping, I m afraid you wont have anyone to sell to. Cause I know I would not place a single satoshi as a buy order knowing the price s gonna go only down. Also, only a noob would enter the market now and buy so new people re out too. I know some people re gonna say I m sharing negative marketing to CLAM but I would not like for these noobs who enter PoS for the first time to come here and lose their money without even having a chance to profit. On the other hand, I would like CLAM to go down, ever. I hope you see my point, what do we do now? Where does CLAM go from here?
Not to mention the fact I hope you do plan to keep some of your CLAM to stake and profit from PoS in the future as well. So, dev team, community, where do we go from here? What is the way out? Sitting and doing nothing isnt cause one does not need to be a genius to figure out where all this is gonna end if nothing s being done.
No doubt, the digging was the catalyst of the price dump. But CLAMs were previously overpriced. The price today is closer to the right price given the current situation: there are potentially still millions of undug CLAMs and the only use case for clams is JustDice. I think you and others are focused way too much on the price of CLAM. If your only interest in Clam is to profit from it then Clams won't go anywhere. The price matters very little. For Clams to succeed, there needs to more reasons to own Clams. Haha. We re focusing on the price of CLAM?? So why did you dump any of them if you believed so much in reasons to own CLAMS? You could have staked all of them and sell stakes only. I think you are missing his point. What I think he is trying to say is aside from the price there are no reasons to own Clams apart from JustDice. Killing the dig is the only option I can think of for CLAM to survive. If I am mistaken and there s something wrong with my logic, pls show me where I am wrong. I am an easy guy to talk to.
Killing the dig makes Clams just like any of the hundreds (thousands) of other altcoins out there. The dig was the only thing that made Clams what it is. Like I said before the price was unrealistically high, probably still too high - especially if a couple more whales come along. |
|
|
|
[quote author=ethought link=topic=408268.msg13081439#msg13081439 date=1448605468]
2015-11-27 06:18:35 connect() to 69.164.198.161:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 66.228.56.115:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 104.200.17.141:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 45.79.149.192:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)
Any idea why this might be happening? I synced with no problems a few days ago on the last Digibyte version.
[/quote]
It appears you are attempting to connect on port 12025. It should be 12024. 12025 is the testing port. Did you compile the wallet yourself? Which branch did you use? The tesnet currently has 4 blocks on it I believe  I was using the digispeed branch, looking at the commits for digispeed-release it is clear I should be using the digispeed-release branch. Might be worth making that clear on the Github page. |
|
|
|
Is there a pool for this coin?
No Sir. PoW (Proof of Work) ended and BitBean is now pure PoS (Proof of Sprout). To begin Sprouting after you have sent at least 1,000 BitBeans and after you encrypt your Vault for the first time, you should select "Unlock Vault" from the Settings Menu or new Context Menu (RMB click a blank area of space in the new Wallet.) BitBeans mature after about 6 hours, they will compete on the network with other Beans that have matured. Source is getting cleaned in preparation for Java migration, so PoW code will be removed from source in v1.2 Best Regards, Shawn Kent (aka BitBeaner) Project Manager & Lead Developer www.bitbean.orgWe have a POS pool running for Bitbean at https://www.coinwallet.coThank you for the post. Could you please update the BitBean logo on your site? You can find the new logo here: http://www.bitbean.org/downloads.htmlLogo updated, thanks. |
|
|
|
Issues continue.
Can you please provide a list of up to date nodes?
rpcuser=yourusername rpcpassword=yourpassword algo=scrypt rpcport=14022 port=12024 addnode=216.250.125.121 addnode=69.164.198.161 addnode=66.228.56.115 addnode=104.200.17.141 addnode=45.79.149.192 addnode=104.237.137.28 addnode=45.33.7.79 addnode=45.79.10.59 If anyone is running a dedicated node please quote this post with an IP if you would like to help seed the network in instances like this and be added to the OP and website. Seems like all connections to nodes are getting refused. $tail -n 200 debug.log
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 482, prev=362a475393c6b3f3c7fff79f1e1b12a14d7be72db9be999d4c2811eeb0b4f785
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 483, prev=13004255db26881f4f86b0c72d41707871bf1163e939b5ab2e62b063ae13394c
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 484, prev=cafc82996eb4d40137a2c985578deee1f49efb748c442c51733b63466d8eb536
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 485, prev=273174ede619f24540f4b4508461f0a2948b95fd07a811f70e08906cc82140d7
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 486, prev=2d938089824f247d96b7da37e62d5e7bc9c9b5149dfcf7741cedbc2e2fa33c95
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 487, prev=f2fb6925ab495c0c260432ee229d18d933d9576ee44812a6a2e87e1bc95b4026
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 488, prev=42eeeb35c02962ed2d5a777c7bbbdd2f515ff2affe225759278dda4f37daaa56
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 489, prev=e1ba2e7300bdb1ead27e7bd269c80e3fce3068733af3639e845a13c1a3eac80f
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 490, prev=76faf8053c36e1fbdf74218163d26f2fa42a50ce8da213849035c2fa343f44ce
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 491, prev=e002dc5c8646ba40de34602fdb01e3d5905cf080025cf5909b26e923ff464276
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 492, prev=0a461b59a20c100ae2f7844639881ed9aed0c44d00744438e0ffbd6007cef2bf
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 493, prev=b333dc30e63ea05b26e325bb46797320ea637a3cb3cdc37c423da2de9270de1f
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 494, prev=737d352a7aaf52bb5f07b325d0faeda325e5212ee93a088df9351094f2da583f
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 495, prev=f30de0dfbf9d8bf392cf899c36c4af12720af38218f1fcfa5257a79e2091bd3b
2015-11-27 06:16:28 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 496, prev=d2f8cbcf445d80cc7467f3fecbe3d412957c59a30fd87a810d4a208b4154e573
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 497, prev=8d3c2c5c08b50cace1c83e9410965804897df344004a4da8eb6331d7223397e3
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 498, prev=034955564faa6d1833d6d8098aa9a4d90677f6a19d5c6fb4d6c0343de59699f6
2015-11-27 06:16:28 ProcessBlock: ORPHAN BLOCK 499, prev=93fa794939985ff63a798fe19d50beed8027ed3ae511dbc860d4d2ad1845365e
2015-11-27 06:16:29 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:29 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:29 connect() to 45.79.10.59:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:30 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:31 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:32 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:34 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:16:34 ProcessBlock: ORPHAN BLOCK 500, prev=c1e2073a2a133f85d20dd1c41b45317df85a2d183699f25766912860b68d9b2e
2015-11-27 06:16:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
...
2015-11-27 06:18:35 connect() to 69.164.198.161:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:35 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 66.228.56.115:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:36 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 104.200.17.141:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:37 connect() to 45.79.149.192:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 120.86.52.18:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 104.237.137.28:12025 failed after select(): Connection refused (111)
2015-11-27 06:18:38 connect() to 45.33.7.79:12025 failed after select(): Connection refused (111)
Any idea why this might be happening? I synced with no problems a few days ago on the last Digibyte version. |
|
|
|
Anyone else having problems syncing. I am constantly getting stuck after 4 blocks:
"version" : 4000000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 4,
"timeoffset" : 0,
"connections" : 8,
Been like that overnight, I deleted everything and started again and it is stuck again.
Alternately anyone have some good current nodes?
Thanks
This is the first we have heard of this issue. All the server upgrades we made (20 some wallets) worked without a problem. If you have continued issues let us know. Issues continue. Can you please provide a list of up to date nodes? |
|
|
|
Is there a pool for this coin?
No Sir. PoW (Proof of Work) ended and BitBean is now pure PoS (Proof of Sprout). To begin Sprouting after you have sent at least 1,000 BitBeans and after you encrypt your Vault for the first time, you should select "Unlock Vault" from the Settings Menu or new Context Menu (RMB click a blank area of space in the new Wallet.) BitBeans mature after about 6 hours, they will compete on the network with other Beans that have matured. Source is getting cleaned in preparation for Java migration, so PoW code will be removed from source in v1.2 Best Regards, Shawn Kent (aka BitBeaner) Project Manager & Lead Developer www.bitbean.orgWe have a POS pool running for Bitbean at https://www.coinwallet.co |
|
|
|
|
Anyone else having problems syncing. I am constantly getting stuck after 4 blocks:
"version" : 4000000,
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 4,
"timeoffset" : 0,
"connections" : 8,
Been like that overnight, I deleted everything and started again and it is stuck again.
Alternately anyone have some good current nodes?
Thanks
|
|
|
|
Hello community. We are working on creating more ways for you to earn XQN coins, and we are in contact with steakcloud.com, https://twitter.com/steakcloudThis is a multipool for miners, and we are looking to get XQN added as a supported coin, and as payout option. We will also donate a amount for steakcloud to stake, and distribute the stake amongst the miners. To be added, we must show that this is something our community wants, and tweet them asking to add us. Cooperating with a multipool could increase our community. IW Also, just wanted to remind people we have a Quotient POS pool at https://www.coinwallet.co. |
|
|
|
 Diamond has now been added the CoinWallet.co online wallet service and POS Pool.https://www.coinwallet.coRunning since Nov 2013. Coinwallet.co serves as an easy to use and accessible wallet that you can access with just an internet connection. Handy to aggregate your mining income or have a small amount of coins accessible when you don't have access to your main wallet. Free deposits. 0.5% fee on withdrawals. POS pool active on all deposits after minimum stake age. As always use online wallets with caution and store the majority of your coins in cold storage or a secure / encrypted wallet on your own computer. |
|
|
|
|
Any actual development still happening on this coin?
Seems very quiet here..
|
|
|
|
My client wont sync anymore, tried fresh installs everything, it wont do it, what can be the problem?
Try adding these nodes: addnode=144.76.185.69 addnode=91.232.105.11 addnode=2a01:4f8:151:6347::2 addnode=176.9.113.75 addnode=45.79.151.194 addnode=88.198.207.8 addnode=168.235.150.242 addnode=109.236.85.42 addnode=192.241.224.61 addnode=162.243.198.51 addnode=192.99.32.187 addnode=74.207.230.61 addnode=104.236.69.34 addnode=2600:3c02::f03c:91ff:fe6e:e806 addnode=159.203.117.103 addnode=203.45.89.214 addnode=199.233.246.224 addnode=5.189.139.227 addnode=23.117.142.67 addnode=86.188.104.174 addnode=75.136.69.71 addnode=93.33.144.9 addnode=109.182.159.47 addnode=151.80.33.164 addnode=86.191.255.223 addnode=52.5.155.203 addnode=99.237.87.158 addnode=213.107.69.133 addnode=91.73.255.52 addnode=2602:306:c5b4:a190:1d42:b1e5:8ad3:adcd addnode=78.62.83.197 addnode=2605:f700:80:800::4958:58fc addnode=2605:e000:a901:be00:ac5a:6691:f0a6:d3d7 addnode=89.164.59.191 addnode=2606:a000:8880:e900:9066:ff21:6cb8:b507 addnode=65.182.72.222 addnode=107.170.174.86 addnode=72.10.216.141 addnode=98.238.201.128 addnode=2003:89:ee36:587:6d14:c7da:ef2e:5695 addnode=188.218.135.19 addnode=91.230.202.187 addnode=31.223.129.19 addnode=125.212.124.117 addnode=188.68.49.137 addnode=185.37.86.95 addnode=141.135.135.208 |
|
|
|
|
Show Posts
