Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add llc joinder to draft tool #202

Open
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Add llc joinder to draft tool #202

wants to merge 5 commits into from

Conversation

audsssy
Copy link
Collaborator

@audsssy audsssy commented May 5, 2022

No description provided.

@vercel
Copy link

vercel bot commented May 5, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
kali-ui ✅ Ready (Inspect) Visit Preview May 6, 2022 at 10:11AM (UTC)

@audsssy audsssy changed the title Add llc joinder Add llc joinder to draft tool May 5, 2022
@audsssy
Copy link
Collaborator Author

audsssy commented May 6, 2022

Gonna add this in the following areas (only applicable to LLCs) -

  1. an option as crowdsale terms
  2. as option for tribute prop (might need to make capital contributions dynamic to allow for IP submissions)

Any others?

@z0r0z
Copy link
Member

z0r0z commented May 6, 2022

makes a lot of sense! So, I suppose in tribute extension, the user can provide details that clarify whether they are also attaching IP.... so less sure if we make that an open param. But the concept of "Joinder Contracts" should be inclusive imo of the crowdsale and tribute extensions activated by a DAO.

z0r0z and others added 2 commits May 6, 2022 15:39
clarify transfer provision (to more fit with joinder context)
@audsssy
Copy link
Collaborator Author

audsssy commented May 10, 2022

So I'm thinking doc for tribute with ERC20 or ETH should be identical to that of crowdsale, but tribute with NFT may use the following edits

Buyer shall purchase from Seller, and Seller shall sell to Buyer, Membership Interests in exchange for a non-fungible token ("NFT") representing subject matter as provided in tokenURI() of NFT recorded at the time of **proposing this Tribute proposal** capital contributions in cryptographic value according to the terms of the sale program recorded at the time of purchase in the Joinder Contracts. Such sale shall conclude and be effective upon the recording of the transfer in the Joinder Contracts.

I think we can find better language for proposing this Tribute proposal but wdyt about this edit for tribute with NFT?

I think bulk of work here will be around front end logic to have 2 Joinder Ks (one for capital contribute and another for IP/NFT) and based on user selection of either ETH, ERC20, or ERC721, front end automates accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants