Advantage of having one default ERC20 tokenscript:
1) We have aligned the behaviour of ERC20 tokens (e.g. status update) to the same source, avoiding having some info from etherscan and some info from nodes and potentially out of sync.
2) As we introduce Activity, we avoid having to hard code rules like this event filter
(|(from=$owner_address)(to=$owner_address))
3) Others have somewhere to start with when they customise their ERC20 TS.
4) We reduce the hard-coded approach for approve() and other ERC20 actions.
Presently I consider shipping such default transcripts with the product αW instead of hosting them somewhere.
Advantage of having one default ERC20 tokenscript:
1) We have aligned the behaviour of ERC20 tokens (e.g. status update) to the same source, avoiding having some info from etherscan and some info from nodes and potentially out of sync.
2) As we introduce Activity, we avoid having to hard code rules like this event filter
3) Others have somewhere to start with when they customise their ERC20 TS.
4) We reduce the hard-coded approach for
approve()and other ERC20 actions.Presently I consider shipping such default transcripts with the product αW instead of hosting them somewhere.