Louis 👵 🦇🔊 pfp

Louis 👵 🦇🔊

@superlouis.eth

684 Following
2353 Followers
Louis 👵 🦇🔊 pfp
0 reply
0 recast
3 reactions
Louis 👵 🦇🔊 pfp
My worst fear happened last night. After 677 days since my last proposal, I got an opportunity, and my node missed it. Trying not to rage-quit the solo staking game, let's figure out what wen wrong: - No missing attestation, I usually get alerts when I miss attestation and go fix it. I wrongly assumed that healthy attestations meant healthy validator. - Nimbus version 24.12.0 (dappnode package 1.0.16, only 3 weeks late from the "medium-urgency" update) - No errors in the logs. Only a casual warning: "Block could not be sent from validator that is also managed by the beacon node" Looking into the log history, it turns out a similar warning appeared for attestations as well: "A validator client has attempted to send an attestation from validator that is also managed by the beacon node" I mean what the f* is this supposed to mean? Upgraded Nimbus to the latest version (no config change). Warnings are gone. See you in 2 years.
12 replies
18 recasts
109 reactions
Louis 👵 🦇🔊 pfp
0 reply
1 recast
4 reactions
Louis 👵 🦇🔊 pfp
3 replies
0 recast
6 reactions
Louis 👵 🦇🔊 pfp
3 replies
0 recast
13 reactions
Louis 👵 🦇🔊 pfp
3 replies
0 recast
9 reactions
Louis 👵 🦇🔊 pfp
1 reply
2 recasts
1 reaction
Louis 👵 🦇🔊 pfp
1 reply
0 recast
5 reactions
Louis 👵 🦇🔊 pfp
5 replies
0 recast
6 reactions
Louis 👵 🦇🔊 pfp
We're doing it wrong. This is a hot take: I don't think legacy wallet UX is a problem (as long as you stay away from metamask). None of the crypto-noobs I've onboarded had issues with writing down a seed phrase and signing transactions. The "signature popup fear" is unfounded. People like to get a confirmation when they are doing something, especially with the strong commitment that comes with blockchains. If people don't want to create/use a wallet to use your product, the wallet is not the problem, your product is. Yet we are trying so hard to make web3 look like web2. And people hate creating and logging in their web2 accounts (I've been locked out of my google account more often than any wallet that I own). Today I have passkeys and embedded wallets all over the place, and every time I'm prompted to login I have no idea if I'm logging in to the right account or creating a new one. An example of today, trying to sign in my Bracket account:
4 replies
1 recast
4 reactions
Louis 👵 🦇🔊 pfp
3 replies
2 recasts
9 reactions
Louis 👵 🦇🔊 pfp
2 replies
0 recast
3 reactions
Louis 👵 🦇🔊 pfp
2 replies
0 recast
9 reactions
Louis 👵 🦇🔊 pfp
2 replies
0 recast
9 reactions
Louis 👵 🦇🔊 pfp
Hello dear Monique friends! Okay, okay. it took way longer than expected to announce the new Monique. Let's start with the cool update: ENS integration is dope: you can resolve any mnemonic with the addr.id suffix (it's also a new name I'm considering). This is huge, it means that you can already use mnemonics inside any wallet or explorer that supports ENS! Now the other (less cool) update: I'm hoping to build a more efficient naming algorithm and I need your help. I started a discussion on the Ethereum Magicians forum on the challenge of using a checksum and reducing the space of available mnemonics. So far I haven't found a satisfying solution. With the current 4-bit checksum and bip39 wordlist there are "only" 500M addresses that can fit in 3 words. That will not be enough if I want to include L2 addresses in the longer term. https://ethereum-magicians.org/t/short-mnemonics-for-addresses/21279 If you're interested in the discussion, or know someone, let me know!
1 reply
2 recasts
1 reaction
Louis 👵 🦇🔊 pfp
5 replies
0 recast
15 reactions
Louis 👵 🦇🔊 pfp
4 replies
0 recast
0 reaction
Louis 👵 🦇🔊 pfp
2 replies
1 recast
0 reaction
Louis 👵 🦇🔊 pfp
2 replies
0 recast
1 reaction
Louis 👵 🦇🔊 pfp
2 replies
1 recast
0 reaction