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.
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. If you look now, GetNetworkHashPS is showing 178 MH/s while P2Pool's network is reflecting 391MH/s. |
|
|
|
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'
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. |
|
|
|
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.  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. |
|
|
|
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 |
|
|
|
any idea how to reduce the amount of orphans when mining? @200mh/s i get ~80-90% orphans....
Lower your intensity... set config to --queue 0 --scan-time 1 --expiry 1 any wallet settings? I'm running it on a pool, but seems it's too much to handle efficiently... Wallet settings? I'm not quite sure what you're asking there, running it on a pool? Please explain your situation a bit more and I'll do my best to help you... |
|
|
|
any idea how to reduce the amount of orphans when mining? @200mh/s i get ~80-90% orphans....
Lower your intensity... set config to --queue 0 --scan-time 1 --expiry 1 |
|
|
|
Try using the bootstrap.dat file and also adding nodes to your config. https://bitcointalk.org/index.php?topic=199839.msg6223915#msg6223915RoyalCoin Nodes: addnode=192.99.44.51 addnode=65.161.46.127 addnode=89.76.154.197 addnode=62.254.202.134 addnode=38.126.175.2 addnode=82.2.7.48 addnode=159.224.220.21 addnode=87.98.218.143 addnode=98.208.162.200 addnode=50.26.216.184 addnode=69.66.122.7 addnode=210.84.24.29 addnode=70.164.233.143 addnode=5.249.152.30 |
|
|
|
I went ahead and put the P2Pool back up, everything should still work as it did before. Bytecoin P2PoolDecentralized Server Location: USA/California  Server Stats: http://bte.thecomputerfield.com:5152/static/Use Stratum: -o stratum+tcp://bte.thecomputerfield.com:5152 -u <your_bytecoin_address> -p <random_password> Non Stratum: -o http://bte.thecomputerfield.com:5152 -u <your_bytecoin_address> -p <random_password> Reducing DOA; Add +16 directly to the END of your WALLET address. i.e. cgminer -o http://bte.thecomputerfield.com:5152 -u 8FJg9N8J181VFjzw2eip4meZQTMzga4CXo +16 -p x Just as a reminder, there are no accounts or coins stored by the pool. No confirmations to wait for....your coins are sent to you as soon as a block is found. Every block found is simultaneously announced across all the wallets in the P2Pool so there are less orphans encountered. NOTE: If you're getting stratum auth error, be sure to use the --fix-protocol switch in your miners config. |
|
|
|
The primary source of downloads for Fastcoin are available on Sourceforge. | Windows, Mac, Debian, Ubuntu, Mint, Fedora, Redhat, Slackware, Multibit, |
and the Android wallet. The source is also available along with the bootstrap.dat. http://sourceforge.com/projects/fastcoin
|
|
|
|
Any updates on new or current working pools?
Check out the list of public nodes on P2Pools.org http://p2pools.org/fst |
|
|
|
I have windows qt wallet v0.8.7.2-unk-beta
I have 2 transactions of 25000 outgoing which are stuck with ?. I tried rescan, I tried to use the raw transaction and another wallet to rebroadcast and it is still stuck. Any ideas how I can get these coins back?
Just export your private keys and import them into a new wallet. The tx could have very well been broadcast into an orphan block is all. |
|
|
|
Coingecko has been doing a good job at providing ALOT of information related to alternate cryptocurrencies. It seems like the handful of other sites that are similar, like coinwarz and coinmarketcap, just haven't put in the effort to support everyone's interest. Mind you, they have provided valuable information for both miners and investors. Bias choices have easily been made based on this information. While miners have constantly used these sites precisely looking for the current most profitable coin to dump on an exchange, investors look to support a coin by increasing it's market cap in order to gain more attention and ranks which will later increase only their profits until they cash in. If the miners aren't dumping their new alts on an exchange to turn out a wee-bit of profits, then they are simply an enthusiast who is collecting with high hopes of someday cashing in for even bigger profits at the expense of others. I think the mentality needs to change when thinking about alts, particularly when it comes to usability, functionality and overall sustainability. Most importantly, one should ensure the coin they look to support doesn't have a group of anonymous developers who are only interested in counterfeiting coins for a short time and who have nothing else better to do with their lives and their time. Now I'll mention Fastcoin, because it works, it's stable, it's been around almost two years and has been able to withstand multiple attempts of attack all while holding it's own weight. It hasn't needed huge publicity, nor has it needed a bootstrapped, high flutin' flashy website that appeals to those looking for eye candy. It's just a super fast coin with a good re-targeting algorithm and true to it's name. https://www.coingecko.com/en/coins/fastcoin I am listed under the 'Altcoin Team Leads' on coingecko's top cryptocurrency people you should absolutely follow on Twitter. https://twitter.com/JonMarshallz |
|
|
|
Any updates on new or current working pools?
The pool's are regularly updated on the FastCoinTalk forum, there are threads in which users can discuss their opinions on various pools as well as the pool operator's who offer suggestions on proper miner configuration tailored to your specific hardware. http://www.fastcointalk.org/index.php/board,3.0.html |
|
|
|
Notification from https://www.coins-e.com/ @fast_coin #FST has won this week's voting. Stay tuned as we add your coin to our exchange! |
|
|
|
|
The Krugercoin wallet completely synced for me, then I went ahead and sent a transaction to the Cryptsy exchange. Everything still works as expected, just because a coin doesn't get very many posts on this "Bitcoin" forum, does not necessarily mean it is 'dead'.
-m0
|
|
|
|
 I've resolved the problem that had caused some users to pull out their hair because of the slow synchronization time. It was caused by a recent blk*.dat file being corrupt prior to creating the bootstrap.dat file. The new revised bootstrap.dat has been uploaded to both sources below and a full sync up to 3850000 blocks now takes less than 7 hours on the most minimal hardware. 1 CPU core, 512MB Ram, 2GB swapfile, using the following command line perimeter. Archive Mirror - https://archive.org/details/fastcoin_bootstrap (wget compatible) SourceForge - https://sourceforge.net/projects/fastcoin/files/bootstrap/2014-12-24/ The bug that limited some clients to only 8 connections has also been resolved. Users can now add listen=1 to their fastcoin.conf file enabling the client to accept more incoming connections. It's also suggested to use; maxconnections=30
listen=1 More or less depending on the users preference. Happy Holidays! |
|
|
|
|
Show Posts
