 Show Posts
|
|
Pages: « 1 [2] 3 4 5 »
|
insane price action on polo , over 9k sato atm
Looks like someone is messing around since poloniex has the old wallet. ( I assume new addresses start with N). This has been quite common on yobit when on coins with wallets under maintenance. If you have NAV on poloniex, it would be a good time to sell there for BTC and buy on bittrex... |
|
|
|
Hi all, I am having trouble syncing my wallet.
Any advice would be appreciated, go easy on me as I'm a noob ☺
If your in windows wallet go in debug menu and clixl the reindex button. If Linux u need to run ./darknetd --reindex It probably would be good to check if there are peers connected first and try adding nodes if necessary. In either case, I would take a quick look at the debug logs before restarting. |
|
|
|
Any update from yobit for deposit or WD process??
It's hopeless. My ticket not even looked at I think yoshit is never going to fix their TEKcoin wallet, or respond to a support ticket even so yeah... I think they just let them pile up and answer them when it is fixed. I had a transaction for another altcoin that was stuck due to a non-working wallet and made two tickets. After a couple weeks, perhaps something timed out and the funds were back in my account. After the wallet was fixed, perhaps a month after the first ticket, both tickets were answered with the same copy-paste that probably went to others complaining about the same thing. I suppose the TEK problem is a bit more complicated as there have been transactions made to the wrong fork, so they would need figure out which transactions to reverse. I don't have much TEK in yobit limbo but I hope it will reappear soon. |
|
|
|
darknet-cli masternodelist full |grep ENABLED|wc -l
792 Masternode cashout? Was almost 900 recently. (2 days ago maybe) It could be a VPS hosting issue as some of mine suddenly went missing/expired today for no reason. Edit1: It's definitely a VPS hosting issue. Seems some of their servers went down unexpectedly. Edit2: I got them back online now.  Yep. saw the post in the DNET hoster's thread. 718 now. I thought for a moment that it could also be something up with the masternode upgrade. If you don't run many nodes, it could be good to wait a bit and not to be the first one to update. Now 720. |
|
|
|
Good time to buy! |
|
|
|
|
I am so going to buy this!
|
|
|
|
Maybe my re-enroll was missed? Anyway, I'd like to to Enroll again^2 Thank you, re-enroll
Lyddite
|
|
|
|
thank you Noise23!!Mandatory update hardfork incoming use version 2.4.0.0 Any indication of when will be the cut-off date for the old wallet? april 6th HardFork Technical Details, please! Thanks! Please post a change log ! I agree... I had a quick look at git. In my opinion, polling random servers that aren't part of the TEKcoin network is something the one should explicitly need to enable. It would be nice if the list of servers was in a configuration file instead. The collected data could be used to learn more about the behavior of the network. ( not just TEKcoins p2p network). It would also be interesting to provide an incentive to nodes to provide and share accurate data to those interested. |
|
|
|
|
Thank you, re-enroll
Lyddite
|
|
|
|
|
Haha, block chain synced quickly!
|
|
|
|
Nice pool! Thanks! With the current difficulty, solo mining is not really attractive for me. Any pointers to the for or SPHminer that some are using? I wonder if something needs to be restarted though. The last mined block has been showing up as "New" for quite a while now. decred (decred) 0 DCR 256.392 k 7 653 5h ago New |
|
|
|
Happy DRK accident anniversary!
Oh, I remember it well. I was pretty pissed...I was looking over old posts the other night (I'd been off the forum for quite a while until recently) and saw that and chuckled to myself.  Just remembered to add this to my own list of coins lost on exchanges... Vircurex: BTC, LTC - Frozen Crypsty: (DASH and BTC) - Wallets in Maintenance C-CEX: DRK (DASH) - Apparently status will be updated after refunding some BTC that were lost. Previously, the DRK showed up in my account balance. At some point last year, the History has been "consolidated." So it is not clear what has happened. On a more positive note... Took my BTC out of banx.io yesterday. It didn't take long at all. |
|
|
|
Hey vircurex owner is still trying! I got 1LTC back out of 1,000 that was locked for a return of 0.1%! that's something at least  The announcement was last updated in January3rd, 2016. Maybe there is some hope. Update 3rd January 2016
Payout to frozen accounts this month:
3.45 BTC
101.6 LTC
151,953.9 FTC
48,937 TRC
Total balances after the amounts have been distributed
BTC: 328 accounts with frozen amounts, total 1,666 BTC
FTC: 0 accounts with frozen amounts, total 0 FTC
LTC: 2162 accounts with frozen amounts, total 124,763 LTC
TRC: 39 accounts with frozen amounts, total 78,782 TRC |
|
|
|
|
Congratulations kilowatt!!
I woke up to see the block hadn't been found yet and was considering renting some more hash for this. Then the normal morning chaos with kids kept me busy... By the time I was able to warm up some chicken nuggets for breakfast and rent a bit more hashpower the block was was found.
Renting hash for the first time in order to get my average high enough was an easy, painless and perhaps almost pleasant experience. It could be that the rented hash pays for itself in the next few blocks.
I had received some bitfury h-cards and m-boards from a friend recently. The lottery was the perfect incentive to get the stuff up and running to upgrade my modest mining / heating setup. If I don't start mining more than 300 GH/s, my rewards will surely enter the dust category that are waiting to be paid eventually. While not difficult to set up, it's clear that a full set of h-cards will need a bit better power supply than one can salvage from an old PC so it is not up to full capacity yet.
Next, month, I should have no problem beating the average with own hardware.
-Lyddite
|
|
|
|
one more thing where is the up to date windows wallet
Yeah can anyone else answer this? I just want to double-check and make sure I have the right version so I'm not staking false coins. Yes the wallet is the most recent one everyone is using. Just give your coins some time since others are battling for blocks. Also I noticed TRBO is trading on C-CEX c-cex.com/?p=trbo-btc though Cryptsy is the main go to place for acquiring them. I mentioned this a few days ago. There is a wide spread and no activity except Nov. 13-14. I noticed that cryptsy has no withdrawal fees for TRBO. At C-cex it's 0.1 (insignificant unless this coin goes to the moon). |
|
|
|
Please, it's 2015. This is 64 bit code only, but if it's working ignore the error as it's just something to do with your distribution.
Compiled on another system (32-bit too - so the bitness doesn't meter) - now works like a charm :-) Ok... this explains the problems I have had... Whether it works on a 32 bit system depends on how you use it.
I thought I would see if one of the small project boards would work as a proxy so I compiled it on an Odroid C1 (fedora). Compiled easily with only signed/unsigned warnings and connects just fine to kano.is but I get the following error when a miner finds a share and tries to submit it:
32bit processor? There's no 32 bit support in ckpool code. Understood - but I thought I saw a message earlier that someone had compiled it on a 32bit processor and it worked. I expected it wouldn't compile if that were the issue but it does and connects to kano.is with no problem. Just can't submit any shares. I'll drop the experiment. Thought a simple, cheap, power efficient proxy would be good to run vs having it on one of my servers. It would be good to have a redundant, backup proxy. I managed to compile and run using debian jessie and ./configure --without-ckdb with the intention of running it on an old laptop as a proxy and hoping to get some nice logs. Did not succeed in getting the "-p" proxy to run It would almost work but the following would appear in the logs and eventually the hashrate on the pool ( kano.is ) would drop off and it would fail to submit shares. Invalid json line:1 col:4 pos:4 text: NULL string argument from stratifier.c submit_share:2965
Attempted to send null message to generator in send_proc The passthrough proxy "-P" does work well in 32 bit. The hashrates add up and each worker shows up on the pool. I have used it for several weeks to combine the connections from miners on different machines. Failed to set json object from connector.c connector_stats:782
Invalid json line:1 col:5 pos:5 text: NULL string argument from connector.c connector_stats:784
Failed to set json object from connector.c connector_stats:787
Passthrough:{"runtime": 593} My advice to anyone ckpool/ckproxy with a 32 bit system is to experiment, test, check the logs and verify that the hashrates correspond at all ends. Difficulty adjustments can complicate the testing. It would be nice if everything worked without problems on 32 bit systems. Then again, I should probably ditch the old laptops. For the record, I'm running my small ckproxy on an old Compaq Evo N410, Pentium III, 1200MHz ca. 2003. |
|
|
|
|
