LegalLab

Desktop WPF application allowing you to work and experiment with TAG Legal objects:

• Digital IDs
• Smart Contracts
• e-Daler Wallet
• Contractual & Conditional Payments
• Marketplace Auctions
• Neuro-Features

Note: MicrosoftInterop

To compile the project, you need to clone the MicrosoftInterop repository into a folder parallel to the LegalLab folder. The LegalLab application uses a library from this repository, that converts Microsoft Word to Markdown. This library allows LegalLab to create smart contracts from Word documents.

Setup File

A setup file for LegalLab exists, and can be downloaded from https://lab.tagroot.io/Downloads/LegalLab/setup.exe.

Example Contracts

The repository contains several example contracts that can be used as templates in order to experiment and get to learn how to use TAG technologies.

• Marketplace contains Marketplace examples.

  • Buying Services contains examples related to buying services on the marketplace.

    • BuyService.xml is a Request for Tenders, where a Buyer requests service providers to offer their services to the Buyer. The Aauctioneer selects the best option, or the first offer that reaches the acceptable level. Bad offers are immediately rejected.

    • OfferService.xml represents an offer of a servce by a Seller, requested in a Request for Tenders made in a separate contract by a Buyer.

  • Selling Items contains examples related to selling items on the marketplace.

    • SellItem.xml is a Request for Tenders, where a Seller requests prospective buyers to make offer on an item made for sale by the Seller. The Aauctioneer selects the best option, or the first offer that reaches the acceptable level. Bad offers are immediately rejected.

    • SellToken.xml is a Request for Tenders, where a Seller requests prospective buyers to make offer on a token made for sale by the Seller. The Aauctioneer selects the best option, or the first offer that reaches the acceptable level. Bad offers are immediately rejected.

    • OfferItem.xml represents an offer by a Buyer to by an item (or token), as a response to a Request for Tenders made in a separate contract by a Seller.

• StateMachines contains examples related to creating state-machine-based tokens.

  • Calculator.xml creates a simple calculator state-machine, that can be controlled by local and external text and XML notes.

  • CrowdFunding.xml creates a state-machine for crowd-funding a project. The state-machine also contains an escrow feature that allows the machine to control how funds are released to the project, for the duration of the project.

  • DigitalSensorTwin.xml creates a digital twin of a sensor. The state-machine that is created persists sensor-data from the sensor in two ways: It subscribes to events to receive momentary values as soon as they are available. It also performs polling using a preset interval, to assure key frame values are a available. Sensor data is sampled and accessible both in present reports and history reports.

  • MicroLoan.xml creates a state-machine implementing a micro-loan, where a borrower borrows a small amount of money from a lender for a small amount of time. The state-machine automatically returns the borrowed money according to an agreed plan. Failed attempts are logged, and interest accumulated up to a maximum debt limit.

  • ProjectEscrow.xml creates a state-machine for an escrow account for a project. The buyer of the token invests into the project, and the escrow feature allows the machine to control how funds are released to the project, for the duration of the project.

  • BuyTransferSellEDaler.xml shows how you can buy, transfer and sell eDaler automatically from a state-machine, based on XML-notes added to the token by the parties of the contract. This can be used to automate payment events between participants, without the need for them to be online.

• Syntax contains examples related to the syntax of different aspects of smart contracts.

  • Syntax.xml describes the Markdown syntax available for designing human-readable text in smart contracts. Sign such a contract to illustrate receipt and understanding of the information contained in the contract.

  • CalculatedParameters.xml shows how calculated parameters can be used in contracts.

  • ParameterTypes.xml contains contract parameters of different types. Can be used to test contract interfaces under development.

  • RoleReferenceParameters.xml shows how to use role reference parameters. This allows you to create contracts where you include information from the signatories into the contract text, without having to define separate parameters the users have to edit. This simplifies contract creation, and improves integrity of the information presented.

  • GeoSpatialParameters.xml shows how geo-spatial parameters can be used in contracts.

• Tokens contains examples on how to create and manage Neuro-Feature tokens.

  • Create contains examples on how to create tokens.

    • Specific contains specific examples on how to create tokens.

      • Achievement.xml creates a unique achievement token that can be awarded to a recipient for special occations.

      • DemoToken.xml creates a simple token with a friendly name, that can be used for demo.

      • DemoTokens5.xml creates five simple tokens with a friendly name, that can be used for demo.

    • CreateTokenContract1.xml can be used to create one named (ID) token. The operation includes instant payments of commissions.

    • CreateTokenContract1RandomId.xml can be used to create one token, where the Trust Provider assigns a random ID. The operation includes instant payments of commissions.

    • CreateTokenContract1UniqueId.xml can be used to create one token whose ID is determined by its contents, and is therefore guaranteed to be unique. The operation includes instant payments of commissions.

    • CreateTokenContract5.xml can be used to create a batch of five named (ID) tokens. The operation includes instant payments of commissions.

    • CreateTokenContract5RandomId.xml can be used to create a batch of five tokens, where the Trust Provider assigns them random IDs. The operation includes instant payments of commissions.

    • CreateTokenContract5UniqueId.xml can be used to create a batch of five tokens, whose IDs are determined by their contents, and are therefore guaranteed to be unique, as a batch. The operation includes instant payments of commissions.

  • Destroy contains examples on how to destroy tokens.

    • DestroyTokenContract1.xml can be used to destroy a token one owns.

    • DestroyTokenContract5.xml can be used to destroy a batch of five tokens, as long as one owns all tokens in the batch.

  • Donate contains examples on how to donate tokens.

    • DonateTokenContract1.xml can be used to donate a token from the current owner to a new owner. The token maintains its current registered value.

    • DonateTokenContract5.xml can be used to donate a batch of five tokens from the current owner to a new owner. The tokens maintain their currently registered values.

  • Transfer contains examples on how to transfer the ownership of tokens.

    • TransferTokenContract1.xml can be used to transfer the ownership of a token from the current owner to a new owner. The process includes assigning a new value, as well as performing instant payments.

    • TransferTokenContract5.xml can be used to transfer the ownership of a batch of five tokens from the current owner to a new owner. The process includes assigning a new value for the tokens, as well as performing instant payments.

• Voting contains examples related to voting.

  • OpenVoteYesNoAbstain.xml shows how to create a contract that creates a Neuro-Feature token for an open voting procedure. Voting is performed by participants signing ballot contracts with containing information about how they vote. Presentation of voting counts is done using token reports. Layouts and images are available in the ExampleImages and ExampleLayouts folders.

  • OpenBallotYesNoAbstain.xml is a contract representing a ballot in an open voting procedure. Each signed ballot gets counted in the corresponding open voting procedure and presented by the open voting token.

• Memberships contains examples related to membership tokens.

  • Simple models a simple organization token that validates and counts membership applications and memberships. Each membership is also modelled as a token. Membership token is modelled as a static membership certificate.

    • SimpleOrganization.xml contains the contract that creates the simple organization.

    • Membership.xml contains the contract that creates the membership application.

• Construction contains examples related to construction.

  • BimRegister.xml shows how to use a token as a processor of BIMXML documents to reflect changes made to buildings.

• Logistics contains examples related to logistics.

  • SimpleOrder.xml shows how to use a contract with calculated parameters and role-reference parameters to simplify the process of collecting order information and providing validated infomration, in a decentralized manner.