Plutus v3 docs added #128
Closed
Plutus v3 docs added #128
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
agaffney
reviewed
Oct 10, 2025
| } | ||
| ``` | ||
|
|
||
| - `PlutusV3Script []PlutusData.PlutusV3Script`: This field is a slice of `PlutusV3Script` types. It holds all the Plutus V3 scripts that are required to validate the transaction. These scripts are typically referenced by script hashes within the transaction outputs or inputs. |
There was a problem hiding this comment.
This statement isn't quite true. This can hold V3 scripts that can be used to validate the transaction, but it's far more common for this to be empty and to instead use references to scripts that have been included in the outputs from other TXs
| // ... | ||
| ``` | ||
|
|
||
| This structured approach ensures that all necessary Plutus V3 scripts are correctly bundled with the transaction, enabling successful on-chain validation. |
There was a problem hiding this comment.
As noted above, they usually are not bundled with the transaction that they are validating
|
|
||
| ## Adding Plutus V3 Reference Inputs | ||
|
|
||
| The `AddReferenceInputV3` function is used to add a transaction input as a reference input for Plutus V3 scripts. Reference inputs are a key feature of Plutus V3, allowing scripts to inspect the contents of UTxOs without consuming them. This is particularly useful for on-chain governance, oracle data, or any scenario where a script needs to read state without altering it. |
There was a problem hiding this comment.
This is most often used to add a reference to a V3 script that was added on-chain in a previous TX
| **Parameters:** | ||
|
|
||
| - `stakingCredential []byte`: The staking credential (e.g., stake key hash) to be included in the address. Can be `nil` for base addresses without a staking part. | ||
| - `networkId byte`: The network identifier (e.g., `0x00` for testnet, `0x01` for mainnet). |
There was a problem hiding this comment.
Are there constants for the testnet vs. mainnet networkId values? Magic numbers are generally a bad idea
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Also benchmark tool was removed and moved to another repository https://github.com/MIxAxIM/apollo-testing-suite