Topic: Whitelist Requests (Want out of here?) - page 60. (Read 474339 times)

Please white list me, I know have been involved with bitcoin for over 2 years, If i know a 7950 can hash at 600+ i know a bit about bitcoin

Thanks

Hello -

Could you please enable access for me please?  I'm >10 posts and >4 hours and I still can't post.

Thanks.

Hello, I would like to be whitelisted as well. I may be new to the forum, but I have been in BTC and LTC mining since early 2012 and I am contributing to data on mining hardware on all fronts. As this is one of the best used forums I would like to be able to post in the mining section.

Thanks for your attention. Howdy!

d0vr: OK
GandalfG: OK
sexcoyote: OK
Kiaya: OK

Whitelisted and welcome to the community!

Hi There - would be great to get whitelisted. I'm a software developer with 12 years experience; MEng Software Engineering, good maths background, decent practical understanding of Bitcoin, Altcoins, Ripple and OT.

Im trading on btc-e and mtgox, interested in alt coin advices and information

also like to try build own mining rig

Whitelist pls.  

help me out of jail please.

hello, really good forum! here at last we can talk about everything on bt, with many users and people espera! I would like to be able to take mining area, because I want to see if I can get me a asic (now I minig with the gpu and fpga 1)! hello and thanks

Hello

I am a long time lurker on this forum. Register here July 29, 2011, 05:47:38 PM   
Even though I don't post till now I feel like a  member of this community.

Finally start posting in order to participate in buy Avalon chips for build my miner https://bitcointalksearch.org/topic/group-buy-avalon-asic-chips-sebastianju-batch-6-ordered-closed-187660 and start help/support the other in their construction https://bitcointalksearch.org/topic/diy-pcb-with-avalon-the-quarter-stick-needs-help-161715

I will be appreciate adding me to the white list.

*Bangs on the gate*

Let me in!!

** BANG BANG BANG ***

I Wantz in!!
Gimme MOAR!!!

Actually, I'm interested in an ASIC chip group buy really...

