Bitcoin Forum
May 13, 2024, 09:24:05 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 [28] 29 30 31 32 33 34 35 36 37 »
541  Economy / Investor-based games / Re: 1.7 X Your Entry [OPEN] on: July 18, 2011, 12:19:59 PM
Took a peek at blockexplorer and the site after the last payment popped up in my wallet. All good for me, but it looks like you missed the 1.2 that 1JVhf... entered before the first 0.5 deposit.
542  Economy / Investor-based games / Re: 1.7 X your entry starts..now! on: July 18, 2011, 02:15:27 AM
Bitcoin likes to mix things up. Like the way the transaction you sent being split into two parts, with some bitcoins sent back to your own wallet...

...these games usually bring out some questions about things like that. Smiley
543  Economy / Investor-based games / Re: 1.7 X your entry starts..now! on: July 18, 2011, 01:29:54 AM
Any "from" address for a transaction would work for sending payments back to the sender's wallet, and senders can't choose what inputs to use, so... I have no idea what kind of "known" address you are looking for.
544  Economy / Investor-based games / Re: 1.7 X your entry starts..now! on: July 18, 2011, 01:04:05 AM
I really should stop reading the gambling forum. But I'm not broke yet, so what the heck... Tongue
545  Economy / Investor-based games / Re: Bitcoin Pyramid [alpha-stage, 0.01 btc for first newcomers!] on: July 17, 2011, 04:43:37 PM
With that explanation I think it works well enough as it is. Smiley
546  Economy / Collectibles / Re: 1 gram .999 fine silver "bitcoin" rounds . Available 6 - 8 weeks on: July 17, 2011, 04:04:31 PM
It would make a nice conversation piece in the future, when a bitcoin buys you a ten kilo bar of silver. A bit like having a slice of the 10000BTC pizza, maybe... Cheesy
547  Economy / Services / Re: Spotify Premium Accounts [Spotify Invites] on: July 17, 2011, 03:41:42 PM
But not anyone can pay for it in bitcoins.

I find this to be a good idea, but maybe it should be clearer in the title that this is a giftcard buying service..? Smiley
548  Economy / Investor-based games / Re: Bitcoin Pyramid [alpha-stage, 0.01 btc for first newcomers!] on: July 17, 2011, 03:15:48 PM
How about something to encourage deposits? Maybe a limit on random payments where the user gets to keep the amount equal to his deposit plus 50%, and the remainder is paid to the sponsor.
549  Economy / Marketplace / Re: Bitcoin Randomizer, just a stupid pyramid scheme on: July 17, 2011, 02:19:35 PM
Still would like this to come back to life. I think many would be interested in a more detailed report of what happened, or at least some sign that this thread is being read by BitLex.

