4 ms·
Why can't browser natively sign transactions using secp256k1? And why is that not required for L2 transactions?
by ck_one 5y ago
Why can't browser natively sign transactions using secp256k1? And why is that not required for L2 transactions?
- xrd 5y agoBrowsers don't have that cryptographic primitive available. L2s can choose whatever encryption schemes they want. They could use rot13 if their customers would be willing to work on a L2 chain with that compromise. :) A blockchain (if you already know this, sorry...) is just a ledger with transactions created using public/private keys. Ethereum (and Bitcoin) use secp256k1. But, each blockchain can choose their own and L2s have different ones for different reasons. Eventually the L2 needs to put something back on L1 and that transaction has to be using the crytpo the L1 uses. But, the L2 can store into the L1 the answer to a ZK-proof (with the answer as a link in a Merkle tree), and how you manage transactions (and that Merkle tree) inside the L2 is up to the L2 managers.