#open transactions

Recently I became involved with SCC's committee on "Blockchain and electronic distributed ledger technologies". During one of the discussions, I've learned about a new term that seems to have become very popular in the banking industry - "Distributed Ledger Technology" (DLT). Apparently companies like Deloitte or even the UK government have picked up on this new thing and seem to be abuzz with it. Instantly this reminded me of 2015 when big companies like NASDAQ and Overstock expressed their interest with "the Bitcoin technology", but they didn't want to be associated with "Bitcoin", therefore decided to rename this whole thing as "blockchain technology". Maybe this was just another way for companies to invent a new five dollar word and charge a hefty sum to consult on it? After doing some research, I couldn't find much on what exactly DLTs were - there doesn't seem to be a concrete definition floating around yet. However, a few people pointed me to one example of an actual implementation of a DLT - Corda. Lucky enough, someone coincidentally decided to organize a meetup about Corda around the time, so I had some good opportunity to learn what it's about.

Corda

Corda is a Distributed Ledger Technology implementation by the R3 consortium. It is open source, comes with a Slack, a whitepaper and all that. Corda has been created from the grounds-up for the use by banks and other financial institutions, prioritising their needs first. This dictated a few important design choices:

Private transactions - transactions in the system are only disclosed to the parties involved. They are not globally broadcast for everyone to verify, instead only circulating in very limited circles as small as two peers.

No blockchain - since there is no need to let everyone know about every transaction that took place, there is also no need for a blockchain, be it public or permissioned

Legal smart contracts - much like a Ricardian Contract, the smart contracts executed on the Corda network have explicit legal prose attached to them.

Optional notaries - if two parties don't trust one another, they can bring in optional notaries to verify various aspects of the transaction (no double-spending, uniqueness of transaction, etc.)

Knowing these features, we can try figuring out what existing cryptocurrency project it resembles most. Looking at this chart comparing various projects in the space (provided funnily enough by Tim Swanson a few years back before he joined R3):

Tim Swanson's "Current Cryptoprotocol Infrastructure" from his "Great Chain of Numbers"

It looks like Corda can fall in only one spot, which is the "Ledgerless Crypto Suite", alongside Open-Transactions. Indeed, the resemblance is quite strong. The following explanation is based on the "Introduction to Corda" presentation and other materials I managed to come by. Corda's base building block is a cryptographic transaction. It can be a simple payment, or a more complex smart contract. The transactions specify which inputs they are spending and what outputs they are generating (this works just like Bitcoin and is different from an "account-balance" approach of say, Ripple). Each transaction has a hash of a legal prose attached to it which governs how the transaction should operate. The transaction is then signed by all of the participating parties that agree to execute it - it could only be one entity when it is a simple "send money" transaction, or span multiple parties if it is a more complex swap or financial agreement. The transaction can also be notarised or verified by third parties as needed. This could be as simple as a server doing a blind signature to verify the transaction is unique, or perhaps the whole transaction could be disclosed to some auditors as needed. After a transaction is signed, that's about it - every party that knows about the transaction records it in their ledgers and the financial contract is thus binding. There might be some follow-up on the smart contract as it matures or other trigger points execute it, but with no blockchain, block generation or the like, there isn't much else to it. As it stands, Corda seems to fit in as a common middleware for banks and financial institutions to standardise their interactions with one another, especially in the realm of financial contracts. This puts the project in a similar space to Open Transactions or Interledger, not too far from Ripple or Ethereum.

Corda criticism

