user5602: In the second transaction of the auction example, these are the output EUTxO's. In the final transaction, only wallet 1 and the script are inputs. How does the script know that wallet 3 has done the highest bid? I would expect that the script also stores 'wallet 3' as data, so it's known who had done the bid.
Or, in the closing Tx, how does the script know that wallet 3 did the bid (from the playground, this doesn't seem to be stored.)


user6089: Each change in state in the auction contract passes a new datum (arbitrary data). The auction datum is made up of the 'Auction' and 'Bid' records. The bid record has a 'bBidder' field which is the public key of the bidder. You can't see this in the playground because the actual datum value isn't stored on-chain, the hash is which allows others to validate. When a validator (or the simulator) calculates the highest bidder, it does it from the start based off the series of eUXTOs'.
As to how does the auction example know who started the bid? When a new eUXTO is added to the series of bids, the validator calculates the previous bids up to the current one, in order to discover the datum. This datum is then used in the contract script again to place the next bid.
The reason this can be done is because the result is entirely deterministic. Based off the same inputs (transactions in/endpoints), you'll get the same output.

5602: <p>In the second transaction of the auction example, these are the output EUTxO's. In the final transaction, only wallet 1 and the script are inputs. How does the script know that wallet 3 has done the highest bid? I would expect that the script also stores 'wallet 3' as data, so it's known who had done the bid.
Or, in the closing Tx, how does the script know that wallet 3 did the bid (from the playground, this doesn't seem to be stored.)</p>
<p><a href="https://i.stack.imgur.com/XIHpF.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/XIHpF.png" alt="output of 2nd transaction in the auction example" /></a></p>
 6089: <p>Each change in state in the auction contract passes a new datum (arbitrary data). The auction datum is made up of the 'Auction' and 'Bid' records. The bid record has a 'bBidder' field which is the public key of the bidder. You can't see this in the playground because the actual datum value isn't stored on-chain, the hash is which allows others to validate. When a validator (or the simulator) calculates the highest bidder, it does it from the start based off the series of eUXTOs'.</p>
<p>As to how does the auction example know who started the bid? When a new eUXTO is added to the series of bids, the validator calculates the previous bids up to the current one, in order to discover the datum. This datum is then used in the contract script again to place the next bid.</p>
<p>The reason this can be done is because the result is entirely deterministic. Based off the same inputs (transactions in/endpoints), you'll get the same output.</p>
