full image - Repost: I don't like polyseed. (from Reddit.com, I don't like polyseed.)
Mining:
Exchanges:
Donations:
There, I said it. I don't think I'm the only one.It's much too complex for what a seed is for. A seed is a key, nothing more. It encodes a key in a human readable way. Whether there's a passphrase or not is not encoded in the seed, and shouldn't be, for plausible deniability.Custom bits in the seed seem like one hell of a way to cause trouble.Information in the seed besides a key means the seed is not uniformly random. Polyseed attempts to mitigate this by distributing the extra information in the seed in a predictable way so that there are no seed collisions. I don't think this is a good idea even then.Block height... I'm sure it helps a lot of people to sync a seed when the block height is encoded in it. But you can just write the block height on the paper you write the seed on and accomplish the same thing.150 bits of a polyseed are the key. I'm partial to 256 bit keys. Everyone says it's overkill, but I don't see a cost that outweighs said overkill. The order of a 12 word bip39 mnemonic (for example) can be brute forced in minutes. A 24 word one takes billions of years. Nobody is ever going to convince me that that is not worth it.I'll stick to 25 word mnemonics in Monero for the foreseeable feature. I just wanted to bring this up because I've never seen a whole lot of discussion on the matter, and very little of the naysayer side on this topic.
Social Media Icons