Jeremy Rubin

This allows you to setoptions modulate the thresholds and weights for existing keys without accidentally making a previously invalid transaction valid. I think a more classic example is the "mom...

No, that doesn't work for a couple different reasons. 1) need to simulsig across accounts. 2) Requires a known sequence number/freeze to simul authorize 3) requires publishing all pre-signed (O(N))...

I think @jonjove should take a look at this one as he'll have a handle on the least annoying way to implement. Not sure it's particularly hi impact -- but...

@jedmccaleb we actually need a SEP and a CAP -- CAP would cover signature aggregation which would happen in core. Maybe we should start with the SEP, and eventually move...

1. It is compatible with ed25519 curve 2. It does allow weighted signatures; but it's a bit more complicated (or really any monotone boolean circuit) and doesn't permit non-interactive setup...

Someone at interstellar should take part-ownership, I believe there is code which could be released for this purpose. Someone else at SDF should take ownership of seeing it made available...

I'm not interested in pushing any further on this -- it's an issue with the way that we do signatures, but it's not something we can easily fix. Similar to...

Thanks for taking the time to respond. > The same reason that you're posting any operation: you want authenticated > information to be publicly available in a resilient manner. So...

I think the main points I'm interested in are: 1) Storing them on chain is expensive, and needs to/will become more expensive over time. We may even explore making reserves...

Yes, hence I've proposed deprecating but not removing. As stewards of the protocol, there's an obligation to encourage good software engineering. I agree there is a need to store data...