https://x.com/eridianalpha/status/1757731294555865275?s=46&t=whpr0JATT7WArfgJwgnO9g
staking
I think @lidofinance grants org (lego.lido.fi) would be happy to pick this up! Liquid blobs!
In the past 2TB was recommended but I would lean towards going for 4TB these days. Prices are pretty good (basically where 2TB was a few years ago) and it's way more future proof taking into account things like possible gaslimit increases down the road, resource needs for large blobs etc.
staking
Yeah something like that. Can start with an allowlist and everyone gets X vouches and then new PFP minters can also get Y vouches.
GreecasterFor sure! Now that frames have text input you could also have a "vouch" button where you input the username/FID of the account you want to vouch and then they can mint.
GreecasterWould be cool to get some sort of greecaster PFP thing going and watch it spread just to see how many of us there are out there. You can mint only if vouched for.
GreecasterI think it's controllable by us via signatures but not directly owned, I haven't fully understood the technical details yet. So, we'd have to wait for bag creator to add this functionality.
Minting from the bag after I sent it Degen worked. That’s all I wanted to test. I wasn’t expecting or trying to get that Degen back.
I treated the bag as a black hole and I do not expect anything to come out of it, it's still clearly a work in progress. I can't help, sorry.
If you mint it to the "safe" wallet I don't think it's possible yet. You'll need some interface created to "sign" the message with the account that owns the safe to transfer the NFT out somewhere else. Basically some sort of UI to manage your "bag".
So we need to send $DEGEN to the safe wallet? How do we figure out what that wallet addr is?
Something like plugins would still be cool. For example you could have a "$degen tips" plugin that would autohide all degen tip posts to reduce clutter and just summarize them in like a status line item under the post, and then you could tip via a button or something.
There's a lot of nuance here that you're sidestepping. Data doesn't end up to 100% for a variety of logical reasons, here's one example: a validator client can be connected to multiple EL nodes at the same time (via various manners). What's the correct way to report this?
EthereumEg improve reporting at CL: https://github.com/ethereum/execution-apis/pull/517 (doesn't help that much and can be easily spoofed / lied to) Another thing being done: network analysis of nodes that we can then cross-check against self-reported data. and...
Ethereum