Bitcoin Forum
May 10, 2024, 11:00:13 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 [7]  All
  Print  
Author Topic: [FREE RAFFLE] - Custom eXch Cryptosteel Capsule (#1)!  (Read 1511 times)
joker_josue
Legendary
*
Offline Offline

Activity: 1652
Merit: 4564


**In BTC since 2013**


View Profile WWW
March 09, 2024, 11:50:51 AM
 #121

Congratulations to the winner @aliveNFT

It was good for everyone to participate, come to the next round.  Wink

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
MoparMiningLLC
aka Stryfe
Legendary
*
Online Online

Activity: 2072
Merit: 2224


EIN: 82-3893490


View Profile WWW
March 09, 2024, 02:14:13 PM
 #122

oh for sure - I get it and the math is easy to calculate. I personally would still prefer keeping it simple and using only the block hash on its own - if no winner, then next block. Seems more fair and more simple to me.

I'm not sure that the simpler way is "if no winner, then next block." if no winner again, then next block... I have seen similar raffles where several blocks were needed.
bitmover's tool is also provably fair

It's probably a matter of habit, you've been used to using one method for years.

no it isnt that at all - it is as I stated, I want, when I do a raffle myself, the winning number to be the actual number the contestants chose, not some number that gets calculated using the block hash.

That is basically the same.

Instead of waiting for the next block, you get the last 6 digits of that block hash, and use the module operator of the total number of participants to get the division remainder .

The modulo.opertator is very simple
For example

Code:
13%5=3

The division remainder (3) is then used to choose the winner.  As the division remainder can never be greater than the number of participants.

Very simple math that works.

It isn't a mysterious and complex calculation



but if someone picks 32 and the block ends in 32 - they are not the winner - so no it is not the same thing at all. The amount of participants and the other 4 digits can change it.

This is no where near the same thing. This does solve waiting for a next block but it does not let people actually choose what number they want to be their "winning" number.

and because no one knows how many participants there will actually be (if not waiting for it to fully fill - but if did wait for it to fill, then could just still use the block hash as it is) and they are not getting to select the other 4 numbers - it does create a mystery as to who will win.

My philosophy - keep it simple. let them choose a very specific value and that value - alone and without other calculations - determines whether they win or not.

this process just basically eliminates the need for waiting for a second block incase of no winner.

I can also see it beneficial where a block is set at the very start and raffle tickets are given in the order of people joining the raffle and the number is simply assigned to them.  

Mine BTC @ kano.is
Offering escrow services https://bitcointalk.org/index.php?topic=5154480
All Bitcoin 3D printing needs at CryptoCloaks
Pages: « 1 2 3 4 5 6 [7]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!