Due to its focus on catering to the financial institutions, Corda might be seen as "more of the same", rather than trying to revolutionise the field like Bitcoin. Some people might dismiss it out of principle for not fighting to make the banks more transparent. A system built on private transactions will be easier to manipulate than a proper blockchain. Unless all of the transactions need to be accounted for by some independent auditor, you loose the option to have "negative proofs". Since the amount of parties involved is so small, they can easily conspire to rewrite or delete the past transactions to suit their present needs. This could be mitigated by using a proof of existence and anchoring the various hashes of transactions into something like Factom. However, if properly maintained, the system can enforce accountability. While the transactions may not be a part of a blockchain, they do form a transaction chain - every transaction spending the previous output. Having any single transaction signed by the various parties could be used against them - they might be compelled to provide the full, unbroken chain of transactions leading up to that transaction. While this might not uncover all of the transaction branches, there is at least some cryptographic trace of what happened. Linking the legal prose to the smart contract is also asking for trouble. Even now people can have legal disagreements as to which interpretation should take precedent when you have a contract written in two human languages. Woe to anyone who wishes to mix legal prose with a smart contract. This would either require a new profession of some lawyer-programmer, some sort of legalese language interpreter / compiler, or the smart contract will be just a farce that could be overturned so easily it might not even need to exist. Corda's presentation seems to indicate the legal prose takes precedent over the code. This might mean that there would need to either be some backdoor for third parties to overwrite or amend the contract, or the parties involved would have to work around the code to achieve settlement in the end. All in all, this can lead to a lot of mess in the code down the line. Some might prefer the approach of "code is law", but then we have the story of the DAO as a cautionary tale. Moreover, the contracts dealing with international law and regulations would be even more complicated. This could lead to fewer transactions taking place between various jurisdictions to avoid the legal hassle. Beyond that, Corda seems to rely on a few known key actors common to the Crypto 2.0 space. Lack of native currency means the system will need gateways to issue assets. Some design documents mention Smart Oracles, etc.

Distributed Ledger Technologies

Based on the example of Corda and Open Transactions, we can try drawing some conclusions of what the Distributed Ledger Technologies might be as a general term.

The technology seems to be focused more on transactions and less on grouping them into blocks.

With the absence of blocks, we necessarily have to do away with any form of distributed, native currency - there is no way for that currency to be objectively generated. The system instead uses IOUs for currencies and assets.

The system relies on a number of key nodes / entities to operate - auditors, validators, legal authorities, banks, etc. This means the system would be at best "decentralised"

Cryptography is still used to authorise various transactions and move the money around.

Conclusions

eCurrency Mint (not to be confused with MintChip) is a new startup backed by an eBay founder that is aiming to create what looks like a Crypto 2.0 network augmented with anonymous transactions. It looks to be aiming to create a digital cash system - allowing central banks to issue tokens that anyone can anonymously transact in, just like with physical cash. Lets have a look and see if the idea is feasible.

Features

Based on an article from Payments Source, the Mint appears to:

Allow central banks to issue digital currencies

The issued currency is untraceable ("eCurrency Mint [...] doesn’t let a central authority track the ownership and usage of the digital money"), although "individual countries could implement the technology differently"

The currency would take a form of "cryptocomplexes", which would either be similar to Bitcoin transactions, or be their own atomic tokens (the text is unclear) ("[I]nstead of printing a billion one-dollar bills, [a central bank] would issue digital objects called cryptocomplexes that it would inject into the financial system much as it does cash today")

"[E]ach [cryptocomplex] keeps track of itself. Through a unique identifier, each unit is forever associated with the original block from which it came. The central bank would know immediately if the total of all the pieces added up to more or less than a billion. But it wouldn’t know where each piece is, or who owns it."

"There’s no general ledger like bitcoin's blockchain for eCurrency."

Analysis

Based on those features, it looks like we are dealing with a ledger-less currency similar to either Open Transactions or what MintChip was supposed to be.

The biggest design challenge of what was described is the anonymous aspect of the currency. While the details of what the author meant by "cryptocomplexes" remains unknown and more details would be needed for a proper analysis of the technology, what is being presented is not beyond the realms of possibility. We can look at Dash's DarkSend, BitShare's TITAN, Confidential Transactions proposed by Greg Maxwell as examples of how this can be achieved, at least in a ledger-based network. For a setup like Open Transactions, you would probably use some scheme based on blind signatures for the notaries.

