Content
@
0 reply
20 recasts
20 reactions
Dan | Icebreaker
@web3pm
Look again: the cast is now diamonds. The first Cast has been /witnessed in its raw form to serve as an onchain verifiable attestation. No data transformation required. In addition to being more efficient architecturally, this opens up the ability for anyone to retroactively make any cast - past or future - function as an onchain verifiable attestation. This model extends to making any cryptographically verifiable data (whether web2 or web3) retroactively verifiable onchain under any schema. https://easscan.org/offchain/attestation/view/0x640feccf1388c125f3025c7e1c7e7cd39c6497936579f7ba4d6096d4f7fb5f58 https://paragraph.xyz/@icebreakerlabs/casts-vs-attestations-which-is-better
4 replies
30 recasts
55 reactions
na
@na
big if true 👀
1 reply
0 recast
2 reactions
Dan | Icebreaker
@web3pm
Don’t trust me, you can verify it onchain! I know @osprey is adding more tooling for how to visualize. Maybe you could point us to the latest way to do so? We are using the cast hash as the UID posted to @witness and then reference it back in our /eas attestation to make it easy to find later
1 reply
0 recast
3 reactions
Joe / 0xOsprey.eth
@osprey
https://scan.witness.co/leaf/0x0fa2d8a6b91993402b215f092ba786bcf99f1bfa000000000000000000000000
0 reply
0 recast
2 reactions
