Hoping to get a client out with updated seeds shortly. Any of the pool ops or anyone have any other concerns with the client?
It's going to look a little bit nicer, as well
If you can edit the benjaminsd getmininginfo RPC call to return networkhashps, that will help anyone else looking to setup a pool using MPOS. Without it, MPOS requires some custom coding to report the network hashrate & est. next difficulty numbers. |
|
|
|
I have a further question, consider me a noob.
I have a leased 2.7 ghz server with 4gb of RAM. It has no ASIC gear, so I can't mine SHA coins at any decent speed, right?
But, I can use my server to mine altcoin of some kind. And also I assume that many here are experts and are mining both SHA and scrypt as is the 'new way' it seems.
So, how can I support the benjamins movement with my dumb old server, and also, what scrypt coin should I mine? I am seeing catcoin looks like the same graphing pattern as benjamins, I like that upward slope in difficulty but the true money altcoins are ones that are trashcoins in terms of descending difficulty.
Unfortunately without a GPU you're not going to do much good mining scrypt. You're probably better of mining a CPU-only coin like PrimeCoin or my favorite - Datacoin |
|
|
|
Someone is being a Knob and selling low amounts for low prices at 2556/7/8/9 etc at 10 BEN per order....WTF are you thinking !
Trading bots. |
|
|
|
PityThePool - Ben finally fixed to show proper network hashrate and est next difficulty  Did you add the network hash yourself or use our update? Just want to make sure ours was correct I used the updated source you provided. Pool software (MPOS) however does not use that - it can only use the "networkhashps" property provided by getmininginfo, which Benjamins stilll does not provide. I pretty much suck at PHP so it took me awhile to figure out how to change the PHP to make it work with getnetworkhashps  |
|
|
|
Running new wallet 1.0.1 Pity the Pool! BlackCoin (BC) Pool- Solid servers, UPS/generator backups
- Redundant internet
- 1.5% fee
- Dedicated equipment - we own the hardware, we own the data center
http://bc.pitythepool.com |
|
|
|
PityThePool - Ben finally fixed to show proper network hashrate and est next difficulty
|
|
|
|
PityThePool BlackCoin pool is operating againAny of you that had balances there should be updated. Sorry I forgot to schedule the cron job to do block payouts. Ready to go now.
|
|
|
|
I read somewhere they are supposed to launch on February 28 but I can't seem to find it now http://pir.pitythepool.com is up and running, been mining there for a LONG time now, working well |
|
|
|
|
I tested myself and Allcrypt is right - the JSON RPC interface is broken.
I tested sending getmininginfo and receive HTTP (500) Internal Server Error
Some commands work: getaccountaddress, listtransactions, getbalance
Most do not. getpeerinfo, getinfo, getmininginfo, gethashespersec, getgenerate, many more
These commands all work from the debug console in the Windows wallet - they do *NOT* work over a http connection to the wallet. They all return HTTP 500 Internal Server Error
|
|
|
|
I vote every day. I dont know how some coins get on there so fast. There must be a trick or a scrypt they run to rack up the voting! You can send BTC to buy votes. Every coin added so far has had 2+ BTC added. Kitteh doesn't really need any more exchanges, it's already on enough. i just dont understand why you would pay 2BTC just to have a coin added to an exchange that already makes a ton of money off of trade fees... The "bribes" are paid by large holders of coins that don't exist on any exchanges yet (or only exist on really crappy ones) All coins are worth $0 until they show up on an exchange. If I were holding 200M of some coin that wasn't traded anywhere yet, or only traded on some really crappy exchange, I might put some BTC towards getting it listed elsewhere so I could have a better chance at selling them. |
|
|
|
|
Update:
A few minor UI fixes. Sorry I had a major hardware failure at my data center and this kinda took over my life for about a week. More coming soon.
Coming soon:
Still working on the alerts mechanism. Also re-architecting this a bit while I finish the Windows agent which will allow you to view/control your rigs without setting up any firewall/nat rules.
Still looking for more users and more feedback!
|
|
|
|
I am still going to reiterate my previous statement about difficulty adjustments; something needs to be done about the 24 hour time frame on the difficulty retarget. KGW is a good solution, or even a more old-fashioned 6 hours retarget would be just fine. If we keep growing hashpower at an exponential rate like this, it is going to be more difficult to make updates and improvements in the future.
I agree on the current 24hr diff retarget. Every scrypt coin I've been involved with, if it becomes even moderately successful, ends up going to KGW or a 1-block retarget eventually anyway. There is over 30GH of mining power between Middlecoin, Hashcows and Multipool.us. They can easily send a coin's diff to Mars within a few hours and it with a retarget of 24h it may take weeks to adjust back down. |
|
|
|
Is the pitythepool working correctly??
Yes. Looks like overnight one of the cron jobs that handles payouts and new blocks was disabled. Nothing was lost, just that auto payouts and the website stats were not updating properly. Working fine now. |
|
|
|
With respect to exchanges, I'd recommend Mintpal- they run a very tight ship over there, with something like 865BTC in volume over the past 24 hours. I've seen it go as high as 2300BTC during the MINT dump. Very reliable exchange with a limited number of trading pairs.
I also like MintPal - out of the dozen or so new exchanges that have popped up over the past couple months, I think MintPal and Poloniex look the most promising. I think AllCrypt has potential as well, have to see how their "grand opening" goes in a few days. Fixed the diff retarget duration on PityThePool, I had misread it as 2 hours when I configured the pool originally. Looks like we are about 30 blocks away. |
|
|
|
 Pity the Pool! PirateCoin (PIR) Pool- Solid servers, UPS/generator backups
