gitaalekhyapaul.eth | .polygon pfp

gitaalekhyapaul.eth | .polygon

@gitaalekhyapaul

134 Following
36 Followers


gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
@ethindia do we get auto-acceptance if we PLAY#THE#GAME ?
0 reply
0 recast
0 reaction

gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
Was working on some code which required inter-operability between ethers and viem, and quickly got myself sucked into a wormhole of function wrappers of function wrappers. ETH interoperability wen? @viem @ethers
1 reply
0 recast
1 reaction

gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
Recasting here to understand how the community feels Eigenlayer can be a part of this:
0 reply
0 recast
1 reaction

gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
Here's something I am interested to collaborate on: Exploring universal reputation-backed decentralized identity solutions using SMPCs and ZKPs, facilitating ease of onboarding non-native Web3 users Looking for interested folks to create a working group for this idea.
0 reply
0 recast
1 reaction

gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
Since you're acting as a proxy anyways, isn't that kind of obvious that there has to be a trust assumption between the 3rd party clients and your backend? Just strying to understand more about the implementation and the goal here...
0 reply
0 recast
0 reaction

gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
You can generate a key pair for each client 3rd party app and then use that to create a digest of the webhook data and send it to the 3rd party clients. Then the clients can verify the digital signature using the API key.
1 reply
0 recast
0 reaction

jamesyoung.eth pfp
jamesyoung.eth
@jamesyoung
vibe shift
1 reply
2 recasts
5 reactions

gitaalekhyapaul.eth | .polygon pfp
gitaalekhyapaul.eth | .polygon
@gitaalekhyapaul
feat(warpcast): init profile SKIP_CI
0 reply
0 recast
0 reaction