I think the point npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9 (npub1t89…a5h9) is making though is: “an ion node isn't giving me any proofs that i can use to verify the legitimacy of a response" (definitely correct me if I’m wrong Colby)
if i send a request to an ION node to resolve a DID for me, what proofs are provided alongside the resolution result that would allow me to do any integrity checks?
Without these proofs, an ION node could just lie to me about the contents of a DID Doc and I’d be none the wiser.
an example that isn't ENS would be a DWeb Message or a Nostr event. they're independently verifiable. i can immediately do a sigcheck clientside and know whether the message/event is bunk.
it seems like ION node does have these proofs because they’re required in order to anchor a DID (e.g. self certifying inception event). it just doesn’t return them currently.
If they were returned as part of a resolution result (or could be requested separately) a client would have everything needed to verify legitimacy I think.
Or is the expectation to run your own ion node if you want to verify? Which is a significantly heavy lift
moegrammer /
npub1m0…cv88s
2023-03-20 00:40:23
in reply to nevent1q…754u
Author Public Key
npub1m0ea03u6j2v4ena3xkvh4stp9aqkxly2spd78yeqfv73cfmf6ynsvcv88sSeen on
wss://nos.lolPublished at
2023-03-20 00:40:23Event JSON
{
"id": "6e49aa347f2430408d38af6741eac63690f2976f36a722063160b3b522475cac",
"pubkey": "dbf3d7c79a92995ccfb135997ac1612f41637c8a805be393204b3d1c2769d127",
"created_at": 1679272823,
"kind": 1,
"tags": [
[
"e",
"6e1828963340f8c865c863be2d7cb984f8eb43fe6ddad32b3ecf8f5846345810",
""
],
[
"e",
"d60cbd2bd4500b5dbd5cdcfc25d980ef1272304d4faf9d6cc1b6a532211d9acc"
],
[
"p",
"59cacbd83ad5c54ad91dacf51a49c06e0bef730ac0e7c235a6f6fa29b9230f02"
],
[
"p",
"b9003833fabff271d0782e030be61b7ec38ce7d45a1b9a869fbdb34b9e2d2000"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"784e39dc3ad9d11bff0a1c11b37c81a58c64e13d17b76a7ddb04c45e55fffeee"
]
],
"content": "I think the point #[2] is making though is: “an ion node isn't giving me any proofs that i can use to verify the legitimacy of a response\" (definitely correct me if I’m wrong Colby)\n\nif i send a request to an ION node to resolve a DID for me, what proofs are provided alongside the resolution result that would allow me to do any integrity checks? \n\nWithout these proofs, an ION node could just lie to me about the contents of a DID Doc and I’d be none the wiser. \n\nan example that isn't ENS would be a DWeb Message or a Nostr event. they're independently verifiable. i can immediately do a sigcheck clientside and know whether the message/event is bunk.\n\nit seems like ION node does have these proofs because they’re required in order to anchor a DID (e.g. self certifying inception event). it just doesn’t return them currently. \n\nIf they were returned as part of a resolution result (or could be requested separately) a client would have everything needed to verify legitimacy I think. \n\nOr is the expectation to run your own ion node if you want to verify? Which is a significantly heavy lift",
"sig": "7ce7cf8d613e8cdafc78422cee7aca93545c75eb40bd940d32b52c0e32b8ac9114f0b43b5f1f358c5bb0e2bb6bbe64e4a8c1d3b02b588bbba270cf614da9a95c"
}