TOKENDEFI

[Tokenfinance]

dap: <to be assigned>
project name: <project name, company name>
main site: <link to website>
author: <a list of the author's or authors' name(s) and/or username(s), or name(s) and email(s), e.g. (use with the parentheses or triangular brackets): FirstName LastName (@GitHubUsername), FirstName LastName <foo@bar.com>, FirstName (@GitHubUsername) and GitHubUsername (@GitHubUsername)>
discussions-to: <URL>
status: Draft
created: <date created on, in ISO 8601 (yyyy-mm-dd) format>

Simple Summary

"If you can't explain it simply, you don't understand it well enough." Provide a simplified and layman-accessible explanation of your product or company. Limit to 1 sentence.

Abstract

A short (~200 word) description of your product/company.

Resources

Links to your sites, code, and developer tools

• Site - link to site
• Code - link to code
• Dev Tools - link to dev tools

Motivation

The DAP should clearly explain how it fits in the DeFi ecosystem. Provide examples of possible integrations if applicable. DAP submissions without sufficient motivation may be rejected outright.

Specification

The technical specification should show how the project works in actual implementation. Code snippets, visualizations, white papers works here.

Rationale

The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. off-chain orders and on-chain settlement vs direct on-chain order creation and settlement. The rationale may also provide evidence of consensus within the community, and should discuss important objections or concerns raised during discussion.