pnc

#!/bin/bash

set -e

CONTENTS=$(tesseract -c language_model_penalty_non_dict_word=0.8 --tessdata-dir /usr/local/share/tessdata/ "$1" stdout -l eng | xml esc)

hex=$((cat <<EOF
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">

Dobrokhvalov

//import "openzeppelin-solidity/contracts/ECRecovery.sol";

contract InviteLink {
    using ECRecovery for bytes32;
    IERC1077 owner;
    
    // Mappings of transit pub key => true if link is used.
    mapping (bytes => bool) usedLinks;

    constructor(IERC1077 _owner) {

Dobrokhvalov

Ens Login iFrame draft proposal

Abstract

• User enters his ENS (e.g. user.my-wallet.eth)
• Dapp queries the Ethereum blockchain with an ENS to get the provider source URL/IPFS hash and loads the wallet provider in a sandboxed iframe.
• Dapp interacts with the wallet provider via PostMessage interface - https://developer.mozilla.org/en-US/docs/Web/API/Window/postMessage
• Messages between dapp and wallet provider should comply with EIP-1474 - https://eips.ethereum.org/EIPS/eip-1474

Iframe benefits

• Better security: wallet provider code is loaded in a sandbox environment, can't read dapp's localstorage/cookies and can't track dapp location
• Formalized specs: a wallet provider needs to provide a js code that can respond to the eip-1474 messages