Skip to main content

EXPERIMENTAL_changes-{contract_code_changes} RPC Method

Returns the code changes that were made when deploying a contract. The change is a base64 encoded WASM file.

Updated on
Oct 4, 2023

EXPERIMENTAL_changes-{contract_code_changes} RPC Method

Parameters

changes_type
string
The type of changes
account_ids
array
An array of account ids
finality
string
The assurance that the transaction cannot be altered, reversed, or canceled after they are completed. For finality=final, it means that it has been validated on at least 66% of the nodes in the network and for finality=optimistic, it uses the latest block recorded on the node that responded to the query passed
block_id
integer/string
The block id, it could be either block number or block hash

Returns

block_hash
The hash of the block this transaction was associated with
changes
An array of changes that occurred in the account during the transaction
cause
The reason behind the account changes
type
The change causing factor in an account. It could be transaction_processing or receipt_processing
tx_hash/receipt_hash
There can be two values returned dependent on the change-causing factor. For transaction_processing, the returned value is tx_hash, which represents the hash of the transaction. For receipt_processing, the returned value is receipt_hash, which represents the hash of the receipt.
type
The type of changes occurred in the account
change
The changes occurred in the account during the transaction
account_id
The identifier for the account
code_base64
The code changes encoded in base64
Request
1
curl https://docs-demo.near-mainnet.quiknode.pro/ \
2
--request POST \
3
--header "Content-Type: application/json" \
4
--data '{"method": "EXPERIMENTAL_changes","params": {"changes_type": "contract_code_changes", "account_ids": ["prophet.poolv1.near", "kiln.poolv1.near"], "block_id": 80712125},"id":1,"jsonrpc":"2.0"}'
Don't have an account yet?
Create your QuickNode endpoint in seconds and start building
Get started for free