You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
If a table row for that symbol already exists for the owner, then the open action would do nothing. Otherwise, it will create a zero-balance table row for that symbol and charge the RAM to ram_payer.
This action allows contracts or wallet clients to easily replicate the current behavior of eosio.token::transfer even after its behavior is modified (see #62). The current behavior is that the token transfer action succeeds (assuming the sender and recipient contracts that are notified do not fail) even if there is no existing row for that symbol in the recipient's table. Contracts and wallet clients can simply package the two actions (eosio.token::open action followed by the eosio.token::transfer action) and get the same behavior they are used to at the risk of having to pay for the RAM if the recipient's tables need a new table row.
The text was updated successfully, but these errors were encountered:
An
open
action is needed to complement the existingclose
action in the eosio.token contract.Action signature:
If a table row for that symbol already exists for the
owner
, then theopen
action would do nothing. Otherwise, it will create a zero-balance table row for that symbol and charge the RAM toram_payer
.This action allows contracts or wallet clients to easily replicate the current behavior of
eosio.token::transfer
even after its behavior is modified (see #62). The current behavior is that the token transfer action succeeds (assuming the sender and recipient contracts that are notified do not fail) even if there is no existing row for that symbol in the recipient's table. Contracts and wallet clients can simply package the two actions (eosio.token::open
action followed by theeosio.token::transfer
action) and get the same behavior they are used to at the risk of having to pay for the RAM if the recipient's tables need a new table row.The text was updated successfully, but these errors were encountered: