 Show Posts
|
|
Pages: [1] 2 »
|
Sent EMD coins to cryptsy from my wallet about 36 hours ago. No sign of them, they're just gone into the void apparently.
Cryptsy has huge delays in EMD, CGB and ELC (and maybe some more coins) last week or two... The only way is to write to their support, in most cases they,I think, manually push the transfers... Or I don't know what they do, half an hour after creating a support ticked the money is there... I'm having the same problem as you with my CGB for 2 days. Nobody knows why it happens, but writing to them will cause that they will deal with the problem. Thank you for that I was wondering.... It looks like Cryptsy has fixed the EMD deposits (albeit with a lot of nagging). My last 2 deposits turned up within 10 minutes. |
|
|
|
Soooo many rejects on this network... >50% rejects.
Either there is someone with miners purposely rejecting coins, or this is the worst block-speed ever. lol.
Is this wallets network that slow to update "new blocks". Might be why there are so many rejects. BLocks are found but the wallet is taking forever to tell the rest of the world, once one is found.
Even with a 2500ms ping (2.5sec) the blocks should be traversing the net a lot faster. Oh wait, then there is IIRC crap that adds delays. Time to copy a more updated coin with these same settings and upgrade the wallet, or double block times and reward, to compensate. (Half the daily blocks, so the block-time is 40-sec target not 20-sec which is obviously 50% longer than it takes for the blocks to propagate the network after being confirmed.)
Just saying... if you want this coin to live...
Otherwise you should all be doubling your value, since you are only making half as much as you think you are making, based on estimates from 20-sec calculations and 0%-rejects.
I've mined 70 odd blocks in the past 24 hours and haven't had one reject (I don't think I've had any rejects in all the time I've been mining EMD). What OS is your wallet running on? |
|
|
|
Yep, the difficulty retarget to 1.9 hasn't been too popular. It's Mhash rate is now lower than the diff  . |
|
|
|
|
"txid" : "222748717a046585ad1327ae095895b574d1740caa6b6264c6d22a1e599e96cc"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
I couldn't help myself. I re-started mining and got one almost straight away. Good to see it's since clicked over the 6000 mark, although difficulty of 1.9 might still pose a problem with current network hash per second.
|
|
|
|
|
There was no payment for found blocks and no word from the dev (except that he's mined a million USD-e and he's been spending his 'development' time on the USD-e thread photoshopping pictures of US government) so I removed my 2Mhash this morning. You might be waiting a little while longer for the 6000th block.
|
|
|
|
Yeah I have lost my faith in this coin.
The coin could easily be pushed so that the retarget would have been hit. The dev could have paid the bounties to keep the coin going. And The dev could speak up so we know something, or just to keep the channels alive and maybe draw some new people in. Instead, he hasn't spoken at all on the Bacon coin thread, but he is all over the USD-e thread, meaning he is here and reading the forums, but it seems he has left and is mining something else as well.
It looks like rammy may have a touch of ADD. I've just pulled my 2Mhash as well 'cause if the dev doesn't care about it why should I. It would have been nice if he'd let everyone else know but I guess he was busy amassing his 1 million USD-e's with reduced competition . |
|
|
|
|
"txid" : "518a80955a7c13fd1ffc0282edf9b1b9860aeb3b5526b429d53264137f3d2d11"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
FWIW. Here's hoping OP makes good on their promise to pay bonuses on these blocks. I don't know why you'd go to all the trouble of setting up an altcoin and not try and push it over the first hurdle by at least keeping the masses informed. It's not hard! If they'd done that I wouldn't be writing this now.
|
|
|
|
|
"txid" : "2ffa86590d9e5050b3d4345994ad7dc48339f6f7cd512f08545e84c12c415ae4"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
|
"txid" : "4bb1952f9c8270161e2cbabd68af9369d2833d1eb9ed4dd99d6351315446a0dc"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
|
"txid" : "1072f17522c800773939c1c3e907c42fc1ab1fdbe33b1d4cf2ff9faaf178847b"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
*takes a deep breath*
*furiously copy/pastes*
"txid" : "aac894c65f369a3a82dc36215e7eb5532247acac403c5cd1ec08d541049cb1d7",
"txid" : "7dd8a8a6a8a0c77a5a6ee1864d76664da1af968dadb5e625825f24fa808d7fdf",
"txid" : "2e6e00f534d44bb5dfed0b5bbc958ed5d2477b3d575e8da2d34933dde5aeb77a",
<snip>
FIFTY!!! AH AH AH AHHHH!!!
*wipes sweat off forehead*
Bloody hell! Someone's been busy. |
|
|
|
I'm not sure how to find the text ID but the pool shows I found block 5744, which has a hash of d95c7a7a212cb8297fcb3c331523ac2af911d9f0f66f9b9430afa7270661ba76
If that isn't the ID, let me know where to look for the correct one.
Thank you,
GMrMdTyvTjZ8P9xCLwFWtyPvk4q9j6TwKi
The "txid" ('tx' stands for transaction) comes from the baconbitsd listtransactions command (I just copy and past it from the terminal window). If you want to get the 'Transaction ID' in baconbits-qt, click the 'Transfat' button then right-click the transaction, select 'Show transaction details' from the list and you'll see the 'Transaction ID' at the bottom. Ah! okay, thanks. So working from the pool (my wallet is flaking a bacon bit at the moment) this appears to be the transaction ID: 2f0d890ba718c50c1f1a08e4edbf379ca4886f1ec9b36a7dbf3b4f8a1932797c Actually since the mine went poof last night...it kinda looks like this coin may be a tad moribund. Yeah, that's the Transaction ID for 5744 (although I've just noticed it's before the promo block range  ). It'll be interesting to see how this coin develops. It had a fantastic launch, which almost killed it. It's not worth everyone piling back in when the diff changes. Another spike like that and it's goodnight. However, most of the other new alts are having their own issues at the moment and there's nothing really profitable to mine even in the existing alts. It is holiday season so it'll be interesting to see what happens when everyone's back on board. |
|
|
|
"txid" : "5c8c630198ed3e1c11b0b8e39ffc495735a4f3049a363c86c709070adc2c264d" GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH Another one. Am I the only one mining this coin?  |
|
|
|
How is baconbits doing? How many ltc are 900 baconbits worth?
As there's currently around 627,300 baconbits in existence, and 24,757,750 litecoins I'd say your 900 YUM should be worth around 35520 LTC (in a perfect world, that is)  . |
|
|
|
I'm not sure how to find the text ID but the pool shows I found block 5744, which has a hash of d95c7a7a212cb8297fcb3c331523ac2af911d9f0f66f9b9430afa7270661ba76
If that isn't the ID, let me know where to look for the correct one.
Thank you,
GMrMdTyvTjZ8P9xCLwFWtyPvk4q9j6TwKi
The "txid" ('tx' stands for transaction) comes from the baconbitsd listtransactions command (I just copy and past it from the terminal window). If you want to get the 'Transaction ID' in baconbits-qt, click the 'Transfat' button then right-click the transaction, select 'Show transaction details' from the list and you'll see the 'Transaction ID' at the bottom. |
|
|
|
|
"txid" : "dbe7c0359e720279a0c4c9f8ad0f2c09518c30f20728bc0603b1e621e54888a2"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
|
"txid" : "b35228816ec0824cb48f4385b9c8a37a1ba712fc27ea654ad157cee0ee6f370d"
"txid" : "8bf0c480516110fc88bd27a1ef0b7b0137132cf4a4a8226faa6b75ff69006354"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
|
"txid" : "2f2c5d05f55a2a976afd4c045f1f43b194e7a1717e18d9a0d760a5fdef5dc833"
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
i dont understand. randomly this wallet starts synchronizing at over 400K blocks. it shows im at %1 . then it goes back to synch with 5k something block.. anyone else experiencing this?
Same here (see my post above). I'm currently at 12.5% (40456 blocks remaining). My client initially starts up as 'up to date', then after a minute or two start syncing 140k blocks, goes to 400, then back down. Hopefully the retarget fixes this - and I hope that the pools don't jump back in and stuff it up again. |
|
|
|
|
GXWVkuaiFVzQkCv3eeMF7EQEtDQvc5FnsH
|
|
|
|
|
