I wasn't talking about the idea. I was talking about my implementation (the code). But yeah, you can use it if you want.  Ok thanks. I would pay 8 XMR for a script that setup a cryptonote pool for private use.
Every pool I've used has gone down multiple times, but making my own pool for Monero has been troublesome, working on it for weeks now.
Why would you make a private pool for yourself ? Just solo mine on the same address. Maybe it is because you can't solomine with the claymore gpu miner. You need a pool for the mandatory dev fee. But I am sure there are some private pool. The advantage of being private is a better chance to avoid DDOS attacks... |
|
|
|
On monero thread, they said that cpu hashrate is far better in Linux. You should compare cpu mining on Linux with gpu mining on windows. |
|
|
|
Elsewhere they say the difference in speed is 2.2 to 5 times as fast. That is far, far less then an order of magnitude.
CZ decided to launch a testnet, with links to the github weeks before the coin launched. While it seemed like a good idea at the time, to test his coin .. what he actually did was open it wide for people to prey on. I find it not only probable, but instead extremely likely, that there were GPU miners either at launch or within the week after it. His unfamiliarity with the typical nature of this board left his coin extremely vulnerable and he is now left to contemplate a hard fork to stop the abuse. Please note that with this abuse he might not even have the ability to enforce a hardfork due to potential miner take over. Here is what I'm talking about, and this is half of the daily emission. Thus, 50% of mining is done by his software.It does not matter if it's 2.2 to 5 times as fast, the time in which his coin has been exploited vs the time it has not been exploited is very large. Unfortunately, Claymore or another developer did not provide a GPU miner to act as a crutch until such time when an open source one was ready. Fortunately, with the slower emission .. this has a chance to even out over time. I hope the best for him, but I do not believe he grasps the full nature of variables involved in what he's doing .. this is not knocking his ability to program. Hmm, good points. However, he could enforce a hardfork even with a more powerful miner out there, as hardforking only requires that the people using the coin update their software. If for example the dev says, "This is the new version" a rogue miner doesn't need to accept it, true, but if all the services and majority of users stick with the 'official' chain, then the rogue miner would solving blocks that no one else accepts. That sounds like a recipe for chaos, with some users on one chain and other users on the other. It is impossible to get all users to upgrade anything, it just doesn't happen. For such a young coin, hardfork should be possible : the dev needs to coordinate the fork with the exchanges and the pools. That's the point. The pools are controlled by the miners. They won't fork against their interests. He'd probably have to relaunch a new coin to do this. There are only two miners concerned (Christian & Christian dev of ccminer which have developped a private miner and will probably incorporate in ccminer later): they do not operate from official pool... |
|
|
|
Claymore are you using VMPROTECT on the EXE files?
If so that could/would explain a lot of the problems people are having. It has some problems when dealing directly with hardware.
iam pretty sure it does..... use vmprotect If so it would explain a lot of the memory errors and loosing touch with the hardware. Yes I use vmprotect. Do you know a lot about it to state that it's the reason of problems with GPUs? If so, let me know more details, I will be glad to check it. I always test both original and vmprotect versions on my systems and I never saw any differences for several months in different miners and other software I created. For CryptoNote miner, for example, both versions don't work until I set pagefile 16GB. If you have problems with vmprotect - miner will not start on your system at all because it does its job at starting only. If you see at least one line in console after starting - everything works properly. The problem is in AMD drivers, they don't want to work with large memory sizes. Drivers just don't allow OpenCL app to allocate a lot of GPU memory at once. For example, 290X card has 4GB but OpenCL gives me less than 1GB at once by default. GPU_MAX_ALLOC_PERCENT variable is a solution (I can assign up to 3GB), but buggy solution as you can see. And AMD found a solution - today I tried Catalyst 14.6 and even with GPU_MAX_ALLOC_PERCENT I cannot allocate more than 1GB at once now. So they solved the problem  I have a couple of ideas about possible workaround, I hope it will help, new version will be available soon. Anyway, working with AMD OpenCL is some kind of magic which is much more unstable than vmprotect. Maybe this can help : http://devgurus.amd.com/thread/159516 : "
Hi vanja_z, welcome to the forum,
Currently OpenCL users are limited to 25% of device memory,
I don't know where you get this from, perhaps it's a rumor, but it's certainly not correct.
(there is a 512MB limit per allocation call but you can allocate as much as you like)
I do predominately scientific computing and often need very large and fast memory so I am mostly using the 7970. On the 7970, I often allocate a single contiguous buffer that uses just shy of 3GB, the device limit. It's very simple, all you do is allocate in chunks of 512MB or less and make sure the chunks are rounded to about 0x4000 bytes, then they will be placed contiguously. Example, allocating 2GB you might have kernel buffers like
__kernel(global float *A, global float *B, global float *C, global float *D){}
Since this is C language and A,B,C,D are memory pointers, you can use A to reference all of memory.
Here is a printout from a typical program start:
open:devices 3 gpus, 1 cpu, device(0) = Tahiti
start(cl):ndevs=3 gpus=1 time=57.136
<readback of actual allocation map>
buffer 0 start 01D1E000 to 21D1E000 size=20000000 Gap = 00000
buffer 1 start 21D1E000 to 41D1E000 size=20000000 Gap = 00000
buffer 2 start 41D1E000 to 61D1E000 size=20000000 Gap = 00000
buffer 3 start 61D1E000 to 81D1E000 size=20000000 Gap = 00000
buffer 4 start 81D1E000 to A1D1E000 size=20000000 Gap = 00000
buffer 5 start A1D1E000 to B0E1E000 size=0F100000 Gap = 00000
buffer 6 start B0E1E000 to BF21E000 size=0E400000 Gap = 00000
buffer 7 start BF21E000 to BFE1E000 size=00C00000 Gap = ---- (last address on GPU is BFFFFFFC)
The last couple of buffers are different size for an unrelated reason. Note, I have not used GPU_MAX_ALLOC
type parameters and have never seen a need to. This also works on Cayman, and Barts devices but I prefer
Tahiti because the memory is so large and fast. Sorry, I don't know much about Nvida devices because I
usually choose hardware based on specifications.
Hope it helps." |
|
|
|
Elsewhere they say the difference in speed is 2.2 to 5 times as fast. That is far, far less then an order of magnitude.
CZ decided to launch a testnet, with links to the github weeks before the coin launched. While it seemed like a good idea at the time, to test his coin .. what he actually did was open it wide for people to prey on. I find it not only probable, but instead extremely likely, that there were GPU miners either at launch or within the week after it. His unfamiliarity with the typical nature of this board left his coin extremely vulnerable and he is now left to contemplate a hard fork to stop the abuse. Please note that with this abuse he might not even have the ability to enforce a hardfork due to potential miner take over. Here is what I'm talking about, and this is half of the daily emission. Thus, 50% of mining is done by his software.It does not matter if it's 2.2 to 5 times as fast, the time in which his coin has been exploited vs the time it has not been exploited is very large. Unfortunately, Claymore or another developer did not provide a GPU miner to act as a crutch until such time when an open source one was ready. Fortunately, with the slower emission .. this has a chance to even out over time. I hope the best for him, but I do not believe he grasps the full nature of variables involved in what he's doing .. this is not knocking his ability to program. Hmm, good points. However, he could enforce a hardfork even with a more powerful miner out there, as hardforking only requires that the people using the coin update their software. If for example the dev says, "This is the new version" a rogue miner doesn't need to accept it, true, but if all the services and majority of users stick with the 'official' chain, then the rogue miner would solving blocks that no one else accepts. That sounds like a recipe for chaos, with some users on one chain and other users on the other. It is impossible to get all users to upgrade anything, it just doesn't happen. For such a young coin, hardfork should be possible : the dev needs to coordinate the fork with the exchanges and the pools. |
|
|
|
|
Hello,
I have switch to the command line wallet (after gui wallet, since you were suggesting this was part of the problem) and I think there are about 5 xmr unpaid on your side.
My address : 43B1yuNxZSnHYXJSZFM2GxewTUW3rnzrhJbua8M1C4otZ1k6UxeSKzE9xu8UqfBf9bXfqW8Cya2ivAb awapoDRpaJKcCcEn
Could you have a look please?
|
|
|
|
Caution advised: No payouts from http://monero.crypto-pool.fr/ in the last 14hr+.The pool shows my Total Paid at over 2XMR, but nothing has been received. My wallet is synced and operating fine and I've never had issues with payouts from other pools before. I contacted the pool admin, and he doesn't seem to know what's going on (claiming payouts are fine when they are not, and asking me if I am out of sync). It's certainly not a problem on my end, because others confirm not receiving payment (at least 2 other miners in IRC). I would suggest being careful on crypto-pool.fr until the pool admin provides an update. Yep, having same problem. Started mining there about 14 hours ago and haven't received any payments yet. Interestingly, I am also having problems receiving a poloniex withdrawal, the transaction status is confimed finished and it gives me a transaction hash, but that does not exist on the blockchain - about 5 hours have passed now and still nothing in my wallet or on the blockchain. Very weird. Edit: Does anyone have recommendations on an alternate GPU pool? The admin (superesistant in this forum) said he was changing his payout system due to the "dust" problem discussed here previously. I think the new payout system doesn't work properly yet. See https://bitcointalk.org/index.php?topic=613072.180The owner is active in this thread and member of this forum since may 2013, active for monero promotion. This is not a scam. But I agree : there is payment problem (I am waiting about 7 xmr). |
|
|
|
MAX_MONEY is pretty much what it sounds like. This means that the actual maximum supply of SuperCoin is 150 million, not 50 million. Furthermore, the maximum PoW coins is 50 million, rather than the claimed 18.2 million. The 150 million number appears twice in the code, so it can hardly be considered an accident.
That's retarded. How the fuck are you able to run an exchange, if you can't even figure out the basics? MAX_MONEY doesn't indicate maximum supply, it's a check value for transaction validity. In the asiacoin hidden premine, I believe these constants were used to trick the blockchain explorer et the wallet code which give the total number of coins. |
|
|
|
I see same thing on 290, and clock is stable on 280X. Some algos don't use memory heavily so driver reduces mem clock, it must not cause less mining speed if driver knows what it's doing. The questions is why it reduces clock for 290 only.
Because the power saving features on R9 290 are more advanced than in previous generation : the gpu and mem frequency are fastly adapted to the present charge. For X11 mining (before recent optimizations), I obtained some minor performance increase with disabling this power management behaviour : in MSI afterburner, using unofficial overclocking with disabling powerplay : this forces always max clock. |
|
|
|
Here, I am done - I think this makes sense.
Read this while reviewing the flow chaeplin posted:
The transactions sent from the mixer (C) to the end address is of a set size (his example was 10). This is D.
He can then search the blockchain for possible candidates (value 10) via a script. Which gets us to block 28531 - this matches the 10.00 XC value. This can be linked at blocked 28533 with the mixer C - we already know C (output 9.99999).
This allows him to trace back to 28531 in the blockchain - to find the values that == 10.00 and match to a specific address - in this case: XQdBjeQtH1JGrkd2MWcXbtsRVeKHWZbnqa which is B.
You can then take all the transactions for this address B - review them and find two matching amounts that == 10 which belong to one single address. This address is A. Since this address B has never been used before this transaction - this is easy to do - and - even if it had multiple transactions - they would not all related back to one single point with one single value (10).
Thanks, this seems a clear explanation. To prevent this kind of tracking, the solution could be multiple node used for one transaction. Is this the multipath revision announced by the dev? What is DRK solution to prevent this kind of analysis? |
|
|
|
Can the fucking retarded hacker stop DDOS the pool ??
What's the point of doing that ? Are you 12 ?
Your pool is a good one and attracts many miners (including me : thanks for your good work) : I suppose someone is happy reducing global hashrate to improve his personnal gains ... It happened for every successful coins. I hope you will find some way to make your pool ddos "super" resistant. |
|
|
|
I sent 9 XC by sendfrommixer command to another address, but only 2 XC sent out, the rest are still in my wallet, why?
I believe there is a limit to the amount right now, since the mixer is still in beta state (to prevent significant loss). |
|
|
|
It's not a fighting amongst mintcoin holders. Just community stating their opinion. First of all whatever the reasons, I don't believe a hard fork will benefit the coin. The coin's parameters are good enough (even if not perfect), and for some minor modifications, it won't be worth to risk a hard fork. Remember what happened after removing POW (1.6->1.7 transition), for weeks we had to remind people to switch to new version. MINT's parameters are what makes MINT itself. I don't also think devs should disclose everything such as the expected "big news" announcement, it may be hidden for some reasons, and I expect it to be good when it can be announced. But; the problem lies with keeping the premine intransparent and devs not being active enough (I don't mean bugfixes here). For the devs; they are active and react instantly when there's anything critical going on, I'll give them that. But unless anything critical happens, we don't hear anything from them. This sometimes sounds as if they're nonexistant and abandoned the coin. The premine transparency is another problem. I don't care if the devs are keeping it for the community, got some of it for themselves, got it stolen, or anything, I really don't care. What I care is transparency. I don't need to know exact numbers either, the community will be satisfied with answers like "around 100M is spent on bounties, around 100M's keys are lost in some data loss, we reserve this many coins for our personal payment; but you can find remaining 450-500M in these addresses in blockchain explorer and all of these coins are reserved for use at least after 1 year: link of blockchain explorer". That's all needed to resolve transparency. Exact book keeping is not required in any way. Communication is. But devs staying mute on these issues is exaggerating the problems. For bugfixes, problems with wallet: I don't think it's the devs job to fix everything and release things. If you can help, and want to help, just fork the coin code on github with your user account ( https://github.com/mintcoinproject/mintcoin ), fix the issue which bothers you, and send a pull request to the devs. Devs merge those sooner or later, and it'll be ready in next release. As long as something doesn't require a hard fork, it's the community's job -- otherwise it just becomes one man's coin. I won't blame the devs for not fixing problems, but for transparency and activity (in the sense of keeping us informed of what's going on, if anything's going on, etc), it's on devs' hands, and that's what causes the issues with the community. +1 With all the recent problems of premine with various coins, there is an increasing need of transparency : as you said, at least some estimate on main spendings, and some adresses to follow the premine major movements. I think this is the new standard expected by the altercoin community now. |
|
|
|
If Mintcoin added anonymity and a hidden message system, do you think this will help or is it just too gimmicky? I would really love to see more investors go in with Mintcoin and push the price upwards and onwards.
Can someone please explain to me how having a Mint address lets me identify someone? I'm serious, genuinely curious. Having an adress does not expose you in any way, however, if you know that an adress belongs to a specific person, you can easily track every payment to and from that person via the blockchain. As someone has already stated; it's basically like leaving your checkbook open to the public - for anyone to read. For regular purchases, like buying a cup of coffe or purchasing a funny hat for your dog, no one will give a shit. It comes down to how Mintcoin should be adopted and used. To the average Joe, Darkcoin probably sounds like scary shit, used for money laundering and buying drugs and weapons. I'm not certain that I support Mint becoming anonymous. The big problem we've got now is that Mint has no value backing it up. Just take a look at Karma. I think IF Mint should "copy" any other coin, the PoC-model from Karmashares would be the way to go. It basically means setting up an LLC, where anyone can become a stakeholder in the company. It would reduce the amount of coins in circulation and possibly bring up the value of the coin -depening of the success of the company and it's projects. This however, requires dedication and a lot of support from the community and the developers. I know there are lots of dedicated people out there who could make this happen. This may be the perfect opportunity for making use of the premine. As some have said it on VTC thread, this is more a question of privacy than anonymity : some people may prefer that their whole transactions won't be opened to everyone ... this is understandable... |
|
|
|
As you guys can see we had a great head-start but some of the coins are catching up, and they're heavily advertising for it (they will get more votes, no doubt). 1st UTC Ultracoin 69 [18%] 2nd AC Asiacoin 59 [16%]3rd MYR MyriadCoin 50 [13%] 4th FLT FlutterCoin 48 [13%] 5th GRS Groestlcoin 40 [11%] 5th CINNI CinniCoin 40 [11%] So if you haven't done so, AC needs you right now: CoinPayments.net Vote NOW!http://www.coinpayments.net/vote
What you need to do:
1. Go to the website.
2. Choose AsiaCoin and click Submit.
3. Fill out the form to get your own BTC deposit address.
4. Send 0.001 BTC - or equivalent in LTC/Doge - to that address (make sure to add a transaction fee to ensure it arrives within 4 hours!)
5. Confirm your email (click on the link sent to your email). They will send the confirmation email after your BTC transaction gets 6 confirmations. If you don't do this, your vote won't get confirmed.
Done! Please read my other post about CoinPayments to know why this is very important for AsiaCoin.
Don't forget to click on the link in the confirmation email, which they send once your transaction is completed and after its 6 or 10 confirmations. If you don't do this, your vote won't count. + the little 0.001 btc you spent will go to a charity project (water project) : this is not like mintpal btc voting which is unfair. |
|
|
|
What address is the Premine in? I want to check
extract from the first post : The address for first maildrop is mWuwabhbmNHyYNLbQ8pzYfnFymHm5JicXf. The address for the bounties is me4HkydLYfdH3PP2oDudqRYnpFvxuCL3K2. The rest of the reserve for the other distributions is situated in magsvXHxvJhN3i3pEoSCPGJr5VwzFVgkrF. |
|
|
|
Wallet not syncing.
Where do I find the latest nodes?
Try first just to close wallet and reopen, usually helps Tried that. Not helping this time. I have had to delete everything in appdata\Roaming\Blackcoin EXCEPT wallet.dat to get the syncing working. This will take time though as the whole blockchain needs to be downloaded. Backup wallet.dat and proceed with caution and with own consideration Same here ... Trying this. Thanks. Seems like it's working. Hello, I have found the culprit for me : the antivirus bitdefender keeps deleting blk0001.dat declaring it as a threat. For anyone having this kind of problem, look at the antivirus log. |
|
|
|
Hello,
I have a synchronisation problem with my wallet (windows 7) : the synchornisation stopped at a certain block. I tried to delete everything in my AppData\Roaming\BlackCoin directory (except wallet.dat) : same problem.
I tried with a previously saved wallet.dat : same problem.
could someone help me please?
Below an extract of debug.log :
received block 7b77d1bc1f5813ebad91
ProcessBlock: ORPHAN BLOCK, prev=96c127be23c233132c43
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(f24278724d, 2), 1400880380) for orphan block 7b77d1bc1f5813ebad91a3b4ec6ecb53592328d74255cc3306aca892416a4eb1
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
received block 7c8e1f98fa4d40094434
ProcessBlock: ORPHAN BLOCK, prev=ff9f0459d26398f17d8f
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
I had the same issue yesterday after a power outage. Download the latest qt (even if your on the latest release), and replace your existing wallet. Delete everything but your wallet.dat from AppData and try again. I was sweating bullets when this happened to me, however fixing it was pretty easy. Good luck! Thanks, I forced a check on the filesystem and redowload the new wallet : I will see tomorrow if the sync process worked. |
|
|
|
|
Hello,
I have a synchronisation problem with my wallet (windows 7) : the synchornisation stopped at a certain block. I tried to delete everything in my AppData\Roaming\BlackCoin directory (except wallet.dat) : same problem.
I tried with a previously saved wallet.dat : same problem.
could someone help me please?
Below an extract of debug.log :
received block 7b77d1bc1f5813ebad91
ProcessBlock: ORPHAN BLOCK, prev=96c127be23c233132c43
ERROR: ProcessBlock() : duplicate proof-of-stake (COutPoint(f24278724d, 2), 1400880380) for orphan block 7b77d1bc1f5813ebad91a3b4ec6ecb53592328d74255cc3306aca892416a4eb1
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
received block 7c8e1f98fa4d40094434
ProcessBlock: ORPHAN BLOCK, prev=ff9f0459d26398f17d8f
ProcessSyncCheckpoint: pending for sync-checkpoint 9503e0779197ad5a77e85ae0af6e3d1bbad318d6d36e8fff67f5f7e9d658a93a
|
|
|
|
anyone knows whats happening to vtc? why price dropped badly?  u getting out of a P&D + Btc rises = VTC downtrend See 1 month Graph at crabtsy lol crabtsy There is also the big drk rise which make many to sold others altcoins to buy dark, a plausible candidate to replace ltc at the 2nd place. |
|
|
|
|
Show Posts
