Topic: [ANN] Fastcoin - FST - The Fastest coin so far in the market - is launched!! - page 53. (Read 238170 times)

FASTCOIN???
My wallet is downloading the blocks. NO problem, but it goes so slowly.
Already two days i'm downloading the blocks and still 70 weeks behind.
Is this normal?

Not sure why, but the wallet seems to lock up on my pool. I have to keep going in to restart the wallet, and there are TON of pending/unconfirmed but not orphaned blocks. Going to shut down FST on diggerpool.com until this gets resolved. There has been a miner in there for a while, so I am going to send this person what I have in my personal wallet.

I could make one if people would use it... I made an SBC one as it's currently pretty much top ranking on Coinwarz http://151.80.140.87/MPOS/public/index.php?page=register

But as I said, if anyone would be interested in a pool I wouldn't mind giving it a shot

where is a good pool to mine fast that is not P2P? every pool on the list that is on the official site is crap. either the site can not be loaded or found, is a fishing site or the pool does not work at all.

What's happening is that the P2Pool network has so much hashrate that it's solving multiple's of the same blocks, causing some to orphan which in turn causes the daemon to improperly calculate the hashrate. So essentially the pool is assuming it has more hashrate because of the multiple blocks being submitting at the same time.

The difference between the client and P2Pool estimate could simply be because one is averaging more blocks than the other.

The client will use up to 300 prior blocks to calculate the network hashrate; under perfect conditions, 300 blocks is an hour. The fact that P2Pool's estimated hashrate is more erratic suggests a shorter sample period.

I don't think it's even feasible to postulate that P2Pool could somehow magically be hashing at a higher rate than the overall FST network, since it writes found blocks to the chain, just like a solo miner, or centralised pool. The blocks in the chain define the hashrate, including those found by P2Pool. If P2Pool was indeed somehow hashing "out of band" then there must be some incredible inefficiency present somewhere, which is causing it to waste hashing power.

Just went up - bouncing around 251 MH/s while P2Pool is 330MH/s

P2Pool node - http://inetrader.com:5150/static/

I SEE 272

If you look now, GetNetworkHashPS is showing 178 MH/s while P2Pool's network is reflecting 391MH/s.

I've had a quick look at GetNetworkHashPS() in rpcmining.cpp, and it seems to calculate the average hashrate based on the difference in time and work between the current block, and an earlier one (covering a reasonable period). I don't understand why blocks that p2pool found would not be included in this calculation.

These are my results from a few days ago:

http://www.xpool.ca/blocks/FST

The pool was ~250mh

I'm going to run a test for two hours and put in about 100 mh/s and count the blocks generated, found and orphaned as a little benchmark for others to based the decisions to mine or not mine when comparing this coins to others.

It's probably due to more then just that one factor, the same can happen on an MPOS based pool with a huge miner that doesn't have properly configured mining hardware. Some of these huge hitters are coming from cloud mining contracts which point their option limited hardware at whatever coin is the current most profitable.

At the same time, orphan rate's are still largely do to lack of network propagation and latency, providing your client with plenty of connections, preferably with the lowest latency will greatly improve your chances against having solved blocks go orphan.

12 seconds between blocks is just really fast, and for some, by the time they announce a solved block, a larger miner has already announced and confirmed their better block.

so - are you inferring that these mis-configured machines on the p2pool network are actually hurting everyone's ability to find blocks and/or contributing to the orhpan rates?


because my observations indicate that the orphaned blocks do come in 'spurts'

Thank you for your input, but like I said, currently, networkhashps is not reflecting the amount of hashrate that is produced by P2Pool network. Your measurements are producing graphs which gets its data from the networkhashps client response.



When these spikes occur, they produce quite a bit of DOA, either by improper miner configuration settings or an intensity level that should be reduced.

Just downloaded the new wallet as mentioned in this post.
COnnected immediately to the network and started downloaded the blocks.
Good job.
Great wallet.

I don't mean to dispute your assertions but over 2 gh/s is simply not born out by the facts.

Smarterhash.com measures network hash for FST and over 50 other scrypt coins every 30 seconds and the highest  this coin has been in the past 7 days has been 1.22 GH/s on Feb 18, 2015 at 7:55 AM UTC

This chart was produced about 2 minutes before I posted this message.

FST would be one of the most profitable coins to mine if were not for the extraordinary number of orphan blocks. But due to it's high number of orphan blocks it's about 12th on the list profitability wise daily with an optimum hash rate for profitability of about 100 to 200 MH/s - the last 24 hour average hash rate for the coin was 364.81 MH/s an if you had put 100 MH/s of mining power on the coin, THEORETICALLY it would have yielded you approximately $9.15 but due to the high number of orhpan blocks that number was down around $7.00 - not bad income for 100 MH/s but there were 12 other coins that would have made your more money over the past 24 hours.

The incredible amount of hashrate that has been recently hitting the Fastcoin network has caused lower hashrate miners to experience these orphan blocks, they are having an even harder chance at solving blocks.

The networkhashps option that shows the total network hashrate doesn't include the P2Pool network because of it being decentralized and the way it calculates payouts by the amount of shares submitted.

We've seen spikes of up to 2GH/s on the P2Pool network which end up cornering the network and causing other centralized pools blocks to orphan. This does go both ways depending on where the hashrate is pointed.

It is suggested that for the time being, lower hashrate miners should attempt mining on the P2Pool network, all payouts are sent directly to your wallet, while larger hashrate miners should perhaps setup their own node to run locally or mine directly on an MPOS based pool.

Currently the network is sustaining around 325-342 MH/s while the P2Pool network is sustaining around 436MH/s up to 2.5GH/s spikes earlier today.

We will begin working on ways to make things for efficient to cope with the amount of hashrate being pointed on such a fast transacting coin.

https://www.coingecko.com/en/coins/fastcoin - Network information
http://inetrader.com:5150/static/ - Primary Public P2Pool node
http://www.reddit.com/r/fastcoin - Reddit - (subscribe for updates)
http://sourceforge.com/projects/fastcoin - sourceforge downloads

-m0

example

I've noticed an incredible high amount of orphaned blocks too. One year ago, when I had been actively mining FST, the situation was different.