Peter Conrad

I think a solution outside consensus would be preferrable, because the automatism is computation-intensive whereas the resulting set of trades is comparatively cheap and sufficient for consensus. Client-side is probably...

IMO crippling functionality is not the right solution when dealing with user stupidity. (General rule: when you think you've made your software foolproof, evolution kicks in and creates bigger, better...

Of course the software is functional. If users don't read and mindlessly click on "OK" three times(!) even if they don't understand what they are doing you can hardly blame...

1. We don't call it contract, we call it proposal. 2. "Inherently obfuscated" is debatable. All that's necessary to know is there. I wouldn't call it more obfuscated than a...

I will not support such a protocol change, not even with a review.

> The development team is not authorized to modify voting power We developers know that. We do not change consensus without following proper procedures, i. e. creating a BSIP and...

Core team considers cost/benefit ratio when discussing BSIPs, but without formal market research. PMs are not a new core feature, but currently they are hardly useful for building a business...

This would require additional processing on-chain. I don't see a significant advantage for users - recipients have to check for incoming funds anyway. Can someone check how often withdrawals have...

Is anybody still working on this?

> still not fully mature. Note that you can create "draft" pull requests.