Following the quickstart guidance using Ropsten testnet, I have done the following on a synced geth console:
> loadScript('/my/path/to/ensutils-testnet.js');
> new Date(testRegistrar.expiryTimes(web3.sha3('blipblop.test')).toNumber() * 1000)
<Date Thu, 01 Jan 1970 01:00:00 BST>
> ens.setResolver(namehash('blipblop.test'), publicResolver.address, {from: eth.accounts[0]});
"0x28f01d23b98a7b4fe1bc4324cb70e406714e1c14e64e632708f8ec44cebbde78"
When I look up the transaction on etherscan, it reports a bad jump destination and the name does no resolve:
> getAddr('blipblop.test')
"0x0000000000000000000000000000000000000000"
Am I doing something obviously wrong?
Should there be a delay between setting the resolver and being able to resolve the name?
Related (on main net): ENS setResolver bad jump destination
loadscriptcommand. I don't have any further code to add - is there something obvious missing? I've followed the linked guide --> http://docs.ens.domains/en/latest/quickstart.html – Lee Aug 16 '17 at 12:28testRegistrarstep – Lee Aug 16 '17 at 13:14getAddr('blipblop.test')still gives"0x0000000000000000000000000000000000000000"– Lee Aug 16 '17 at 20:02resolver.setAddr()? – carver Aug 16 '17 at 20:210x00...aftergetAddrhowever – Lee Aug 16 '17 at 20:400x27d224a842cd4d6f0e5161a3dbe482a65e8848ad4bbc8645faacaf989157b97b? I get namehash:> namehash('blipblop.test') "0x370f76c0ca0ed4644977abd7995b060f3f13dca45a330b2cd9ef9275b009da0b"– carver Aug 16 '17 at 20:50blipblop2.test! – Lee Aug 16 '17 at 20:51