 Show Posts
|
|
Pages: « 1 2 [3] 4 »
|
Thank you. Now I understand it. So Slush is actually including the fees into the Block Value rather than deduct like Kano. Now you can see how people can easily be confused as there's no standardization. Ok, no more questions from me before people start screaming.
Just to clarify the block value is always 25BTC + the fees included with the transactions confirmed in that block. On Kano the value displayed is this amount - the pool fee. The slush page shows the whole block value BUT miners are not paid off this amount. Somewhere in the background on Slush the pool fee is deducted and then the remainder is divided up to the miners. Slush is a little deceptive by using the pre pool fee amount as it could be interpreted by some as the blocks on Slush are higher value. Just another example of why kano.is is the best pool out there. Transparency !!! X |
|
|
|
For testing I sent a BTC payment of 2BTC somewhere with 20block confirmation set, to see how long it would take vs the usual 5..
Never had an unconfirmed stuck before. Will it eventually 'return' or is it considered gone ??
You picked a bad day to try this. Almost every block today has been full and there has been 5000+ transactions left in the mempool. As a result anyone sending BTC has been doing so with VERY high fees. At one point i saw 15000 transactions pending with over 3 BTC worth of fees. Seems like the lower fee transactions just keep getting left behind. Eventually when the transaction backlog clears up your low priority transaction will be included in a block. X |
|
|
|
lazy math is 10,000 th is good to go. you can max at say 240 th so with a careful rental you have a 240/10000 or a 2.4% shot with a 240 th rental
Actually my understanding of the contest is it's judged off the average hash rate or the "red line" on the hash rate chart. So someone could in fact use 1000Th for 1/4 of the 5nd time and still qualify for the contest. X |
|
|
|
woow amazing luck, congrats to 1Q8VghUJkNeFnaKy553b9buUWKxFYL579G . someone who has got same hasrate can not find block lots of days.
This hashrate would expect to find 1 block in approx. 10 days. Excellent luck indeed. X |
|
|
|
It is Amazing! Can someone please explain why this address has hit the last 3 blocks for SoloCKPool? They have a high hashrate of course, but the total the pool has a total of 2PH as of right now. So the "lotto" pool has about 500th from what I understand. Now it would be amazing for the entire pool to hit 3 blocks in the amount of time the "lotto" group has hit with just 1/4 of the pool hashrate.
Why aren't any other addresses hitting? Or do they have several lotto runs going right now? And how much if I want to join 1
All of these blocks were found on the de pool. The de pool before this lotto run started was running around 300T. The lotto run was for 5 BTC run of around 500Th. This gave them the majority of the de pools hash rate for approx. 2 days. Excellent luck and they found 3 blocks in this time. Keep in mind that the different solo pools operate independently of each other so you can't use the main solo pool hashrate for calculations. X |
|
|
|
Milliseconds slower maybe, but seconds slower? Not possible.
Here is a link to see the seconds difference between the BIG pools on block notification. http://poolbench.antminer.link/#Your home bitcoind could be seeing new blocks as much to a whole minute behind the rest of the network. This results in your miners working on work from the last block during the time it takes to realize a new block has been found. This work is wasted as no new block can possibly be found on an old blocks work. You can probably see the difference between your home solo mining attempt and ck's solo pool by just watching the cgminer interface during a block change. If ckpool is your backup you will notice the announce of a new block will come from pool 1 well before your home bitcoind notices the block. X |
|
|
|
... and we have a winner  Block during CKDB restart (still restarting) Winner is indeec444 with ~85THs  Nice green block. Pretty empty thou... X |
|
|
|
 congrats to 3JhmANFUNJkBREYYfPPy8hdJ3cnrGvWKhY for the Block! {"hashrate1m": "125T", "hashrate5m": "123T", "hashrate1hr": "124T", "hashrate1d": "124T", "hashrate7d": "112T", "lastupdate": 1453146737, "workers": 112, "shares": 249386150227, "bestshare": 5858515.5556973545, "bestever": 252987485486} That's 3 in a row for this particular user. Nice returns for 125T. Congrats! X |
