Johnny Goodnow

Mostly I'm looking for what steps should be taken next on this issue in your respective opinions.

@bonen did @stanford-scs's comment around SEP-0001 solve your issue? If not, it's probably worth getting additional feedback on our mailing list, and potentially making a CAP if it feels like...

@MonsieurNicolas, do you want to work this into a draft? Re-open the discussion on the mailing list? Hand it off to someone else?

@MonsieurNicolas is it worth reviving this discussion? I agree it's a weird behavior that affects usability, but it feels mildly painful as opposed to detrimental (especially if changing the behavior...

@MonsieurNicolas do you mean "yes, I think this should be revisited but I don't have the bandwidth to look into it/write a CAP" or "no, I don't think the cost...

@jonjove @MonsieurNicolas — any thoughts on this? Seems gnarly, and I'm not sure if any past changes about liabilities in the protocol have changed this scenario.

Hey @MikeFair — what do you feel you need here next? Do you want to move this forward with a CAP proposal (along with any additions that would probably need...

@MikeFair could you post your last few comments to our mailing list, and link to this issue? [You can join it here](https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!forum/stellar-dev). I think you'll likely get more traction towards...

Hi @ghost, could you help explain the intent of adding this to SEP-0001? I'm trying to have a better understanding of why it's valuable for users to know if an...

Hey @MikeFair — if you have any interest in pushing this forward, writing a CAP draft, or moving conversation to our mailing list (link in the main README) to get...