polymutex

@polymutex.eth

768 Following

1613 Followers

polymutex pfp

Thanks for the vote of confidence! :) TBH what's been holding me back from actually trying it out is the prospect of having to do the accounting for a stream of hourly taxable events for the rest of my life. But it's encouraging to know that you'd trust my profile. I should check it out in more details this weekend.

1 reply

0 recast

1 reaction

polymutex pfp

Herculean schlep work by @darrylyeo, converting all of Walletbeat's function-based string templates into plain serializable strings. This was necessary for the React→Svelte migration. I feel bad for having made the original string templating code use functions now... https://github.com/walletbeat/walletbeat/pull/137

2 replies

1 recast

3 reactions

polymutex pfp

@ncitron.eth How crazy of an idea is the above?

1 reply

0 recast

0 reaction

polymutex pfp

I think the level of the cinematography here is aiming for the "Jony Ive" type of feel: actually orchestrated to death, but engineered to look effortless ("I didn't try that hard, this level of quality just comes naturally to me")

0 reply

0 recast

2 reactions

polymutex pfp

Cool concept. Interesting to think about how this type of monetary system might work with anons or pseudoanons. Who would trust anons to issue their own currency? How could anons live in a digital economy? Without accountability mechanisms, would the value of their issuance be a pure reflection of their reputation?

2 replies

1 recast

9 reactions

polymutex pfp

I wonder if React usage is mandated in its system message given how hard it's rejecting use of Svelte.

1 reply

0 recast

2 reactions

polymutex pfp

(this phrase is an idiom, not a dunk)

0 reply

0 recast

1 reaction

polymutex pfp

A penny for your thoughts.

2 replies

0 recast

1 reaction

polymutex pfp

This seems to assume that provers would unconditionally accept redundant workloads. My sense is that in practice, economically-motivated provers would reject workloads when they know that a sufficient number of other provers are already working on the same workload. This saves on bandwidth/power costs.

0 reply

0 recast

1 reaction

polymutex pfp

Thanks! Kind of a cute name too.

0 reply

0 recast

1 reaction

polymutex pfp

What's this app?

1 reply

0 recast

0 reaction

polymutex pfp

OK I was wrong, @chaskin.eth did it first. https://warpcast.com/chaskin.eth/0x606f7e6b

2 replies

0 recast

11 reactions

polymutex pfp

I've seen zero posts on Farcaster about 𝗿𝗲𝗮𝗹-𝘁𝗶𝗺𝗲 𝗘𝘁𝗵𝗲𝗿𝗲𝘂𝗺 𝗯𝗹𝗼𝗰𝗸 𝗽𝗿𝗼𝘃𝗶𝗻𝗴 having been achieved today. Seems like a huge deal. The ZK future is here. https://x.com/SuccinctLabs/status/1924845712921264562

2 replies

8 recasts

32 reactions

polymutex pfp

https://deepwiki.com/walletbeat/walletbeat is impressively accurate. Much more accurate than the human-written README that's currently in the repo, by far. Also, it generates flowcharts that explain the rating process for each attribute. They're actually clearer than the manually-written rating process descriptions.

2 replies

1 recast

8 reactions

polymutex pfp

0 reply

0 recast

1 reaction

polymutex pfp

Thanks as always for keeping me honest on this and pushing for focus. We're making progress on this too though! I did add EIP-5792 a few days ago, which EIP-7702 made more relevant. https://warpcast.com/polymutex.eth/0xf34bed08 Also added wallet type schema for the 7702 delegator contracts, though they are not exposed in the UI yet. Lastly I am also working on a document for the EF as part of responding to https://warpcast.com/polymutex.eth/0x9daffecc. In flight! I will also say though, getting to work on things that embody idealism is precisely what makes me encouraged to work on them. It may come across as lack of focus, but I also see it as a necessity for motivation.

2 replies

0 recast

1 reaction

polymutex pfp

I don't think you need governance here. My sense is that you could: - At time time T, load Helios with checkpoint from time T-1 and run it in a sandbox that records all the network traffic. - Look at the checkpoint for time T it produced. - Re-run Helios in a zkVM with a clock set back to time T. Block its external network access, but inject the incoming traffic you had recorded (behavior and incoming/outgoing network traffic should be exactly deterministic). - Re-verify that it produced the same checkpoint for time T. - Submit new checkpoint + proof of correct Helios execution from the zkVM. This effectively means that if you trust the checkpoint at time T-1 and that you trust Helios is correctly implemented and that the zkVM is as well, you can now also trust the checkpoint at time T.

2 replies

0 recast

1 reaction

Darryl Yeo 🛠️ pfp

Darryl Yeo 🛠️

Commencing /svelte -ification of /walletbeat...

3 replies

5 recasts

38 reactions

polymutex pfp

Excited for this 👀

0 reply

1 recast

5 reactions

polymutex pfp

Just chiming in again to say that I appreciate you wading through the BSky crypto takes so that others don't have to.

0 reply

0 recast

1 reaction