Add EIP: On-Chain Function Return Type Encoding #19289
Annotations
10 errors
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L59
error[markdown-order-section]: body has extra section(s)
--> EIPS/eip-7899.md
|
59 | ## ELI5: The Mystery Pump Dispensers
|
= help: see https://ethereum.github.io/eipw/markdown-order-section/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L158
error[markdown-order-section]: section `Reference Implementation` is out of order
--> EIPS/eip-7899.md
|
158 | ## Reference Implementation
|
= help: `Reference Implementation` should come after `Test Cases`
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L24
error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC`
--> EIPS/eip-7899.md
|
24 | Currently, Solidity does not provide a standardized on-chain method for discovering the return types of a function without source co...
|
= help: see https://ethereum.github.io/eipw/markdown-refs/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L42
error[markdown-refs]: references to proposals with a `category` of `ERC` must use a prefix of `ERC`
--> EIPS/eip-7899.md
|
42 | A function’s return type **MUST** be encoded as a `bytes32` word, where each byte represents a type token. The first `N` bytes (st...
|
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L10
error[preamble-date-created]: preamble header `created` is not a date in the `YYYY-MM-DD` format
--> EIPS/eip-7899.md:10:9
|
10 | created: <2025-03-01>
| ^^^^^^^^^^^^^ input contains invalid characters
|
= help: see https://ethereum.github.io/eipw/preamble-date-created/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L9
error[preamble-enum-category]: preamble header `category` has an unrecognized value
--> EIPS/eip-7899.md:9:10
|
9 | category: <ERC>
| ^^^^^^^ must be one of: `Core`, `Networking`, `Interface`
|
= help: see https://ethereum.github.io/eipw/preamble-enum-category/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L8
error[preamble-enum-type]: preamble header `type` has an unrecognized value
--> EIPS/eip-7899.md:8:6
|
8 | type: <Standards Track>
| ^^^^^^^^^^^^^^^^^^ must be one of: `Standards Track`, `Meta`, `Informational`
|
= help: see https://ethereum.github.io/eipw/preamble-enum-type/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L4
error[preamble-len-description]: preamble header `description` value is too long (max 140)
--> EIPS/eip-7899.md:4:13
|
4 | ...on: This EIP standardizes on-chain return type encoding, removing off-chain ABI dependencies and improving interoperability between smart contracts. It is efficient, flexible, and fully algorithmic, making it ideal for dynamic cross-contract interactions.
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ too long
|
= help: see https://ethereum.github.io/eipw/preamble-len-description/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L3
error[preamble-len-title]: preamble header `title` value is too long (max 44)
--> EIPS/eip-7899.md:3:7
|
3 | title: On-Chain Function Return Type Encoding for Solidity Functions
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ too long
|
= help: see https://ethereum.github.io/eipw/preamble-len-title/
|
|
Run ethereum/eipw-action@be3fa642ec311d0b8e1fdb811e5c9b4ada3d3d93:
EIPS/eip-7899.md#L4
error[preamble-re-description]: preamble header `description` should not contain `standard` (or similar words.)
--> EIPS/eip-7899.md:4:13
|
4 | ...on: This EIP standardizes on-chain return type encoding, removing off-chain ABI dependencies and improving interoperability between smart contracts. It is efficient, flexible, and fully algorithmic, making it ideal for dynamic cross-contract interactions.
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ prohibited pattern was matched
|
= info: the pattern in question: `(?i)standar\w*\b`
= help: see https://ethereum.github.io/eipw/preamble-re-description/
|
Loading