(And no, I'm not going to spam my referral link for the new pyramid. You have to look in my signature for that...  Grin)
550  Economy / Collectibles / Re: 1 gram .999 fine silver "bitcoin" rounds . Available 6 - 8 weeks on: July 17, 2011, 01:52:58 PM
How about selling a special initial run for bitcoin paying buyers only, with a numbered certificate or similar for added customer value (and potential future collector's value)?
551  Bitcoin / Pools / Re: [445 GH/s] Eligius pool: ~0Fee SMPPS, no reg, RollNtime, SQL, hop OK, 8decimals on: July 17, 2011, 12:21:14 PM
To make it even clearer: Are the "Paid in this block" BTC really paid in "this" block and if so, how? And if not, how then and why? Smiley

I think "rewarded in this block" would be more accurate, since the part that exceeds 50BTC may not be paid out in the same block even if the user is over the threshold. But they are guaranteed rewards, and will be paid out later.

It seems that when the pool has funds it pays out the whole 50BTC income to miners in later blocks, and instead adjusts the "server funds" by internally moving bitcoins from the "outstanding rewards" pile. In short blocks, that would mean that miners still get paid the whole block income even if the table says "paid in this block: 10BTC". So, "rewarded" would work better there as well.
552  Economy / Investor-based games / Re: Bitcoin Pyramid [alpha-stage, 0.01 btc for first newcomers!] on: July 16, 2011, 04:24:32 PM
I agree that a higher threshold for withdrawals is a good idea. Too many small transactions can make it expensive to get the bitcoins out of the wallet again.

You could keep the internal threshold lower, though, so that people can enjoy watching the decimals add up until it reaches the withdrawal threshold. Smiley
553  Economy / Investor-based games / Re: Bitcoin Pyramid [alpha-stage, 0.01 btc for first newcomers!] on: July 16, 2011, 03:36:32 PM
Your threshold seems to need some fixing. Just got a 0.0045 payment to sent to me.

In other news: Yay! I got random milli-btc from the pyramid! Wink
554  Economy / Investor-based games / Re: Bitcoin Pyramid [alpha-stage, 0.01 btc for first newcomers!] on: July 16, 2011, 03:00:18 PM
Ah... the unlimited hierarchy is so unlimited that I failed to grasp it.

(I get stupid when I haven't slept for 30 hours. I should ask a medical professional why that happens. Grin)
555  Bitcoin / Pools / Re: [445 GH/s] Eligius pool: ~0Fee SMPPS, no reg, RollNtime, SQL, hop OK, 8decimals on: July 16, 2011, 01:23:30 PM
Blocks are 50BTC, but with the PPS system rounds can have higher rewards since the pool pays for the shares with coins it kept after short rounds. But automatic payments are still limited by the 50BTC that fit into generation, so after rounds where the value of shares exceeds that limit the pool has to queue the payments and fit them into future blocks.

The sendmany transactions were only for paying balances from the closed pools, so until there's a solution that takes cares of backlogs in a better way I think it would be appropriate to update the information about payments... at least as a precaution against the kind of people who feel they have to tediously express their opinions when they have to wait for something...  Tongue
556  Bitcoin / Pools / Re: [360 GH/s] Eligius pool: ~0Fee SMPPS, no reg, RollNtime, SQL, hop OK, 8decimals on: July 16, 2011, 10:42:01 AM
In addition, the Linux networking stack has been randomly choosing machines it doesn't allow to connect--  we get the SYN packet fine, but Linux silently discards it without passing it to pushpoold.
Turns out this is a known issue when net.ipv4.tcp_tw_recycle and NAT are combined. I have disabled it on the pool server, so it should be resolved now. Much thanks to mobiusl and everyone else who helped troubleshoot!

Are the NAT issues something that explains why I had connection problems when I was connected over VPN (which I assume uses NAT rather than giving everyone a unique IP at the exit), or is it just something related to the server/hosting setup?
It could be. The problem as I understand it, is that your miners are sending relative-to-an-unknown-value timestamps in the packets, and tcp_tw_recycle ignores ones with timestamps going backward in time (or something like that). So minerA and minerB have different relative-timestamps, but the earlier of the two gets ignored because of the later's packets...

Has been running fine since your first post. It was an intermittent problem, though, so I guess it's still too early to be certain if it's something related or just good luck on my side.

Something else... I noticed to pool just finished a 250BTC round, so how about an addition to the stats pages that mentions that payments may take a few rounds when the pool has a backlog to process?
557  Bitcoin / Pools / Re: [360 GH/s] Eligius pool: ~0Fee SMPPS, no reg, RollNtime, SQL, hop OK, 8decimals on: July 15, 2011, 07:58:20 PM
In addition, the Linux networking stack has been randomly choosing machines it doesn't allow to connect--  we get the SYN packet fine, but Linux silently discards it without passing it to pushpoold.
Turns out this is a known issue when net.ipv4.tcp_tw_recycle and NAT are combined. I have disabled it on the pool server, so it should be resolved now. Much thanks to mobiusl and everyone else who helped troubleshoot!

Are the NAT issues something that explains why I had connection problems when I was connected over VPN (which I assume uses NAT rather than giving everyone a unique IP at the exit), or is it just something related to the server/hosting setup?
558  Other / CPU/GPU Bitcoin mining hardware / Re: 6 PCIe slots. Wet dream? on: July 14, 2011, 04:34:48 PM
It does have an extra 6-pin to power the PCI-E slots directly from the GPU, so that should help (but might skew the load balancing if you use a multi-rail PSU)

You could also get risers with supplementary power, so they draw power directly from the PSU.

Or, you could probably build two rigs for the same cost by getting cheaper motherboards and power supplies.
559  Bitcoin / Pools / Re: [360 GH/s] Eligius pool: ~0Fee SMPPS, no reg, RollNtime, SQL, hop OK, 8decimals on: July 14, 2011, 01:26:24 PM
Though with such a low hashrate, is this a good pool for me?  Huh

Depends on your patience. It should take you about 6 days to get to over the threshold and get in line for payment at the current difficulty. But other than that, I think it would work well for you. With large proportional/score based pools there's a number of rounds that last only a few minutes, and with a low hashrate you risk getting only a few or even no shares at all into those rounds.
560  Bitcoin / Pools / Re: [360 GH/s] Eligius pool: ~0Fee SMPPS, no reg, RollNtime, SQL, hop OK, 8decimals on: July 14, 2011, 12:03:11 AM
Speaking of wallets... I've had to -rescan my wallet twice to find generated transactions in the last week. Maybe not directly Eligius related more than the pool being the only source of such transactions, but maybe someone else has encountered the same problem and knows what the cause might be.

First time was with .23 on Windows, but I don't remember if the second one was before or after I updated to .24
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 [28] 29 30 31 32 33 34 35 36 37 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!