Noah

This project utilizes a deadman switch alongside neutrally incentivized MEV mechanisms (to gauruntee maintenance without our intervention) to ensure that funds will always be withdrawn and liquidated to a predetermined beneficiary address should a set amount of time pass without the owner's intervention (meaning they have either lost access to their wallet or themselves).

At that point in time, funds are liquidated through either a dutch auction through Noah ourselves, or through a uniswap hook depending on what the user has designated. The user also has a choice of either liquidating to USDC or PYUSD (still using the most efficient liquidity routes regardless of choice), in addition to the choice to use Fern as an offramp.

If the user choses fern as an offramp, they are prompted to complete KYC (currently a KYC facade), and generate first a customerID then a paymentID. These are stored for future use upon which time a quote is generated and then funds can be offramped. For users that have chosen to recieve USD directly, funds are pooled in the Noah contract and then the admin submits our stored customerID, paymentID and quote to create a new payment address, to which the admin then calls 'fernOffRamp' to send the according amount of capital to the newly generated payment address for offramping.

At that point the standard inheritance process can proceed and a naive or even completely ignorant beneficiary can access their funds without necessarily ever touching web3.

Deployments: For most of our suite we used Hardhat alongside a number of custom scripts for deployment and infrastructure maintenance.

We are already or are deploying over the next few hours across:

• ETH
• Katana
• Flow
• Arbitrum
• Zircuit
• Hedera
• Flare
• Chiliz
• MegaETH

Depending on the chain above there are various enshrined benefits (E.G. Flare's price feeds), consumer benefits (E.g. Flow's consumer oriented ecosystem, or Chiliz' fan oriented ecosystem), or DeFi benifets (E.g. ubiquitous standards across Katana)

IDE: We used Nora for a lot of our solidity development IDE. Nora really established all of our initial codebase and structure as well as wrote 90+% of our tests, ensuring we had full coverage and expected operation when it came to deployment.

Pricing: We used two price sources to ensure that our liquidations operated in an effective manner, Flare and Chainlink. When either were not available, we used one or the other, while when both are available we used an average of the two with small modifiers to create the starting and ending prices for our dutch auctions and uniswap price checks.

Currencies + Offramps: As mentioned we provide the ability to liquidate to PYUSD, USDC, or USD directly.

For PYUSD, funds are normally liquidated to ETH or USDC before being then liquidated to PYUSD.

If the user choses fern as an offramp, they are prompted to complete KYC (currently a KYC facade), and generate first a customerID then a paymentID. These are stored for future use upon which time a quote is generated and then funds can be offramped. For users that have chosen to recieve USD directly, funds are pooled in the Noah contract and then the admin submits our stored customerID, paymentID and quote to create a new payment address, to which the admin then calls 'fernOffRamp' to send the according amount of capital to the newly generated payment address for offramping. At that point funds are essentially treated like any bank account for traditional inheritance processes or for individual ownership.

ENS: As part of our integration for ENS we built out partial 721 compatability, but full ENS transfer compatability as our frontend was focused on their integration. With our completed integration user can now chose to put an ENS in their Ark, ensuring that should anything happen to them or their keys their ENS is transferred to a predetermined beneficary.