diff --git a/content/03-learn/10-cardano-addresses.mdx b/content/03-learn/10-cardano-addresses.mdx index bcfdc7b0..33698f18 100644 --- a/content/03-learn/10-cardano-addresses.mdx +++ b/content/03-learn/10-cardano-addresses.mdx @@ -14,7 +14,7 @@ Shelley introduces four different types of addresses: Besides those new addresses, Shelley continues to support Byron-era *bootstrap addresses* and *script addresses*, but only the new base and pointer addresses carry stake rights. Therefore, addresses consist of some serialized data specified in the ledger specification stored in the -blockchain’s blocks, e.g., an Unspent Transaction Output (UTXO) address. +blockchain’s blocks, eg, an Unspent Transaction Output (UTXO) address. The serialized data (address) contains two parts: @@ -30,7 +30,7 @@ The stake rights can only be exercised by registering the stake key and delegati ### Pointer addresses -A pointer address indirectly specifies the staking key that should control the stake for the address. It references a stake key by a stake key pointer, which is a location on the blockchain of the stake key [registration certificate](https://docs.cardano.org/getting-started/operating-a-stake-pool/creating-keys-and-certificates#creatinganoperationalcertificate) for that key. Pointer addresses can be used in transactions, even if their target is not an active stake key registration. This covers the scenario where the key was unregistered after (or indeed, before) the transaction, and also covers pointers to targets that are plainly invalid. The reason for allowing such invalid targets is so that nodes only need to track the *currently active* stake keys. +A pointer address indirectly specifies the staking key that should control the stake for the address. It references a stake key by a stake key pointer, which is a location on the blockchain of the stake key registration certificate for that key. Pointer addresses can be used in transactions, even if their target is not an active stake key registration. This covers the scenario where the key was unregistered after (or indeed, before) the transaction, and also covers pointers to targets that are plainly invalid. The reason for allowing such invalid targets is so that nodes only need to track the *currently active* stake keys. The pointer can be considerably shorter than the hash used in base addresses. diff --git a/content/12-smart-contracts/01-plutus/03-plutus-scripts.mdx b/content/12-smart-contracts/01-plutus/03-plutus-scripts.mdx index 69632c24..89e9fbdb 100644 --- a/content/12-smart-contracts/01-plutus/03-plutus-scripts.mdx +++ b/content/12-smart-contracts/01-plutus/03-plutus-scripts.mdx @@ -39,7 +39,7 @@ The data contained in the context is: - [Writing basic minting policies](https://plutus.readthedocs.io/en/latest/tutorials/basic-minting-policies.html) - [How to export scripts, datums, and redeemers](https://plutus.readthedocs.io/en/latest/howtos/exporting-a-script.html) - [How to profile the budget usage of Plutus scripts](https://plutus.readthedocs.io/en/latest/howtos/profiling-scripts.html) -- [Plutus script examples in the Babbage era](https://github.com/input-output-hk/cardano-node/tree/master/doc/reference/plutus) +- [Plutus script examples in the Babbage era](https://github.com/input-output-hk/cardano-node-wiki/tree/main/docs/reference/plutus) - [Plutus Pioneer code examples](https://github.com/input-output-hk/plutus-pioneer-program#code-examples) - [Optimization techniques for Plutus scripts](https://plutus.readthedocs.io/en/latest/reference/writing-scripts/optimization.html) - [Plutus language changes (V1 and V2)](https://plutus.readthedocs.io/en/latest/reference/cardano/language-changes.html) diff --git a/content/15-tools/02-release-notes.mdx b/content/15-tools/02-release-notes.mdx index 553b779a..00887235 100644 --- a/content/15-tools/02-release-notes.mdx +++ b/content/15-tools/02-release-notes.mdx @@ -16,7 +16,7 @@ Name | Version | Release Date [Cardano Node](https://github.com/input-output-hk/cardano-node) | [8.1.2](https://github.com/input-output-hk/cardano-node/releases/tag/8.1.2) | 24 July, 2023 [Cardano RTView](https://github.com/input-output-hk/cardano-rt-view) | [0.3.0](https://github.com/input-output-hk/cardano-rt-view/releases/tag/0.3.0) | 15 January, 2021 [Cardano DB Sync](https://github.com/input-output-hk/cardano-db-sync/releases) | [13.1.0.0](https://github.com/input-output-hk/cardano-db-sync/releases/tag/13.1.0.0) | 20 January, 2023 -[Cardano Rosetta](https://github.com/input-output-hk/cardano-rosetta) | [2.1.0](https://github.com/input-output-hk/cardano-rosetta/releases/tag/2.1.0) | 30 January, 2023 +[Cardano Rosetta](https://github.com/input-output-hk/cardano-rosetta) | [2.1.0](https://github.com/cardano-foundation/cardano-rosetta/releases/tag/2.1.0) | 30 January, 2023 [Cardano GraphQL](https://github.com/input-output-hk/cardano-graphql) | [8.0.0](https://github.com/input-output-hk/cardano-graphql/releases/tag/8.0.0) | 7 February, 2023 [Cardano Explorer](https://github.com/input-output-hk/cardano-explorer-app) | [1.6.0](https://github.com/input-output-hk/cardano-explorer-app/releases/tag/1.6.0) | 27 July, 2021 [Cardano Transactions](https://github.com/input-output-hk/cardano-transactions) | [1.0.0](https://github.com/input-output-hk/cardano-transactions/releases/tag/1.0.0) | 21 April, 2020