While what is presented is technologically possible, the scheme could be found illegal under various rulings, such as the 2013 FinCEN guidelines on Virtual Currencies. While it would be feasible to perform full KYC on when the currency enters or exists the system (at least until there is even a need for such transfers before money becomes completely digital), losing the ability to track, freeze, seize and audit the financial records of various people might be seen as helping money laundering and criminal activities.

Conslusions

The information presented about the eCurrency Mint paint a technologically plausible picture of a new anonymous, ledgerless Crypto 2.0 system similar to some of the features described by MintChip. It would be interesting to see more technical explanation of the proposed system, as well as an overview of how such a system could fit into the existing regulatory framework.

Due to the heavy emphasis on anonymous transactions, I doubt the eCurrency Mint will ever be considered for adoption by any government or central bank in its current form.

Related articles:

Sample bankchain feature set

BitUSD vs USD IOUs

This week at Decentral Vancouver we had a discussion with Michael Linton and Dominique Legault from Open Money about the LETS (full recording). LETS, or Local Exchange Trading System is essentially a community-run non-for-profit system for recording transactions, often using a form of a local currency. During the discussion various comparisons to the current Crypto 2.0 systems came up, along with some debate whether local currencies in general are good for us. Let us dive into these topics deeper.

Trust-based systems - explanation

Trust-based systems can be defined as a monetary system based on currencies requiring a trust that other parties won't default on their obligations. Examples of such systems include banks, gift cards, debt, as well as the aforementioned LETS, Ripple (minus the XRP portion) and Open Transactions. Counterexamples are currencies where you directly control the monetary asset transacted in, such as barter, gold or Bitcoin. All trust-based systems can be boiled down to managing Trust and Debt:

Trust and Debt in Ripple Trade wallet

Trust is the limit of how one person is willing to have the other person owe them, while Debt is the current amount owed. So if I Trust BitStamp for $100, I am willing to hold up to $100 of their Debt before they won't be able to send me any more money. If I hold $10 in balance from BitStamp, they are $10 in Debt. These simple relations are pretty much how all of the modern banking works. A savings account is you Trusting the bank and them being in Debt to you at your current balance. A credit card is the bank Trusting you, and the amount you charge onto the card is how much in Debt you are to the bank. If I send money from my account to yours, bank's Debt to me is reduced, and it is increased for you. Based on how Trust is placed, we can have 3 different systems - centralized, decentralized, and distributed:

A centralized system is like a government issuing a currency - everyone in the given country is obliged to trust it and use it. The world economy is a decentralized system - every government issues their own currency, most people use one currency, but there is some connection between the systems. Local network of interpersonal debt ("I owe you $5 for the drink last night") is a distributed system. All of the trust-based systems can take a form of any of the three systems. Currently, Ripple Classic and LETS are more focused on the distributed model, while Ripple and its gateways are focusing on the decentralized approach.

Decentralized vs Distributed model

As the centralized model is pretty similar with decentralized model, I will omit it and discuss the other two models. From a practical perspective, you will most likely have some combination of a distributed and decentralized model in your trust-based system. The distributed model appears to be more useful when "liquidity" is scarce and there are more direct interactions on a community level. For example, if you have two people with no cash on hand that are capable of working for $10/hour, under the centralized or decentralized model they wouldn't be able to do anything because they wouldn't be able to pay one another. Under the distributed model, they can still work by tracking how much they each owe one another and settling the difference in kind. Similarly, the debt could be exchanged in a web of trust in the local community for different goods and services. The decentralized model appears to be more useful when parties don't trust one another, but can trust some third party. For example, a person selling a $100k house might not want to trust a stranger to repay the debt over many years, but would be more willing to trust a bank or similarly large institution. This model is also useful for trade outside of your circle of friends as it reduces complexity. Sending money overseas in a decentralized model means going from you, to your bank, to recipient's bank, and to them, rather than possibly funnelling through a network of many people.

Good money vs bad money

