You are viewing a single comment's thread:
The way you tie the seed too the last two blocks plus a tx id is brilliant. As a numbers guy that really clicks for me, its audit friendly and and easy to reproduce later. The flow feels clean and simple all around. Cant wait too see where you take this :)
But wait , it can't right?
Because the txid is chosen randomly each time?
@thecrazygm
if you use the same sha256 seed that it renders, like the one in the image it will get the same result. In a real use case I would think the tx_id would be static because it would be using the tx of the custom_json it was called in.
You are right though, if you call it with just the block info it would call a new random tx,
For provable purposes, i would log the 3 ids it used and the sha256 to compare against later (which is what the thing I'm playing with now does, adds the actual seed to the database for comparison checks ).
View more
Originally I had it using the first transaction for the roll. But if 2 people roll at the same they would get the same results, which is why I moved to random TX in block.
View more