Content
@
0 reply
0 recast
0 reaction
androidsixteen
@androidsixteen.eth
TIL about Witness lazy minting (h/t @eulerlagrange.eth): https://docs.witness.co/concepts/usecases#provenant-lazy-nft-minting-erc721p Really cool idea - decouples execution & clearing from settlement in media issuance: 1) First put provenance onchain 2) Then make it composable with global state (by issuing the actual NFT) "Soulbound" NFTs that don't need to be composable with other onchain state could just do #1 and save a lot of gas, provided the offchain app knows how to use Witness' interface — am I thinking about this right @osprey?
1 reply
3 recasts
11 reactions
Joe / 0xOsprey.eth
@osprey
great way of describing it! capture “what”, “who” and “when” in an onchain verifiable way without gas or settling onchain 🫡
1 reply
0 recast
0 reaction
Joe / 0xOsprey.eth
@osprey
another cool thing is that the offchain proofs require nothing but read access to one of the many underlying public blockchains that the protocol settles to periodically not requirement to trust or rely on anything but the chain for verifying “when”
1 reply
0 recast
1 reaction
androidsixteen
@androidsixteen.eth
I guess the challenge is changing app devs' paradigms around how to read onchain data, since you just need witness' merkle root and the merkle path to confirm the data. But who generally is expected to provide the merkle path? And how often do y'all "checkpoint" the merkle root? Have you run into gas issues at all?
1 reply
0 recast
2 reactions
