I’ve been working on generic immutability solutions for a while. However, a few months ago, I decided to "forget" everything I learned previously and focus on generating very specific products that solve real and daily problems. For that purpose, I decided to review existing technologies and arm myself with a new toolbox to build solutions. After researching and testing different technologies I stumbled upon Lisk and found its possibilities and community fascinating. This is a short story of how I built my first Lisk PoC, and how I’m going to turn it into a real application for a company that wants to transform the way healthy food is marketed. Global Context Consumers are progressively adopting healthier habits, which include nutrient-rich food, with a critical eye on sustainability. To satisfy this growing demand, new products and services are emerging, ranging from locally produced organic food stores to personalized diet services based on physique and daily activity. One of the biggest problems facing the entire supply chain (not just the consumer), is the lack of transparency. From the moment a grain is sown in the ground until the time it's consumed, it goes through a number of steps (harvest, collection, transformation, packaging, delivery), that are mostly opaque to both the consumer, as well as each intermediary in the chain. Each actor performs internal control on their domain, however this information is usually not shared. This type of fractional and dispersed information does not allow traceability to be generated in a simple way, and also complicates the participation of new actors in the production process. More importantly, the information that reaches the consumer is generally only the one that the last link in the chain deemed to be important, which is reflected on the information printed on the rear of the packaging. What is “Fit”? Although we as technologists assume that all actors in our society have access to unimaginable amounts of technology and tools, reality has shown me that the healthy food sector, and especially small producers (at least in our region), have few alternatives to reach out to their customers with a more detailed narrative regarding how their products are sourced, processed, and brought to market; and specifically how they differ from other producers. I understood that the solution was to find an anchor point and try to build from there. Luckily it transpired that a certain store had the same idea, promoting all of this information themselves, and guaranteeing to their customers that the producers they select are working in a correct and transparent manner. For this they decided to become "oracles" of processes and began to share this information in an open network between the producers and the end customers. Fit is an e-commerce project for a healthy food store (FitMarket Argentina), aiming to offer more transparency to its consumers regarding food, sustainability, and processes, and a new information channel to its suppliers using a network and a mobile app. We started by defining certain types of "tasks" (which are going to coincide in a certain way with the transactions), that Fit was going to administer, and these tasks can be seen listed below: Select the best possible producers/suppliers based upon how they treat the product, respect for the environment, etc. If we think about this from a technical point of view, they would register the producer. (Custom transaction: Register Producer) For some time they would observe the way in which the producer develops his activity and they would generate stamps or reports (this is not modeled yet, as it  has just started!) The producer sends the product to Fit ( , where information that both consider important is loaded). Register Product Fit receives the product, checks it, stores it, seals it. ( ) Finish Transport & Update Product Info A customer acquires the product and Fit sends it, (Not in the demo but really similar to the Supply Chain example). The customer receives the package (it is registered, this is open and gives information to the entire chain!) The customer requires information about what was purchased or about a product of interest. It is quite evident that many of the issues described appear to be quite obvious and simple. Nevertheless, the fact remains that a store that is trying to generate a chain of transparency, in order to differentiate itself from other stores, whilst simultaneously collaborating with producers, and evangelizing the benefits of technologies is quite fascinating. So how does it work? Implemented Custom Transactions The Fit Market proof of concept consists of the following seven custom transactions: Register Market Register Producer Register Product Register Pallet Start Transport Finish Transport Update Product Info 1. Register Market The register market custom transaction lets Fit Market register a new distribution center, entering its name and location, which will later be displayed on a map to trace a product's journey from field to the customer: market = store.account.get( .asset.marketId); (!market.asset.name) { updatedMarketAccount = {
        ...market,
        ...{ : { : .asset.name, : .asset.latitude, : .asset.longitude, : }
        }
    };
    
    store.account.set(market.address, updatedMarketAccount);
} const this if const asset name this latitude this longitude this type "Market" 2. Register Producer The register producer custom transaction lets Fit Market register a new approved healthy food provider, entering its name and location. It will later be possible to add the producer's history, thus creating a direct communication channel between producers and customers. producer = store.account.get( .asset.producerId); (!producer.asset.name) { updatedProducerAccount = {
        ...producer,
        ...{ : { : .asset.name, : .asset.latitude, : .asset.longitude, : }
        }
    };
    
    store.account.set(producer.address, updatedProducerAccount);

} const this if const asset name this latitude this longitude this type "Producer" 3. Register Product This allows a producer to register a new product batch. The required barcode and batch ID will enable clients to search a product's information by scanning them with Fit Market's app. product = store.account.get( .asset.productId); (!product.asset.name) { updatedProductAccount = {
        ...product,
        ...{ : { : .asset.barcode, : .asset.batch, : .asset.name, : .asset.produced_quantity, : .asset.produced_quantity, : .asset.produced_date, : .asset.due_date, : }
        }
    };
    
    store.account.set(product.address, updatedProductAccount);

} const this if const asset barcode this batch this name this produced_quantity this remaining_quantity this produced_date this due_date this type "Product" 4. Register a Pallet Products are usually shipped to Fit Market distribution centers in bulk. This custom transaction will enable producers to prepare a batch and have it ready for shipment. pallet = store.account.get( .asset.palletId); (!pallet.asset.status) { sender = store.account.get( .senderId); senderBalancePostageDeducted = utils.BigNum(sender.balance).sub( utils.BigNum( .asset.postage)); updatedSender = {
        ...sender, : senderBalancePostageDeducted.toString(),
    };

    store.account.set(sender.address, updatedSender); product = store.account.get( .asset.productId); productRemainingQuantity = product.asset.remaining_quantity - .asset.product_quantity;

    product.asset.remaining_quantity = productRemainingQuantity;

    store.account.set(product.address, product); palletBalanceWithPostage = utils.BigNum(pallet.balance).add( utils.BigNum( .asset.postage)); updatedPalletAccount = {
        ...pallet,
        ...{ : palletBalanceWithPostage.toString(), : { : .asset.recipientId, : .senderId, : .asset.security, : .asset.postage, : , : , : .asset.productId, : .asset.product_quantity
            }
        }
    };
    
    store.account.set(pallet.address, updatedPalletAccount);

} const this if /*
     * Update the sender account:
     * - Deduct the postage from senders' account balance
     */ const this const new new this const balance /*
     * Update the product account:
     * - Deduct product_quantity from product's remaining_quantity
     */ const this const this /*
     * Update the pallet account:
     * - Add the postage to the pallet account balance
     * - Add all important data about the pallet inside the asset field:
     *   - recipient: ID of the pallet recipient
     *   - sender: ID of the pallet sender
     *   - carrier: ID of the pallet carrier
     *   - security: Number of tokens the carrier needs to lock during the transport of the pallet
     *   - postage: Number of tokens the sender needs to pay for transportation of the pallet
     *   - status: Status of the transport (pending|ongoing|success|fail)
     *   - product: ID of the product
     *   - product_quantity: amount of products carried on this pallet
     */ const new new this const balance asset recipient this sender this security this postage this status 'pending' carrier null product this product_quantity this 5. Start Transport Similar to Lisk's supply chain example, the start transport transaction is launched by a carrier, who will transport the pallet from the producer to Fit Market. It will lock the security fee from the carrier's balance while the shipment is ongoing. pallet = store.account.get( .asset.palletId); (pallet.asset.status === ){ carrier = store.account.get( .senderId); carrierBalance = utils.BigNum(carrier.balance); palletSecurity = utils.BigNum(pallet.asset.security); (carrierBalance.gte(palletSecurity)) { carrierBalanceWithoutSecurity = carrierBalance.sub(palletSecurity); updatedCarrier = {
            ...carrier,
            ...{ : carrierBalanceWithoutSecurity.toString(), : { : pallet.asset.security,
                }
            }
        };
        
        store.account.set(carrier.address, updatedCarrier); pallet.asset.status = ;
        pallet.asset.carrier = carrier.address;
        store.account.set(pallet.address, pallet);
    }
} const this if "pending" const this const new const new if /*
         * Update the Carrier account:
         * - Lock security inside the account
         * - Remove the security form balance
         */ const const balance asset lockedSecurity /*
         * Update the Packet account:
         * - Set status to "ongoing"
         * - set carrier to ID of the carrier
         */ "ongoing" 6. Finish Transport Similar to Lisk's supply chain example, the finish transport transaction lets Fit Market announce the success or failure of the shipment after the delivered product's inspection. pallet = store.account.get( .asset.palletId); carrier = store.account.get(pallet.asset.carrier); sender = store.account.get(pallet.asset.sender); recipient = store.account.get( .senderId); (recipient.address === pallet.asset.recipient) { (pallet.asset.status !== ) {
        errors.push( TransactionError( , .id, , .asset.status
            )
        ); errors;
    } ( .asset.status === ) { carrierBalanceWithSecurityAndPostage = utils.BigNum(carrier.balance).add( utils.BigNum(pallet.asset.security)).add( utils.BigNum(pallet.asset.postage));

        carrier.balance = carrierBalanceWithSecurityAndPostage.toString();
        carrier.asset.lockedSecurity = ;

        store.account.set(carrier.address, carrier); pallet.balance = ;
        pallet.asset.status = ;

        store.account.set(pallet.address, pallet); errors;
    } senderBalanceWithSecurityAndPostage = utils.BigNum(sender.balance).add( utils.BigNum(pallet.asset.security)).add( utils.BigNum(pallet.asset.postage));

    sender.balance = senderBalanceWithSecurityAndPostage.toString();

    store.account.set(sender.address, sender); carrier.asset.lockedSecurity = ;

    store.account.set(carrier.address, carrier); pallet.balance = ;
    pallet.asset.status = ;

    store.account.set(pallet.address, pallet); errors;
} let this let let let this // if the transaction has been signed by the pallet recipient if // if the pallet status isn't "ongoing" if "ongoing" new 'FinishTransport can only be triggered, if pallet status is "ongoing"' this 'ongoing' this return // if the transport was a success if this "success" /*
         * Update the Carrier account:
         * - Unlock security
         * - Add postage & security to balance
         */ const new new new null /*
         * Update the Packet account:
         * - Remove postage from balance
         * - Change status to "success"
         */ '0' 'success' return // if the transport failed /*
     * Update the Sender account:
     * - Add postage and security to balance
     */ const new new new /*
     * Update the Carrier account:
     * - Set lockedSecurity to 0
     */ null /*
     * Update the Packet account:
     * - set status to "fail"
     * - Remove postage from balance
     */ '0' 'fail' return 7. Update Product Info Small local producers usually don't have the required skills or tools to give additional information about their products directly to their customers. This transaction allows Fit Market to fill in the gaps. This information helps Fit Market's clients have actionable information about their products, especially for those who have specific dietary needs. product = store.account.get( .asset.productId); (!product.asset.fitinfo) { product.asset.fitinfo = {};
    product.asset.fitinfo.organic = .asset.organic;
    product.asset.fitinfo.noTACC = .asset.noTACC;
    product.asset.fitinfo.transFat = .asset.transFat;
    product.asset.fitinfo.daily_units = .asset.daily_units;
    product.asset.fitinfo.market = .senderId;

    store.account.set(product.address, product);
} const this if /*
     * Update the product account:
     *   - organic: true | false | unknown
     *   - noTACC: true | false | unknown
     *   - transFat: true | false | unknown
     *   - daily_units: MAX daily units according to ingredients
     */ this this this this this Components of the PoC Working custom transactions that can run on Lisk. Back-end: A minimal ExpressJS front-end to register markets, producers, products & pallets, start and finish transports, and update key product information (interact with transactions). Front-end: Front-end From the beginning I wanted to separate the project from the PoC and the front-end from the back-end. It has really been quite complex to establish this, especially when the PoC is mutating to a "real project". However, I am sure that one of the keys to overall user adoption is related to usability. That's why I'm still working on the final interfaces, but a reference to them can be seen below: Resources : GitHub https://github.com/wozalabs/fit_market : DEMO http://169.57.173.116:3000/ Conclusions My conclusions consist of the following observations, one regarding the technical side and about Lisk in particular, and a general one about food traceability. From a technical viewpoint, the possibilities that Lisk offers and especially its community and its constant desire to be a useful tool to develop solutions do not cease to impress me. I think great things can only be expected from this technology together with the team behind it, and I will continue to become more and more involved in it. Regarding the case of food traceability, on which I will surely continue working, I can only state that there is a distinct lack of knowledge by the general public, and also in some cases professionals and technologists, regarding new technologies, and also how to take advantage of them to change the processes of production, consumption, information and therefore our daily lives. Beyond the great statements that we continually read and consult, the penetration that this originates in other sectors is minimal and I believe we have a great possibility of working to improve in the future. Future developments Luckily this project continues on and is growing larger and larger having many participants wanting to be part of it. Furthermore, Fitmarket will open its first branch in Switzerland in 2 weeks. Regarding the technical issues, I intend to add information on sustainability by crossing not only information provided by the relevant actors, but also its crossing with geospatial information. In addition, I do not rule out the use of remote sensors to automate part of the processes. I will need to evangelize about technologies, improve the frontend, and begin to integrate chains of different types of information on the same source. I think I have an interesting challenge ahead of me, although fortunately I have found technologies and tools that provide me with viable alternatives as well as a very active community. Disclaimer: This blog post was written by our community member, Sebastian Priolo as part of his participation in the Lisk Builders program.

Chain

Lisk

Trace

Visit us

Too Long; Didn't Read

Build JavaScript blockchain apps easily with Lisk

How I Built the Fit Ecommerce App with Lisk

Too Long; Didn't Read

Companies Mentioned

Coin Mentioned

@lisk

RELATED STORIES