Daibase Protocol is designed chiefly for Chefs.
Smart Contracts are its target audience.
What PALM* merely promises in it's red&white-papers, Daibase delivers firsthand.
(*name changed to avoid association.)
Use-cases
- DAIX are suited for debt-denoted forward\future contracts.
- Daibase can be used as a stable unit of account, much like a simple currency such as Bitcoin or Digital CHF, directly inside Smart Contracts.
- Can be used as an automated hedge in smart contracts that are based on "Price-Denoted" "call writing" (Options).
- Daibase Protocol can be used to replace the role of dollar-backed tokenizations to remove dependence on Tra-Fi (Traditional Finance).
- Employed as a demand gauge for other "target-based" Elastic assets.
- And as a spice in many, many more secret recipes of innovative Chefs.
Use the parti() function to participate in self-issuing DAIX tokens. The default function receive() can be used to send native coins to the DAIX smart contract and self-issue DAIX to the sender as well.
NOTES:
- No tax is levied on such transactions by the Daibase Protocol from the sender.
- Such transactions do however charge the tax from the Main-Pair's Liquidity Pool and send it to the King-Maker contract.
- These transactions would thus increase the price of DAIX tokens by a small amount, equal to square root of twice the issued amount's share in Liquidity Pool.
- Each such call to parti shall return and emit a few important things back in the calldata.
About LibDAIX and IXD
Daibase Protocol has created its own interface and also a library. Anyone can introduce these in their own contracts today itself.
The Llibrary consists of many helper functions, and is known as
"LibDAIX".
The interface is named
"IXD". (DAIX was actually called XD prior to version v0.1)
Prototype
(Last update as of v0.1.44)
Function Declaration
function parti()
public override payable
returns (uint256 A)
Old
function parti()
public override payable
returns (uint256 part)
"part" / "A" signifies the amount of DAIX tokens issued to the sender of transaction message.
Application Interface
parti
{
"inputs": [],
"name": "parti",
"outputs": [
{
"internalType": "uint256",
"name": "part",
"type": "uint256"
}
],
"stateMutability": "payable",
"type": "function"
}
receive
{
"stateMutability": "payable",
"type": "receive"
}
"parti" signifies the participate function of Daibase. DAIX tokens issued to the sender of transaction message.
Event Declarations
Events
event Based(uint G, uint E, uint256 T);
Partied
event Partied(uint M, string R, uint N, string S, uint L);
Event Reference
- E
Epoch
- G
Internal
- L
Main-Pair's Liquidity equivalence
- M
Amount sent, denoted in Wei (1e-18)
- N
Issued DAIX, denoted in Wei (1e-18)
- R
Reference String
- S
Reference String
- T
Total inclusive DAIX supply
Detailed guides coming soon. Last Update: v0.1.44 (April, Week 1)