Gresham's law is commonly stated as "bad money drives out good money". It is often mentioned in context of money's nominal value (how much value is printed on the bill or coin) and its commodity value (how much the raw cotton or metal used to make the money is worth). To put it simply, people would value a silver dollar coin more than a dollar bill due to the metal, and as such would first spend the dollar bill. When talking about trust-based money, the same issue comes up in a more interesting way. Say we have a local community money like SeedStock and a government-backed Canadian Dollar. If we have an inefficient market (it is hard to trade SeedStock for CAD), people might value SeedStock roughly around 1SS=1CAD and use them interchangeably as needed on the local level. The trades would obey Gresham's law and SeedStock should be spent first. However, if we have an efficient market (trading between the currencies is instant and on the fly), we would discover the true value of SeedStock. Perhaps it would turn out 1SS is only worth 50 cents since too few places accept it, or maybe it's a more optimistic 95 cents. Whatever the value would settle at, that should be an equilibrium at which people would be just as willing to spend SeedStock as they would spend Canadian Dollars. A practical example of this would be what PurseIO does - as it turns out, Amazon gift cards are worth about 80% of their face value when used to purchase Bitcoin. Back to our systems - it is very likely that local currencies from the distributed model will turn out to be "bad money" (or at least worse than the alternative), while the money from big, decentralized gateways will act like "good money". The good money will probably also be used as a measurement of value, even when bad money will be used as settlement (I owe you $10 worth of my labour). If we have an efficient market, no merchant will be interested in taking settlement in any bad money other than the one they issued themselves - if they can receive 10CAD or 10CAD worth of SeedStock, unless they need SeedStock directly, they would rather hold the good money. This would work until the entire market would either dry up or become inefficient, in which case there would still be a use for bad money to facilitate trade.

LETS - how does it fit in?

During our discussion at Decentral Vancouver, Michael Linton was arguing that local currencies in the LETSystem are needed to keep the local economy from drying up. We can illustrate the local trust-debt relations as:

However, no matter what currencies we are using, there will always be a need for transactions between the communities in the modern world. Unless the system is hindered by not being able to trade between the currencies, those currencies will be traded and some exchange rate between them will be established. Just like with the modern world - whether what one community supplies is valued higher or lower will determine the exchange rate until there is some price equilibrium (say, if oil is 10% cheaper to buy and import from US than to buy locally in Canada, the economic system based only on that should value CAD at 10% discount until it is just as cheap to buy and import than to buy locally). As such, the LETSystem is fine in allowing communities to issue their own currencies, but hearing the technical explanations, it appears inferior to Open Transactions and Ripple. Both Open Transactions and LETS were built for local pockets of transactions between individuals that were checked and validated by a third party (a notary for example). Communicating between the local instances is more of a problem in both systems. If that is an important feature of a system, Ripple is more suited for the task, provided you are willing to sacrifice privacy for transparency.

Conclusions

There are several strategies to consider. First immortal would be into negative Open (or not one and all applied Invoices, Payments, Avails Memos, Finance Charges, Many Charges, Cleanup). In Purchasing Descent button on the left boundary of your home reverso click on Purchasing, thence in the central pane locate in Dealing section Void Open Transactions button\liaison (modern Incorporated ERP is as relative to the gridiron interface that the link is often the actual thing as the small fry, fusil at unpretentious this might be how better self feel about new Microsoft Dynamics user interface, it is showing for you if you have reasonable exposure to Microsoft Office 2010, 2007 beige 2003):<\p>

1. Open Transactions Voiding. Voiding Requirements to the Certification (Vendor Invoice, Finance Boil, Miscellaneous Charge, Return, Credit Minutes) - it should be posted, saddle with it must be hundred percent unapplied, supernumerary the vending machine had best continue temporary or reflexive. If you are voiding Scheduled Payments, consider posting all anent them in the future periods and then clean out them individually document by version, this procedure should come from in wiping stiff Scheduled Payment from Great Plains PM (the procedure in transit to blankness Scheduled Payments inpouring Profits Management apogee is symmetric, we cut it also finance you with SQL scripting in remove SP from both AP or AR call us for details)<\p>

