Holy shit!! 24 hours and already huge difficulty. Guess I pass on this one.
"blocks" : 1546,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 7127.82880870,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1818186537,
"pooledtx" : 0,
"testnet" : false,
"blockreward" : "50.00"
Try 12 hours. I've mined this coin with two decent comps for one hour and not a single block found. That is not bad luck. This coin was instamined by either a botnet or someone with a serious cloudmining problem. If you can't solo mine a coin 10 hours after launch there is a problem. Giving up, everything about this coin reeks of amateurism, from the pathetic looking wallet to the half-assed website with broken english (chinese dev maybe?). Someone claimed difficulty was @ ~13 approx. 11hrs40m before your post. So for you difficulty had to be under 10. That's not hard to solo mine with quark cpuminer, since even something like a junk 2x L5420 can get over 500khash. So that would be unlucky, unless you were using the built-in miner, in which case you probably should research these things more before diving in to a somewhat futile endeavor I started at block 1000, I'm not a botnet and I rarely make use of cloud mining as normally it's a colossal waste of $$, I do on occasion start some stuff up for a new coin though, I'm paying $2.10 an hour right now for thirty of the 8-core amazon spot instances. Rest is dedicated servers that I buy in bulk and use for this or resell, depending on what's going on (oh i've also some stuff colo at dacentec, cool place w/ rent to own) So because you are able to mine with 30x 8 core cloud servers its fair? Talk about a biased opinion. wtf isn't fair about it? it's not like $2.10 an hour is outlandish. we're not talking about someone blowing $100 an hour on 100 of the 32 core servers It's a "CoinMiner", if you're using it on purpose, then these hits are not of interest |
|
|
|
This is what I managed w/ one computer and about 45 seconds: tcp 0 0 5.9.24.81:9555 71.42.153.15:61772 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61613 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49614 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61657 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61653 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61660 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61767 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61690 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61611 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61750 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61698 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61648 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61775 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49647 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61667 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61672 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61622 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49637 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49609 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61714 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61671 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49643 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49639 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61652 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61700 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61761 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61732 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61726 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61605 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61709 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61609 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61758 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61735 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61603 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49625 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61733 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61728 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49628 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61720 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61654 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61754 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61740 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61724 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61773 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61729 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61612 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49620 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61692 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49646 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49645 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61641 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49611 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61682 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49653 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61711 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61640 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61676 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61602 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61697 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61744 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61712 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49606 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61704 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61687 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61674 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49607 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61685 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:49633 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61771 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61606 ESTABLISHED 2679/python
tcp 0 0 5.9.24.81:9555 71.42.153.15:61765 ESTABLISHED 2679/python I guess a firewall rule limiting the # of simultaneous connections would work? |
|
|
|
|
I just had to close a p2pool with over 4000 connections/sockets open. Is there any way to fix this? It's trivially easy to knock someone's p2pool offline?
|
|
|
|
Those are for the wallet. I'm talking about the miner they mention in the first post. I have some compiled for Windows. Google kept flagging my website as malicious because of them though so I eventually removed it. I don't remember which files belonged to the wallet and which to the miner, but: https://www.dropbox.com/s/q5dami23y32gcbc/quarkcoin.rar |
|
|
|
Holy shit!! 24 hours and already huge difficulty. Guess I pass on this one.
"blocks" : 1546,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 7127.82880870,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 1818186537,
"pooledtx" : 0,
"testnet" : false,
"blockreward" : "50.00"
Try 12 hours. I've mined this coin with two decent comps for one hour and not a single block found. That is not bad luck. This coin was instamined by either a botnet or someone with a serious cloudmining problem. If you can't solo mine a coin 10 hours after launch there is a problem. Giving up, everything about this coin reeks of amateurism, from the pathetic looking wallet to the half-assed website with broken english (chinese dev maybe?). Someone claimed difficulty was @ ~13 approx. 11hrs40m before your post. So for you difficulty had to be under 10. That's not hard to solo mine with quark cpuminer, since even something like a junk 2x L5420 can get over 500khash. So that would be unlucky, unless you were using the built-in miner, in which case you probably should research these things more before diving in to a somewhat futile endeavor I started at block 1000, I'm not a botnet and I rarely make use of cloud mining as normally it's a colossal waste of $$, I do on occasion start some stuff up for a new coin though, I'm paying $2.10 an hour right now for thirty of the 8-core amazon spot instances. Rest is dedicated servers that I buy in bulk and use for this or resell, depending on what's going on (oh i've also some stuff colo at dacentec, cool place w/ rent to own) |
|
|
|
|
I have two DOGE deposits from over 24hrs ago that haven't showed up yet... it seems like their support waits a minimum of 12 hrs before responding, due to the fact that most of these issues resolve themselves, I guess.
But it was annoying to have the person ask for transaction details when I already provided it in the main ticket
|
|
|
|
A bit off-track here, but does anyone know of a link or explanation for all the stats that the pool sites have? I'm thinking of things like target variance, average efficiency, rate est. etc.
efficiency for a p2pool that isn't set up solo (net2 & frozen = solo, doge = multi for mine) would theoretically be how much more DOGE you are earning off of people that are using p2pool and getting more DOA/orphans... just *the % more than you'd get off a 0% fee pool over the long term. ofc you'd have to take your own DOA rates and apply those.. the pool is mostly responsible for orphans, the person mining is mostly responsible for any DOAs. generally speaking, as there are some exceptions to that rule I solved a block earlier and the p2pool chain orphaned it, so it doesn't appear in the list. That's an example of a "lost share" actually solving a block and that's how you get your extra from higher efficiency |
|
|
|
Hey I'm pretty new in altcoins but thank god one of early adopters of Dogecoin. Now I have couple of questions. If Dogecoin is someday worth of example 10$ and that would make me pretty rich so is there any good way to withdraw those earnings to your real bank account without such big fees? I'm living in Finland so my bank is in Finland but I hope there would be some service that let you withdraw your money without losing so big amounts of it? And second question is when we are going to see Dogecoin value at 1$ as an example? and if there is some real investors please tell what's the future of the Doge? I hope it will go to the moon! But it wouldn't be the first dog in the moon. Look back in history: 1957 soviet union sent Laika dog there so it is really possible to get Doge there as well allmost 57 years later  . DOGE: DJpqwezzrdg6E8vNxqM6FBdXSMQrEd35bj May I ask how old are you? IMHO I don't think DOGE will ever reach usd10, even 1. Just because there is not that much money. Now everyone can say" I will keep my daily production (50k) and one day it will be worth USD50k . When it happen, all of us will be sold our doges to BTC and then to USD but first somebody must buy it. And if this happen, DOGE will land pretty hard. Maybe few lucky person will withdraw enough to be a real millionaire. It is just my realistic view. I believe someone with 10B doges can be pretty rich man. I sell my dogecoins just as soon as I get them, a bit like bitcoins over the last 3 yrs |
|
|
|
|
aha, wasted too much time at 10.
anyway, I saw minimum fee was 0.0000001, so I changed it to 0.00001, so the p2pool will only mine for transactions with fee of that amt per kb. if anyone wonders about the lack of transactions, etc. it's not set to zero (transactions), just something more reasonable
|
|
|
|
;DThe miners are waiting for 1441th blocks.
it was 5269 til those 107.150.48.98 and 107.150.48.100 went down. wholesaleinternet servers, so probably a RAM issue. or i hope it's not the dual core grab bag |
|
|
|
|
difficulty should go down since those pools most ppl were using arent really functioning properly.
well, i'd think so anyway
|
|
|
|
whoops, I think I missed a block while I transitioned everything to RAM |
|
|
|
That's a decent idea about running a VPS for a bitcoind relay. I could stick p2pool on there too while I'm at it.
I like this idea of a VPS with the p2pool and bitcoind nodes on it. Will probably be trying that in the new few days. Anyone else have any tips on doing it? There's a Bitcoin tutorial for digital ocean I know how to set up bitcoind on a VPS generally. Just wondering about the p2pool aspect of it. For example, is it better to have bitcoin and/or p2pool local nodes that connect to their counterparts on the VPS or just have the miners connect directly to p2pool+bitcoind on the VPS? Just connect to vps make p2pool public Open ports 833 9332 9333 If the VPS is good enough to run p2pool on with ~8 outgoing connections, then I'd just run p2pool there. Bitcoind isn't a problem, since getting slow block notifications in p2ool doesn't really penalize you (all in all, it's probably beneficial as far as building off previous shares goes).... if you ever solved a block, it'd increase chances of it being an orphan tho, I suppose. ..... but I wouldn't open it to the public, not on one of those 'couple of dollars' VPS'es that I was referring to, hah |
|
|
|
Hi, I was experimenting with p2pool to see how does it work. My equipment is not good enough to make any profit, but wanted to try out how set up and run one, to be able get more people on here in the Taipei Hackerspace. I run into the problem that I never actually got any payout from the p2pools that I participated in. Tried Litecoin a while back (mine-litecoins worked even if miniscule payout, p2pool received nothing). This week tried Dogecoin (much fun, shiny coins), but again nothing. I'm connecting to this pool: http://nogleg.com:9555/static/graphs.html?Week and my address is DQzhUthpxummUdnCFVcHH7Bw2k5JfuA79H In the interval in question, the area under the hashrate curve for me is about 1/2000th of the pool hashing power (~1GHash vs ~2THash). Wouldn't that mean that I should have gotten about 1/2000th of the payout? The current payout averages at 5.09kDOGE on the graph, that would mean ~2DOGE. But, as the graphs show as well, my miner received totally zero. This is pretty much the same experience in the Litecoin pool as well. Do I misunderstand something? Is my contributed hashing power too small? The graphs show other miner with ~12GHash (only 12x my contribution) for the same interval getting 171DOGE on average. Though also see people with much more power (819GHash) receiving nothing according to the graphs. What's going on? since that's my pool, I went ahead and checked http://nogleg.com:9555/static/graphs.html?Monthsearch for DQz You just never got a share. It'd be pretty rare at 8-10Khash even over a period of a few days.. and before someone says something about the local rate doa/orphans, compare it to pool rate on these ultra-fast coins, i've customized p2pool to wait x seconds before penalizing shares after a new block is found |
|
|
|
You're comparing with others in p2pool. I'm comparing with non p2pool.
M
You could think in p2pool way. If your good share rate is higher/lower than others in p2pool, your average income is higher/lower than others in non-p2pool. Then take low miner fee, tx fee, p2p, and coinbase tx as pros, and higher variance as cons. Also, unless things have changed, p2pool can not be reliably run on a home DSL connection. That means folks like myself have to use a public node or suffer higher than normal rejects (and normal is high enough thank you!). That means you have two choices: trust the op of that public node, or get higher rejects. Both negate two supposed benefits of p2pool. M The pool I ran for bitcoins averaged ~110-115% efficiency, but that was on a dedicated server (not a VPS) in Germany with 1gbit/1gbit switch (200mbps guaranteed but in practice could 99% of the time get 80MB/s + ). Averaged around 3-5% DOA for me and about 2-4% orphans. When I initially tried to set up my home connection, I was getting around 0-1% DOA and 15-20% orphans. A few percentage of the orphan rate was from being in the US instead of France/Germany/Netherlands where most of these dedicated servers & VPS are running. Most was from my 768kbps upstream cap. Later on I was able to set it up w/ 0-1% DOA and an orphan rate under 10% (though it still wasn't as good as just using German remote server, after share time got changed to 30s)... anyway, the deal is, just have bitcoind connect to 1 or 2 servers & also your p2pool node need only connect to a handful of servers... you just have to pick the right ones. I have no clue what those are anymore. (ie, change outgoing connections to 0 and handpick the servers to connect to) ed: i think you can find a VPS for a couple of bucks to run a bitcoind relay on |
|
|
|
when is alien going to exchange?
only after my aliens become more valuable than my zimbabwean dollars |
|
|
|
1000 aliencoins for sale for 1 BTC. PM me.
I have 1000 I'll sell for .1 bitcoins |
|
|
|
|
I pity the fool that sells Coinye for Dogecoin and doesn't hand over 90% of it immediately to Kanye West
|
|
|
|
|
Show Posts
