- Fox-Ified RPC commands.
This will not work. If you don't also provide the old method names, I will have to remove your coin from our pool, and I'm sure other pool operators will agree with me on here. We rely on standardized rpc command names, it would be too much work to figure out what the RPC commands for each coin are. Can you please, either change them back, or make it so that the old commands also work. (I thought that using a custom wallet name was bad, but this is way stupider:)) Also you say this is a mandatory update, but don't say when the fork will happen, is it "after block 196,000"? |
|
|
|
Update 1.5 for FoxCoin RELEASED!
Changelog:
- Fox-Ified RPC commands.
- Added sexy syncing bar.
- No seriously, the new syncing bar is awesome.
- Did you see the last one?
- Added inbuilt miner.
- Added statistics page.
- Clients can now connect to up to 16 nodes.
- Fixed bug where block reward would drop to 5 FOX after block 196,000.
- Updated mining tutorial.
- Cleaned up source.
THIS UPDATE IS MANDATORY!
Windows Binaries / Source / GitHub on OP and website. OSX Coming soon.
Can you please try to learn how to use git. "git pull" should not look like this: $ git pull
Auto-merging src/version.h
CONFLICT (add/add): Merge conflict in src/version.h
Auto-merging src/version.cpp
CONFLICT (add/add): Merge conflict in src/version.cpp
Auto-merging src/qt/statisticspage.h
CONFLICT (add/add): Merge conflict in src/qt/statisticspage.h
....
It's very annoying, figuring out what changed is much much harder now. |
|
|
|
We are fast, already upgraded to the new wallet, feel free to park your miners at: https://pot.hash.so/* 1% default donation, can be removed but please don't  * Super fast servers * vardiff * Default MPOS layout, the one you know well (efficient!), Internals have been optimized to make it faster! * stratum on port 80 and 443, which helps if you are behind a firewall. * One click coin switcher, mine all of our ( 30) coins with ease! (New coins to be added in the next few days!) * Nice coin list that displays all of our coins, and stats about them. * PPLNS * Very nice admins, come say Hi in IRC #hash.so @ freenode |
|
|
|
Definitely could use a little bit more miners on https://corg.hash.so/ we aren't even close to 90% of the network, yet! |
|
|
|
Come mine Klondike with us: https://kdc.hash.so/* 1% default donation, can be removed but please don't * Super fast servers * vardiff * Default MPOS layout, the one you know well (efficient!), Internals have been optimized to make it faster! * stratum on port 80 and 443, which helps if you are behind a firewall * One click coin switcher, mine all of our ( 30) coins with ease! * PPLNS * Very nice admins, come say hi in IRC #hash.so @ freenode |
|
|
|
Need some more hash over at updamoon.com. Looks like hash.so is hogging it all Spread the hashish! Sorry I make it way too easy to switch miners to other coins It's quite nice to mine low diff coins, I have some SOL stashed away myself. |
|
|
|
A little bit more time for pools would have been nice, why such a freaking rush, it's not like few days of warning would have changed things dramatically. My 200MH/s pool was stuck on the wrong fork for maybe 12 hours  I blame no one else than myself, but I might have been able to see the update if there would have been more time. I do apologize for the short notice- we were pumping messages out for 5 days ahead of the release, pools should have been on notice but I still understand the window to upgrade was short. Luckily the majority of the network moved over very quickly. What pool do you run? If it is a public pool we're trying to keep the list of updated pools current so post up your pool if its public. Thanks. When I left the fork there was still 700MH/s on the forked network, so I definitely was not alone. It also wasn't that bad for us, I think the pool was only popular for 7 hours, and only last two hours we had more than 100MH/s on there. Unfortunate, but happens. My pools is at https://meow.hash.so/ but it's currently down for maintenance  I need to nuke it up and start fresh, my miners will love me.. |
|
|
|
A little bit more time for pools would have been nice, why such a freaking rush, it's not like few days of warning would have changed things dramatically. My 200MH/s pool was stuck on the wrong fork for maybe 12 hours I blame no one else than myself, but I might have been able to see the update if there would have been more time. |
|
|
|
My transactions are lost, in the web site i see 17 transactions total 276402.44511173 debit,ap but in my wallet i see 2 transactions total 61383.81587254? my wallet is up to date? what is the reason???  You need to upgrade to a new leafcoin wallet: https://bitcointalk.org/index.php?topic=430091.0 I see your transactions on the block explorers just fine. Thanks for mining with us, and let me know if you need anything else! |
|
|
|
Come mine Penguincoin with us: https://peng.hash.so/* 1% default donation, can be removed but please don't * Super fast servers * vardiff * Default MPOS layout, the one you know well (efficient!), Internals have been optimized to make it faster! * stratum on port 80 and 443, which helps if you are behind a firewall * One click coin switcher, mine all of our ( 31) coins with ease! * PPLNS * Very nice admins, come say hi in IRC #hash.so @ freenode |
|
|
|
Come mine TopCoin with us: https://top.hash.so/* 1% default donation, can be removed but please don't * Super fast servers * vardiff * Default MPOS layout, the one you know well (efficient!), Internals have been optimized to make it faster! * stratum on port 80 and 443, which helps if you are behind a firewall * One click coin switcher, mine all of our ( 31) coins with ease! * PPLNS * Very nice admins, come say hi in IRC #hash.so @ freenode |
|
|
|
But Solcoin project why are you worrying about this? It's not a problem and it takes something extreme for a pool to have to delete their chain and download it again. Those pools will sort it out themselves when they notice an orphan, syncing up to proper chain automatically.
Because we have only two nodes. They are enough for this low hashrate and for just two pools, but since there was a fork and since the number of peers is low (two nodes, two pools) the worst case scenario is that one or both pools overtake the nodes, and then we have to resync the nodes instead. I don't see the fork, both pools found the block 14224 at the same time. Both pools considered their version "valid". Other nodes in the network don't really care. And it was resolved when hash.so found the next block (14225). At that point updamoon wallet realized that their 14224 is not going anywhere and marked it as orphan. All looks very normal to me. A fork could have happened when we were running different versions of the wallets, but I didn't see it happen even then. (and I did redownload my blockchains when I first noticed that there might be a issue). |
|
|
|
We have a problem, actually. Both hash.so and updamoon.com reports to have found block 14224, meaning there is a fork on one of the pools. Both nodes are in sync. I cannot tell which pool has forked because MPOS never reveals block hashes, but I suspect it is hash.so after all since updamoon seems to have a higher hashrate right now. Could admins of hash.so and updamoon.com verify that your latest blocks match the block explorer sitting on the second node? ( http://solcoin-explorer.tru.io/ ) Whichever of the pools are out of sync should kill their chain and redownload from the nodes, unless you're interested in trying to race for the longest chain. Looks like it resolved itself, we won! |
|
|
|
Is one of the pools still over 51%? smc.hash.so was it? I can't remember, but shouldn't people be aware of this potential problem?
smc.hash.so have ~50%+ now :/ Coin Pool rate Net rate Difficulty
smc 482.3 MH/s 864 MH/s 8.50960573 We need to look at these things DEV - have you made any Tool for this? (repost from reddit: http://www.reddit.com/r/SmartCoin/comments/1xiyet/read_httpssmchashso_is_500mhs_and_entire_network/cfe9ljf) It doesn't really matter how much of the network we have, also those numbers are misleading. Network hash rate updates much more slowly than our pools dashboard. The page you should look at is this: https://smc.hash.so/index.php?page=statistics&action=blocksFrom there you can see that currently our pool only has about 33% of the network, not even near to the 51%. That said, most of the time combined hashing power of hash.so (all the different coins) is well over 51% of the SMC network. If I wanted to do a 51% attack, I could just point all the miners to SMC. This holds obviously is true for all large pools and smaller coins. Say if you have a 5GH/s doge pool, you could easily point everyone to some "low" difficulty coin for a few minutes to do your evil deeds, the miners wouldn't even notice it. (I posted this to BTCtalk: https://bitcointalk.org/index.php?topic=400893.msg4920872#msg4920872 a while ago). The bottomline is that you need to trust the pool you are mining on. We try to be as transparent as possible so that people can mine with us, and I think our track record speaks for itself |
|
|
|
actually I think there was no fork. My pools crons were just disabled. I think everything went smoothly I'll look more once I'm at home. I'll cross fingers, let us know please so I know if I can keep mining on hash.so to spread hashrate better. Yeah, everything looks good. I re-downloaded the block chain, but none of the blocks got marked as orphans. And well, I did upgrade pretty quickly, so I guess we got lucky. A bit stupid of me to forget to re-enable crons after the wallet upgrade |
|
|
|
Small update with correction to block maturity setting is available: Pools and node operators, please download latest version. The links on front page are updated.
Doesn't this potentially fork the coin? Some wallets will accept blocks with coins that have matured for 72 blocks and older wallets will reject such blocks. Doesn't sound like a safe thing to do. I upgraded my pools wallet, but now I'm not sure if it was a good idea or not. Yes, this had a potential risk, but it had to be done. Thankfully the Solcoin network is still small so the problem hit "only" one party, and I apologize that it was your pool that hit the snag. I hope you will have oversight with the bump in the road and keep operating your pool for the currency. Both nodes and the other pool are running the latest version and they are in sync at the correct block - if you delete the chain and resync from scratch miners can resume on the old block path. Since we have few transactions going currently it only takes about a minute for the daemon to download the entire chain from the nodes. actually I think there was no fork. My pools crons were just disabled. I think everything went smoothly I'll look more once I'm at home. |
|
|
|
|
Show Posts