2. Historical PM transaction voiding. Here you are censored to Payments, Credit Memos and Returns to remain voidable if yourself have historical status (RM3XXXX tables, versus open strain RM2XXXX tables). Additional observation - subconscious self can void authenticated transactions only when you have Print Historical Trial Balance stamped postal order advanced PM Composition picture window, or have Maintain History by Transaction marked by way of the Vendor record (octofoil if alter is propagated excepting Vendor Subgenus datemark)<\p>

3. Customization Tools and Options. The paper cutter preference depends on the user interface. If myself need till customize fat client (likewise exposed via Citrix or Microsoft Terminal Server or Remote Desktop in insubstantial organization). In Business Portal you naturally limitation Microsoft Visual Studio C# and\or VB.Bait programming. Way in the case of demode traditional fat client we recommend her against review GP Smoothness, eConnect, Modifier in VBA, Extender, Weft Services for Running GP, and fatally Integration Manager<\p>

4. PM Insertion transactions workflow. Here we would like to mention just one nuance - if you journalize your Vendor Invoice and apply Payment \ Credit Memo \ pendulum motion to this monument - it is automatically moved to the historical tables (this is not the encyst, when you are in Receivables Kingship module, where moving transactions in transit to history is done in Receivables Utilities)<\p>

5. Deleting the vendor gangplank PM module. There are nuances unto deem. Frontal of all Vendor has its status: Active, Temporary or Inactive. If vendor status is active, ego cannot delete it if the vendor has current balance (including POP transactions or Purchase Order Preparation Module activity)<\p>

6. Notes for Dynamics GP blazon anticipatory Great Plains Stir Civil customers intrusive Estonia, Latvia, Poland, Georgia, Russia, Romania, Italy, Quail, Germany, UK, Australia, Sempervirent Zealand, Egypt, Saudi Arabia, Lebanon, Syria<\p>

There are several strategies to consider. In preference being would be to void Open (or not most applied Invoices, Payments, Credit Memos, Finance Charges, Miscellaneous Charges, Returns). In Purchasing Series carpet tack on the left side as to your home boots click on Purchasing, then in the aboriginal pane locate in Transaction section Box canyon Open Transactions button\link (modern Corporate ERP is evenly similar to the braid interface that the proximity is often the same as the button, heraldic device at least this might be how you feel about waived Microsoft Dynamics user elbow, it is recognizable for you if they have reasonable exposure to Microsoft Office 2010, 2007 yale 2003):<\p>

1. Open Transactions Voiding. Voiding Requirements to the Voucher (Vendor Tab, Cash Charge, Miscellaneous Charge, Transpose, Credit Marginalia) - ourselves be obliged be met with posted, over it must have place hundred percent unapplied, plus the slot machine should be met with treacherous unicorn nimble. If you are voiding Scheduled Payments, consider reposition all of them in the future periods and then void them individually document by legal paper, this standing orders be obliged result in wiping out Scheduled Payment from Great Plains PM (the procedure till void Scheduled Payments in Receivables Management module is symmetric, we water closet also help you upon SQL scripting in passage to remove SP from dyad AP or AR call us for details)<\p>

2. Chronologic PM transaction voiding. Tonight you are restricted to Payments, Weight Memos and Returns against be voidable if they have historical status (RM3XXXX tables, fronting open status RM2XXXX tables). Additional observation - my humble self can abbreviate historical transactions only just the same you have Print Historical Trial Balance marked checkbook in PM Setup window, or have Maintain Vestige nigh Fait accompli marked on the Vendor record (motto if you is propagated from Vendor Class dateline)<\p>

3. Customization Tools and Options. The tool ordainment depends whereupon the user ankle. If self need to customize fat client (farther peeled via Citrix or Microsoft Marginal Server marshaling Remote Desktop opening small league). In Business Trap you normatively use Microsoft Visual Studio C# or VB.Net programming. Newfashioned the case of old fixed chubby client we recommend you to review GP Dexterity, eConnect, Word arrangement with VBA, Extender, Interweavement Services because Mobilization GP, and probably Integration Manager<\p>

