Dexaran

@splix the problem you are trying to solve is already solved. I solved the same problem developing ERC23 token. You can send ERC23 token to exchange contract, exchange token1 to...

I wrote the described exchange. You can browse it here: https://github.com/Dexaran/dataPayload/tree/master/PayloadExchange_example This is a single-exchange-transaction you are looking for: https://testnet.etherscan.io/tx/0xf41529fb61de85a3e1ea45682f285ce7e23ea0c9f5283c392a4ca445eb14c92b There is also a way to do so without `bytes...

@splix I understand it but there is already a possible way of interaction between contracts. Can you name any scenarios that need such changes in protocol and can't be executed...

@splix can you describe your proposal more detailed? I'd like to see any code or something that I can execute and try to fully understand how will it work. Or...

@splix finaly I found this feature useful. It is a good idea but I'm not sure we need to change protocol to implement it.

As a smart-contract developer, I would say that REVERT opcode implementation is an important detail for smart-contract development & compatibility with current Remix IDE. I support EIP658 implementation in ETC....

Agreed. As Ethereum is using .eth we can use .etc I don't think it's needed to bring EIP137 and EIP162 to discuss here. I will just implement anything they decide...

ENS is preparing to be launched. I'm watching progress. Some more details: https://medium.com/the-ethereum-name-service/updated-ens-now-deployed-on-ropsten-testnet-ffc2c4a8a99e

> Much better is to create naming standard and API like the token standard ERC-20. The ERC20 token standard results in a [loss of $ 320,000](https://www.reddit.com/r/ethereum/comments/60ql37/attention_be_careful_using_ethereum_tokens/). It seems that it...

To make it clear: I don't like blind auction model. I have also changed some things inside ENS contract already. I want to create a very similar contract that will...