<p>Yes, that's right. The parameter values you provide gets set in the validator resulting in different script CBORs for different values. Script address is derived from the hash of a script's CBOR.</p>
<p>Different Script CBOR -&gt; Different Script Hash -&gt; Different Script Address.</p>

CC BY-SA 4.0
2024-12-02T16:28:24.453Z
2024-12-02T16:28:24.453Z
Nikhil Shetty
<p>Re <a href="https://plutus.cardano.intersectmbo.org/docs/auction-smart-contract/on-chain-code" rel="nofollow noreferrer">https://plutus.cardano.intersectmbo.org/docs/auction-smart-contract/on-chain-code</a></p>
<blockquote>
<p>Note that AuctionParams is not an argument of the compiled validator. AuctionParams contains contract properties that don't change, so it is simply built into the validator by partial application.</p>
</blockquote>
<p>This means that if I create multiple auctions with different parameters, each will have a different script address, correct?</p>

<plutus-pioneer-program>
Do the validator params become part of the validator code, and are therefore included in the script address?
# Do the validator params become part of the validator code, and are therefore included in the script address?

(Asked by: username_0 on 2024-10-08)

Re <https://plutus.cardano.intersectmbo.org/docs/auction-smart-contract/on-chain-code>

> Note that AuctionParams is not an argument of the compiled validator. AuctionParams contains contract properties that don't change, so it is simply built into the validator by partial application.

This means that if I create multiple auctions with different parameters, each will have a different script address, correct?

**Tags:** plutus-pioneer-program

---

## 1 answers

### Answer by username_1 on 2024-12-02. Score: 1

Yes, that's right. The parameter values you provide gets set in the validator resulting in different script CBORs for different values. Script address is derived from the hash of a script's CBOR.

Different Script CBOR -> Different Script Hash -> Different Script Address.


---

