# Records

Zoe v0.5.0. Last updated 4/20/2020.

These records (JavaScript objects with data properties and no functions) are used throughout Zoe.

# OfferResultRecord

This is returned in a promise by a call to offer on Zoe. It contains promises for handle for querying Zoe about the offer, the payouts when the offer is complete, the result of invoking the contract-specific hook associated with the invitation, and if appropriate for the specified exit policy, a remote object with a complete operation to complete the offer.

The offerHandle promise fulfills once the payments in the offer have been escrowed. The contractOfferPromise is from the contract, and so depends on the contract code. The paymentKeywordRecordPromise gets resolved by Zoe when the corresponding offer is completed (i.e., when the offer exits).

  offerHandle: offerHandlePromise,
  outcome: contractOfferPromise,
  payout: paymentKeywordRecordPromise,
  completeObj: remoteCompleteObj

# Proposal

A Proposal has three parts: want and give are used by Zoe to enforce offer safety; exit is used to specify the particular payout-liveness policy that Zoe can guarantee. want and give are objects with keywords as keys and amounts as values.

  want: someAmountKeywordRecord,
  give: anotherAmountKeywordRecord,
  exit: someExitRule

# IssuerKeywordRecord

The keys are keywords, and the values are issuers. These keywords will be used by users to make their proposal. In the below example, "Asset" and "Price" are keywords.

  Asset: moolaIssuer,
  Price: simoleanIssuer

# PaymentKeywordRecord

The keys are keywords, and the values are payments

  Asset: moolaPayment,
  Price: simoleanPayment,

# AmountKeywordRecord

The keys are keywords, and the values are amounts. Keywords are unique identifiers per contract, that tie together the proposal, payments to be escrowed, and payouts to the user. In the below example, "Asset" and "Price" are keywords. And in an auction instance, the keywords might be "Asset" and "Bid".

Users should submit their payments using keywords: const payments = { Asset: moolaPayment };

And, users will receive their payouts with keywords as the keys of a payout object: moolaPurse.deposit(payout.Asset);

  Asset: amountMath.make(5),
  Price: amountMath.make(9)

# AmountMathKeywordRecord

The keys are keywords, and the values are the amountMath for particular issuers.

const record = {
  Asset: ticketAmountMath,
  Price: simoleanAmountMath

# BrandKeywordRecord

The keys are keywords and the values are the brands for particular issuers.

# ExitRule

The possible kinds are 'waived', 'onDemand', and 'afterDeadline'. timer and deadline only are used for the afterDeadline kind.

The possible records are:

{ waived: null }

{ onDemand: null }

{ afterDeadline: { timer :Timer, deadline :Deadline} }

  afterDeadline: {
    timer: someTimer,
    deadline: 1893459600

  waived: null,

# OfferStatuses Record

active and inactive lists of offerHandles.

  active: someListOfOfferHandles,
  inactive: anotherListOfOfferHandles

# Installation Record

  handle, // opaque identifier, used as the table key
  installation, // contract code

# Instance Record

  handle, // opaque identifier for the instance, used as the table key
  installationHandle, // opaque identifier for the installation
  publicAPI, // the invite-free publicly accessible API for the contract
  terms, // contract parameters
  issuerKeywordRecord, // record with keyword keys, issuer values
  brandKeywordRecord, // record with keyword keys, brand values

# Offer Record

  handle, // opaque identifier for the offer, used as the table key
  instanceHandle, // opaque identifier for the instance
  proposal, // the offer proposal (including want, give, exit)
  currentAllocation, // the amountKeywordRecord that will be turned into payouts