Public verification records

Transaction 780301f2393e

These are the public commitment records for this transaction. The resolved outcome and a reviewed copy of the report have been deliberately published as EigenSelect's worked example. The report contains no email address or holder URL. Other transactions keep the outcome and report private to the holder unless the holder shares them. Everything needed to check that the published digests are what they claim to be is on this page. Instructions for each channel are on the verification page.

Records

Pre-commitment record	`pre.780301f2393e.eigenselect.eu` dig TXT pre.780301f2393e.eigenselect.eu +short
Post-resolution record	`post.780301f2393e.eigenselect.eu` dig TXT post.780301f2393e.eigenselect.eu +short
Manifest digest	sha256:7486c43b688b0b6b5cba8869448653669cf6040ef9d6912c29ff42233e3758dc
Resolution digest	sha256:00cb547d00036dc9c6117447a47bc7f9133fef58cf933774897c776cc0ddecfb
Nostr event (pre)	d5e8e31428ff3e9c19163d637e6e86f297b25af9d76075c951650e04f099134e
Nostr event (post)	b2954dfb11f3f84eec36faddd8b516de34610f0e21499f7c01ffc118686df9c2
Committed manifest	`manifest.json` the exact bytes the digest above covers
Committed circuit	`circuit.qasm` the transpiled circuit, as executed

The resolution record, whose sha256 is the h= value in the post-resolution DNS record, names the winning outcome. It is served to the report holder from the status page, and anyone they share it with can hash it the same way.

To check the manifest against what was published in DNS before the processor was contacted:

curl -s https://eigenselect.com/verify/780301f2393e/1/manifest.json | shasum -a 256
dig TXT pre.780301f2393e.eigenselect.eu +short

Any resolver answers these queries; the .eu registry has delegated eigenselect.eu to our nameservers since 15 August 2026 and publishes the DS record for the zone's key. Drop +short and a validating resolver shows ad in the header flags; append @ns1.eigenselect.com to ask an authoritative server directly; the answer is the same. Some earlier reports print the same queries with @ns1.eigenselect.com appended; that form still works.

The manifest commits to the circuit by hash. To check that hash against the circuit that ran:

curl -s https://eigenselect.com/verify/780301f2393e/1/circuit.qasm | shasum -a 256
# expect: dc059c36453d7bea6041690a778013c2e70264dafb6e3552578fc31a5f9473a3