Prosaic contracts

Core library Headless wallet GUI wallet Web library
Search…
Prosaic contracts
Prosaic contracts are the feature of Obyte platform that helps people to make an agreement on, basically, anything, as text of contracts is a simple text. The benefit of using Obyte prosaic contracts is that after both sides of the contract sign it, a unit, which in fact is a public proof of contract agreement, is posted into DAG, which contains a hash of contract text, while being signed by both peers of the contract. So anyone can check the fact of agreement on the exact same text by those two contract peers. The contract text itself is not revealed but stored in peers wallets.
To offer a prosaic contract from your bot, you have to follow these steps:
user pairs with your bot.
you ask the user to send his payment address (it will be included in the contract) in the chat.
you send the user the private profile of the other side of the contract.
you create a new prosaic contract using the user's address and your address as parties of the contract (also defining contract's title, text and how long the offer is valid).
you send specially formatted chat message with the contract to the user and wait for the response on it ('accept' or 'decline').
the user views the contract in his wallet and agrees or declines it.
on receiving 'accepted' response, you generate new shared address with special definition ('and' between two addresses).
then you top up this shared address to compensate fees.
you initiate posting a 'data' message from this shared address, containing contract text hash. User will then be asked to sign this transaction from the same shared address (as he is a part of its definition).
after getting the user's signature for the 'data' unit, you post it into DAG. Mission accomplished.
We have a special wrapper API for all of these steps in ocore/prosaic_contract_api.js, which in turn is calling ocore/prosaic_contract.js methods. For simplicity, here is an example of using *_api.js, you can check it's code to get a better understanding of what's going on.
start.js
1
"use strict";
2
const headlessWallet = require('headless-obyte');
3
const eventBus = require('ocore/event_bus.js');
4
const prosaic_contract = require('headless-obyte/prosaic_contract_api.js');
5
​
6
function onReady() {
7
    prosaic_contract.listenForPendingContracts(headlessWallet.signWithLocalPrivateKey);
8
​
9
    let contract_text = "I pay Tom $20, if he sends me a pair of his Air Jordans.";
10
    let contract_title = "Air Jordans Purchase from Tom";
11
    let contract_is_valid_until = 24; //hours
12
​
13
    headlessWallet.readFirstAddress(my_address => {
14
        let peer_address = "62SU7724ME5MWB7VEP64VURYZHDRSDWN";
15
        let peer_device_address = "0PUQK5HOEKS4NONGL2ITJI3HMJ76P3LKI";
16
        prosaic_contract.offer(contract_title,
17
                                contract_text,
18
                                my_address,
19
                                peer_address,
20
                                peer_device_address,
21
                                contract_is_valid_until,
22
                                [],
23
                                headlessWallet.signWithLocalPrivateKey, {
24
            onOfferCreated: function(objContract) {
25
                console.log("on offer created", objContract);
26
            },
27
            onResponseReceived: function(accepted) {
28
                console.log("on response received", accepted);
29
            },
30
            onSigned: function(objContract) {
31
                console.log("on signed", objContract);
32
            },
33
            onError: function(error) {
34
                console.log("on error", error);
35
            }
36
        });
37
    });
38
};
39
eventBus.once('headless_wallet_ready', onReady);
Copied!
callbacks object consists of four optional callback functions, which called in following sequence:
onOfferCreated is called right after the contract was created and sent to peer. Always called.
onResponseReceived is called when peer respond to the contract, supplying the response in accepted bool argument.
onSigned indicates that the contract was successfully signed and unit with contract's hash was posted into DAG.
onError can only happen when handling the response, if your bot did receive any response, either onError or onSigned will be called.
The core module for prosaic contracts is ocore/prosaic_contract.js. You can directly use it's exported methods, so check the content of it first.
Smart contract language reference
Contracts with arbitration
Last modified 2yr ago
Export as PDF
Copy link