Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
12 changes: 9 additions & 3 deletions docs.json
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,12 @@
},
"favicon": "/favicon.png",
"api": {
"baseUrl": "https://mainnet.mirrornode.hedera.com"
"baseUrl": "https://mainnet.mirrornode.hedera.com",
"openapi": [
"openapi.yaml",
"hedera-status-api.yaml",
"smart-contract-verification-api.yaml"
]
},
"appearance": {
"default": "light"
Expand All @@ -38,12 +43,13 @@
"options": [
"copy",
"view",
"chatgpt",
"vscode",
"claude",
"chatgpt",
"perplexity",
"mcp",
"cursor",
"vscode"
"download-spec"
]
},
"markdown": {
Expand Down
4 changes: 2 additions & 2 deletions evm/differences/native-devs/ed25519-integration.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ function verifyED25519Signature(
bytes32 messageHash,
bytes memory signatureBlob
) public returns (bool) {
(bool success, ) = address(0x167).call(
(bool success, ) = address(0x16a).call(
abi.encodeWithSignature(
"isAuthorizedRaw(address,bytes32,bytes)",
accountAlias,
Expand Down Expand Up @@ -77,7 +77,7 @@ This example demonstrates requiring multiple valid signatures for critical contr

```solidity
function validateMultiSig(address accountAlias, bytes memory proposalData, bytes memory signatureBlob) public returns (bool) {
(bool success, ) = address(0x167).call(
(bool success, ) = address(0x16a).call(
abi.encodeWithSignature("isAuthorized(address,bytes,bytes)", accountAlias, proposalData, signatureBlob)
);
return success;
Expand Down
2 changes: 1 addition & 1 deletion evm/tokens/erc721.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ description: "Use the ERC-721 non-fungible token standard on Hedera, including s
The [ERC-721](https://ethereum.org/en/developers/docs/standards/tokens/erc-721/) standard introduces a [non-fungible token (NFT)](/support/glossary#non-fungible-token-nft) in which each issued token is unique and distinct from others. This standard defines functions and events that enable the creation, ownership, and transfer of non-fungible assets.

<Info>
**Note**:`ERC-721` Token addresses refer to full Hedera Token Service (HTS) fungible token entities. These tokens can be fully managed by HTS API calls. Additionally, by utilizing [`IERC721`](https://docs.openzeppelin.com/contracts/2.x/api/token/erc721#IERC721) interfaces or system contract functions, these tokens can also be managed by smart contracts on Hedera.
**Note**:`ERC-721` Token addresses refer to full Hedera Token Service (HTS) non-fungible token (NFT) entities. These tokens can be fully managed by HTS API calls. Additionally, by utilizing [`IERC721`](https://docs.openzeppelin.com/contracts/2.x/api/token/erc721#IERC721) interfaces or system contract functions, these tokens can also be managed by smart contracts on Hedera.
</Info>

## Supported Functions
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ This creates a new directory with a standard Foundry project structure, includin

#### Install Dependencies

Foundry uses git submodules to manage dependencies. We'll install the OpenZeppelin Contracts library, which provides a standard and secure implementation of the ERC20 token.
Foundry uses git submodules to manage dependencies. We'll install the OpenZeppelin Contracts library, which provides a standard and secure implementation of the ERC-721 token.

```bash
forge install OpenZeppelin/openzeppelin-contracts
Expand Down
2 changes: 1 addition & 1 deletion native/files/errors.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Network response messages and their descriptions.
| Network Response | Description |
| --------------------------------------- | ------------------------------------------------------------------------ |
| `FEE_SCHEDULE_FILE_PART_UPLOADED` | Fee Schedule Proto File Part uploaded |
| `FILE_CONTENT_EMPT` | The contents of file are provided as empty. |
| `FILE_CONTENT_EMPTY` | The contents of file are provided as empty. |
| `FILE_DELETED` | the file has been marked as deleted |
| `FILE_SYSTEM_EXCEPTION` | Unexpected exception thrown by file system functions |
| `FILE_UPLOADED_PROTO_INVALID` | Fee Schedule Proto uploaded but not valid (append or update is required) |
Expand Down
Loading