Where is some formula how luck chart is created?
I`m not sure that "Hashing performed vs blocks produced" is accurate.
I think that graph would better be called "Hashing performed based on shares found vs blocks produced" but why would this be inaccurate? Maybe is is very wrong because of jumpers? They add much power for short period of time and killing match?
Hopping will not affect luck. If p2pool's hash rate increases because of a new miner (hopper or not), then the estimated time to find a block will go down. If they leave, it goes back up. It looks like we NEVER make less calculations than we need!
I do not know what this means. |
|
|
|
Try 50btc.com (or btcguild or abcpool).
I've given up on p2pool. There is something seriously wrong with it (or I just got a really bad luck. Variance is a bitch, I guess)
In 12 hours on p2pool, my 3.5Gh/s rig generated (to be paid when block is found) a whole 0.31 BTC. Yesterday I switched to 50btc.com, the earnings were 1.15 BTC in the same 12 hour period.
I like the idea of p2pool, however I'm not going to run my rig on p2pool just because I like the idea behind it.
I'm not a religious person. So I wish you all p2pool devotees good luck with it.
If someone knows how to make more money on p2pool than 1.5% pps, please post your p2pool/miner configuration. I'd be willing to validate your results.
I assume you ran it for more than 12 hours. I ran it for a few weeks, and reached the same conclusion as you. I'm happily mining on ozcoin.net now. Free (donation requested) unless you want PPS. And we're over 1.1 terahash/s for the last 24 hours now. Yesterday was nice!!  In the last 24 hours I got 3.57 btc after 1% donation with 5 gh/s. Supposedly ozcoin averages about 750gh/s and a lot of GPUMax users have ozcoin as the backup pool. M He says "12 hours" multiple times, so your assumption is wrong... Long term, p2pool is only paying 90% of what is expected. I don't know why this hasn't sunk in... Some people are saying p2pool pays more than PPS and they are wrong as clearly demonstrated by the luck chart. Other people are saying that p2pool pays far less than PPS and they are also wrong as also clearly demonstrated by the luck chart. Comparing a PPLNS pool to a PPS pool over a short period demonstrates a lack of understanding of the payout methods. http://p2pool.info/luck |
|
|
|
|
I just tested the tablesorterfix branch on my Linux VM and it works great. The CPU issues are totally gone. I'll test on my Mac next.
|
|
|
|
Anyone have any comments about 0.77? Given the lack of response to it, I suspect either no one is using it, or there are no complaints. Either way, it's about time to release it, because I'm positive there are some users out there suffering (or stopped using) due to the table-sorting bug.
Haven't had a chance to pull that branch yet. I will probably have time tomorrow. EDIT: Oh cool. I see you went ahead and released it. |
|
|
|
A) the average of: "number of 1-difficulty shares" / "the block difficulty for each block found" ... over a LONG period of time (months)
this is how you correctly calculate "LUCK" and should normally be close to 1.0 (100%) over a long period of time
And p2pool is sitting under 90% 90 day luck and seems to have been since January (when the pool actually started to grow). The question still remains; Is this 90% really just "bad luck", or is it caused by some flaw in p2pool's code? |
|
|
|
Give her a shot, I think your clocks are either too high or you have a fussy GPU in there (probably GPU_0) that doesn't want to play nice. # Big A Miner Thing configuration
# /etc/bamt/bamt.conf
---
settings:
miner_id: bamt-miner
miner_loc: unspecified location
do_monitor: 0
# if monitoring, how do we send email alerts?
# these are required..
# smtp_host: smtp.gmail.com
# smtp_to: you@yourmail.com
# these are optional..
# smtp_from: somefrom@address
# smtp_subject: I wanted a custom subject in my alerts...
# smtp_port: 587
# smtp_auth_user: user@where
# smtp_auth_pass: secret
# smtp_tls: 1
# smtp_ssl: 1
gpu0:
disabled: 0
# pre_oc_cmd:
core_speed_0: 300
core_speed_1: 800
core_speed_2: 850
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
# core_voltage_0: 1.125
# core_voltage_1: 1.125
# core_voltage_2: 1.125000
fan_speed: 40
# post_oc_cmd:
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=9
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 2
gpu1:
disabled: 0
core_speed_0: 300
core_speed_1: 800
core_speed_2: 850
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
# core_voltage_0: 1.125
# core_voltage_1: 1.125
# core_voltage_2: 1.125000
fan_speed: 30
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu2:
disabled: 0
core_speed_0: 300
core_speed_1: 800
core_speed_2: 850
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
# core_voltage_0: 1.125
# core_voltage_1: 1.125
# core_voltage_2: 1.125000
fan_speed: 30
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu3:
disabled: 0
core_speed_0: 300
core_speed_1: 800
core_speed_2: 850
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
# core_voltage_0: 1.125
# core_voltage_1: 1.125
# core_voltage_2: 1.125000
fan_speed: 35
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_fan_lo: 2000
monitor_reject_hi: 1
gpu4:
disabled: 0
core_speed_0: 300
core_speed_1: 800
core_speed_2: 850
mem_speed_0: 300
mem_speed_1: 300
mem_speed_2: 300
# core_voltage_0: 1.125
# core_voltage_1: 1.125
# core_voltage_2: 1.125000
fan_speed: 40
kernel: phatk2
kernel_params: BFI_INT VECTORS FASTLOOP=false AGGRESSION=11
pool_file: /etc/bamt/pools
pool_timeout: 180
monitor_temp_lo: 45
monitor_temp_hi: 80
monitor_load_lo: 80
monitor_hash_lo: 125
monitor_shares_lo: 1
You really shouldn't mess with core_speed_0 or core_speed_1, though. |
|
|
|
SLC is a scam, so it doesn't count.
Why do you keep quoting everything in this thread  It's not like it is going to change ever. |
|
|
|
No offense, but bitcoin is going to need at least a decade (maybe century) track record to even be considered in terms of gold. It is experimental. Will the block chain become too bloated? Will it be cracked? Will the network collapse? Can it handle 100,000 transactions a second. To have Paul comment on bitcoin is really lame imho.
Thank god for Paul to make a complete fool out of Krugman.
+1 The internet too, 100 years minimum before I'll be comfortable using it. I lold |
|
|
|
if bitcoind_available():
if bitcoind_rpc('getconnectioncount'):
echo 'online mode'
else:
echo 'Satoshi found, but it has no connections. Falling back to offline mode.'
else:
echo 'offline mode'
I think this would work and should be easy enough to implement. Interesting idea. You're right there is no use cases I'm aware of for using Satoshi client if it's not connected to any peers. However, I've never accessed bitcoind via RPC, I didn't even know there was a way to query the number of connections. I assumed that if google/MS was ping-able, then the Satoshi client is at least capable of having peers. It seems that that assumption is not the case. I don't suppose that connectioncount is something I can query peer-to-peer? Doesn't seem like it, but I also don't want to have to open another network connection just for this purpose... Oh yeah. I forgot you talked to bitcoind over the p2p port, not the rpc layer. Hmm... I'm pretty sure there is a way to ask a node for a list of at least some of it's peers; that is how the network works, right? I don't have any experience with the p2p layer though. |
|
|
|
Can anyone help me solve why I get this error on mac OSX 10.6.8? % sudo make -f Makefile.osx
cc -ggdb -O3 -Wall -c -o pattern.o pattern.c
pattern.c:32:18: error: pcre.h: No such file or directory
pattern.c:1639: error: expected specifier-qualifier-list before ‘pcre’
pattern.c: In function ‘vg_regex_context_add_patterns’:
pattern.c:1658: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
pattern.c:1660: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
pattern.c:1661: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
pattern.c:1671: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1672: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1673: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_pat’
pattern.c:1676: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
pattern.c:1677: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1678: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1678: error: ‘pcre’ undeclared (first use in this function)
pattern.c:1678: error: (Each undeclared identifier is reported only once
pattern.c:1678: error: for each function it appears in.)
pattern.c:1678: error: expected expression before ‘)’ token
pattern.c:1679: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1679: error: ‘pcre_extra’ undeclared (first use in this function)
pattern.c:1679: error: expected expression before ‘)’ token
pattern.c:1680: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_pat’
pattern.c:1681: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
pattern.c:1686: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1687: warning: implicit declaration of function ‘pcre_compile’
pattern.c:1689: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1702: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1703: warning: implicit declaration of function ‘pcre_study’
pattern.c:1703: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1706: warning: implicit declaration of function ‘pcre_free’
pattern.c:1706: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1709: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_pat’
pattern.c: In function ‘vg_regex_context_free’:
pattern.c:1727: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1728: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1729: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1731: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
pattern.c:1732: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c: In function ‘vg_regex_test’:
pattern.c:1748: error: ‘pcre’ undeclared (first use in this function)
pattern.c:1748: error: ‘re’ undeclared (first use in this function)
pattern.c:1789: warning: implicit declaration of function ‘pcre_exec’
pattern.c:1789: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1790: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1796: error: ‘PCRE_ERROR_NOMATCH’ undeclared (first use in this function)
pattern.c:1804: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1808: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1813: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_pat’
pattern.c:1817: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1818: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1819: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1826: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1826: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1827: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1828: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_extra’
pattern.c:1829: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_pat’
pattern.c:1829: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex_pat’
pattern.c: In function ‘vg_regex_context_new’:
pattern.c:1856: error: ‘vg_regex_context_t’ has no member named ‘vcr_regex’
pattern.c:1857: error: ‘vg_regex_context_t’ has no member named ‘vcr_nalloc’
make: *** [pattern.o] Error 1
"pattern.c:32:18: error: pcre.h: No such file or directory" I think that is the part that matters. Try using brew to 'brew install pcre' and then go again http://mxcl.github.com/homebrew/ |
|
|
|
Ok thanks, got my iOS 5 jailbroken and believe I have found the issue.
I'm looking forward to the fix. I had been wanting to send some coins the last few days and using my phone is by far the easiest way; I missed it. EDIT: and the security doc looks good. I wasn't expecting the site to be running on 3 mac minis. Just 1 small thing, "CSFR" should be "CSRF" |
|
|
|
Something I have thought about doing for a long time. Subscribe.
 I still think an address namespace in namecoin (or something similar) is a better long term solution than vanity addresses, but they are fun for now. Is there some way to charge based on how long the key took to find? Like what if you set the price equal to whatever you would made mining BTC? |
|
|
|
In the past 24 hours Deepbit has found 18 blocks at 3177 GH/s, giving them a value of ⊅0.28328612 per gigahash.
In the past 24 hours P2Pool has found 5 blocks at 229 GH/s, giving them a value of ⊅1.09170305 per gigahash. Awesome sumarization! I absolutly agree! P2pool rules!  Thanks check_status! Given 100% luck, what would the BTC per gigahash be? What about stats for the last 7, or 30, or 90 days? |
|
|
|
So I'm running the latest git, but it still says .76. Shouldn't it be .77? It's also always sitting at 98% CPU and being really unresponsive  It looks like you have a check to google.com to see if the network is up. Problem is, all my connections on this test system are proxied through Tor and sometimes google blocks Tor exit nodes so I get a socket timeout from line 729 of ArmoryQt.py in setupNetworking Side note: The blockchain loaded in 90 seconds. Outside of a VM (on the host) it loads in about 60. To run from git, you need to switch to the "tablesortingfix" branch. I will merge the code into master once I'm ready to "release" it. And yes, I know it's slowing down. The acceleration of blockchain size has me scrambling to get some major things updated sooner rather than later. Unfortunately, I'm just not there yet. :-/ Oh okay. I'll switch branches and test it out. As for "google.com", I also check microsoft.com ... I don't suppose that helps? I figured that was a reliable way to determine if you have a connection to the outside world, but I guess it isn't. Recommendations?
Is there any use case for having internet but no connection to bitcoind? If not, how about this pseudo-code: if bitcoind_available():
if bitcoind_rpc('getconnectioncount'):
echo 'online mode'
else:
echo 'Satoshi found, but it has no connections. Falling back to offline mode.'
else:
echo 'offline mode'
I think this would work and should be easy enough to implement. |
|
|
|
So I'm running the latest git, but it still says .76. Shouldn't it be .77? It's also always sitting at 98% CPU and being really unresponsive It looks like you have a check to google.com to see if the network is up. Problem is, all my connections on this test system are proxied through Tor and sometimes google blocks Tor exit nodes so I get a socket timeout from line 729 of ArmoryQt.py in setupNetworking Side note: The blockchain loaded in 90 seconds. Outside of a VM (on the host) it loads in about 60. |
|
|
|
|
Pleasure doing business with you!
|
|
|
|
the way it works, is you buy it for some one else (and i provide an email address for you to buy it for), for 8$
Oh I see now. They have a gift option. PM me your email address and I'll PM you a bitcoin address |
|
|
|
That is realistic. I've been pointing 1/2 of my power at p2pool. I get between .9 and 1.2btc per block. I was one of the top 10 miners. I should be able to get between 4 and 5 btc per day. Lately it's been about 2, 3 on a really good day.
Um... if you expect 4 to 5 and you instead get 2 to 3, that isn't a 3 times difference. I also think that day to day luck is too variable. Look at least at the last week's luck. Look at the last 90 days: http://p2pool.info/88.2%. M Exactly. 88% is not 33%. Would be nice if p2pool was closer to 100% though. You also have to reduce intensity to run your miners efficiently on p2pool, so that is another couple % of revenue lost |
|
|
|
I tried to run 5 5870 with BAMT,but after couple minutes,OS would crashed(mouse doesn't move,keyboard doesn't work,stop mining,no network),anybody has any ideas?
Post your config. Are you overclocking? If so, reduce your clocks. |
|
|
|
|
So this "swiss" pharmacy doesn't actually ship to Switzerland? lol
|
|
|
|
|
Show Posts
