Skip to content

Update EIP-6466: clarify contract_address field presence in receipt types #10781

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update EIP-6466: clarify contract_address field presence in receipt types #10781

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 EIPS/eip-6466.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ Receipts are constructed as follows.
| - | - |
| `from` | The transaction sender's address |
| `gas_used` | How much gas this individual transaction used. Replaces `cumulative_gas_used` |
| `contract_address` | For transactions deploying a contract, the new contract address |
| `contract_address` | For transactions deploying a contract, the new contract address. Present only in `CreateReceipt` |
| `logs` | Logs emitted during transaction execution |
| `status` | [EIP-658](./eip-658.md) transaction status code |
| `authorities` | For transactions with an authorization list, the list of [EIP-7702](./eip-7702.md) `authority` addresses. Non-successful authorizations are represented with an all-zero address |
Expand Down Expand Up @@ -164,7 +164,7 @@ Within `logs`, the `logIndex` field is changed to indicate the log index positio

The `logsBloom` field is no longer returned for new receipts. It continues to be returned for historical receipts conforming to earlier schemes.

`from`, `gasUsed`, and `contractAddress` are already provided via JSON-RPC and are left unchanged.
`from`, `gasUsed`, and `contractAddress` are already provided via JSON-RPC and are left unchanged. For `BasicReceipt` and `SetCodeReceipt`, `contractAddress` will be `null` as these receipt types do not contain the `contract_address` field.

### Consensus `ExecutionPayload` changes

Expand Down
Loading