Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update 20230330-interaction-templates-1.1.0.md #228

Merged
merged 3 commits into from
Jan 8, 2024
Merged

Update 20230330-interaction-templates-1.1.0.md #228

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f1efc3f
Update 20230330-interaction-templates-1.1.0.md
JeffreyDoyle Dec 8, 2023
3c4f33c
Update 20230330-interaction-templates-1.1.0.md
bthaile Dec 8, 2023
6e2abbd
Update 20230330-interaction-templates-1.1.0.md
JeffreyDoyle Jan 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions application/20230330-interaction-templates-1.1.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -620,7 +620,7 @@ pub fun main(address: Address): UFix64 {

#### `data.dependencies`

For each dependency of the interaction (each contract that is imported in the cadence of the interaction), there must be network keyed (mainnet || testnet) dependency information. The information for each network should contain the address of the account where the contract is deployed, the fully qualified identifier for the contract, dependency tree pin and block height the pin was preformed at. The dependency tree pin is performed by the following pseudocode:
For each dependency of the interaction (each contract that is imported in the cadence of the interaction), there must be network keyed (mainnet || testnet) dependency information. The information for each network should contain the address of the account where the contract is deployed, dependency pin of the contract, the pin of the contract itself (SHA3-256 hash of itself) and block height the pin was preformed at. The dependency tree pin is performed by the following pseudocode:

```javascript
// Example contracts map
Expand Down Expand Up @@ -858,7 +858,7 @@ template-message-key = Key for a template message (eg: "title", "descr
template-message = [ sha3_256(template-message-key), [ ...template-message-translation ] ]

template-dependency-contract-pin-block-height = Network block height the pin was generated against.
template-dependency-contract-pin = Pin of contract and it's dependency tree
template-dependency-contract-pin = Pin of contract and its dependency tree
template-dependency-contract-pin-self = Pin of the contract itself
template-dependency-network-address = Address of an account
template-dependency-network = "mainnet" | "testnet" | "emulator" | Custom Network Tag
Expand Down