Skip to content
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.

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

EIP-2021: Payoutable Token #2021

Merged
merged 12 commits into from
Nov 23, 2019
Merged

EIP-2021: Payoutable Token #2021

merged 12 commits into from
Nov 23, 2019

Conversation

daniel-iobuilders
Copy link
Contributor

@daniel-iobuilders daniel-iobuilders commented May 13, 2019

An extension to the ERC-20 standard token that allows Token wallet owners to request payout from their wallet, by calling the smart contract and attaching a payout instruction string.

Token wallet owners (or approved addresses) can order payout requests through blockchain. This is done by calling the orderPayoutFrom or orderPayoutFrom methods, which initiate the workflow for the token contract operator to either honor or reject the payout request. In this case, payout instructions are provided when submitting the request, which are used by the operator to determine the destination of the funds.

@daniel-iobuilders daniel-iobuilders changed the title EIP: Payoutable Token EIP-2021: Payoutable Token May 14, 2019
@axic axic merged commit 05a85a9 into ethereum:master Nov 23, 2019
CarlBeek added a commit to CarlBeek/EIPs that referenced this pull request Nov 26, 2019
…tore

* 'bls_keystore' of github.com:CarlBeek/EIPs: (47 commits)
  fix link to heading
  Fix spelling
  Fix email address
  Draft EIP: BLS12-381 Deterministic Account Hierarchy (ethereum#2334)
  Fix some URLs and require 2333 too
  Add name to metadata title (ethereum#2370)
  Draft: BLS12-381 Key Generation (ethereum#2333)
  Automatically merged updates to draft EIP(s)  (ethereum#2397)
  Hard fork proposal to address the Ice age (ethereum#2387)
  Automatically merged updates to draft EIP(s) 1767 (ethereum#2262)
  EIP-2021: Payoutable Token (ethereum#2021)
  EIP-2009: Compliance Service (ethereum#2009)
  EIP-2019: Fundable Token (ethereum#2019)
  Use solidity/javascript highlighting in various EIPs (ethereum#2372)
  EIP-2018: Clearable Token (ethereum#2018)
  EIP-1996: Holdable token (ethereum#1996)
  Fix the username of @pizza-r0b in EIP-2309 (ethereum#2389)
  Clarify that empty accounts also return 0 in EIP-1052 (ethereum#2388)
  dType Functions Extension - Decentralized Type System for EVM (ethereum#2267)
  Fix spelling of GitHub [R4R] (ethereum#2369)
  ...
@KevinSmall
Copy link

Below are some typos and small clarification requests:

  1. Typo in abstract
    The first part of the abstract says: "this is done by calling the orderPayoutFrom or orderPayoutFrom methods" which are same methods.

  2. Update actors section
    EIP-2021 talks about a "notary", but notary is not mentioned in the Actors section of that page.

  3. Standardise name of "payout agent"
    https://eips.ethereum.org/EIPS/eip-2021 talks about "token contract owner", "agent" and "notary", which I think are the same thing. https://github.com/IoBuilders/payoutable-token talks about "payout agent" which I guess is the same as "agent". It would make reading this EIP for the first time easier to understand, if the same term was used throughout (I liked "payout agent").

  4. Clarification of the EIP
    When reading EIP-2021 on https://eips.ethereum.org/EIPS/eip-2021 for the first time, with no prior knowledge, it was not clear that the word "payout" meant "moving token value from on-chain to a regular bank account". When reading the IoBuilders site for example in the sequence diagrams it is clearer, and we see the term "user bank account".

tkstanczak pushed a commit to tkstanczak/EIPs that referenced this pull request Nov 7, 2020
Arachnid pushed a commit to Arachnid/EIPs that referenced this pull request Mar 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants