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

Adding (generic) Augmented Bonding Curve #37

Open
drllau opened this issue Sep 14, 2021 · 3 comments
Open

Adding (generic) Augmented Bonding Curve #37

drllau opened this issue Sep 14, 2021 · 3 comments

Comments

@drllau
Copy link
Member

drllau commented Sep 14, 2021

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)
LexDAO tokens

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

@drllau
Copy link
Member Author

drllau commented Sep 14, 2021

PS optional extra is a white list - only existing participants can trade amongst themselves to rebalance portfolio as otherwise selling "securities" to public is headache inducing.

@cimplylimited
Copy link
Member

@drllau I am assuming this has long since been left in the dust, though the model is interesting and on the surface seems to circumvent security issues since we are talking about a pool of verified time. Interesting theory. If you would like to reopen this dialogue or help me find a place to move this file, I'm doing some review of what is in the GitHub as a whole. Good luck sir.

@cimplylimited
Copy link
Member

@drllau this too

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

No branches or pull requests

2 participants