mirror of https://github.com/status-im/EIPs.git
Update eip-681.md
[ERC] default chain_id behavior changed for backwards compatibility.
This commit is contained in:
parent
4eca54f289
commit
b5444e4c94
|
@ -56,7 +56,7 @@ For the syntax of ENS_NAME, please consult ERC #137 defining Ethereum Name Servi
|
|||
|
||||
`target_address` is mandatory and denotes either the beneficiary of native token payment (see below) or the contract address with which the user is asked to interact.
|
||||
|
||||
`chain_id` is optional and contains the decimal chain ID, such that transactions on various test- and private networks can be requested. If no `chain_id` is present, the main network (1) is assumed.
|
||||
`chain_id` is optional and contains the decimal chain ID, such that transactions on various test- and private networks can be requested. If no `chain_id` is present, the client's current network setting remains effective.
|
||||
|
||||
If `function_name` is missing, then the URL is requesting payment in the native token of the blockchain, which is Ether in our case. The amount is specified in `value` parameter, in the atomic unit (i.e. Wei). The use of scientific notation is strongly encouraged. For example, requesting 2.014 ETH to address `0xfb6916095ca1df60bb79Ce92ce3ea74c37c5d359` would look as follows:
|
||||
[ethereum:0xfb6916095ca1df60bb79Ce92ce3ea74c37c5d359?value=2.014e18](ethereum:0xfb6916095ca1df60bb79Ce92ce3ea74c37c5d359?value=2.014e18)
|
||||
|
|
Loading…
Reference in New Issue