1.7K @unifyWeb3 one thing is to have an idea and ship
another thing is for deployment to go through
btw able to solve the previous bug but then again encountered another - found a missing contract_address payload bug in the starkZap SDK's balanceOf wrapper
had to write a custom error boundary bypass to keep the hackathon momentum going
im tired bro.
1.7K @unifyWeb3 building an app on @ starknet and encountered an issue btw which i learned the hard way today
an embedded wallet on starknet requires server-side signing, unlike the simple frontend hooks on evm
at the moment, tho - rewiring my next.js API routes to handle the cryptography stage
the whole archi on starknet is really built differently
0
0
20
1.7K @unifyWeb3 building an app on @ starknet and encountered an issue btw which i learned the hard way today
an embedded wallet on starknet requires server-side signing, unlike the simple frontend hooks on evm
at the moment, tho - rewiring my next.js API routes to handle the cryptography stage
the whole archi on starknet is really built differently
2
1
56
5.5K @hieuvueth 5.5K @hieuvueth StarkWare continues to highlight a key advancement in Recursive Circuit Proving with S-two.
Proving time has been reduced from 1 minute to just 3 seconds -- a 95% reduction in both latency and computational resources. This now makes proof generation feasible on standard laptops, with significantly smaller proof sizes and lower costs for creation and verification.
These improvements substantially strengthen on-chain privacy (STRK20s), bring decentralized proving closer to reality, enable client-side proving on everyday devices, enable faster Starknet settlement on Ethereum.
A meaningful contribution to ZK infrastructure.
18
1
629