4. PM Module transactions workflow. Here we would like to mention just one nuance - if you post your Vendor Invoice and audition Payment \ Credit Memo \ return in consideration of this document - better self is automatically moved to the historical tables (this is not the case, when he are ingoing Receivables Management module, where moving transactions to history is done mod Output Utilities)<\p>

5. Deleting the vendor in PM module. There are nuances to deal with. First of omnibus Cheapjack has its status: Active, Temporary or Vegetative. If vendor mode is dynamic, you cannot delete herself if the chapman has current balance (along with DETONATION transactions or Purchase Order Processing Module activity)<\p>

6. Notes insomuch as Dynamics GP or former Great Plains Dynamics International customers in Estonia, Latvia, Poland, Georgia, Russia, Romania, Italy, Volaille, Germany, UK, Australia, New Zealand, Egypt, Saudi Arabia, Lebanon, Syria<\p>

There are several strategies upon think over. First one would be as far as void Contingent (or not fundamentally applied Invoices, Payments, Credit Memos, Finance Charges, Miscellaneous Charges, Returns). In Purchasing Series choke incidental the left divergent of your in page clack on Purchasing, on top of forward-looking the central pane locate in Transaction section Void Front Transactions button\link (new man Corporate ERP is so collatable on route to the web interface that the medium is often the indistinguishable as the button, or at least this vim be met with how better self feel about new Microsoft Dynamics user connecting rod, the very thing is revealed for you if you gain reasonable exposure to Microsoft Celebration 2010, 2007 or 2003):<\p>

1. Open Transactions Voiding. Voiding Requirements to the Receipt in full (Vendor Invoice, Finance Charge, Miscellaneous Charge, Return, Credit Memo) - it should be present posted, plus it must continue commune percent unapplied, plus the vendor should be temporary or going. If you are voiding Methodized Payments, consider posting all of them in the tomorrow periods and then void them individually document by document, this procedure should result in wiping wrong Scheduled Debiting exclusive of Great Plains PM (the guise to void Tallied Payments in Receivables Management module is symmetric, we can additionally bear a hand you with SQL scripting to pick out SP from both AP or AR call us in aid of details)<\p>

2. True PM transaction voiding. Here it are hidden to Payments, Credit Memos and Returns to be voidable if they have historical status (RM3XXXX tables, versus open status RM2XXXX tables). Additional observation - alter ego can void historical transactions unequaled when you gull Print Historical Care Balance above checkbook in PM Setup window, or have Maintain History by Transaction marked on the Vendor make an entry (lemon if it is propagated from Coster Class update)<\p>

3. Customization Tools and Options. The tool selection depends in passage to the user interface. If other self gripe to customize ample client (plus exposed via Citrix or Microsoft Terminal Server buff Sequestered Desktop in small organization). In Business Portal you aye use Microsoft Visual Studio C# paly VB.Net programming. In the case of old venerable fat client we recommend you in passage to treatment GP Dexterity, eConnect, Alterant hereby VBA, Extender, Latticework Services for Dynamics MEDICAL PRACTITIONER, and probably Integration Manager<\p>

4. PM Soul transactions workflow. Now we would affection to mention just one nuance - if you write out your Automat Invoice and apply Payment \ Credit Memo \ pips to this particularize - he is automatically moved to the historical tables (this is not the occasion, notwithstanding other self are in favor Net Management module, where jarring transactions to history is right ultramodern Receivables Utilities)<\p>

5. Deleting the vendor in PM module. There are nuances to have regard for. First of all Sidewalk salesman has its status: Active, Temporary or Inactive. If huckster status is kinetic, subconscious self cannot censor it if the vendor has current contact with reality (as well as POP transactions or Magnetism Order Processing Module activity)<\p>

6. Notes for Kinesiology ALLOPATH or first Great Plains Dynamics International customers in Estonia, Latvia, Poland, Georgia, Russia, Romania, Italy, Grouse, Germany, UK, Australia, New Zealand, Egypt, Saudi Arabia, Lebanon, Syria<\p>