@shargon @ixje @roman-khimov @vncoelho @edgedlt @igormcoelho @neo-project/ngd-shanghai

@shargon, what would be transferFrom and allowance?

@shargon, what would be transferFrom and allowance?

you allow another account to transfer from an account you own. The other account uses transferFrom

Add transferFrom and allowance?

With approve and transferFrom, you need two steps. In Neo3, we don't need them. With transfer and onPayment, you only need one step.

Removed name method, because it should be in manifest for all the contracts, not only for the token contracts.

Then we'd better add author, description, email, website in manifest file, too

Then we'd better add author, description, email, website in manifest file, too

They can be in Extra.

Boa Reference: https://github.com/CityOfZion/neo3-boa/blob/development/boa3_test/examples/NEP17.py

Should we add the onPayment method to the standard methods of NEP-17 or C# smart contract template?

@chenzhitong onPayment is a receiver method.

If a receiver doesn't implement the onPayment method, will the transfer execute fail?
接收者不实现onPayment ，转账是否会报错？

In addition, should the manifest of the NEP-7 method must be written

"permissions": [
  {
    "contract": "*",  
    "methods": "*"
  }
]

, because it needs to call the onPayment method of to.
是不是所有的NEP-17方法都要在manifest中添加上述的permission，因为它需要调用to的onPayment方法
@erikzhang

那一个合约（ICO合约）想接收别人给他转账，是不是要在 manifest 中这么写
"trusts": *
这样岂不是很不安全。
@erikzhang

"trusts": *

For example, if the ICO contract needs to receive neo, it has to trust neo. I don't think an ICO can accept any type of tokens.

When will it be merged to master. The proposal seems is already implemented in native ocntract.

Merge?

Celebrate🎉