autonomous42: OK
Kolast: OK
BitKoot: OK
Aedius: OK
SolidG: OK
x86Daddy: OK
Brassguy: OK
AirBreather: OK
penny for your thoughts: OK
mnx: OK
bobfranklin: OK
yeltz: OK
z3r0: OK
buttkinz: OK
iamthekey: OK
lano1106: OK
gradius`: OK
elgeo: OK
seannnyx: OK
jski: OK
Rathjinx: OK
sniper.btcoin: OK


Whitelisted and welcome to the community!

Please let me in whitelist 

I've been mining of the last month now and I'm quickly getting a grasp on how the whole thing works and the economics involved. My partner and I are working on the best mining solutions right now to ensure we break even in a timely fashion. I actually just registered because I have an urgent observation to make in the Slush's pool thread.

Members sometimes complain that rounds net them 1/10000 of what they usually get because of some flaw in slush's decaying shares algorithm. I am very certain that round 17979 is going to be bust for some people because the total round score has not reset in a good 15-20 blocks (the round is just over 4 hours long at this point). I'm not sure yet how often the total score resets but I caught on to this when I noticed my estimated reward drop from a typical .003 or so to .00000001. Some people last time thought it was stratum backing up and not properly reporting shares but it's this danged "hop-proof" mechanic he employs! I've got a thing or two to say about that in general, but I think I may have found the bug. Mark my words, people will be complaining about round 17979.

Edit: And just like that the score reached some unknown critical mass and reset. We'll see about 17979 but I think I may be on to something.

Looks like i posted a whitelist request just on the cusp of the new whitelist request sticky in the newb policy discussion thread. At the request of a mod I'm reposting here.

Hi.  I am hoping to submit some artwork for the contest at https://bitcointalksearch.org/topic/1000-mbtc-remaining-bounty-for-teaser-artworkmedia-200915

Could I be allowed to post in that thread?

Could I be whitelisted, Please? I'd like to make a post in the marketplace forum.

Requesting whitelisting for my account due to the fact that I am running an upcoming alternative cryptocurrency business that features the hottest cryptos right now, specifically YaCoin.

 Please place me on the Whitelist I am trying to find out more information about a group buy.

Thanks

^^^  what he said   

Hi!  I've got a bachelor's degree in computer science with a cognate in economics.

I have been really following along with Bitcoin since November 2012, around the same time I pre-ordered a BFL Jalapeno.

Since then, I've been learning way more than I ever really needed to know about cryptography and statistics.  Though I probably don't need to go this much in-depth, I'll go ahead and freestyle rant about what comes to mind.

Out there in the magical land of the Internet, I have a machine that's running bitcoin-qt.  Right now, this machine is connected to 23 other machines running some software, including 173.242.112.53 to try and help zero-fee transactions make it into blocks found by Eligius.
Side note: Speaking of Eligius, this is the pool I mine on with my stupid NVIDIA GPU at just enough to cover electricity costs at the current exchange rate and difficulty.  The pool has had a stroke of bad luck recently.  I guess that since I ostensibly have to prove that I know more than the average newbie, it makes sense for me tell you that "Eligius has had a stroke of bad luck" simply means that other pools keep finding blocks before Eligius.

At any given moment (and every 10 minutes, on average), one or more of those 23 other machines can send me a packet of data that can be interpreted as a block ("block X"), let's say generated by BTCGuild (nowadays, there's like a 40-45% chance that it was, which would be quite troubling if someone other than eleuthria were running that pool).  When this happens, bitcoin-qt looks at block X and runs through several validation rules:

• Are the transactions valid?
• Are all the hashes correct?
• Does block X's header's hash contain the minimum required number of leading zeroes, as required by the current network difficulty?
• Does block X form the longest valid chain (ties are allowed)?

If the answer is "yes" to all of the above, then my machine tells all of the other machines it's connected to about block X, and they (probably) run the same checks themselves.

At some point, the other mining pools (sticking with my Eligius example for now) hear about this and do the same kinds of checks.  When those checks pass, if block X forms a longer valid chain than what its miners are currently building off of, Eligius will (hopefully) tell all of the connected miners to switch to building off of block X.  After all, most clients aren't expected to accept a block that doesn't form the longest valid chain -- that goes against the rules that people agree to when using Bitcoins.

Sometime between when BTCGuild generates block X and when Eligius hears about it, it's possible that one of the miners connected to Eligius finds another block (block Y) that builds off of the same previous block as block X.  When this happens, Eligius will happily propagate block Y to all of the nodes it's connected to, who will now will see a tie for "longest valid chain", and issue new work to its miners to start building off of block Y.  At this point, the block chain is temporarily "forked".

A "fork" like this isn't the end of the world.  Eligius will eventually hear about block X.  When it does, it (hopefully) doesn't tell all its miners to switch from building off of block Y to building off of block X, as they're both equally viable candidates for "longest valid chain", and there's a cost associated with switching like this.  Suppose that Eligius finds block Z that builds off of block Y before hearing about any blocks that build off of block X (highly unlikely, but possible).  Then, Eligius will propagate block Z out to the network.

Remember, BTCGuild is still trying to build off of block X.  If block Z reaches BTCGuild before they find their own block Z' that builds off of block X, then that forms the new longest valid chain, and they'll be forced to abandon block X.  We would call block X an "orphan".

All of the inputs to transactions that were included as a part of block X are now viable inputs for transactions added to future blocks.  In most cases, if a transaction made it into orphaned block X, it will likely have been seen by enough of the network that a transaction with the same inputs would be rejected, but it does open up the possibility that a future block mined by someone at a later time could contain a transaction with the same inputs and different outputs, which is almost surely going to be embedded into the blockchain.  This is obviously extremely unlikely, but since there is that possibility, it's often recommended to wait until several blocks have built upon the block containing your transaction before going to spend those coins.

I guess that sounded like a conclusion, so I'll stop there.  Can I get out, please?