Package Exports
- erc-payable-token/test/introspection/SupportsInterface.behavior
 - erc-payable-token/test/introspection/SupportsInterface.behavior.js
 
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (erc-payable-token) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
ERC-1363 Payable Token
ERC-1363 is an extension interface for ERC-20 tokens that supports executing code on a recipient contract after transfer or transferFrom, or code on a spender contract after approve, in a single transaction.
There is no way to execute code on a receiver/spender contract after ERC-20 transfers or approvals so, to perform an action, it is required to send another transaction. This introduces complexity in UI development and friction on adoption as users must wait for the first transaction to be executed and then submit the second one. They must also pay GAS twice.
ERC-1363 makes tokens capable of performing actions more easily and working without the use of any off-chain listener. It allows to make a callback on receiver/spender contracts, after transfers or approvals, in a single transaction.
The following are functions and callbacks introduced by ERC-1363:
transferAndCallandtransferFromAndCallwill call anonTransferReceivedon aERC1363Receivercontract.approveAndCallwill call anonApprovalReceivedon aERC1363Spendercontract.
ERC-1363 tokens can be used for specific utilities in all cases that require a callback to be executed after a transfer or an approval received. ERC-1363 is also useful for avoiding token loss or token locking in contracts by verifying the recipient contract's ability to handle tokens.
[!IMPORTANT] This repo contains the reference implementation of the official ERC-1363.
Install
npm install erc-payable-tokenUsage
pragma solidity ^0.8.20;
import "erc-payable-token/contracts/token/ERC1363/ERC1363.sol";
contract MyToken is ERC1363 {
    constructor(string memory name, string memory symbol) ERC20(name, symbol) {
        // your stuff
    }
  // your stuff
}Code
IERC1363
Interface of the ERC-1363 standard as defined in the ERC-1363.
interface IERC1363 is IERC20, IERC165 {
    function transferAndCall(address to, uint256 value) external returns (bool);
    function transferAndCall(address to, uint256 value, bytes calldata data) external returns (bool);
    function transferFromAndCall(address from, address to, uint256 value) external returns (bool);
    function transferFromAndCall(address from, address to, uint256 value, bytes calldata data) external returns (bool);
    function approveAndCall(address spender, uint256 value) external returns (bool);
    function approveAndCall(address spender, uint256 value, bytes calldata data) external returns (bool);
}IERC1363Receiver
Interface for any contract that wants to support transferAndCall or transferFromAndCall from ERC-1363 token contracts.
interface IERC1363Receiver {
    function onTransferReceived(address spender, address sender, uint256 amount, bytes calldata data) external returns (bytes4);
}IERC1363Spender
Interface for any contract that wants to support approveAndCall from ERC-1363 token contracts.
interface IERC1363Spender {
    function onApprovalReceived(address sender, uint256 amount, bytes calldata data) external returns (bytes4);
}IERC1363Errors
Interface of the ERC-1363 custom errors following the ERC-6093 rationale.
ERC1363
Implementation of the ERC-1363 interface.
The reference implementation of ERC-1363 that extends ERC-20 and adds support for executing code after transfers and approvals on recipient contracts.
[!IMPORTANT]
transferAndCall,transferFromAndCallandapproveAndCallrevert if the recipient/spender is an EOA address.To transfer tokens to an EOA or approve it to spend tokens, use the ERC-20
transfer,transferFromorapprovemethods.
Presets
[!WARNING] The
presetscontracts are ideas and suggestions for using ERC-1363 tokens within your contracts.When inheriting and copying from these contracts, you must include a way to use the received tokens, otherwise they will be stuck into the contract.
Always test your contracts before going live.
ERC1363Guardian
A contract that allows to accept ERC-1363 callbacks after transfers or approvals.
It emits a TokensReceived event to notify the transfer received by the contract.
It also implements a _transferReceived function that must be overridden to make your stuff within your contract after a onTransferReceived.
It emits a TokensApproved event to notify the approval received by the contract.
It also implements a _approvalReceived function that must be overridden to make your stuff within your contract after a onApprovalReceived.
[!TIP] After an
approveAndCallyour contract should use the allowance to do something.For instance, you may choose to transfer the approved amount of tokens into the contract itself and then update internal status.
function _approvalReceived( address token, address owner, uint256 value, bytes calldata data ) internal override { IERC20(token).transferFrom(owner, address(this), value); // update internal status }You must then include a way to use the received tokens, otherwise they will be stuck into the contract.
Examples
[!CAUTION] The
examplescontracts are for testing purpose only. Do not use in production.When copying from these contracts, you must include a way to use the received tokens, otherwise they will be stuck into the contract.
Always test your contracts before going live.
ERC1363Payable
An example contract that allows to test accepting ERC-1363 deposits via transferAndCall, transferFromAndCall and approveAndCall.
Inherits from ERC1363Guardian but requires a IERC1363 address to set as accepted token.
Deposits done using not accepted tokens will revert.
Once a deposit is confirmed, the contract increases the user credit value.
ERC1363MethodCallReceiver
An example contract that allows to test passing methods via abi encoded function call.
It executes the method passed via data. Methods emit a MethodCall event.
Documentation
Code Analysis
Development
Install dependencies
npm installCompile
npm run compileTest
npm testCode Coverage
npm run coverageLinter
Check Solidity files
npm run lint:solCheck JS/TS files
npm run lint:jsFix JS and Solidity files
npm run lint:fixLicense
Code released under the MIT License.