https://bitcointalksearch.org/topic/m.9991269
Im not promoting this coin.
Devs have a look at their pow . If you are able to implement something like this .would make your coin perfect.
Topic: [ANN][POW] 👾Torque👾 - decentralized node list via IPFS & ZeroNet - page 82. (Read 87266 times)
March 08, 2018, 04:51:42 AM
March 07, 2018, 11:12:40 PM
Wow, What's happening. The network hashrate has reached 19 MH/s. But we do not have an idea who is behind these hashes. It could mean the price will jump or just vice verse. Let's see........ The mystery will be opened up.
Up now March 07, 2018, 10:20:35 PM
Wow, What's happening. The network hashrate has reached 19 MH/s. But we do not have an idea who is behind these hashes. It could mean the price will jump or just vice verse. Let's see........ The mystery will be opened up.
March 07, 2018, 09:37:03 PM
Network hash is about 12 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.58 MH/s for cryptoknight pool.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
This is a good example of NiceHash use. When you are renting a few mega-hashes, which will make up more than half of the network hash rate, you are guaranteed to be mining almost every block. If you're going to be the reason for mining almost every block then it would be more than logical to either solo mine or set up a private pool as more coins will be earned.Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
ok, Dev, thanks. Is the algo particularly suitable or designed for nicehash extraction as someone noticed the difficult changing?
Please vote for this coin today!. I give a support for its IPFS and ZeroNet!
I see 3 pools which found all unconfirmed blocks(18 unconfirmed blocks +1 Maturity 0 ).
https://communitypool.stellite.cash/#/blocks (hash rate: 248.64 KH/s) - 8 unconfirmed blocks + 1 (Maturiy 0)
http://cryptoknight.cc/stellite/#pool_blocks (hash rate: 504.20 KH/s) - 8 unconfirmed blocks
https://stl.dreampool.info/#pool_blocks (hash rate: 59.35 KH/s) - 2 unconfirmed blocks
Therefore, Mysterious ~16 MH/s - 0 unconfirmed block
Whole network hashrate is 17.30 MH/s. Difficulty: 1111381158
How can you explain this situation? (I have suspected botnet for the Big network hashrate, but it was not real big network hashrate.)
March 07, 2018, 05:39:01 PM
Hello all,
we've just launched a new Europe-based Mining Pool for Stellite ! Please if you can support !
http://stellite.cryptonight-pool.eu
https://imgur.com/a/5h3kN
Thank you in advance!
Happy mining !
we've just launched a new Europe-based Mining Pool for Stellite ! Please if you can support !
http://stellite.cryptonight-pool.eu
https://imgur.com/a/5h3kN
Thank you in advance!
Happy mining !
March 07, 2018, 11:36:56 AM
is there a delay in transactions atm been pending a while now
March 07, 2018, 11:22:44 AM
I would propose a difficulty algorithm that depends not only on past block times, but on the current time since last block. With an exponential decay kicking in when the block time passes the target block time (or 2x block time, etc - could be parameterized or a function of some previous blocks like a 200 element moving average), it would not matter if a ton of hash power was previously involved in the preceding blocks, block time would quickly conform closer and closer to the target time.
This would avoid situations where, after a large hash created a high difficulty, then that hash power were removed, where it might take hours to find the next block. You could have a fast acting difficulty measure to increase difficulty during high hash rates, and a fast acting fall off of difficulty when they leave, without a long block time on the first block found after the loss of that hash power.
However, some research would need to be done to see how easily this approach would be gamed by someone intermittently throwing large amount of hash power at the network. I suspect that this would not be such a bad thing, but some scenarios would be worth investigating.
This would avoid situations where, after a large hash created a high difficulty, then that hash power were removed, where it might take hours to find the next block. You could have a fast acting difficulty measure to increase difficulty during high hash rates, and a fast acting fall off of difficulty when they leave, without a long block time on the first block found after the loss of that hash power.
However, some research would need to be done to see how easily this approach would be gamed by someone intermittently throwing large amount of hash power at the network. I suspect that this would not be such a bad thing, but some scenarios would be worth investigating.
March 07, 2018, 06:54:21 AM
Network hash is about 12 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.58 MH/s for cryptoknight pool.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
This is a good example of NiceHash use. When you are renting a few mega-hashes, which will make up more than half of the network hash rate, you are guaranteed to be mining almost every block. If you're going to be the reason for mining almost every block then it would be more than logical to either solo mine or set up a private pool as more coins will be earned.Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
ok, Dev, thanks. Is the algo particularly suitable or designed for nicehash extraction as someone noticed the difficult changing?
Please vote for this coin today!. I give a support for its IPFS and ZeroNet!
Excellent. This is a very good sign. Devs are listening to the community and taking actions. Good luck for this coin.
March 07, 2018, 06:14:13 AM
Network hash is about 12 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.58 MH/s for cryptoknight pool.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
This is a good example of NiceHash use. When you are renting a few mega-hashes, which will make up more than half of the network hash rate, you are guaranteed to be mining almost every block. If you're going to be the reason for mining almost every block then it would be more than logical to either solo mine or set up a private pool as more coins will be earned.Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
ok, Dev, thanks. Is the algo particularly suitable or designed for nicehash extraction as someone noticed the difficult changing?
Please vote for this coin today!. I give a support for its IPFS and ZeroNet!
March 07, 2018, 05:56:37 AM
Padarobin by my theory we are going neither up or down , people are just going away. already one customer check comments 
., DEVs is someone trying to time warp ?
Think these are still early days. Those moving away are the greedy ones that are only after quick buck. ., DEVs is someone trying to time warp ? March 07, 2018, 04:14:08 AM
We where 1ste place yesterday so keep on voting lets get back that number 1 position.
March 07, 2018, 04:08:25 AM
March 07, 2018, 03:39:35 AM
FUCKING NICEHASH BLOCKING everywhere!!!!
March 07, 2018, 03:31:17 AM
Network hash is about 11 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.5 MH/s for cryptoknight pool. The nicehash has been staying here for quite some time. A lot of money to spend on hiring nichhash? Is it profitable currently? Maybe, this guy bets this coin bright future.
March 07, 2018, 03:10:28 AM
Network hash is about 12 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.58 MH/s for cryptoknight pool.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
This is a good example of NiceHash use. When you are renting a few mega-hashes, which will make up more than half of the network hash rate, you are guaranteed to be mining almost every block. If you're going to be the reason for mining almost every block then it would be more than logical to either solo mine or set up a private pool as more coins will be earned.Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
ok, Dev, thanks. Is the algo particularly suitable or designed for nicehash extraction as someone noticed the difficult changing?
Please vote for this coin today!. I give a support for its IPFS and ZeroNet!
March 07, 2018, 02:03:35 AM
Network hash is about 12 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.58 MH/s for cryptoknight pool.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
This is a good example of NiceHash use. When you are renting a few mega-hashes, which will make up more than half of the network hash rate, you are guaranteed to be mining almost every block. If you're going to be the reason for mining almost every block then it would be more than logical to either solo mine or set up a private pool as more coins will be earned. Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
March 07, 2018, 02:03:12 AM
Another day another time to vote.
We are now at place 2
get us back to place 1 and vote again on https://acc.vicex.io/acc/listing
We are now at place 2
get us back to place 1 and vote again on https://acc.vicex.io/acc/listing March 06, 2018, 10:48:35 PM
Network hash is about 12 MH/s , while the two major pools' hashrates are about 0.3 MH/s for community pool and about 0.58 MH/s for cryptoknight pool.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
Is this normal?. Do not tell that 12 MH/s is an averaged network hashrate.
March 06, 2018, 07:56:22 PM
http://cryptoknight.cc/stellite/
that guy is jumping from pool to pool. often he has double the net hash algo . as much i see is sequence of 12hrs. how much time thake for diff to adjust.?
that guy is jumping from pool to pool. often he has double the net hash algo . as much i see is sequence of 12hrs. how much time thake for diff to adjust.?
March 06, 2018, 06:44:20 PM
Today, the situation changes again. Just one minute ago, the whole network from the community pool has 2.0 MH/s hashrate. However, in one of the pools (another pool), it presents about 6.0 MH/s hashrate, but simultaneously its network hash rate still shows only 2.0 MH/s, yesterday, vice verse. Something must be wrong here.
Where are you checking the network hash rate? It always takes some time to update, definitely longer than the counter for the actual pool you're viewing it on. Jump to: