memoscan

0x179a…9285

All memos sent from and to 0x179a…9285.
0x179a8627…9285sent to0xf790a5f5…1365·#23,544,458·0x45435e6e…d8356e
Great to see this! Quick note - this proposal only sets forward resolution, not reverse resolution (aka primary name) which is what ENS' potential upcoming naming initiative is about (https://discuss.ens.domains/t/21402). In order to set the reverse records, you'd also have to call `setNameForAddr()` on the ENS Reverse Registrar (reverse.ens.eth) for each contract with the following params: - `addr` should be the contract address - `owner` should be the Nouns executor/timelock (0xb1a32FC9F9D8b2cf86C068Cae13108809547ef71) - `resolver` should be 0xF29100983E058B709F3D539b0c765937B804AC15 (`defaultResolver()` on the Reverse Registrar) - `name` should be the name like "auction.nouns.eth" `setNameForAddr()` depends on a contract having an `owner()` method, which StreamFactory and NounsDAOProxy do not have. So unfortunately these cannot be setup as primary names, but still can have forward resolution like the proposal currently configures. Ping me on tg if you want help adding the calldata to the prop!
0x179a8627…9285sent to0x323a7639…b7e3·#21,424,651·0x8d974bc1…e2b71d
While I appreciate Unruggable's technical contributions to ENS and CCIP Read gateways — and would support their continued involvement in the service provider program — I don't feel they are the best team to operate this infrastructure.
0x179a8627…9285·#17,248,461·0xe363d5c8…297856
OffchainResolver: Not a signerSignatureVerifier: Invalid sigat`SignatureVerifier: Signature exp`ECDSA: invalid signatureECDSA: invalid signature lengthECDSA: invalid signature 's' val`https://ens-gateway.gregskril.com/{sender}/{data}.json