Hi, just woke up here, I currently have Flu-A. People are saying there was a verifiable FC post from my account. Any WC protocol sleuths who can help me identify the exact signer that sent it (would sure be nice if these were device linked), I'd appreciate it.

co founder of @metamask . Making computers behave for us.

It came from your Warpcast signer. That signer is not revealed to anyone but Merkle apps.

Hope you feel better 🫂

that means his seed from warpcast compromised?

CEO and Founder of $BLEU

Developing infinite memetics AI Agent @elefant


lebleuelefant.com

Warpcast would still need to create the private signer key.

Not taking any sides here just trying to make sure we're all secure. Some useful info I just validated myself:

If you ADD a message (hub speak for casting) using signer A
and then DELETE a message using signer B

all the signing tools, hub message APIs, etc. will say signer A doesn't have any recent activity because the message returned by the hub is overwritten to say signer B is affiliated with the message. Because it was the last one to interact with it (delete). 

If someone (most likely MM team @dwr.eth @v) has logs of hub events then we'll know which signer sent the cast from @danfinlay's account this am. 

Until then we can't be sure that it was the Warpcast signer. We also can't be sure that any of the other signers are off the hook. All we know is the Warpcast signer deleted the message (probably after Dan logged on).

how'd you validate the warpcast signer added the message? I know it deleted it but this is my current understanding

how'd you validate the warpcast signer added the message? I know it deleted it but this is my current understanding https://warpcast.com/sayangel/0xb5d58dfd

Creator of @harmonybot @yoinker /bot-or-not | /blitkin | /orange-dao | IRL: Building spatial computing for construction @ Resolve YC W15

I can check our own hub logs for the original message signer. Merkle can also check their APIs for the same.

Good insight.