Difference between pages "Error" and "Prosaic contract"

From Obyte Wiki
(Difference between pages)
(huh?: changed note)
 
(added note re profile name)
 
Line 1: Line 1:
Error messages in the [[wallet]] and (maybe) how to fix them.
 
  
==huh?==
+
The ability to create prosaic contracts is launched in version 2.7.0 on 20 April 2019.<ref>https://medium.com/obyte/introducing-prosaic-contracts-5d3564638a20</ref>
Table information collection in progress. Please contact @slackjore with any info.
 
{| class="wikitable"
 
|-
 
! Error message !! Notes
 
|-
 
| could not send payment: bad signature at path r || look under the table
 
|-
 
| could not send payment: precommit callback failed || smart wallet containing committed funds that only the counter-party can now spend
 
|-
 
| could not send payment: authentifier verification failed || [[smart contract]] conditions not fulfilled
 
|-
 
| could not send payment: known bad || if you try a bad send repeatedly
 
|-
 
| could not create payment proposal: No bytes to pay fees || so send bytes to wallet
 
|-
 
| connect to light vendor failed [socket closed] || firewall? turn off Tor? (light vendor = hub)
 
|-
 
| ??? || incoming payment not confirmed yet, so wait another 5 minutes or so
 
|-
 
| [internal] connection closed || maybe non-functioning hub: change to another hub
 
|-
 
| unable to verify the first certificate || ???
 
|-
 
| too many messages, try sending a smaller amount [of blackbytes] || send smaller amounts
 
|-
 
| on login “Uncaught exception: Error: message encrypted to unknown key, device" || don't click ok; right click > "inspect" > delete the window in the html code ; restart
 
|-
 
| unable to find parents; failed to find compatible parents: no deep units || witness error, such as (user) swapping out two at once
 
|-
 
| Syncing -- __ private payments left (Android) || probably a connection problem
 
|-
 
| Uncaught exception: Error: Error: SQLITE_ERROR: no such index: outputsIsSerial SELECT unit, message_index, sequence FROM outputs INDEXED BY outputsIsSerial JOIN units USING(unit) WHERE outputs.is_serial IS NULL AND units.is_stable=1 AND is_spent=0 || Likely due to restoring a full backup on a new wallet when the original full backup was an older wallet version. Try downloading a legacy wallet to restore and send funds to the new version
 
|}
 
  
===Comments===
+
== Overview ==
 +
We already have [[smart contract]]s that allow two parties to create a both human- and machine-readable contract that is enforced automatically, in a decentralized way, by all network participants. The parties can be anonymous, don’t need to have any reputation, and the trust is provided by a large community of independent automated verifiers who make sure all the rules are being followed. However, the scope of smart contracts is limited: they can only operate based on data available on the ledger and can allow only the terms that can be represented in a precise machine-readable language.
  
'''tonych [10:43 AM 2017-06-14 #helpdesk]:'''
+
We also have a connection to the real world: a real-world identity that can be [[identity_verification|verified]] and privately stored on the user’s wallet, while a personal-data-free proof of this identity is published on the public DAG.
  
<blockquote>'''Bad signature at path r''' is a mysterious bug that affected a few users in the past but there is no clarity about its nature. Are you on android, did you send any payments from this wallet before? any other unusual actions with this
+
We now leverage the real-world identity to sign conventional contracts. We call them ''prosaic contracts'' because they are written in natural language, contrary to smart contracts that have code under the hood (and code is poetry).
wallet?</blockquote>
 
  
==External links==
+
The solution is very simple: Enable two parties to sign the text of the contract through an easy-to-use interface, store the contract’s text privately in the wallets of both parties, and post their signatures to the DAG where they are verified, timestamped, and stored forever by the network participants. After signing, the parties can easily find the contract text in their wallets to check that they are executed as agreed upon. In case of dispute, any of the parties can reveal the full contract to a third party, who can easily verify the validity of signatures through the DAG.
  
==References==
+
=== Profile name ===
 +
Enter both First and Last name in the profile. Otherwise the prosaic contract will display "unknown name."
 +
 
 +
== References ==
 +
<references />
  
 
[[Category:Browse]]
 
[[Category:Browse]]

Latest revision as of 16:05, 21 May 2019

The ability to create prosaic contracts is launched in version 2.7.0 on 20 April 2019.[1]

Overview

We already have smart contracts that allow two parties to create a both human- and machine-readable contract that is enforced automatically, in a decentralized way, by all network participants. The parties can be anonymous, don’t need to have any reputation, and the trust is provided by a large community of independent automated verifiers who make sure all the rules are being followed. However, the scope of smart contracts is limited: they can only operate based on data available on the ledger and can allow only the terms that can be represented in a precise machine-readable language.

We also have a connection to the real world: a real-world identity that can be verified and privately stored on the user’s wallet, while a personal-data-free proof of this identity is published on the public DAG.

We now leverage the real-world identity to sign conventional contracts. We call them prosaic contracts because they are written in natural language, contrary to smart contracts that have code under the hood (and code is poetry).

The solution is very simple: Enable two parties to sign the text of the contract through an easy-to-use interface, store the contract’s text privately in the wallets of both parties, and post their signatures to the DAG where they are verified, timestamped, and stored forever by the network participants. After signing, the parties can easily find the contract text in their wallets to check that they are executed as agreed upon. In case of dispute, any of the parties can reveal the full contract to a third party, who can easily verify the validity of signatures through the DAG.

Profile name

Enter both First and Last name in the profile. Otherwise the prosaic contract will display "unknown name."

References