Got my BFL Single today and I'm raffling it away for 0.5BTC!

[deepceleron]

Hmm checked the list, and It seems as if I only got half the tickets I purchased.

Those numbers are in BTC, not tickets.

So, how hard and complicated can we make it to figure out a single secure and fair random number between 0 and 20644?

Pretty easy once the future block is specified: http://we.lovebitco.in/lottery.html
You should do the math yourself too, since I now could know my ticket number and craft a devious web page.  

What about the 3 digit numbers?

The last column in my list is credits * 100, the actual number of tickets, necessary because of the fractions from referrals.

[1713988393]

1713988393

[1713988393]

1713988393

[1713988393]

1713988393

[1713988393]

1713988393

[BurtW]

Hmm checked the list, and It seems as if I only got half the tickets I purchased.

It lists number of BTC paid, not number of tickets Thus the x.5s

What about the 3 digit numbers?

What you do is look at the first two columns.  There is a first and a last number.  Those are your numbers.  If the random number falls between your first and your last then you win.  The range of numbers you get is determined by the amount of BTC times 100, so if you spent 5.25 BTC then you get 525 numbers out of the entire range of possible numbers.

[cyberlync]

What the hell was the point in selling raffle tickets then? Oh well, I guess I didn't follow the whole thread. Nevermind, as long as things go as they should

[Jonathan Ryan Owens]

I'm actually coming to the conclusion that our leaderless movement has infected the Raffle.

I have an idea.

@Matthew: print out 209~ tickets, put them in a container, and have a lightly dressed korean girl pull the winning number.

Do this live on ustream.tv or another streaming platform.

[dollartrader]

...have a lightly dressed korean girl pull the winning number.

Do this live on ustream.tv or another streaming platform.

+100 and do the raffle later..

[wogaut]

I'm actually coming to the conclusion that our leaderless movement has infected the Raffle.

I have an idea.

@Matthew: print out 209~ tickets, put them in a container, and have a lightly dressed korean girl pull the winning number.

Do this live on ustream.tv or another streaming platform.

Nope, that would be 20645 (20644 including the "0" number) tickets, otherwise the shares would not be reflected properly in the probability game.

[deepceleron]

I see an error that will require republication of a corrected list by MNW. As alluded to above, BTC amounts are in the list, not ticket amounts (BTC x2). However referrals were likely paid as though tickets=BTC, causing referrals to pay double.

Since the list of "credits" is BTC amounts (not "tickets"), the list of credits should have had one more digit of accuracy, with amounts like 0.525

• Provide your e-mail address to a referral
• When they purchase their raffle credits, they will receive an additional 5% credit for each credit they purchase.
• You will receive an additional 25% credit for each credit purchased through the referral.
  

Referral example:

You purchase 1 credit. You now have 1 raffle credit.
Friend 1 purchases 1 credit through your referral e-mail.
You now have 1.25 raffle credits. Friend 1 now has 1.05 raffle credits.

So with BTC as the amounts, it would have needed three-digit accuracy if done right:
-When you don't use a referral, your 0.5 BTC became 0.5 credits (confirmed from my entry),
-when you use a referral, your 0.5 BTC becomes 0.525 credits (a bonus of 5%, 0.025 credits).
-when you receive a referral, you receive .125 credits.

It looks like the "referral" program gave twice the percentage it should have, since everything in the list is in increments of 0.05.

[wogaut]

I see an error that will require republication of a corrected list by MNW. As alluded to above, BTC amounts are in the list, not ticket amounts (BTC x2). However referrals were likely paid as though BTC=tickets, causing referrals to pay double.

Since the list of "credits" is BTC amounts (not "tickets"), the list of credits should have had one more digit of accuracy, with amounts like 0.525

I was wondering when this would come up  

But instead of having 3 digits, just convert BTC to raffle credits (*2) and keep 2 digits.

... and add the referrals _after_  multiplication of course...

[Jonathan Ryan Owens]

I see an error that will require republication of a corrected list by MNW. As alluded to above, BTC amounts are in the list, not ticket amounts (BTC x2). However referrals were likely paid as though BTC=tickets, causing referrals to pay double.

Since the list of "credits" is BTC amounts (not "tickets"), the list of credits should have had one more digit of accuracy, with amounts like 0.525

• Provide your e-mail address to a referral
• When they purchase their raffle credits, they will receive an additional 5% credit for each credit they purchase.
• You will receive an additional 25% credit for each credit purchased through the referral.
  

Referral example:

You purchase 1 credit. You now have 1 raffle credit.
Friend 1 purchases 1 credit through your referral e-mail.
You now have 1.25 raffle credits. Friend 1 now has 1.05 raffle credits.

So with BTC as the amounts, it would have needed three-digit accuracy if done right:
-When you don't use a referral, your 0.5 BTC became 0.5 credits (confirmed from my entry),
-when you use a referral, your 0.5 BTC becomes 0.525 credits (a bonus of 5%, 0.025 credits).
-when you receive a referral, you receive .125 credits.

It looks like the "referral" program gave twice the percentage it should have, since everything in the list is in increments of 0.05.

[cablepair]

