Trent Nelson

The best option I've thought of is that we decouple address from pubkey and discern between them in `FromStr` with everyone's favorite discriminator, decoded length. `Address` then looks like ```...

Shower thought: Add an _optional_, detached checksum to the address string encoding. Something like ``` {BASE58_ADDRESS}[{SEP}{BASE58_CHECKSUM}] ``` Pros: * Typo/copypasta resistance * No changes to accounts storage as the checksum...

`_` seems to behave well (doesn't break double-click select) in the fields I've tested so far

> oh, 0 could be a SEP too. Maybe that's better since it'll just blend in with the rest of the address. I was thinking we want checked vs raw...

> I feel that telling users to manually strip the checksum to pass to a legacy address seems like a recipe for fund loss, making it easy to visually separate...

@CriesofCarrots @sconybeare @armaniferrante @vidorge any thoughts on detached address checksums as proposed [here](https://github.com/solana-labs/solana/issues/6970#issuecomment-856944798)

> When wallets show the first and last characters, should they show the last characters of the pubkey or its checksum? First N characters and full checksum seems good to...

Pretty low odds we're going to get exchange buy in for something like that. They're very resistant to anything that doesn't fit their chain integration interfaces. The UX deviation is...

> +1 to what @behzadnouri said. From my observations, the vast majority (90%+) of gossip vote transactions error out for `already_processed` because generally turbine votes land faster. However, in the...

As I understand this proposal, it's not intended to prevent contention on a given program/program-owned-resource, but rather to prevent this contention from spilling out as a negative externality on the...