Given we both got our laptops out just after take-off, and had code on our screens, it was pretty clear we were heading to Cancún, and started talking about our projects with one another. I’d see Nick talk about ENS at theLondon Ethereum Meetupa while back, and had integration with it inweb3jon my todo list. However, given that I had Nick sat next to me, and a 9 hour flight in front of me, it was a no-brainer to start work on it then and there!
The ENS support in web3j means that anywhere you previously had to use a contract or wallet address, you can now use an ENS domain name instead.
The web3j implementation provides input normalisation and validation adhering toUTS #46. Nick was adamant that any ENS implementations does this :).
web3j can now work with Truffle JSON files for generating smart contract wrappers. This means that if you currently or have used Truffle for your smart contract development, you can generate smart contract wrappers in Java from them. The advantage of this approach is that your smart contracts will know where they’ve been deployed previously.