https://github.com/lexDAO/LexCorpus/blob/master/contracts/legal/dao/membership/OperatingAgreement.md adapt for Nevada

LexCorpus could use a primitive pattern to transfer a contract role, right, etc., to another account and then have this acceptance be contingent on receiver "claiming." Basic OZ pattern here: https://github.com/aragon/zeppelin-solidity/blob/master/contracts/ownership/Claimable.sol

This should prob go into a new folder, "utils".

we should add permit() pull using simple code here: https://github.com/banteg/permit-deposit/tree/master/contracts

this allows users to avoid approve TX // simple call deposit~~~https://github.com/banteg/permit-deposit/tree/master/contracts

we should focus contracts into groups that folks can contribute on different aspects:

• Conditions
• LexLocker
• LexToken

adapt Shapiro code deference form tailored for MolochV2 investment club, https://github.com/metacartel/MCV/blob/master/Legal/Grimoire%20and%20Exhibits/MCV-Grimoire-Final-All-Exhihbits.pdf

Basic sanity check on quality of LXL syntax / NatSpec requested: https://github.com/lexDAO/LexCorpus/blob/master/contracts/escrow/lexlocker/solidity/LexLocker.sol

Respond with comments and/or PRs. 🙋🏻‍♂️

https://github.com/lexDAO/LexCorpus/blob/master/contracts/token/certification/Certification.sol

basically, we could use a function like 'selfPermit' that verifies a dai or eip-2612 off-chain signed approval, to be called in batch (multi call) before depositDues() in cases where duesToken supports metaTxs.

This EIP is about to enter acceptance stage.

The LexOwnable.sol contract will need to be updated in line.

event TransferOwner(address indexed from, address indexed to) event OwnershipTransferred(address indexed previousOwner, address indexed newOwner);

LexOwnable can be called from either side, previous or new
transferOwner(address to, bool direct)
A workaround may be to combine with ERC1363 to force a recipient call

additional query function
function owner() view external returns(address);

Note: OpenZepplin has express renounce function whereas LexOwnable cannot be set to zero.

^ title

we have a bare bones escrow contract for locking and releasing erc20 tokens between a depositor (grantor) and recipient.

NFTs can represent financial assets, other rights, and simple escrow in lexdao syntax would be great.

adapt file: escrow

erc721 interface: file

Fairmint has what it describes as a DAT (digital automated trust)
At heart it is an augmented bonding curve with some extra services

A bonding curve contract is a specific type of smart-contract that issues its own tokens through Buy and Sell functions. To buy tokens, the buyer sends ETH to the Buy function which calculates the average price of the token in ETH and issues you the correct amount. The Sell function works in reverse: The contract will calculate the current average selling price and will send you the correct amount of ETH

Looking over the LexDAO token catalog (could be out of date)

can we create an ETH to LXB bonding curve, or more precisely to a pool of LDM time tokens which is the pledged (future) hours that members will be donating to the LexDAO (to be redeemed for either mentoring proto-LEETH or sold to back hire of other services?)

I've started refactoring the LDM(S) into a time-based token plus a higher dispute resolution tribute but need some liquidity. The value is market based but would be at floor #LDM tokens x hourly charge-out rate ...

LDMS token.pdf

we should probably fork and simplify OZ governor contract (collapsing timelock 'delay' concept?) https://github.com/OpenZeppelin/openzeppelin-contracts/blob/master/contracts/governance/Governor.sol

The LexToken Factory could benefit from an interface that checks and returns the manager of a given LexToken. This should then allow our dapp to instantly recognize and upload LexToken management actions when they show up. Will add more deets....

Run basic security check on lexToken.sol // share results in discord hack chat.

50 $LEX.

makes sense to add some bounties for wet code matters and loop into lexdao docs / corpus

currently corpus contracts are MIT. should we explore a permissive/but paid licensing?

see https://github.com/lexDAO/LexCorpus/blob/master/contracts/legal/dao/delegation/DelegationLetter.md

we should likely redraft and make more clear how revocation/removal of governance rights shall occur, as well as what should happen in the event either party loses private keys and technical ability to recover votes (this might involve liquidated damages based on value of delegation?)

**drafting may also be more explicit on function calls (hell, could even include bytes4 function 'signature' related to template governance token created on hack call: #29

https://github.com/lexDAO/dripDrop/blob/drip-dividend/contracts/MemberDrawDropFactory.sol

https://github.com/lexDAO/LexCorpus/blob/master/contracts/legal/dao/membership/OperatingAgreement.md adapt for WY

We are very close to having a light implementation of ERC-721 token that also tracks some of our 'offer token' patterns from LexToken ERC-20.

Requesting a review of the basic contract: https://github.com/lexDAO/LexCorpus/blob/master/contracts/token/lextoken/solidity/LexNFTFactory.sol

Bounty: 25 $LEX

Collecting requirements for Dunsmoor mvp Escrow for lawyers to resolve funds.

• Does LexLocker work here?

https://github.com/lexDAO/LexCorpus/blob/master/contracts/conditions/Whitelistable.sol