I appreciate the effort by the person who made the list but personally I think it would be unacceptable for anyone to produce a list other than the OP (Matt)

Not that I think anyone would cheat but it surely is not a good idea for a contestant in this raffle to compile the list that is used to determine the winner.

[Joshwaa]

I see an error that will require republication of a corrected list by MNW. As alluded to above, BTC amounts are in the list, not ticket amounts (BTC x2). However referrals were likely paid as though BTC=tickets, causing referrals to pay double.

Since the list of "credits" is BTC amounts (not "tickets"), the list of credits should have had one more digit of accuracy, with amounts like 0.525

• Provide your e-mail address to a referral
• When they purchase their raffle credits, they will receive an additional 5% credit for each credit they purchase.
• You will receive an additional 25% credit for each credit purchased through the referral.
  

Referral example:

You purchase 1 credit. You now have 1 raffle credit.
Friend 1 purchases 1 credit through your referral e-mail.
You now have 1.25 raffle credits. Friend 1 now has 1.05 raffle credits.

So with BTC as the amounts, it would have needed three-digit accuracy if done right:
-When you don't use a referral, your 0.5 BTC became 0.5 credits (confirmed from my entry),
-when you use a referral, your 0.5 BTC becomes 0.525 credits (a bonus of 5%, 0.025 credits).
-when you receive a referral, you receive .125 credits.

It looks like the "referral" program gave twice the percentage it should have, since everything in the list is in increments of 0.05.

One of the best movies ever!!

[deepceleron]

I appreciate the effort by the person who made the list but personally I think it would be unacceptable for anyone to produce a list other than the OP (Matt)

Not that I think anyone would cheat but it surely is not a good idea for a contestant in this raffle to compile the list that is used to determine the winner.

It's pretty easy to look at the ticket number ranges vs credits and see I did the math right (or discover I did it wrong...).

With the error I discovered, Matthew will need to create a new list which will have a different number of total credits - he can turn the credits in to ticket numbers like my example. If the referral calculation was done in error by the way the bitpay was set up and Matthew only got the results from them, it may take a bit of time to fix.

[BurtW]

Now that is more like it!  Things were going a bit too smoothly.

[Phraust]

I haven't checked on this thread in a few days, but had bought a few tickets.

my email is 5a4419d19fbf16aefeda35aaa84833e976c3b454189b46675437d960261b8baa

Hope I didn't miss out.

[cablepair]

I appreciate the effort by the person who made the list but personally I think it would be unacceptable for anyone to produce a list other than the OP (Matt)

Not that I think anyone would cheat but it surely is not a good idea for a contestant in this raffle to compile the list that is used to determine the winner.

It's pretty easy to look at the ticket number ranges vs credits and see I did the math right (or discover I did it wrong...).

With the error I discovered, Matthew will need to create a new list which will have a different number of total credits - he can turn the credits in to ticket numbers like my example. If the referral calculation was done in error by the way the bitpay was set up and Matthew only got the results from them, it may take a bit of time to fix.

I understand the list can be verified by all but I personally don't have the time to check all of theses variables and I don't think it's fair that I should have to , Matt is running the contest - he is responsible - he should provide the list.

[Matthew N. Wright]

I haven't checked on this thread in a few days, but had bought a few tickets.

my email is 5a4419d19fbf16aefeda35aaa84833e976c3b454189b46675437d960261b8baa

Hope I didn't miss out.

I got your PM just now and I was about to respond to you, but I responded in the thread instead. You used a upper-case first letter in your e-mail address (check your invoice) and then when you went to confirm, you used a lower-case email in your own SHA256 hashing.

It is no surprise you didn't find your e-mail address, because it's 8a6b6a6233d1367f5dd28257c7dafdef653bf556f3fa69e7f282aecb076cca3e

[Matthew N. Wright]

Now that is more like it!  Things were going a bit too smoothly.

i no rite?

UPDATE: I realized I was confusing myself about the BTC>Credits thing, almost as much as everyone else was confused about it too.

I'm going back to the original and recalculating. I will repost a proper and less confusing list in a few minutes.,

[Phraust]

I haven't checked on this thread in a few days, but had bought a few tickets.

my email is 5a4419d19fbf16aefeda35aaa84833e976c3b454189b46675437d960261b8baa

Hope I didn't miss out.

I got your PM just now and I was about to respond to you, but I responded in the thread instead. You used a upper-case first letter in your e-mail address (check your invoice) and then when you went to confirm, you used a lower-case email in your own SHA256 hashing.

It is no surprise you didn't find your e-mail address, because it's 8a6b6a6233d1367f5dd28257c7dafdef653bf556f3fa69e7f282aecb076cca3e

Thanks for clearing that up

[Matthew N. Wright]

[Matthew N. Wright]

UPDATE:

Code:

	Referrals	Purchased	Referrer Bonuses	Referral Bonuses	Total Credits
Totals	30		388		7.2			7.5			402.7

The current rate of exchange for raffle credits to tickets has been decided on as

0.1 credit = 1 tickets.

That means that at present, there are 4,027 tickets.


0.01 credit = 1 tickets.

That means that at present, there are 40,270 tickets.

Now comes the fun part--- choosing the winner!