- Redundant internet
- 1.5% fee
- Dedicated equipment - we own the hardware, we own the data center
http://pir.pitythepool.com
Looks like PIR will be on AllCrypt at launch day! |
|
|
|
Fork Averted. Pitythepool is down to 21 M/H and the network is at 47 M/H.
Although, unless I'm reading this wrong it looks like only a single miner has that 21 MH/S rate, and joined PityThePool, causing that spike. Someone out there has a big, big, rig.
Just be more careful about where you guys mine until we have a larger mining base. Hashrates should stabilize soon among the 3 pools. Sorry for the inconvenience.
I don't believe there is any single miner with 21MH, PityThePool has no one near that size. It's pretty normal for a pool's hashrate to swing +/- 10-20% minute by minute, even more. Could be 22MH one minute and 28MH the next with no new miners having joined. The pool's hashrate calculation is different than that of the wallet and will vary more. I understand your desire to keep the hashrate distributed but unfortunately this is pretty much how it's going to be until there are some more pools online and more exposure to the coin. Every coin goes through this the first several days. Another big help to guard against accidental/unwanted forks would be to get a block explorer up and running. I run several pools and it is a big help when there is question as to whether or not a coin has been forked. Pool operators can reference the official block explorer to determine whether the blocks they are finding are on the correct chain. On a side note - I expected the diff to have adjusted by now, it's been hours at 0.66 diff and no change . . . diff retarget is 30 blocks correct? |
|
|
|
|
WTF happened to original dev motd2k? Just made a coin, nice website and block explorer to go with it and bailed?
|
|
|
|
MINERS, PLEASE DISTRIBUTE YOURSELVES AMONG THE POOLS
A large portion of Pool Mining is coming from PityThePool (>23 MH/s) or 51%. Since our subsidy requires less than 40% of the total mining power, I'm sure it is in the best interest of the pool manager and the coin that we are not subject to a 51% attack and that the individual pool rate is below 40%.
Agreed. There is no risk of a 51% attack from PityThePool, but accidental forks can occur anytime a single entity controls > 51% of the network hashrate. New registrations are disabled at PityThePool until the hashrate is better distributed. *Edit* Would help if you could make the pools list a little more prominent on the ANN thread and update your website with a pools listing. |
|
|
|
OMG, that is GREAT, glad I'm not the only one here who remembers Weird Al |
|
|
|
|
Show Posts