|
|
|
Thanks Zach i did miss that post, Kano or -ck was wondering if everything is alright with the block propagation its at an extreme today or maybe there is a glitch with the site.. Rank Pool Ave Delta From First Pool Delta minus Best
1 stratum.mining.eligius.st:3334 6.5483448217655 0
2 stratum.btcchina.com:3333 9552.8558958371 9546.3075510154
3 stratum.bw.com:3333 9925.048134625 9918.4997898032
4 nl1.ghash.io:3333 10027.742528295 10021.194183473
5 solo.antpool.com:3333 10129.075428568 10122.527083746
6 stratum.mainnet.mining.strateman.ninja:3333 10330.801666679 10324.253321857
7 solo.ckpool.org:3333 10331.125611107 10324.577266285
8 stratum.kano.is:3333 10331.63709259 10325.088747769 These stats are obviously wrong. If you scroll down you will see the eligius block stat is repeated on several block finds with the same time. This of course threw off all to calculations to follow. It seems to be working again properly now but it will take some time for the average to update. X |
|
|
|
Hi I am trying to connect to kano but no luck. Can someone verify if this correct for my S3
host : stratum+tcp://stratum81.kano.is:81
username : 1xxxxbtcaddress
Yes this is correct but why not just use: stratum.kano.is:3333 I've never had trouble connecting with these settings. X |
|
|
|
BTC Help, please. Kano sent me from the IRC Node to ask for help in solving this problem. I have recently switched from another pool to Kano's (kano.is) because I was having this problem and now it is occurring on kano.is. I am registered on the site and have put in the stratum .3333 at kano.is for my configuration. And then of course I click save and apply. However, immediately upon doing so, this screen appears.  Whenever this screen pops up I am immediately disconnected from the pool that I have (in this case kano's) put into my miner's configuration page whereas kano's URL was showing up under my status page's pool URL section. Now this Mr. Nice Hash appears. I have tried resets and reboots, disconnected the power, and shut down my miner altogether. The problem persists. I've got an s4. Please advise. Thank you. Only solution for this hack is re-imaging the SD card back to original firmware. It's fairly straightforward and easy to do. Send me a pm if you need help. X |
|
|
|
Good Morning CK,
a other thing. after the last block was found, my bestshare is already on the last high value....
it is possible to set the bestshare back to 0 if a block is found on a other solo server?
Have a great day
Willi
Your bestshare is on the DE server. It will reset back once the DE pool finds a new block. Keep in mind that the new solo pools work independently of each other. X |
|
|
|
I've just realised that I rented a EU Rig and put it on the DE server, then tried to connect my personal miners up to the US server but got Authentication failed, so I tried the DE port and it works...  Can you only have your workers running on one pool ? DE ping would be worse for my personal rigs then US ping as I am in AUS. No, they should work anywhere. This is very weird, I can connect to DE and HK servers with both of the ports but I can't connect to the US server as it says the same thing... DDoS on the US server ? Nope, all quiet as far as I can see. Check your settings as the most likely thing is a syntax issue. I've seen this error as well. Seems to be happening since the combined stats on the main pool. I believe it's caused by using the same user/worker name on both pools. Change solo to a new address and you will connect instantly. X |
|
|
|
Why don't we move everything back to the start. Call it Isotope again and wait for the next one.
I'm up for this. I've already msgd CEX about the possibility. X |
|
|
|
I have been back and forth with CEX support over this issue for the past 2 weeks. I have supplied them with the original source code as they requested and yet they still refuse to do anything. Last message I received: "Last time we had update from chips team and it was chips wallet. Not and Isotope. Please, don't reply by e-mail. Use our support section: https://c-cex.com/?id=support" There has never been a CHIPS wallet. This coin has always been a re-brand of Isotope. At this point is looks like any users with XTP on local wallets will be left out of the swap. Hopefully the dev can act quickly and do something about it or implement some way to account for local wallet users balances. X |
|
|
|
So this: Wed Dec 23 13:10:04 2015
is the date that everyone is stuck with? If the answer is yes then why don't several people just unlock their wallets?
The Isotope block chain is no longer frozen and solved some blocks again earlier today. Not sure if it was from the CEX wallet or someone else. I'm trying to create enough small inputs to keep the chain moving myself. If anyone has coin in a locked wallet please unlock your wallet so we can get the blockchain moving again. X |
|
|
|
We had to recompile wallet (server change) and found that currently there is no CHIPS wallet source available.
I already contacted Blockpoker Team and offered them free to make CHIPS to BP swap for our customers. Total balance can be proved with in/out transaction ID's so technically there will be no problems.
We only need approval/agreement from BP team and we are ready to do it without any delay.
Yuriy.
The CHIPS wallet source is available here: https://github.com/IsotopeCoin/xtpThe blockchain for this coin is frozen because it is a POS coin and the CEX wallet contains most of the coin supply. When CEX took the wallet offline for maintenance the chain stopped because there was no coin left available to stake. I have been in contact with your exchange since day 1 of maintenance mode but so far nothing has been done. There are still 2 active nodes on the Isotope(CHIPS) network. If the CEX wallet is brought back online the chain should start moving again. X |
|
|
|
Wonder how many smartchips are still left.. Would guess a lot of them have been lost over time, due to all it has been through, and that the wallet is not active anymore. It would not surprise me if if only half of the coins get swapped The isotope(Smartchips) wallet and network is still active. I am running 2 of the 3 full nodes functioning today. X |
|
|
|
|
